hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.3 Functional entities
| See clause 4.3.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2 High level functionality and features
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.1 Authorization and Provisioning for A2X communications
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.1.1 General
| Authorization and provisioning of parameters for A2X communication leverages V2X mechanisms as defined in TS 23.287 [11] clause 5.1.1 with the following differences:
- V2X is replaced by A2X.
- The V1 reference point is replaced by the A2X1 reference point.
- The set of parameters defined for A2X are described in cl... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.1.2 Authorization and Provisioning for A2X communications over PC5 reference point
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.1.2.1 Policy/Parameter provisioning
| A2X leverages what is defined for V2X in TS 23.287 [11] clause 5.1.2.1 with the following differences:
- V2X is replaced by A2X.
- The V1 reference point is replaced by the A2X1 reference point.
- Tx Profiles for LTE PC5 are not required.
- Groupcast related policy/parameters are not required.
- In addition to exi... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.1.2.2 Principles for applying parameters for A2X communications over PC5 reference point
| A2X leverages what is defined for V2X in TS 23.287 [11] clause 5.1.2.2 with the following differences:
- V2X is replaced by A2X.
- The V1 reference point is replaced by the A2X1 reference point.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.1.3 Authorization and Provisioning for A2X communications over Uu reference point
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.1.3.1 Policy/Parameter provisioning
| The following set of information may be provisioned to the UAV UE for A2X communication over the Uu reference point using MBS:
1) Mapping of the A2X service type to A2X Application Server address information (consisting of IP address/FQDN and transport layer port#) for unicast.
2) List of FQDNs or IP addresses of the... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.2 A2X communication
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.2.1 A2X communication over PC5 reference point
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.2.1.1 General
| A2X communication over PC5 reference point leverages V2X mechanisms to support Unicast communication mode for NR and Broadcast communication mode for both NR and LTE as defined in clause 5.2.1.1 of TS 23.287 [11] with the following applicable differences:
- V2X is replaced by A2X.
- The distinction between Vehicle UE... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.2.1.2 Broadcast mode communication over PC5 reference point
| A2X leverages what is defined for V2X in clause 5.2.1.2 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
- The applicable configuration is described in clause 6.2.1.2.
- PC5 QoS parameters are described in clause 6.2.4.
- Enhanced QoS handling for NR based PC5 reference point is described... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.2.1.3 Unicast mode communication over PC5 reference point
| A2X leverages what is defined for V2X in clause 5.1.1.3 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
- Definitions for PC5 QoS flows are described in clause 6.2.4.
- Definitions for A2X identifiers are described in clause 6.2.6.
- Procedures for Unicast mode A2X communication over PC5... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.2.1.4 IP address allocation
| A2X leverages what is defined for V2X in clause 5.2.1.5 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
- Procedures for Unicast mode A2X communication over PC5 reference point are described in clause 6.3.3.2.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.2.2 A2X communication over Uu reference point
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.2.2.1 A2X communication via unicast
| A2X leverages what is defined for V2X in clause 5.2.2.1 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.2.2.2 A2X reception via MBS
| A2X leverages what is defined for V2X in clause 5.2.2.2 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
- Multicast MBS session is not supported.
- MBS session announcement is provisioned as described in clauses 6.2.1.1 and 6.2.1.3.1.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.3 A2X Application Server discovery
| Procedures and mechanisms for V2X Application Server discovery used for V2X communication over Uu operation mode as specified in clause 5.3 of TS 23.287 [11] apply to A2X Application Server discovery used for A2X Broadcast MBS sessions with the following differences:
- The A2X Application Server address information as... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.4 QoS handling for A2X communication
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.4.1 QoS handling for A2X communication over PC5 reference point
| A2X leverages what is defined for V2X in clauses 5.4.1 to 5.4.3 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
- Groupcast mode communication is not supported.
- Definitions for PC5 QoS handling are described in clause 6.2.4.
- PC5 QoS configuration parameters are described in clause 6.... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.4.2 QoS handling for A2X communication over Uu reference point
| A2X leverages what is defined for V2X in clause 5.4.5 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
- Notification on QoS Sustainability Analytics to the V2X Application Server is not supported in this release.
- QoS Change based on extended NG-RAN Notification to support Alternative Se... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.5 Subscription to A2X service
| A2X leverages what is defined for V2X in clause 5.5 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
- The distinction between Vehicle and Pedestrian UE is not supported.
- Definitions for PC5 QoS parameters are described in clause 6.2.4.
- The procedure PCF based A2X Service Authorizatio... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.6 Identifiers
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.6.1 Identifiers for A2X communication over PC5 reference point
| A2X leverages what is defined for V2X in clause 5.6.1 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
- Groupcast mode communication and corresponding identifiers are not supported.
- IP address allocation for A2X is described in clause 6.2.2.1.4.
- A2X configuration parameters are descr... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.7 Interworking between EPS A2X and 5GS A2X
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.7.1 A2X Policy and parameter provisioning
| A2X leverages what is defined for V2X in clause 5.8.1 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.7.2 PC5 operation
| A2X leverages what is defined for V2X in clause 5.8.1 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.2.8 MBS Service Description for A2X use
| The announced service information for V2X use as specified in clauses 5.10.2 and 5.10.3 of TS 23.287 [11] is used for the announced service information for A2X use with the following difference:
- V2X is replaced by A2X, e.g. V2X communication to A2X communication, V2X Application Server to A2X Application Server, etc... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3 Functional description and information flows
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.1 Control and user plane stacks for NR PC5 reference point supporting A2X services
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.1.1 User plane for PC5 reference point supporting A2X services
| Figure 6.3.1.1-1 depicts a user plane for NR PC5 reference point, i.e. PC5 User Plane Protocol stack.
Legend:
- PC5-U: The SDAP/PDCP/RLC/MAC/PHY functionality is specified in TS 38.300 [15].
- For PDCP SDU type "Non-IP", a "Non-IP Type" header included in the SDU by upper layer to indicate the type of non-IP messa... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.1.2 Control plane for NR PC5 reference point supporting A2X services
| The protocol stack of clause 6.1.2 of TS 23.287 [11] applies.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.2 Procedures for A2X service authorization and provisioning to UE
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.2.1 General
| The procedures for service authorization and provisioning to UE may be initiated by the PCF (as described in clause 6.3.2.2), by the UE (as described in clause 6.3.2.3), or by the AF (as described in clause 6.3.2.4).
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.2.2 PCF based A2X Service Authorization and Provisioning to UE
| For PCF based Service Authorization and Provisioning to UE, the Registration procedures as defined in clause 4.2.2.2 of TS 23.502 [3], UE Policy Association Establishment procedure as defined in clause 4.16.11 of TS 23.502 [3] and UE Policy Association Modification procedure as defined in clause 4.16.12 of TS 23.502 [3... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.2.3 Procedure for UE triggered A2X Policy provisioning
| The UE triggered Policy Provisioning procedure is initiated by the UE to request A2X Policy/Parameter from the PCF when UE determines the A2X Policy/Parameter is invalid in the following cases:
- if the validity timer indicated in the A2X Policy/Parameter expires;
- if there are no valid parameters, e.g. for the A2X ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.2.4 AF-based service parameter provisioning for A2X communications over control plane
| The A2X Application Server can provision the 5GC with A2X service parameters via NEF using the procedure defined in clause 4.15.6.7 of TS 23.502 [3] with the following considerations:
- The AF in TS 23.502 [3] is considered as A2X Application Server in this specification.
- Service Description indicates A2X service d... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.3 Procedures for A2X communication over PC5 reference point
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.3.1 Broadcast mode A2X communication over NR PC5 reference point
| A2X leverages what is defined for V2X in clause 6.3.1 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
- The applicable configuration is described in clause 6.2.1.2.
- PC5 QoS parameters are described in clause 6.2.4.
- QoS handling for NR based PC5 reference point is described in clause ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.3.2 Unicast mode A2X communication over PC5 reference point
| A2X leverages what is defined for V2X in clause 6.3.3 of TS 23.287 [11] with the following differences:
- V2X is replaced by A2X.
- The applicable configuration is described in clause 6.2.1.2.
- PC5 QoS parameters are described in clause 6.2.4.
- A PC5 unicast link is described in clause 6.2.2.1.3.
- IP address al... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.4 Procedures for A2X communication over Uu reference point
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.4.1 A2X Application server discovery using broadcast MBS session
| The procedure for V2X Application Server discovery using broadcast MBS session as specified in clause 6.4.2 of TS 23.287 [11] is used for A2X Application Server discovery using broadcast MBS session with the following difference:
- V2X is replaced by A2X, e.g. V2X message to A2X message, V2X Application Server to A2X ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.4.2 Procedures for A2X communication with MBS
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.4.2.1 MBS service area mapping
| Procedures and mechanisms for MBS service area mapping for V2X communication with MBS as specified in clause 6.4.3.1 of TS 23.287 [11] apply to MBS service area mapping for Broadcast Remote ID using MBS with the following differences:
- V2X is replaced by A2X, e.g. V2X services to A2X services, V2X Application Server ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.5 Procedures for Service Authorization to NG-RAN for A2X communications over PC5 reference point
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.5.1 General
| In order to enable PC5 radio resource control in NG-RAN, per PC5 RAT A2X service authorization information and PC5 QoS parameters need to be made available in NG-RAN, this clause describes the corresponding procedures and aspects.
NOTE: LTE Uu can control LTE PC5 and/or NR PC5 resource management from the cellular net... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.5.2 Registration procedure
| The Registration procedure for UE is performed as defined in TS 23.502 [3] with the following additions:
- The UE includes the PC5 Capability for A2X (i.e. LTE PC5 only, NR PC5 only, both LTE and NR PC5) as part of the "5GMM capability" in the Registration Request message. The AMF stores this information for A2X opera... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.5.3 Service Request procedure
| The Service Request procedure for UE in CM-IDLE state is performed as defined in TS 23.502 [3] with the following additions:
- If the UE is PC5 capable for A2X and the UE is authorized to use A2X communication over PC5 reference point, then the AMF shall include a "A2X services authorized" indication per PC5 RAT in th... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.5.4 N2 Handover procedure
| The N2 based handover or the Inter-RAT to NG-RAN handover procedures for UE are performed as defined in TS 23.502 [3] with the following additions:
- If the UE is PC5 capable for A2X and the UE is authorized to use A2X communication over PC5 reference point, then the target AMF shall send the "A2X services authorized"... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.5.5 Xn Handover procedure
| The Xn based handover procedures for UE are performed as defined in TS 23.502 [3] with the following additions:
- If the "A2X services authorized" indication is included in the UE context (as described in TS 38.423 [16]), then the source NG-RAN shall include a "A2X services authorized" indication per PC5 RAT, UE-PC5-A... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.5.6 Subscriber Data Update Notification to AMF
| The procedure of Subscriber Data Update Notification to AMF is performed as defined in TS 23.502 [3] with the following additions:
- The Nudm_SDM_Notification service operation may contain the "A2X services authorized" indication per PC5 RAT and/or the UE-PC5-AMBR per PC5 RAT.
- The AMF updates the UE Context with th... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.3.5.7 Delivery of PC5 QoS parameters to NG-RAN
| The UE Policy Association Establishment procedure and UE Policy Association Modification procedure, as defined in TS 23.502 [3], is used to provide to the AMF PC5 QoS parameters used by NG-RAN. When receiving Npcf_UEPolicyControl_Create Request from the AMF which includes the PC5 capability for A2X or when receiving th... |
aac84734dd828878c9914c9a3545338d | 23.272 | 1 Scope | This document defines the Stage 2 architecture and specification for the CS Fallback and for SMS over SGs for EPS or CS Fallback and SMS over S102. The scope of this document includes the architecture enhancements for functionality to enable fallback from E-UTRAN access to UTRAN/GERAN CS domain access and to CDMA 1x RT... |
aac84734dd828878c9914c9a3545338d | 23.272 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
aac84734dd828878c9914c9a3545338d | 23.272 | 3 Definitions and abbreviations | |
aac84734dd828878c9914c9a3545338d | 23.272 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
1xCS: The 3GPP2 legacy circuit Switched signalling system as defined in 3GPP2 X.S0042-0 [22].
CSMT fla... |
aac84734dd828878c9914c9a3545338d | 23.272 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
1xCS IWS Circuit Switched fallback Interworking solution Function for 3GPP2 1xCS.
CSMT Circui... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4 Overall Description | |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.1 General Considerations | The CS fallback in EPS enables the provisioning of voice and other CS-domain services (e.g. CS UDI video/ LCS/ USSD) by reuse of CS infrastructure when the UE is served by E‑UTRAN. A CS fallback enabled terminal, connected to E‑UTRAN may use GERAN or UTRAN to connect to the CS‑domain. This function is only available in... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.2 Reference Architecture | The CS fallback and SMS over SGs in EPS function is realized by using the SGs interface mechanism between the MSC Server and the MME.
The SGs interface functionality is based on the mechanisms specified for the Gs interface, TS 23.060 [3].
Figure 4.2-1: EPS architecture for CS fallback and SMS over SGs
NOTE 1: The MGW ... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.2.1 Reference points | SGs: It is the reference point between the MME and MSC server. The SGs reference point is used for the mobility management and paging procedures between EPS and CS domain, and is based on the Gs interface procedures. The SGs reference point is also used for the delivery of both mobile originating and mobile terminating... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.3 Functional entities | |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.3.1 UE | The CS fallback capable UE supports access to E-UTRAN/EPC as well as access to the CS domain over GERAN and/or UTRAN.
The SMS over SGs capable UE supports access to E-UTRAN/EPC and may support access to the CS domain over GERAN and/or UTRAN.
The support of SMS over SGs is mandatory for a UE that supports CS fallback, w... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.3.2 MME | The CS fallback and/or SMS over SGs enabled MME supports the following additional functions:
- Multiple PLMNs selection for the CS domain.
- RAT selection for the CS domain.
- Deriving a VLR number and LAI from the TAI of the current cell and based on the selected PLMN or the selected RAT for CS domain, or using a defa... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.3.3 MSC | The CS fallback and/or SMS over SGs enabled MSC supports the following additional functions:
- Maintaining SGs association towards MME for EPS/IMSI attached UE.
- Supporting SMS procedures defined in this document.
- When configured to support the return to the last used PLMN after CSFB:
- Indicating to GERAN/UTRAN dur... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.3.4 E-UTRAN | The CS fallback enabled E-UTRAN supports the following additional functions:
- Forwarding paging request for CS domain to the UE.
- Directing the UE to the target CS capable cell considering the registered PLMN ID and possibly the LAC for CS domain received from the MME.
- The configuration of appropriate cell reselect... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.3.5 SGSN | If the SGSN supports ISR, SGSN shall follow the rules and procedures described in TS 23.401 [2] and TS 23.060 [3] with the following additions and clarifications:
- The SGSN shall not send the ISR activated indication at combined RAU/LAU procedure if the UE indicates support of CSFB and/or SMS over SGs.
An SGSN that su... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.3.6 BSS | If the BSS receives indication from the MSC that the CS service (Call, CISS or LCS) was established as a result of CS fallback the BSS may e.g. select to use RR Connection Release with Redirect to send the UE back to E-UTRAN at release of the CS service.
When configured to support the return to the last used PLMN after... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.3.7 RNS | If the RNS receives indication from the MSC that the CS service (Call, CISS or LCS) was established as a result of CS fallback the RNS may e.g. select to use RRC Connection Release with Redirect to send the UE back to E-UTRAN at release of the CS service.
When configured to support the return to the last used PLMN afte... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.4 Control plane | |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.4.1 MME - MSC Server | Legend:
SGsAP: This protocol is used to connect an MME to an MSC Server based on the BSSAP+.
Stream Control Transmission Protocol (SCTP): This protocol transfers signalling messages.
Figure 4.4.1-1: SGs Interface |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.5 Co-existence with IMS services | A CS Fallback and IMS capable UE shall follow the procedures for domain selection for UE originating session/calls according to TS 23.221 [26] 'Domain selection for UE originating sessions / calls'.
An IMS capable UE which supports SMS over IP networks shall follow the procedures for domain selection for UE originating... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.6 Emergency Calls | |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.6.1 General | When UE is performing CS fallback procedure for Mobile Originating Call for the purpose of emergency call, it shall indicate to the MME that this CS fallback request is for emergency purpose. MME also indicates to the E-UTRAN via the appropriate S1-AP message that this CS fallback procedure is for emergency purpose. If... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.6.2 Procedures to handle emergency call setup with IMSI | This procedure is only invoked when permitted by the operator policy.
When MME detects that the CSFB request is due to emergency call and eNodeB indicates that the UE is not available for the PS service at the target RAT, it shall mark the SGs association as not valid (i.e., move to SGs-NULL state) and shall not send I... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.7 CSFB Priority Call Handling | CSFB Priority call handling ensures that, when the network supports eMLPP service (TS 22.067 [37]) or another CS domain priority scheme (e.g. TIA-917 [46] or TR 22.952 [47]), end-to-end priority handling is provided for both mobile originated CSFB calls by a user in E-UTRAN which is entitled for this by a CS domain pri... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.8 CS services handling in specific cases | |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.8.1 SGs paging without LAI | If the SGs Paging Request does not contain the LAI, and if the MME can retrieve the S-TMSI associated to the IMSI, the MME shall temporarily store this MSC/VLR number and force the UE to re-attach to the non-EPS services based on:
- If the UE is in connected mode, the MME shall not send a SGs Service Request to the MSC... |
aac84734dd828878c9914c9a3545338d | 23.272 | 4.8.2 Handling of SGs paging when MME cannot retrieve the S-TMSI | Upon receiving SGs Paging Request, if the MME cannot retrieve the S-TMSI associated with IMSI, the MME shall page the UE with IMSI and PS indicator to force the UE to re-attach to EPS and non-EPS services. |
aac84734dd828878c9914c9a3545338d | 23.272 | 5 Mobility Management | |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.1 General | The CS fallback and SMS over SGs in EPS is realized by using the SGs interface mechanism between the MSC Server and the MME. The SMS over SGs NAS procedures are also used for the SMS in MME option.
The use of the "pool-area" concept as specified in TS 23.236 [23] allows to minimize the occurrence of MSC change at CS fa... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.2 Attach procedure | The attach procedure for the CS fallback, SMS over SGs or "SMS in MME" in EPS is realized based on the combined GPRS/IMSI Attach procedure specified in TS 23.060 [3].
Figure 5.2-1: Attach Procedure
1) The UE initiates the attach procedure by the transmission of an Attach Request (parameters as specified in TS 23.401 [2... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.3 Detach procedure | |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.3.1 UE-initiated Detach procedure | The UE-initiated Detach procedure for the CS fallback and SMS over SGs in EPS is realized based on the MS-Initiated Detach Procedure specified in TS 23.060 [3].
Figure 5.3.1-1: UE-initiated Detach Procedure
1) The UE initiates the detach procedure by the transmission of a Detach Request (parameters as specified in TS 2... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.3.2 MME-initiated Detach procedure | The MME-initiated detach procedure for the CS fallback and SMS over SGs in EPS is realized based on the SGSN-Initiated Detach Procedure specified in TS 23.060 [3].
Figure 5.3.2-1: MME-initiated Detach Procedure
1) The MME-initiated Detach procedure is performed as specified in TS 23.401 [2].
2a) If EPS service is not a... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.3.3 HSS-initiated Detach procedure | The HSS-initiated detach procedure for the CS fallback and SMS over SGs in EPS is realized based on the HLR-Initiated Detach Procedure specified in TS 23.060 [3].
Figure 5.3.3-1: HSS-initiated Detach Procedure
1) The HSS-initiated Detach procedure is performed as specified in TS 23.401 [2].
2) The MME sends an EPS Deta... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.3.4 Administration of the MME - MSC/VLR Association | The MME - MSC/VLR association is created at the following occasions:
- Combined EPS/ IMSI attach in clause 5.2.
- Combined TA/LA Update in clause 5.4.
The association is updated on the following occasions:
- When an UE changes MME.
The MME - MSC/VLR association is removed at the following occasions:
- UE-initiated Deta... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.4 TA/LA Update procedure | |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.4.0 General | When a CS fallback and/or SMS over SGs capable UE is EPS/IMSI attached, it initiates the combined TA/LA procedure based on the triggers specified in TS 23.401 [2].
When a CS fallback and/or SMS over SGs capable UE is not EPS/IMSI attached, it may initiate a combined TA/LA procedure in order to use CS Fallback or SMS ov... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.4.1 Combined TA/LA Update Procedure | NOTE 1: The combined TA/LA Update procedure for the CS fallback, SMS over SGs or "SMS in MME" in EPS is realized based on the combined RA/LA Update procedure specified in TS 23.060 [3].
Figure 5.4.1-1: Combined TA / LA Update Procedure
1) The UE detects a change to a new TA by discovering that its current TAI is not in... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.4.2 Periodic TA and LA Update Procedure | When the UE is camped on E-UTRAN, periodic LA updates shall not be performed, but periodic TA updates shall be performed. In this case, an SGs association is established and the MSC/VLR shall disable implicit detach for EPS-attached UEs and instead rely on the MME to receive periodic TA updates.
When a periodic TA upda... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.4.3 Non-EPS Alert procedure | The MSC/VLR may request an MME to report activity from a specific UE. In this case, the MSC/VLR shall send a SGsAP Alert Request (IMSI) message to the MME where the UE is currently EPS-attached.
Upon reception of the SGsAP Alert Request (IMSI) message, the MME shall set NEAF (Non-EPS Alert Flag). If NEAF is set for an ... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.4.4 Void | |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.5 Idle Mode Signalling Reduction | In relation with CSFB and/or SMS over SGs, when ISR is activated, the UE follows regular ISR behaviour. It may reselect between E-UTRAN and GERAN/UTRAN without a need to update the CN. When a mobile terminated service arrives, the MSC/VLR sends a paging message via SGs to the MME. The MME pages in the TA(s) registered ... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.6 Mobility Management for SMS over SGs only UEs | UEs that need SMS service but not CSFB indicate this specific condition with the "SMS-only" indication in the EPS/IMSI Attach Request and combined TA/LA update procedures (or, for a UE that only supports NB-IoT, optionally using the EPS Attach Request and TA update procedures, see TS 23.401 [2]). This allows an operato... |
aac84734dd828878c9914c9a3545338d | 23.272 | 5.7 Access to CS services after selecting a non-3GPP access | When a UE, which obtained voice and/or SMS services using an EPS/IMSI registration via E-UTRAN, selects a non-3GPP access network, the UE tries to retain these services by actions described in TS 23.221 [26], clause 7.2a. |
aac84734dd828878c9914c9a3545338d | 23.272 | 6 Mobile Originating Call | |
aac84734dd828878c9914c9a3545338d | 23.272 | 6.1 General | This clause describes the mobile originating call procedures for the CS Fallback in EPS. |
aac84734dd828878c9914c9a3545338d | 23.272 | 6.2 Mobile Originating call in Active Mode - PS HO supported | This flow may be executed when the eNodeB knows that both the UE and the network support PS HO, in the normal case. Clause 6.6 describes the procedure when the procedure is rejected by the MME.
Figure 6.2-1: CS Call Request in E-UTRAN, Call in GERAN/UTRAN
NOTE 1: DTM is not mandatory for CS Fallback to work and is not ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.