This document summarizes the various interfaces in a GSM network and their functions. It describes:
- The MS-BTS interface (Um interface) and its layers and protocols.
- The BTS-BSC interface (Abis interface) and its layers.
- The BSC-MSC interface (A interface) and its protocols for administration and control of radio resources.
- Other interfaces like MSC-VLR (B), MSC-HLR (C), VLR-HLR (D), MSC-MSC (E), MSC-EIR (F), VLR-VLR (G), HLR-AUC (H), and BSC-TR
• -How the channel concept is used on the radio interface
• -Different burst formats in the radio interface
• -The hierarchical frame structure
• -The content sent in different logical channels
• -The mapping of the logical channels
• -Superframe and Hyperframe
• -MOBILE STATIONS ISDN NUMBER (MSISDN)
• INTERNATIONAL MOBILE SUBSCRIBER IDENTITY (IMSI)
• TEMPORARY MOBILE SUBSCRIBER IDENTITY (TMSI)
• LOCATION AREA IDENTITY (LAI)
• CELL GLOBAL IDENTITY (CGI)
• BASE STATION IDENTITY CODE (BSIC)
• PIN management
Mobile Networks Architecture and Security (2G to 5G)
+ Mobile Networks History 2G/3G/4G/LTE/5G
+ CS/PS/EPC/5GC Core Network Elements Overview
+ Mobile Networks Basic Scenarios
+ Mobile Network Security
+ Authentication / Ciphering
• -How the channel concept is used on the radio interface
• -Different burst formats in the radio interface
• -The hierarchical frame structure
• -The content sent in different logical channels
• -The mapping of the logical channels
• -Superframe and Hyperframe
• -MOBILE STATIONS ISDN NUMBER (MSISDN)
• INTERNATIONAL MOBILE SUBSCRIBER IDENTITY (IMSI)
• TEMPORARY MOBILE SUBSCRIBER IDENTITY (TMSI)
• LOCATION AREA IDENTITY (LAI)
• CELL GLOBAL IDENTITY (CGI)
• BASE STATION IDENTITY CODE (BSIC)
• PIN management
Mobile Networks Architecture and Security (2G to 5G)
+ Mobile Networks History 2G/3G/4G/LTE/5G
+ CS/PS/EPC/5GC Core Network Elements Overview
+ Mobile Networks Basic Scenarios
+ Mobile Network Security
+ Authentication / Ciphering
Global system for mobile communication(GSM)Jay Nagar
~Introduction
~GSM Architecture
~GSM Entities
~SMS Service In GSM
~Call Routing In GSM
~PLMN Interfaces
~GSM Addresses and Identifiers
~Network aspects in GSM
~Handover
~Mobility Management
~GSM Frequency Allocation
~Authentication and Security In GSM
Introduction of PS Core Network Elements and little bit of EPC/LTE Network. This is introductory slides pack for a 10 class/slides set for detail introduction of 2G/3G and LTE PS Core Network.
Topics covered in this presentation:
1. RF spectrum and GSM specifications
2. FDMA and TDMA
3. Digital Voice Transmission
4. Channel coding, Interleaving and Burst formatting
5. GMSK
6. Frame structure of GSM
7. Corrective actions against multipath fading
Global system for mobile communication(GSM)Jay Nagar
~Introduction
~GSM Architecture
~GSM Entities
~SMS Service In GSM
~Call Routing In GSM
~PLMN Interfaces
~GSM Addresses and Identifiers
~Network aspects in GSM
~Handover
~Mobility Management
~GSM Frequency Allocation
~Authentication and Security In GSM
Introduction of PS Core Network Elements and little bit of EPC/LTE Network. This is introductory slides pack for a 10 class/slides set for detail introduction of 2G/3G and LTE PS Core Network.
Topics covered in this presentation:
1. RF spectrum and GSM specifications
2. FDMA and TDMA
3. Digital Voice Transmission
4. Channel coding, Interleaving and Burst formatting
5. GMSK
6. Frame structure of GSM
7. Corrective actions against multipath fading
This presentation discusses about the WCDMA air Interface used in 3G i.e. UMTS. This Radio Interface has great capability on which Third Generation of Mobile Communication is built, with backward compatibility.
Overview 5G Architecture Options from Deutsche TelekomEiko Seidel
At 3GPP RAN#72 5G Architecture discussion took place. This document lists all options that are under discussion.
Source: RP-161266 at RAN#72 Deutsche Telekom
AT&T View on LTE to 5G Network Migration Eiko Seidel
3GPP currently investigates possible 5G architecture options and how to migrate from LTE to 5G. The first stip will be to use Dual Connectivity with 5G while LTE is the Primary Cell. This will allow for very early deployments. Further steps are still to be defined and highly depend on the relation of EPC and Next Generation Core.
Ultra-Reliable Networks – A Mobile Operator Perspective3G4G
Presented by Critical Communications World, Amsterdam – June 2nd 2016 by Mansoor Hanif, Director of Radio Access Networks, EE
*** Shared with permission ***
GSM Air Interface, GSM Frequency Band
PPT File (https://drive.google.com/file/d/1xGLIMwstH1B7Z8y4kLS72HUG-XMtckvb/view?usp=sharing)
Reference: Eng. Waleed El-Safoury Presentations
ell Allocation (CA) is the subset of the total frequency band that is available for one BTS. It can be viewed as the total transport resource available for traffic between the BTS and its attached MSs. One Radio Frequency CHannel (RFCH) of the CA is used to carry synchronization information and the Broadcast Control CHannel (BCCH). This can be any of the carriers in the cell and it is known as the BCCH carrier or the c
carrier. Strong efficiency and quality requirements have resulted in a
0
rather complex way of utilizing the frequency resource. This chapter describes the basic principles of how to use this resource from the physical resource itself to the information transport service offered by the BTS.
Carrier separation is 200 kHz, which provides: • 124 pairs of carriers in the GSM 900 band • 374 pairs of carriers in the GSM 1800 band • 299 pairs of carriers in the GSM 1900 band
Using Time Division Multiple Access (TDMA) each of these carriers is divided into eight Time Slots (TS). One TS on a TDMA frame is called a physical channel, i.e. on each duplex pair of carriers there are eight physical channels.
A variety of information is transmitted between the BTS and thMS. The information is grouped into different logical channelsEach logical channel is used for a specific purpose such as paging, call set-up and speech. For example, speech is sent on the logical channel Traffic CHannel (TCH). The logical channels are mapped onto the physical channels.
The information in this chapter does not include channels specific for GPRS (General Packet Radio Service). For basic information on GPRS see chapter 14 of this documentation.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex ProofsAlex Pruden
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
5. MS-BTS interface (Um interface)
Layer 1: Radio subsystem layer (Physical layer)
Layer 2: LAPDm (modified version of ISDN LAPD
protocol)-protected transfer of signalling messages
Layer 3: Three protocols
RIL3-RR (Radio Interface Layer 3 - Radio Resource
management)
Direct MS-BSC communication
paging, ciphering, handover, radio channel
access
RIL3-MM (Mobility Management)
Direct MS-MSC communication
Roaming & Authentication procedures
RIL3-CM (Connection Management)
Direct MS-MSC communication
Call establishment and release
6. BTS-BSC interface (Abis)
Three layers:
Layer 1: Physical layer
Layer 2: LAPD
Layer 3: BTS Management Protocol
Start of ciphering process
Paging to localize an MS of connection set-up.
Used for
signalling exchange between BSC and BTS
Synchronization information from BSC to BTS
Voice-data traffic
7. BSC-MSC Interface (A)
Message Transfer Part (MTP)
Routing and protected transport of signalling messages
Message transport in SS7 network
Signalling Connection Control Part (SCCP)
Connection-less SCCP: Paging from MSC to BSC
Connection oriented SCCP
BSS Application Part (BSSAP)
BSS Management Application Part (BSSMAP)
Admn. and control of Radio resources,
Maintenance & hand-over control
Direct Transfer Application Part (DTAP)
Direct interface between MSC and MS
DTAP-MM & DTAP-CM
8. B, C, D, E, F Interfaces
MSC-VLR Interface (B)
Internal interface as VLR resides in MSC
MSC-HLR Interface (C)
MAP protocol to retrieve routing information from HLR and to
store routing information in HLR
TCAP protocol to manage dialog between two network entities
VLR-HLR Interface (D)
MAP protocol to support the transfer, cancel or modify the
subscriber information
MSC-MSC Interface (E)
ISUP
MAP protocol for inter-MSC handover and SMS
MSC-EIR Interface (F)
MAP protocol to retrieve IMEI from EIR
9. G, H, M Interfaces
VLR-VLR Interface (G)
MAP protocol to support transfer of subscriber
information between VLRs
HLR-AUC Interface (H)
Internal interface
MAP protocol to HLR to access AUC database.
BSC-TRAU Interface (M)
Internal interface
Encodes bit rate of A-interface (64 kbps) to the
A-bis interface (16 kbps)
10. Multiplexing Technique
Sharing of scarce transport medium resource by use
of a fixed partitioning between several users. GSM
standard has two simultaneous multiplexing
techniques.
Time Division Multiple Access (TDMA)
Resource is shared by time
Each channel is divided into timeslots, each conversation
uses one timeslot.
Many conversations are multiplexed into a single channel.
GSM standard divides each channel (carrier frequency)
into bursts [0.577 ms]. 8 such bursts are a frame.
11. Multiplexing Technique…..
Frequency Division Multiple Access (FDMA)
Resource is shared by frequency
Available frequency band (25MHz freq.) is divided
into 124 sub-bands (separate physical radio
communication channel).
Each channel is identified by central frequency
i.e. carrier frequency
Each base station gets few of those carrier
frequencies.
13. Um Interface
Interface between Mobile Station (MS) and
Base Station (BS)
Two types of channels
Physical Channel
TDMA (Time Division Multiple Access) frame
Logical Channel: These are transmitted on time
slots of the physical channels.
Payload transport
Signalling
Synchronization
Channel assignment etc.
14. Logical channels
It transports either user data during a call or
signalling information for MS or base station.
Two groups of logical channels:
Traffic Channels, for call data
Signalling (control) channels, to communicate
service data between network equipment
nodes.
15. Traffic channel (TCH)
Transmission of user payload data (speech,
data, fax)
Do not carry any control information
Communication over TCH can be
Circuit-switched (Telephony)
Packet-switched
May be fully used (full-rate TCH, TCH/F)
Gross bit rate of 22.8 kbit/sec
Provides a net bit rate at 13 kbit/sec for coded speech.
data streams at 14.4, 12, 9.6, 6, 4.8, 3.6 or 2.4 kbit/sec.
Also known as Bm channel (Mobile B channel)
16. Traffic channel (TCH)…
May be split into two half-rate traffic channels
(half-rate TCH, TCH/H)
can be allocated to different subscribers
Two users share a voice channel
Less transmission bandwidth than full-rate TCH
channels hence doubling the network capacity.
Gross bit rate of 11.4 kbit/sec
Provides a net bit rate for coded speech of 6.5 kbit/sec.
Half-rate data services with 6, 4.8, 3.6 and 2.4 kbit/sec.
Also known as Lm channel (lower-rate mobile channel)
Enhanced full rate traffic channel (TCH/EFR)
Improved voice quality
Provides net bit rate of 12.2 kbit/sec.
17. Signalling (Control) channel
During a call, signalling channel is associated
with a traffic channel and supports the radio
link between the mobile terminal and the BS.
When no active connection, signalling
information like Location Update is
permanently transmitted over the air interface
to the BS.
Offers a continuous signalling service to MSs.
Also known as Dm channel (mobile D
channel)
18. Signalling channel…
Three types
1. Broadcast Channel (BCH)
2. Common Control Channel (CCCH)
3. Dedicated/ Associated Control Channel
(D/ACCH)
19. Signalling channel…
1. Broadcast Channel (BCH)
Uni-directional signalling channel (BSS to MS) i.e.
Downlink channels
Used by Base Station Sub-system (BSS) to broad cast
the same information to all MSs in a cell.
2. Common Control Channel (CCCH)
Uni-directional signalling channel (either Up-link or Down-
link) to deal with access management
Assignment of dedicated channels (SDCCH)
Paging to localise a Mobile station.
3. Dedicated/ Associated Control Channel
(D/ACCH)
Bi-directional signalling channel (Up-link and Down-link)
to deal with access management
20. Broadcast Channel (BCH)
Four types
1. Broadcast Control Channel (BCCH)
2. Frequency Correction Channel (FCCH)
3. Synchronisation Channel (SCH)
4. Cell Broadcast Channel (CBCH)
21. Broadcast Control Channel (BCCH)
Broadcast on the first frequency assigned
to the cell (BCCH carrier)
Radio channel configuration of currently
used cell and of neighboring cells
Contains parameters used by MS to
access the network, e.g. CGI, LAI, RAI,
BA, BSIC, ciphered mode etc.
Synchronization information (Frequency
as well as TDMA frame number)
22. Broadcast Channel (BCH)
2. Frequency Correction Channel (FCCH)
Information about correction of transmission
frequency
Sends a constant frequency shift of the radio
frequency carrier (i.e. Pure carrier wave).
Always broadcast with BCCH
3. Synchronisation Channel (SCH)
Broadcasts information to identify a BTS (BSIC)
(i.e. Base Station transceiver Identity Code)
Broadcasts data for the frame Synchronisation of
an MS. (TDMA frame number)
Always broadcast with BCCH
4. Cell Broadcast Channel (CBCH)
Sends SMS messages in a cell
23. Common Control Channel (CCCH)
Four types
1. Random Access Channel (RACH)
2. Access Grant Channel (AGCH)
3. Paging Channel (PCH)
4. Notification Channel (NCH)
24. Common Control Channel (CCCH)
1. Random Access Channel (RACH)
From MS to BSS i.e. uplink portion of CCCH
Request for a dedicated channel (SDCCH) by an
MS for exclusive use of the MS for one signalling
transaction.
2. Access Grant Channel (AGCH)
From BSS to MS i.e. downlink portion of CCCH
Used to assign an SDCCH or a TCH to a MS.
25. Common Control Channel (CCCH)
3. Paging Channel (PCH)
From BSS to MS i.e. downlink portion of CCCH.
When an incoming call arrives, BS sends out a
request on the PCH to find the mobile stations
requested by the call to activate the call
establishment process.
4. Notification Channel (NCH)
From BSS to MS i.e. downlink portion of CCCH.
Used to inform all MSs about incoming group and
broadcast calls.
26. Dedicated/Associated Control Channel (D/ACCH)
Three types
1. Stand-alone Dedicated Control Channel
(SDCCH)
2. Slow Associated Control Channel (SACCH)
3. Fast Associated Control Channel (FACCH)
27. Stand-alone Dedicated Control Channel (SDCCH)
Not tied to the existence of TCH.
Used for signalling between an MS and BS when there is
no active connection.
Requested from MS via RACH and assigned via AGCH.
After the completion of signalling transaction, SDCCH is
released and can be re-assigned to another MS.
Examples: Updating of location information, subscriber
authentication, ciphering initiation or parts of the
connection set-up until the connection is switched
through, assignment of TCH.
Net bit rate is 0.8 kbps.
28. Slow Associated Control Channel (SACCH)
Always assigned and used with
TCH/FACCH or SDCCH.
Carries information for maintenance of the
connection e.g.
command for synchronisation, transmitter
power control, timing advance data on the
down-link and
Radio link measurements reports on the up-
link.
29. Fast Associated Control Channel (FACCH)
Always assigned with TCH.
Using dynamic pre-emptive multiplexing on a
TCH, additional bandwidth can be made
available for signalling for shorter duration. i.e.
during handover or call release.
FAACH data is transmitted over the allocated
TCH.
Marked by a stealing flag.
Its short time usage is at the expanse of the
user data transport.
30. Frame types on the Um interface
TDMA frame
One Time slot (Burst Period)= 0.577 ms
TDMA frame= 8 BP = 8* 0.577ms = 4.62 ms.
26-TDMA multi-frame
26 TDMA frames= 26 * 8 BP = 120 ms cycle
51-TDMA multi-frame
51 TDMA frames= 51 * 8 BP = 235 ms cycle
Super frame
51 * 26 TDMA frames= 51 * 26 * 8 BP= 6.12 sec
Hyper frame
2048 super frames = 2048 * 6.12 sec= 3 hours 28
minutes 53 sec. and 760 ms.
32. Abis-Interface configuration
PCM 30 (E1) On Abis
Timeslot 0 is used for synchronization purposes
Timeslots 1 to 31 are used for exchanging the
Um-interface formatted 13kbit/s data for signaling.
The 13 kbit/s data is sub-multiplexed into the 64
kbit/s PCM 30-channels of the Abis-interface.
sub-timeslots (16 kbps) carries one traffic channel
with a traffic data rate of 13kbit/s. The remaining
3 kbit/s are used for synchronization and in band
signaling between the BTS and BSC.
Abis-link can carry physical channels from up to
12 TRXs
34. Abis-Interface configuration…..
PCM 24 (T1) On Abis
A framing bit (F) is added to the beginning of
each frame to allow detection of frame
boundaries (synchronization) and for transport of
additional maintenance information.
Timeslots 1 to 31 are used for exchanging the
Um-interface formatted 13kbit/s data for signaling.
The 13 kbit/s data is sub-multiplexed into the 64
kbit/s PCM 30-channels of the Abis-interface.
Each sub-timeslots (16 kbps) carries one traffic
channel with a traffic data rate of 13kbit/s. The
remaining 3 kbit/s are used for synchronization
and in band signaling between the BTS and BSC.
Abis-link can carry physical channels from up to
10 TRXs
35. Signaling link concentration
Both TRX related signaling and cell (O&M)
related signaling can be combined into a single
timeslot on the Abis-interface. However, all
signaling channels sharing a timeslot must
belong to the same cell.
This implies that one timeslot can accommodate
signaling for:
Up to four TRXs (all TRXs must be in the same
cell) or,
Three TRXs + one O&M (all TRXs must be in the
same cell and O&M must relate to that cell).
37. A-Interface configuration
PCM 30 (E1) on A link
Timeslot 0 is used for synchronization
purposes
Timeslots 1 to 31 and 17 to 31 are used for
exchanging the 64kbit/s speech data.
Timeslot 16 is used to transfer the CCS#7
signaling between the BSC and the MSC.
PCM 24 (T1) on A link
framing bit for synchronization is added
before time slot1
Time slot 1 to 15 and 17 to 24 are used for
exchanging the 64 kbit/s/ speech data.
39. M-Interface
Internal interface (BSC-TRAU)
The M-interface is a multiplexed and
transcoded A-interface.
TRAU (Transcoder/Rate Adapter Unit)
encodes the 64 kbit/s PCM signal to a 16
kbit/s signal,
Transcodes four channels of an A-
interface into one channel of an M-
interface.
40. M interface configuration
M interface on PCM 30
Each of the timeslots 1 to 15 and 17 to 31 on
the M-interface contains four multiplexed A-
interface channels.
Timeslot 0 is used for synchronization
purposes.
Timeslot 16 contains the signaling information
which is transparently mapped from timeslot
16 of the A-interface.
M interface on PCM 24
Time slot 0 is framing bit (F) for synchronization
Time slot is up to 24