The document provides an overview of elementary procedures for circuit-switched call control in 3GPP networks. It describes the background of related protocol layers and planes. Call control manages call establishment, clearing, information, and miscellaneous procedures. The main call types are mobile-originated, mobile-terminated, and network-initiated mobile-originated calls. Standard L3 messages follow specific formats and structures, and the call state is represented by state diagrams and message flow diagrams.
ims registration call flow procedure volte sipVikas Shokeen
This PDF , VoLTE IMS Registration tutorial covers IMS Registration sip procedure in depth & Provides extract of 3GPP / GSMA Specs , I am covering below call flow in Depth :-
- LTE Attach & Default Internet EPS bearer
- Role of QCI-1 ( Voice ) , QCI-5 (SIP Signaling) , QCI-6 to 9 (Internet)
- Default Vs Dedicated Bearer in LTE
- Default IMS EPS bearer in LTE
- SIP and IMS Registration
- TAS Registration
This document discusses cell selection and reselection in GSM networks. It explains:
1) Cell selection is performed when a mobile first turns on to select an initial "camped-on" cell. Reselection occurs when the mobile moves to ensure it remains on the best cell.
2) C1 and C2 criteria are used for selection and reselection. C1 compares signal levels and C2 adds offsets.
3) In the scenario, the mobile selects the 900MHz cell using C1/C2 criteria. To prefer the 1800MHz cell instead, the document suggests using the C2 formula without offsets by setting the penalty time lower.
This document summarizes the signaling flow between a UE, RNC, and MSC server during the establishment and release of a circuit switched call. It involves the following key steps:
1. The UE sends an RRC Connection Request to the RNC to initiate a call, and the RNC forwards this to the MSC server.
2. The MSC server and RNC then perform authentication and security procedures with the UE.
3. Once authenticated, the call is established with radio bearer setup between the UE and RNC and exchange of call signaling messages between the UE and MSC server.
4. Upon call completion, signaling is exchanged to release the radio bearers and disconnect the call.
The document discusses the physical layer design of WCDMA networks. It provides an overview of WCDMA network architecture and the UMTS network model. It then describes the physical channels, transport formats, channel coding, spreading techniques and code types used in the WCDMA uplink and downlink. Key aspects covered include dedicated and common physical channels, orthogonal variable spreading factor channelization codes, scrambling codes, and transport block sets.
This document discusses cell coverage and ranges for LTE networks. Key points include:
- LTE aims to support cell radii up to 5 km while still enabling coverage of 100km or more, to support high-speed rail and wide-area deployments.
- Cell sizes in LTE can range from a few meters across in indoor environments to radii of 100km or more for large rural cells.
- The random access preamble formats and timing advance mechanisms in LTE are designed to support the maximum cell size of 100km radius to accommodate the largest expected propagation delays.
- A guard period duration of 700 μs supports one-way propagation delays of around 100km, allowing LTE to potentially support cell
The document discusses UMTS planning and dimensioning processes. It describes:
1) The overall planning process which includes system dimensioning, radio network planning, pre-launch optimization, performance monitoring, and post-launch optimization.
2) The inputs, assumptions, and steps used for air interface dimensioning which includes uplink and downlink link budget analysis to determine coverage requirements and capacity needs.
3) Traffic modelling and load calculation methods to estimate subscriber traffic per cell based on factors like subscriber density, traffic profiles, and cell area.
The document provides an overview of GSM protocols:
- It describes the 7 layers of the OSI model and how they relate to network support layers (physical and data link layers) and user support layers (session, presentation, and application layers).
- It explains key GSM protocol layers including the physical layer, data link layer, and signaling layers used for call setup and termination between mobile devices and the core network.
- It also discusses common protocols used in telephone networks like ISDN, SS7, and how protocols like SCCP, TCAP, MAP, and INAP are used to support services like roaming and calling card transactions.
It is a handbook of UMTS/LTE/EPC CSFB call flows.
This document is originally edited by Justin MA and it is free to share to everyone who are interested.
All reference/resource are from internet. If there is any copy-right issue, please kindly inform Justin by majachang@gmail.com.
Thanks for your reading!
ims registration call flow procedure volte sipVikas Shokeen
This PDF , VoLTE IMS Registration tutorial covers IMS Registration sip procedure in depth & Provides extract of 3GPP / GSMA Specs , I am covering below call flow in Depth :-
- LTE Attach & Default Internet EPS bearer
- Role of QCI-1 ( Voice ) , QCI-5 (SIP Signaling) , QCI-6 to 9 (Internet)
- Default Vs Dedicated Bearer in LTE
- Default IMS EPS bearer in LTE
- SIP and IMS Registration
- TAS Registration
This document discusses cell selection and reselection in GSM networks. It explains:
1) Cell selection is performed when a mobile first turns on to select an initial "camped-on" cell. Reselection occurs when the mobile moves to ensure it remains on the best cell.
2) C1 and C2 criteria are used for selection and reselection. C1 compares signal levels and C2 adds offsets.
3) In the scenario, the mobile selects the 900MHz cell using C1/C2 criteria. To prefer the 1800MHz cell instead, the document suggests using the C2 formula without offsets by setting the penalty time lower.
This document summarizes the signaling flow between a UE, RNC, and MSC server during the establishment and release of a circuit switched call. It involves the following key steps:
1. The UE sends an RRC Connection Request to the RNC to initiate a call, and the RNC forwards this to the MSC server.
2. The MSC server and RNC then perform authentication and security procedures with the UE.
3. Once authenticated, the call is established with radio bearer setup between the UE and RNC and exchange of call signaling messages between the UE and MSC server.
4. Upon call completion, signaling is exchanged to release the radio bearers and disconnect the call.
The document discusses the physical layer design of WCDMA networks. It provides an overview of WCDMA network architecture and the UMTS network model. It then describes the physical channels, transport formats, channel coding, spreading techniques and code types used in the WCDMA uplink and downlink. Key aspects covered include dedicated and common physical channels, orthogonal variable spreading factor channelization codes, scrambling codes, and transport block sets.
This document discusses cell coverage and ranges for LTE networks. Key points include:
- LTE aims to support cell radii up to 5 km while still enabling coverage of 100km or more, to support high-speed rail and wide-area deployments.
- Cell sizes in LTE can range from a few meters across in indoor environments to radii of 100km or more for large rural cells.
- The random access preamble formats and timing advance mechanisms in LTE are designed to support the maximum cell size of 100km radius to accommodate the largest expected propagation delays.
- A guard period duration of 700 μs supports one-way propagation delays of around 100km, allowing LTE to potentially support cell
The document discusses UMTS planning and dimensioning processes. It describes:
1) The overall planning process which includes system dimensioning, radio network planning, pre-launch optimization, performance monitoring, and post-launch optimization.
2) The inputs, assumptions, and steps used for air interface dimensioning which includes uplink and downlink link budget analysis to determine coverage requirements and capacity needs.
3) Traffic modelling and load calculation methods to estimate subscriber traffic per cell based on factors like subscriber density, traffic profiles, and cell area.
The document provides an overview of GSM protocols:
- It describes the 7 layers of the OSI model and how they relate to network support layers (physical and data link layers) and user support layers (session, presentation, and application layers).
- It explains key GSM protocol layers including the physical layer, data link layer, and signaling layers used for call setup and termination between mobile devices and the core network.
- It also discusses common protocols used in telephone networks like ISDN, SS7, and how protocols like SCCP, TCAP, MAP, and INAP are used to support services like roaming and calling card transactions.
It is a handbook of UMTS/LTE/EPC CSFB call flows.
This document is originally edited by Justin MA and it is free to share to everyone who are interested.
All reference/resource are from internet. If there is any copy-right issue, please kindly inform Justin by majachang@gmail.com.
Thanks for your reading!
It is a handbook of UMTS/WCDMA call flows for PS services.
This document is originally edited by Justin MA and it is free to share to everyone who are interested.
All reference/resource are from internet. If there is any copy-right issue, please kindly inform Justin by majachang@gmail.com.
Thanks for your reading!
The document discusses HSPA MAC-centric technologies including HSDPA and HSUPA. It provides an overview of 3GPP UMTS evolution from Release 5 to Release 8, which introduced HSDPA and HSUPA to improve peak data rates and reduce latency. It describes key aspects of HSPA such as the location of MAC-hs at the Node B to enable fast scheduling and HARQ, as well as transport and physical channels used in HSDPA and HSUPA like HS-DSCH, E-DCH, HS-SCCH, and HS-DPCCH. It also covers flow control between the Node B and RNC and enhancements introduced in Release 6.
The document provides information on basic GSM principles and comparisons between TACS, GSM 900, and DCS 1800 mobile networks. It discusses topics like uplink and downlink frequencies, carrier separation, number of channels, access methods, logical channels, control channels, cell identities, and other key GSM concepts and terms. The document also includes detailed descriptions and explanations of terms like IMSI, TMSI, LAI, CGI, BSIC, SIM, and concepts like cell selection, location updating, and pin management.
This document summarizes GSM architecture and call flows, including inter-MSC and intra-MSC call flows. Inter-MSC call flow occurs between two different MSCs, while intra-MSC call flow is between two BSCs within the same MSC. The inter-MSC call flow involves signaling between the BSC, MSC-O, MSC-T, HLR, and RNC to set up and release the call bearers. The intra-MSC call flow involves signaling between the MS-O, BSC-O, MSC/VLR, MGW, HLR, BSC-T, and MS-T to authenticate, set up, and release call bearers within a single MSC
The document describes the key components of a GSM network and their functions:
- The BTS handles radio transmissions and defines each cell. The BSC manages radio resources and handles handovers between BTSs. The MSC performs switching between mobile and other networks.
- The HLR is a central database that stores subscriber information. The VLR temporarily stores subscriber data needed by the local MSC. The EIR stores valid device IDs. The AUC authenticates users and protects the network from fraud.
Together, these components enable functions like call setup, location updates, authentication, and mobility as users move between cells in a GSM network.
The document provides an overview of GSM, GPRS, UMTS, HSDPA and HSUPA protocols and call flows. It describes the architecture, interfaces and protocols of each generation at the physical, data link and network layers. Key protocols discussed include LAPD, RR, MM, CM, SNDCP, GTP, RLC, MAC, RRC. Call flows for basic call origination, authentication, data transfer and detach procedures are illustrated for each network. The document also introduces HSDPA and HSUPA enhancements to UMTS such as new channels, scheduling functionality and H-ARQ protocol.
The document summarizes the initial call setup process between a UE (user equipment), eNB (base station), MME (mobility management entity), HSS (home subscriber server), S-GW (serving gateway), and P-GW (packet data network gateway). It involves:
1) The UE performing random access and connection requests to the eNB;
2) Authentication and security setup between the UE, MME, and HSS;
3) Context setup and exchange of UE capability information between the UE, eNB, and MME;
4) Session creation between the MME, S-GW, and P-GW to enable data transfer.
LTE uses various frequency bands and duplexing techniques to provide high-speed data and peak download speeds of up to 300 Mbps. It supports mobility of up to 350 km/h and uses advanced technologies like OFDM, SC-FDMA, MIMO and turbo coding to achieve low latency and high bandwidth. LTE specifications define channel bandwidths of 1.4, 3, 5, 10, 15 and 20 MHz with modulation schemes of QPSK, 16QAM and 64QAM.
This document provides an overview of the LTE physical channel structure and procedures between the eNB and UE. It describes the LTE architecture and introduces the main physical channels including downlink channels like PBCH, PDCCH, PDSCH and uplink channels like PUSCH, PUCCH, PRACH. It explains the channel mapping and provides examples of the initial access procedure and synchronization signal transmission. Key concepts covered are radio interface protocol stacks, channel coding, multiple access, and reference signals.
This documents will help to understand the details procedure of GSM IDLE Mode Behavior. GSM Idle mode behavior starting from PLMN selection, GSM Cell Camp, Cell Selection, Cell Reselection, Location Update, Paging, System Information to Measurements procedures have been captured in this document.
This document discusses various types of call forwarding in 3 sentences:
It describes unconditional and conditional call forwarding scenarios as well as no reply, busy, and not reachable scenarios. The state transition models show the signaling flows between network elements like the GMSC, HLR, MSC, and VLR when a call is forwarded due to various conditions like absent subscriber, no reply, radio congestion, or detachment. Registration, erasure, activation, and deactivation functions are also covered with regard to managing call forwarding numbers and services.
We are going to cover complete list of VoLTE IMS KPI and performance Indicators . This includes :-
VoLTE IMS Control Plane KPI
- RSR : Registration Success Ratio (%)
- CSSR : Call Setup Success Rate (%)
- CST : Call Setup Time (s)
- MHT/ACD : Average Call duration (s)
VoLTE IMS User Plane KPI
- Mute Rate (%)
- MOS Score (1-5)
- RTP Packet Loss (%)
- One Way Calls (%)
Packet Core 4G Network LTE KPI
- Volte Attach Success Rate (%)
- VoLTE QCI=5 Paging Success Rate (%)
- Dedicated Bearer Activation Success Rate (%)
- IMS IP POOL Utilization (%)
- Create Bearer Success Rate (%)
Radio VoLTE KPI
- Call Drop rate (%)
- SRVCC Success Rate (%)
- Handover SR (%)
Lte default and dedicated bearer / VoLTEmanish_sapra
LTE uses EPS bearers to carry user data traffic. There are two types of EPS bearers - default bearers and dedicated bearers. Default bearers are created for each PDN connection and provide basic "best effort" internet access. Dedicated bearers provide additional tunnels for specific traffic like VoLTE and can have guaranteed bitrates. Dedicated bearers are linked to a default bearer and inherit properties like the PDN address from the default bearer. GTP is the protocol used to encapsulate and carry bearer traffic through the LTE core network.
The document provides an overview of cellular communications and GSM networks. It discusses the need for cellular networks due to limitations of fixed line phones, introduces concepts like frequency reuse and channelization, and describes the components and architecture of GSM networks including mobile stations, base station controllers, switches and databases. It also summarizes the evolution of GSM standards and technology.
The document outlines basic call flows for location updates, mobile originating calls (MOC), mobile terminating calls (MTC), and IP calls. It describes the key steps as:
1) Location update involves identity response, authentication between the SIM and MSC, update location requests, and ciphering.
2) For MOC, the mobile station sends a setup message with the dialed number, the MSC sends a send routing information message to the HLR, and the HLR responds with routing instructions allowing the call to be connected.
3) For MTC, the MSC requests a roaming number from the HLR, the HLR provides a number and the MSC pages the mobile station to alert
The document discusses various LTE measurement parameters and procedures including:
1. The eNB reports a list of detected PRACH preambles and measures timing advance, average RSSI, average SINR, UL CSI, and transport BLER for RRM purposes.
2. UE measurements include CQI, RSRP, and RSRQ while eNB measurements include timing advance, RSSI, SINR, UL CSI, detected preambles, and transport BLER. Inter-RAT measurements are also discussed.
3. Examples of RSRP, RSRQ, and timing advance procedures are provided along with CQI measurement details. PLMN selection, cell selection,
Inter-frequency and inter-RAT handovers can be coverage, load, or service based. Coverage-based handovers are triggered by certain A3/A4/A5 events for inter-frequency and B1/B2 events for inter-RAT. The document discusses the parameters involved in measuring cells and configuring handovers, including measurement reports, handover commands, and key performance indicators for analyzing handover issues. Common causes of handover problems include poor downlink quality, interference, and abnormal X2 interface signaling.
SS7 is a signaling system originally designed for telephone call setup and management between telephone exchanges and customer equipment. It has been developed to transport data and video traffic as well. SS7 uses out-of-band signaling where signaling information is carried on a separate channel from user data. The SS7 protocol stack includes layers like MTP1-3 for transport and routing, SCCP for additional routing functions, and TCAP to support special services through transactions between switches. A basic SS7 network consists of SSP, STP, SCP connected by signaling links to route messages for services like 800 calls.
It is a handbook of UMTS/WCDMA call flows for PS services.
This document is originally edited by Justin MA and it is free to share to everyone who are interested.
All reference/resource are from internet. If there is any copy-right issue, please kindly inform Justin by majachang@gmail.com.
Thanks for your reading!
The document discusses HSPA MAC-centric technologies including HSDPA and HSUPA. It provides an overview of 3GPP UMTS evolution from Release 5 to Release 8, which introduced HSDPA and HSUPA to improve peak data rates and reduce latency. It describes key aspects of HSPA such as the location of MAC-hs at the Node B to enable fast scheduling and HARQ, as well as transport and physical channels used in HSDPA and HSUPA like HS-DSCH, E-DCH, HS-SCCH, and HS-DPCCH. It also covers flow control between the Node B and RNC and enhancements introduced in Release 6.
The document provides information on basic GSM principles and comparisons between TACS, GSM 900, and DCS 1800 mobile networks. It discusses topics like uplink and downlink frequencies, carrier separation, number of channels, access methods, logical channels, control channels, cell identities, and other key GSM concepts and terms. The document also includes detailed descriptions and explanations of terms like IMSI, TMSI, LAI, CGI, BSIC, SIM, and concepts like cell selection, location updating, and pin management.
This document summarizes GSM architecture and call flows, including inter-MSC and intra-MSC call flows. Inter-MSC call flow occurs between two different MSCs, while intra-MSC call flow is between two BSCs within the same MSC. The inter-MSC call flow involves signaling between the BSC, MSC-O, MSC-T, HLR, and RNC to set up and release the call bearers. The intra-MSC call flow involves signaling between the MS-O, BSC-O, MSC/VLR, MGW, HLR, BSC-T, and MS-T to authenticate, set up, and release call bearers within a single MSC
The document describes the key components of a GSM network and their functions:
- The BTS handles radio transmissions and defines each cell. The BSC manages radio resources and handles handovers between BTSs. The MSC performs switching between mobile and other networks.
- The HLR is a central database that stores subscriber information. The VLR temporarily stores subscriber data needed by the local MSC. The EIR stores valid device IDs. The AUC authenticates users and protects the network from fraud.
Together, these components enable functions like call setup, location updates, authentication, and mobility as users move between cells in a GSM network.
The document provides an overview of GSM, GPRS, UMTS, HSDPA and HSUPA protocols and call flows. It describes the architecture, interfaces and protocols of each generation at the physical, data link and network layers. Key protocols discussed include LAPD, RR, MM, CM, SNDCP, GTP, RLC, MAC, RRC. Call flows for basic call origination, authentication, data transfer and detach procedures are illustrated for each network. The document also introduces HSDPA and HSUPA enhancements to UMTS such as new channels, scheduling functionality and H-ARQ protocol.
The document summarizes the initial call setup process between a UE (user equipment), eNB (base station), MME (mobility management entity), HSS (home subscriber server), S-GW (serving gateway), and P-GW (packet data network gateway). It involves:
1) The UE performing random access and connection requests to the eNB;
2) Authentication and security setup between the UE, MME, and HSS;
3) Context setup and exchange of UE capability information between the UE, eNB, and MME;
4) Session creation between the MME, S-GW, and P-GW to enable data transfer.
LTE uses various frequency bands and duplexing techniques to provide high-speed data and peak download speeds of up to 300 Mbps. It supports mobility of up to 350 km/h and uses advanced technologies like OFDM, SC-FDMA, MIMO and turbo coding to achieve low latency and high bandwidth. LTE specifications define channel bandwidths of 1.4, 3, 5, 10, 15 and 20 MHz with modulation schemes of QPSK, 16QAM and 64QAM.
This document provides an overview of the LTE physical channel structure and procedures between the eNB and UE. It describes the LTE architecture and introduces the main physical channels including downlink channels like PBCH, PDCCH, PDSCH and uplink channels like PUSCH, PUCCH, PRACH. It explains the channel mapping and provides examples of the initial access procedure and synchronization signal transmission. Key concepts covered are radio interface protocol stacks, channel coding, multiple access, and reference signals.
This documents will help to understand the details procedure of GSM IDLE Mode Behavior. GSM Idle mode behavior starting from PLMN selection, GSM Cell Camp, Cell Selection, Cell Reselection, Location Update, Paging, System Information to Measurements procedures have been captured in this document.
This document discusses various types of call forwarding in 3 sentences:
It describes unconditional and conditional call forwarding scenarios as well as no reply, busy, and not reachable scenarios. The state transition models show the signaling flows between network elements like the GMSC, HLR, MSC, and VLR when a call is forwarded due to various conditions like absent subscriber, no reply, radio congestion, or detachment. Registration, erasure, activation, and deactivation functions are also covered with regard to managing call forwarding numbers and services.
We are going to cover complete list of VoLTE IMS KPI and performance Indicators . This includes :-
VoLTE IMS Control Plane KPI
- RSR : Registration Success Ratio (%)
- CSSR : Call Setup Success Rate (%)
- CST : Call Setup Time (s)
- MHT/ACD : Average Call duration (s)
VoLTE IMS User Plane KPI
- Mute Rate (%)
- MOS Score (1-5)
- RTP Packet Loss (%)
- One Way Calls (%)
Packet Core 4G Network LTE KPI
- Volte Attach Success Rate (%)
- VoLTE QCI=5 Paging Success Rate (%)
- Dedicated Bearer Activation Success Rate (%)
- IMS IP POOL Utilization (%)
- Create Bearer Success Rate (%)
Radio VoLTE KPI
- Call Drop rate (%)
- SRVCC Success Rate (%)
- Handover SR (%)
Lte default and dedicated bearer / VoLTEmanish_sapra
LTE uses EPS bearers to carry user data traffic. There are two types of EPS bearers - default bearers and dedicated bearers. Default bearers are created for each PDN connection and provide basic "best effort" internet access. Dedicated bearers provide additional tunnels for specific traffic like VoLTE and can have guaranteed bitrates. Dedicated bearers are linked to a default bearer and inherit properties like the PDN address from the default bearer. GTP is the protocol used to encapsulate and carry bearer traffic through the LTE core network.
The document provides an overview of cellular communications and GSM networks. It discusses the need for cellular networks due to limitations of fixed line phones, introduces concepts like frequency reuse and channelization, and describes the components and architecture of GSM networks including mobile stations, base station controllers, switches and databases. It also summarizes the evolution of GSM standards and technology.
The document outlines basic call flows for location updates, mobile originating calls (MOC), mobile terminating calls (MTC), and IP calls. It describes the key steps as:
1) Location update involves identity response, authentication between the SIM and MSC, update location requests, and ciphering.
2) For MOC, the mobile station sends a setup message with the dialed number, the MSC sends a send routing information message to the HLR, and the HLR responds with routing instructions allowing the call to be connected.
3) For MTC, the MSC requests a roaming number from the HLR, the HLR provides a number and the MSC pages the mobile station to alert
The document discusses various LTE measurement parameters and procedures including:
1. The eNB reports a list of detected PRACH preambles and measures timing advance, average RSSI, average SINR, UL CSI, and transport BLER for RRM purposes.
2. UE measurements include CQI, RSRP, and RSRQ while eNB measurements include timing advance, RSSI, SINR, UL CSI, detected preambles, and transport BLER. Inter-RAT measurements are also discussed.
3. Examples of RSRP, RSRQ, and timing advance procedures are provided along with CQI measurement details. PLMN selection, cell selection,
Inter-frequency and inter-RAT handovers can be coverage, load, or service based. Coverage-based handovers are triggered by certain A3/A4/A5 events for inter-frequency and B1/B2 events for inter-RAT. The document discusses the parameters involved in measuring cells and configuring handovers, including measurement reports, handover commands, and key performance indicators for analyzing handover issues. Common causes of handover problems include poor downlink quality, interference, and abnormal X2 interface signaling.
SS7 is a signaling system originally designed for telephone call setup and management between telephone exchanges and customer equipment. It has been developed to transport data and video traffic as well. SS7 uses out-of-band signaling where signaling information is carried on a separate channel from user data. The SS7 protocol stack includes layers like MTP1-3 for transport and routing, SCCP for additional routing functions, and TCAP to support special services through transactions between switches. A basic SS7 network consists of SSP, STP, SCP connected by signaling links to route messages for services like 800 calls.
The document discusses IS-41 network signaling protocols used for mobility management between cellular networks and the PSTN. It describes the SS7 protocol layers including MTP, SCCP, TCAP, ISUP, OMAP, and MAP. It provides examples of TCAP message flows for registration notification and call setup using ISUP signaling between the PCN and PSTN.
The document discusses data link layer and media access control. It covers the following key points:
1. The data link layer is responsible for framing data, performing error checking and flow control between adjacent nodes. It has two sublayers - the logical link control and media access control layers.
2. The media access control layer controls how devices access and share the physical layer transmission medium. It uses protocols like CSMA/CD for Ethernet and CSMA/CA for wireless networks.
3. Framing involves adding headers and trailers to divide data into manageable units called frames. Protocols use byte-oriented or bit-oriented approaches for framing, with techniques like character stuffing to delimit frames
Computer Networks Unit 2 UNIT II DATA-LINK LAYER & MEDIA ACCESSDr. SELVAGANESAN S
The document discusses data link layer framing and protocols. It describes:
1) Two main approaches to framing - byte-oriented (using sentinel characters) and bit-oriented (using bit stuffing). Protocols discussed include BISYNC, DDCMP, and HDLC.
2) Features of PPP framing including negotiated field sizes and use of LCP control messages.
3) Functions of data link layer including framing, flow control, error control, and media access control. The relationship between the logical link control and media access control sublayers is also covered.
The document provides an overview of the TCP/IP network model. It discusses the four layers of the TCP/IP model: application layer, transport layer, internet layer, and network access layer. The application layer contains protocols like HTTP and FTP that allow applications to access networked services. The transport layer uses TCP and UDP to deliver data and provide reliability. The internet layer handles routing and uses IP. The network access layer deals with physical network components like cables and network interface cards.
This document provides an overview of the Controller Area Network (CAN) protocol. It was initially created by Bosch in the 1980s for automotive applications to enable robust serial communication and make vehicles more reliable, safe and fuel-efficient. CAN has since gained widespread use in industrial automation and other fields. The document explains that CAN uses a message-based communication protocol and carrier sense multiple access with collision detection. It also describes CAN message frames, arbitration, and other key aspects of the CAN protocol.
The document discusses the OSI model and networking fundamentals. It defines the seven layers of the OSI model from the physical layer to the application layer. It also compares the OSI model to the TCP model. The physical layer defines cables and physical components. The data link layer provides error-free transmission using frames and MAC addresses. The network layer uses IP addresses for routing. The transport layer segments messages and ensures reliable delivery. The session, presentation and application layers establish communication sessions and enable user applications.
Signaling System #7 (SS7) is a set of telephony signaling protocols that is used to set up most of the world's public switched telephone network (PSTN) connections. It uses a separate channel for call signaling and allows for faster call setup times than older methods. The key components of an SS7 network include service switching points, signaling transfer points, and service control points. SS7 enables services like caller ID, local number portability, and the routing of calls between networks.
The document provides an overview of automotive embedded systems and network technologies. It discusses electronic control units (ECUs) and their functions. Two main automotive bus protocols are described: Local Interconnect Network (LIN) and Controller Area Network (CAN). LIN uses a single wire connection and supports speeds up to 20kbps, while CAN uses a two-wire connection and supports speeds up to 1Mbps. The document outlines the frame structures, message types, and error handling approaches for both LIN and CAN networks.
GSM is a 2G mobile communication system that provides voice and data services using radio frequency bands between 800-2000MHz. It has a three-part architecture including the radio subsystem with mobile stations, base stations and controllers; the network and switching subsystem with mobile switching centers and registers; and the operation subsystem for network management. Key protocols used in GSM include LAPDm for signaling, mobility management for registration and location updating, and call management for call establishment and control. GSM provides location tracking as users roam between different visitor location registers.
Signaling System #7 (SS7) is a telecommunications protocol that defines high-speed circuit switching for telephone calls and uses out-of-band signaling between service switching points, signal transfer points, and service control points. It has advantages like separation of control information onto logically separate paths, message-oriented call information exchange, and ability of a single signaling channel to carry information about multiple trunks. The SS7 architecture includes service switching points, service control points, and signal transfer points that communicate using protocols like ISUP, TCAP, and SCCP.
The GSM network architecture consists of three major subsystems: the network and switching subsystem (NSS), the base station subsystem (BSS), and the operation and support subsystem (OSS). The BSS is composed of the base transceiver station (BTS), base station controller (BSC), and transcoder (TCU/TRAU). The BTS handles radio transmission/reception, the BSC manages radio resources and handles radio call processing, and the TCU converts between GSM and PSTN/ISDN formats. The NSS contains the mobile switching center (MSC), home location register (HLR), visitor location register (VLR), and equipment identity register (EIR), which manage subscriber
This document discusses the data link layer and media access control. It covers topics such as:
- The functions of the data link layer including framing, addressing, error control, and media access control.
- Common data link layer protocols like HDLC, PPP, Ethernet, and IEEE 802.11.
- Link layer addressing using MAC addresses and protocols like ARP.
- Media access control for networks including wired technologies like Ethernet and wireless technologies like IEEE 802.11.
This document discusses various topics related to computer networking including routing, addressing schemes, congestion control, remote procedure calls, simple mail transfer protocol, static routing algorithms, IPv4 addressing, and session layer design issues. It provides definitions and explanations of static and dynamic routing, differentiates between IPv4 and IPv6 addressing, describes congestion and congestion control, discusses the importance and workings of remote procedure calls, provides a detailed explanation of SMTP, explains two static routing algorithms (Dijkstra's algorithm and flooding algorithm), discusses IPv4 addressing schemes, describes congestion avoidance in the transport layer, and discusses design issues of the session layer such as dialog control.
The document discusses two data link layer protocols: PPP and HDLC.
PPP is commonly used for point-to-point access like home internet access. It encapsulates layer 3 protocols for transmission and provides services like authentication, encryption, and compression. However, it does not support flow control or advanced error control.
HDLC is a standard for transmitting data between network points. It organizes data into frames for transmission and verification. HDLC supports two transfer modes and uses frame structures with fields for flags, addresses, control information, payload, and error checking.
SS7 is a global standard for telecommunications that defines procedures and protocols for exchanging information between network elements to setup, route, and control calls. It uses a dedicated digital signaling network and 56/64 kbps signaling links. There are three main types of signaling points: SSPs that originate/terminate calls, STPs that route traffic, and SCPs that determine call routing. The protocol has multiple layers including MTP for transport, SCCP for addressing, and applications like ISUP for call control and TCAP for database queries.
The document discusses computer networks and media access control. It covers topics like Ethernet, wireless LANs, Bluetooth, Wi-Fi, switching, bridging, IP, and more. The key points are:
1. It provides an overview of the topics to be discussed, including media access control, Ethernet standards, wireless technologies, and internetworking basics.
2. It summarizes the evolution of Ethernet and discusses its physical properties, frame format, addressing, and transmitter algorithm using CSMA/CD.
3. It describes wireless LAN standards like Bluetooth and Wi-Fi, addressing problems in wireless networks, and discussing concepts like spread spectrum, CSMA/CA, and network architectures.
This document provides an introduction to MPLS (Multi-Protocol Label Switching). It discusses the drawbacks of traditional IP routing, including destination-based routing lookups needed on every hop. It then describes basic MPLS concepts, including forwarding packets based on labels rather than IP addresses. The MPLS architecture uses a control plane to exchange routing information and labels, and a data plane for simple label-based forwarding. MPLS can operate in frame mode, inserting labels between layers 2 and 3. Label switch routers perform label swapping in the data plane.
The document provides an overview of the ISO OSI model and its 7 layers, describing the functions of each layer. It then discusses several topics related to computer networks, including the ISO/OSI model (layers and functions), ISDN (architecture and usage), LAN protocols (such as Ethernet), framing in the data link layer and its importance, and the IEEE 802.11 wireless networking standard.
Similar to Elementary procedures for Circuit-Switched (CS) Call Control (CC) in 3GPP (20)
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
Northern Engraving | Nameplate Manufacturing Process - 2024Northern Engraving
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/how-axelera-ai-uses-digital-compute-in-memory-to-deliver-fast-and-energy-efficient-computer-vision-a-presentation-from-axelera-ai/
Bram Verhoef, Head of Machine Learning at Axelera AI, presents the “How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-efficient Computer Vision” tutorial at the May 2024 Embedded Vision Summit.
As artificial intelligence inference transitions from cloud environments to edge locations, computer vision applications achieve heightened responsiveness, reliability and privacy. This migration, however, introduces the challenge of operating within the stringent confines of resource constraints typical at the edge, including small form factors, low energy budgets and diminished memory and computational capacities. Axelera AI addresses these challenges through an innovative approach of performing digital computations within memory itself. This technique facilitates the realization of high-performance, energy-efficient and cost-effective computer vision capabilities at the thin and thick edge, extending the frontier of what is achievable with current technologies.
In this presentation, Verhoef unveils his company’s pioneering chip technology and demonstrates its capacity to deliver exceptional frames-per-second performance across a range of standard computer vision networks typical of applications in security, surveillance and the industrial sector. This shows that advanced computer vision can be accessible and efficient, even at the very edge of our technological ecosystem.
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
3. Introduction of Related Backgrounds (1/2)
• The radio interface is layered into three protocol layers [1]:
– the physical layer (L1);
– the data link layer (L2);
– the network layer (L3).
U-plane
• Layer 2 is split into following sublayers:
C-plane
– Medium Access Control (MAC), Radio Link Control (RLC), Packet
Data Convergence Protocol (PDCP) and Broadcast/Multicast
Control (BMC).
• PDCP and BMC exist in the U-plane only.
• Layer 3 and RLC are divided into Control (C-) and User (U-) planes.
• In the C-plane, Layer 3 is partitioned into sublayers (e.g., CC, MM).
– Access Stratum (AS): from RRC (Radio Resource Control) to L1
– Non-Access Stratum (NAS): AS and from NAS to the NAS of
Mobility Management Entity (MME)
4. Introduction of Related Backgrounds (1/2)
• Radio Interface Protocol Architecture (Service Access
Points (SAPs) are marked by circles.)
• “Logical” SAPs
GC
– P2P Communication
GC
• Between RRC and RLC
Nt
DC
UuS boundary
U-plane information
C-plane signalling
L3
control
Radio
Bearers
control
control
control
control
RRC
PDCP
PDCP
L2/PDCP
BMC
• The Service provided by L2
– Radio Bearer
– Signaling Radio Bearers
DC
Duplication avoidance
• Three Types of SAPs in RLC
– Acknowledged Mode (AM)
– Unacknowledged Mode (UM)
– Transparent Mode (TM)
Nt
RLC
RLC
RLC
L2/BMC
L2/RLC
RLC
RLC
RLC
RLC
RLC
Logical
Channels
MAC
L2/MAC
Transport
Channels
PHY
L1
5. Overview on Call Control (1/4)
• Call Control (CC) Protocol [2] or Call Control Function (CCF)
– One of the protocols of the Connection Management (CM)
sublayer
• Each CC entity is independent from each other and shall communicate
with the correspondent peer entity using its own MM connection.
– The present document describes the call control protocol only
with regard to two peer entities.
• Certain sequences of actions of the two peer entities compose
"elementary procedures“.
– These elementary procedures may be grouped into the
following classes:
•
•
•
•
call establishment procedures;
call clearing procedures;
call information procedures;
miscellaneous procedures.
6. Overview on Call Control (2/4)
• Three Basic Types of Calls
– MO Call
• The terms "mobile originating" or "mobile originated" are used to
describe a call initiated by the mobile station (MS).
– MT Call
• The terms "mobile terminating" or "mobile terminated" are used to
describe a call initiated by the network (NW).
– NW Initialed MO Call [3]
• A feature allows the NW to ask the MS to establish a MO connection.
• The serving PLMN provides the MS with the necessary information
which is used by the MS to establish the connection.
• It is mandatory for CCBS ME and is used in the case of a CCBS recall.
– Completion of Calls to Busy Subscriber (CCBS) [4]: CCBS is evoked when a
called party is busy, this supplementary service (SS) enables the calling party
to be connected to a called party
7. Overview on Call Control (3/4)
• Example [5]: To make a phone call.
– From MOC to PTC; from POC to MTC
• Protocol Architecture [6]
– Eight defined architectures
– Example: A MS supporting the PS mode of operation
UMTS service
RABM: RAB Manager
REG: REGister
SM: Session Management
MN: Mobile Network
SMS: Short Message Service
GSMS: GPRS SMS
SS: Supplementary Services
PDP: Packet Data Protocol
TI: Transaction ID
MM: Mobility Management
GMM: GPRS MM
PD: Protocol Discriminator
RABn-SAP
MNCC-SAP
MNSMS-SAP
SMREG-SAP
CM
MNSS-SAP
RABM
RAB
Entity RAB
1
Entity RAB
2
Entity
n
RABMSM-SAP
SM
RAB
Control
GSMS
PDP
TI
CC
TI
GMMREG
PMMSMS
GMMSMSGMMSM- -SAP
-SAP
SAP
SAP
SS
TI
TI
MMSMSSAP
MMCC-SAP GMMSS2SAP
TI
GMMSSSAP MMSSSAP
MM-sublayer
MM
GMM
GMMRABM-SAP
• NAS
• MS side
RAB1-SAP RAB2-SAP
PDCP1-SAP
PDCP2-SAP
PDCPn-SAP
RABMAS-SAP
GMM
coord
MM
coord
PD
PD
RR-SAP
GMMAS-SAP
Access Stratum sublayer
PDCP
BMC
RRC
8. Overview on Call Control (4/4)
• The CC service class consists of the following services [6]:
– MS side
•
•
•
•
•
MO and MT call establishment for normal calls;
MO call establishment for emergency calls;
call maintaining;
call termination;
call related SS Support.
– NW side
•
•
•
•
call establishment;
call maintaining;
call termination;
call related SS support.
• Three matrices to understand CC protocol
– L3 massage structure, service state diagram, and service arrow diagram
9. Standard L3 Messages (1/9)
• A standard L3 message [6]
– (1) Imperative part
Example: General message organization
• A header
• The rest of imperative part
– (2) Non-imperative part
– (Note: Both the non-header part of the imperative part and
the non-imperative part are composed of successive parts
referred as standard Information Elements (IEs).)
• A standard IE may have the following parts, in that order:
– an Information Element Identifier (IEI);
– a Length Indicator (LI);
– a value part.
10. Standard L3 Messages (2/9)
• A standard IE has one of the formats as follows.
– LV-E and TLV-E are used for EPS Mobility Management
(EMM) and EPS Session Management (ESM) only.
• Seven types of standard IEs are defined:
– format V or TV with value part consisting of 1/2 octet;
– format T with value part consisting of 0 octets;
– format V or TV with value part that has fixed length of at least one octet;
– format LV or TLV with value part consisting of zero, one or more octets;
– format LV-E or TLV-E with value part consisting of zero, one or more octets and
a maximum of 65535 octets. This category is used in EPS only.
11. Standard L3 Messages (3/9)
• Example: Type 4 IE of format TLV
– A type 4 standard IE has format LV or TLV. Its LI precedes the
value part, which consists of zero, one, or more octets; if
present, its IEI has one octet length and precedes the LI.
Example: General message organization
• The header of a standard L3 message is composed of two
octets, and structured in three main parts. [6]
– The Protocol Discriminator (PD) (1/2 octet)
– A message type octet
– A half octet used in some cases as Transaction Identifier (TI), in some other cases as a subprotocol discriminator, and called skip indicator otherwise.
12. Standard L3 Messages (4/9)
• For the EPS protocols (EMM and ESM), a standard L3 message can be
either a plain NAS message or a security protected NAS message:
– A plain NAS message
• which is composed of two or three octets, and structured in four main parts.
– A PD (1/2 octet)
– A half octet used in some cases as security header type and in other cases as an EPS
bearer identity (1/2 octet)
– A message type octet
– One octet included in some cases and used as a Procedure Transaction Identity (PTI)
– A secure protected message
• which is composed of six octets, and structured in four main parts.
–
–
–
–
The PD (1/2 octet)
A half octet used as security header type
A message authentication code of four octets
A sequence number of one octet
• This header is followed by a complete plain NAS message (i.e. including the
header of this plain NAS message).
13. Standard L3 Messages (5/9)
• Protocol Discriminator (PD)
(Note that the following contents focus on the standard L3 message which is not for the usage of EPS.)
– Bits 1 to 4 of the first octet of a standard L3 message
– The PD identifies which the standard L3 message
belongs.
– For future evolution to an extension mechanism
• The use of protocol discriminators with one octet length,
where bits 4 to 1 are coded as 1 1 1 0.
– Messages of such protocols may be not standard L3 messages.
14. Standard L3 Messages (6/9)
• Message Type Octet
– The second octet in a standard L3 message
– When a standard L3 message is expected,
• a message is less than 16 bit long, then this message shall be
ignored.
– When accessing Rel.98 and older networks,
GCC: Group CC
BCC: Broadcast CC
• Bit 8 is encoded as "0“
LCS: Location Services
– Further, value "1" is reserved for possible future use as an extension
bit.
– If “1” is detected, a protocol entity shall diagnose a "message not
defined for the PD" error and treat the message accordingly.
• Bit 7
– For RR messages including MM, CC, SS, GCC, BCC and LCS,
» bit 7 is used for send sequence number.
– For all other standard L3 messages (i.e. the protocols other than MM, CC, SS, GCC, BCC and LCS),
» bit 7 is set to a default value.
8
0
7
N (SD)
or 0
6
5
4
3
Message type
2
1
8
octet 1
7
6
5
4
3
Message type
2
1
octet 1
15. Standard L3 Messages (7/9)
• Message Type Octet (Cont.)
– When accessing Rel.99 and newer networks 4 3
6
7
5
8
N (SD) or 0
Message type
– For MM, CC, and SS,
• bits 7 and 8 are used for send sequence number
– For GCC, BCC, and LCS,
8
0
7
6
N (SD)
or 0
• only bit 7 is used for send sequence number 6
7
8
• and bit 8 is set to the default value.
5
4
1
2
octet 1
2
3
1
octet 1
Message type
5
4
3
2
1
Message type
– For all other standard layer 3 messages,
• Non-RR messages
– bits 7 and 8 are set to the default value. (The default values are both 0.)
– Exception: For SM protocol, bit 7 is set to 1.
• RR messages [7]
– bit 8 is set to the default value. (No default value for bit 7)
• EPS
EMM: EPS Mobility Management
ESM: EPS Session Management
– bit 7 is set to 1 while bit 8 is 0 for the EMM and 1 for the ESM.
octet 1
16. Standard L3 Messages (8/9)
• Transaction identifier (TI in PS NAS Msg.; TIO in CS NAS Msg.)
– Bits 5 to 8 of octet 1 of a standard L3 message
– The TI allows to distinguish up to 16 bi-directional messages
flows for a given PD and a given SAP.
• Such a message flow is called a transaction.
– An extension mechanism is also defined.
• which allows to distinguish up to 256 bi-directional messages flows for
a given PD and a given SAP.
• which shall not be used unless explicitly stated in the core spec.
– TI flag
• 0: The message is sent from the side that originates the TI.
• 1: The message is sent to the side that originates the TI.
– TIO (Bits 7 to 5 in octet 1)
– TIE (Bit 7 to 1 in octet 2)
17. Standard L3 Messages (9/9)
• Sub-Protocol Discriminator (SPD)
CTS: Cordless Telephony System
– Bits 5 to 8 of octet 1 of a standard L3 message
– which allows to identify between protocols inside one sublayer.
• Skip indicator
–
–
–
–
Bits 5 to 8 of octet 1 of a standard L3 message
The content of skip indicator depends on the protocol and the SAP.
The use of this half-octet is consistent for a given PD and SAP.
Unless been specified in the protocol, the skip indicator IE is a spare
field.
18. Service State Diagram [6] (1/2)
• Service graph of Call Control entity - MS side
• Three partitions: MO call, call clearing, MT call
19. Service State Diagram (2/2)
• Service graph of Call Control entity - NW side
• Three partitions: MO call, call clearing, MT call
20. Primitive: inter-layer info. in one node
Message: inter-node info.
Service Arrow Diagram (1/3)-MO call setup (Successful case)
Setup Request from MS
Mobile Station
CC
MNCC-SETUP-REQ
MM
MMCC-EST-REQ
RR
RR-EST-REQ
(CM SERV REQ)
L2
L2
RR
MM
Network
CC
DL-RANDOM-ACC-REQ/IND (CHANN REQ)
DL-UNIT-DATA-IND/REQ(IMM ASS)
DL-ASS-REQ
RR-EST-CNF
SABM (CM SERV REQ)
DL-EST-CNF
DL-EST-IND
UA (CM SERV REQ)
RR-EST-IND
(CM SERV REQ)
AUTH REQ
Authentication &
Ciphering
AUTH RES
CIPH MODE CMD
MMCC-EST-CNF
RR-SYNC-IND
(ciph)
CIPH MODE COM
RR-SYNC-REQ
(ciph)
RR-SYNC-CNF
(ciph)
MMCC-EST-IND
(SETUP)
SETUP
MNCC-CALLPROC-IND
CALL PROC
MNCC-CALLPROC-REQ
ASSIGN CMD
MMCC-SYNC-IND
(res ass)
MNCC-ALERT-IND
MNCC-SETUP-CNF
RR-SYNK-IND
(res ass)
RR-SYNC-REQ
(res ass)
ASSIGN COM
RR-SYNC-CNF
(res ass)
ALERT
CONNECT
CONN ACK
MNCC-SETUP-IND
MMCC-SYNC-REQ
(res ass)
MMCC-SYNC-CNF
(res ass)
MNCC-ALERT-REQ
MNCC-SETUP-RSP
MNCC-SETUPCOMPL-IND
MO Call Setup
DATA FLOW
21. Service Arrow Diagram (2/3)-MT call setup (Successful case)
Mobile Station
CC
Network
Setup Request from NW
MM
RR
RR
L2
L2
DL-UNIT-DATA-IND/REQ (PAG REQ)
MM
CC
MMCC-SETUP-REQ
RR-EST-REQ
(mob id)
MMCC-EST-REQ
(mob id)
DL-RANDOM-ACC-REQ/IND (CHANN REQ)
DL-UNIT-DATA-IND/REQ (IMM ASS)
DL-EST-REQ
RR-EST-IND
DL-EST-CONF
SABM (PAG RES)
DL-EST-IND
RR-EST-CNF
UA (PAG RES)
AUTH REQ
Authentication &
Ciphering
AUTH RES
CIPH MODE CMD
RR-SYNC-IND
(ciph)
MNCC-SETUPIND
RR-SYNC-REQ
(res ass)
CIPH MODE COM
RR-SYNC-CNF
(res ass)
MMCC-EST-CNF
SETUP
MMCC-EST-IND
(SETUP)
CALL CONF
MNCC-CALLCONF-REQ
ASSIGN CMD
MMCC-SYNC-IND
(res ass)
RR-SYNC-IND
(res ass)
ASSIGN COM
MNCC-ALERTREQ
ALERT
MNCC-SETUPRES
CONNECT
MNCC-SETUPCOMPL-IND
CONN ACK
MT Call Setup
DATA FLOW
MNCC-CALLCONF-IND
RR-SYNC-REQ
(res ass)
RR-SYNC-CNF
(res ass)
MMCC-SYNC-REQ
(res ass)
MMCC-SYNC-CNF
(res ass)
MNCC-ALERT-IND
MNCC-SETUP-CNF
MNCC-SETUPCOMPL-REQ
22. Service Arrow Diagram (3/3)-MO, call and channel release (Successful case)
Mobile Station
CC
Network
MM
L2
L2
RR
RR
MM
CC
DATA FLOW
Disconnect
DISCONNECT
MNCC-DISC-REQ
MNCC-DISC-IND
MNCC-REL-IND
RELEASE
MNCC-REL-REQ
RELEASE COM
Release
MNCC-REL-CNF
MMCC-REL-REQ
CHANN REL
RR-REL-IND
DL-REL-REQ
DL-REL-CNF
Channel Release
DISC
UA
RR-REL-REQ
DL-REL-IND
MMCC-REL-REQ
23. System Log (1/5)
• Environment - QXDM Prof.
>> Item type: Long packets (OTA)
>> Filter/Register on target for items: CC, MM, GSM RRM
– (Ex.1) The MO call is successful and disconnects by
calling user.
– (Ex.2) The MT call is successful and disconnects by the
calling user.
24. Presence
M: Mandatory
C: Conditional
O: Optional
System Log (2/5)
• Messages for CS CC [2] in Ex.1
– SETUP message content (MS to NW)
• Transaction ID (trans_id_or_skip_ind = 0x0)
–
TI values are assigned by the side of the interface initiating a transaction
.
• Protocol discriminator (prot_disc = 0x3)
– Call control; call related SS messages
• Message type (msg_type = 0x5)
– Call establishment message – SETUP
• Bearer capability 1 (bearer_cap_1_incl = 0x1)
• Called party BCD number (called_party_bcd_incl = 0x1)
25. System Log (3/5)
• Messages for CS CC in Ex.1 (Cont.)
– CC/Call Proceeding (NW to MS)
– CC/Facility (NW to MS)
26. System Log (4/5)
• Messages for CS CC in Ex.1 (Cont.)
– CC/Alerting (NW to MS)
– CC/Connect (NW to MS)
– CC/Connect Acknowledge (MS to NW)
27. System Log (5/5)
• Messages for CS CC in Ex.1 (Cont.)
– CC/Disconnect (MS to NW)
– CC/Release (NW to MS)
– CC/Release Complete (MS to NW)
28. References
• [1] 3GPP TS 25.301 V11.0.0 (2012-09) - 3GPP TSG RAN; Radio Interface
Protocol Architecture (Rel.11)
• [2] 3GPP TS 24.008 V12.3.0 (2013-09) - 3GPP TSG CT; Mobile Radio
Interface Layer 3 Spec.; CN protocols; Stage 3 (Re.12)
• [3] ETSI TS 100 906 v7.0.1 (1999-07) - Digital Cellular Telecom. System
(Phase2+); MS Features (GSM 02.07) ver. 7.0.1 (Rel. 98)
• [4] Asterisk 1.4/Call Completion on Busy Subscriber (CCBS)
• [5] WCDMA/UMTS第三代無線通訊系統(1)--核心網路架構介紹
• [6] 3GPP TS 24.007 V12.0.0 (2013-06) - 3GPP TSG CT; Mobile Radio
Interface Signalling Layer 3; General Aspects (Rel.12)
• [7] 3GPP TS 44.018 V12.0.0 (2013-09) – 3GPP TSG GERAN; Mobile
Radio Interface Layer 3 Spec.; RRC protocol (Rel.12)