Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
1,301 | 10.15 F1-C Traffic Transfer | In EN-DC/NR-DC, the F1-C Traffic Transfer message is sent by the MN to the SN or by the SN to MN to transfer the F1-C traffic to and from an IAB-node. Figure 10.15-1: F1-C transfer procedure in EN-DC 1. When the IAB-MT sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet, it sends it to the MN in a container within ULInformationTransfer message as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. 2. The MN initiates the F1-C Traffic Transfer procedure, in which it transfers the received F1-AP message encapsulated in (SCTP/)IP or F1-C related (SCTP/)IP packet as an octet string. 3. When the SN sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet, it sends it to the MN as an octet string through the F1-C Traffic Transfer procedure. 4. The MN sends the received F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet to the IAB-MT in a container within DLInformationTransfer message as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. Figure 10.15-2: Scenario 1: F1-C transfer between IAB-MT and SN (F1-terminating node) in NR-DC 1. The IAB-MT sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet to the MN (non-F1-terminating node) via SRB2 in a container within ULInformationTransfer message as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. 2. The MN initiates the F1-C Traffic Transfer procedure, in which it transfers the received F1-AP message encapsulated in (SCTP/)IP or F1-C related (SCTP/)IP packet as an octet string. 3. The SN (F1-terminating node) sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet to the MN as an octet string through the F1-C Traffic Transfer procedure. 4. The MN sends the received F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet to the IAB-MT via SRB2 in a container within DLInformationTransfer message as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.15 |
1,302 | 5.39.2 Configuration for the UE | In order to enable UP Remote Provisioning of credentials for NSSAA or secondary authentication/authorization, UE Configuration Data for UP Remote Provisioning are either pre-configured on the UE or provided by the network to the UE. UE Configuration Data for UP Remote Provisioning provided by the network take precedence over corresponding configuration data stored in the UE. UE Configuration Data for UP Remote Provisioning consist of PVS IP address(es) and/or PVS FQDN(s). The PVS IP address or PVS FQDN may be associated with dedicated DNN(s) and/or S-NSSAI(s). If the UE does not have any PVS IP address or PVS FQDN after the establishment of a PDU Session used for UP remote provisioning, the UE may construct an FQDN for PVS discovery as defined in TS 23.003[ Numbering, addressing and identification ] [19]. The UE Configuration Data for UP Remote Provisioning may be stored in the ME. The UE Configuration Data for UP Remote Provisioning (i.e. PVS IP address(es) or PVS FQDN(s)) associated with dedicated DNN(s) and/or S-NSSAI(s) may be locally configured in the SMF. The UE Configuration Data for UP Remote Provisioning, if available, shall be provided to the UE during the establishment of any PDU Session used for UP Remote Provisioning as part of Protocol Configuration Options (PCO) in the PDU Session Establishment Response, if the UE has requested the PVS information via PCO in the PDU Session Establishment Request. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.39.2 |
1,303 | J.1 Procedure for PIN service | Figure J.1-1: Procedure for PIN service PIN is a subscribed service, and a user needs to coordinate with the Mobile Network Operator to subscribe for PIN service. When a user subscribes for a PIN, the subscription data includes the DNN and S NSSAI allocated by the MNO for the PIN service. The PIN user's PEGC UE(s) are then provisioned with appropriate URSP rules to enable the PEGC UE to route the PIN traffic using the DNN and S NSSAI allocated for the PIN. Figure J.1-1 provides a high level procedure for PIN service. Step 1: Step 1 is performed using O&M. A user subscribes to the Mobile Network Operator (MNO) for PIN service. The user provides the list of PEGC UE(s) that are part of the PIN. The MNO verifies the request, performs necessary checks e.g. whether the UEs are allowed to act as PEGC, whether all the requested PEGC UEs are part of the same UDM group etc. If the request is authorized by the MNO, the MNO: - allocates a dedicated DNN, S NSSAI for the PIN; - if the PIN has a single PEGC UE, then updates the PEGC UE subscription with the DNN, S NSSAI allocated for the PIN; - if the PIN has more than one PEGC UE, then creates a group subscription following the 5G VN group management principles as specified in clause 5.29.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The information on the External Group ID and associated DNN and S-NSSAI is provided to the AF for PIN; - if local switching is required, configures in the SMF set and/or in the NRF that the DNN allocated for the PIN is served by a specific SMF set. NOTE: It is assumed that all PEGC UEs that are members of a PIN are part of the same UDM Group ID. If the PEGC UEs requested by the user for PIN creation are not part of the same UDM Group ID, the MNO migrates all the PEGC UEs into a single UDM Group ID for creating the group subscription. Step 2: For routing PIN traffic by the PEGC UE, the AF provides guidance for URSP generation to the 5GC. The AF uses a UE ID (i.e. GPSI) as the target UE if the PIN contains a single PEGC UE. If the PIN contains more than one PEGC UE, then the AF uses External Group ID as the target UEs for providing URSP guidance to the 5GC. The AF request contains DNN, S NSSAI allocated to the user for the PIN service and the traffic descriptor components in the URSP rule request from the AF contains the PIN ID. The NEF authorizes the request received from the AF and stores the information in the UDR as "Application Data". The NEF can use the procedure for authorization of service specific parameter provisioning as specified in clause 4.15.6.7a to authorize the AF request by the UDM. In this case: - if the request is for an individual UE, the UDM checks if the DNN and S NSSAI in the AF request is allowed for the UE; - if the request is for a group of UEs, the UDM checks whether the group related data (e.g. DNN/S NSSAI group related data, see table 4.15.6.3b-1) is authorized for the group. If the AF request is authorized, the NEF stores the AF requested information in the UDR as the "Application Data" (Data Subset setting to "Service specific information"). Step 3: The PCF receives a Nudr_DM_Notify notification of data change from the UDR, generates the URSP rules and initiates UE Policy delivery as specified in clause 4.2.4.3 to provision the URSP rules in the PEGC UE(s). For routing of PIN traffic by the PEGC UE(s), the URSP policies provided to the PEGC UE(s) contain URSP rule with PIN ID as traffic descriptor. Step 4: The AF provides QoS requirements for the PIN traffic following procedures for AF requested QoS for a UE or group of UEs not identified by a UE address as specified in clause 4.15.6.14. Step 5: When the PEGC UE(s) detect PIN traffic, it uses the provisioned URSP rules to identify PDU session to route the traffic as specified in clause 6.6.2.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The 5GC further performs session management and user plane management as described in Annex P, clause P.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When 5G VN Group is not used for a PIN and if the PIN contains more than one PEGCs, then the AF request for URSP guidance and QoS requirements is targeted to each individual PEGC UEs that are part of the PIN. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | J.1 |
1,304 | 4.15.3.1 Monitoring Events | The Monitoring Events feature is intended for monitoring of specific events in 3GPP system and making such monitoring events information reported via the NEF. It is comprised of means that allow NFs in 5GS for configuring the specific events, the event detection and the event reporting to the requested party. To support monitoring features in roaming scenarios, a roaming agreement needs to be made between the HPLMN and the VPLMN. If the AMF/SMF in the VPLMN determine that normalisation of an event report is required, the AMF/SMF normalises the event report before sending it to the NEF. The set of capabilities required for monitoring shall be accessible via NEF to NFs in 5GS. Monitoring Events via the UDM, the AMF, the SMF, the NSACF and the GMLC enables NEF to configure a given Monitor Event at UDM, AMF, SMF, NSACF or GMLC and reporting of the event via UDM and/or AMF, SMF, NSACF or GMLC. Depending on the specific monitoring event or information, it is the AMF, GMLC, NSACF or the UDM that is aware of the monitoring event or information and makes it reported via the NEF. The following table enumerates the monitoring events and their detection criteria: Table 4.15.3.1-1: List of events for monitoring capability | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.3.1 |
1,305 | 8.13.3.3.2 Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Port with TM4 interference model (Cell-Specific Reference Symbols) for TDD PCell | The purpose of these tests is to verify the closed loop rank-one performance with wideband precoding with two transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 4 interference model defined in clause B.5.3. In Table 8.13.3.3.2-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. For TDD FDD CA with TDD PCell with 2 DL CCs, the requirements are specified in Table 8.13.3.3.2-4, based on single carrier requirement specified in Table 8.13.3.3.2-2 and Table 8.13.3.3.2-3, with the addition of the parameters in Table 8.13.3.3.2-1 and the downlink physical channel setup according to Annex C.3.2. Table 8.13.3.3.2-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) with TM4 interference model for CA Table 8.13.3.3.2-2: Single carrier performance for Enhanced Performance Requirement Type A for FDD SCell (FRC) Table 8.13.3.3.2-3: Single carrier performance for Enhanced Performance Requirement Type A for TDD PCell and SCell (FRC) Table 8.13.3.3.2-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.3.3.2 |
1,306 | 6.2.5.2 QoS in MA PDU session | In an MA PDU session, unless it : a) is established over non-3GPP access; and b) has a PDN connection as a user-plane resource; the UE shall have one set of QoS rules, one set of QoS flow descriptions and one session-AMBR. The network can provide the set of QoS rules, the set of QoS flow descriptions and the session-AMBR of the MA PDU session via either access of the MA PDU session. In an MA PDU session, the UE shall support:- - modification or deletion via an access of a QoS rule or a QoS flow description; and - modification via an access of the session-AMBR; of the MA PDU session created via the same or the other access. In an MA PDU session: a) established over non-3GPP access; and b) with a PDN connection as a user-plane resource; the UE shall have two sets of QoS rules, two sets of QoS flow descriptions and two session-AMBR values - one is maintained via non-3GPP access and the other is associated with EPS bearer contexts of the PDN connection and maintained via Extended protocol configuration options IE parameters received via the PDN connection. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.5.2 |
1,307 | 4.7.13.6 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure If a low layer failure occurs before the security mode control procedure is completed, a SERVICE ACCEPT or SERVICE REJECT message has been sent to the MS, the network enters/stays in PMM-IDLE. b) Protocol error If the SERVICE REQUEST message is received with a protocol error, the network shall return a SERVICE REJECT message with one of the following reject causes: #96: Mandatory information element error; #99: Information element non-existent or not implemented; #100: Conditional IE error; #111: Protocol error, unspecified. The network stays in PMM-IDLE mode. c) More than one SERVICE REQUEST received and the procedure has not been completed (i.e., the security mode control procedure has not been completed or SERVICE ACCEPT, SERVICE REJECT message has not been sent) - If one or more of the information elements in the SERVICE REQUEST message differs from the ones received within the previous SERVICE REQUEST message, the previously initiated Service request procedure shall be aborted and the new Service request procedure shall be progressed; - If the information elements do not differ, then the network shall continue with the previous Service request procedure and shall not treat any further this SERVICE REQUEST message. d) ATTACH REQUEST received before the security mode control procedure has been completed or an SERVICE ACCEPT or an SERVICE REJECT message has been sent If an ATTACH REQUEST message is received and the security mode control procedure has not been completed or an SERVICE ACCEPT or an SERVICE REJECT message has not been sent, the network may initiate the GMM common procedures, e.g. the GMM authentication and ciphering procedure. The network may e.g. after a succesful GMM authentication and ciphering procedure execution, abort the Service request procedure, the GMM context, PDP contexts and MBMS contexts, if any, are deleted and the new ATTACH REQUEST is progressed. e) ROUTING AREA UPDATE REQUEST message received before the security mode control procedure has been completed or an SERVICE ACCEPT or an SERVICE REJECT message has been sent If an ROUTING AREA UPDATE REQUEST message is received and the security mode control procedure has not been completed or an SERVICE ACCEPT or an SERVICE REJECT message has not been sent, the network may initiate the GMM common procedures, e.g. the GMM authentication and ciphering procedure. The network may e.g. after a successful GMM authentication and ciphering procedure execution, abort the Service request procedure and progress the routing area update procedure. f) If the Service Type indicates 'data’ and the network fails to re-establish some or all RAB(s) then the SGSN may determine if PDP Context Modification or PDP Context Deactivation should be initiated. The appropriate action is an operator choice and depends on the QoS profile of the PDP Context, and the Uplink data status. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.13.6 |
1,308 | 5.5.3.8 Charging Principles for roaming architecture for voice over IMS with home routed traffic | The roaming architecture for voice over IMS with home routed traffic is described in the TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [209]. The breakout point for both the IMS signalling and media traffic is in the home network for a roaming UE, i.e. for 3GPP systems, the P-GW/GGSN/SMF-UPF for a roaming UE is in the HPLMN of the UE. Based on GSMA BA.27 [500], the VPLMN will not have awareness of the services being used over the IMS APN and cannot support service-aware wholesale charging. Data roaming charges will apply for all traffic traversing S8 or Gp interface per the existing data roaming agreement. The HPLMN operator will be responsible for all interworking connectivity and call termination fees associated with call or service termination. Specifically, the serving PLMN identifier of the UE is needed for the home network. Details are described in the TS 32.260[ Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging ] [20]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.3.8 |
1,309 | 9.11.3.82 NSSRG information | The purpose of the NSSRG information information element is to identify one or more NSSRG values associated with each of the HPLMN S-NSSAIs in a configured NSSAI. The NSSRG information information element is coded as shown in figure 9.11.3.82.1, figure 9.11.3.82.2 and table 9.11.3.82.1. The NSSRG information is a type 6 information element with minimum length of 7 octets and maximum length of 4099 octets. Figure 9.11.3.82.1: NSSRG information information element Figure 9.11.3.82.2: NSSRG values for S-NSSAI Table 9.11.3.82.1: NSSRG information information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.82 |
1,310 | 5.40.5 Handling when a Disaster Condition is no longer applicable | When a UE detects a Disaster Condition is no longer applicable, the UE performs PLMN selection as described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] and may return to the PLMN previously with Disaster Condition. A PLMN providing Disaster Roaming: - May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition when the Disaster Inbound Roamers attempt to transit to 5GMM-CONNECTED mode. - May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by triggering Deregistration procedure. - May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by rejecting Registration Request message. - May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by rejecting Service Request message. - Shall organise the return of the Disaster Roaming UEs in a manner that does not cause overload (e.g. of signalling) in the PLMN that previously had the Disaster Condition. - Stop broadcasting of providing Disaster Roaming service as specified in clause 5.40.3. - May determine that the disaster condition has ended and the UE which is registered for disaster roaming services has an emergency PDU session, the AMF initiates the UE configuration update procedure to indicate that the UE is registered for emergency services as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. - May determine that the disaster condition has ended and inform the UE by initiating the UE configuration update procedure indicating re-registration from UE is required as specified in clause 5.4.4 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] if the UE is in CM-CONNECTED mode. NOTE: Whether and how long the PLMN waits before paging the Disaster Inbound Roamers upon being notified that a Disaster Condition no longer applies is up to operator's policy. The HPLMN i.e. the UDM may trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by triggering Deregistration procedure. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.40.5 |
1,311 | 9.2.4 Measurements | In RRC_CONNECTED, the UE measures multiple beams (at least one) of a cell and the measurements results (power values) are averaged to derive the cell quality. In doing so, the UE is configured to consider a subset of the detected beams. Filtering takes place at two different levels: at the physical layer to derive beam quality and then at RRC level to derive cell quality from multiple beams. Cell quality from beam measurements is derived in the same way for the serving cell(s) and for the non-serving cell(s). Measurement reports may contain the measurement results of the X best beams if the UE is configured to do so by the gNB. The corresponding high-level measurement model is described below: Figure 9.2.4-1: Measurement Model NOTE 1: K beams correspond to the measurements on SSB or CSI-RS resources configured for L3 mobility by gNB and detected by UE at L1. - A: measurements (beam specific samples) internal to the physical layer. - Layer 1 filtering: internal layer 1 filtering of the inputs measured at point A. Exact filtering is implementation dependent. How the measurements are actually executed in the physical layer by an implementation (inputs A and Layer 1 filtering) is not constrained by the standard. - A1: measurements (i.e. beam specific measurements) reported by layer 1 to layer 3 after layer 1 filtering. - Beam Consolidation/Selection: beam specific measurements are consolidated to derive cell quality. The behaviour of the Beam consolidation/selection is standardised and the configuration of this module is provided by RRC signalling. Reporting period at B equals one measurement period at A1. - B: a measurement (i.e. cell quality) derived from beam-specific measurements reported to layer 3 after beam consolidation/selection. - Layer 3 filtering for cell quality: filtering performed on the measurements provided at point B. The behaviour of the Layer 3 filters is standardised and the configuration of the layer 3 filters is provided by RRC signalling. Filtering reporting period at C equals one measurement period at B. - C: a measurement after processing in the layer 3 filter. The reporting rate is identical to the reporting rate at point B. This measurement is used as input for one or more evaluation of reporting criteria. - Evaluation of reporting criteria: checks whether actual measurement reporting is necessary at point D. The evaluation can be based on more than one flow of measurements at reference point C e.g. to compare between different measurements. This is illustrated by input C and C1. The UE shall evaluate the reporting criteria at least every time a new measurement result is reported at point C, C1. The reporting criteria are standardised and the configuration is provided by RRC signalling (UE measurements). - D: measurement report information (message) sent on the radio interface. - L3 Beam filtering: filtering performed on the measurements (i.e. beam specific measurements) provided at point A1. The behaviour of the beam filters is standardised and the configuration of the beam filters is provided by RRC signalling. Filtering reporting period at E equals one measurement period at A1. - E: a measurement (i.e. beam-specific measurement) after processing in the beam filter. The reporting rate is identical to the reporting rate at point A1. This measurement is used as input for selecting the X measurements to be reported. - Beam Selection for beam reporting: selects the X measurements from the measurements provided at point E. The behaviour of the beam selection is standardised and the configuration of this module is provided by RRC signalling. - F: beam measurement information included in measurement report (sent) on the radio interface. Layer 1 filtering introduces a certain level of measurement averaging. How and when the UE exactly performs the required measurements is implementation specific to the point that the output at B fulfils the performance requirements set in TS 38.133[ NR; Requirements for support of radio resource management ] [13]. Layer 3 filtering for cell quality and related parameters used are specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] and do not introduce any delay in the sample availability between B and C. Measurement at point C, C1 is the input used in the event evaluation. L3 Beam filtering and related parameters used are specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] and do not introduce any delay in the sample availability between E and F. Measurement reports are characterized by the following: - Measurement reports include the measurement identity of the associated measurement configuration that triggered the reporting; - Cell and beam measurement quantities to be included in measurement reports are configured by the network; - The number of non-serving cells to be reported can be limited through configuration by the network; - Cells belonging to an exclude-list configured by the network are not used in event evaluation and reporting, and conversely when an allow-list is configured by the network, only the cells belonging to the allow-list are used in event evaluation and reporting; - Beam measurements to be included in measurement reports are configured by the network (beam identifier only, measurement result and beam identifier, or no beam reporting). Intra-frequency neighbour (cell) measurements and inter-frequency neighbour (cell) measurements are defined as follows: - SSB based intra-frequency measurement: a measurement is defined as an SSB based intra-frequency measurement provided the center frequency of the SSB of the serving cell and the center frequency of the SSB of the neighbour cell are the same, and the subcarrier spacing of the two SSBs is also the same. - SSB based inter-frequency measurement: a measurement is defined as an SSB based inter-frequency measurement provided the center frequency of the SSB of the serving cell and the center frequency of the SSB of the neighbour cell are different, or the subcarrier spacing of the two SSBs is different. NOTE 2: For SSB based measurements, one measurement object corresponds to one SSB and the UE considers different SSBs as different cells. NOTE 2a: If a UE is configured to perform serving cell measurements based on an NCD-SSB configured in its active BWP, this NCD-SSB is considered as the SSB of the serving cell in the definition of intra-frequency and inter-frequency measurements as above. - CSI-RS based intra-frequency measurement: a measurement is defined as a CSI-RS based intra-frequency measurement provided that: - The subcarrier spacing of CSI-RS resources on the neighbour cell configured for measurement is the same as the SCS of CSI-RS resources on the serving cell indicated for measurement; and - For 60kHz subcarrier spacing, the CP type of CSI-RS resources on the neighbour cell configured for measurement is the same as the CP type of CSI-RS resources on the serving cell indicated for measurement; and - The centre frequency of CSI-RS resources on the neighbour cell configured for measurement is the same as the centre frequency of CSI-RS resource on the serving cell indicated for measurement. - CSI-RS based inter-frequency measurement: a measurement is defined as a CSI-RS based inter-frequency measurement if it is not a CSI-RS based intra-frequency measurement. NOTE 3: Extended CP for CSI-RS based measurement is not supported in this release. Whether a measurement is non-gap-assisted or gap-assisted depends on the capability of the UE, the active BWP of the UE and the current operating frequency: - For SSB based inter-frequency measurement, if the measurement gap requirement information is reported by the UE, a measurement gap configuration may be provided according to the information. Otherwise, a measurement gap configuration is always provided in the following cases: - If the UE only supports per-UE measurement gaps; - If the UE supports per-FR measurement gaps and any of the serving cells are in the same frequency range of the measurement object. - For SSB based intra-frequency measurement, if the measurement gap requirement information is reported by the UE, a measurement gap configuration may be provided according to the information. Otherwise, a measurement gap configuration is always provided in the following case: - Other than the initial BWP, if any of the UE configured BWPs do not contain the frequency domain resources of the SSB associated to the initial DL BWP, and are not configured with NCD-SSB for serving cell measurement. In non-gap-assisted scenarios, the UE shall be able to carry out such measurements without measurement gaps. In gap-assisted scenarios, the UE cannot be assumed to be able to carry out such measurements without measurement gaps. Network may request the UE to measure NR and/or E-UTRA carriers in RRC_IDLE or RRC_INACTIVE via system information or via dedicated measurement configuration in RRCRelease. If the UE was configured to perform measurements of NR and/or E-UTRA carriers while in RRC_IDLE or in RRC_INACTIVE, it may provide an indication of the availability of corresponding measurement results to the gNB in the RRCSetupComplete message. The network may request the UE to report those measurements after security activation. The request for the measurements can be sent by the network immediately after transmitting the Security Mode Command (i.e. before the reception of the Security Mode Complete from the UE). If the UE was configured to perform measurements of NR and/or E-UTRA carriers while in RRC_INACTIVE, the gNB can request the UE to provide corresponding measurement results in the RRCResume message and then the UE can include the available measurement results in the RRCResumeComplete message. Alternatively, the UE may provide an indication of the availability of the measurement results to the gNB in the RRCResumeComplete message and the gNB can then request the UE to provide these measurement results. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.4 |
1,312 | 6.3.1.2.4 Abnormal cases in the UE | The following abnormal cases can be identified: a) PDU session inactive for the received PDU session ID. If the PDU session ID in the PDU SESSION AUTHENTICATION COMMAND message belongs to any PDU session in state PDU SESSION INACTIVE in the UE, the UE shall send a 5GSM STATUS message with the 5GSM cause IE set to #43 "Invalid PDU session identity". b) Collision of UE-requested PDU session release procedure and a PDU session authentication and authorization procedure. When the UE receives a PDU SESSION AUTHENTICATION COMMAND message during the UE-requested PDU session release procedure, and the PDU session indicated in PDU SESSION AUTHENTICATION COMMAND message is the PDU session that the UE had requested to release, the UE shall ignore the PDU SESSION AUTHENTICATION COMMAND message and proceed with the UE-requested PDU session release procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1.2.4 |
1,313 | 5.3.6.2.1 Mobile originated multimedia call establishment | At call setup the required call type, 3G-324M, is indicated by the originating MS in the SETUP message, with the bearer capability IE parameter Other Rate Adaption set to "H.223 and H.245". For analogue multimedia, the support of a fallback to speech is requested by including two bearer capability IEs, multimedia first and speech as the second BC in the SETUP message. The MS shall indicate fallback to speech by these two BC IEs and the associated Repeat Indicator set to "support of fallback". For UDI/RDI multimedia, the support of a fallback and service change is requested by including two bearer capability IEs, with the first BC as the preferred service in the SETUP message. The MS shall indicate service change and fallback by these two BC IEs and the associated Repeat Indicator set to "support of service change and fallback". If the bearer capability IE is received from the MS either in A/Gb or GERAN Iu mode and indicates no A/Gb mode support for the requested bearer service, the network shall consider it as a request to perform an inter-system handover to UTRAN Iu mode, as described in 3GPP TS 23.009[ Handover procedures ] [114] subclause 14.2. The bearer compatibility checking in the network is according to subclause 5.3.4.2.1. If the MS requested for an analogue multimedia call with fallback to speech, or for a UDI/RDI multimedia call with fallback and service change, and the network accepts the call, the network has the following options for the inclusion of bearer capability IEs in the CALL PROCEEDING message: - if the network accepts the requested analogue multimedia call and supports fallback to speech, both multimedia and speech bearer capability IEs shall be included; - if the network accepts the requested UDI/RDI multimedia call and supports fallback and service change, both multimedia and speech bearer capability IEs shall be included. The order of the bearer capability IEs determines the preferred service, and the network may reverse the order of these IEs (see 3GPP TS 23.172[ Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 ] [97], subclause 4.2.1); - if the network accepts a multimedia (only) call, a multimedia bearer capability IE shall be included; - if the network accepts a speech (only) call, a speech bearer capability IE shall be included; - for a UDI/RDI multimedia call, if the network accepts the requested speech call and supports service change, both multimedia and speech bearer capability IEs shall be included. The order of the bearer capability IEs determines the preferred service, and the network may reverse the order of these IEs (see 3GPP TS 23.172[ Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 ] [97], subclause 4.2.1); - if the network received a UDI/RDI multimedia bearer capability IE with FNUR equal to 32kbit/s and a speech bearer capability IE in the SETUP message, the network shall not release the call, but shall reply with one bearer capability IE only, as specified in 3GPP TS 23.172[ Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 ] [97]. NOTE: Service change and fallback for UDI/RDI multimedia calls is not supported with Fixed Network User Rate set to 32 kbit/s (see 3GPP TS 23.172[ Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 ] [97]). If the MS requested for a multimedia call only, and the network accepts the call, the network shall always include a single multimedia bearer capability IE in the CALL PROCEEDING message. The originating user shall determine (possibly by pre-configuration of the terminal) whether a digital connection is required or if the call will be an analog modem call. If the call is expected to be digital the multimedia bearer capability IE parameter ITC is set to UDI/RDI. In an analog call the multimedia bearer capability IE parameter ITC is set to "3,1 kHz audio ex PLMN". Additionally required modem type is indicated (Other Modem Type = V.34). 5.3.6.2.1.1 Fallback If the network, during the setup of an H.324-call, detects that the transit network or the called end does not support an H.324 call (e.g. because of a failure in the modem handshaking in case of an analogue multimedia call), then the network initiates the in-call modification procedure (see subclause 5.3.4.3) towards the MS to modify the call mode to speech, if the MS had included a speech bearer capability IE in the SETUP message. In case of a UDI/RDI multimedia call with service change and fallback, if the network detects that the called end does not support speech, then it initiates an in-call modification procedure towards the MS to modify the call mode to multimedia, if the first bearer capability IE was for a speech call. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.6.2.1 |
1,314 | 9.2.3.2.3 Data Forwarding | The following description depicts the data forwarding principles for intra-system handover. The source NG-RAN node may suggest downlink data forwarding per QoS flow established for a PDU session and may provide information how it maps QoS flows to DRBs. The target NG-RAN node decides data forwarding per QoS flow established for a PDU Session. If "lossless handover" is required and the QoS flows to DRB mapping applied at the target NG-RAN node allows applying for data forwarding the same QoS flows to DRB mapping as applied at the source NG-RAN node for a DRB and if all QoS flows mapped to that DRB are accepted for data forwarding, the target NG-RAN node establishes a downlink forwarding tunnel for that DRB. For a DRB for which preservation of SN status applies, the target NG-RAN node may decide to establish an UL data forwarding tunnel. The target NG-RAN node may also decide to establish a downlink forwarding tunnel for each PDU session. In this case the target NG-RAN node provides information for which QoS flows data forwarding has been accepted and corresponding UP TNL information for data forwarding tunnels to be established between the source NG-RAN node and the target NG-RAN node. If QoS flows have been re-mapped at the source NG-RAN node and user packets along the old source mapping are still being processed at handover preparation, and if the source NG-RAN node has not yet received the SDAP end marker for certain QoS flows when providing the SN status to the target NG-RAN node, the source NG-RAN node provides the old side QoS mapping information for UL QoS flows to the target NG-RAN node for which no SDAP end marker was yet received. The target NG-RAN will receive for those QoS flows the end marker when the UE finalises to send UL user data according to the old source side mapping. The source NG-RAN node may also propose to establish uplink forwarding tunnels for some PDU sessions in order to transfer SDAP SDUs corresponding to QoS flows for which flow re-mapping happened before the handover and the SDAP end marker has not yet been received, and for which user data was received at the source NG-RAN node via the DRB to which the QoS flow was remapped. If accepted the target NG-RAN node shall provide the corresponding UP TNL information for data forwarding tunnels to be established between the source NG-RAN node and the target NG-RAN node. As long as data forwarding of DL user data packets takes place, the source NG-RAN node shall forward user data in the same forwarding tunnel, i.e. - for any QoS flow accepted for data forwarding by the target NG-RAN node and for which a DRB DL forwarding tunnel was established for a DRB to which this QoS flow was mapped at the source NG-RAN node, any fresh packets of this QoS flow shall be forwarded as PDCP SDUs via the mapped DRB DL forwarding tunnel. - for DRBs for which preservation of SN status applies, the source NG-RAN node may forward in order to the target NG-RAN node via the DRB DL forwarding tunnel all downlink PDCP SDUs with their SN corresponding to PDCP PDUs which have not been acknowledged by the UE. NOTE: The SN of forwarded PDCP SDUs is carried in the "PDCP PDU number" field of the GTP-U extension header. - for any QoS flow accepted for data forwarding by the target NG-RAN node for which a DL PDU session forwarding tunnel was established, the source NG-RAN node forwards SDAP SDUs as received on NG-U from the UPF. For handovers involving Full Configuration, the source NG-RAN node behaviour is unchanged from the description above. In case a DRB DL forwarding tunnel was established, the target NG-RAN node may identify the PDCP SDUs for which delivery was attempted by the source NG-RAN node, by the presence of the PDCP SN in the forwarded GTP-U packet and may discard them. As long as data forwarding of UL user data packets takes place for DRBs for which preservation of SN status applies the source NG-RAN node either: - discards the uplink PDCP PDUs received out of sequence if the source NG-RAN node has not accepted the request from the target NG-RAN node for uplink forwarding or if the target NG-RAN node has not requested uplink forwarding for the bearer during the Handover Preparation procedure; or - forwards to the target NG-RAN node via the corresponding DRB UL forwarding tunnel, the uplink PDCP SDUs with their SN corresponding to PDCP PDUs received out of sequence if the source NG-RAN node has accepted the request from the target NG-RAN node for uplink forwarding for the bearer during the Handover Preparation procedure, including PDCP SDUs corresponding to user data of those QoS flows, for which re-mapping happened for a QoS flow before the handover and the SDAP end marker has not yet been received at the source NG-RAN node. As long as data forwarding of UL user data packets takes place for a PDU session, the source NG-RAN node forwards via the corresponding PDU session UL forwarding tunnel, the uplink SDAP SDUs corresponding to QoS flows for which flow re-mapping happened before the handover and the SDAP end marker has not yet been received at the source NG-RAN node, and which were received at the source NG-RAN node via the DRB to which the QoS flow was remapped. For DRBs configured with DAPS handover, data forwarding after the source gNB receives the HANDOVER SUCCESS message from the target gNB follows the same behaviours as described above. For DRBs configured with DAPS handover, before the source gNB receives the HANDOVER SUCCESS message: - The source gNB may forward to the target gNB downlink PDCP SDUs with SNs assigned by the source gNB. No downlink PDCP SDU without a SN assigned or SDAP SDU is forwarded. No uplink PDCP SDU or SDAP SDU is forwarded. - The source gNB sends the EARLY STATUS TRANSFER message to maintain HFN continuity by indicating PDCP SN and HFN of the first PDCP SDU that the source gNB forwards to the target gNB. The subsequent messages may be sent for discarding of already forwarded downlink PDCP SDUs in the target gNB. - The source gNB does not stop transmitting downlink packets to the UE. The source gNB keeps forwarding to the 5GC the uplink SDAP SDUs successfully received in-sequence from the UE. Handling of end marker packets: - The source NG-RAN node receives one or several GTP-U end marker packets per PDU session from the UPF and replicates the end marker packets into each data forwarding tunnel when no more user data packets are to be forwarded over that tunnel. - End marker packets sent via a data forwarding tunnel are applicable to all QoS flows forwarded via that tunnel. After end marker packets have been received over a forwarding tunnel, the target NG-RAN node can start taking into account the packets of QoS flows associated with that forwarding tunnel received at the target NG-RAN node from the NG-U PDU session tunnel. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.3.2.3 |
1,315 | 5.5.2.2.2 Preparation phase | Figure 5.5.2.2.2-1: UTRAN Iu mode to E-UTRAN Inter RAT HO, preparation phase 1. The source RNC decides to initiate an Inter-RAT handover to the E-UTRAN. At this point both uplink and downlink user data is transmitted via the following: Bearers between UE and source RNC, GTP tunnel(s) between source RNC, source SGSN (only if Direct Tunnel is not used), Serving GW and PDN GW. NOTE 1: The process leading to the handover decision is outside of the scope of this specification. 2. The source RNC sends a Relocation Required (Cause, Target eNodeB Identifier, CSG ID, CSG access mode, Source RNC Identifier, Source RNC to Target RNC Transparent Container) message to the source SGSN to request the CN to establish resources in the target eNodeB, Target MME and the Serving GW. The bearers that will be subject to data forwarding (if any) are identified by the target MME in a later step (see step 7 below). When the target cell is a CSG cell or a hybrid cell, the source RNC shall include the CSG ID of the target cell. If the target cell is a hybrid cell, the CSG access mode shall be indicated. 3. The source SGSN determines from the 'Target eNodeB Identifier' IE that the type of handover is IRAT Handover to E-UTRAN. The source SGSN selects the target MME as described in clause 4.3.8.3 on "MME Selection Function". The Source SGSN initiates the Handover resource allocation procedure by sending Forward Relocation Request (IMSI, Target Identification, CSG ID, CSG Membership Indication, MM Context, PDN Connections, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control plane, Source to Target Transparent Container, RAN Cause, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, ISR Supported, Serving Network, Change to Report (if present)) message to the target MME. This message includes all EPS Bearer contexts corresponding to all the bearers established in the source system and the uplink Tunnel endpoint parameters of the Serving GW. If the information ISR Supported is indicated, this indicates that the source SGSN and associated Serving GW are capable to activate ISR for the UE. When ISR is activated the message should be sent to the MME that maintains ISR for the UE when this MME is serving the target identified by the Target Identification. RAN Cause indicates the Cause as received from source RNC. The Source to Target Transparent Container contains the value from the Source RNC to Target RNC Transparent Container received from the Source RNC. The old Serving Network is sent to target MME to support the target MME to resolve if Serving Network is changed. Change to Report flag is included by the source SGSN if reporting of change of UE Time Zone, or Serving Network, or both towards Serving GW / PDN GW was deferred by the source SGSN. The source SGSN shall perform access control by checking the UE's CSG subscription when CSG ID is provided by the source RNC. If there is no subscription data for this CSG ID or the CSG subscription is expired, and the target cell is a CSG cell, the source SGSN shall reject the handover with an appropriate cause unless the UE has emergency bearer services. The source SGSN includes the CSG ID in the Forward Relocation Request when the target cell is a CSG cell or hybrid cell. When the target cell is a hybrid cell, or if there are one or several emergency bearers and the target cell is a CSG cell, the CSG Membership Indication indicating whether the UE is a CSG member shall be included in the Forward Relocation Request message. This message includes all PDN Connections active in the source system and for each PDN Connection includes the associated APN, the address and the uplink tunnel endpoint parameters of the Serving GW for control plane, and a list of EPS Bearer Contexts. Prioritization of EPS Bearer Contexts is performed by the target core network node. The MM context contains security related information, e.g. UE Network capabilities and used UMTS integrity and ciphering algorithm(s) as well as keys, as described in clause 5.7.2 (Information Storage for MME). The target MME selects the NAS ciphering and integrity algorithms to use. These algorithms will be sent transparently from the target eNodeB to the UE in the Target to Source Transparent Container (EPC part). The MME establishes the EPS bearer(s) in the prioritized order. The MME deactivates, as provided in step 8 of the execution phase, the EPS bearers which cannot be established. The target MME shall determine the Maximum APN restriction based on the APN Restriction of each bearer context received in the Forward Relocation Request, and shall subsequently store the new Maximum APN restriction value. If SIPTO at the Local Network is active for a PDN connection in the architecture with stand-alone GW the source SGSN shall include the Local Home Network ID of the source cell in the PDN Connections corresponding to the SIPTO at the Local Network PDN connection. 4. The target MME determines if the Serving GW is to be relocated, e.g., due to PLMN change. If the Serving GW is to be relocated, the target MME selects the target Serving GW as described under clause 4.3.8.2 on "Serving GW selection function". The target MME sends a Create Session Request message (IMSI, MME Address and TEID, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, PDN GW address(es) for user plane, PDN GW UL TEID(s) for user plane, PDN GW address for control plane, and PDN GW TEID(s) for control plane, the Protocol Type over S5/S8, Serving Network) per PDN connection to the target Serving GW. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. 4a. The target Serving GW allocates its local resources and returns them in a Create Session Response (Serving GW address(es) for user plane, Serving GW UL TEID(s) for user plane, Serving GW Address for control plane, Serving GW TEID for control plane) message to the target MME. 5. The target MME requests the target eNodeB to establish the bearer(s) by sending the message Handover Request (UE Identifier, S1AP Cause, KeNB, allowed AS Integrity Protection and Ciphering algorithm(s), NAS Security Parameters to E-UTRAN, EPS Bearers to be setup list, CSG ID, CSG Membership Indication, Source to Target Transparent Container). The NAS Security Parameters to E-UTRAN includes the NAS Integrity Protection and Ciphering algorithm(s), eKSI and NONCEMME are targeted for the UE. S1AP Cause indicates the RAN Cause as received from source SGSN. The Source to Target Transparent Container contains the value from the RAN Transparent Container received from the source SGSN. NOTE 2: The target MME derives K'ASME from CK and IK in the MM context and associates it with eKSI, as described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41] and selects NAS Integrity Protection and Ciphering algorithm(s). The MME and UE derive the NAS keys and KeNB from K'ASME. If the MME shares an EPS security association with the UE, the MME may activate this native EPS security context by initiating a NAS SMC procedure after having completed the handover procedure. For each EPS bearer requested to be established, 'EPS Bearers To Be Setup' IE shall contain information such as ID, bearer parameters, Transport Layer Address, "Data forwarding not possible" indication, and S1 Transport Association. The target MME ignores any Activity Status Indicator within an EPS Bearer Context and requests the target eNodeB to allocate resources for all EPS Bearer Contexts received from the source side. The Transport Layer Address is the Serving GW Address for user data, and the S1 Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data. "Data forwarding not possible" indication shall be included if the target MME decides the corresponding bearer will not be subject to data forwarding. The target MME shall include the CSG ID and CSG Membership Indication when provided by the source SGSN in the Handover Request message. The information about the selected NAS ciphering and integrity protection algorithm(s), KSI and NONCEMME will be sent transparently from the target eNodeB to the UE in the Target to Source Transparent Container, and in the message UTRAN HO Command from source RNC to the UE. This will then allow data transfer to continue in the new RAT/mode target cell without requiring a new AKA (Authentication and Key Agreement) procedure. More details are described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]. If the target cell is a CSG cell, the target eNodeB shall verify the CSG ID provided by the target MME, and reject the handover with an appropriate cause if it does not match the CSG ID for the target cell. If the target eNodeB is in hybrid mode, it may use the CSG Membership Status to perform differentiated treatment for CSG and non-CSG members. If the target cell is a CSG cell, and if the CSG Membership Indication is "non member", the target eNodeB only accepts the emergency bearers. 5a. The target eNodeB allocates the requested resources and returns the applicable parameters to the target MME in the message Handover Request Acknowledge (Target to Source Transparent Container, EPS Bearers setup list, EPS Bearers failed to setup list). The target eNodeB shall ignore it if the number of radio bearers in the Source to Target Transparent container does not comply with the number of bearers requested by the MME and allocate bearers as requested by the MME. Upon sending the Handover Request Acknowledge message the target eNodeB shall be prepared to receive downlink GTP PDUs from the Serving GW for the accepted EPS bearers. The target eNodeB selects AS integrity and ciphering algorithm(s). In addition to the information provided by the MME (eKSI, NAS Integrity Protection and Ciphering algorithm(s) and NONCEMME), the target eNodeB inserts AS integrity and ciphering algorithm(s) into the UTRAN RRC message, which is contained in the Target to Source Transparent Container. 6. If 'Indirect Forwarding' and relocation of Serving GW apply the target MME sends a Create Indirect Data Forwarding Tunnel Request message (Target eNodeB Address, TEID(s) for DL data forwarding) to the Serving GW. Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE. 6a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and Serving GW DL TEID(s) for data forwarding) message to the target MME. 7. The target MME sends the message Forward Relocation Response (Cause, List of Set Up RABs, EPS Bearers setup list, MME Tunnel Endpoint Identifier for Control Plane, RAN Cause, MME Address for control plane, Target to Source Transparent Container, Address(es) and TEID(s) for Data Forwarding, Serving GW change indication) to the source SGSN. Serving GW change indication indicates whether a new Serving GW has been selected. The Target to Source Transparent Container includes the value from the Target to Source Transparent Container received from the target eNodeB. The IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' defines the destination tunnelling endpoint for data forwarding in target system, and it is set as follows. If 'Direct Forwarding' or if 'Indirect Forwarding' but no relocation of Serving GW applies, then the IEs 'Address(es) and TEID(s) for Data Forwarding' contains the forwarding DL GTP-U tunnel endpoint parameters to the eNodeB received in step 5a. If 'Indirect Forwarding' and relocation of Serving GW apply the IEs 'Address(es) and TEID(s) for Data Forwarding' contains the DL GTP-U tunnel endpoint parameters to the Target eNodeB or to the forwarding Serving GW received in step 6a. 8. If "Indirect Forwarding" applies, the source SGSN shall send the message Create Indirect Data Forwarding Tunnel Request (Address(es) and TEID(s) for Data Forwarding (received in step 7)) to the Serving GW used for indirect forwarding. Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE. 8a. The Serving GW returns the forwarding user plane parameters by sending the message Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for data forwarding). If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es) and TEID(s) will not be included in the message. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.2.2.2 |
1,316 | 6.6.2F.1 Spectrum emission mask | The spectrum emission mask of the category NB1 and NB2 UE applies to frequencies (ΔfOOB) starting from the edge of the assigned category NB1 or NB2 channel bandwidth. For frequencies greater than (ΔfOOB) as specified in Table 6.6.2F.1-1 the spurious requirements in subclause 6.6.3 are applicable. The power of any category NB1 or NB2 UE emission shall not exceed the levels specified in Table 6.6.2F.1-1. The spectrum emission limit between each ΔfOOB is linearly interpolated. Table 6.6.2F.1-1: category NB1 and NB2 UE spectrum emission mask In addition to the spectrum emission mask requirement in Table 6.6.2F.1-1 a category NB1 or NB2 UE shall also meet the applicable E-UTRA spectrum emission mask requirement in sub-clause 6.6.2. E-UTRA spectrum emission requirement applies for frequencies that are Foffset away from edge of NB1 or NB2 channel edge as defined in Table 6.6.2F.1-2. Table 6.6.2F.1-2: Foffset for category NB1 and NB2 UE spectrum emission mask Note: Foffset in Table 6.6.2F.1-2 is used to guarantee co-existence for guard-band operation. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2F.1 |
1,317 | – RRCRelease | The RRCRelease message is used to command the release of an RRC connection or the suspension of the RRC connection. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE RRCRelease message -- ASN1START -- TAG-RRCRELEASE-START RRCRelease ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcRelease RRCRelease-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCRelease-IEs ::= SEQUENCE { redirectedCarrierInfo RedirectedCarrierInfo OPTIONAL, -- Need N cellReselectionPriorities CellReselectionPriorities OPTIONAL, -- Need R suspendConfig SuspendConfig OPTIONAL, -- Need R deprioritisationReq SEQUENCE { deprioritisationType ENUMERATED {frequency, nr}, deprioritisationTimer ENUMERATED {min5, min10, min15, min30} } OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCRelease-v1540-IEs OPTIONAL } RRCRelease-v1540-IEs ::= SEQUENCE { waitTime RejectWaitTime OPTIONAL, -- Need N nonCriticalExtension RRCRelease-v1610-IEs OPTIONAL } RRCRelease-v1610-IEs ::= SEQUENCE { voiceFallbackIndication-r16 ENUMERATED {true} OPTIONAL, -- Need N measIdleConfig-r16 SetupRelease {MeasIdleConfigDedicated-r16} OPTIONAL, -- Need M nonCriticalExtension RRCRelease-v1650-IEs OPTIONAL } RRCRelease-v1650-IEs ::= SEQUENCE { mpsPriorityIndication-r16 ENUMERATED {true} OPTIONAL, -- Cond Redirection2 nonCriticalExtension RRCRelease-v1710-IEs OPTIONAL } RRCRelease-v1710-IEs ::= SEQUENCE { noLastCellUpdate-r17 ENUMERATED {true} OPTIONAL, -- Need S nonCriticalExtension SEQUENCE {} OPTIONAL } RedirectedCarrierInfo ::= CHOICE { nr CarrierInfoNR, eutra RedirectedCarrierInfo-EUTRA, ... } RedirectedCarrierInfo-EUTRA ::= SEQUENCE { eutraFrequency ARFCN-ValueEUTRA, cnType ENUMERATED {epc,fiveGC} OPTIONAL -- Need N } CarrierInfoNR ::= SEQUENCE { carrierFreq ARFCN-ValueNR, ssbSubcarrierSpacing SubcarrierSpacing, smtc SSB-MTC OPTIONAL, -- Need S ... } SuspendConfig ::= SEQUENCE { fullI-RNTI I-RNTI-Value, shortI-RNTI ShortI-RNTI-Value, ran-PagingCycle PagingCycle, ran-NotificationAreaInfo RAN-NotificationAreaInfo OPTIONAL, -- Need M t380 PeriodicRNAU-TimerValue OPTIONAL, -- Need R nextHopChainingCount NextHopChainingCount, ..., [[ sl-UEIdentityRemote-r17 RNTI-Value OPTIONAL, -- Cond L2RemoteUE sdt-Config-r17 SetupRelease { SDT-Config-r17 } OPTIONAL, -- Need M srs-PosRRC-Inactive-r17 SetupRelease { SRS-PosRRC-Inactive-r17 } OPTIONAL, -- Need M ran-ExtendedPagingCycle-r17 ExtendedPagingCycle-r17 OPTIONAL -- Cond RANPaging ]], [[ ncd-SSB-RedCapInitialBWP-SDT-r17 SetupRelease {NonCellDefiningSSB-r17} OPTIONAL -- Need M ]], [[ resumeIndication-r18 ENUMERATED {true} OPTIONAL, -- Need N srs-PosRRC-Inactive-v1800 SetupRelease { SRS-PosRRC-Inactive-v1800 } OPTIONAL, -- Need M srs-PosRRC-InactiveValidityAreaConfigList-r18 SetupRelease { SRS-PosRRC-InactiveValidityAreaConfigList-r18 } OPTIONAL, -- Need M ran-ExtendedPagingCycle-r18 ExtendedPagingCycle-Config-r18 OPTIONAL, -- Cond RANPaging multicastConfigInactive-r18 SetupRelease { MulticastConfigInactive-r18 } OPTIONAL -- Need M ]] } PeriodicRNAU-TimerValue ::= ENUMERATED { min5, min10, min20, min30, min60, min120, min360, min720} CellReselectionPriorities ::= SEQUENCE { freqPriorityListEUTRA FreqPriorityListEUTRA OPTIONAL, -- Need M freqPriorityListNR FreqPriorityListNR OPTIONAL, -- Need M t320 ENUMERATED {min5, min10, min20, min30, min60, min120, min180, spare1} OPTIONAL, -- Need R ..., [[ freqPriorityListDedicatedSlicing-r17 FreqPriorityListDedicatedSlicing-r17 OPTIONAL -- Need M ]] } PagingCycle ::= ENUMERATED {rf32, rf64, rf128, rf256} FreqPriorityListEUTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityEUTRA FreqPriorityListNR ::= SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityNR FreqPriorityEUTRA ::= SEQUENCE { carrierFreq ARFCN-ValueEUTRA, cellReselectionPriority CellReselectionPriority, cellReselectionSubPriority CellReselectionSubPriority OPTIONAL -- Need R } FreqPriorityNR ::= SEQUENCE { carrierFreq ARFCN-ValueNR, cellReselectionPriority CellReselectionPriority, cellReselectionSubPriority CellReselectionSubPriority OPTIONAL -- Need R } RAN-NotificationAreaInfo ::= CHOICE { cellList PLMN-RAN-AreaCellList, ran-AreaConfigList PLMN-RAN-AreaConfigList, ... } PLMN-RAN-AreaCellList ::= SEQUENCE (SIZE (1.. maxPLMNIdentities)) OF PLMN-RAN-AreaCell PLMN-RAN-AreaCell ::= SEQUENCE { plmn-Identity PLMN-Identity OPTIONAL, -- Need S ran-AreaCells SEQUENCE (SIZE (1..32)) OF CellIdentity } PLMN-RAN-AreaConfigList ::= SEQUENCE (SIZE (1..maxPLMNIdentities)) OF PLMN-RAN-AreaConfig PLMN-RAN-AreaConfig ::= SEQUENCE { plmn-Identity PLMN-Identity OPTIONAL, -- Need S ran-Area SEQUENCE (SIZE (1..16)) OF RAN-AreaConfig } RAN-AreaConfig ::= SEQUENCE { trackingAreaCode TrackingAreaCode, ran-AreaCodeList SEQUENCE (SIZE (1..32)) OF RAN-AreaCode OPTIONAL -- Need R } SDT-Config-r17 ::= SEQUENCE { sdt-DRB-List-r17 SEQUENCE (SIZE (0..maxDRB)) OF DRB-Identity OPTIONAL, -- Need M sdt-SRB2-Indication-r17 ENUMERATED {allowed} OPTIONAL, -- Need R sdt-MAC-PHY-CG-Config-r17 SetupRelease {SDT-CG-Config-r17} OPTIONAL, -- Need M sdt-DRB-ContinueROHC-r17 ENUMERATED { cell, rna } OPTIONAL -- Need S } SDT-CG-Config-r17 ::= OCTET STRING (CONTAINING SDT-MAC-PHY-CG-Config-r17) SDT-MAC-PHY-CG-Config-r17 ::= SEQUENCE { -- CG-SDT specific configuration cg-SDT-ConfigLCH-RestrictionToAddModList-r17 SEQUENCE (SIZE(1..maxLC-ID)) OF CG-SDT-ConfigLCH-Restriction-r17 OPTIONAL, -- Need N cg-SDT-ConfigLCH-RestrictionToReleaseList-r17 SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity OPTIONAL, -- Need N cg-SDT-ConfigInitialBWP-NUL-r17 SetupRelease {BWP-UplinkDedicatedSDT-r17} OPTIONAL, -- Need M cg-SDT-ConfigInitialBWP-SUL-r17 SetupRelease {BWP-UplinkDedicatedSDT-r17} OPTIONAL, -- Need M cg-SDT-ConfigInitialBWP-DL-r17 BWP-DownlinkDedicatedSDT-r17 OPTIONAL, -- Need M cg-SDT-TimeAlignmentTimer-r17 TimeAlignmentTimer OPTIONAL, -- Need M cg-SDT-RSRP-ThresholdSSB-r17 RSRP-Range OPTIONAL, -- Need M cg-SDT-TA-ValidationConfig-r17 SetupRelease { CG-SDT-TA-ValidationConfig-r17 } OPTIONAL, -- Need M cg-SDT-CS-RNTI-r17 RNTI-Value OPTIONAL, -- Need M ..., [[ cg-SDT-ConfigLCH-RestrictionToAddModListExt-v1800 SEQUENCE (SIZE(1..maxLC-ID)) OF CG-SDT-ConfigLCH-Restriction-v1800 OPTIONAL, -- Need N cg-MT-SDT-MaxDurationToNext-CG-Occasion-r18 ENUMERATED { ms10, ms100, sec1, sec10, sec60, sec100, sec300, sec600, sec1200, sec1800, sec3600, spare5, spare4, spare3, spare2, spare1} OPTIONAL -- Need R ]] } CG-SDT-TA-ValidationConfig-r17 ::= SEQUENCE { cg-SDT-RSRP-ChangeThreshold-r17 ENUMERATED { dB2, dB4, dB6, dB8, dB10, dB14, dB18, dB22, dB26, dB30, dB34, spare5, spare4, spare3, spare2, spare1} } BWP-DownlinkDedicatedSDT-r17 ::= SEQUENCE { pdcch-Config-r17 SetupRelease { PDCCH-Config } OPTIONAL, -- Need M pdsch-Config-r17 SetupRelease { PDSCH-Config } OPTIONAL, -- Need M ... } BWP-UplinkDedicatedSDT-r17 ::= SEQUENCE { pusch-Config-r17 SetupRelease { PUSCH-Config } OPTIONAL, -- Need M configuredGrantConfigToAddModList-r17 ConfiguredGrantConfigToAddModList-r16 OPTIONAL, -- Need N configuredGrantConfigToReleaseList-r17 ConfiguredGrantConfigToReleaseList-r16 OPTIONAL, -- Need N ... } CG-SDT-ConfigLCH-Restriction-r17 ::= SEQUENCE { logicalChannelIdentity-r17 LogicalChannelIdentity, configuredGrantType1Allowed-r17 ENUMERATED {true} OPTIONAL, -- Need R allowedCG-List-r17 SEQUENCE (SIZE (0.. maxNrofConfiguredGrantConfigMAC-1-r16)) OF ConfiguredGrantConfigIndexMAC-r16 OPTIONAL -- Need R } CG-SDT-ConfigLCH-Restriction-v1800 ::= SEQUENCE { cg-SDT-MaxDurationToNext-CG-Occasion-r18 ENUMERATED { ms10, ms100, sec1, sec10, sec60, sec100, sec300, sec600, sec1200, sec1800, sec3600, spare5, spare4, spare3, spare2, spare1} OPTIONAL -- Need R } SRS-PosRRC-Inactive-r17 ::= OCTET STRING (CONTAINING SRS-PosRRC-InactiveConfig-r17) SRS-PosRRC-InactiveConfig-r17 ::= SEQUENCE { srs-PosConfigNUL-r17 SRS-PosConfig-r17 OPTIONAL, -- Need R srs-PosConfigSUL-r17 SRS-PosConfig-r17 OPTIONAL, -- Need R bwp-NUL-r17 BWP OPTIONAL, -- Need S bwp-SUL-r17 BWP OPTIONAL, -- Need S inactivePosSRS-TimeAlignmentTimer-r17 TimeAlignmentTimer OPTIONAL, -- Need M inactivePosSRS-RSRP-ChangeThreshold-r17 RSRP-ChangeThreshold-r17 OPTIONAL -- Need M } RSRP-ChangeThreshold-r17 ::= ENUMERATED {dB4, dB6, dB8, dB10, dB14, dB18, dB22, dB26, dB30, dB34, spare6, spare5, spare4, spare3, spare2, spare1} SRS-PosConfig-r17 ::= SEQUENCE { srs-PosResourceSetToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16 OPTIONAL,-- Need N srs-PosResourceSetToAddModList-r17 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSet-r16 OPTIONAL,-- Need N srs-PosResourceToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResourceId-r16 OPTIONAL,-- Need N srs-PosResourceToAddModList-r17 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResource-r16 OPTIONAL -- Need N } SRS-PosRRC-Inactive-v1800 ::= SEQUENCE { srs-PosRRC-AggBW-InactiveConfigList-r18 SetupRelease { SRS-PosRRC-AggBW-InactiveConfigList-r18 } OPTIONAL, -- Need M srs-PosResSetLinkedForAggBWInactiveList-r18 SetupRelease { SRS-PosResSetLinkedForAggBWInactiveList-r18 } OPTIONAL, -- Need M srs-PosTx-Hopping-r18 SetupRelease { SRS-PosTx-Hopping-r18 } OPTIONAL, -- Need M ... } SRS-PosRRC-InactiveValidityAreaConfigList-r18 ::= SEQUENCE SIZE(1..maxNrOfVA-r18) OF SRS-PosRRC-InactiveValidityAreaConfig-r18 SRS-PosRRC-InactiveValidityAreaConfig-r18 ::= SEQUENCE { configType-r18 ENUMERATED {preconfig, non-preconfig}, srs-PosConfigValidityArea-r18 SEQUENCE (SIZE(1..maxNrOfCellsInVA-r18)) OF CellIdentity, srs-PosConfigNUL-r18 SRS-PosConfig-r17 OPTIONAL, -- Need R srs-PosConfigSUL-r18 SRS-PosConfig-r17 OPTIONAL, -- Need R bwp-NUL-r18 BWP OPTIONAL, -- Need S bwp-SUL-r18 BWP OPTIONAL, -- Need S areaValidityTA-Config-r18 SetupRelease { AreaValidityTA-Config-r18 } OPTIONAL, -- Need M srs-PosRRC-AggBW-InactiveConfigList-r18 SetupRelease { SRS-PosRRC-AggBW-InactiveConfigList-r18 } OPTIONAL, -- Need M srs-PosResSetLinkedForAggBWInactiveList-r18 SetupRelease { SRS-PosResSetLinkedForAggBWInactiveList-r18 } OPTIONAL, -- Need M srs-PosHyperSFN-Index-r18 ENUMERATED {even0, odd1} OPTIONAL, --Need S ... } AreaValidityTA-Config-r18 ::= SEQUENCE { inactivePosSRS-ValidityAreaTAT-r18 ENUMERATED {ms1280, ms1920, ms2560, ms5120, ms10240, ms20480, ms40960, infinity}, inactivePosSRS-ValidityAreaRSRP-r18 RSRP-ChangeThreshold-r17 OPTIONAL, -- Need M autonomousTA-AdjustmentEnabled-r18 ENUMERATED {true} OPTIONAL -- Need M } -- Editor's Note: FFS on configType timer value and on optional need codes for area Validity TA Config SRS-PosResSetLinkedForAggBWInactiveList-r18 ::= SEQUENCE (SIZE(1..maxNrOfLinkedSRS-PosResourceSet-r18)) OF SRS-PosResourceSetLinkedForAggBW-r18 SRS-PosRRC-AggBW-InactiveConfigList-r18 ::= SEQUENCE (SIZE (2..3)) OF SRS-PosRRC-AggBW-InactiveConfig-r18 SRS-PosRRC-AggBW-InactiveConfig-r18 ::= SEQUENCE { srs-PosConfig-r18 SRS-PosConfig-r17, freqInfoAdditionalCcList-r18 ARFCN-ValueNR } ExtendedPagingCycle-r17 ::= ENUMERATED {rf256, rf512, rf1024, spare1} ExtendedPagingCycle-Config-r18 ::= SEQUENCE { extendedPagingCycle-r18 ENUMERATED {hf2, hf4, hf8, hf16, hf32, hf64, hf128,hf256, hf512, hf1024, spare6, spare5, spare4, spare3, spare2, spare1}, pagingPTWLength-r18 ENUMERATED {ms1280, ms2560, ms3840, ms5120, ms6400, ms7680, ms8960, ms10240, ms11520, ms12800, ms14080, ms15360, ms16640, ms17920, ms19200, ms20480, ms21760, ms23040, ms24320, ms25600, ms26880, ms28160, ms29440, ms30720, ms32000, ms33280, ms34560, ms35840, ms37120, ms38400, ms39680, ms40960} } MulticastConfigInactive-r18::= SEQUENCE { inactivePTM-Config-r18 OCTET STRING (CONTAINING MBSMulticastConfiguration-r18) OPTIONAL, -- Need N inactiveMCCH-Config-r18 OCTET STRING (CONTAINING SystemInformation) OPTIONAL -- Need N } -- TAG-RRCRELEASE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,318 | 4.4.2 Control Plane | The figure below shows the protocol stack for the control plane, where: - PDCP, RLC and MAC sublayers (terminated in gNB on the network side) perform the functions listed in clause 6; - RRC (terminated in gNB on the network side) performs the functions listed in clause 7; - NAS control protocol (terminated in AMF on the network side) performs the functions listed in TS 23.501[ System architecture for the 5G System (5GS) ] [3]), for instance: authentication, mobility management, security control… Figure 4.4.2-1: Control Plane Protocol Stack | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.4.2 |
1,319 | 4.2.1.6 Number of additional E-RABs failed to setup | a) This measurement provides the number of additional E-RABs failed to setup. The measurement is split into subcounters per failure cause. b) CC. c) On transmission by the eNodeB/RN of an E-RAB SETUP RESPONSE message, each E-RAB failed to establish is added to the relevant measurement per cause, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of additional E-RABs failed to setup. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB. EstabAddFailNbr.Cause where Cause identifies the cause resulting in the additional E-RAB setup failure. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic. h) EPS. i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.1.6 |
1,320 | 8.18.2 CG based SDT | The procedure for CG based small data transmission in RRC Inactive is shown in Figure 8.18.2-1. Figure 8.18.2-1: CG based Small Data Transmission in RRC Inactive state. 1. The gNB-CU decides to move UE into RRC_INACTIVE state. 2. The gNB-CU-CP decides to configure CG-SDT, it sends UE CONTEXT MODIFICATION REQUEST message including a query indication for CG-SDT related resource configuration associated with the information of SDT Radio Bearer(s). 3. The gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message including the CG-SDT related resource configurations for the requested SDT Radio Bearer(s) within the DU to CU RRC Information IE. 4. The gNB-CU-CP sends the BEARER CONTEXT MODIFICATION REQUEST towards the gNB-CU-UP, with the suspend indication. 5. The gNB-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE towards the gNB-CU-CP. 6. The gNB-CU-CP sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU including an RRCRelease message to the UE with the CG-SDT information within suspend configuration. The gNB-CU notifies the gNB-DU to keep the SDT RLC config, F1-U tunnels, F1AP UE association, and store the CG resource for SDT when the UE is entering RRC_INACTIVE state with an explicit CG-SDT kept indicator. 7. The gNB-DU sends the RRCRelease message to UE. 8. The gNB-DU sends UE CONTEXT RELEASE COMPLETE message. The gNB-DU keeps the SDT RLC config, F1-U tunnels, F1AP UE association, and stores the CG resource for SDT when the UE entering RRC_INACTIVE. The gNB-DU also stores the C-RNTI, CS-RNTI, and which bearers are CG-SDT bearers. After a period of time of the UE being in RRC_INACTIVE state. 9. The UE decides to perform CG based SDT procedure, it sends the RRCResumeRequest message together with UL SDT data/UL NAS PDU. 10. The gNB-DU sends the UL RRC MESSAGE TRANSFER message including the RRCResumeRequest message to indicate the access due to CG-SDT. 11/12. If UE context is successfully retrieved as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2], the gNB-CU-CP initiates the BEARER CONTEXT MODIFICATION procedure to resume SDT DRBs. 13 – 13a. The gNB-DU sends the UL SDT data, if any, to the gNB-CU-UP, and/or sends the UL signalling, if any, to the gNB-CU-CP via the UL RRC MESSAGE TRANSFER message, in which any UL NAS PDU is delivered to AMF. NOTE 1: void. Upon receiving the UE INACTIVITY NOTIFICATION message without SDT volume threshold crossed indication from the gNB-DU and deciding to terminate the ongoing SDT procedure, the gNB-CU shall transmit the UE CONTEXT RELEASE COMMAND message to the gNB-DU. NOTE 2: Upon receiving BSR from the UE, in case that UL SDT data size in the BSR is larger than the threshold configured from the gNB-CU-CP, the gNB-DU sends the UE INACTIVITY NOTIFICATION message with the SDT volume threshold crossed indication to the gNB-CU-CP. Upon receiving such indication, the gNB-CU-CP may terminate the ongoing SDT procedure, by sending the RRCResume message to move the UE to RRC_CONNECTED, or by sending the RRCRelease message to move the UE to RRC_INACTIVE. If CG-SDT is re-configured, the gNB-CU may request the gNB-DU to keep CG-SDT configuration and resources in the UE CONTEXT RELEASE COMMAND message. Upon receiving non-SDT data, the gNB-CU-UP shall send the DL DATA NOTIFICATION message to the gNB-CU-CP. The gNB-CU-CP shall terminate the ongoing SDT procedure as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. If the amount of the received DL SDT data is above the data size threshold configured by the gNB-CU-CP, the gNB-CU-UP shall send the DL DATA NOTIFICATION message with the SDT data size threshold crossed indication. The gNB-CU-CP may terminate the ongoing SDT procedure. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.18.2 |
1,321 | 4.17.6 SMF Provisioning of available UPFs using the NRF 4.17.6.1 General | This clause describes the provisioning of available UPFs in SMF using the NRF as documented in clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. This optional node-level step takes place prior to selecting the UPF for PDU Sessions and may be followed by N4 Node Level procedures defined in clause 4.4.3 where the UPF and the SMF exchange information such as the support of optional functionalities and capabilities. As an option, UPF(s) may register in the NRF. This registration phase uses the Nnrf_NFManagement_NFRegister operation and hence does not use N4. For the purpose of SMF provisioning of available UPFs, the SMF uses the Nnrf_NFManagement_NFStatusSubscribe, Nnrf_NFManagement_NFStatusNotify and Nnrf_NFDiscovery services to learn about available UPFs. NOTE 1: The protocol used by UPF to interact with NRF is described in TS 29.510[ 5G System; Network function repository services; Stage 3 ] [37] UPFs may be associated with UPF Provisioning Information in the NRF. The UPF Provisioning Information consists of: - a list of (S-NSSAI, DNN); - UE IPv4 Address Ranges and/or IPv6 Prefix Range(s) per (S-NSSAI, DNN); and NOTE 2: The above information can be used by the SMF for UPF selection when static IP address/prefix allocation is required for a UE. - a SMF Area Identity the UPF can serve. The SMF Area Identity allows limiting the SMF provisioning of UPF(s) using NRF to those UPF(s) associated with a certain SMF Area Identity. This can e.g. be used if an SMF is only allowed to control UPF(s) configured in NRF as belonging to a certain SMF Area Identity. - the supported ATSSS steering functionality, i.e. whether MPTCP functionality or ATSSS-LL functionality or MPQUIC functionality, or any combination of them is supported. - the supported UPF event exposure service and supported Event IDs, e.g. local notification of QoS Monitoring to AF or e.g. events for data collection to NWDAF by Nupf_EventExposure_Notify. The SMF Area Identity and UE IPv4 Address Ranges and/or IPv6 Prefix Range(s) are optional in the UPF Provisioning Information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.6 |
1,322 | 5.43.4 Reporting of satellite backhaul to SMF | If the AMF is aware that a satellite backhaul is used towards 5G AN, the AMF may report this to SMF as part of the PDU Session establishment procedure as described in clause 4.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If AMF is aware that satellite backhaul category changes (e.g. at handover), the AMF reports the current satellite backhaul category and indicates the satellite backhaul category change to SMF. Satellite backhaul category refers to the type of the satellite (i.e. GEO, MEO, LEO or OTHERSAT, DYNAMIC_GEO, DYNAMIC _MEO, DYNAMIC _LEO, DYNAMIC _OTHERSAT) used in the backhaul as specified in clause 5.4.3.39 of TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [183]. Only a single backhaul category can be indicated. If dynamic satellite backhaul is used by the NG-RAN, i.e. capabilities (latency and/or bandwidth) of the satellite backhaul change over time due to e.g. use of varying inter-satellite links as part of backhaul, the AMF notifies the SMF of the corresponding dynamic satellite backhaul category to serve the PDU Session and the SMF can notify it to other NFs as described in clause 5.2.8.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE: It is assumed that the AMF can determine the Satellite backhaul category for the notification to the SMF based on local configuration, e.g. based on Global RAN Node IDs associated with satellite backhaul. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.43.4 |
1,323 | – DL-DCCH-Message | The DL-DCCH-Message class is the set of RRC messages that may be sent from the network to the UE on the downlink DCCH logical channel. -- ASN1START -- TAG-DL-DCCH-MESSAGE-START DL-DCCH-Message ::= SEQUENCE { message DL-DCCH-MessageType } DL-DCCH-MessageType ::= CHOICE { c1 CHOICE { rrcReconfiguration RRCReconfiguration, rrcResume RRCResume, rrcRelease RRCRelease, rrcReestablishment RRCReestablishment, securityModeCommand SecurityModeCommand, dlInformationTransfer DLInformationTransfer, ueCapabilityEnquiry UECapabilityEnquiry, counterCheck CounterCheck, mobilityFromNRCommand MobilityFromNRCommand, dlDedicatedMessageSegment-r16 DLDedicatedMessageSegment-r16, ueInformationRequest-r16 UEInformationRequest-r16, dlInformationTransferMRDC-r16 DLInformationTransferMRDC-r16, loggedMeasurementConfiguration-r16 LoggedMeasurementConfiguration-r16, spare3 NULL, spare2 NULL, spare1 NULL }, messageClassExtension SEQUENCE {} } -- TAG-DL-DCCH-MESSAGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,324 | 9.5.6 Activate Secondary PDP Context Reject | This message is sent by the network to the MS to reject activation of an additional PDP context associated with the same PDP address and APN as an already active PDP context. See Table 9.5.6/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: activate SECONDARY PDP context reject Significance: global Direction: network to MS Table 9.5.6/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Activate SECONDARY PDP context reject message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.5.6 |
1,325 | B.1 Causes related to nature of request | Cause #8 – Operator Determined Barring This 5GSM cause is used by the network to indicate that the requested service was rejected by the SMF due to Operator Determined Barring. Cause #26 – Insufficient resources This 5GSM cause is used by the UE or by the network to indicate that the requested service cannot be provided due to insufficient resources. Cause #27 – Missing or unknown DNN This 5GSM cause is used by the network to indicate that the requested service was rejected by the external DN because the DNN was not included although required or if the DNN could not be resolved. Cause #28 – Unknown PDU session type This 5GSM cause is used by the network to indicate that the requested service was rejected by the external DN because the requested PDU session type could not be recognised or is not allowed. Cause #29 – User authentication or authorization failed This 5GSM cause is used by the network to indicate that the requested service was rejected by the external DN due to a failed user authentication, revoked by the external DN, or rejected by 5GCN due to a failed user authentication or authorization. Cause #31 – Request rejected, unspecified This 5GSM cause is used by the network or by the UE to indicate that the requested service or operation or the request for a resource was rejected due to unspecified reasons. Cause #32 – Service option not supported This 5GSM cause is used by the network when the UE requests a service which is not supported by the PLMN. Cause #33 – Requested service option not subscribed This 5GSM cause is sent when the UE requests a service option for which it has no subscription. Cause #35 – PTI already in use This 5GSM cause is used by the network to indicate that the PTI included by the UE is already in use by another active UE requested procedure for this UE. Cause #36 – Regular deactivation This 5GSM cause is used to indicate a regular UE or network initiated release of PDU session resources. Cause #37 – 5GS QoS not accepted This 5GSM cause is used by the network if the new 5GS QoS that was indicated in the UE request cannot be accepted. Cause #38 – Network failure This 5GSM cause is used by the network to indicate that the requested service was rejected due to an error situation in the network. Cause #39 – Reactivation requested This 5GSM cause is used by the network to request a PDU session reactivation. Cause #41 – Semantic error in the TFT operation This 5GSM cause is used by the UE to indicate a semantic error in the TFT operation included in the request. Cause #42 – Syntactical error in the TFT operation This 5GSM cause is used by the UE to indicate a syntactical error in the TFT operation included in the request. Cause #43 – Invalid PDU session identity This 5GSM cause is used by the network or the UE to indicate that the PDU session identity value provided to it is not a valid value or the PDU session identified by the PDU session identity IE in the request or the command is not active. Cause #44 – Semantic errors in packet filter(s) This 5GSM cause is used by the network or the UE to indicate that the requested service was rejected due to one or more semantic errors in packet filter(s) of the QoS rule included in the request. Cause #45 – Syntactical error in packet filter(s) This 5GSM cause is used by the network or the UE to indicate that the requested service was rejected due to one or more syntactical errors in packet filter(s) of the QoS rule included in the request. Cause #46 – Out of LADN service area This 5GSM cause is used by the network to indicate the UE is out of the LADN service area. Cause #47 – PTI mismatch This 5GSM cause is used by the network or UE to indicate that the PTI provided to it does not match any PTI in use. Cause #50 – PDU session type IPv4 only allowed This 5GSM cause is used by the network to indicate that only PDU session type IPv4 is allowed for the requested IP connectivity. Cause #51 – PDU session type IPv6 only allowed This 5GSM cause is used by the network to indicate that only PDU session type IPv6 is allowed for the requested IP connectivity. Cause #54 – PDU session does not exist This 5GSM cause is used by the network at handover of a PDU session between non-3GPP access and 3GPP access, or at interworking of a PDN connection from non-3GPP access network connected to EPC or from E-UTRAN connected to EPC to a PDU session, to indicate that the network does not have any information about the requested PDU session. Cause #57 – PDU session type IPv4v6 only allowed This 5GSM cause is used by the network to indicate that only PDU session types IPv4, IPv6 or IPv4v6 are allowed for the requested IP connectivity. Cause #58 – PDU session type Unstructured only allowed This 5GSM cause is used by the network to indicate that only PDU session type Unstructured is allowed for the requested DN connectivity. Cause #59 – Unsupported 5QI value This 5GSM cause is used by the network if the 5QI indicated in the UE request cannot be supported. Cause #61 – PDU session type Ethernet only allowed This 5GSM cause is used by the network to indicate that only PDU session type Ethernet is allowed for the requested DN connectivity. Cause #67 – Insufficient resources for specific slice and DNN This 5GSM cause is by the network to indicate that the requested service cannot be provided due to insufficient resources for specific slice and DNN or maximum group data rate on a 5G VN group identified by a specific slice and DNN has been exceeded. Cause #68 – Not supported SSC mode This 5GSM cause is used by the network to indicate that the requested SSC mode is not supported. Cause #69 – Insufficient resources for specific slice This 5GSM cause is used by the network to indicate that the requested service cannot be provided due to insufficient resources for specific slice, maximum number of PDU sessions on a specific slice has been already reached, data rate on a specific slice has been exceeded, or UE-Slice-MBR has been exceeded. Cause #70 – Missing or unknown DNN in a slice This 5GSM cause is used by the network to indicate that the requested service was rejected by the external DN because the DNN was not included although required or if the DNN could not be resolved, in the slice. Cause #81 – Invalid PTI value This 5GSM cause is used by the network or UE to indicate that the PTI provided to it is invalid for the specific 5GSM message. Cause #82 – Maximum data rate per UE for user-plane integrity protection is too low This 5GSM cause is used by the network to indicate that the requested service cannot be provided because the maximum data rate per UE for user-plane integrity protection is too low. Cause #83 – Semantic error in the QoS operation This 5GSM cause is used by the network or the UE to indicate that the requested service was rejected due to a semantic error in the QoS operation included in the request. Cause #84 – Syntactical error in the QoS operation This 5GSM cause is used by the network or the UE to indicate that the requested service was rejected due to a syntactical error in the QoS operation included in the request. Cause #85 – Invalid mapped EPS bearer identity This 5GSM cause is used by the network or the UE to indicate that the mapped EPS bearer identity value provided to it is not a valid value or the mapped EPS bearer identified by the mapped EPS bearer identity does not exist. Cause #86 – UAS services not allowed This 5GSM cause is used by the network to indicate that the requested UAS services are not allowed. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | B.1 |
1,326 | 6.3.4 Abnormal cases in the network | The following abnormal case can be identified: a) Lower layer indication of non-delivered NAS PDU due to handover Unless the procedure descriptions in clause 6.4, 6.5 or 6.6 specify a different behaviour, the following applies: If the downlink ESM NAS message could not be delivered due to an intra MME handover and the target TA is included in the TAI list, then upon successful completion of the intra MME handover the MME shall retransmit the ESM message. If a failure of the handover procedure is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the downlink ESM NAS message. b) Lower layer indication of non-delivered NAS PDU due to inter-eNodeB connected mode mobility when the transport of user data via the control plane is used If the downlink ESM NAS message could not be delivered due to inter-eNodeB connected mode mobility and the MME is not changed, then upon successful completion of inter-eNodeB connected mode mobility the MME shall retransmit the ESM message. If a failure of inter-eNodeB connected mode mobility is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the downlink ESM NAS message. NOTE: If the downlink ESM NAS message could not be delivered due to inter-eNodeB connected mode mobility and the MME is changed, the retransmission of downlink ESM NAS message is not supported. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.4 |
1,327 | 5.6.4.2 Usage of an UL Classifier for a PDU Session | In the case of PDU Sessions of type IPv4 or IPv6 or IPv4v6 or Ethernet, the SMF may decide to insert in the data path of a PDU Session an "UL CL" (Uplink classifier). The UL CL is a functionality supported by an UPF that aims at diverting (locally) some traffic matching traffic filters provided by the SMF. The insertion and removal of an UL CL is decided by the SMF and controlled by the SMF using generic N4 and UPF capabilities. The SMF may decide to insert in the data path of a PDU Session a UPF supporting the UL CL functionality during or after the PDU Session Establishment, or to remove from the data path of a PDU Session a UPF supporting the UL CL functionality after the PDU Session Establishment. The SMF may include more than one UPF supporting the UL CL functionality in the data path of a PDU Session. The UE is unaware of the traffic diversion by the UL CL, and does not involve in both the insertion and the removal of UL CL. In the case of a PDU Session of IPv4 or IPv6 or IPv4v6 type, the UE associates the PDU Session with either a single IPv4 address or a single IPv6 Prefix or both of them allocated by the network. When an UL CL functionality has been inserted in the data path of a PDU Session, there are multiple PDU Session Anchors for this PDU Session. These PDU Session Anchors provide different access to the same DN. In the case of a PDU Session of IPv4 or IPv6 or IPv4v6 type, only one IPv4 address and/or IPv6 prefix is provided to the UE. The SMF may be configured with local policies for some (DNN, S-NSSAI) combinations to release the PDU Session when there is a PSA associated with the IPv4 address allocated to the UE and this PSA has been removed. NOTE 0: The use of only one IPv4 address and/or IPv6 prefix with multiple PDU Session Anchors assumes that when needed, appropriate mechanisms are in place to correctly forward packets on the N6 reference point. The mechanisms for packet forwarding on the N6 reference point between the PDU Session Anchor providing local access and the DN are outside the scope of this specification. The UL CL provides forwarding of UL traffic towards different PDU Session Anchors and merge of DL traffic to the UE i.e. merging the traffic from the different PDU Session Anchors on the link towards the UE. This is based on traffic detection and traffic forwarding rules provided by the SMF. The UL CL applies filtering rules (e.g. to examine the destination IP address/Prefix of UL IP packets sent by the UE) and determines how the packet should be routed. The UPF supporting an UL CL may also be controlled by the SMF to support traffic measurement for charging, traffic replication for LI and bit rate enforcement (Session-AMBR per PDU Session). NOTE 1: When N9 forwarding tunnel exists between source ULCL and target ULCL, the Session-AMBR per PDU Session can be enforced by the source UL CL UPF. NOTE 2: The UPF supporting an UL CL may also support a PDU Session Anchor for connectivity to the local access to the data network (including e.g. support of tunnelling or NAT on N6). This is controlled by the SMF. Additional UL CLs (and thus additional PDU Session Anchors) can be inserted in the data path of a PDU Session to create new data paths for the same PDU Session. The way to organize the data path of all UL CLs in a PDU Session is up to operator configuration and SMF logic and there is only one UPF supporting UL CL connecting to the (R)AN via N3 interface, except when session continuity upon UL CL relocation is used. The insertion of an ULCL in the data path of a PDU Session is depicted in Figure 5.6.4.2-1. Figure 5.6.4.2-1: User plane Architecture for the Uplink Classifier NOTE 3: It is possible for a given UPF to support both the UL CL and the PDU Session Anchor functionalities. Due to UE mobility the network may need to relocate the UPF acting as UL CL and establish a new PSA for local access to the DN. To support session continuity during UL CL relocation the network may establish a temporary N9 forwarding tunnel between the source UL CL and target UL CL. The AF may influence the creation of the N9 forwarding tunnel as described in clause 5.6.7.1. The N9 forwarding tunnel is maintained until: - all active traffic flowing on it ceases to exist for: - a configurable period of time; or - a period of time indicated by the AF; - until the AF informs the SMF that it can release the source PSA providing local access to the DN. During the existence of the N9 forwarding tunnel the UPF acting as target UL CL is configured with packet filters that: - force uplink traffic from existing data sessions between UE and the application in the source local part of the DN (as defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]) into the N9 forwarding tunnel towards the source UL CL. - force any traffic related to the application in the target local part of the DN to go to the new local part of the DN via the target PSA. SMF may send a Late Notification to AF to inform it about the DNAI change as described in clause 4.3.6.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. This notification can be used by the AF e.g. to trigger mechanisms in the source local part of the DN to redirect the ongoing traffic sessions towards an application in the target local part of the DN. SMF can also send late notification to the target AF instance if associated with this target local part of the DN. The procedure for session continuity upon UL CL relocation is described in clause 4.3.5.7 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When an I-SMF is inserted for a PDU Session, the details of UL CL insertion which is controlled by an I-SMF is described in clause 5.34.4. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.4.2 |
1,328 | 4.4 MM specific procedures | A MM specific procedure can only be started if no other MM specific procedure is running or no MM connection exists between the network and the mobile station. The end of the running MM specific procedure or the release of all MM connections have to be awaited before a new MM specific procedure can be started. During the lifetime of a MM specific procedure, if a MM connection establishment is requested by a CM entity, this request will either be rejected or be delayed until the running MM specific procedure is terminated (this depends on the implementation). Any MM common procedure (except IMSI detach) may be initiated during a MM specific procedure. Unless it has specific permission from the network (follow-on proceed) the mobile station side should await the release of the RR connection used for a MM specific procedure before a new MM specific procedure or MM connection establishment is started. NOTE: The network side may use the same RR connection for MM connection management. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4 |
1,329 | 5.20d User Plane Direct 5GS Information Exposure 5.20d.1 General | In order to expose network information, the user plane direct 5GS information exposure function may be applied. The user plane direct 5GS information exposure function allows the UPF to report the network information directly to consumer based on the instructions provided by SMF. NOTE: In the scenario of Edge Computing as described in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130], the consumer can be the L-NEF or local AF when the local AF is trusted. When the exposed network information is provided by the UPF, the PSA UPF may be instructed to report network information via Nupf_EventExposure service (e.g. directly to an AF, i.e. bypassing the SMF and the PCF); or the UPF may be instructed to report the information to the consumer via SMF/PCF/NEF, as described in clause 5.8.2.18. When the exposed network information is provided by the NG-RAN, the NG-RAN may be instructed by the SMF to report the information via the GTP-U tunnel(s) between the NG RAN and PSA UPF, as defined in clause 5.45. The User Plane Direct 5GS Information Exposure may be used for exposing the following information: - QoS Monitoring information (see clause 5.45). - TSC Management Information (see clause 5.28.3). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.20d |
1,330 | 16.18.2 Subscription-based Identification of Aerial UE | Support for Aerial UE functions is stored in the user's subscription information in UDM. UDM transfers this information to the AMF during Registration, Service Request and Mobility Registration Update procedures. The Aerial UE subscription information can be provided by the AMF to the NG-RAN node via the NGAP INITIAL CONTEXT SETUP REQUEST message during the Registration, Mobility Registration Update and Service Request procedures. The subscription information can also be updated via the NGAP UE Context Modification procedure and NGAP Path Switch Acknowledge procedure. In addition, for Xn-based handover, the source NG-RAN node can include the Aerial UE subscription information in the XnAP HANDOVER REQUEST message and RETRIEVE UE CONTEXT RESPONSE message to the target NG-RAN node. For intra- and inter-AMF NG-based handover, the AMF provides the Aerial UE subscription information to the target NG-RAN node after the handover procedure. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.18.2 |
1,331 | 6.1.3.4.1 PDP context deactivation initiated by the MS | In order to deactivate a PDP context, the MS sends a DEACTIVATE PDP CONTEXT REQUEST message to the network, enters the state PDP-INACTIVE-PENDING and starts timer T3390. The message contains the transaction identifier (TI) in use for the PDP context to be deactivated and a cause code that typically indicates one of the following causes: # 25: LLC or SNDCP failure (A/Gb mode only); # 26: insufficient resources; # 36: regular deactivation; or # 37: QoS not accepted. The network shall reply with the DEACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the MS shall stop timer T3390. In A/Gb mode, both the MS and the network shall initiate local release of the logical link if it is not used by another PDP context. In Iu mode, the network shall initiate the release of Radio Access Bearer associated with this PDP context. If the selected Bearer Control Mode is 'MS/NW' the MS should not deactivate a PDP context, if it is the only PDP context without TFT within a group of active PDP contexts sharing the same PDP address and APN. NOTE 1: A configuration with more than one PDP context without TFT within a group of active PDP contexts sharing the same PDP address and APN can occur during a network initiated PDP context modification due to asynchronous TFT states in the MS and in the network (see e.g. subclause 6.1.3.3.4 bullet a.3 in the description of the TFT checks). NOTE 2: If the MS deactivates the last remaining PDP context without TFT within a group of active PDP contexts sharing the same PDP address and APN, a network implementing this version of the protocol will deactivate all other active PDP contexts sharing the same PDP address and APN by explicit peer-to-peer signalling; a network compliant with earlier versions of the protocol can initiate the re-establishment of this PDP context using the network requested secondary PDP context activation procedure. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.4.1 |
1,332 | 5.8.10.4 Sidelink measurement report triggering 5.8.10.4.1 General | The UE shall: 1> for each sl-MeasId included in the sl-MeasIdList within VarMeasConfigSL: 2> if the sl-ReportType is set to sl-EventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the sl-EventId of the corresponding sl-ReportConfig within VarMeasConfigSL, is fulfilled for NR sidelink frequency for all NR sidelink measurements after layer 3 filtering taken during sl-TimeToTrigger defined for this event within the VarMeasConfigSL, while the VarMeasReportListSL does not include a NR sidelink measurement reporting entry for this sl-MeasId (a first NR sidelink frequency triggers the event): 3> include a NR sidelink measurement reporting entry within the VarMeasReportListSL for this sl-MeasId; 3> set the sl-NumberOfReportsSent defined within the VarMeasReportListSL for this sl-MeasId to 0; 3> include the concerned NR sidelink frequency in the sl-FrequencyTriggeredList defined within the VarMeasReportListSL for this sl-MeasId; 3> initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5; 2> else if the sl-ReportType is set to sl-EventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the sl-EventId of the corresponding sl-ReportConfig within VarMeasConfigSL, is fulfilled for NR sidelink frequency not included in the sl-FrequencyTriggeredList for all NR sidelink measurements after layer 3 filtering taken during sl-TimeToTrigger defined for this event within the VarMeasConfigSL (a subsequent NR sidelink frequency triggers the event): 3> set the sl-NumberOfReportsSent defined within the VarMeasReportListSL for this sl-MeasId to 0; 3> include the concerned NR sidelink frequency in the sl-FrequencyTriggeredList defined within the VarMeasReportListSL for this sl-MeasId; 3> initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5; 2> else if the sl-ReportType is set to sl-EventTriggered and if the leaving condition applicable for this event is fulfilled for NR sidelink frequency included in the sl-FrequencyTriggeredList defined within the VarMeasReportListSL for this sl-MeasId for all NR sidelink measurements after layer 3 filtering taken during sl-TimeToTrigger defined within the VarMeasConfigSL for this event: 3> remove the concerned NR sidelink frequency in the sl-FrequencyTriggeredList defined within the VarMeasReportListSL for this sl-MeasId; 3> if sl-ReportOnLeave is set to true for the corresponding reporting configuration: 4> initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5; 3> if the sl-FrequencyTriggeredList defined within the VarMeasReportListSL for this sl-MeasId is empty: 4> remove the NR sidelink measurement reporting entry within the VarMeasReportListSL for this sl-MeasId; 4> stop the periodical reporting timer for this sl-MeasId, if running; 2> if sl-ReportType is set to sl-Periodical and if a (first) NR sidelink measurement result is available: 3> include a NR sidelink measurement reporting entry within the VarMeasReportListSL for this sl-MeasId; 3> set the sl-NumberOfReportsSent defined within the VarMeasReportListSL for this sl-MeasId to 0; 3> initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5, immediately after the quantity to be reported becomes available for the NR sidelink frequency: 2> upon expiry of the periodical reporting timer for this sl-MeasId: 3> initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.4 |
1,333 | 4.15.6.6a AF session with required QoS update procedure | Figure 4.15.6.6a-1: AF session with required QoS update procedure 1. For an established AF session with required QoS, the AF may send a Nnef_AFsessionWithQoS_Update request message (AF Identifier, Transaction Reference ID, [Flow description information], [QoS Reference or individual QoS parameters], [Alternative Service Requirements (as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20])]) to NEF for updating the reserved resources. Optionally, Indication of ECN marking for L4S, PDU Set QoS Parameters (as described in clause 5.7.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and Protocol Description (as described in clause 5.37.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) can be included in the AF request. For a Multi-modal service, the AF may provide/update Multi-modal Service Requirements information of the existing data flows as described in clause 6.1.3.27.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Optionally, a period of time or a traffic volume for the requested QoS can be included in the AF request. The Transaction Reference ID provided in the AF session with required QoS update request message is set to the Transaction Reference ID that was assigned, by the NEF, to the Nnef_AFsessionWithQoS_Create request message. The AF may, instead of a QoS Reference, provide one or more of the following individual QoS parameters: Requested 5GS Delay (optional), Requested Priority (optional), Requested Guaranteed Bitrate, Requested Maximum Bitrate, Maximum Burst Size and Requested Packet Error Rate. The AF may also provide an Averaging Window. Regardless whether the AF request is formulated using a QoS Reference or individual QoS parameters, the AF may also provide one or more of the following parameters that describe the traffic characteristics: flow direction, Burst Arrival Time at UE (uplink) or UPF (downlink), Periodicity, Time domain, Survival Time, Capability for BAT adaptation or BAT Window, Periodicity Range. The optional Alternative Service Requirements provided by the AF shall either contain QoS References or Requested Alternative QoS Parameter Set(s) in a prioritized order as specified in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Optionally, Packet Delay Variation requirements can be included in the AF request as described in clause 6.1.3.26 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 2. The NEF authorizes the AF request of updating AF session with required QoS and may apply policies to control the overall amount of QoS authorized for the AF. If the authorisation is not granted, all steps (except step 5) are skipped and the NEF replies to the AF with a Result value indicating that the authorisation failed. 3. The NEF shall contact the same NF type (i.e. TSCTSF or PCF) as with the initial Nnef_AFsessionWithQoS_Create request during the establishment procedure in clause 4.15.6.6. If the NEF determined not to invoke the TSCTSF, then steps 3, 4, 5, 6, 7 are executed, otherwise, steps 3a, 3b, 4a, 4b, 5, 6a, 6b, 7 are executed. If the Nnef_AfsessionWithQoS_Update adds any parameters that would require the NEF to invoke TSCTSF while the NEF determined not to invoke the TSCTSF for the initial Nnef_AFsessionWithQoS_Create request, the NEF shall reject the Nnef_AFsessionWithQoS_Update request with a cause value indicating the reason of failure. If the NEF does not invoke the TSCTSF, the NEF interacts with the PCF by triggering a Npcf_PolicyAuthorization_Update request and forwards received parameters to the PCF. Any optionally received period of time or traffic volume is mapped and forwarded as sponsored data connectivity information (as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). If the AF is considered to be trusted by the operator, the AF uses the Npcf_PolicyAuthorization_Update request message to interact directly with PCF to update the reserving resources for an AF session. 3a. If the NEF decided to contact the TSCTSF when the session was established, the NEF forwards received parameters in the Ntsctsf_QoSandTSCAssistance_Update request message to the TSCTSF. Any optionally received period of time or traffic volume is mapped and forwarded as sponsored data connectivity information (as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). If the AF is considered to be trusted by the operator, the AF uses the Ntsctsf_QoSandTSCAssistance_Update request message to interact directly with TSCTSF to update the reserving resources for an AF session. 3b. The TSCTSF interacts with the PCF by triggering a Npcf_PolicyAuthorization_Update request and forwards the received parameters after executing the adjustment and mapping actions described in step 3b of clause 4.15.6.6. 4. The PCF processes the Npcf_PolicyAuthorization_Update request according to the actions described in step 4 of clause 4.15.6.6. 4a. The PCF processes the Npcf_PolicyAuthorization_Update request according to the actions described in step 4a of clause 4.15.6.6. If the PCF has received a request to unsubscribe for 5GS Bridge/Router information Notification, the PCF uses the PCF initiated SM Policy Association Modification procedure as described in clause 4.16.5.2 to unsubscribe for 5GS Bridge/Router information event from the SMF. 4b. The TSCTSF sends a Ntsctsf_QoSandTSCAssistance_Update response message (Transaction Reference ID, Result) to the NEF. Result indicates whether the request is granted or not. If the AF is considered to be trusted by the operator, the TSCTSF sends the Ntsctsf_QoSandTSCAssistance_Update response message directly to AF. 5. The NEF sends a Nnef_AFsessionWithQoS_Update response message (Transaction Reference ID, Result) to the AF. Result indicates whether the request is granted or not. 6. The PCF sends Npcf_PolicyAuthorization_Notify message to the NEF when the modification of the transmission resources corresponding to the QoS update succeeded or failed, or when an Alternative Service Requirement is being applied. If the AF is considered to be trusted by the operator, the PCF sends the Npcf_PolicyAuthorization_Notify message directly to AF. 6a. The PCF sends Npcf_PolicyAuthorization_Notify message to the TSCTSF when the modification of the transmission resources corresponding to the QoS update succeeded or failed, or when an Alternative Service Requirement is being applied. 6b. The TSCTSF sends Ntsctsf_QoSandTSCAssistance_Notify message with the event reported by the PCF to the NEF. If the AF is considered to be trusted by the operator, the TSCTSF sends the Ntsctsf_QoSandTSCAssistance_Notify message directly to the AF. 7. The NEF sends Nnef_AFsessionWithQoS_Notify message with the event reported by the PCF to the AF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.6a |
1,334 | – RRCReestablishment | The RRCReestablishment message is used to re-establish SRB1. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE RRCReestablishment message -- ASN1START -- TAG-RRCREESTABLISHMENT-START RRCReestablishment ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReestablishment RRCReestablishment-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReestablishment-IEs ::= SEQUENCE { nextHopChainingCount NextHopChainingCount, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReestablishment-v1700-IEs OPTIONAL } RRCReestablishment-v1700-IEs ::= SEQUENCE { sl-L2RemoteUE-Config-r17 SetupRelease {SL-L2RemoteUE-Config-r17} OPTIONAL, -- Cond L2RemoteUE nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCREESTABLISHMENT-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,335 | C.1 Routing Area Identities | This clause describes a possible way to support inter-PLMN roaming. When an MS roams between two SGSNs within the same PLMN, the new SGSN finds the address of the old SGSN from the identity of the old RA. Thus, each SGSN can determine the address of every other SGSN in the PLMN. When an MS roams from an SGSN in one PLMN to an SGSN in another PLMN, the new SGSN may be unable to determine the address of the old SGSN. Instead, the SGSN transforms the old RA information to a logical name of the form: racAAAA.lacBBBB.mncYYY.mccZZZ.gprs A and B shall be Hex coded digits; Y and Z shall be encoded as single digits (in the range 0-9). If there are less than 4 significant digits in AAAA or BBBB, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digit coding. As an example, the logical name for RAC 123A, LAC 234B, MCC 167 and MNC 92 will be coded in the DNS server as: rac123A.lac234B.mnc092.mcc167.gprs. The SGSN may then acquire the IP address of the old SGSN from a DNS server, using the logical address. Introducing the DNS concept in GPRS enables operators to use logical names instead of IP addresses when referring to nodes (e.g. GSNs), thus providing flexibility and transparency in addressing. Each PLMN should include at least one DNS server (which may optionally be connected via the DNS service provided by the GSM Association). Note that these DNS servers are GPRS internal entities, unknown outside the GPRS system. The above implies that at least MCC || MNC || LAC || RAC (= RAI) is sent as the RA parameter over the radio interface when an MS roams to another RA. If for any reason the new SGSN fails to obtain the address of the old SGSN, the new SGSN takes the same actions as when the corresponding event occurs within one PLMN. Another way to support seamless inter-PLMN roaming is to store the SGSN IP addresses in the HLR and request them when necessary. If Intra Domain Connection of RAN Nodes to Multiple CN Nodes (see 3GPP TS 23.236[ Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ] [23]) is applied then the Network Resource Identifier (NRI) identifies uniquely a given SGSN node out of all the SGSNs serving the same pool area. If the new SGSN is not able to extract the NRI from the old P-TMSI, it shall retrieve the address of the default SGSN (see 3GPP TS 23.236[ Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ] [23]) serving the old RA, using the logical name described earlier in this clause. The default SGSN in the old RA relays the GTP signalling to the old SGSN identified by the NRI in the old P-TMSI unless the default SGSN itself is the old SGSN. If the new SGSN is able to extract the NRI from the old P-TMSI, then it shall attempt to derive the address of the old SGSN from the NRI and the old RAI. NRI-to-SGSN assignments may be either configured (by O&M) in the new SGSN, or retrieved from a DNS server. If a DNS server is used, it shall be queried using the following logical name, derived from the old RAI and NRI information: nriCCCC.racDDDD.lacEEEE.mncYYY.mccZZZ.gprs C, D and E shall be Hex coded digits, Y and Z shall be encoded as single digits (in the range 0-9). If there are less than 4 significant digits in CCCC, DDDD or EEEE, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digits coding. As an example, the logical name for NRI 3A, RAC 123A, LAC 234B, MCC 167 and MNC 92 will be coded in the DNS server as: nri003A.rac123A.lac234B.mnc092.mcc167.gprs. If for any reason the new SGSN fails to obtain the address of the old SGSN using this method, then as a fallback method it shall retrieve the address of the default SGSN serving the old RA. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | C.1 |
1,336 | 6.3.2.6 Abnormal cases in the UE | The following abnormal cases can be identified: a) PDU session inactive for the received PDU session ID. If the PDU session ID in the PDU SESSION MODIFICATION COMMAND message belongs to any PDU session in state PDU SESSION INACTIVE in the UE, the UE shall set the 5GSM cause IE to #43 "Invalid PDU session identity" in the 5GSM STATUS message, and set the PDU session ID to the received PDU session ID in the UL NAS TRANSPORT message as specified in subclause 5.4.5. b) Collision of network-requested PDU session modification procedure and UE-requested PDU session modification procedure. If the UE receives a PDU SESSION MODIFICATION COMMAND message during the UE-requested PDU session modification procedure, the PTI IE of the PDU SESSION MODIFICATION COMMAND message is set to "No procedure transaction identity assigned", and the PDU session indicated in the PDU SESSION MODIFICATION COMMAND message is the PDU session that the UE had requested to modify, the UE shall abort internally the UE-requested PDU session modification procedure, enter the state PDU SESSION ACTIVE and proceed with the network-requested PDU session modification procedure. c) A semantic error in QoS operations or a sematic error in packet filters is detected in a PDU SESSION MODIFICATION COMMAND message that contains other optional information elements. If the UE diagnoses a semantic error in QoS operations or a semantic error in packet filters in the PDU SESSION MODIFICATION COMMAND, as specified in subclause 6.3.2.4, and the message contains other optional information elements, the UE shall discard the other optional information elements and shall send the PDU SESSION MODIFICATION REJECT message as specified in subclause 6.3.2.4. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.2.6 |
1,337 | 6.3.1 Scrambling | For each codeword , the block of bits , where is the number of bits in codeword transmitted on the physical channel in one subframe/slot/subslot, shall be scrambled prior to modulation, resulting in a block of scrambled bits according to where the scrambling sequence is given by clause 7.2. The scrambling sequence generator shall be initialised at the start of each subframe, where the initialisation value of depends on the transport channel type according to where corresponds to the RNTI associated with the PDSCH transmission as described in clause 7.1 TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. For BL/CE UEs, the same scrambling sequence is applied per subframe to PDSCH for a given block of subframes. The subframe number of the first subframe in each block of consecutive subframes, denoted as , satisfies . For the block of subframes, the scrambling sequence generator shall be initialised with where and is the absolute subframe number of the first downlink subframe intended for PDSCH. The PDSCH transmission spans consecutive subframes including subframes that are not BL/CE DL subframes where the PDSCH transmission is postponed. For BL/CE UEs, - if the PDSCH is carrying SIB1-BR - - else if the PDSCH is carrying SI message (except for SIB1-BR) or if the PDSCH transmission is associated with P-RNTI or SC-RNTI: - for frame structure type 1 and for frame structure type 2 - otherwise - for UEs assuming CEModeA (according to the definition in Clause 12 of [4]) or configured with CEModeA - for frame structure type 1 and for frame structure type 2 for UEs assuming CEModeB (according to the definition in Clause 12 of [4]) or configured with CEModeB For PDSCH with a subframe duration, up to two codewords can be transmitted in one subframe, i.e., . In the case of single codeword transmission, is equal to zero. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.1 |
1,338 | 5.8.9.1b.2 Sidelink Carrier Addition/Modification | The UE shall: 1> for unicast, if the sidelink carrier addition was triggered due to the reception of the RRCReconfigurationSidelink message; or 1> for unicast, after receiving the RRCReconfigurationCompleteSidelink message, 2> for each sl-Carrier-Id value included in the sl-CarrierToAddModList that is not part of the current UE configuration (sidelink carrier addition): 3> add the sidelink carrier, corresponding to the sl-Carrier-Id, in accordance with the sl-AbsoluteFrequencyPointA for reception; 1> for unicast, if the sidelink carrier was modified due to the reception of the RRCReconfigurationSidelink message; or 1> for unicast, after receiving the RRCReconfigurationCompleteSidelink message, 2> for each sl-Carrier-Id value included in the sl-CarrierToAddModList that is part of the current UE configuration (sidelink carrier modification): 3> modify the sidelink carrier configuration in accordance with sl-AbsoluteFrequencyPointA for reception; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1b.2 |
1,339 | 5.35A.3.1 UE mobility between a fixed cell and MBSR cell | The procedure of Inter-gNB-DU Mobility as defined in TS 38.401[ NG-RAN; Architecture description ] [42] or the handover procedure using the Xn/N2 reference points as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3] can be used. For UEs in RRC_IDLE and RRC_INACTIVE state when a MBSR goes out-of-service, procedure for cell (re-)selection as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50] for RRC_IDLE and RRC_INACTIVE is used. For UEs in RRC_CONNECTED state, if the MBSR goes out-of-service due to e.g. MBSR moves to an area where the MBSR is not allowed to provide the relay service, the procedure for IAB node release as specified in TS 38.401[ NG-RAN; Architecture description ] [42] is used. The IAB-donor-CU triggers handover procedure when it is possible for the UEs accessing emergency service and being served by the MBSR, if MBSR is about to become unavailable to provide the services. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.35A.3.1 |
1,340 | 4.4.2.3 Establishment of a 5G NAS security context during N1 mode to N1 mode handover | During an N1 mode to N1 mode handover, the target AMF may derive a new 5G NAS security context for which the target AMF creates a new 5G NAS security context as indicated in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. When a new 5G NAS security context is derived using the same KAMF, the target AMF includes the 8 least significant bits of the downlink NAS COUNT in the Intra N1 mode NAS transparent container IE, and indicates that a new KAMF shall not be derived (see subclause 9.11.2.6). The AMF shall increment the downlink NAS COUNT by one after creating the Intra N1 mode NAS transparent container IE. When a new 5G NAS security context is created from a new KAMF, the target AMF includes the 8 least significant bits of the downlink NAS COUNT in the Intra N1 mode NAS transparent container IE and indicates that a new KAMF shall be derived (see subclause 9.11.2.6). The AMF shall then set both the uplink and downlink NAS COUNT counters of this 5G NAS security context to zero. The AMF shall increment the downlink NAS COUNT by one after creating the Intra N1 mode NAS transparent container IE. The target AMF also includes the ngKSI with the same value as the ngKSI currently being used with the UE, the message authentication code, and the selected NAS algorithms in the Intra N1 mode NAS transparent container IE. When the UE receives a command to perform handover to NG-RAN including an Intra N1 mode NAS transparent container IE (see subclause 9.11.2.6), the UE derives a new 5G NAS security context as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. When the Intra N1 mode NAS transparent container IE indicates that a new KAMF needs to be derived, the UE shall set both the downlink NAS COUNT and uplink NAS COUNT to zero after creating the new 5G NAS security context. If the received Intra N1 mode NAS transparent container IE does not have a valid NAS COUNT (see subclause 4.4.3.2) or the received NAS MAC is not verified successfully (see subclause 4.4.3.3) the UE shall discard the content of the received Intra N1 mode NAS transparent container IE, continue to use the current 5G NAS security context, and inform the lower layers that the received Intra N1 mode NAS transparent container is invalid. NOTE 1: During N1 mode to N1 mode handover, the Intra N1 mode NAS transparent container IE (see subclause 9.11.2.6) is equivalent to sending a SECURITY MODE COMMAND message to the UE in order to derive and use a new 5G NAS security context, optionally created with a new KAMF. The UE maintains the Selected EPS NAS security algorithms until the UE receives a new Selected EPS NAS security algorithms. After the new 5G NAS security context is taken into use for 3GPP access following a successful N1 mode to N1 mode handover and the UE is registered with the same PLMN over the 3GPP access and non-3GPP access: a) the UE is in 5GMM-IDLE mode over non-3GPP access, the AMF and the UE shall activate and take into use the new 5G NAS security context over the non-3GPP access as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] after the AMF sends or the UE receives the REGISTRATION ACCEPT message respectively. If the new 5G NAS security context is created from a new KAMF, the AMF and the UE shall set the downlink NAS COUNT and uplink NAS COUNT to zero also for the non-3GPP access, otherwise the downlink NAS COUNT and uplink NAS COUNT for the non-3GPP access are not changed; or b) the UE is in 5GMM-CONNECTED mode over non-3GPP access, in order to activate the new 5G NAS security context over the non-3GPP access that has been activated for the 3GPP access the AMF shall send the SECURITY MODE COMMAND message over the non-3GPP access as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The SECURITY MODE COMMAND message shall include the same ngKSI to identify the new 5G NAS security context that was activated over the 3GPP access and shall include the horizontal derivation parameter indicating "KAMF derivation is not required". Otherwise, if the new 5G NAS security context is created from a new KAMF, the AMF and the UE shall set the downlink NAS COUNT and uplink NAS COUNT to zero for the non-3GPP access. NOTE 2: Explicit indication "KAMF derivation is not required" for the non-3GPP access is to align security contexts within the UE without a subsequent derivation of a new KAMF in the non-3GPP access. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.2.3 |
1,341 | 9.11.3.33 NAS message container | The purpose of the NAS message container IE is to encapsulate a plain 5GS NAS REGISTRATION REQUEST, DEREGISTRATION REQUEST, or SERVICE REQUEST message, or to encapsulate non-cleartext IEs of a CONTROL PLANE SERVICE REQUEST message. The NAS message container information element is coded as shown in figure 9.11.3.33.1 and table 9.11.3.33.1. The NAS message container is a type 6 information element. Figure 9.11.3.33.1: NAS message container information element Table 9.11.3.33.1: NAS message container information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.33 |
1,342 | 8.10.1.2.5B Single-layer Spatial Multiplexing (With Enhanced DMRS table configured) | For single-layer transmission on antenna port 7, 8, 11 or 13 upon detection of a PDCCH with DCI format 2C, the requirement is specified in Table 8.10.1.2.5B -2, with the addition of the parameters in Table 8.10.1.2.5B -1 and the downlink physical channel setup according to Annex C.3.2. The purpose of the test is to verify rank-1 performance on antenna port 11 with a simultaneous transmission on the antenna port 7, 8 or 13 with DMRS enhancement table and 4 orthogonal DMRS ports (dmrs-Enhancements-r13 UE-EUTRA-Capability [7]). Table 8.10.1.2.5B-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations with Enhanced DMRS table Table 8.10.1.2.5B-2: Minimum performance for CDM-multiplexed DM RS with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations with Enhanced DMRS table | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.2.5B |
1,343 | 5.6.3.5 Abnormal cases on the UE side | The following abnormal cases can be identified: a) NOTIFICATION message received via non-3GPP access with access type indicating 3GPP access when UE-initiated 5GMM specific procedure or service request procedure over 3GPP access is ongoing. The UE shall proceed with 5GMM specific procedure or service request procedure. If for registration procedure and service requestprocedure lower layers indicate that the access attempt is barred, then the UE shall handle the pending NOTIFICATION message as specified in subclause 5.6.3.2. Otherwise, the UE shall ignore the NOTIFICATION message once lower layers confirms the establishment of the signalling connection. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.3.5 |
1,344 | 6.3.4 Distribution of IMSI and temporary authentication data within one serving network domain | The purpose of this procedure is to provide a newly visited VLR/SGSN with temporary authentication data from a previously visited VLR/SGSN within the same serving network domain. The procedure is shown in Figure 11. Figure 11: Distribution of IMSI and temporary authentication data within one serving network domain The procedure shall be invoked by the newly visited VLRn/SGSNn after the receipt of a location update request (resp. routing area update request) from the user wherein the user is identified by means of a temporary user identity TMSIo (resp. P-TMSIo) and the location area identity LAIo (resp. routing area identity RAIo) under the jurisdiction of a previously visited VLRo/SGSNo that belongs to the same serving network domain as the newly visited VLRn/SGSNn. The protocol steps are as follows: a) The VLRn/SGSNn sends a user identity request to the VLRo/SGSNo, this message contains TMSIo and LAIo (resp. P-TMSIo and RAIo). b) The VLRo/SGSNo searches the user data in the database. If the user is found, the VLRo/SGSNo shall send a user identity response back that: i) shall include the IMSI, ii) may include a number of unused authentication vectors (quintets or triplets) ordered on a first-in / first-out basis, and iii) may include the current security context data: CK, IK and KSI (UMTS) or Kc and CKSN (GSM). The SGSNn shall derive Kc128 from the current security context data according to annex B.5 if it received a CK/IK pair and KSI from the SGSNo and if the SGSNn is to use a 128-bit GSM ciphering algorithm in GSM. The VLRn shall derive Kc128 from the current security context data according to annex B.5 if it received a CK/IK pair and KSI from the VLRo and if the VLRn is to signal a 128-bit GSM ciphering algorithm as a permitted ciphering algorithm to the BSS in GSM. The VLRo/SGSNo subsequently deletes the authentication vectors which have been sent and the data elements on the current security context. If the user cannot be identified the VLRo/SGSNo shall send a user identity response indicating that the user identity cannot be retrieved. c) If the VLRn/SGSNn receives a user identity response with an IMSI, it creates an entry and stores any authentication vectors and any data on the current security context that may be included. If the VLRn/SGSNn receives a user identity response indicating that the user could not be identified, it shall initiate the user identification procedure described in 6.2. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3.4 |
1,345 | 4.11.1.3.2A 5GS to EPS Idle mode mobility using N26 interface with data forwarding | Figure 4.11.1.3.2A-1 describes the idle mode mobility registration procedure from 5GS to EPS when N26 is supported with data forwarding. Figure 4.11.1.3.2A-1: 5GS to EPS Idle mode mobility using N26 interface with data forwarding 1. Steps 1-7 from clause 4.11.1.3.2 with the following enhancements: - The (V-)SMF includes the Buffered DL Data Waiting indication in the Nsmf_PDUSession_Response in step 5c of figure 4.11.1.3.2-1, if the Extended buffering timer is running in (V-)SMF. - The AMF forwards the Buffered DL Data Waiting indication to MME in step 6 of figure 4.11.1.3.2-1, if it's received from SMF above. 2. Steps 7-9 from clause 5.3.3.1A of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 3. Steps 14, 15, 15a and 16 from clause 4.11.1.3.2. 4. Steps 10-14 from clause 5.3.3.1A of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 5. Steps 10a, b, c from clause 4.11.1.2.1 with the following enhancements: - If data forwarding tunnel information (i.e. Forwarding F-TEID) is received from MME in step 14 of figure 5.3.3.1A-1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] in step 4 above, the AMF provides the data forwarding tunnel info to (V-)SMF in Nsmf_PDUSession_UpdateSMContext Request. The (V-)SMF provides the data forwarding tunnel info to (V-)UPF if data is buffered in (V-)UPF. - The (V-)SMF and (V-)UPF forwards data using the provided SGW forwarding tunnel above. The (V-)SMF also initiates a timer to release the SM context or data forwarding tunnel of the PDU session. The data received by the Serving GW on the forwarding tunnel is forwarded on the (newly) established tunnel to eNB. 6. Step 15b from clause 4.11.1.3.2 with following enhancements: The (V-)SMF initiates the release of data forwarding tunnel after the timer in step 5 above is expired. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.3.2A |
1,346 | 16.3.4.5 Mobility | To make mobility slice-aware in case of Network Slicing, S-NSSAI is introduced as part of the PDU session information that is transferred during mobility signalling. This enables slice-aware admission and congestion control. Both NG and Xn handovers are allowed regardless of the slice support of the target NG-RAN node i.e. even if the target NG-RAN node does not support the same slices as the source NG-RAN node. An example for the case of connected mode mobility across different Registration Areas is shown in Figure 16.3.4.5-1 for the case of NG based handover and in Figure 16.3.4.5-2 for the case of Xn based handover. Figure 16.3.4.5-1: NG based mobility across different Registration Areas Figure 16.3.4.5-2: Xn based mobility across different Registration Areas | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.3.4.5 |
1,347 | – AreaConfiguration | The AreaConfiguration indicates area for which UE is requested to perform measurement logging. If not configured, measurement logging is not restricted to specific cells or tracking areas but applies as long as the RPLMN is contained in plmn-IdentityList stored in VarLogMeasReport. AreaConfiguration information element -- ASN1START -- TAG-AREACONFIGURATION-START AreaConfiguration-r16 ::= SEQUENCE { areaConfig-r16 AreaConfig-r16, interFreqTargetList-r16 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R } AreaConfiguration-r17 ::= SEQUENCE { areaConfig-r17 AreaConfig-r16 OPTIONAL, -- Need R interFreqTargetList-r17 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R } AreaConfiguration-v1800 ::= SEQUENCE { cag-ConfigList-r18 CAG-ConfigList-r18 OPTIONAL, -- Need R snpn-ConfigList-r18 SNPN-ConfigList-r18 OPTIONAL -- Need R } AreaConfig-r16 ::= CHOICE { cellGlobalIdList-r16 CellGlobalIdList-r16, trackingAreaCodeList-r16 TrackingAreaCodeList-r16, trackingAreaIdentityList-r16 TrackingAreaIdentityList-r16 } InterFreqTargetInfo-r16 ::= SEQUENCE { dl-CarrierFreq-r16 ARFCN-ValueNR, cellList-r16 SEQUENCE (SIZE (1..32)) OF PhysCellId OPTIONAL -- Need R } CellGlobalIdList-r16 ::= SEQUENCE (SIZE (1..32)) OF CGI-Info-Logging-r16 TrackingAreaCodeList-r16 ::= SEQUENCE (SIZE (1..8)) OF TrackingAreaCode TrackingAreaIdentityList-r16 ::= SEQUENCE (SIZE (1..8)) OF TrackingAreaIdentity-r16 TrackingAreaIdentity-r16 ::= SEQUENCE { plmn-Identity-r16 PLMN-Identity, trackingAreaCode-r16 TrackingAreaCode } CAG-ConfigList-r18 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-Config-r18 CAG-Config-r18 ::= SEQUENCE { plmn-Identity-r18 PLMN-Identity, cag-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 } SNPN-ConfigList-r18 ::= CHOICE { snpn-ConfigCellIdList-r18 SNPN-ConfigCellIdList-r18, snpn-ConfigTAIList-r18 SNPN-ConfigTAIList-r18, snpn-ConfigIDList-r18 SNPN-ConfigIDList-r18 } SNPN-ConfigCellIdList-r18 ::= SEQUENCE (SIZE (1..maxSNPN-ConfigCellId-r18)) OF SNPN-ConfigCellId-r18 SNPN-ConfigCellId-r18 ::= SEQUENCE { cgi-Identity-r18 CGI-Info-Logging-r16, nid-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 } SNPN-ConfigTAIList-r18 ::= SEQUENCE (SIZE (1..maxSNPN-ConfigTAI-r18)) OF SNPN-ConfigTAI-r18 SNPN-ConfigTAI-r18 ::= SEQUENCE { tai-Identity-r18 TrackingAreaIdentity-r16, nid-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 } SNPN-ConfigIDList-r18 ::= SEQUENCE (SIZE (1..maxSNPN-ConfigID-r18)) OF SNPN-ConfigID-r18 SNPN-ConfigID-r18 ::= SEQUENCE { plmn-Identity-r18 PLMN-Identity, nid-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 } -- TAG-AREACONFIGURATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,348 | 5.5.3.2.2 Normal and periodic tracking area updating procedure initiation | The UE in state EMM-REGISTERED shall initiate the tracking area updating procedure by sending a TRACKING AREA UPDATE REQUEST message to the MME, a) when the UE detects that the current TAI is not in the list of tracking areas that the UE previously registered in the MME, unless the UE is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17] and is entering a tracking area in a new PLMN that is neither the registered PLMN nor in the list of equivalent PLMNs; b) when the periodic tracking area updating timer T3412 expires and the UE is not registered for emergency services (see subclause 5.3.5); c) when the UE enters EMM-REGISTERED.NORMAL-SERVICE and the UE's TIN indicates "P-TMSI"; d) when the UE performs an inter-system change from S101 mode to S1 mode and has no user data pending; e) when the UE receives an indication from the lower layers that the RRC connection was released with cause "load balancing TAU required"; f) when the UE deactivated EPS bearer context(s) locally while in EMM-REGISTERED, because it could not establish a NAS signalling connection, and then returns to EMM-REGISTERED.NORMAL-SERVICE and no EXTENDED SERVICE REQUEST message, CONTROL PLANE SERVICE REQUEST message or DETACH REQUEST message with detach type is "EPS detach" or "combined EPS/IMSI detach" is pending to be sent by the UE; g) when the UE changes any one of the UE network capability information, the MS network capability information or the N1 UE network capability information; h) when the UE changes the UE specific DRX parameter (in WB-S1 mode or NB-S1 mode); i) when the UE receives an indication of "RRC Connection failure" from the lower layers and has no signalling or user uplink data pending (i.e. when the lower layer requests NAS signalling connection recovery); j) when the UE enters S1 mode after 1xCS fallback or 1xSRVCC; k) when due to manual CSG selection the UE has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the UE's Allowed CSG list or in the UE's Operator CSG list; l) when the UE reselects an E-UTRAN cell while it was in GPRS READY state or PMM-CONNECTED mode; m) when the UE supports SRVCC to GERAN or UTRAN or supports vSRVCC to UTRAN and changes the mobile station classmark 2 or the supported codecs, or the UE supports SRVCC to GERAN and changes the mobile station classmark 3; n) when the UE changes the radio capability for GERAN, or cdma2000® or both; o) when the UE's usage setting or the voice domain preference for E-UTRAN change in the UE; NOTE 1: For the change of UE's usage setting or the voice domain preference for E-UTRAN which results in disabling UE's E-UTRA capability, the UE can skip sending TRACKING AREA UPDATE REQUEST message and directly perform disabling of UE's E-UTRA capability. p) when the UE activates mobility management for IMS voice termination as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex P.2, and the TIN indicates "RAT-related TMSI"; q) when the UE performs an inter-system change from A/Gb mode to S1 mode and the TIN indicates "RAT-related TMSI", but the UE is required to perform tracking area updating for IMS voice termination as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex P.4; r) upon reception of a paging indication using S-TMSI and the UE is in state EMM-REGISTERED.ATTEMPTING-TO-UPDATE; NOTE 2: As an implementation option, the MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. s) when the UE needs to update the network with EPS bearer context status due to local de-activation of EPS bearer context(s) as specified in clause 6.5.1.4A; t) when the UE needs to request the use of PSM or needs to stop the use of PSM; u) when the UE needs to request the use of eDRX or needs to stop the use of eDRX; v) when a change in the eDRX usage conditions at the UE requires different extended DRX parameters; w) when a change in the PSM usage conditions at the UE requires a different timer T3412 value or different timer T3324 value; NOTE 3: A change in the PSM or eDRX usage conditions at the UE can include e.g. a change in the UE configuration, a change in requirements from upper layers or the battery running low at the UE. x) when the CIoT EPS optimizations the UE needs to use, change in the UE; y) when the Default_DCN_ID value changes, as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]; NOTE 4: The tracking area updating procedure is initiated after deleting the DCN-ID list as specified in annex C. z) when the UE performs inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE operates in single-registration mode, and conditions specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] apply; za) when the UE in EMM-IDLE mode changes the radio capability for E-UTRAN; zb) when the UE needs to request new ciphering keys for ciphered broadcast assistance data; zc) when the UE in EMM-IDLE mode changes the radio capability for NG-RAN; zd) when the UE performs inter-system change from N1 mode to S1 mode in EMM-CONNECTED mode; ze) in WB-S1 mode, when the UE has received a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested"; zf) when the UE needs to use the WUS assistance, stop to use the WUS assistance, or change the conditions for using the WUS assistance; zg) when the MUSIM UE needs to request an IMSI Offset value as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] that is used for deriving the paging occasion as specified in 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]; or zh) when the UE in EMM-IDLE mode needs to inform the network that a UE radio capability information update is required due to a cell change between E-UTRAN and satellite E-UTRAN cells. If case b) is the only reason for initiating the normal and periodic tracking area updating procedure, the UE shall indicate "periodic updating" in the EPS update type IE; otherwise the UE shall indicate "TA updating". For cases n, za, zc and zh the UE shall include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message. NOTE 4a: For cases n, za, zc and zh if the UE supports RACS irrespective whether the UE has an applicable UE radio capability ID for the new UE radio configuration in the selected PLMN the UE radio capability information update needed IE is included in the TRACKING AREA UPDATE REQUEST message. If the UE is in the EMM-CONNECTED mode and the UE changes the radio capability for E-UTRAN or for NG-RAN, the UE may locally release the established NAS signalling connection and enter the EMM-IDLE mode. Then, the UE shall initiate the tracking area updating procedure including a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message. For case l, if the TIN indicates "RAT-related TMSI", the UE shall set the TIN to "P-TMSI" before initiating the tracking area updating procedure. For case r, the "active" flag in the EPS update type IE shall be set to 1. If a UE is only using EPS services with control plane CIoT EPS optimization, the "signalling active" flag in the Additional update type IE shall be set to 1. If the UE is using only control plane CIoT EPS optimization, the case i only applies to the case that the UE has indicated to the network that subsequent to the uplink data transmission a downlink data transmission is expected during the transport of uplink user data via the control plane procedure (see clause 6.6.4). If the UE has to request resources for ProSe direct discovery or Prose direct communication (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), then the UE shall set the "active" flag to 1 in the TRACKING AREA UPDATE REQUEST message. If the UE does not have any established PDN connection, and the inter-system change from N1 mode to S1 mode is not due to emergency services fallback, the "active" flag in the EPS update type IE shall be set to 0. When the UE has user data pending and performs an inter-system change from S101 mode to S1 mode to a tracking area included in the TAI list stored in the UE, the UE shall perform a service request procedure instead of a tracking area updating procedure. When initiating a tracking area updating procedure while in S1 mode, the UE shall use the current EPS NAS integrity key to integrity protect the TRACKING AREA UPDATE REQUEST message, unless the UE is performing inter-system change from N1 mode to S1 mode. In order to indicate its UE specific DRX parameter for WB-S1 mode while in E-UTRAN coverage, the UE shall send the TRACKING AREA UPDATE REQUEST message containing the UE specific DRX parameter in the DRX parameter IE to the network, with the exception of the case if the UE had indicated its DRX parameter for WB-S1 mode (3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]) to the network while in GERAN or UTRAN coverage. In this case, when the UE enters E-UTRAN coverage and initiates a tracking area updating procedure, the UE shall not include the UE specific DRX parameter in the DRX parameter IE in the TRACKING AREA UPDATE REQUEST message. In NB-S1 mode, a UE that wishes to use or change a UE specific DRX parameter in NB-S1 mode shall include its requested value in every TRACKING AREA UPDATE REQUEST message except when initiating the periodic tracking area updating procedure. If the UE supports eDRX and requests the use of eDRX, the UE shall include the extended DRX parameters IE in the TRACKING AREA UPDATE REQUEST message. If the UE supports PSM and requests the use of PSM, the UE shall include the T3324 value IE with a requested timer value in the TRACKING AREA UPDATE REQUEST message. When the UE includes the T3324 value IE and the UE indicates support for extended periodic timer value in the MS network feature support IE, it may also include the T3412 extended value IE to request a particular T3412 value to be allocated. If a UE supporting CIoT EPS optimizations in NB-S1 mode initiates the tracking area updating procedure for EPS services and "SMS only", the UE shall indicate "SMS only" in the Additional update type IE and shall set the EPS update type IE to "TA updating". If the UE supports enhanced discontinuous coverage, then the UE shall set the EDC bit to "Enhanced discontinuous coverage supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. If the network has indicated support for enhanced discontinuous coverage and needs to indicate upcoming availability due to discontinuous coverage, the UE shall include the Unavailability information IE in the TRACKING AREA UPDATE REQUEST message. The UE shall set the unavailability type in the Unavailability information IE to "unavailability due to discontinuous coverage". The UE may include the unavailability period duration or the time to the start of the unavailability period or both in the Unavailability information IE. If the UE supports S1-U data transfer and multiple user plane radio bearers (see 3GPP TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [44], 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]) in NB-S1 mode, then the UE shall set the Multiple DRB support bit to "Multiple DRB supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. If the UE is in NB-S1 mode, then the UE shall set the Control plane CIoT EPS optimization bit to "Control plane CIoT EPS optimization supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. If the UE is capable of NB-N1 mode, then the UE shall set the Control plane CIoT 5GS optimization bit to "Control plane CIoT 5GS optimization supported" in the N1 UE network capability IE of the TRACKING AREA UPDATE REQUEST message. If the UE supports control plane MT-EDT, then the UE shall set the CP-MT-EDT bit to "Control plane Mobile Terminated-Early Data Transmission supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. If the UE supports user plane MT-EDT, then the UE shall set the UP-MT-EDT bit to "User plane Mobile Terminated-Early Data Transmission supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. If the UE supports EPS-UPIP, the UE shall set the EPS-UPIP bit to "EPS-UPIP supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. If the UE has to request resources for V2X communication over PC5 (see 3GPP TS 23.285[ Architecture enhancements for V2X services ] [47]), then the UE shall set the "active" flag to 1 in the TRACKING AREA UPDATE REQUEST message. After sending the TRACKING AREA UPDATE REQUEST message to the MME, the UE shall start timer T3430 and enter state EMM-TRACKING-AREA-UPDATING-INITIATED (see example in figure 5.5.3.2.2.1). If timer T3402 is currently running, the UE shall stop timer T3402. If timer T3411 is currently running, the UE shall stop timer T3411. If timer T3442 is currently running, the UE shall stop timer T3442. For all cases except cases z and zd: 1) if the UE supports neither A/Gb mode nor Iu mode, the UE shall include a valid GUTI in the Old GUTI IE in the TRACKING AREA UPDATE REQUEST message. In addition, the UE shall include Old GUTI type IE with GUTI type set to "Native GUTI"; or 2) if the UE supports A/Gb mode or Iu mode or both, the UE shall handle the Old GUTI IE as follows: - If the TIN indicates "P-TMSI" and the UE holds a valid native P-TMSI and RAI, the UE shall map the P-TMSI and RAI into the Old GUTI IE, and include Old GUTI type IE with GUTI type set to "Mapped GUTI". If a P-TMSI signature is associated with the P-TMSI, the UE shall include it in the Old P-TMSI signature IE. Additionally, if the UE holds a valid GUTI, the UE shall indicate the GUTI in the Additional GUTI IE. NOTE 5: The mapping of the P-TMSI and RAI to the GUTI is specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. - If the TIN indicates "GUTI" or "RAT-related TMSI" and the UE holds a valid GUTI, the UE shall indicate the GUTI in the Old GUTI IE, and include Old GUTI type IE with GUTI type set to "Native GUTI". If a UE has established PDN connection(s) and uplink user data pending to be sent via user plane when it initiates the tracking area updating procedure, or uplink signalling not related to the tracking area updating procedure when the UE does not support control plane CIoT EPS optimization, it may set the "active" flag in the TRACKING AREA UPDATE REQUEST message to indicate the request to establish the user plane to the network and to keep the NAS signalling connection after the completion of the tracking area updating procedure. If a UE is using EPS services with control plane CIoT EPS optimization and has user data pending to be sent via control plane over MME but no user data pending to be sent via user plane, or uplink signalling not related to the tracking area updating procedure, the UE may set the "signalling active" flag in the TRACKING AREA UPDATE REQUEST message to indicate the request to keep the NAS signalling connection after the completion of the tracking area updating procedure. For all cases except cases z and zd, if the UE has a current EPS security context, the UE shall include the eKSI (either KSIASME or KSISGSN) in the NAS Key Set Identifier IE in the TRACKING AREA UPDATE REQUEST message. Otherwise, the UE shall set the NAS Key Set Identifier IE to the value "no key is available". If the UE has a current EPS security context, the UE shall integrity protect the TRACKING AREA UPDATE REQUEST message with the current EPS security context. Otherwise the UE shall not integrity protect the TRACKING AREA UPDATE REQUEST message. When the tracking area updating procedure is initiated in EMM-IDLE mode to perform an inter-system change from A/Gb mode or Iu mode to S1 mode and the TIN is set to "P-TMSI", the UE shall include the GPRS ciphering key sequence number applicable for A/Gb mode or Iu mode and a nonceUE in the TRACKING AREA UPDATE REQUEST message. When the tracking area updating procedure is initiated in EMM-CONNECTED mode to perform an inter-system change from A/Gb mode or Iu mode to S1 mode, the UE shall derive the EPS NAS keys from the mapped K'ASME using the selected NAS algorithms, nonceMME and KSISGSN (to be associated with the mapped K'ASME) provided by lower layers as indicated in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]. The UE shall reset both the uplink and downlink NAS COUNT counters of the mapped EPS security context which shall be taken into use. If the UE has a non-current native EPS security context, the UE shall include the KSIASME in the Non-current native NAS key set identifier IE and its associated GUTI, as specified above, either in the Old GUTI IE or in the Additional GUTI IE of the TRACKING AREA UPDATE REQUEST message. The UE shall set the TSC flag in the Non-current native NAS key set identifier IE to "native security context". For the case z, if upper layers have indicated that IMS signalling or IMS emergency signalling was already ongoing in N1 mode before performing the inter-system change from N1 mode to S1 mode, or if the inter-system change from N1 mode to S1 mode is due to emergency services fallback, the "active" flag in the EPS update type IE shall be set to 1. For the case z, the TRACKING AREA UPDATE REQUEST message shall be integrity protected using the 5G NAS security context available in the UE. If there is no valid 5G NAS security context available in the UE, the TRACKING AREA UPDATE REQUEST message shall be sent without integrity protection. The UE shall include a GUTI, mapped from 5G-GUTI (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58] and 3GPP TS 23.003[ Numbering, addressing and identification ] [2]), in the Old GUTI IE in the TRACKING AREA UPDATE REQUEST message. In addition, the UE shall include Old GUTI type IE with GUTI set to "Native GUTI", and the UE shall include a UE status IE with a 5GMM registration status set to "UE is in 5GMM-REGISTERED state". Additionally, if the UE holds a valid GUTI, the UE shall indicate the GUTI in the Additional GUTI IE. NOTE 6: The value of the EMM registration status included by the UE in the UE status IE is not used by the MME. For the case zd, the TRACKING AREA UPDATE REQUEST message shall be integrity protected using the mapped EPS security context as derived when triggering the handover to E-UTRAN (see clause 4.4.2.2). The UE shall include a GUTI, mapped from 5G-GUTI (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58] and 3GPP TS 23.003[ Numbering, addressing and identification ] [2]), in the Old GUTI IE in the TRACKING AREA UPDATE REQUEST message. In addition, the UE shall include Old GUTI type IE with GUTI set to "Native GUTI", and the UE shall include a UE status IE with a 5GMM registration status set to "UE is in 5GMM-REGISTERED state". Additionally, if the UE holds a valid GUTI, the UE shall indicate the GUTI in the Additional GUTI IE. If the UE has a non-current native EPS security context, the UE shall include the KSIASME in the Non-current native NAS key set identifier IE of the TRACKING AREA UPDATE REQUEST message. The UE shall set the TSC flag in the Non-current native NAS key set identifier IE to "native security context". NOTE 7: The value of the EMM registration status included by the UE in the UE status IE is not used by the MME. When the tracking area updating procedure is initiated in EMM-IDLE mode, the UE may also include an EPS bearer context status IE in the TRACKING AREA UPDATE REQUEST message, indicating which EPS bearer contexts are active in the UE. The UE shall include the EPS bearer context status IE in TRACKING AREA UPDATE REQUEST message: a) for the case f; b) for the case s; c) for the case z; d) if the UE has established PDN connection(s) of "non IP" or Ethernet PDN type; and e) if the UE: 1) locally deactivated at least one dedicated EPS bearer context upon an inter-system mobility from WB-S1 mode to NB-S1 mode in EMM-IDLE mode; 2) locally deactivated at least one dedicated EPS bearer context upon an inter-system change from WB-N1 mode to NB-S1 mode in EMM-IDLE mode for the UE operating in single-registration mode (see clause 6.4.2.1); or 3) locally deactivated at least one default EPS bearer context upon an inter-system change from N1 mode to NB-S1 mode in EMM-IDLE mode for the UE operating in single-registration mode (see clause 6.5.0). If the UE initiates the first tracking area updating procedure following an attach in A/Gb mode or Iu mode, the UE shall include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message. If the UE initiates the first tracking area updating procedure following an initial registration in N1 mode and the UE is operating in the single-registration mode, the UE shall include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports SRVCC to GERAN/UTRAN, the UE shall set the SRVCC to GERAN/UTRAN capability bit in the MS network capability IE to "SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported". For all cases except case b, if the UE supports vSRVCC from S1 mode to Iu mode, then the UE shall set the H.245 after handover capability bit in the UE network capability IE to "H.245 after SRVCC handover capability supported" and additionally set the SRVCC to GERAN/UTRAN capability bit in the MS network capability IE to "SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported" in the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports ProSe direct discovery, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe direct discovery bit to "ProSe direct discovery supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports ProSe direct communication, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe direct communication bit to "ProSe direct communication supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports acting as a ProSe UE-to-network relay, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe UE-to-network relay bit to "acting as a ProSe UE-to-network relay supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. If the UE supports NB-S1 mode, Non-IP or Ethernet PDN type, N1 mode, UAS services, URSP provisioning in EPS or if the UE supports DNS over (D)TLS (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), then the UE shall support the Extended protocol configuration options IE. NOTE 8: Support of DNS over (D)TLS is based on the informative requirements as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. For all cases except case b, if the UE supports the Extended protocol configuration options IE, then the UE shall set the ePCO bit to "extended protocol configuration options supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. If the UE supports providing PDU session ID in the Protocol configuration options IE or the Extended protocol configuration option IE when its N1 mode capability is disabled, then the UE shall set the ePCO bit to "extended protocol configuration options supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports V2X communication over E-UTRAN-PC5, then the UE shall set the V2X PC5 bit to "V2X communication over E-UTRAN-PC5 supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports V2X communication over NR-PC5, then the UE shall set the V2X NR-PC5 bit to "V2X communication over NR-PC5 supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports the restriction on use of enhanced coverage, then the UE shall set the RestrictEC bit to "Restriction on use of enhanced coverage supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports the control plane data back-off timer T3448, the UE shall set the CP backoff bit to "backoff timer for transport of user data via the control plane supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports dual connectivity with NR, then the UE shall set the DCNR bit to "dual connectivity with NR supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message and shall include the UE additional security capability IE in the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports SGC, then the UE shall set the SGC bit to "service gap control supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports signalling for a maximum number of 15 EPS bearer contexts, then the UE shall set the 15 bearers bit to "Signalling for a maximum number of 15 EPS bearer contexts supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the MUSIM UE supports the NAS signalling connection release, then the UE shall set the NAS signalling connection release bit to "NAS signalling connection release supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message otherwise the UE shall not set the NAS signalling connection release bit to "NAS signalling connection release supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the MUSIM UE supports the paging indication for voice services, then the UE shall set the paging indication for voice services bit to "paging indication for voice services supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message otherwise the UE shall not set the paging indication for voice services bit to "paging indication for voice services supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the MUSIM UE supports the reject paging request, then the UE shall set the reject paging request bit to "reject paging request supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message otherwise the UE shall not set the reject paging request bit to "reject paging request supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the MUSIM UE sets: - the reject paging request bit to "reject paging request supported"; - the NAS signalling connection release bit to "NAS signalling connection release supported"; or - both of them; and supports the paging restriction, then the UE shall set the paging restriction bit to "paging restriction supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message otherwise the UE shall not set the paging restriction bit to "paging restriction supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the MUSIM UE supports the paging timing collision control, then the UE shall set the paging timing collision control bit to "paging timing collision control supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message otherwise the UE shall not set the paging timing collision control bit to "paging timing collision control supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except cases b and zb, if the UE supports ciphered broadcast assistance data and the UE needs to obtain new ciphering keys, the UE shall include the Additional information requested IE with the CipherKey bit set to "ciphering keys for ciphered broadcast assistance data requested" in the TRACKING AREA UPDATE REQUEST message. For case ee, the UE shall include the Additional information requested IE with the CipherKey bit set to "ciphering keys for ciphered broadcast assistance data requested" in the TRACKING AREA UPDATE REQUEST message. For case a, if the UE supports ciphered broadcast assistance data and the UE detects entering a tracking area for which one or more ciphering keys stored at the UE is not applicable, the UE should include the Additional information requested IE with the CipherKey bit set to "ciphering keys for ciphered broadcast assistance data requested" in the TRACKING AREA UPDATE REQUEST message. For case b, if the UE supports ciphered broadcast assistance data and the remaining validity time for one or more ciphering keys stored at the UE is less than timer T3412, the UE should include the Additional information requested IE with the CipherKey bit set to "ciphering keys for ciphered broadcast assistance data requested" in the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports N1 mode for 3GPP access, the UE shall set the N1mode bit to "N1 mode for 3GPP access supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message and shall include the UE additional security capability IE in the TRACKING AREA UPDATE REQUEST message. For all cases except case b, in WB-S1 mode, if the UE supports RACS the UE shall set the RACS bit to "RACS supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For cases n, za, zc and zh, in WB-S1 mode, if the UE supports RACS and the UE has an applicable UE radio capability ID for the new UE radio configuration in the selected PLMN, the UE shall set the URCIDA bit to "UE radio capability ID available" in the UE radio capability ID availability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except cases b, n, za, zc and zh, in WB-S1 mode, if the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected PLMN, the UE shall set the URCIDA bit to "UE radio capability ID available" in the UE radio capability ID availability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except case b, if the UE supports WUS assistance, then the UE shall set the WUSA bit to "WUS assistance supported" in the UE network capability IE, and if the UE is not attaching for emergency bearer services, the UE may include its UE paging probability information in the Requested WUS assistance information IE in the TRACKING AREA UPDATE REQUEST message. For all cases except case a, except case b, for a MUSIM UE if the UE needs to indicate an IMSI offset value to the network and the network has indicated to the UE that it supports paging timing collision control, the UE shall include the IMSI offset value in the Requested IMSI offset IE in the TRACKING AREA UPDATE REQUEST message. For case a, MUSIM UE may include the IMSI offset value in the Requested IMSI offset IE in the TRACKING AREA UPDATE REQUEST message even if the network has not indicated that it supports paging timing collision control. If the network supports the NAS signalling connection release and the MUSIM UE requests the network to release the NAS signalling connection, the UE shall set Request type to "NAS signalling connection release" in the UE request type IE and, if the network supports the paging restriction, may set the paging restriction preference in the Paging restriction IE in the TRACKING AREA UPDATE REQUEST message. In addition, the UE shall - set the "active" flag to 0 in the EPS update type IE; and - set the "signalling active" flag to 0 in the Additional update type IE, if the Additional update type IE is included. NOTE 9: If the network has already indicated support for NAS signalling connection release in the current stored tracking area list and the UE doesn't have a PDN connection for emergency bearer services established, the MUSIM UE is allowed to request the network to release the NAS signalling connection during tracking area updating procedure that is due to mobility to a tracking area outside the current tracking area list even before detecting whether the network supports the NAS signalling connection release in the new tracking area. NOTE 10: If the network has already indicated support for paging restriction in the current stored tracking area list and the UE doesn't have a PDN connection for emergency bearer services established, the MUSIM UE is allowed to include paging restriction together with the request to the network to release the NAS signalling connection during tracking area updating procedure that is due to mobility to a tracking area outside the current tracking area list even before detecting whether the network supports the paging restriction in the new tracking area. Figure 5.5.3.2.2.1: Tracking area updating procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.3.2.2 |
1,349 | 5.16.5 Multimedia Priority Services | TS 22.153[ Multimedia priority service ] [24] specifies the service requirements for Multimedia Priority Service (MPS). MPS allows Service Users (as per TS 22.153[ Multimedia priority service ] [24]) priority access to system resources in situations such as during congestion, creating the ability to deliver or complete sessions of a high priority nature. Service Users are government-authorized personnel, emergency management officials and/or other authorized users. MPS supports priority sessions on an "end-to-end" priority basis. MPS is based on the ability to invoke, modify, maintain and release sessions with priority, and deliver the priority media packets under network congestion conditions. MPS is supported in a roaming environment when roaming agreements are in place and where regulatory requirements apply. NOTE 1: If a session terminates on a server in the Internet (e.g. web-based service), then the remote end and the Internet transport are out of scope for this specification. MPS is supported for Service Users using UEs connecting via 3GPP access. MPS is also supported for Service Users using UEs that support connecting via Trusted or Untrusted non-3GPP access via WLAN for MPS. N3IWF selection is according to clause 6.3.6 for PLMN access. A Service User may use an MPS-subscribed UE or any other UE to obtain MPS. An MPS-subscribed UE obtains priority access to the Radio Access Network by using the Unified Access Control mechanism according to TS 22.261[ Service requirements for the 5G system ] [2]. This mechanism provides preferential access to UEs based on its assigned Access Identity. If an MPS-subscribed UE belongs to the special Access Identity as defined in TS 22.261[ Service requirements for the 5G system ] [2], the UE has preferential access to the network compared to ordinary UEs in periods of congestion. MPS subscription allows users to receive priority services, if the network supports MPS. The same MPS subscription applies to access via 3GPP access and non-3GPP access via WLAN. MPS subscription entitles a USIM with special Access Identity. MPS subscription includes indication for support of priority PDU connectivity service including MPS for Data Transport Service and IMS priority service support for the end user. Priority Level regarding QoS Flows and IMS are also part of the MPS subscription information. The usage of Priority Level is defined in TS 22.153[ Multimedia priority service ] [24], TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15]. NOTE 2: The same MPS subscription in the UDM and/or on the USIM is used for priority treatment of 3GPP procedures when the access is WLAN. NOTE 3: The term "Priority PDU connectivity services" is used to refer to 5G System functionality that corresponds to the functionality as provided by LTE/EPC Priority EPS bearer services in clause 4.3.18.3 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. MPS includes signalling priority and media priority. All MPS-subscribed UEs get priority for QoS Flows (e.g. used for IMS signalling) when established to the DN that is configured to have priority for a given Service User by setting MPS-appropriate values in the QoS profile in the UDM. Service Users are treated as On Demand MPS subscribers or not, based on regional/national regulatory requirements. On Demand service is based on Service User invocation/revocation explicitly and applied to the media QoS Flows being established. When not On Demand MPS service does not require invocation, and provides priority treatment for all QoS Flows only to the DN that is configured to have priority for a given Service User after attachment to the 5G network. MPS for Data Transport Service is an on-demand service that may be invoked/revoked by an authorized Service User using a UE with a subscription for MPS (i.e. according to its MPS profile), or using a UE that does not have a subscription for MPS (using methods not in scope of this specification). MPS for Data Transport Service requires explicit invocation. The Service User invokes the service by communicating with an AF. The authorization of an MPS for Data Transport Service request is done by the AF or the PCF according to clause 6.1.3.11 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. Upon successful authorization, the PCF performs the necessary actions to achieve appropriate ARP and 5QI settings for the QoS Flows (see clause 6.1.3.11 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). MPS for Data Transport Service enables the prioritization of all traffic on the QoS Flow associated with the default QoS rule and other QoS Flows upon AF request. The QoS modification to the QoS Flow associated with the default QoS rule and other QoS Flows is done based on operator policy and regulatory rules by means of local PCF configuration. NOTE 4: According to regional/national regulatory requirements and operator policy, On-Demand MPS (including MPS for Data Transport Service) Service Users can be assigned the highest priority. NOTE 5: If no configuration is provided, MPS for Data Transport Service applies only to the QoS Flow associated with the default QoS rule. NOTE 6: MPS for DTS controls the priority of traffic on QoS Flows independent of the application(s) being used. Other mechanisms (e.g. Priority PDU connectivity service) can be used to control the priority of traffic on other QoS Flows under the control of specific data application(s), based on operator policy. NOTE 7: MPS for Data Transport Service can be applied to any DNN other than the well-known DNN for IMS. For MPS for Data Transport Service, the AF may also create an SDF for priority signalling between the UE and the AF (see clause 6.1.3.11 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). Priority treatment is applicable to IMS based multimedia services and Priority PDU connectivity service including MPS for Data Transport Service. Priority treatment for MPS includes priority message handling, including priority treatment during authentication, security, and Mobility Management procedures. Priority treatment for MPS session requires appropriate ARP and 5QI (plus 5G QoS characteristics) setting for QoS Flows according to the operator's policy. NOTE 8: Use of QoS Flows for MPS with QoS characteristics signalled as part of QoS profile enables the flexible assignment of 5G QoS characteristics (e.g. Priority Level) for MPS. When an MPS session is requested by a Service User, the following principles apply in the network: - QoS Flows employed in an MPS session shall be assigned ARP value settings appropriate for the priority of the Service User. - Setting ARP pre-emption capability and vulnerability for MPS QoS Flows, subject to operator policies and depending on national/regional regulatory requirements. - Pre-emption of non-Service Users over Service Users during network congestion situation, subject to operator policy and national/regional regulations. The terminating network identifies the priority of the MPS session and applies priority treatment, including paging with priority, to ensure that the MPS session can be established with priority to the terminating user (either a Service User or normal user). MPS priority mechanisms can be classified as subscription-related, invocation-related, and those applied to existing QoS Flows. Subscription related mechanisms, as described in clause 5.22.2, are further divided into two groups: those which are always applied and those which are conditionally applied. Invocation-related mechanisms, as described in clause 5.22.3, are further divided into three groups: those that apply for mobile originated SIP call/sessions, those that apply for mobile terminated SIP call/sessions, and those that apply for the Priority PDU connectivity services including MPS for Data Transport Service. Methods applied to existing QoS Flows focus on handover and congestion control and are described in clause 5.22.4. NOTE 9: The network can hide its topology from the AF supporting MPS for Data Transport Service. At the same time, the UE needs to provide its locally known IP address to the AF supporting MPS for Data Transport Service to support interactions with the applicable PCF. Thus, there can be no NAT of the UE IP address between the UPF and the AF supporting MPS for Data Transport Service. For WLAN access, the UE may notify the TNAN/N3IWF of its MPS subscription before the NAS Registration Request. Based on operator policy, the TNAN/N3IWF may use this indication to provide this UE with priority treatment in the case of congestion/overload before receipt of the NAS Registration Request with an MPS priority establishment cause. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.5 |
1,350 | 5.7.4.1 HARQ feedback | Sidelink HARQ feedback uses PSFCH and can be operated in one of two options. In one option, which can be configured for unicast and groupcast, PSFCH transmits either ACK or NACK using a resource dedicated to a single PSFCH transmitting UE. In another option, which can be configured for groupcast, PSFCH transmits NACK, or no PSFCH signal is transmitted, on a resource that can be shared by multiple PSFCH transmitting UEs. The latter option is not supported for sidelink in unlicensed spectrum. In sidelink resource allocation mode 1, a UE which received PSFCH can report sidelink HARQ feedback to gNB via PUCCH or PUSCH. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.4.1 |
1,351 | 4.7.3.2.4 Combined GPRS attach not accepted by the network | If the attach request can neither be accepted by the network for GPRS nor for non-GPRS services, an ATTACH REJECT message is transferred to the MS. The MS receiving the ATTACH REJECT message containing a reject cause other than GMM cause value #25 or the message is integrity protected, shall stop the timer T3310, and for all causes except #7, #12, #14, #15, #22 and #25 deletes the list of "equivalent PLMNs". If the ATTACH REJECT message containing GMM cause value #25 was received without integrity protection, then the MS shall discard the message. If the attach request is rejected due to NAS level mobility management congestion control, the network shall set the GMM cause value to #22 "congestion" and assign a back-off timer T3346. The MS shall then take one of the following actions depending upon the reject cause: # 3 (Illegal MS); # 6 (Illegal ME), or # 8 (GPRS services and non-GPRS services not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The new GMM state is GMM-DEREGISTERED.NO-IMSI. The new MM state is MM IDLE. The MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed or the timer T3245 expires as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. NOTE 1: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9 for reject cause #8 If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the combined attach procedure is rejected with the EMM cause with the same value. # 7 (GPRS services not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM is removed. The new GMM state is GMM-DEREGISTERED; the MM state is MM IDLE. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. NOTE 2: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9. A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network. A GPRS MS operating in MS operation mode A or B shall proceed with the appropriate MM specific procedure according to the MM service state. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the combined attach procedure is rejected with the EMM cause with the same value. # 11 (PLMN not allowed); The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number stored, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall reset the GPRS attach attempt counter and changes to state GMM-DEREGISTERED. The MS shall set the update status to U3 ROAMING NOT ALLOWED, reset the location update attempt counter and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. The MS shall store the PLMN identity in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value. The MS shall start timer T3340 as described in subclause 4.7.1.9. The MS shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the combined attach procedure is rejected with the EMM cause with the same value. # 12 (Location area not allowed); The MS shall delete any RAI, P-TMSI, P-TMSI signature GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. The MS shall set the update status to U3 ROAMING NOT ALLOWED, reset the location update attempt counter and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. The MS shall store the LAI in the list of "forbidden location areas for regional provision of service". The MS shall start timer T3340 as described in subclause 4.7.1.9. The MS shall perform a cell selection according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. NOTE 3: The cell selection procedure is not applicable for an MS in GAN mode. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the combined attach procedure is rejected with the EMM cause with the same value. # 13 (Roaming not allowed in this location area); The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE or optionally to GMM-DEREGISTERED.PLMN-SEARCH. The MS shall set the update status to U3 ROAMING NOT ALLOWED, reset the location update attempt counter and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. The mobile station shall store the LAI in the list of "forbidden location areas for roaming". The MS shall start timer T3340 as described in subclause 4.7.1.9. The MS shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the combined attach procedure is rejected with the EMM cause with the same value. # 14 (GPRS services not allowed in this PLMN); The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall reset the GPRS attach attempt counter and shall change to state GMM-DEREGISTERED. The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific PS-attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value. As an implementation option, a GPRS MS operating in operation mode A or B may perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If an MS in GAN mode performs a PLMN selection, it shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause is: - On the "User Controlled PLMN Selector with Access Technology"; - On the "Operator Controlled PLMN Selector with Access Technology" list; - On the "PLMN Selector" list for an MS using a SIM/USIM without access technology information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are not present); or - A PLMN identified as equivalent to any PLMN, within the same country, contained in the lists above. If the MS does not perform a PLMN selection then a GPRS MS operating in MS operation mode A or B which is not yet IMSI attached for CS services in the network shall then perform an IMSI attach for non-GPRS services according to the conditions for the MM IMSI attach procedure (see subclause 4.4.3). A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network. A GPRS MS operating in MS operation mode A or B shall proceed with the appropriate MM specific procedure according to the MM service state. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the combined attach procedure is rejected with the EMM cause with the same value. # 15 (No Suitable Cells In Location Area); The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. The MS shall set the update status to U3 ROAMING NOT ALLOWED, reset the location update attempt counter and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. The MS shall store the LAI in the list of "forbidden location areas for roaming". The MS shall start timer T3340 as described in subclause 4.7.1.9. The MS shall search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]. NOTE 4: The cell selection procedure is not applicable for an MS in GAN mode. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the combined attach procedure is rejected with the EMM cause with the same value. # 22 (Congestion); If the T3346 value IE is present in the ATTACH REJECT message and the value indicates that this timer is neither zero nor deactivated, the MS shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the MS for this case is specified in subclause 4.7.3.1.5. The MS shall abort the attach procedure, reset the GPRS attach attempt counter, set the GPRS update status to GU2 NOT UPDATED and enter state GMM-DEREGISTERED.ATTEMPTING-TO-ATTACH. The MS shall stop timer T3346 if it is running. If the ATTACH REJECT message is integrity protected, the MS shall start timer T3346 with the value provided in the T3346 value IE. If the ATTACH REJECT message is not integrity protected, the MS shall start timer T3346 with a random value from the default range specified in table 11.3a. The MS stays in the current serving cell and applies the normal cell reselection process. The attach procedure is started, if still necessary, when timer T3346 expires or is stopped. A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the attach procedure is rejected with the EMM cause with the same value. # 25 (Not authorized for this CSG) Cause #25 is only applicable in UTRAN Iu mode and when received from a CSG cell. Other cases are considered as abnormal cases and the specification of the mobile station behaviour is given in subclause 4.7.3.2.5. The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. If the CSG ID and associated PLMN identity of the cell where the MS has sent the ATTACH REQUEST message are contained in the Allowed CSG list stored in the MS, the MS shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list. If the CSG ID and associated PLMN identity of the cell where the MS has sent the ATTACH REQUEST message are contained in the Operator CSG list, the MS shall proceed as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] subclause 3.1A. The MS shall start timer T3340 as described in subclause 4.7.1.9. If the MS is IMSI attached for non-GPRS services, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE. The MS shall search for a suitable cell according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the combined attach procedure is rejected with the EMM cause with the same value. Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is specified in subclause 4.7.3.2.5. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.2.4 |
1,352 | 10.4 Mandatory field missing | The UE shall: 1> if the message includes a field that is mandatory to include in the message (e.g. because conditions for mandatory presence are fulfilled) and that field is absent or treated as absent: 2> if the RRC message was not received on DCCH or CCCH; or 2> if the PC5 RRC message was not received on SCCH: 3> if the field concerns a (sub-field of) an entry of a list (i.e. a SEQUENCE OF): 4> treat the list as if the entry including the missing or not comprehended field was absent; 3> else if the field concerns a sub-field of another field, referred to as the 'parent' field i.e. the field that is one nesting level up compared to the erroneous field: 4> consider the 'parent' field to be set to a not comprehended value; 4> apply the generic error handling to the subsequent 'parent' field(s), until reaching the top nesting level i.e. the message level; 3> else (field at message level): 4> ignore the message. NOTE 1: The error handling defined in these clauses implies that the UE ignores a message with the message type or version set to a not comprehended value. NOTE 2: The nested error handling for messages received on logical channels other than DCCH, CCCH and SCCH applies for errors in extensions also, even for errors that can be regarded as invalid network operation e.g. the network not observing conditional presence. NOTE 3: UE behaviour on receipt of an RRC message on DCCH or CCCH or a PC5 RRC message on SCCH that does not include a field that is mandatory (e.g. because conditions for mandatory presence are fulfilled) is unspecified. The following ASN.1 further clarifies the levels applicable in case of nested error handling for errors in extension fields. -- /example/ ASN1START -- Example with extension addition group ItemInfoList ::= SEQUENCE (SIZE (1..max)) OFItemInfo ItemInfo ::= SEQUENCE { itemIdentity INTEGER (1..max), field1 Field1, field2 Field2 OPTIONAL, -- Need N ... [[ field3-r9 Field3-r9 OPTIONAL, -- Cond Cond1 field4-r9 Field4-r9 OPTIONAL -- Need N ]] } -- Example with traditional non-critical extension (empty sequence) BroadcastInfoBlock1 ::= SEQUENCE { itemIdentity INTEGER (1..max), field1 Field1, field2 Field2 OPTIONAL, -- Need N nonCriticalExtension BroadcastInfoBlock1-v940-IEs OPTIONAL } BroadcastInfoBlock1-v940-IEs::= SEQUENCE { field3-r9 Field3-r9 OPTIONAL, -- Cond Cond1 field4-r9 Field4-r9 OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL -- Need S } -- ASN1STOP The UE shall, apply the following principles regarding the levels applicable in case of nested error handling: - an extension addition group is not regarded as a level on its own. E.g. in the ASN.1 extract in the previous, a error regarding the conditionality of field3 would result in the entire itemInfo entry to be ignored (rather than just the extension addition group containing field3 and field4); - a traditional nonCriticalExtension is not regarded as a level on its own. E.g. in the ASN.1 extract in the previous, an error regarding the conditionality of field3 would result in the entire BroadcastInfoBlock1 to be ignored (rather than just the non-critical extension containing field3 and field4). | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 10.4 |
1,353 | 8.3.1 Call Control | The mobile station and the network shall ignore a Call Control message received with TI EXT bit = 0. Otherwise, if the TI EXT bit =1 or no extension is used, the behaviour described below shall be followed. The mobile station and network shall reject a SETUP, EMERGENCY SETUP or START CC message received with octet 1 part of the TI value coded as "111" by sending RELEASE COMPLETE with cause #81 "Invalid transaction identifier value" The TI value in RELEASE COMPLETE shall be the complete TI value including the extension octet from the message that caused the rejection. Any message other than SETUP, EMERGENCY SETUP or START CC received with octet 1 part of the TI value coded as "111" shall be ignored. For a call control message received with octet 1 part of the TI value not coded as "111", the following procedures shall apply: a) For a network that does not support the "Network initiated MO call" option and for all mobile stations: Whenever any call control message except EMERGENCY SETUP, SETUP or RELEASE COMPLETE is received specifying a transaction identifier which is not recognized as relating to an active call or to a call in progress, the receiving entity shall send a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" using the received transaction identifier value and remain in the Null state. For a network that does support the "Network initiated MO call" option $(CCBS)$: Whenever any call control message except EMERGENCY SETUP, SETUP, START CC or RELEASE COMPLETE is received specifying a transaction identifier which is not recognized as relating to an active call or to a call in progress, the receiving entity shall send a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" using the received transaction identifier value and remain in the Null state. b) When a RELEASE COMPLETE message is received specifying a transaction identifier which is not recognized as relating to an active call or to a call in progress, the MM connection associated with that transaction identifier shall be released. c) For a network that does not support the "Network initiated MO call" option and for all mobile stations: When an EMERGENCY SETUP or, a SETUP message is received specifying a transaction identifier which is not recognized as relating to an active call or to a call in progress, and with a transaction identifier flag incorrectly set to "1", this message shall be ignored. For a network that does support the "Network initiated MO call" option $(CCBS)$: When an EMERGENCY SETUP, a START CC or, a SETUP message is received specifying a transaction identifier which is not recognised as relating to an active call or to a call in progress, and with a transaction identifier flag incorrectly set to "1", this message shall be ignored. d) When a SETUP message is received by the mobile station specifying a transaction identifier which is recognized as relating to an active call or to a call in progress, this SETUP message shall be ignored. e) For a network that does not support the "Network initiated MO call" option: When an EMERGENCY SETUP message or a SETUP message is received by the network specifying a transaction identifier which is recognized as relating to an active call or to a call in progress, this message need not be treated and the network may perform other actions. For a network that does support the "Network initiated MO call" option $(CCBS)$: When an EMERGENCY SETUP message or a START CC message is received by the network specifying a transaction identifier which is recognised as relating to an active call or to a call in progress, this message need not be treated and the network may perform other actions. The same applies to a SETUP message unless the transaction has been established by a START_CC message and the network is in the "recall present" state (N0.6). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.3.1 |
1,354 | 10.5.1.15 MS network feature support | The purpose of the MS network feature support information element is to indicate support of mobility management parameters during the tracking area updating, location updating, routing area updating, IMSI attach, GPRS attach, and EPS attach procedures. The MS network feature support information element is coded as shown in figure 10.5.1.15/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.1.15/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The MS network feature support information element is a type 1 information element. Figure 10.5.1.15/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MS network feature support information element Table 10.5.1.15/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MS network feature support information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.1.15 |
1,355 | 5.5.3.2.6 Abnormal cases in the UE | The following abnormal cases can be identified: a) Access barred because of access class barring, EAB, ACDC or NAS signalling connection establishment rejected by the network without "Extended wait time" received from lower layers In WB-S1 mode, if the tracking area updating procedure is started in response to a paging request from the network, access class barring, EAB or ACDC is not applicable. In NB-S1 mode, if the tracking area updating procedure is started in response to a paging request from the network, access barring is not applicable. In WB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the tracking area updating procedure shall not be started. The UE stays in the current serving cell and applies the normal cell reselection process. The tracking area updating procedure is started as soon as possible and if still necessary, e.g. when access for "originating signalling" is granted on the current cell or when the UE moves to a cell where access for "originating signalling" is granted. In NB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the tracking area updating procedure shall not be started. The UE stays in the current serving cell and applies the normal cell reselection process. Further UE behaviour is implementation specific, e.g. the tracking area updating procedure is started again after an implementation dependent time. In NB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), a request for an exceptional event is received from the upper layers, then the tracking area updating procedure shall be started. NOTE 1: In NB-S1 mode, the EMM layer cannot receive the access barring alleviation indication from the lower layers (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). If access is barred because of access class barring for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]) and if: - one of the MO MMTEL voice call is started, MO MMTEL video call is started or MO SMSoIP is started conditions is satisfied; - the upper layers request to send a mobile originated SMS over NAS or SMS over S102; or - the upper layers request user plane radio resources, ACDC is applicable to the request and the UE supports ACDC. then the tracking area updating procedure shall be started according to clause 5.5.3.2.2. The call type used shall be per annex D of this document. NOTE 2: If more than one of MO MMTEL voice call is started, MO MMTEL video call is started or MO SMSoIP is started conditions are satisfied, it is left to UE implementation to determine the call type based on Annex D of this document. If access is barred for a certain ACDC category (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), and if the upper layers request user plane radio resources for a higher ACDC category and the UE supports ACDC, then the tracking area updating procedure shall be started according to clause 5.5.3.2.2. If an access request for an uncategorized application is barred due to ACDC (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), and if the upper layers request user plane radio resources for a certain ACDC category and the UE supports ACDC, then the tracking area updating procedure shall be started according to clause 5.5.3.2.2. If the trigger for the tracking area updating procedure is the response to a paging request from the network and the NAS signalling connection establishment is rejected by the network, the tracking area updating procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process. The tracking area updating procedure may be started if it is still necessary when access for "terminating calls" is granted or because of a cell change. aa) Lower layer failure to establish the RRC connection and: - the UE is in its HPLMN or in an EHPLMN (if the EHPLMN list is present); - the tracking area updating request is not for initiating a PDN connection for emergency bearer services; - the UE does not have a PDN connection for for emergency bearer services; - the UE supports being configured with CustomLLFailureRetry as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]); and - CustomLLFailureRetry leaf is present as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]); The UE shall increment the UE implementation specific attempt counter. If the UE implementation specific attempt counter is less than the value of MaxMinRetry, the UE shall start T3411 with the duration of MinRetryTimer. If the UE implementation specific attempt counter is equal to the value of MaxMinRetry, the UE shall start T3402 with the duration of MaxRetryTimer. The tracking area updating procedure shall be aborted, and the UE shall proceed as described below. b) Lower layer failure not covered in case aa) or release of the NAS signalling connection without "Extended wait time" and without "Extended wait time CP data" received from lower layers before the TRACKING AREA UPDATE ACCEPT or TRACKING AREA UPDATE REJECT message is received The tracking area updating procedure shall be aborted, and the UE shall proceed as described below. c) T3430 timeout The UE shall abort the procedure. The NAS signalling connection, if any, shall be released locally. NOTE 3: The NAS signalling connection can also be released if the UE deems that the network has failed the authentication check as specified in clause 5.4.2.7. The UE shall proceed as described below. d) TRACKING AREA UPDATE REJECT, other causes than those treated in clause 5.5.3.2.5, and cases of EMM cause values #22, #25, #31 and #78, if considered as abnormal cases according to clause 5.5.3.2.5 If the tracking area updating request is not for initiating a PDN connection for emergency bearer services, upon reception of the EMM causes #95, #96, #97, #99 and #111 the UE should set the tracking area updating attempt counter to 5. The UE shall proceed as described below. e) Change of cell into a new tracking area If a cell change into a new tracking area occurs before the tracking area updating procedure is completed, the tracking area updating procedure shall be aborted and re-initiated immediately. The UE shall set the EPS update status to EU2 NOT UPDATED. The UE shall proceed as described below. f) Tracking area updating and detach procedure collision EPS detach containing detach type "re-attach required" or "re-attach not required": If the UE receives a DETACH REQUEST message before the tracking area updating procedure has been completed, the tracking area updating procedure shall be aborted and the detach procedure shall be progressed. If the DETACH REQUEST message contains detach type "re-attach not required" and EMM cause #2 "IMSI unknown in HSS", the UE will follow the procedure as described below for the detach type "IMSI detach". EPS detach containing detach type "IMSI detach": If the UE receives a DETACH REQUEST message before the tracking area updating procedure has been completed, the DETACH REQUEST message shall be ignored and tracking area updating procedure shall be progressed. The UE shall proceed as described below. g) Tracking area updating and GUTI reallocation procedure collision If the UE receives a GUTI REALLOCATION COMMAND message before the tracking area updating procedure has been completed, this message shall be ignored and the tracking area updating procedure shall be progressed. h) Transmission failure of TRACKING AREA UPDATE REQUEST message indication from lower layers The tracking area updating procedure shall be aborted and re-initiated immediately. The UE shall set the EPS update status to EU2 NOT UPDATED. i) Transmission failure of TRACKING AREA UPDATE COMPLETE message indication with TAI change from lower layers If the current TAI is not in the TAI list, the tracking area updating procedure shall be aborted and re-initiated immediately. The UE shall set the EPS update status to EU2 NOT UPDATED. If the current TAI is still part of the TAI list, it is up to the UE implementation how to re-run the ongoing procedure. j) Transmission failure of TRACKING AREA UPDATE COMPLETE message indication without TAI change from lower layers It is up to the UE implementation how to re-run the ongoing procedure. k) "Extended wait time" from the lower layers If the TRACKING AREA UPDATE REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the UE shall start timer T3346 with the "Extended wait time" value and reset the tracking area updating attempt counter. If the TRACKING AREA UPDATE REQUEST message did not contain the low priority indicator set to "MS is configured for NAS signalling low priority", the UE is operating in NB-S1 mode and the UE is not a UE configured to use AC11 – 15 in selected PLMN, then the UE shall start timer T3346 with the "Extended wait time" value and reset the tracking area updating attempt counter. In other cases the UE shall ignore the "Extended wait time". The UE shall abort the tracking area updating procedure, stay in the current serving cell, set the EPS update status to EU2 NOT UPDATED, change the state to EMM-REGISTERED.ATTEMPTING-TO-UPDATE and apply the normal cell reselection process. If the UE had used eDRX before initiating tracking area updating procedure, then the UE shall continue to use the eDRX with the extended DRX parameters IE received during the last attach or tracking area updating procedure. The UE shall proceed as described below. ka) "Extended wait time CP data" from the lower layers If the UE is operating in NB-S1 mode and supports the timer T3448, the UE shall start the timer T3448 with the "Extended wait time CP data" value. If the UE is operating in NB-S1 mode and does not support the timer T3448, the UE shall start the timer T3346 with the "Extended wait time CP data" value and reset the tracking area updating attempt counter. In other cases the UE shall ignore the "Extended wait time CP data". The UE shall abort the tracking area updating procedure, stay in the current serving cell, set the EPS update status to EU2 NOT UPDATED, change the state to EMM-REGISTERED.ATTEMPTING-TO-UPDATE and apply the normal cell reselection process. If the UE had used eDRX before initiating tracking area updating procedure, then the UE shall continue to use the eDRX with the extended DRX parameters IE received during the last attach or tracking area updating procedure. The UE shall proceed as described below. l) Timer T3346 is running The UE shall not start the tracking area updating procedure unless: - the UE is in EMM-CONNECTED mode; - the UE received a paging; - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services; - the UE is requested by the upper layer for a CS fallback for emergency call or a 1xCS fallback for emergency call; - the UE in NB-S1 mode is requested by the upper layer to transmit user data related to an exceptional event and i) the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]); and ii) timer T3346 was not started when NAS signalling connection was established with RRC establishment cause set to "MO exception data"; - the UE has a PDN connection established without the NAS signalling low priority indication or is establishing a PDN connection without the NAS signalling low priority indication, the timer T3402 and the timer T3411 are not running and the timer T3346 was started due to rejection of a NAS request message (e.g. ATTACH REQUEST, TRACKING AREA UPDATE REQUEST or EXTENDED SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority"; or - the MUSIM UE needs to request an IMSI offset value as specified in clause 5.5.3.2.2. The UE stays in the current serving cell and applies the normal cell reselection process. NOTE 4: It is considered an abnormal case if the UE needs to initiate a tracking area updating procedure while timer T3346 is running independent on whether timer T3346 was started due to an abnormal case or a non successful case. If the TAI of the current serving cell is not included in the TAI list or the TIN indicates "P-TMSI", the UE shall set the EPS update status to EU2 NOT UPDATED and change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. If the tracking area updating procedure needs to be initiated for an MO MMTEL voice call or an MO MMTEL video call is started, then a notification that the procedure was not initiated due to network congestion shall be provided to upper layers. NOTE 5: This can result in the upper layers requesting establishment of the originating voice call on an alternative manner e.g. requesting establishment of a CS voice call (see 3GPP TS 24.173[ IMS Multimedia telephony communication service and supplementary services; Stage 3 ] [13E]). The UE shall proceed as described below. la) Timer T3448 is running The UE shall not start the tracking area updating procedure with the "signalling active" flag set, unless: - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE which is only using EPS services with control plane CIoT EPS optimization received a paging; or - the UE in NB-S1 mode is requested by the upper layer to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]). The UE stays in the current serving cell and applies the normal cell reselection process. The UE shall proceed as described below. m) Mobile originated detach required Detach due to removal of USIM or due to switch off: The tracking area updating procedure shall be aborted, and the UE initiated detach procedure shall be performed. Detach not due to removal of USIM and not due to switch off: The UE initiated detach procedure shall be initiated after successful completion of the tracking area updating procedure. o) Timer T3447 is running The UE shall not start the tracking area updating procedure with the "signalling active" flag set or the "active" flag set, unless: - the UE received a paging; - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services; or - the MUSIM UE needs to request an IMSI offset value as specified in clause 5.5.3.2.2. The UE stays in the current serving cell and applies the normal cell reselection process. The tracking area update request procedure is started, if still necessary, when timer T3447 expires. p) Tracking area updating and paging procedure collision If the UE receives a CS SERVICE NOTIFICATION message before the tracking area updating procedure has been completed, the UE shall progress the tracking area updating procedure and respond to the CS SERVICE NOTIFICATION upon successful completion of the tracking area updating procedure. For the cases aa, b, c, d, e, f with detach type "re-attach required" or "re-attach not required" with EMM cause other than #2 "IMSI unknown in HSS", k and ka, the UE shall stop any ongoing transmission of user data. For the cases aa, b, c, d, k, ka, l and la, the UE shall proceed as follows: 1) Timer T3430 shall be stopped if still running. 2) For the cases aa, b, c, d, la k when the "Extended wait time" is ignored, and ka when the "Extended wait time CP data" is ignored, if the tracking area updating request is not for initiating a PDN connection for emergency bearer services, the tracking area updating attempt counter shall be incremented, unless it was already set to 5. 3) If the tracking area updating attempt counter is less than 5, the TAI of the current serving cell is included in the TAI list, the EPS update status is equal to EU1 UPDATED, the TIN does not indicate "P-TMSI" and the tracking area updating procedure is performed not due to an inter-system change from N1 mode to S1 mode and the tracking area updating procedure is not performed due to cases g, m, n, za, zc in clause 5.5.3.2.2: - the UE shall keep the EPS update status to EU1 UPDATED and enter state EMM-REGISTERED.NORMAL-SERVICE. The UE shall start timer T3411. - If in addition the TRACKING AREA UPDATE REQUEST indicated "periodic updating" or if tracking area updating procedure was initiated to recover NAS signalling connection due to "RRC Connection failure" from the lower layers, none of the other reasons for initiating the tracking area updating procedure listed in clause 5.5.3.2.2 was applicable, and the TRACKING AREA UPDATE REQUEST message did not include T3324 value IE, T3412 extended value IE or Extended DRX parameters IE, the timer T3411 may be stopped when the UE enters EMM-CONNECTED mode. - If timer T3411 expires the tracking area updating procedure is triggered again. 4) If the tracking area updating attempt counter is less than 5, and the TAI of the current serving cell is not included in the TAI list or the EPS update status is different to EU1 UPDATED or the TIN indicates "P-TMSI" or the tracking area updating procedure is performed due to an inter-system change from N1 mode to S1 mode or if the tracking area updating procedure is performed due to cases g, m, n, za, zc in clause 5.5.3.2.2: - for the cases k and l, the tracking area updating procedure is started, if still necessary, when timer T3346 expires or is stopped. - for the case ka, if timer T3346 is started, the tracking area updating procedure is started, if still necessary, when timer T3346 expires or is stopped. - for the case ka, if timer T3448 is started and the "signalling active" flag is set in the TRACKING AREA UPDATE REQUEST message, the tracking area updating procedure is started, if still necessary, when timer T3448 expires or is stopped. - for the case la, if the "signalling active" flag is set in the TRACKING AREA UPDATE REQUEST message, the tracking area updating procedure is started, if still necessary, when timer T3448 expires or is stopped. - for the cases aa, b, c, d, k when the "Extended wait time" is ignored, and ka when the "Extended wait time CP data" is ignored, if the tracking area updating request is not for initiating a PDN connection for emergency bearer services, the UE shall start timer T3411, shall set the EPS update status to EU2 NOT UPDATED and change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. When timer T3411 expires the tracking area updating procedure is triggered again. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GPRS update status as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the abnormal case when a normal or periodic routing area updating procedure fails and the routing area updating attempt counter is less than 5 and the GPRS update status is different from GU1 UPDATED. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GS update status as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the abnormal cases when a registration procedure for mobility and periodic registration fails and the registration attempt counter is less than 5 and the 5GS update status is different from 5U1 UPDATED. 5) If the tracking area updating attempt counter is equal to 5: - the UE shall start timer T3402 if the value of the timer as indicated by the network is not zero, shall set the EPS update status to EU2 NOT UPDATED; - if the value of T3402 as indicated by the network is zero, the UE shall perform the actions defined for the expiry of the timer T3402; - the UE shall delete the list of equivalent PLMNs and shall change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE or optionally to EMM-REGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]; and - if A/Gb mode, Iu mode or N1 mode is supported by the UE: - if A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GPRS update status as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the abnormal case when a normal or periodic routing area updating procedure fails and the routing area updating attempt counter is equal to 5; - if the UE is operating in single-registration mode, the UE shall in addition handle the 5GS update status as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the abnormal case when a registration procedure for mobility or periodic registration update performed over 3GPP access fails and the registration attempt counter is equal to 5; and - if the UE does not change to state EMM-REGISTERED.PLMN-SEARCH, the UE shall - except for case aa attempt to select GERAN, UTRAN or NG-RAN radio access technology. For case aa the UE may attempt to select GERAN, UTRAN or NG-RAN radio access technology and proceed with appropriate GMM or 5GMM specific procedures. Additionally, if the UE selects GERAN or UTRAN radio access technology, the UE may disable the E-UTRA capability as specified in clause 4.5. If No E-UTRA Disabling In 5GS is enabled at the UE (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [50] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) and the UE selects NG-RAN radio access technology, it shall not disable the E-UTRA capability; otherwise, the UE may disable the E-UTRA capability as specified in clause 4.5. NOTE 6: Whether the UE requests RRC to treat the active E-UTRA cell as barred (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]) is left to the UE implementation. If a GERAN or UTRAN cell is selected: - a UE in PS mode 1 or PS mode 2 of operation shall proceed with appropriate GMM specific procedures; - a UE in CS/PS mode 1 or CS/PS mode 2 of operation shall proceed with appropriate MM or GMM specific procedures. If an NG-RAN cell is selected, the UE shall proceed with appropriate 5GMM specific procedures. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.3.2.6 |
1,356 | – UL-ExcessDelayConfig | The IE UL-ExcessDelayConfig IE specifies the configuration of the UL PDCP Excess Packet Delay per DRB measurement specified in TS 38.314[ NR; Layer 2 measurements ] [53]. UL-ExcessDelayConfig information element -- ASN1START -- TAG-ULEXCESSDELAYCONFIG-START UL-ExcessDelayConfig-r17 ::= SEQUENCE { excessDelay-DRBlist-r17 SEQUENCE (SIZE(1..maxDRB)) OF ExcessDelay-DRB-IdentityInfo-r17 } ExcessDelay-DRB-IdentityInfo-r17 ::= SEQUENCE { drb-IdentityList SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity, delayThreshold ENUMERATED {ms0dot25, ms0dot5, ms1, ms2, ms4, ms5, ms10, ms20, ms30, ms40, ms50, ms60, ms70, ms80, ms90, ms100, ms150, ms300, ms500} } -- TAG-ULEXCESSDELAYCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,357 | 10.5.1.3 Location Area Identification | The purpose of the Location Area Identification information element is to provide an unambiguous identification of location areas within the area covered by the 3GPP system. The Location Area Identification information element is coded as shown in figure 10.5.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Location Area Identification is a type 3 information element with 6 octets length. Figure 10.5.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Location Area Identification information element Table 10.5.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Location Area Identification information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.1.3 |
1,358 | 5.3.19A.1 UE not operating in SNPN access operation mode | The following requirements apply for a UE that is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]). When the UE adds a PLMN identity to the "forbidden PLMN list" or sets the USIM as invalid for 5GS services for 3GPP access or non-3GPP access, and timer T3245 (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]) is not running, the UE shall start timer T3245 as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12], subclause 4.1.1.6. Upon expiry of the timer T3245, the UE shall erase the "forbidden PLMN list" and "forbidden PLMNs for GPRS service" list and set the USIM to valid for 5GS services for 3GPP access and non-3GPP access. When the lists are erased, the UE performs cell selection according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]. If the UE is switched off when the timer T3245 is running, the UE shall behave as follows when the UE is switched on and the USIM in the UE remains the same: - let t1 be the time remaining for T3245 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the UE will follow the behaviour as defined in the paragraph above upon expiry of the timer T3245. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.19A.1 |
1,359 | 5.1.1 Random Access Procedure initialization | The Random Access procedure described in this clause is initiated by a PDCCH order, by the MAC sublayer itself or by the RRC sublayer. Random Access procedure on an SCell shall only be initiated by a PDCCH order. If a MAC entity receives a PDCCH transmission consistent with a PDCCH order, as specified inTS 36.212 [5], masked with its C-RNTI, and for a specific Serving Cell, the MAC entity shall initiate a Random Access procedure on this Serving Cell. For Random Access on the SpCell a PDCCH order or RRC optionally indicate the ra-PreambleIndex and the ra-PRACH-MaskIndex, except for NB-IoT where the subcarrier index is indicated; and for Random Access on an SCell, the PDCCH order indicates the ra-PreambleIndex with a value different from 000000 and the ra-PRACH-MaskIndex. For the pTAG preamble transmission on PRACH and reception of a PDCCH order are only supported for SpCell. If the UE is an NB-IoT UE, the Random Access procedure is performed on the anchor carrier or one of the non-anchor carriers for which PRACH resource has been configured in system information. Before the procedure can be initiated, the following information for related Serving Cell is assumed to be available for UEs other than NB-IoT UEs, BL UEs or UEs in enhanced coverage, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], unless explicitly stated otherwise: - the available set of PRACH resources for the transmission of the Random Access Preamble, prach-ConfigIndex. - the groups of Random Access Preambles and the set of available Random Access Preambles in each group (SpCell only): The preambles that are contained in Random Access Preambles group A and Random Access Preambles group B are calculated from the parameters numberOfRA-Preambles and sizeOfRA-PreamblesGroupA: If sizeOfRA-PreamblesGroupA is equal to numberOfRA-Preambles then there is no Random Access Preambles group B. The preambles in Random Access Preamble group A are the preambles 0 to sizeOfRA-PreamblesGroupA – 1 and, if it exists, the preambles in Random Access Preamble group B are the preambles sizeOfRA-PreamblesGroupA to numberOfRA-Preambles – 1 from the set of 64 preambles as defined in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7]. - if Random Access Preambles group B exists, the thresholds, messagePowerOffsetGroupB and messageSizeGroupA, the configured UE transmitted power of the Serving Cell performing the Random Access Procedure, PCMAX, c, as specified in TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [10], and the offset between the preamble and Msg3, deltaPreambleMsg3, that are required for selecting one of the two groups of Random Access Preambles (SpCell only). - the RA response window size ra-ResponseWindowSize. - the power-ramping factor powerRampingStep. - the maximum number of preamble transmission preambleTransMax. - the initial preamble power preambleInitialReceivedTargetPower. - the preamble format based offset DELTA_PREAMBLE (see clause 7.6). - the maximum number of Msg3 HARQ transmissions maxHARQ-Msg3Tx (SpCell only). - the Contention Resolution Timer mac-ContentionResolutionTimer (SpCell only). NOTE 1: The above parameters may be updated from upper layers before each Random Access procedure is initiated. The following information for related Serving Cell is assumed to be available before the procedure can be initiated for NB-IoT UEs, BL UEs or UEs in enhanced coverage, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]: - if the UE is a BL UE or a UE in enhanced coverage: - the available set of PRACH resources associated with each enhanced coverage level supported in the Serving Cell for the transmission of the Random Access Preamble, prach-ConfigIndex. - for EDT, the available set of PRACH resources associated with EDT for each enhanced coverage level supported in the Serving Cell for the transmission of the Random Access Preamble, prach-ConfigIndex. - the groups of Random Access Preambles and the set of available Random Access Preambles in each group(SpCell only): - except for EDT: - if sizeOfRA-PreamblesGroupA is not equal to numberOfRA-Preambles: - Random Access Preambles group A and B exist and are calculated as above; - else: - the preambles that are contained in Random Access Preamble groups for each enhanced coverage level, if it exists, are the preambles firstPreamble to lastPreamble. - for EDT, the preambles that are contained in Random Access Preamble groups for each enhanced coverage level, if it exists, are the preambles firstPreamble to edt-LastPreamble if PRACH resources configured by edt-PRACH-ParametersCE are different from the PRACH resources configured by PRACH-ParametersCE for all enhanced coverage levels and edt-PRACH-ParametersCE for all other enhanced coverage levels, otherwise the preambles for EDT are the preambles lastPreamble+1 to edt-LastPreamble. NOTE 2: When a PRACH resource is shared for multiple enhanced coverage levels, and enhanced coverage levels are differentiated by different preamble indices, Group A and Group B is not used for this PRACH resource. - if the UE is an NB-IoT UE: - the available set of PRACH resources supported in the Serving Cell on the anchor carrier, nprach-ParametersList, and on the non-anchor carriers, in ul-ConfigList. - for EDT, the available set of PRACH resources associated with EDT on anchor carrier, nprach-ParametersList-EDT, and on the non-anchor carriers, in ul-ConfigList. - for random access resource selection and preamble transmission: - a PRACH resource is mapped into an enhanced coverage level. - each PRACH resource contains a set of nprach-NumSubcarriers subcarriers which can be partitioned into one or two groups for single/multi-tone Msg3 transmission by nprach-SubcarrierMSG3-RangeStart and nprach-NumCBRA-StartSubcarriers as specified in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7], clause 10.1.6.1. Each group is referred to as a Random Access Preamble group below in the procedure text. - a subcarrier is identified by the subcarrier index in the range: [nprach-SubcarrierOffset, nprach-SubcarrierOffset + nprach-NumSubcarriers -1] - each subcarrier of a Random Access Preamble group corresponds to a Random Access Preamble. - when the subcarrier index is explicitly sent from the eNB as part of a PDCCH order ra-PreambleIndex shall be set to the signalled subcarrier index. - the mapping of the PRACH resources into enhanced coverage levels is determined according to the following: - the number of enhanced coverage levels is equal to one plus the number of RSRP thresholds present in rsrp-ThresholdsPrachInfoList. - each enhanced coverage level has one anchor carrier PRACH resource present in nprach-ParametersList and zero or one PRACH resource for each non-anchor carrier signalled in ul-ConfigList. - for EDT, each enhanced coverage level has zero or one anchor carrier PRACH resource present in nprach-ParametersList-EDT and zero or one PRACH resource for each non-anchor carrier signalled in ul-ConfigList. - enhanced coverage levels are numbered from 0 and the mapping of PRACH resources to enhanced coverage levels are done in increasing numRepetitionsPerPreambleAttempt order. - when multiple carriers provide PRACH resources for the same enhanced coverage level, the UE will randomly select one of them using the following selection probabilities: - the selection probability of the anchor carrier PRACH resource for the given enhanced coverage level, nprach-ProbabilityAnchor, is given by the corresponding entry in nprach-ProbabilityAnchorList - the selection probability is equal for all non-anchor carrier PRACH resources and the probability of selecting one PRACH resource on a given non-anchor carrier is (1- nprach-ProbabilityAnchor)/(number of non-anchor NPRACH resources) - the criteria to select PRACH resources based on RSRP measurement per enhanced coverage level supported in the Serving Cell rsrp-ThresholdsPrachInfoList. - the maximum number of preamble transmission attempts per enhanced coverage level supported in the Serving Cell maxNumPreambleAttemptCE. - the number of repetitions required for preamble transmission per attempt for each enhanced coverage level supported in the Serving Cell numRepetitionPerPreambleAttempt. - the configured UE transmitted power of the Serving Cell performing the Random Access Procedure, PCMAX, c, as specified in TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [10]. - the RA response window size ra-ResponseWindowSize and the Contention Resolution Timer mac-ContentionResolutionTimer (SpCell only) per enhanced coverage level supported in the Serving Cell. - for EDT, the Contention Resolution Timer mac-ContentionResolutionTimer configured for EDT (SpCell only) per enhanced coverage level supported in the Serving Cell. - the power-ramping factor powerRampingStep and optionally powerRampingStepCE1. - the maximum number of preamble transmission preambleTransMax-CE. - the initial preamble power preambleInitialReceivedTargetPower and optionally preambleInitialReceivedTargetPowerCE1. - the preamble format based offset DELTA_PREAMBLE (see clause 7.6). - for NB-IoT, the use of contention free random access ra-CFRA-Config. The Random Access procedure shall be performed as follows: - flush the Msg3 buffer; - set the PREAMBLE_TRANSMISSION_COUNTER to 1; - if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage: - set the PREAMBLE_TRANSMISSION_COUNTER_CE to 1; - if the starting enhanced coverage level, or for NB-IoT the starting number of NPRACH repetitions, has been indicated in the PDCCH order which initiated the Random Access procedure, or if the starting enhanced coverage level has been provided by upper layers: - the MAC entity considers itself to be in that enhanced coverage level regardless of the measured RSRP; - else: - if the RSRP threshold of enhanced coverage level 3 is configured by upper layers in rsrp-ThresholdsPrachInfoList and the measured RSRP is less than the RSRP threshold of enhanced coverage level 3 and the UE is capable of enhanced coverage level 3 then: - the MAC entity considers to be in enhanced coverage level 3; - else if the RSRP threshold of enhanced coverage level 2 configured by upper layers in rsrp-ThresholdsPrachInfoList and the measured RSRP is less than the RSRP threshold of enhanced coverage level 2 and the UE is capable of enhanced coverage level 2 then: - the MAC entity considers to be in enhanced coverage level 2; - else if the measured RSRP is less than the RSRP threshold of enhanced coverage level 1 as configured by upper layers in rsrp-ThresholdsPrachInfoList then: - the MAC entity considers to be in enhanced coverage level 1; - else: - the MAC entity considers to be in enhanced coverage level 0; - set the backoff parameter value to 0 ms; - for the RN, suspend any RN subframe configuration; - proceed to the selection of the Random Access Resource (see clause 5.1.2). NOTE 3: There is only one Random Access procedure ongoing at any point in time in a MAC entity. If the MAC entity receives a request for a new Random Access procedure while another is already ongoing in the MAC entity, it is up to UE implementation whether to continue with the ongoing procedure or start with the new procedure. NOTE 4: An NB-IoT UE measures RSRP on the anchor carrier. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.1.1 |
1,360 | 18.1 Support of SDT procedure over RACH | For SDT procedure over RACH, if the UE accesses a gNB other than the last serving gNB, the UL SDT data/signalling is buffered at the receiving gNB, and then the receiving gNB triggers the XnAP Retrieve UE Context procedure. The receiving gNB indicates SDT to the last serving gNB and the last serving gNB decides whether to relocate the UE context or not. Other SDT assistance information (e.g., single packet, multiple packets) may also be provided by the receiving gNB to help the decision of UE context relocation. If the UE is configured with the clock quality control information, the last serving gNB may perform full UE context relocation. If the last serving gNB decides not to relocate the full UE context, it transfers a partial UE context containing SDT RLC context information necessary for the receiving gNB to handle SDT via the Partial UE Context Transfer procedure. Then, in case SDT is used for user data over DRBs, UL/DL tunnels are established for DRBs configured for SDT between the receiving gNB and the last serving gNB. The PDCP PDU of UL/DL data is transferred over the tunnels, until the last serving gNB terminates the SDT session and directs the UE to continue in RRC_INACTIVE by sending the RRCRelease message. Or in case SDT is used for signalling, SRB PDCP PDUs are transferred between the receiving gNB and the last serving gNB via the XnAP RRC Transfer procedure, until the last serving gNB terminates the SDT session and directs the UE to continue in RRC_INACTIVE by sending the RRCRelease message. During the SDT session, in case the receiving gNB detects that no more packets are to be transmitted, or radio link problem is detected, the receiving gNB may also request to terminate the SDT session to the last serving gNB via the UE Context Retrieve Confirmation procedure. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 18.1 |
1,361 | 9.3.18.1 Release (network to mobile station direction) | This message is sent, from the network to the mobile station to indicate that the network intends to release the transaction identifier, and that the receiving equipment shall release the transaction identifier after sending RELEASE COMPLETE. See table 9.68/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: RELEASE Significance: local (note) Direction: network to mobile station Table 9.68/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : RELEASE message content (network to mobile station direction) NOTE: This message has local significance; however, it may carry information of global significance when used as the first call clearing message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.18.1 |
1,362 | 5.3.5.11 Full configuration | The UE shall: 1> release/ clear all current dedicated radio configurations except for the following: - the MCG C-RNTI; - the AS security configurations associated with the master key; - the SRB1/SRB2 configurations and DRB/multicast MRB configurations as configured by radioBearerConfig or radioBearerConfig2. NOTE 1: Radio configuration is not just the resource configuration but includes other configurations like MeasConfig. Radio configuration also includes the RLC bearer configurations as configured by RLC-BearerConfig, PC5 Relay RLC channel as configured by SL-RLC-ChannelConfig, and Uu Relay RLC channel as configured by Uu-RelayRLC-ChannelConfig. In case NR-DC or NE-DC is configured, this also includes the entire NR or E-UTRA SCG configuration which are released according to the MR-DC release procedure as specified in 5.3.5.10. NOTE 1a: For NR sidelink communication/discovery, the radio configuration includes the sidelink RRC configuration received from the network, but does not include the sidelink RRC reconfiguration and sidelink UE capability received from other UEs via PC5-RRC. In addition, the UE considers the new NR sidelink configurations as full configuration, in case of state transition and change of system information used for NR sidelink communication/discovery. NOTE 1b: To establish the RLC bearer of SRB(s) after release due to fullConfig, the network can include the srb-Identity within srb-ToAddModList (i.e. the UE applies RLC default configuration) and/or provide rlc-BearerToAddModList of concerned SRB(s) explicitly. - the logged measurement configuration; 1> if the spCellConfig in the masterCellGroup includes the reconfigurationWithSync: 2> release/ clear all current common radio configurations; 2> if sl-PathSwitchConfig was included in reconfigurationWithSync: 3> use the default values specified in 9.2.3 for timer T311; 2> else: 3> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311; 1> else (full configuration after re-establishment or during RRC resume): 2> if the UE is acting as L2 U2N Remote UE: 3> use value for timer T311, as included in ue-TimersAndConstants received in SIB1 2> else: 3> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1; 1> if no measConfigAppLayerId is included: 2> inform upper layers about the release of all application layer measurement configurations; 2> discard any received application layer measurement report from upper layers; 2> consider itself not to be configured to send application layer measurement report. 1> if the UE is acting as L2 U2N Remote UE at the target side during reconfiguration with sync, or after re-establishment, or during RRC resume: 2> apply the default configuration of SL-RLC1 as specified in clause 9.2.4 and associate it with the SRB1; 1> else: 2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the following: - parameters for which values are provided in SIB1; 2> apply the default MAC Cell Group configuration as specified in 9.2.2; 2> for each srb-Identity value included in the srb-ToAddModList (SRB reconfiguration): 3> establish an RLC entity for the corresponding SRB; 3> apply the default SRB configuration defined in 9.2.1 for the corresponding SRB; NOTE 2: This is to get the SRBs (SRB1 and SRB2 for reconfiguration with sync and SRB2 for resume and reconfiguration after re-establishment) to a known state from which the reconfiguration message can do further configuration. 1> for each pdu-Session that is part of the current UE configuration: 2> release the SDAP entity (clause 5.1.2 in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24]); 2> release each DRB associated to the pdu-Session as specified in 5.3.5.6.4; NOTE 3: This will retain the pdu-Session but remove the DRBs including drb-identity of these bearers from the current UE configuration. Setup of the DRBs within the AS is described in clause 5.3.5.6.5 using the new configuration. The pdu-Session acts as the anchor for associating the released and re-setup DRB. In the AS the DRB re-setup is equivalent with a new DRB setup (including new PDCP and logical channel configurations). 1> for each mbs-SessionId that is part of the current UE configuration and associated to a multicast MRB: 2> release the SDAP entity (clause 5.1.2 in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24]); 2> release each multicast MRB associated to the mbs-SessionId as specified in 5.3.5.6.6; NOTE 4: This will retain the mbs-SessionId but remove the multicast MRBs including mrb-identity of these bearers from the current UE configuration. Setup of the multicast MRBs within the AS is described in clause 5.3.5.6.7 using the new configuration. The mbs-SessionId acts as the anchor for associating the released and re-setup multicast MRB. In the AS the multicast MRB re-setup is equivalent with a new multicast MRB setup (including new PDCP and logical channel configurations). 1> for each pdu-Session that is part of the current UE configuration but not added with same pdu-Session in the drb-ToAddModList: 2> if the procedure was triggered due to reconfiguration with sync: 3> indicate the release of the user plane resources for the pdu-Session to upper layers after successful reconfiguration with sync; 2> else: 3> indicate the release of the user plane resources for the pdu-Session to upper layers immediately; 1> for each mbs-SessionId that is part of the current UE configuration but not added with the same mbs-SessionId in the mrb-ToAddModList: 2> if the procedure was triggered due to reconfiguration with sync: 3> indicate the release of the user plane resources for the mbs-SessionId to upper layers after successful reconfiguration with sync; 2> else: 3> indicate the release of the user plane resources for the mbs-SessionId to upper layers immediately. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.11 |
1,363 | 9.11.3.101 S-NSSAI time validity information | The purpose of the S-NSSAI time validity information information element is to provide S-NSSAI time validity information of one or more S-NSSAIs to the UE. The S-NSSAI time validity information information element is coded as shown in figures 9.11.3.101.1 and 9.11.3.101.2 and table 9.11.3.101.1. The S-NSSAI time validity information information element can contain per-S-NSSAI time validity information for maximum 16 S-NSSAIs. The S-NSSAI time validity information information is a type 4 information element with a minimum length of 23 octets and a maximum length of 257 octets. Figure 9.11.3.101.1: S-NSSAI time validity information information element Figure 9.11.3.101.2: Per-S-NSSAI time validity information for S-NSSAI 1 Figure 9.11.3.101.3: Per-S-NSSAI time validity information for the S-NSSAI Figure 9.11.3.101.4: Time window 1 Table 9.11.3.101.1: S-NSSAI time validity information information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.101 |
1,364 | 5.2.2.3.7 NO-CELL-AVAILABLE | The UE shall perform cell selection according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21] and choose an appropriate substate when a cell is found. When the lower layers indicate to prepare for an S101 mode to S1 mode handover and the PLMN identity of the target cell provided with this indication is not in one of forbidden PLMN lists, the UE shall enter substate NORMAL-SERVICE. NOTE: It is assumed that the UE can determine the PLMN identity of networks supporting cdma2000® HRPD access from the information broadcast over the radio interface. For the purpose of S101 mode to S1 mode handover, the UE can use the PLMN identity of the visited cdma2000® HRPD network also as PLMN identity of the target cell. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.2.3.7 |
1,365 | 16.9.2.1 Overview | The AS protocol stack for the control plane for SCCH for RRC in the PC5 interface consists of RRC, PDCP, RLC and MAC sublayers, and the physical layer. The protocol stack of control plane for SCCH for RRC is shown in Figure 16.9.2.1-1. Figure 16.9.2.1-1: Control plane protocol stack for SCCH for RRC. For support of PC5-S protocol specified in TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [40], PC5-S is located on top of PDCP, RLC and MAC sublayers, and the physical layer in the control plane protocol stack for SCCH for PC5-S, as shown in Figure 16.9.2.1-2. Figure 16.9.2.1-2: Control plane protocol stack for SCCH for PC5-S. The AS protocol stack for SBCCH in the PC5 interface consists of RRC, RLC, MAC sublayers, and the physical layer as shown below in Figure 16.9.2.1-3. Figure 16.9.2.1-3: Control plane protocol stack for SBCCH. The AS protocol stack for user plane in the PC5 interface consists of SDAP, PDCP, RLC and MAC sublayers, and the physical layer. The protocol stack of user plane is shown in Figure 16.9.2.1-4. Figure 16.9.2.1-4: User plane protocol stack for STCH. Sidelink Radio bearers (SLRB) are categorized into two groups: sidelink data radio bearers (SL DRB) for user plane data and sidelink signalling radio bearers (SL SRB) for control plane data. Separate SL SRBs using different SCCHs are configured for PC5-RRC and PC5-S signalling respectively. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.2.1 |
1,366 | 4.3.21.4.2 Group Wake Up Signal | To support the Group Wake Up Signal feature, the WUS Assistance Information is used by the eNodeB to help determine the WUS group used when paging the UE (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]). The content of the WUS Assistance Information consists of the paging probability information. The paging probability information provides a metric on the probability of a UE receiving a paging message based on, e.g., statistical information. The UE may in the Attach Request message provide its capability to support WUS Assistance Information. If WUS Assistance Information is supported, then the UE in the Attach Request or Tracking Area Update message may provide the additional UE paging probability information. The MME may use the UE provided paging probability, local configuration and/or previous statistical information for the UE, when determining the WUS Assistance Information. If the UE supports WUS Assistance Information, the MME may assign WUS Assistance Information to the UE, even when the UE has not provided the additional UE paging probability information. If the MME has determined WUS Assistance Information for the UE, the MME provides it to the UE in every Attach Accept and/or Tracking Area Update message. The MME stores the WUS Assistance Information parameter in the MM context and provides it to the eNodeB when paging the UE. UE and MME shall not include WUS Assistance Information in Emergency Attach Request/Attach Accept and in Tracking Area Update/Tracking Area Update Accept messages if the UE has an active emergency PDN connection. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.21.4.2 |
1,367 | 4.4.4.10 Abnormal cases on the network side | a) RR connection failure If a RR connection failure occurs during a common procedure integrated with the location updating procedure, the behaviour of the network should be according to the description of that common procedure. If a RR connection failure occurs when a common procedure does not exist, the location updating procedure towards the mobile station should be aborted. b) protocol error If the LOCATION UPDATING REQUEST message is received with a protocol error, the network should, if possible, return a LOCATION UPDATING REJECT message with one of the following Reject causes: #96: Mandatory information element error #99: Information element non-existent or not implemented #100: Conditional IE error #111: Protocol error, unspecified Having sent the response, the network should start the channel release procedure (see subclause 3.5). Figure 4.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Location updating sequence | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.4.10 |
1,368 | 6.2.5.1.1.2 Signalled QoS rules | The NAS protocol enables the network to provide the UE with signalled QoS rules associated with a PDU session. The network can provide the UE with one or more signalled QoS rules associated with a PDU session at the PDU session establishment or at the PDU session modification. Each signalled QoS rule contains: a) an indication of whether the QoS rule is the default QoS rule; b) a QoS rule identifier (QRI); c) a QoS flow identifier (QFI); d) optionally, a set of packet filters; and e) a precedence value. NOTE 1: The default QoS rule indication (DQR) of a signalled QoS rule cannot be changed. For case d) above: 1) If the QoS rule is the default QoS rule of a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, the set of packet filters contains zero or more packet filters for DL direction, and may additionaly contain one of the following: A) a match-all packet filter for UL direction; B) a match-all packet filter for UL and DL directions; C) zero or more packet filters for UL direction (other than the match-all packet filter for UL direction); D) zero or more packet filters for UL and DL directions (other than the match-all packet filter for UL and DL directions); or E) one or more packet filters for UL direction (other than the match-all packet filter for UL direction) and one or more packet filters for UL and DL directions (other than the match-all packet filter for UL and DL directions). The set of packet filters for the default QoS rule shall not be empty. If the default QoS rule contains a match-all packet filter, then the highest precedence value shall be used for the default QoS rule. NOTE 1a: Set of packet filters for the default QoS rule can contain only packet filters for DL direction e.g. for determination that local preconditions are met in an IMS session (see 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14]) with a receive only media. 2) If the QoS rule is a QoS rule of a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type and is not the default QoS rule, the set of packet filters contains zero or more packet filters for the DL direction, and may additionally contain one of the following: A) zero or more packet filters for UL direction (other than the match-all packet filter for UL direction); and B) zero or more packet filters for both UL and DL directions (other than the match-all packet filter for UL and DL directions). The set of packet filters for a QoS rule which is not the default QoS rule shall not be empty. NOTE 1b: Set of packet filters for a QoS rule which is not the default QoS rule can contain only packet filters for DL direction e.g. for determination that local preconditions are met in an IMS session (see 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14]) with a receive only media. 3) For PDU session of unstructured PDU session type, there is only one QoS rule associated with it and the set of packet filters of that QoS rule is empty. If the UE requests a new QoS rule, it shall assign a precedence value for the signalled QoS rule which is not in the range from 70 to 99 (decimal). NOTE 2: In this release of the specification, there is no support for a match-all packet filter for DL direction. NOTE 3: In order to support QoS differentiation in case of access to PLMN services via an SNPN, the UE, within the SNPN, can construct packet filters based on the destination IP address to reach the N3IWF in the PLMN and the security parameters index (SPI) for the IPsec SA. NOTE 4: In order to support QoS differentiation in case of access to SNPN services via a PLMN, the UE, within the PLMN, can construct packet filters based on the destination IP address to reach the N3IWF in the SNPN and the security parameters index (SPI) for the IPsec SA. NOTE 5: The above described condition of assigning a precedence value for the signalled QoS rule is applied to the UE when the UE requests a QoS rule for network to bind service data flows described by the QoS rule to a dedicated QoS flow by setting the segregation bit to 1. In NB-N1 mode, there is only one QoS rule associated with a PDU session and that is the default QoS rule. As described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], when the SMF determines that the UE has: a) moved from a tracking area in WB-N1 mode into a tracking area in NB-N1 mode; b) moved from a tracking area in WB-S1 mode into a tracking area in NB-N1 mode; or c) moved from a tracking area in NR connected to 5GCN into a tracking area in NB-N1 mode; the SMF shall, for each PDU session that is kept active, initiate the PDU session modification procedure (see subclause 6.3.3.2) to delete every QoS rule that is not the default QoS rule, if any. Within a PDU session: a) each signalled QoS rule has a unique QRI; b) there is at least one signalled QoS rule; c) one signalled QoS rule is the default QoS rule; and d) there can be zero, one or more signalled QoS rules associated with a given QFI. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.5.1.1.2 |
1,369 | 8.108 Presence Reporting Area Action | Presence Reporting Area Action is coded as depicted in Figure 8.108-1. Figure 8.108-1: Presence Reporting Area Action Table 8.108-1: Action values The Action value 1 (Start Reporting change) shall be used to request to start reporting changes of UE presence in the Presence Reporting Area identified by the Presence Reporting Area Identifier and, if present, the Presence Reporting Area elements composing the Presence Reporting Area. The Action value 2 (Stop Reporting change) shall be used to request to stop reporting changes of UE presence in a Presence Reporting Area. The Action value 3 (Modify Presence Reporting Area elements composing the PRA) shall be used to request to modify the Presence Reporting Area elements composing the PRA and to continue reporting changes of UE presence in that Presence Report Area. The Inactive PRA (INAPRA) flag in the Octet 5 shall be set to 1 on the S10/S16/S3 interface if the PRA is inactive in the source MME/SGSN during an inter MME/SGSN mobility procedure, i.e. the reporting change of UE presence in this Presence Reporting Area was requested by the PGW/PCRF/OCS but it was deactivated by the source MME/SGSN, e.g. due to an overload situation. The Presence Reporting Area Identifier shall be present if the Action value requests to start, stop or modify reporting changes of UE presence in a Presence Reporting Area. If so, the Presence Reporting Area Identifier shall contain an identifier of the Presence Reporting Area and be encoded using full hexadecimal representation(binary, not ASCII encoding). The Presence Reporting Area Identifier is defined in clause 19.10 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. Octets 9 to 14 shall be present if the Action value requests to start reporting change of UE presence in a Presence Reporting Area and the Presence Reporting Area is not pre-configured in the MME/SGSN, or the Action value requests to modify the Presence Reporting Area elements composing a Presence Reporting Area not pre-configured in the MME/SGSN. If so, these octets shall indicate the number of TAI (15 at most), Macro eNodeB ID (63 at most), Home eNodeB ID (63 at most), ECGI (63 at most), RAI (15 at most), SAI (63 at most) and CGI (63 at most) which compose the PRA. TAIs in octets 15 to 'k', if any, shall be encoded as per the TAI field in clause 8.21.4. Octets 15 to 'k' shall be absent if the field 'Number of TAI' is set to the value '0'. Macro eNB IDs in octets 'k+1' to 'm', if any, shall be encoded as per octets 6 to 11 of the Target ID for type Macro eNodeB in figure 8.51-2. Octets 'k+1' to 'm' shall be absent if the field 'Number of Macro eNodeB' is set to the value '0'. Home eNB IDs in octets 'm+1' to 'p', if any, shall be encoded as per octets 6 to 12 of the Target ID for type Home eNodeB in figure 8.51-3. Octets 'm+1' to 'p' shall be absent if the field 'Number of Home eNodeB' is set to the value '0'. ECGIs in octets 'p+1' to 'q', if any, shall be encoded as per the ECGI field in clause 8.21.5. Octets 'p+1' to 'q' shall be absent if the field 'Number of ECGI' is set to the value '0'. RAIs in octets 'q+1' to 'r', if any, shall be encoded as per the RAI field in clause 8.21.3. Octets 'q+1' to 'r' shall be absent if the field 'Number of RAI' is set to the value '0'. SAIs in octets 'r+1' to 's', if any, shall be encoded as per the SAI field in clause 8.21.2. Octets 'r+1' to 's' shall be absent if the field 'Number of SAI' is set to the value '0'. CGIs in octets 's+1' to 't', if any, shall be encoded as per the CGI field in clause 8.21.1. Octets 's+1' to 't' shall be absent if the field 'Number of CGI' is set to the value '0'. Extended Macro eNB IDs in octets 't+2' to 'v', if any, shall be encoded as per octets 6 to 11 of the Target ID for type Extended Macro eNodeB in figure 8.51-x. Octets 't+2' to 'v' shall be absent if the field 'Number of Extended Macro eNodeB' is set to the value '0'. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.108 |
1,370 | 6.4.2 Ciphering and integrity mode negotiation | When an MS wishes to establish a connection with the network, the MS shall indicate to the network in the MS/USIM Classmark which cipher and integrity algorithms the MS supports. This information itself must be integrity protected. As it is the case that the RNC does not have the integrity key IK when receiving the MS/USIM Classmark this information must be stored in the RNC. The data integrity of the classmark is performed, during the security mode set-up procedure by use of the most recently generated IK (see section 6.4.5). The network shall compare its integrity protection capabilities and preferences, and any special requirements of the subscription of the MS, with those indicated by the MS and act according to the following rules: 1) If the MS and the network have no versions of the UIA algorithm in common, then the connection shall be released. 2) If the MS and the network have at least one version of the UIA algorithm in common, then the network shall select one of the mutually acceptable versions of the UIA algorithm for use on that connection. The network shall compare its ciphering capabilities and preferences, and any special requirements of the subscription of the MS, with those indicated by the MS and act according to the following rules: 1) If the MS and the network have no versions of the UEA algorithm in common and the network is not prepared to use an unciphered connection, then the connection shall be released. 2) If the MS and the network have no versions of the UEA algorithm in common and the user (respectively the user's HE) and the network are willing to use an unciphered connection, then an unciphered connection shall be used. 3) If the MS and the network have at least one version of the UEA algorithm in common, then the network shall select one of the mutually acceptable versions of the UEA algorithm for use on that connection. Because of the separate mobility management for CS and PS services, one CN domain may, independent of the other CN, establish a connection to one and the same MS. Change of ciphering and integrity mode (algorithms) at establishment of a second MS to CN connection shall not be permitted. The preferences and special requirements for the ciphering and integrity mode setting shall be common for both domains. (e.g. the order of preference of the algorithms). | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.2 |
1,371 | 4.23.7.3 Inter NG-RAN node N2 based handover with I-SMF insertion/change/removal 4.23.7.3.1 General | When I-SMF is inserted or changed or removed during inter NG-RAN node N2 handover, the procedures defined in this clause are used. To support the EAS session continuity upon UL CL relocation, a N9 forwarding tunnel to support the EAS session continuity is established and released between the Source UL CL and Target UL CL as described in clause 4.23.9.4 or clause 4.23.9.5. NOTE: This allows the UE to go on exchanging with the source EAS despite the fact that a new UL CL has been allocated to the PDU Session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.7.3 |
1,372 | 4.3.2.2.2 S-CSCF online charging / IMS Gateway Function | As stated above, the S-CSCF does not trigger any online charging events and thus does not include the CTF online charging enhancements described in clause 4.3.2.1 (in contrast, it does have a CTF for offline charging, as described in clause 4.3.1.1). Instead, the ISC interface is employed by the S-CSCF online charging, implying that online charging is transparent to the S-CSCF and appears like any other service logic controlled by a SIP application server. Therefore, if support for Ro based online charging is required instead of / or in addition to application server or MRFC, a special CTF is needed in order to mediate between the Ro based SBCF and the SIP based service control. This role is taken by the IMS Gateway Function (IMS GWF), which translates between SIP service control towards the S-CSCF and Ro Credit-Control on the OCS side. From the perspective of the online charging architecture, the IMS GWF is an online charging capable CTF; from the perspective of the S-CSCF, the IMS GWF is a SIP application server and is triggered the same way. It is out of scope of the 3GPP standards whether the IMS GWF is embedded in the S-CSCF, embedded in the OCS/SBCF, or exists as a stand-alone component. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.2.2.2 |
1,373 | 7 Consolidated potential requirements 7.1 General | The UTM shall be able to associate the UAV and UAV controller, identify them as a UAS, and authorise a UAS to operate. The UTM shall be able to refuse authorisation for a UAS to operate. The 3GPP system shall enable a UAS to send the following UAV data to a UTM: unique identity (this may be unique 3GPP identity), UE capability of the UAV, make & model, serial number, take-off weight, position, owner identity, owner address, owner contact details, owner certification, take-off location, mission type, route data, operating status. The 3GPP system shall enable a UAS to send the following UAV controller data to a UTM: unique identity, UE capability of the UAV controller, position, owner identity, owner address, owner contact details, owner certification, the identity of the UAV operator who operate the UAV controller, UAV operator license and certification. The 3GPP system shall enable a UAS to send different UAS data to UTM based on the different authentication and authorizations level which are applied to the UAS. The 3GPP system shall support capability to extend UAS data being sent to UTM with the evolution of UTM and its support applications in future. The 3GPP system shall enable a UE in a UAS to send the following identifiers to a UTM: IMSI, IMEI, MSISDN. The 3GPP system may enable an MNO to augment the data sent to a UTM with the following: network-based positioning information, preconfigured pairing data. NOTE: this augmentation may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information. A UAS may optimise subsequent messages sent to an UTM by omitting unchanged static or semi-static data (e.g. owner identity, owner address, owner contact details, owner certification). The UTM shall be able to inform an MNO of the outcome of an authorisation to operate. The 3GPP system shall enable an MNO to allow a UAS authorisation request only if appropriate subscription information is present. An MNO shall be able to enforce the authorisation for a UAS to operate (e.g. by enabling or disabling communication between the UAV and UAV controller). The 3GPP system shall enable a UTM to be aware of the identity/identities of a UAS. The 3GPP system shall enable a UAS to update a UTM with the live location information of a UAV and its UAV controller. The 3GPP system may enable an MNO to supplement location information sent to a UTM. NOTE: this supplement may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information. The 3GPP system shall support a UTM to consume Location Service provided by the network. The 3GPP system shall enable a UAS to send the location of the UAV and UAV controller towards UTM with at least a periodicity of 1 update per second. The 3GPP system shall enable an authorised official to query a UTM for information, location, and identities of an active UAS when an authorised official provides a subset of UAS data (e.g. an IMSI, general location, or IMEI). An MNO shall be able to enforce the authorisation for assisting a UAS to operate, e.g. by establishing a reliable route within 3GPP network to deliver the commands/control messages between the UAV and UAV controller. The 3GPP network shall be able to support roaming when providing network assisted UAS operation. The 3GPP system shall provide the capability for an MNO to receive the UAS information regarding its 3GPP communication capabilities. The 3GPP system shall support the UAS identification data which can differentiate the UAS with UAS-capable UE and the UAS with non-UAS-capable UE. NOTE: UAS-capable UE refers to the UE which support interaction capability with UTM and certain 3GPP communication features which 3GPP provides for UAS. The 3GPP system shall support identification and reporting unauthorized UAVs to a UTM. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7 |
1,374 | 6.1.3.1 PDP context activation | The purpose of this procedure is to establish a PDP context between the MS and the network for a specific QoS on a specific NSAPI. The PDP context activation may be initiated by the MS or the initiation may be requested by the network. An MS attached for emergency bearer services shall only request a PDP context with request type set to "emergency". If there already is a PDN connection for emergency bearer services established, the MS shall not request an additional PDN connection for emergency bearer services. The MS shall not request emergency bearer services in A/Gb mode or in GERAN Iu mode. If the MS has reached the maximum number of active PDP contexts (see subclause 6.1.3.0) and the upper layers of the MS request activation of additional PDP context, then the MS shall not send an ACTIVATE PDP CONTEXT REQUEST message or an ACTIVATE SECONDARY PDP CONTEXT REQUEST message to activate the additional PDP context. If the additional PDP context is a PDP context with type set to "emergency", then it may skip explicit deactivation to free PDP context resources and instead re-activate the necessary context(s) relying on network handling of abnormal cases as specified in subclause 6.1.3.1.5 case c). In either case it is an MS implementation option which PDP context(s) to re-use for emergency. Each PDP address may be described by one or more PDP contexts in the MS or the network. The PDP Context Activation procedure is used to activate the default PDP context for a given PDP address and APN, i.e. a PDN connection, whereas all additional contexts associated to the same PDP address and APN are activated with the secondary PDP context activation procedure. An MS supporting S1 mode shall keep the default PDP context activated during the lifetime of the PDN connection. An MS not supporting S1 mode should apply the same behaviour (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). When more than one PDP context is associated to a PDP address, there shall be a Traffic Flow Template (TFT), including one or more packet filters, for each or all but one context. The downlink and uplink packet filters are considered separately. If present, the TFT shall be sent transparently either from the MS via the SGSN to the GGSN to enable packet classification and policing for downlink data transfer in the GGSN or from the GGSN via the SGSN to the MS to be used in a network requested secondary PDP context activation procedure (see subclause 6.1.3.2) and enable packet classification and policing for uplink data transfer in the MS (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). For the purpose of requesting non-IP connectivity, the MS shall set the PDP type number in the Requested PDP address information element in the ACTIVATE PDP CONTEXT REQUEST message to "non IP". The MS supporting non-IP connectivity shall also support the extended protocol configuration options IE. For the purpose of requesting IP address allocation the MS shall set the PDP type number in the Requested PDP address information element in the ACTIVATE PDP CONTEXT REQUEST message based on its IP stack configuration (e.g. the per APN settings specified in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]) as follows: a) An MS, which is IPv6 and IPv4 capable, and - has not been allocated an IP address for this APN, shall set the PDP type number to "IPv4v6 address"; - has been allocated an IPv4 address for this APN and received the SM cause #52, "single address bearers only allowed", and is requesting an IPv6 address, shall set the PDP type number to "IPv6 address"; - has been allocated an IPv6 address for this APN and received the SM cause #52, "single address bearers only allowed", and is requesting an IPv4 address, shall set the PDP type number to "IPv4 address". b) An MS, which is only IPv4 capable, shall set the PDP type number to "IPv4 address". c) An MS, which is only IPv6 capable, shall set the PDP type number to "IPv6 address". d) When the IP version capability of the MS is unknown in the MS (as in the case when the MT and TE are separated and the capability of the TE is not known in the MT), the MS shall set the PDP type number to "IPv4v6 address". On receipt of the ACTIVATE PDP CONTEXT REQUEST message sent by the MS, the network when allocating an IP address shall take into account the PDP type number, the operator policies of the home and visited network, and the user's subscription data. - If the MS requests PDP type IPv4v6, but the network configuration dictates the use of IPv4 addressing only or IPv6 addressing only for this APN, the network shall override the PDP type requested by the MS to a single address PDP type (IPv4 or IPv6). In the ACTIVATE PDP CONTEXT ACCEPT message sent to the MS, the network sets the PDP type number to either "IPv4 address" or "IPv6 address" and the SM cause to #50 "PDP type IPv4 only allowed", or #51 "PDP type IPv6 only allowed", respectively (see subclause 6.1.3.1.1). - If the MS requests PDP type IPv4v6, but the operator uses single addressing per PDP context due to interworking with nodes of earlier releases, the network shall override the PDP type requested by setting the PDP type in the ACTIVATE PDP CONTEXT ACCEPT message sent to the MS to a single address PDP type. In the ACTIVATE PDP CONTEXT ACCEPT message sent to the MS, the network sets the PDP type number to either "IPv4 address" or "IPv6 address" and the SM cause to #52, "single address bearers only allowed" (see subclause 6.1.3.1.1). The MS, in a pre release 8 network not supporting IPv4/v6, could encounter other network reactions: - If the MS requests PDP type IPv4v6, and the PDP type is changed to PDP type IPv4 and no SM cause is included, the MS should request another PDP context for PDP type IPv6 to the same APN. NOTE: Some networks can respond with ACTIVATE PDP CONTEXT REJECT with SM cause #28 "unknown PDP address or PDP type". In that instance, the MS can attempt to establish dual-stack connectivity by performing two PDP context activation request procedures to activate an IPv4 PDP context and an IPv6 PDP context, both to the same APN. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.1 |
1,375 | 6.4.1 Default EPS bearer context activation procedure 6.4.1.1 General | The purpose of the default bearer context activation procedure is to establish a default EPS bearer context between the UE and the EPC. The default EPS bearer context activation procedure is initiated by the network as a response to the PDN CONNECTIVITY REQUEST message from the UE. The default bearer context activation procedure can be part of the attach procedure, and if the attach procedure fails, the UE shall consider that the default bearer activation has implicitly failed. The default EPS bearer context does not have any TFT assigned during the activation procedure. This corresponds to using a match-all packet filter. The network may at any time after the establishment of this bearer assign a TFT to the default EPS bearer and may subsequently modify the TFT or the packet filters of this default bearer. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.1 |
1,376 | 6.4.4.2 EPS bearer context deactivation initiated by the network | If a NAS signalling connection exists when the MME initiates the EPS bearer context deactivation procedure, the MME shall initiate the EPS bearer context deactivation procedure by sending a DEACTIVATE EPS BEARER CONTEXT REQUEST message to the UE, start the timer T3495, and enter the state BEARER CONTEXT INACTIVE PENDING (see example in figure 6.4.4.2.1). The DEACTIVATE EPS BEARER CONTEXT REQUEST message contains an ESM cause typically indicating one of the following: #8: operator determined barring; #26: insufficient resources; #29: user authentication or authorization failed; #36: regular deactivation; #38: network failure; #39: reactivation requested; #112: APN restriction value incompatible with active EPS bearer context; or #113: Multiple accesses to a PDN connection not allowed. If the deactivation is triggered by a UE initiated bearer resource modification procedure or UE requested PDN disconnect procedure, the DEACTIVATE EPS BEARER CONTEXT REQUEST message shall contain the procedure transaction identity (PTI) value received by the MME in the BEARER RESOURCE MODIFICATION REQUEST or PDN DISCONNECT REQUEST respectively. When the MME wants to deactivate all EPS bearer contexts of a PDN connection and thus disconnect the UE from the PDN, the MME shall include the EPS bearer identity of the default bearer associated to the PDN in the DEACTIVATE EPS BEARER CONTEXT REQUEST message. In this case, the MME shall not include the WLAN offload indication in the DEACTIVATE EPS BEARER CONTEXT REQUEST message, and if the UE receives the WLAN offload indication, the UE shall ignore the indication. NOTE 1: If the DEACTIVATE EPS BEARER CONTEXT REQUEST message contains the UAS services not allowed indication in the Extended protocol configuration options IE, then the ESM cause value #29 "user authentication or authorization failed" is included in the DEACTIVATE EPS BEARER CONTEXT REQUEST message. If no NAS signalling connection exists when the MME initiates the EPS bearer context deactivation, the ESM entity in the MME shall locally deactivate the EPS bearer context towards the UE without any peer-to-peer ESM signalling between the MME and the UE. NOTE 2: The EPS bearer context state(s) can be synchronized between the UE and the MME at the next EMM-IDLE to EMM-CONNECTED transition, e.g. during a service request or tracking area updating procedure. Figure 6.4.4.2.1: EPS bearer context deactivation procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.4.2 |
1,377 | 5.1.2.1 Interworking between 5G systems | The 5G system shall support a UE with a 5G subscription roaming into a 5G Visited Mobile Network which has a roaming agreement with the UE's 5G Home Mobile Network. The 5G system shall enable a Visited Mobile Network to provide support for establishing home network provided data connectivity as well as visited network provided data connectivity. The 5G system shall enable a Visited Mobile Network to provide support for services provided in the home network as well as provide services in the visited network. Whether a service is provided in the visited network or in the home network is determined on a service by service basis. The 5G system shall provide a mechanism for a network operator to limit access to its services for a roaming UE, (e.g. based on roaming agreement). The 5G system shall provide a mechanism for a network operator to direct a UE onto a partnership network for routing all or some of the UE user plane and associated control plane traffic over the partnership network, subject to an agreement between the operators. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.1.2.1 |
1,378 | 4.15.6.6 Setting up an AF session with required QoS procedure | Figure 4.15.6.6-1: Setting up an AF session with required QoS procedure 1. The AF sends a request to reserve resources for an AF session using Nnef_AFsessionWithQoS_Create request message (UE address, AF Identifier, Flow description information or External Application Identifier, QoS Reference or individual QoS parameters, Alternative Service Requirements (as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), DNN, S-NSSAI) to the NEF. Optionally, QoS monitoring requirements, Indication of ECN marking for L4S, PDU Set QoS Parameters (as described in clause 5.7.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and Protocol Description (as described in clause 5.37.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) can be included in the AF request. For a Multi-modal service, the AF may provide a Multi-modal Service ID together with Multi-modal Service Requirements information for each data flow, as described in clause 6.1.3.27.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Optionally, a period of time or a traffic volume for the requested QoS can be included in the AF request. The AF may, instead of a QoS Reference, provide one or more of the following individual QoS parameters: Requested 5GS Delay (optional), Requested Priority (optional), Requested Guaranteed Bitrate, Requested Maximum Bitrate, Maximum Burst Size and Requested Packet Error Rate. The AF may also provide an Averaging Window value for deriving such parameters for GBR QoS Flows. Regardless of whether the AF request is formulated using a QoS Reference or individual QoS parameters, the AF may also provide one or more of the following parameters that describe the traffic characteristics: flow direction, Burst Arrival Time at UE (uplink) or UPF (downlink), Periodicity, Time domain, Survival Time, Capability for BAT adaptation or BAT Window, Periodicity Range. The AF may also provide an RT Latency Indication. The optional Alternative Service Requirements provided by the AF shall either contain QoS References or Requested Alternative QoS Parameter Set(s) in a prioritized order as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Optionally, Packet Delay Variation requirements can be included in the AF request as described in clause 6.1.3.26 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Optionally, the AF may provide QoS duration and QoS inactivity interval in order to indicate PCF the time period when the QoS should be applied. NOTE 1: For multi-modal flows related to multiple UEs, multiple UE-specific AF requests are used and the AF provided information to NEF is the same as single UE case (as defined in clause 5.37.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). 2. The NEF authorizes the AF request that contains a single UE address and may apply policies to control the overall amount of QoS authorized for the AF. If the authorisation is not granted, all steps (except step 5) are skipped and the NEF replies to the AF with a Result value indicating that the authorisation failed. The NEF assigns a Transaction Reference ID to the Nnef_AFsessionWithQoS_Create request. The NEF determines whether to invoke the TSCTSF or to directly contact the PCF based on operator configuration. This determination may use the presence of a QoS Reference or individual QoS parameters in the AF request. The determination may also use the AF identifier or the presence of AF provided parameters that describe the traffic characteristics in the AF request. NOTE 2: The determination can also be based on an SLA between operator and application provider, e.g. using the DNN/S-NSSAI for the AF session according to the SLA. If the NEF determines not to invoke the TSCTSF, then steps 3, 4, 5, 6, 7, 8 are executed, otherwise, steps 3a, 3b, 4a, 4b, 5, 6a, 7a, 7b, 8 are executed. 3. If the NEF determines to contact the PCF directly without invoking the TSCTSF, the NEF uses the UE address to discover the PCF from the BSF. The NEF forwards received parameters to the PCF in the Npcf_PolicyAuthorization_Create request. Any optionally received period of time or traffic volume mapped and forwarded as sponsored data connectivity information (as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). If the AF is considered to be trusted by the operator, the AF uses the Npcf_PolicyAuthorization_Create request message to interact directly with PCF to request reserving resources for an AF session. 3a. If the NEF determines to invoke the TSCTSF, the NEF forwards received parameters in the Ntsctsf_QoSandTSCAssistance_Create request message to the TSCTSF. Any optionally received period of time or traffic volume is mapped and forwarded as sponsored data connectivity information (as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). If the AF is considered to be trusted by the operator, the AF uses the Ntsctsf_QoSandTSCAssistance_Create request message to interact directly with TSCTSF to request reserving resources for an AF session. A TSCTSF address may be locally configured (a single TSCTSF per DNN/S-NSSAI) in the NEF, PCF and trusted AF. Alternatively, the NEF uses the AF Identifier to determine the DNN/S-NSSAI and uses the DNN/S-NSSAI to discover the TSCTSF from the NRF. 3b. The TSCTSF determines whether it has an AF session with a PCF for the given UE address. In this case the TSCTSF sends a Npcf_PolicyAuthorization_Update request message to the PCF and forwards the received parameters after executing the adjustment and mapping actions described below. If the TSCTSF does not have an AF-session for a given UE address, the TSCTSF discovers the PCF and a Npcf_PolicyAuthorization_Create request message to the PCF. If the TSCTSF receives a Requested 5GS Delay, the TSCTSF calculates a Requested PDB by subtracting the UE-DS-TT Residence Time (either provided by the PCF or pre-configured at TSCTSF) from the Requested 5GS Delay and sends the Requested PDB to the PCF instead of the Requested 5GS Delay. If the TSCTSF receives any of the following parameters: flow direction, Burst Arrival Time, Periodicity, Time domain, Survival Time, Capability for BAT adaptation or BAT Window, Periodicity Range from the NEF, the TSCTSF determines the TSC Assistance Container and sends it to the PCF instead of these parameters. 4. For requests received from the NEF in step 3, the PCF determines whether the request is authorized and notifies the NEF if the request is not authorized. If the request is authorized, the PCF derives the required QoS parameters of the PCC rule based on the information provided by the NEF and determines whether this QoS is allowed (according to the PCF configuration) and notifies the result to the NEF. If the AF is considered to be trusted by the operator, the PCF sends the Npcf_PolicyAuthorization_Create response message directly to AF. If the PCF receives the individual QoS parameters instead of QoS Reference, the PCF determines a 5QI that matches the individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. It also sets the GBR and MBR for the PCC rule according to the requested values. The PCF may use the Requested Priority from the AF to determine Priority Level as defined in clause 5.7.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Requested individual QoS parameter values supersede default values for the 5QI. If the PCF receives the RT Latency Indication described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], the PCF executes Uplink-Downlink Transmission Coordination as described in clause 5.37.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the associated QoS monitoring for the two correlated QoS Flows as described in clause 6.1.3.27.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. If the PCF receives PDU Set QoS parameters described in clause 5.7.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the PDU Set QoS parameters are applied as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. If the PCF receives an explicit indication (i.e. Indication of ECN marking for L4S) as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], PCF decides that the service data flow supports ECN marking for L4S. PCF then indicates to the SMF to enable ECN marking for L4S for that QoS flow. In addition, if the Alternative Service Requirements are provided, the PCF derives the Alternative QoS parameter set(s) in the same way from the one or more QoS Reference parameters or the Requested Alternative QoS Parameter Set(s) contained in the Alternative Service Requirements keeping the same prioritized order (as defined in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). NOTE 3: The PCF derived Alternative QoS parameter set(s) for the PCC rule are subsequently used to establish Alternative QoS Profile(s). The Alternative QoS Profile parameters provided to the NG-RAN are specified in clause 5.7.1.2a of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For multi-modal flows, the PCF derives the required QoS parameters in the PCC rules and generates the QoS monitoring requirements policy for each media flow, based on the information provided by the NEF. If the PCF determines that the SMF needs updated policy information, the PCF issues a Npcf_SMPolicyControl_UpdateNotify request with updated policy information about the PDU Session as described in the PCF initiated SM Policy Association Modification procedure in clause 4.16.5.2. 4a. For requests received from the TSCTSF in step 3b, the PCF determines whether the request is authorized and notifies the TSCTSF if the request is not authorized. If the request is authorized, the PCF derives the required QoS parameters of the PCC rule in the same way it is described in step 4 based on the information provided by the TSCTSF and determines whether this QoS is allowed (according to the PCF configuration) and notifies the result to the TSCTSF. If the PCF determines that the SMF needs updated policy information, the PCF issues a Npcf_SMPolicyControl_UpdateNotify request with updated policy information about the PDU Session as described in the PCF initiated SM Policy Association Modification procedure in clause 4.16.5.2. If the PCF receives a subscription for the 5GS Bridge/Router information from the TSCTSF, if the PCF does not have the 5GS Bridge/Router information for the PDU Session, the PCF uses the PCF initiated SM Policy Association Modification procedure as described in clause 4.16.5.2 to subscribe for 5GS Bridge/Router information event from the SMF. Once the PCF has the 5GS Bridge/Router information, the PCF notifies the TSCTSF for the 5GS Bridge/Router information (including the UE-DS-TT Residence Time). 4b. The TSCTSF sends a Ntsctsf_QoSandTSCAssistance_Create response message (Transaction Reference ID, Result) to the NEF. Result indicates whether the request is granted or not. If the AF is considered to be trusted by the operator, the TSCTSF sends the Ntsctsf_QoSandTSCAssistance_Create response message directly to AF. 5. The NEF sends a Nnef_AFsessionWithQoS_Create response message (Transaction Reference ID, Result) to the AF. Result indicates whether the request is granted or not. 6. The NEF shall send a Npcf_PolicyAuthorization_Subscribe message to the PCF to subscribe to notifications of Resource allocation status and may subscribe to other events described in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 6a. The TSCTSF shall send a Npcf_PolicyAuthorization_Subscribe message to the PCF to subscribe to notifications of Resource allocation status and may subscribe to other events described in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The TSCTSF that receives Capability for BAT adaptation or BAT Window in step 3a shall subscribe to notification on BAT offset via sending a Npcf_PolicyAuthorization_Subscribe request message to the PCF. 7. When the event condition is met, e.g. that the establishment of the transmission resources corresponding to the QoS update succeeded or failed, the PCF sends Npcf_PolicyAuthorization_Notify message to the NEF notifying about the event. If the AF is considered to be trusted by the operator, the PCF sends the Npcf_PolicyAuthorization_Notify message directly to AF. 7a. When the event condition is met, e.g. that the establishment of the transmission resources corresponding to the QoS update succeeded or failed, the PCF sends Npcf_PolicyAuthorization_Notify message to the TSCTSF notifying about the event. 7b. The TSCTSF sends Ntsctsf_QoSandTSCAssistance_Notify message with the event reported by the PCF to the NEF. If the AF is considered to be trusted by the operator, the TSCTSF sends the Ntsctsf_QoSandTSCAssistance_Notify message directly to AF. 8. The NEF sends Nnef_AFsessionWithQoS_Notify message with the event reported by the PCF to the AF. The AF may send Nnef_AFsessionWithQoS_Revoke request to NEF in order to revoke the AF request. The NEF authorizes the revoke request and triggers the Ntsctsf_QoSandTSCAssistance_Delete and/or Npcf_PolicyAuthorization_Delete service operations for the AF request. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.6 |
1,379 | 13.1 Overview and Principles | The following principles apply to NR connected to 5GC security, see TS 33.501[ Security architecture and procedures for 5G System ] [5]: - For user data (DRBs), ciphering provides user data confidentiality and integrity protection provides user data integrity; - For RRC signalling (SRBs), ciphering provides signalling data confidentiality and integrity protection signalling data integrity; NOTE: Ciphering and integrity protections are optionally configured except for RRC signalling for which integrity protection is always configured. Ciphering and integrity protection can be configured per DRB but all DRBs belonging to a PDU session for which the User Plane Security Enforcement information indicates that UP integrity protection is required (see TS 23.502[ Procedures for the 5G System (5GS) ] [22]), are configured with integrity protection. - For key management and data handling, any entity processing cleartext shall be protected from physical attacks and located in a secure environment; - The gNB (AS) keys are cryptographically separated from the 5GC (NAS) keys; - Separate AS and NAS level Security Mode Command (SMC) procedures are used; - A sequence number (COUNT) is used as input to the ciphering and integrity protection and a given sequence number must only be used once for a given key (except for identical re-transmission) on the same radio bearer in the same direction. The keys are organised and derived as follows: - Key for AMF: - KAMF is a key derived by ME and SEAF from KSEAF. - Keys for NAS signalling: - KNASint is a key derived by ME and AMF from KAMF, which shall only be used for the protection of NAS signalling with a particular integrity algorithm; - KNASenc is a key derived by ME and AMF from KAMF, which shall only be used for the protection of NAS signalling with a particular encryption algorithm. Key for gNB: - KgNB is a key derived by ME and AMF from KAMF. KgNB is further derived by ME and source gNB when performing horizontal or vertical key derivation. Keys for UP traffic: - KUPenc is a key derived by ME and gNB from KgNB, which shall only be used for the protection of UP traffic between ME and gNB with a particular encryption algorithm; - KUPint is a key derived by ME and gNB from KgNB, which shall only be used for the protection of UP traffic between ME and gNB with a particular integrity algorithm. Keys for RRC signalling: - KRRCint is a key derived by ME and gNB from KgNB, which shall only be used for the protection of RRC signalling with a particular integrity algorithm; - KRRCenc is a key derived by ME and gNB from KgNB, which shall only be used for the protection of RRC signalling with a particular encryption algorithm. Intermediate keys: - NH is a key derived by ME and AMF to provide forward security. - KgNB* is a key derived by ME and gNB when performing a horizontal or vertical key derivation. The primary authentication enables mutual authentication between the UE and the network and provide an anchor key called KSEAF. From KSEAF, KAMF is created during e.g. primary authentication or NAS key re-keying and key refresh events. Based on KAMF, KNASint and KNASenc are then derived when running a successful NAS SMC procedure. Whenever an initial AS security context needs to be established between UE and gNB, AMF and the UE derive a KgNB and a Next Hop parameter (NH). The KgNB and the NH are derived from the KAMF. A NH Chaining Counter (NCC) is associated with each KgNB and NH parameter. Every KgNB is associated with the NCC corresponding to the NH value from which it was derived. At initial setup, the KgNB is derived directly from KAMF, and is then considered to be associated with a virtual NH parameter with NCC value equal to zero. At initial setup, the derived NH value is associated with the NCC value one. On handovers, the basis for the KgNB that will be used between the UE and the target gNB, called KgNB*, is derived from either the currently active KgNB or from the NH parameter. If KgNB* is derived from the currently active KgNB, this is referred to as a horizontal key derivation and is indicated to UE with an NCC that does not increase. If the KgNB* is derived from the NH parameter, the derivation is referred to as a vertical key derivation and is indicated to UE with an NCC increase. Finally, KRRCint, KRRCenc, KUPint and KUPenc are derived based on KgNB after a new KgNB is derived. This is depicted on Figure 13.1-1 below: Figure 13.1-1: 5G Key Derivation With such key derivation, a gNB with knowledge of a KgNB, shared with a UE, is unable to compute any previous KgNB that has been used between the same UE and a previous gNB, therefore providing backward security. Similarly, a gNB with knowledge of a KgNB, shared with a UE, is unable to predict any future KgNB that will be used between the same UE and another gNB after n or more handovers (since NH parameters are only computable by the UE and the AMF). The AS SMC procedure is for RRC and UP security algorithms negotiation and RRC security activation. When AS security context is to be established in the gNB, the AMF sends the complete UE 5G security capabilities to the gNB (i.e., all bits for every capability defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [28] and received in NAS signalling). At handover (or at UE Context retrieval), the complete UE 5G security capabilities are also sent by the source gNB to the target gNB (or by the last serving gNB to the receiving gNB respectively). The gNB chooses the ciphering algorithm which has the highest priority from its configured list and is also present in the UE 5G security capabilities. The gNB also chooses the integrity algorithm which has the highest priority from its configured list and is also present in the UE 5G security capabilities. The chosen algorithms are indicated to the UE in the AS SMC and this message is integrity protected. RRC downlink ciphering (encryption) at the gNB starts after sending the AS SMC message. RRC uplink deciphering (decryption) at the gNB starts after receiving and successful verification of the integrity protected AS security mode complete message from the UE. The UE verifies the validity of the AS SMC message from the gNB by verifying the integrity of the received message. RRC uplink ciphering (encryption) at the UE starts after sending the AS security mode complete message. RRC downlink deciphering (decryption) at the UE shall start after receiving and successful verification of the AS SMC message. The RRC Connection Reconfiguration procedure used to add DRBs shall be performed only after RRC security has been activated as part of the AS SMC procedure. A UE connected to 5GC, shall support integrity protected DRBs at any data rate, up to and including the highest data rate supported by the UE for both UL and DL. In case of failed integrity check (i.e. faulty or missing MAC-I), the concerned PDU shall be discarded by the receiving PDCP entity. Key refresh is possible for KgNB, KRRC-enc, KRRC-int, KUP-enc, and KUP-int and can be initiated by the gNB when a PDCP COUNTs are about to be re-used with the same Radio Bearer identity and with the same KgNB. Key re-keying is also possible for the KgNB, KRRC-enc, KRRC-int, KUP-enc, and KUP-int and can be initiated by the AMF when a 5G AS security context different from the currently active one shall be activated. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 13.1 |
1,380 | – MeasObjectEUTRA | The IE MeasObjectEUTRA specifies information applicable for E-UTRA cells. MeasObjectEUTRA information element -- ASN1START -- TAG-MEASOBJECTEUTRA-START MeasObjectEUTRA::= SEQUENCE { carrierFreq ARFCN-ValueEUTRA, allowedMeasBandwidth EUTRA-AllowedMeasBandwidth, cellsToRemoveListEUTRAN EUTRA-CellIndexList OPTIONAL, -- Need N cellsToAddModListEUTRAN SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-Cell OPTIONAL, -- Need N excludedCellsToRemoveListEUTRAN EUTRA-CellIndexList OPTIONAL, -- Need N excludedCellsToAddModListEUTRAN SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-ExcludedCell OPTIONAL, -- Need N eutra-PresenceAntennaPort1 EUTRA-PresenceAntennaPort1, eutra-Q-OffsetRange EUTRA-Q-OffsetRange OPTIONAL, -- Need R widebandRSRQ-Meas BOOLEAN, ..., [[ associatedMeasGap-r17 MeasGapId-r17 OPTIONAL -- Need R ]], [[ measSequence-r18 MeasSequence-r18 OPTIONAL -- Need R ]] } EUTRA-CellIndexList ::= SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-CellIndex EUTRA-CellIndex ::= INTEGER (1..maxCellMeasEUTRA) EUTRA-Cell ::= SEQUENCE { cellIndexEUTRA EUTRA-CellIndex, physCellId EUTRA-PhysCellId, cellIndividualOffset EUTRA-Q-OffsetRange } EUTRA-ExcludedCell ::= SEQUENCE { cellIndexEUTRA EUTRA-CellIndex, physCellIdRange EUTRA-PhysCellIdRange } -- TAG-MEASOBJECTEUTRA-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,381 | W.4.1.3 User-plane procedure | The UE registers to the MBS service and receives the MBS traffic as specified in TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102] with the following changes. - MBSSF takes the role of the BM-SC in TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102]. - The UE authenticates to the MBSSF (i.e. MBSF or MBSTF) based on the GBA as in MBMS security (see TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102]) or based on the AKMA (see TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [104]). When the AKMA is used, the MRK is derived from the KAF as specified in Annex F of TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102] by replacing the Ks_NAF for the GBA_ME run with KAF. Furthermore, when the AKMA is used, the MUK is set to KAF. When the authorization of MBS service to the UE is required, the user id (e.g., GPSI) provided to the MBSSF by the AAnF shall be used. NOTE a: Void - The identifier(s) of MBS user service(s) in TS 26.502[ 5G multicast-broadcast services; User service architecture ] [108] is included in local configuration in MBSSF or in UDM as part of MBS subscription data for a UE, which identifies the user service(s) that the UE is allowed to join. After receiving the HTTP POST message (see clause 6.3.2 of TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102]) that] includes the identifier(s) of MBS user service(s), MBSSF shall authorize the UE based on local configuration if available. If no local configuration is available, the MBSSF should send verification request with user id (e.g., IMPI in GBA or GPSI in AKMA) and identifier(s) of MBS user service(s) to UDM to acquire the authorization result. If the UE is authorized, the MBSSF registers the UE to the MBS user service(s). NOTE: the local configuration in MBSSF may be preconfigured or provided by AF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | W.4.1.3 |
1,382 | 6.4.2 UE-requested PDU session modification procedure 6.4.2.1 General | The purpose of the UE-requested PDU session modification procedure is: a) to enable the UE to request modification of a PDU session; b) to indicate a change of 3GPP PS data off UE status for a PDU session; c) to revoke the previously indicated support for reflective QoS; d) to request specific QoS handling and segregation of service data flows; e) to indicate to the network the relevant 5GSM parameters and capabilities (e.g. the UE's 5GSM capabilities, whether the UE supports more than 16 packet filters, the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink, the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink and whether the UE requests the PDU session to be an always-on PDU session in the 5GS) for a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface and the UE has not previously successfully performed the UE-requested PDU session modification to indicate to the network the relevant 5GSM parameters and capabilities; f) to delete one or more mapped EPS bearer contexts; g) to convey a port management information container; h) to re-negotiate header compression configuration associated to a PDU session using control plane CIoT 5GS optimization; or i) to enable the UE to request to join or leave one or more multicast MBS sessions associated with a PDU session. j) to send the URSP rule enforcement report to the network. NOTE 1: The case c), d), e), f) and g) do not apply to PDU sessions associated with the control plane only indication. NOTE 2: For case e), the procedure is attempted after the first inter-system change from S1 mode to N1 mode. When the UE-requested PDU session modification procedure is used to indicate a change of 3GPP PS data off UE status for a PDU session (see subclause 6.2.10), the UE shall initiate the UE-requested PDU session modification procedure even if the UE is outside the LADN service area or the timer T3396, T3584, T3585 or the back-off timer is running or is deactivated. If the UE needs to revoke the previously indicated support for reflective QoS for a PDU session and timer T3396, T3584, T3585 or the back-off timer is running or is deactivated, the UE shall not initiate the UE-requested PDU session modification procedure and shall instead initiate the UE-requested PDU session release procedure. If the UE needs to initiate the UE-requested PDU session modification procedure to indicate to the network the relevant 5GSM parameters and capabilities (e.g. the UE's 5GSM capabilities, whether the UE supports more than 16 packet filters, the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink, the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink and whether the UE requests the PDU session to be an always-on PDU session in the 5GS) for a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, the UE is a UE operating in single-registration mode in the network supporting N26 interface, the UE has not previously successfully performed the UE-requested PDU session modification to indicate to the network the relevant 5GSM parameters and capabilities, and: a) timer T3396, T3584, T3585 or the back-off timer is running, the UE shall initiate the UE-requested PDU session modification procedure after expiry of timer T3396, T3584 or T3585 or after expiry of the back-off timer; or b) the UE is in substate 5GMM-REGISTERED.NON-ALLOWED-SERVICE and has not performed the the UE-requested PDU session modification procedure (see subclause 5.3.5), the UE shall initiate the UE-requested PDU session modification procedure after entering substate 5GMM-REGISTERED.NORMAL-SERVICE. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.2 |
1,383 | 4.25.2 SMF-NEF Connection Establishment | When the UE performs the PDU Session establishment with PDU Session type of "Unstructured" and the subscription information corresponding to the UE requested DNN includes the "NEF Identity for NIDD" (NEF ID), then the SMF initiates a SMF-NEF Connection establishment procedure towards the NEF corresponding to the "NEF ID" for that DNN / S-NSSAI Combination. Figure 4.25.2-1: SMF-NEF Connection procedure 1. Steps 1-7 and step 9 of clause 4.3.2.2.1 for UE-requested PDU Session Establishment Procedure for non-roaming scenarios or steps 1-9 of clause 4.3.2.2.2 for UE-requested PDU Session Establishment Procedure for home-routed roaming scenarios. The (H-)SMF receives the Session Management Subscription data for the corresponding SUPI, DNN and S-NSSAI that is associated with NEF Identity for NIDD and NIDD information such GPSI and AF Identifier. 2. If the subscription information corresponding to DNN and S-NSSAI includes the "NEF Identity for NIDD" (NEF ID), the SMF shall create a PDU session towards the NEF. The SMF invokes Nnef_SMContext_Create Request (User Identity, PDU Session ID, SMF ID, NIDD information, S-NSSAI, DNN, [RDS support indication], [Small Data Rate Control parameters], [Small Data Rate Control Status], [Serving PLMN Rate Control parameters]) message towards the NEF. The RDS support indication is included if the UE capability to support Reliable Data Service (RDS) is included in the PCO in the PDU Session Establishment Request message. The SMF provides Small Data Rate Control parameters to the NEF for PDU Session, if required. The SMF provides the Small Data Rate Control Status to the NEF, if received from the AMF. If the Serving PLMN intends to enforce Serving PLMN Rate Control (see clause 5.31.14.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) for this PDU session then the SMF shall provide Serving PLMN Rate Control parameters to NEF for limiting the rate of downlink control plane data packets. If no AF has previously performed the NIDD Configuration procedure with the NEF for the User Identity received in step 2, then the NEF initiates the NIDD Configuration procedure (see clause 4.25.3) before step 3. 3. The NEF creates an NEF PDU session Context and associates it with User Identity and PDU session ID. The NEF invokes Nnef_SMContext_Create Response (Cause, [RDS support indication], [Extended Buffering Support indication], [NIDD parameters]) towards the SMF confirming establishment of the PDU session to the NEF for the UE. If NEF supports and allows use of RDS, it includes the RDS support indication to SMF and the SMF includes it in the PCO. If NEF supports Extended Buffering, NEF includes Extended Buffering Support indication in the response and subscribes for mobility-related events with the AMF to receive an indication when the UE becomes reachable. The NIDD parameters (e.g. maximum packet size) are sent to the SMF, if available. 4. Steps 11-13 of clause 4.3.2.2.1 for UE-requested PDU Session Establishment Procedure for non-roaming scenarios or steps 13-16 of clause 4.3.2.2.2 for UE requested PDU Session Establishment Procedure for home-routed roaming scenarios. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.25.2 |
1,384 | 8.2.2 Handling ASN.1/PER encoded parameters | During the TAU/RAU/HO procedures MME/S4-SGSN GTPv2 entities send some of the RANAP/S1AP/BSSGP parameters to a GTPv2 peer. Copying of the BSSGP parameters into GTPv2 IEs is straightforward. RANAP and S1AP, however, use ASN.1/PER encoding, which is different from GTPv2 specific TLV encoding. Transparent copying of RANAP/S1AP parameters across GTPv2 interfaces: a GTPv2 entity shall transparently copy the respective information into one or more octets of the GTPv2 IE as specified in Annex B and clause 8.48. With this approach, GTPv2 will not be impacted if the contents of such RANAP/S1AP parameter changes over the time. Non-transparent copying of RANAP/S1AP parameters across GTPv2 interfaces: - GTPv2 entity decodes ASN.1/PER parameter and shall encode the value(s) into one or more octets of the GTPv2 IE according to what is specified in the present document. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.2.2 |
1,385 | 13.4.1.2.1 OAuth 2.0 roles | In the roaming scenario, OAuth 2.0 roles are as follows: a. The visiting Network Repository Function (vNRF) shall be the OAuth 2.0 Authorization server for vPLMN and authenticates the NF Service Consumer. b. The home Network Repository Function (hNRF) shall be OAuth 2.0 Authorization server for hPLMN and generates the access token. c. The NF Service Consumer in the visiting PLMN shall be the OAuth 2.0 client. d. The NF Service Producer in the home PLMN shall be the OAuth 2.0 resource server. OAuth 2.0 client (NF Service Consumer) registration with the OAuth 2.0 authorization server (NRF) in the vPLMN Same as in the non-roaming scenario in 13.4.1.1. OAuth 2.0 resource server (NF Service Producer) registration with the OAuth 2.0 authorization server (NRF) in the hPLMN Same as in the non-roaming scenario in 13.4.1.1. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.4.1.2.1 |
1,386 | 12.2.4 APN level load control 12.2.4.1 General | APN level load control refers to advertising of the load information at APN level granularity and selection of the target node based on this information. It helps to achieve an evenly load balanced network at APN granularity by the use of the dynamic load information provided within the Load Control Information with the APN scope. Only a PGW may advertise APN level load information. APN level load control is an optional feature that may be supported when the following pre-condition is applicable. Pre-Condition: In the given network, when the ratio of the configured APN resource to the overall capacity of the PGW is not the same across all the PGWs in the network. NOTE: In other cases, e.g. when all the resources of the PGW are available for all the APNs served by that PGW, the node level load information is exactly the same as APN level load information, for each of its APNs, and hence performing node load control is sufficient. If APN load control is supported and activated at the PGW, the PGW should advertise the APN load information. If the APN level load control feature is supported at the node performing the PGW selection, i.e. an MME, S4-SGSN, ePDG, TWAN, the node shall utilize this information when selecting the PGW. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.2.4 |
1,387 | 5.7A.3 Secondary RAT Usage Data Reporting Procedure | The procedure in Figure 5.7A.3-1 may be used to report Secondary RAT usage data from eNodeB to the MME. It is executed by the eNodeB to report the Secondary RAT usage data information which is then included in messages on S11 towards Serving GW and S5/S8 interface to the PGW (e.g. during I-RAT handover procedures, S1 handover, X2 handover). This then further uses existing EPC signalling of the procedures involved. The procedure in Figure 5.7A.3-2 may be used to report the Secondary RAT usage data from MME to the Serving GW. Optionally, it is used to report the Secondary RAT usage data from Serving GW to the PDN GW when the reporting to PDN GW is activated. If the Secondary RAT usage data is provided by an S1AP message from eNodeB to MME other than the one indicated in Figure 5.7A.3-1, the procedures in clause 5.7A.3-2 may be used to transfer the secondary RAT usage data to the Serving GW and PDN GW (e.g. during S1 Release procedure). The eNodeB may also provide the user location information, e.g. ECGI, PSCell ID. During IRAT handovers, the procedures 5.7A.3-1 to 5.7A.3-2 in its entirety is executed to provide reporting of Secondary RAT usage data to the Serving GW and to the PDN GW if PGW secondary RAT usage data reporting is active. Handover related signalling of IRAT procedures may be used to provide reporting of Secondary RAT usage data to the Serving GW instead of the signalling of figure 5.7A.3-2, when PGW secondary RAT usage data reporting is not active. Figure 5.7A.3-1: RAN Secondary RAT usage data Reporting procedure 1. The eNodeB, if it supports Dual Connectivity with Secondary RAT (using NR radio (see clause 4.3.2a on Support for Dual Connectivity), using unlicensed spectrum in the form of LAA/LWA/LWIP/NR-U (see clause 4.3.30)) and it is configured to report Secondary RAT usage data for the UE, depending on certain conditions documented in this specification, it shall send a RAN usage data Report message to the MME including the Secondary RAT usage data for the UE. The eNodeB will send only one RAN usage report for a UE when the UE is subject to handover by RAN. The RAN usage data report includes a handover flag to indicate when the message is sent triggered by X2-handover. If Dual Connectivity is active or had been activated by that eNodeB, the eNodeB shall add the PSCell ID (and the time elapsed since the Dual Connectivity was released if Dual Connectivity is no longer activated) to the RAT usage data Report message. In the case of X2 handover, the MME is expected to handle a secondary RAT data reporting received from the source eNodeB within a short time after Path Switch Request by forwarding it to the SGW, e.g. using the GW Secondary RAT usage data Reporting procedure. Figure 5.7A.3-2: GW Secondary RAT usage data Reporting procedure The eNodeB, if it supports Dual Connectivity with Secondary RAT (using NR radio (see clause 4.3.2a on Support for Dual Connectivity), using unlicensed spectrum in the form of LAA/LWA/LWIP/NR-U (see clause 4.3.30)) and it is configured to report Secondary RAT usage data for the UE, it shall send include the Secondary RAT usage data for the UE to the MME in certain messages depending on certain conditions documented elsewhere in this TS. Secondary RAT usage reporting from the eNodeB is provided using S1 signalling message which are either at the UE level (eg. Path Switch Request, etc), or at bearer level (eg. E-RAB modification indication, Deactivate bearer response, etc.) as captured in relevant clauses in this specification. If Secondary RAT usage report is provided in bearer level signalling message by the eNodeB, the Secondary RAT usage report is related only to the specific bearer. 1. The MME forwards the Secondary RAT usage data and User Location Information, PSCell ID to the SGW in a Change Notification Request (Secondary RAT usage data) message. If the SGW is requested to forward Secondary RAT usage data to the PGW, the MME includes a flag causing the SGW to forward this to the PGW. Also, the MME informs the Serving GW if the secondary RAT usage data shall not be processed by the Serving GW (e.g. during Serving GW relocation when the usage data is to be forwarded via the target Serving GW). 2. The Serving GW may, based on flags received in the previous message and local configuration in the Serving GW, send the Change Notification (Secondary RAT usage data) message to the PDN GW. 3. The PDN GW acknowledges receiving the Secondary RAT usage data for the UE by a Change Notification Ack() message to the Serving GW. 4. The SGW acknowledges by sending a Change Notification ack() message back to the MME. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7A.3 |
1,388 | – RACH-ConfigGenericTwoStepRA | The IE RACH-ConfigGenericTwoStepRA is used to specify the 2-step random access type parameters. RACH-ConfigGenericTwoStepRA information element -- ASN1START -- TAG-RACH-CONFIGGENERICTWOSTEPRA-START RACH-ConfigGenericTwoStepRA-r16 ::= SEQUENCE { msgA-PRACH-ConfigurationIndex-r16 INTEGER (0..262) OPTIONAL, -- Cond 2StepOnly msgA-RO-FDM-r16 ENUMERATED {one, two, four, eight} OPTIONAL, -- Cond 2StepOnly msgA-RO-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Cond 2StepOnly msgA-ZeroCorrelationZoneConfig-r16 INTEGER (0..15) OPTIONAL, -- Cond 2StepOnly msgA-PreamblePowerRampingStep-r16 ENUMERATED {dB0, dB2, dB4, dB6} OPTIONAL, -- Cond 2StepOnlyNoCFRA msgA-PreambleReceivedTargetPower-r16 INTEGER (-202..-60) OPTIONAL, -- Cond 2StepOnlyNoCFRA msgB-ResponseWindow-r16 ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80, sl160, sl320} OPTIONAL, -- Cond NoCFRA preambleTransMax-r16 ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Cond 2StepOnlyNoCFRA ..., [[ msgB-ResponseWindow-v1700 ENUMERATED {sl240, sl640, sl960, sl1280, sl1920, sl2560} OPTIONAL -- Cond NoCFRA2 ]] } -- TAG-RACH-CONFIGGENERICTWOSTEPRA-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,389 | 4.3.1.7.2 Average quality of the neighboring cell when HO is triggered | This measurement provides the average quality of the neigbor cell that triggered HO (target HO cell) reported in the UE measurement reports. The average is computed over all measurement reports that triggered HO during the measurement granularity period. Separate measurement is produced for each measurement quantity {RSRP, RSRQ}. DER (n=1) For each UtranRelation, this measurement is obtained by accumulating the value (linear value converted from dbm unit) of the quality of neighbor (target) cell (RSRP, RSRQ) in the UE measurement report causing HO to the subject neighbor (target) cell on the UtranRelation, and dividing the accumulated value by the number of HO occurrence on the UtranRelation at the end of granularity period, and converting the value back to dbm unit from linear value. Separate measurement is provided for RSRP and for RSRQ. Each measurement is a single integer value in dBm (RSRP) or dB (RSRQ) HO.TrgtCellQual.RSRP HO.TrgtCellQual.RSRQ EUtranRelation Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.7.2 |
1,390 | 4.3.5.8A Homogenous Support of IMS Voice over PS Sessions Indication | The "Homogenous Support of IMS Voice over PS Sessions" indication is provided by the MME to the HSS, and can be used by the HSS to avoid requesting the serving nodes whether or not an IMS Voice over PS session according to TS 22.173[ IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 ] [73] with a bearer that supports Conversational Voice as specified in TS 23.203[ Policy and charging control architecture ] [6] is supported. This indication is stored in the MME MM context. The MME shall behave as follows whenever it sends a Update Location Request or a Notify Request message to the HSS: - if "IMS Voice over PS Sessions" is supported homogeneously in all TAs in the serving MME for the UE, the MME shall include the "Homogenous Support of IMS Voice over PS Sessions" indication set to "Supported". - if none of the TAs of the serving MME supports "IMS Voice over PS Sessions" for the UE, the MME shall include the "Homogenous Support of IMS Voice over PS Sessions" indication set to "Not supported". - if "IMS Voice over PS Sessions" support is either non-homogeneous or unknown, the MME shall not include the "Homogenous Support of IMS Voice over PS Sessions" indication. Regarding homogenous support/non-support of IMS Voice over PS session for all registered TAs of the UE, see clause 4.3.5.8. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.5.8A |
1,391 | 5.1.2.2 Legacy service support | In principle, the 5G system shall support all EPS capabilities (e.g. from TSs 22.011, 22.101, 22.278, 22.185, 22.071, 22.115, 22.153, 22.173, 22.468). However, - voice service continuity from NG-RAN to GERAN shall not be supported, - voice service continuity from NG-RAN to UTRAN CS should be supported (see Note), - voice service continuity from GERAN to NG-RAN shall not be supported, - voice service continuity from UTRAN to NG-RAN shall not be supported, - CS fallback from NG-RAN to GERAN shall not be supported, - CS fallback from NG-RAN to UTRAN shall not be supported, - seamless handover between NG-RAN and GERAN shall not be supported, - seamless handover between NG-RAN and UTRAN shall not be supported, - access to a 5G core network via GERAN or UTRAN shall not be supported, - video service continuity between 5GS and UMTS shall not be supported, - IP address preservation for PS service when UE moves between 5GS and GSM/UMTS shall not be supported, and - Service continuity between 5GS and CDMA2000 shall not be supported. NOTE: Architectural or protocol changes needed to support voice service continuity from NG-RAN to UTRAN CS are expected to have minimum impact on architecture, specifications, or the development of the 5G New Core and New Radio. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.1.2.2 |
1,392 | 4.11.0a.5 PDN Connection Establishment | During establishment of non-emergency PDN connection in the EPC, the UE and the SMF+PGW-C exchange information via PCO as described in clause 5.15.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For UE with 5GC NAS capability disabled (i.e. N1 mode is disabled), the UE may also allocate a PDU Session ID and send it to the SMF+PGW-C via PCO. If the SMF+PGW-C supports more than one S-NSSAI and the APN is valid for more than one S-NSSAI, before the SMF+PGW-C provides an S-NSSAI to the UE, the SMF+PGW-C should check such that the selected S-NSSAI is among the UE's subscribed S-NSSAIs which supports interworking with EPC and that the S-NSSAI is not subject to Network Slice-Specific Authentication and Authorization, by retrieving the Subscribed S-NSSAI from UDM using the Nudm_SDM_Get service operation (the SMF+PGW-C discovers and selects a UDM as described in clause 6.3.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If the SMF+PGW-C is in a VPLMN, the SMF+PGW-C uses the Nnssf_NSSelection_Get service operation to retrieve a mapping of the Subscribed S-NSSAIs to Serving PLMN S-NSSAI values. If the S-NSSAIs supported by the SMF+PGW-C are all subject to NSSAA, then the SMF+PGW-C should reject the PDN connection establishment. If the selected S-NSSAI is subject to NSAC and EPS counting is required for the S-NSSAI, the SMF+PGW-C uses the Nnsacf_NSAC_NumberOfUEsUpdate services operation and/or the Nnsacf_NSAC_NumberOfPDUsUpdate services operation to check if the selected S-NSSAI is available as described in clause 4.11.5.9. The SMF+PGW-C uses the Nudm_SDM_Subscribe service operation to subscribe the change of the Session Management Subscription data. If the SMF+PGW-C is notified from UDM with subscription data change, the SMF+ PGW-C takes actions for the PDN connection as described in clause 5.17.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. As described in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74], during establishment of a PDN connection, a UE that hosts EEC(s) may indicate to the SMF+PGW-C, in the PCO, that it supports the ability to receive ECS address(es) via NAS and to transfer the ECS Address(es) to the EEC(s). If the UE indicated in the PCO that it supports the ability to receive ECS address(es) via NAS, the SMF+PGW-C may provide the ECS Address Configuration Information (as described in clause 6.5.2 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]) to the UE in the PCO. The SMF+PGW-C may derive the Edge Configuration Server Information based on local configuration, the UE's location and/or UE subscription information. The SMF+PGW-C may use the bearer modification procedure without bearer QoS update to send the UE a PCO with updated ECS Address Configuration Information as defined in clause 6.5.2 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74] to the UE. During establishment of non-emergency PDN connection in the EPC, if PGW-C+SMF is selected for a UE that has 5GS subscription, the SMF may be configured to obtain the subscribed IP index from UDM as part of subscription data using the Nudm_SDM_Get service operation (the PGW-C+SMF discovers and selects a UDM as described in clause 6.3.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). During establishment of non-emergency PDN connection in EPC, if PGW-C+SMF is selected for a UE that has 5GS subscription, the SMF may be configured to obtain the subscribed User Plane Security Policy from UDM as part of subscription data using the Nudm_SDM_Get service operation (the PGW-C+SMF discovers and selects a UDM as described in clause 6.3.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The SMF uses the subscribed User Plane Security Policy as described in clause 5.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. During establishment of non-emergency PDN connection in the EPC, if SMF+PGW-C is selected for a UE that has 5GS subscription but does not support 5GC NAS and is accessing via EPC/E-UTRAN and if the SMF+PGW-C supports more than one S-NSSAI and the APN is valid for more than one S-NSSAI, the SMF+PGW-C+PGW-C may proceed as specified in first paragraph of this clause or select any S-NSSAI associated with the APN of the PDN connection. The SMF+PGW-C shall not provide any 5GS related parameters to the UE. NOTE 1: The SMF+PGW-C knows that the UE does not support 5GS NAS if the UE does not provide PDU Session ID in PCO (see clause 5.15.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). During establishment of emergency PDN connection: - The SMF+PGW-C is to be derived from the emergency APN or to be statically configured in the Emergency Configuration Data in MME. - 5GC interworking support with N26 or without N26 is determined based on UE's 5G NAS capability and local configuration (in the Emergency Configuration Data in MME). - The S-NSSAI configured for the emergency APN in SMF+PGW-C is not sent to the UE by the SMF+PGW-C. One S-NSSAI is configured for the emergency APN. During establishment of non-emergency PDN connection and emergency PDN connection, if SMF+PGW-C is selected for a UE that does not support 5GC NAS, the SMF+PGW-C creates unique PDU Session ID for each PDN connection of the UE. - The unique PDU Session ID can be created based on the EPS Bearer IDs assigned by the MME for the PDN Connections associated with the UE and not be in the range of PDU Session ID values that can be created by a 5GC NAS capable UE. - If handover between EPS and EPC/ePDG (as specified in clause 8.6 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26]) is required, the SMF+PGW-C, based on operator configuration, may perform the following to ensure the uniqueness of PDU Session ID: - the SMF+PGW-C queries the UDM for any PDU Session ID(s) that are already registered in the UDM for the UE by invoking Nudm_UECM_Get service operation. - the SMF+PGW-C creates a PDU session ID that does not collide with the received PDU session ID(s). - When the SMF+PGW-C establishes the PDN connection successfully, the SMF+PGW-C performs UDM registration using the Nudm_UECM_Registration service operation. NOTE 2: If the scenario that a UE handovers a PDN connection with APN1 established via MME to ePDG and then establishes a second PDN connection with APN2 via MME needs to be supported in a given deployment, then, based on operator configuration, the SMF+PGW-C can query the UDM to avoid that the same PDU Session ID value of first PDN connection would be assigned by the SMF+PGW-C for the second PDN connection. When the SMF+PGW-C establishes the PDN connection successfully, the SMF+PGW-C provides the ID of the PCF ID selected for the PDN connection in the UDM using the Nudm_UECM_Registration service operation. A SMF+PGW-C may support L2TP as described in clause 4.3.2.4. In this case step 1 and step 7 of Figure 4.3.2.4-1 correspond to a PDN Connection establishment and a SMF+PGW-C replaces the SMF in that Figure. To support User Plane Integrity Protection with EPS and policies that Require User Plane integrity protection to be used, at PDN connection establishment, the MME shall indicate to the SMF+PGW-C (via the Serving GW) whether the UE, the current eNB and the MME support User Plane Integrity Protection in EPS. If the MME and the UE support User Plane Integrity Protection, then the SMF+PGW-C informs the MME of the User Plane integrity protection policy (Required, Preferred, Not Needed) applicable to the PDN connection on a per-EPS bearer basis. In turn, the MME informs the eNB. To support URSP Provisioning in EPS, during Initial Attach with default PDN connection establishment procedure in EPS, the UE provides the "Indication of URSP Provisioning Support in EPS" in the PCO or in the ePCO in the PDN connectivity request as described in clause 5.17.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the SMF+PGW-C supports URSP Provisioning in EPS and the ePCO capability, it provides the "Indication of URSP Provisioning Support in EPS" in the ePCO in the Create Session Response. If the UE receives the "Indication of URSP Provisioning Support in EPS" in the ePCO from SMF+PGW-C provided in the PDN Connectivity Accept message, the UE initiates the UE requested bearer resource modification procedure and includes the UE Policy Container in the ePCO in the Request Bearer Resource Modification message, see clause 4.11.0a.10. If the default PDN connection is not established during Initial Attach procedure, the aforementioned procedure happens during the first request for PDN connectivity. If the negotiation of the support of URSP provisioning in EPS fails for the first PDN connection the UE may retry the aforementioned procedure successively for the next PDN connectivity requests until it succeeds for one of them as specified in clause 5.17.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.5 |
1,393 | 4.3.23 Access network selection and traffic steering based on RAN-assisted WLAN interworking | As described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5], TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34], TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] and TS 25.331[ None ] [33], UTRAN and E-UTRAN may provide RAN assistance parameters to the UE via RRC signalling. The RAN assistance parameters may e.g. include E-UTRAN signal strength and quality thresholds, WLAN channel utilization thresholds, WLAN backhaul data rate thresholds, a list of WLAN identifiers and Offload Preference Indicator (OPI). The UE uses the RAN assistance parameters to perform access network selection and traffic steering decisions between 3GPP access and WLAN using procedures defined in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34] or using ANDSF policies defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Co-existence between the procedures defined in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34] and ANDSF policies is described in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. For traffic steering decisions using procedures defined in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34] the MME may provide information to the UE indicating which PDN Connection can be offloaded to WLAN and which PDN Connection shall not be offloaded to WLAN. When provided by the MME, this indication is provided in NAS signalling on a per PDN Connection basis when a PDN Connection is established. The MME may provide a per-RAT indication for the PDN connection, e.g. if the indication is different for UTRAN and for E-UTRAN. If the MME provides a single indication, the UE shall apply such indication both to E-UTRAN and UTRAN. Traffic steering decisions using procedures defined in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34] are not applicable to non-seamless WLAN offload (see TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2] for the definition of non-seamless WLAN offload). In order for the operator to allow/prohibit WLAN offloading on per user and per APN basis, subscription data in the HSS may be configured to indicate if WLAN offload is allowed or prohibited for an APN. The MME determines the WLAN offloading permissions for the UE and PDN Connection as described below: - The MME determines the offloadability of a PDN Connection based on subscription data and locally configured policy (e.g. for roaming users or when the subscription data does not include any WLAN offloadability indication). - When the UE establishes a new PDN Connection, the MME may indicate whether this PDN Connection is offloadable or not offloadable to WLAN. - The MME may provide an updated WLAN offloadability indication of a PDN Connection to the UE. This may be initiated by HSS as part of the Insert Subscriber Data procedure as described in clause 5.3.9.2. It can also be initiated by the MME by initiating steps 4 to 7 of the Bearer Modification Procedure in clause 5.4.3, Figure 5.4.3-1 or by adding the WLAN offloadability indication to a session management NAS message sent to the UE as part of an existing procedure. The MME shall not trigger signalling to an ECM-IDLE UE solely for the purpose of updating the WLAN offloadability indication. When the UE applies the procedures defined in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34] and TS 25.304[ None ] [12], if the UE has Local Operating Environment Information (LOEI), as defined in TS 23.261[ IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2 ] [54], the UE shall consider the RAN rules in combination with the non-radio related aspects of LOEI, and shall give priority to LOEI if it indicates WLAN is not acceptable for non-radio related reasons. For example, if the active RAN rule indicates that traffic shall be moved to WLAN access, but the LOEI in the UE indicates that WLAN access is unacceptable due to non-radio related causes (e.g. due to authentication issues, low battery power, etc.), the UE shall not move the traffic to WLAN. When the UE applies the procedures defined in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34], the UE takes into account the WLAN offloadability indication from MME to perform handover between 3GPP access and WLAN access using the handover procedures described in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. When the UE receives a WLAN offloadability indication from the network for a PDN connection the UE stores it for the lifetime of that PDN Connection and updates it if a new value is received from the network. The UE shall apply the latest indication previously received for the PDN Connection. The indication of whether a PDN connection is offloadable or not offloadable should be passed from the source to the target serving node in mobility management procedures from a MME to a MME/SGSN. This allows the target SGSN/MME to learn the indication previously provided to the UE and to decide the need for providing an updated indication to the UE. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.23 |
1,394 | 8.24.1 RAN TSS reporting towards the CN | The signaling flow for RAN TSS reporting towards the CN is shown in Figure 8.24.1-1. This procedure is used when the TSCTSF subscribes to RAN TSS reporting at the AMF as described in TS 23.502[ Procedures for the 5G System (5GS) ] [32]. Figure 8.24.1-1: RAN TSS reporting towards the CN 0. The gNB-DU is pre-configured with a threshold for each RAN TSS attribute it supports. The gNB-DU does not report RAN TSS attribute values better than the pre-configured thresholds, i.e. if a RAN TSS attribute has a value better than the pre-configured threshold, the gNB-DU reports the threshold value to the gNB-CU instead. NOTE 1: It is assumed the pre-configured thresholds in the gNB-DU are sufficient to meet UE time sync performance requirement which are configured by the operator. 1. The AMF requests RAN TSS reporting by sending the TIMING SYNCHRONISATION STATUS REQUEST message to the gNB-CU. 2. The gNB-CU requests RAN TSS reporting from at least one gNB-DU by sending the TIMING SYNCHRONISATION STATUS REQUEST message to the gNB-DU. NOTE 2: It is up to gNB-CU implementation whether to send the request to all its gNB-DUs or to a particular subset of its gNB-DUs, depending on e.g. network topology. 3. The gNB-DU replies to the gNB-CU by sending the TIMING SYNCHRONISATION STATUS RESPONSE message. 4. The gNB-CU replies to the AMF by sending the TIMING SYNCHRONISATION STATUS RESPONSE message. If the gNB-CU does not receive a successful response from at least one gNB-DU, the gNB-CU replies to the AMF by sending the TIMING SYNCHRONISATION STATUS FAILURE message and the flow stops at this step. 5. Upon sending the response to the gNB-CU, the gNB-DU provides a first RAN TSS report to the gNB-CU by sending the TIMING SYNCHRONISATION STATUS REPORT message. NOTE 3: The RAN TSS attributes included in the report is up to gNB-DU implementation. 6. The gNB-CU sends the TIMING SYNCHRONISATION STATUS REPORT message to the AMF. The message contains the RAN TSS attributes received from the gNB-DU and the RAN TSS Scope IE to indicate whether the scope of the RAN TSS report is “RAN node level” or “cell list level”. 7. Later, the gNB-DU detects a primary source event: a) a RAN TSS attribute cannot meet a pre-configured threshold (i.e. status is degraded); b) a RAN TSS attribute meets the pre-configured threshold again (i.e. status is no longer degraded); c) event a) occurred and b) has not yet been reached, the gNB-DU performs periodic reporting or a previously reported RAN TSS attribute value can no longer be met. NOTE 4: Additional primary source events, if any, are up to gNB-DU implementation. 8. Upon detecting the primary source event, the gNB-DU provides an updated RAN TSS report to the gNB-CU by sending a TIMING SYNCHRONISATION STATUS REPORT message. 9. Same as step 6. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.24.1 |
1,395 | C.4.2 High level common architecture | The logical ubiquitous charging architecture and the information flows for offline and online charging of figure 4.2.1, applied to the convergent scenario (i.e. both the Fixed Broadband Access network and Evolved Packet Core (EPC) owned by a single operator) with PCEF located in Fixed Broadband Access is shown in the figure C.4.2.1 below, based on Architecture defined in TS 23.203[ Policy and charging control architecture ] [71] annex S clause S.4.1. Figure C.4.2.1: Logical ubiquitous charging architecture and information flows PCEF located in IP-Edge | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | C.4.2 |
1,396 | 4.2.5.2 UE Reachability Notification Request procedure | The UE Reachability Notification Request procedure is illustrated in figure 4.2.5.2-1. Figure 4.2.5.2-1: UE Reachability Notification Request Procedure 1a. [Conditional] When a service-related entity requests the UDM to provide an indication regarding UE reachability, the UDM checks whether that service-related entity is authorized to perform this request on this subscriber. The service-related entity may subscribe in UDM to receive notifications about UE Reachability or UE Reachability for SMS delivery events as defined in clause 4.15.3. NOTE 1: This request for UE Reachability Notification is received in UDM using different interfaces/services depending on the service-related entity. For example, an SBI capable service-related entity can use the Nudm_EventExposure_Subscribe service while an SMS-GMSC using non-SBI interfaces triggers this procedure as described in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7]. The UDM may retrieve from the UDR the list of NF IDs for Network Functions authorized by the HPLMN to request notifications on this UE's reachability. If the entity is not authorized, the UDM may reject the request (e.g. if the requesting entity is recognized as being a valid entity, but not authorized for that subscriber) or discard it silently (e.g. if the requesting entity is not recognized). Appropriate O&M reports are generated. 1b. [Conditional] The UDM stores the identity of the service-related entity. In the case that the service-related entity is an SMS-GMSC using non-SBI interfaces, the UDM stores the SC address within the MWD list. Otherwise, if the service-related entity is an SBI capable service-related entity, the UDM stores the address of the SBI capable service-related entity in the form of a subscription to the Nudm_EventExposure service. If the UE Reachability Notification Request is for SMS over NAS and no SMSF is registered for the target UE, steps 2 to 4 are skipped. Otherwise the UDM sets the URRP-AMF flag parameter and continues with step 2. 1c. [Conditional] An NF (e.g. SMF) may subscribe event of UE reachability status change by using the Namf_EventExposure_Subscribe service operation. Steps 2 to 4 are skipped. The AMF invokes the Namf_EventExposure_Notify service operation to report the current reachability state of a UE to the NF if requested by the consumer NF. 2. [Conditional] If the value of URRP-AMF flag parameter changes from "not set" to "set" and an AMF is registered in the UDM for the target UE, the UDM initiates Namf_EventExposure_Subscribe service operation for UE reachability for UE reachable for DL traffic (SUPI, UE Reachability) towards the AMF. The UDM may indicate if direct notification to NF shall be used by the AMF. When direct notification to NF is indicated to the AMF, the URRP-AMF is not set in the UDM in step 1a for NF initiated requests. If the service-related entity requested UDM to receive notifications about UE Reachability for SMS delivery, the UDM shall not indicate direct notification to NF. NOTE 2: The UDM can trigger UE Reachability Notification Request procedure with two different AMFs for a UE which is connected to 5G Core Network over 3GPP access and non-3GPP access simultaneously. Also, for interworking with EPC, the UDM/HSS can trigger UE Reachability Notification Request procedure with MME as described in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 3. The AMF checks that the requesting entity is authorized to perform this request on this subscriber. If the AMF has an MM Context for that user, the AMF stores the NF ID in the URRP-AMF information, associated with URRP-AMF information flag to indicate the need to report to the UDM or directly to the NF with a UE Activity Notification (see clause 4.2.5.3). 4. [Conditional] For UE reachability for UE reachable for DL traffic, if the UE state in AMF is in CM-CONNECTED state and the Access Type is 3GPP access, the AMF initiates N2 Notification procedure (see clause 4.8.3) with reporting type set to Single RRC_CONNECTED state notification. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.5.2 |
1,397 | 6.9.3 Mapping to resource elements | The sequence for each of the PHICH groups is defined by where the sum is over all PHICHs in the PHICH group and represents the symbol sequence from the :th PHICH in the PHICH group. PHICH groups are mapped to PHICH mapping units. For normal cyclic prefix, the mapping of PHICH group to PHICH mapping unit is defined by where , and where is given by Table 6.9-1. For extended cyclic prefix, the mapping of PHICH group and to PHICH mapping unit is defined by where and where is given by Table 6.9-1. Let , denote symbol quadruplet for antenna port. Mapping to resource elements is defined in terms of symbol quadruplets according to steps 1–10 below: 1) For each value of 2) Let denote the number of resource element groups not assigned to PCFICH in OFDM symbol 3) Number the resource-element groups not assigned to PCFICH in OFDM symbol from 0 to, starting from the resource-element group with the lowest frequency-domain index. 4) Initialize (PHICH mapping unit number) 5) For each value of 6) Symbol-quadruplet from PHICH mapping unit is mapped to the resource-element group represented by as defined in clause 6.2.4 where the indices and are given by steps 7 and 8 below: 7) The time-domain index is given by 8) Set the frequency-domain index to the resource-element group assigned the number in step 3 above, where is given by in case of extended PHICH duration in MBSFN subframes, or extended PHICH duration in subframes 1 and 6 for frame structure type 2, or extended PHICH duration in subframe with the same duration as the DwPTS duration of a special subframe configuration in frame structure type 3 and by otherwise. 9) Increase by 1. 10) Repeat from step 5 until all PHICH mapping units have been assigned. The PHICH duration is configurable by higher layers according to Table 6.9.3-1. The PHICH shall not be transmitted in MBSFN subframes with zero-size non-MBSFN region. Table 6.9.3-1: PHICH duration in MBSFN and non-MBSFN subframes | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.9.3 |
1,398 | 13.2.3.1 Overview of protection policies | The protection policy suite is comprised of a data-type encryption policy and a modification policy. Together, these policies determine which part of a certain message shall be confidentiality protected and which part of a certain message shall be modifiable by IPX providers. The SEPP shall apply the protection policies for application layer protection of messages on the N32-f interface. There are two types of protection policies, namely: - Data-type encryption policy: specifies which data types need to be confidentiality protected; - Modification policy: specifies which IEs are modifiable by intermediaries. In addition, there is a mapping between the data-types in the data-type encryption policy and the IEs in NF API descriptions which is given in a NF-API data-type placement mapping. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.3.1 |
1,399 | 5.1 Identification for routeing purposes | MSCs, GSNs, location registers and CSSs are identified by international E.164 numbers and/or Signalling Point Codes ("entity number", i.e., "HLR number", "VLR number", "MSC number", "SGSN number", "GGSN number" and "CSS number") in each PLMN. MMEs that support "SMS in MME" are identified by international PSTN/ISDN numbers for SM Routing via an IWF (i.e. "MME number for MT SMS"). Additionally SGSNs and GGSNs are identified by GSN Addresses. These are the SGSN Address and the GGSN Address. A GSN Address shall be composed as shown in figure 9. Figure 9: Structure of GSN Address The GSN Address is composed of the following elements: 1) The Address Type, which is a fixed length code (of 2 bits) identifying the type of address that is used in the Address field. 2) The Address Length, which is a fixed length code (of 6 bits) identifying the length of the Address field. 3) The Address, which is a variable length field which contains either an IPv4 address or an IPv6 address. Address Type 0 and Address Length 4 are used when Address is an IPv4 address. Address Type 1 and Address Length 16 are used when Address is an IPv6 address. The IP v4 address structure is defined in RFC 791 [14]. The IP v6 address structure is defined in RFC 2373 [15]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.1 |
1,400 | 4.16.7 Negotiations for future background data transfer 4.16.7.1 General | The procedure for future background data transfer as specified in clause 4.16.7.2 enables the negotiation between the NEF and the H-PCF about the transfer policies for the future background data transfer (as described in clause 6.1.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). The transfer policies consist of a desired time window for the background data transfer, a reference to a charging rate for the time window, network area information and optionally a maximum aggregated bitrate, as described in clause 6.1.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. This negotiation is preliminarily conducted (when AF initiates a procedure to NEF) before the UE's PDU Session establishment. When the AF wants to apply the Background Data Transfer Policy to an existing PDU Session, then at the time the background data transfer is about to start the AF invokes the Npcf_PolicyAuthorization_Create service directly with PCF, or via the NEF, to apply the background data transfer policy for an individual UE. When the AF wants to apply the Background Data Transfer Policy to a future PDU Session, then the AF invokes Nnef_ApplyPolicy_Create service to provide, to the NEF, the Background Data Transfer Reference ID together with the External Identifier or External Group Identifier of the UE(s) that are subject to the policy. The procedure for BDT warning notification as specified in clause 4.16.7.3 enables the PCF to notify the AF that the network performance in the area of interest goes below the criteria set by the operator as described in clause 6.1.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.7 |
Subsets and Splits