hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9.3 Behaviour in State 'REGISTERED-CONDITIONAL' | 5.4.1.9.3.0 General This state has three sub-states: 'AWAIT_POS_REQ', 'AWAIT-GPS-POSITION' and 'AWAIT-REG-MODE-UPDATE', and 'AWAIT-HANDOVER-LEASE'. 5.4.1.9.3.1 Behaviour in Substate 'AWAIT-POS-REQ' On receipt of the SSR_SIGDATA_IND primitive from SSR, REGM shall unpack the encapsulated REGM PDU from the peer agent and ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9.4 Behaviour in State 'REGISTERED' | On receipt of the REGM_CONN_REQ primitive from GMMH/MMH, REGM shall respond with the REGM_CONN_CNF primitive. REGM shall also send the REGM_CONN_IND primitive to RBC. On receipt of the REGM_REL_REQ primitive from GMMH/MMH, REGM shall start timer TU10. REGM shall compose the REGM:SignallingConnectionReleaseReq PDU and s... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9.5 Behaviour in State 'RELEASING' | 5.4.1.9.5.0 General The RELEASING state has seven substates. 5.4.1.9.5.1 Behaviour in Substate 'AWAIT-RELEASE' On receipt of the SSR_SIGDATA_IND primitive from SSR, REGM shall unpack the encapsulated REGM PDU from the peer agent and examine the AL Signal Type IE: • 1> if the PDU type is REGM:Deregister, then REGM shall... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9.6 Behaviour in State 'AWAIT-HANDOVER-RESPONSE' | On receipt of the CBCn_HANDOVER_CNF primitive from the Bearer Control layer, REGM shall compose the REGM:HandoverAck PDU and send it to the SSR for transmission to the peer REGM agent in the RNC using the SSR_SIGDATA_REQ primitive. The REGM state shall change to 'REGISTERED'. If timer TU7 expires, then REGM shall save ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9.7 Behaviour in Any State (Not State 'IDLE') | On receipt of the AL_COMDATA_IND primitive from the COM-SAP, REGM shall examine the PDU type IE. If the PDU type is REGM:DeregisterCommon, then REGM shall send the REGM_REL_IND primitive to GMMH/MMH/RBC. REGM shall send the SSR_DISCONNECT_REQ primitive to SSR. The REGM state shall change to 'RELEASING-AWAIT-DISCONNECT'... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9.8 Behaviour in Any State (Not State 'IDLE' or State 'REGISTERED') | On receipt of the REGM_CONN_REQ primitive from GMMH/MMH, REGM shall follow the procedure described in clause 5.4.1.9.9. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.9.9 Common Procedures | REGM shall maintain a SERVICE DOMAIN state variable which implicitly tracks the state of GMMH and MMH. The variable allows REGM to determine which AL agents need to receive notification of change in state of the UE-Specific Signalling connection via the REGM_CONN_CNF, REGM_CONN_IND, REGM_CONN_REJ, REGM_REL_CNF, and REG... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.10 REGM Timers and Counters | Default values in Table 5.10 apply to all UE Classes unless otherwise indicated. Figure 6.4 contains a summary of REGM timers in the RNC and UE. REGM Counters are defined in Table 5.11. Table 5.10: REGM Timers [UE] Timer Default Value [Min, Max] Value State Comments TU1 30 s [0, 600 s] 'IDLE-AWAIT-PSAB- DISCOVERY' Supe... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.1.11 Satellite Table | REGM shall maintain a table of satellite identifying frequencies in non-volatile programmable memory. Each row of the table contains data for one satellite and includes the satellite id, satellite longitude, primary identifying L-band frequency, and alternate identifying L-band frequency. Each row may optionally contai... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2 GMMH | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.1 GMMH Protocol Data Units | The GMMH Protocol Data Units are shown in Table 5.13. Table 5.13: GMMH::GMMH Protocol Data Units PDU SAP Direction Addressing Information Elements PagingType2 SIG To UE BCnID AL Signal Type, ALPD, CN Domain Identity, Paging Cause, Paging Record Type ID InitialDirectTransfer SIG From UE BCnID AL Signal Type, ALPD, CN Do... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.2 Service Primitives at GMMH-SIG-SAP | The service primitives at GMMH-SIG-SAP are shown in Table 5.14. Table 5.14: GMMH::SSR Service Primitives at GMMH-SIG-SAP [UE] Primitive Direction Parameters SSR_SIGDATA_REQ GMMH requests SSR to send a PDU to its peer in the RNC. To SSR GMMH PDU, {SUSP} OPTIONAL SSR_SIGDATA_IND SSR indicates to GMMH that it has received... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.3 Service Primitives at GMMAL-SAP | The GMMAL-SAP and associated service primitives are functionally identical to the GMMAS-SAP and associated service primitives defined in ETSI TS 124 007 [1]; only the names have changed for clarity. The service primitives at GMMAL-SAP are shown in Table 5.15. ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 43 Table 5.15: GMM... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.4 Service Primitives at GMMH-REGM-SAP | See clause 5.4.1.4. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.5 Service Primitives at GMMH-CBCn-SAP | The service primitives at GMMH-CBCn-SAP are shown in Table 5.16. ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 44 Table 5.16: GMMH::CSR Service Primitives at GMMH-CBCn-SAP [UE] Primitive Direction Parameters CBCn_SECURITY_REQ GMMH requests BCn to start, or modify ciphering for all PDUs received at the indicated SAPs (BCnID... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.6 Service Primitives RBCPS-GMMH-SAP | See clause 5.4.4.8. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.7 GMMH States | The GMMH states are shown in Table 5.17. Table 5.17: GMMH States [UE] Number State Description 1 IDLE Initial State A UE-Specific signalling connection has not been established and GMMH is unable to route messages between GMM and the BCn layer. 2 AWAIT-SIG-CONN-EST GMMH has requested REGM to establish a UE-Specific si... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.8 GMMH Behaviour | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.8.0 General | 5.4.2. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 8.0 General | GMMH behaviour in the UE is summarized in the signal-state diagrams in Figure 5.11 and Figure 5.12. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.8.1 Behaviour in State 'IDLE' | On receipt of the GMMAL_EST_REQ primitive from GMM, GMMH shall save the encapsulated Layer 3-PDU (NAS Message). GMMH shall then request REGM to establish the UE-Specific Signalling connection by sending the REGM_CONN_REQ primitive. The GMMH state shall change to 'AWAIT-SIG-CONN-EST'. On receipt of the REGM_PAGE_IND pri... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.8.2 Behaviour in State 'AWAIT-SIG-CON-ESTABLISH' | On receipt of the REGM_CONN_REJ primitive from REGM, GMMH shall notify GMM of the failure to establish the UE-Specific Signalling connection by sending the GMMAL_EST_REJ primitive. The GMMH state shall change to 'IDLE'. On receipt of the REGM_CONN_CNF primitive from REGM, GMMH shall save the value of the 'UE Security C... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.8.3 Behaviour in State 'CONNECTED' | 5.4.2.8.3.1 Behaviour in Substate 'CONNECTED' On receipt of the GMMAL_DATA_REQ primitive from GMM, GMMH shall use the encapsulated Layer 3-PDU (NAS Message) to compose the GMMH:UplinkDirectTransfer PDU and send it to the SSR for transmission to the peer GMMH agent in the RNC using the SSR_SIGDATA_REQ primitive. On rece... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.8.4 Behaviour in State 'CONNECTED-IU-REL' | On receipt of the GMMAL_EST_REQ primitive from GMM, GMMH shall use the encapsulated Layer 3-PDU (NAS Message) to compose the GMMH:InitialDirectTransfer PDU and send it to the SSR for transmission to the peer GMMH agent in the RNC using the SSR_SIGDATA_REQ primitive. GMMH shall notify GMM of the establishment of the UE-... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.2.8.5 Behaviour in State 'AWAIT-SIG-CON-RELEASE' | On receipt of the REGM_REL_CNF primitive from REGM, GMMH shall inform GMM of the release of the PS signalling connection by sending the GMMAL_REL_IND primitive. The GMMH state shall change to 'IDLE'. On receipt of the REGM_SIGNAL_CONN_REL_IND primitive from REGM, GMMH shall inform GMM of the release of the PS signallin... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3 MMH | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.1 MMH Protocol Data Units | The MMH Protocol Data Units are shown in Table 5.18. Table 5.18: MMH::MMH Protocol Data Units PDU SAP Direction Addressing Information Elements PagingType2 SIG To UE BCnID AL Signal Type, ALPD, CN Domain, Paging Cause, Paging Record Type ID InitialDirectTransfer SIG From UE BCnID AL Signal Type, ALPD, CN Domain Identit... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.2 Service Primitives at MMH-SIG-SAP | The service primitives at MMH-SIG-SAP are shown in Table 5.19. Table 5.19: MMH::SSR Service Primitives at MMH-SIG-SAP [UE] Primitive Direction Parameters SSR_SIGDATA_REQ MMH requests SSR to send a PDU to its peer in the RNC. To SSR MMH PDU, {SUSP} OPTIONAL SSR_SIGDATA_IND SSR indicates to MMH that it has received a PDU... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.3 Service Primitives at MMAL-SAP | The service primitives at MMAL-SAP are shown in Table 5.20. The MMAL-SAP and associated service primitives are functionally identical to the RR-SAP and associated service primitives defined in ETSI TS 124 007 [1]. Some modifications have been made to the service primitives to suit the Adaptation Layer model or provide ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.4 Service Primitives at MMH-REGM-SAP | See clause 5.4.1.4. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.5 Service Primitives at MMH-CBCn-SAP | The service primitives at MMH-CBCn-SAP are as shown in Table 5.23. Table 5.23: MMH::CSR Service Primitives at MMH-CBCn-SAP [UE] Primitive Direction Parameters CBCn_SECURITY_REQ MMH requests BCn to start, or modify ciphering for all PDUs received at the indicated SAPs (BCnID). To CSR ALPD, Mode (Start/ Modify), CK, STAR... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.6 Service Primitives RBCCS-MMH-SAP | See clause 5.4.4.8. ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 53 |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.7 MMH States | The MMH states are as shown in Table 5.24. Table 5.24: MMH States [UE] Number State Description 1 IDLE Initial State A UE-Specific signalling connection has not been established and MMH is unable to route messages between MM and the BCn layer. 2 AWAIT-SIG-CONN-EST MMH has requested REGM to establish a UE-Specific sign... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.8 MMH Behaviour | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.8.0 General | MMH behaviour in the UE is summarized in the signal-state diagrams in Figures 5.13 and 5.14. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.8.1 Behaviour in State 'IDLE' | On receipt of the MMAL_EST_REQ primitive from MM, MMH shall save the encapsulated Layer 3-PDU (NAS Message). MMH shall then request REGM to establish the UE-Specific Signalling connection by sending the REGM_CONN_REQ primitive. The MMH state shall change to 'AWAIT-SIG-CONN-EST'. On receipt of the REGM_PAGE_IND primitiv... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.8.2 Behaviour in State 'AWAIT-SIG-CON-ESTABLISH' | On receipt of the REGM_CONN_REJ primitive from REGM, MMH shall notify MM of the failure to establish the UE-Specific Signalling connection by sending the MMAL_EST_REJ primitive. The MMH state shall change to 'IDLE'. On receipt of the REGM_CONN_CNF primitive from REGM, MMH shall save the value of the 'UE Security Capabi... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.8.3 Behaviour in State 'CONNECTED' | 5.4.3.8.3.1 Behaviour in Substate 'CONNECTED' On receipt of the MMAL_DATA_REQ primitive from MM, MMH shall use the encapsulated Layer 3-PDU (NAS Message) to compose the MMH:UplinkDirectTransfer PDU and send it to the SSR for transmission to the peer MMH agent in the RNC using the SSR_SIGDATA_REQ primitive. On receipt o... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.8.4 Behaviour in State 'CONNECTED-IU-RELEASED' | On receipt of the MMAL_EST_REQ primitive from MM, MMH shall use the encapsulated Layer 3-PDU (NAS Message) to compose the MMH:InitialDirectTransfer PDU and send it to the SSR for transmission to the peer MMH agent in the RNC using the SSR_SIGDATA_REQ primitive. MMH shall notify MM of the establishment of the UE-Specifi... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.8.5 Behaviour in State 'AWAIT-SIG-CON-RELEASE' | On receipt of the REGM_REL_CNF primitive from REGM, MMH shall inform MM of the release of the CS signalling connection by sending the MMAL_REL_IND primitive. The MMH state shall change to 'IDLE'. On receipt of the REGM_SIGNAL_CONN_REL_IND primitive from REGM, MMH shall inform MM of the release of the CS signalling conn... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.3.8.6 Behaviour in State 'ABORT-REQUESTED' | On receipt of the REGM_CONN_CNF primitive from MM, MMH shall request REGM to release the UE-Specific Signalling connection by sending the REGM_REL_REQ primitive. The MMH state shall change to 'AWAIT-SIG-CONN-REL'. On receipt of the REGM_CONN_REJ primitive from REGM, MMH shall send the MMAL_REL_IND primitive to MM. The ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4 Radio Bearer Control (RBC) | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.1 RBC Protocol Data Units | The RBC Protocol Data Units are as shown in Table 5.25. Table 5.25: RBC::RBC Protocol Data Units PDU SAP Direction Addressing Information Elements Establish SIG To UE BCnID AL Signal Type, ALPD, BCnID (DATA-SAP), BCn Type, Number of (BCn) Parameters, BCn Parameter List, Control Flags, Transaction ID, BCt Type, BCtID, B... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.3 Service Primitives at RBC-SIG-SAP (RBCPS-SIG-SAP, RBCCS-SIG-SAP) | The service primitives at RBC-SIG-SAP are as shown in Table 5.26. ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 59 Table 5.26: RBC::SSR Service Primitives at RBC-SIG-SAP [UE] Primitive Direction Parameters SSR_SIGDATA_REQ RBC requests SSR to send a PDU to its peer in the RNC To SSR RBC PDU SSR_SIGDATA_IND SSR indicates to ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.4 Service Primitives at RABMAL-SAP (RBC PS Domain Only) | The service primitives at RABMAL-SAP are as shown in Table 5.27. The RABMAL-SAP and associated service primitives are functionally identical to the RABMAS-SAP and associated service primitives defined in ETSI TS 124 007 [1]; only the names have changed for clarity. Table 5.27: RABM::RBC-PS Service Primitives at RABMAL-... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.5 Service Primitives at MMRBC-SAP (RBC CS Domain Only) | The service primitives at MMRBC-SAP are as shown in Table 5.28. Table 5.28: RBC-CS::MMH Service Primitives at MMRBC-SAP [UE] Primitive Direction Parameters RBC_SYNC_REQ RBC requests MMH to send the MMAL_SYNC_IND message (resource assignment or channel mode modification) to the MM agent, indicating the assigned RAB ID a... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.7 Service Primitives at CPDCP-SAP (RBC PS Domain Only) | The service primitives at CPDCP-SAP are as shown in Table 5.30. Table 5.30: RBC::PDCP Service Primitives at CPDCP-SAP [UE] Primitive Direction Parameters CPDCP_CONFIG_REQ To PDCP PDCP Info, BCnID (DATA-SAP), SN Sync, R/I CPDCP_RELEASE_REQ To PDCP BCnID (DATA-SAP) ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 61 5.4.4.8 Ser... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.9 Service Primitives at CSH-RBC-SAP (RBC CS Domain Only) | The service primitives at CSH-RBC-SAP are as shown in Table 5.32. Table 5.32: RBC::CSH Service Primitives at CSH-RBC-SAP [UE] Primitive Direction Parameters CSH_CONFIG_REQ To CSH BCnID (DATA-SAP), Forward CS Frames Per PDU, Return CS Frames Per PDU, Return DTX CSH_CONFIG_CNF To RBC-CS BCnID (DATA-SAP), Circuit Switched... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.10 RBC States | The RBC states are as shown in Table 5.33. Table 5.33: RBC States Number State Description 1 IDLE Initial State A UE-Specific signalling connection has not been established. No RBC procedure is in progress. 2 CONNECTED A UE-Specific signalling connection has been established. No RBC procedure is in progress. >2a CONNE... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11 RBC Behaviour | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.0 General | RBC behaviour in the UE is summarized in the signal-state diagrams in Figures 5.15 and 5.16. RBC maintains a "RAB Table" which relates DATA-SAP handles (BCnID) to their corresponding RAB IDs. ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 63 Figure 5.15: UE RBC Signal-State Diagram - Establish and Release Functions ETSI ETS... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.1 Behaviour in State 'IDLE' | On receipt of the REGM_CONN_IND primitive from REGM, the RBC state shall change to 'CONNECTED'. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.2 Behaviour in State 'CONNECTED' | On receipt of the SSR_SIGDATA_IND primitive from SSR, RBC shall unpack the encapsulated RBC PDU from the peer agent in the UE and examine the AL Signal Type IE: • 1> If the PDU type is RBC:Establish, then RBC shall create a new entry in the RAB Table with the indicated values of BCnID (DATA-SAP) and RAB ID. The RNC sha... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.3 Behaviour in State 'CONNECTED-AWAIT-CREATE' | On receipt of the CBCn_CREATE_CNF primitive from CBCn (via CSR), • 1> PS Domain only: RBC shall compose the RABMAL_RAB_EST_IND primitive and send it to RABM. The RBC state shall change to 'CONNECTED-AWAIT-RAB-EST'. • 1> CS Domain only: - 2> if ciphering is enabled, then RBC shall compose the RBC_CK_INFO_REQ primitive a... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.4 Behaviour in State 'CONNECTED-AWAIT-RAB-REL' | 5.4.4.11.4.0 General This state has two numbered substates. 5.4.4.11.4.1 Behaviour in State 'CONNECTED-AWAIT-RAB-REL-1' On receipt of the RABMAL_RAB_REL_RES primitive from RABM, the RBC state shall change to 'CONNECTED'. ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 66 5.4.4.11.4.2 Behaviour in State 'CONNECTED-AWAIT-RAB-R... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.5 Behaviour in State 'CONNECTED-AWAIT-DESTROY' | 5.4.4.11.5.0 General This state has five numbered substates. 5.4.4.11.5.1 Behaviour in State 'CONNECTED-AWAIT-DESTROY-1' On receipt of the CBCn_DESTROY_CNF primitive from CBCn via CSR, the RBC shall remove the corresponding entry from the RAB Table. RBC shall compose the RBC:EstablishReject PDU and send it to the SSR f... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.6 Behaviour in State ' CONNECTED-AWAIT-RAB-EST' | On receipt of the RABMAL_RAB_EST_RES primitive from RABM: • 1> if ciphering is enabled then RBC shall compose the RBC_CK_INFO_REQ primitive and send it to GMMH. The RBC state shall change to 'CONNECTED-AWAIT-KEYS'. • 1> if ciphering is not enabled then RBC shall compose the RBC:EstablishAck PDU and send it to the SSR f... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.7 Behaviour in State 'CONNECTED-AWAIT-KEYS' | On receipt of the RBC_CK_INFO_RSP from GMMH or MMH, RBC shall compose the CBCn_SECURITY_REQ primitive and send it to CBCn (via CSR). The RBC state shall change to 'CONNECTED-AWAIT-SECURITY'. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.8 Behaviour in State 'CONNECTED-AWAIT-SECURITY' | On receipt of the CBCn_SECURITY_CNF primitive from CBCn (via CSR): • 1> PS Domain only: RBC shall compose the RBC:EstablishAck PDU and send it to the SSR for transmission to the peer RBC agent in the RNC using the SSR_SIGDATA_REQ primitive. RBC shall also compose the CPDCP_CONFIG_REQ primitive and send it to PDCP. The ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.9 Behaviour in State 'CONNECTED-AWAIT-CSH' | On receipt of the CSH_CONFIG_CNF primitive from CSH, REGM shall compose the RBC:EstablishAck PDU and send it to the SSR for transmission to the peer RBC agent in the RNC using the SSR_SIGDATA_REQ primitive. RBC shall also compose the RBC_SYNC_REQ primitive and send it to MMH. The RBC state shall change to 'CONNECTED'. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.10 Behaviour in State 'CONNECTED-AWAIT-MODIFY' | On receipt of the CBCn_MODIFY_CNF primitive from CBCn (via CSR), RBC shall compose the RBC:ModifyAck PDU and send it to the SSR for transmission to the peer RBC agent in the RNC using the SSR_SIGDATA_REQ primitive. The RBC state shall change to 'CONNECTED'. On receipt of the CBCn_MODIFY_REJ primitive from CBCn (via CSR... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.11 Behaviour in Any State (Not 'IDLE') | On receipt of the CBCn_FAILURE_IND primitive from CBCn (via CSR), RBC shall examine the 'Failure Cause' parameter of the primitive: • 1> If the 'Failure Cause' parameter indicates a radio resource layer failure ("Conn Failure" or "Max Unack Reached"): - 2> PS domain only: RBC shall compose the RABMAL_STATUS_IND primiti... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.4.11.12 Common Procedures | RBC PDUs contain a 4-bit 'Transaction ID' IE which allows RBC (in the RNC) to associate a response or acknowledgement with a request and allows multiple requests to be in transit at any one time. RBC shall repeat the value the of the 'Transaction ID' IE received in any request (e.g. RBC:Establish) in the corresponding ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5 SSR | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.1 Service Primitives at REGM-SIG-SAP | See clause 5.4.1.3. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.2 Service Primitives at GMMH-SIG-SAP | See clause 5.4.2.2. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.3 Service Primitives at MMH-SIG-SAP | See clause 5.4.3.2. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.4 Service Primitives at RBC-SIG-SAP | See clause 5.4.4.3. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.5 Service Primitives at SIG-SAP | The service primitives at SIG-SAP are shown in Table 5.34. See ETSI TS 102 744-3-5 [11], clause 6.2 for the definition of the parameter 'AL PDU'. The Message Unit Identifier (MUI) is used to indicate which AL PDU is confirmed by the BCn_AM_DATA_CNF primitive. Table 5.34: SSR::BCn Service Primitives at SIG-SAP [UE] Prim... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.6 SSR States | The SSR states are as shown in Table 5.35. Table 5.35: SSR States [UE] Number State Description 1 IDLE Initial State The SSR is unable to route messages between the SIG-SAP and AL agents because the SIG-SAP has not been created (i.e. the UE has not completed the Registration procedure with the RNC). 2 CONNECTED The SS... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.7 SSR Behaviour | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.7.0 General | SSR behaviour in the UE is summarized in the signal-state diagram in Figure 5.17. ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 70 Figure 5.17: SSR Signal-State Diagram ETSI ETSI TS 102 744-3-6 V1.1.1 (2015-10) 71 |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.7.1 Behaviour in State 'IDLE' | On receipt of the SSR_CONNECT_REQ primitive from REGM, the SSR shall initiate a connection to the specified SIG-SAP (BCnID) and send the SSR_CONNECT_CNF primitive to REGM. The SSR state shall then change to 'CONNECTED'. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.7.2 Behaviour in State 'CONNECTED' | On entry to state 'CONNECTED', the SSR shall initialize the Message Unit Identifier (MUI) counter to "0". On receipt of the SSR_SIGDATA_REQ primitive from any AL agent, the SSR shall increment the MUI by one and compose the AL PDU as shown in Figure 5.18 with the 'Integrity Check Included' IE set to "0". The SSR shall ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.5.7.3 Behaviour in State 'CONNECTED-INTEGRITY' | On receipt of the SSR_SIGDATA_REQ primitive from any AL agent, the SSR shall increment the MUI by one and compose the AL PDU as shown in F with the 'Integrity Check Included' IE set to "1". The SSR shall perform integrity protection as described in clause 7.1 and append the Message Authentication Code for Integrity (MA... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.6 CSR | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.6.1 Service Primitives at REGM-CBCn-SAP | See clause 5.4.1.6. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.6.2 Service Primitives at GMMH-CBCn-SAP | See clause 5.4.2.5. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.6.3 Service Primitives at MMH-CBCn-SAP | See clause 5.4.3.5. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.6.4 Service Primitives at RBC-CBCn-SAP | See clause 5.4.4.6. SSR_SIGDATA_REQ( ) BCn_AM_DATA_REQ( ) AL Signal Type ALPD PDU Body REGM PDU GMMH PDU MMH PDU RBC PDU AL Signal Type PDU Body ALPD ic (1) AL Message Sequence No. AL PDU SSR_SIGDATA_IND( ) BCn_AM_DATA_IND( ) AL Signal Type PDU Body ALPD ic (1) AL Message Sequence No. MAC-I (Integrity Protection) ETSI ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.6.5 Service Primitives at CBCn-SAP | The service primitives at CBCn-SAP are shown in Table 5.36. Table 5.36: CSR::BCn Service Primitives at CBCn-SAP [UE] Primitive Direction Parameters CBCn_CREATE_REQ AL agent (via CSR) requests the BCn layer to create the SIG-SAP or DATA-SAP with the specified handle (BCnID) and QoS attributes. To BCn ALPD, BCnID (SIG- S... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 5.4.6.6 CSR Behaviour | CSR behaviour in the UE is summarized in the signal-state diagram in Figure 5.20. The CSR is a transparent routing function. All primitives received from any Adaptation Layer agent are forwarded to the CBCn-SAP without modification; primitives received from the CBCn-SAP are routed to the correct Adaptation Layer agent ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6 AL Control Plane - RNC Side | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.1 Relay Function | The RNC Adaptation Layer uses a Relay Function to associate or map the elementary procedures and signalling used on the Uu interface and the Iu interface. In the present document, interaction between the Relay Function and the Adaptation Layer is described by service primitives exchanged through the Relay Service Acces... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.2 Services Expected from Lower Layers | The RNC Adaptation Layer uses message transfer services provided by the Bearer Connection layer through two Service Access Points: • Common Signalling Service Access Point (COM-SAP) • UE-Specific Signalling Service Access Point (SIG-SAP) There is one and only one permanent instance of the COM-SAP. There are zero or mor... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.3 Agents in the Adaptation Layer | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.3.0 General | The Adaptation Layer in the RNC contains four classes of agent: • Registration Manager (REGM); • GMM Service Access Point Handler (GMMH); • MM Service Access Point Handler (MMH); and • Radio Bearer Control (RBC). There is one instance each of REGM, GMMH, and MMH and two instances of RBC (one for the PS domain and one f... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.3.1 Registration Manager (REGM) | REGM in the RNC is responsible for: • establishing, maintaining, and releasing the UE Specific Signalling connection by performing the radio interface Registration, Handover, and Deregistration procedures with the UE; • radio interface access control, including geographical barring based on UE position; • paging notifi... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.3.2 GMM and MM Service Access Point Handlers (GMMH, MMH) | GMMH and MMH provide a transparent conduit for Mobility Management messages sent between the UE and Core Network (Serving GPRS Support Node (SGSN) and Mobile Switching Centre (MSC) respectively). GMMH and MMH are also responsible for integrity protection control and ciphering control functions. GMMH and MMH use service... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.3.3 Radio Bearer Control (RBC) | RBC handles all signalling related to the establishment, modification, and release of radio bearers. RBC also configures user plane protocol layers (such as PDCP and CSH). RBC uses services provided by the REGM, the Bearer Connection Layer (via SSR or CSR), and the Relay Function (via RSR). |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.3.4 SIG-SAP Router (SSR) | See clause 5.3.5. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.3.5 CBCn-SAP Router (CSR) | See clause 5.3.6. |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.3.6 RL-SAP Router (RSR) | The Adaptation Layer in the RNC contains a transparent routing function at the RL-SAP for all control service primitives exchanged between the Adaptation Layer and the Relay Function, as shown in Figure 6.2. Routing between the RL-SAP and AL agents is based on the ALPD and (SIG-SAP) Bearer Connection ID (BCnID), which ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.4 Protocol Definitions | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.4.1 REGM | |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.4.1.1 REGM Protocol Data Units | The REGM Protocol Data Units are as shown in Table 6.1. Table 6.1: REGM::REGM Protocol Data Units PDU SAP Direction Addressing Information Elements PagingType1 COM To UE UE NAS ID CN Domain Identity, Paging Cause Register COM From UE UE NAS ID Registration Reference, RI Version, CN Domain Identity, Registration Cause, ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.4.1.2 Service Primitives at COM-SAP | The service primitives at COM-SAP are as shown in Table 6.2. Table 6.2: REGM::BCn Service Primitives at COM-SAP [RNC] Primitive Direction Information Elements AL_COMDATA_REQ REGM requests the BCn layer to send a PDU to its peer in the UE To BCn UE NAS ID and Type, {LAI} OPTIONAL REGM PDU Type, REGM PDU AL_COMDATA_IND B... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.4.1.3 Service Primitives at REGM-SIG-SAP | The service Primitives at REGM-SIG-SAP are as shown in Table 6.3. Table 6.3: REGM::SSR Service Primitives at REGM-SIG-SAP [RNC] Primitive Direction Parameters SSR_SIGDATA_REQ REGM requests SSR to send a PDU to its peer in the UE. To SSR REGM PDU SSR_SIGDATA_IND SSR indicates to REGM that it has received a PDU from the ... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.4.1.5 Service Primitives at REGM-CBCn-SAP | The service primitives at REGM-CBCn-SAP are as shown in Table 6.5. Table 6.5: REGM::CSR Service Primitives at REGM-CBCn-SAP [RNC] Primitive Direction Parameters CBCn_CREATE_REQ REGM requests the BCn layer to create the SIG-SAP with the specified handle (BCnID) and QoS attributes. To CSR ALPD, BCnID (SIG- SAP), BCn/AL P... |
2c98de69420a5d5155a767a06ac35aa1 | 102 744-3-6 | 6.4.1.6 Service Primitives at REGM-RL-SAP | The service primitives at REGM-RL-SAP are as shown in Table 6.6. Table 6.6: REGM::RSR Service Primitives at REGM-RL-SAP [RNC] Primitive Direction Parameters RL_PAGING To REGM BCnID, ALPD, UE NAS ID, Paging Cause, CN Domain Identity RL_SIGNAL_CONN_REL To REGM BCnID, ALPD, CN Domain Identity, Cause RL_ SIGNAL_CONN_REL_RE... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.