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
⌀ |
|---|---|---|---|---|---|---|---|
3,701 | 9.10.2.2 TDD | The requirements are specified in Table 9.10.2.2-4, with the additional parameters in Table 9.10.2.2-1, Table 9.10.2.2-2 and Table 9.10.2.2-3. In Table 9.10.2.2-1, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals, PBCH and can transmit PDSCH, and transmission point 2 (TP 2) has different Cell ID and can transmit PDSCH. The downlink physical channel setup for TP 1 is according to Table C.3.2 and for TP 2 according to Table C.3.2. Table 9.10.2.2-1: Test Parameters Table 9.10.2.2-2: Configurations of PQI and DL transmission hypothesis for each PQI set (Fixed TP1 case) Table 9.10.2.2-3: Configurations of PQI and DL transmission hypothesis for each PQI set (Follow CRI case) Table 9.10.2.2-4: Minimum requirement (FDD) | 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 | 9.10.2.2 |
3,702 | 9.5.9.3 Protocol configuration options | This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the MS and the extended protocol configuration options IE is not supported by both the MS and the network end-to-end for the PDN connection (see subclause 6.1.3.7). This IE is also included to indicate the selected Bearer Control Mode to be applied when the extended protocol configuration options IE is not supported by the MS or the network or both end-to-end for the PDN connection (see subclause 6.1.3.7). | 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.9.3 |
3,703 | 5.2.2.5.3 Namf_Location_EventNotify service operation | Service operation name: Namf_Location_EventNotify Description: Provides UE location related event information related to emergency sessions or deferred location to the consumer NF. Input, Required: Type of location related event (e.g. emergency session initiation, deferred location for the UE available event, activation of location for periodic or triggered location, mobility of a target UE to a new AMF or MME for a deferred location), UE Identification (SUPI or PEI). Input, Optional: GPSI, Geodetic Location, Local Location including Coordinate ID, Civic Location, Indoor/Outdoor indicatio, Position methods used, Notification Target address, Notification Correlation ID, address of a new AMF or MME or MSC server Identity for 5G-SRVCC as specified in TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [81], achieved Location QoS Accuracy. Output, Required: None. Output, Optional: None. See steps 5 and 8 of clause 6.10.1 and step 19 of clause 6.3.1 of TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [51] and clause 6.5.4 of TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [81] for examples of usage of this service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.5.3 |
3,704 | 4.25.8 NEF Initiated SMF-NEF Connection Release procedure | NEF initiates a SMF-NEF connection release procedure in the following cases: - when a NIDD Authorization Update Request from the UDM indicates that the User is no longer authorized for NIDD, or - failure of AF or failure of AF connection, or - based on a request from the AF. Figure 4.25.8-1 illustrates the NEF Initiated SMF-NEF Connection Release procedure based on a request from AF. Figure 4.25.8-1: NEF Initiated SMF-NEF Connection Release procedure on the AF request 1. AF may indicate that a User's NIDD SMF-NEF connection is no longer needed by invoking Nnef_NIDDConfiguration_Delete Request (TLTRI) toward NEF. 2. The NEF deletes the NEF PDU session Context associated with the TLTRI and acknowledges the deletion of the NIDD configuration by invoking Nnef_NIDDConfiguration_Delete Response to the AF. 3. The NEF notifies the deletion of the SM context information by invoking Nnef_SMContext_DeleteNotify Request toward the SMF. 4. The SMF acknowledges the notification by invoking Nnef_SMContext_DeleteNotify Response to the NEF. 5. If the PDU session is not longer needed, the SMF performs steps 2-11 of PDU Session Release Procedure (see clause 4.3.4.2). Figure 4.25.8-2 illustrates the NEF Initiated SMF-NEF Connection Release procedure based on the NIDD Authorization Update. Figure 4.25.8-2: NEF Initiated SMF-NEF Connection Release procedure on the NIDD Authorization Update 1. On NIDD Authorization Update by UDM, NEF may determine that it needs to release the corresponding SMF-NEF Connection. 2. The NEF deletes the corresponding NEF PDU session Context and notifies the deletion of the SM context information by invoking Nnef_SMContext_DeleteNotify Request toward the SMF. 3. The SMF acknowledges the notification by invoking Nnef_SMContext_DeleteNotify Response to the NEF. 4. If the PDU session is not longer needed, the SMF performs steps 2-11 of PDU Session Release Procedure (see clause 4.3.4.2). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.25.8 |
3,705 | 8.2.1.2.7 Minimum Requirement 2 Tx Antenna Port (Superposed transmission) | The requirements are specified in Table 8.2.1.2.7-2, with the addition of the parameters in Table 8.2.1.2.7-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the minimun performance of transmit diversity (SFBC) with 2 transmitter antennas superposed with simultaneous PDSCH interference. Table 8.2.1.2.7-1: Test Parameters for Minimum Requirement 2 Tx Antenna Port - Superposed transmission (FRC) Table 8.2.1.2.7-2: Minimum Performance for Minimum Requirement 2 Tx Antenna Port - Superposed transmission (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.2.1.2.7 |
3,706 | 5.37.8.3 End of Data Burst Indication | An indication of End of Data Burst may be provided to the NG-RAN by the UPF, e.g. to configure UE power management schemes like connected mode DRX. Based on the End of Data Burst Marking Indication in a PCC rule and/or on local operator policies, SMF should request the UPF to detect the last PDU of the data burst and mark the End of Data burst in the GTP-U header of the last PDU in downlink. The SMF may provide the PSA UPF the End of Data Burst Marking Indication and Protocol Description used by the service data flow. The Protocol Description may be received in the PCC rule, based on information provided by the AF or by PCF local policies as described in clause 5.37.5.1. According to the request and information from the SMF, the UPF identifies the last PDU of a Data burst in the DL traffic based on the End indication according to the Protocol Description or UPF implementation and provides an End of Data Burst indication to the NG-RAN over GTP-U of the last PDU of a Data burst. NOTE: There can be some packets from the Data Burst received by NG-RAN after the PDU with End of Data Burst Indication if packets are received out of sequence. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.37.8.3 |
3,707 | 16.8 Support for Time Sensitive Communications 16.8.1 General | Time Sensitive Communications (TSC), as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3], is a communication service that supports deterministic communication and/or isochronous communication with high reliability and availability. Examples of such services are the ones in the area of Industrial Internet of Things, e.g. related to cyber-physical control applications as described in TS 22.104[ Service requirements for cyber-physical control applications in vertical domains ] [39]. To support strict synchronization accuracy requirements of TSC applications, the gNB may signal 5G system time reference information to the UE using unicast or broadcast RRC signalling with a granularity of 10 ns. Uncertainty parameter may be included in reference time information to indicate its accuracy. The UE may indicate to the gNB a preference to be provisioned with reference time information using UE Assistance Information procedure. Propagation delay compensation (PDC) mechanisms may be applied based on RTT or TA, and can be performed at the UE or gNB side. When performed at UE side, the PDC mechanisms are controlled via RRC signalling by the gNB. The RTT-based PDC mechanism is achieved by using Rx-Tx time difference measurements of a single pair of configured TRS/PRS and SRS. The following figure describes the signalling procedures of UE-side RTT-based PDC: Figure 16.8-1: Signalling Procedure of UE-side RTT-based PDC 1. The gNB provides measurement configurations to the UE; 2a/b. The gNB transmits TRS or PRS to the UE for measurements, and the UE transmits SRS to the gNB for measurement; 3a/b. Both the UE and the gNB perform Rx-Tx time difference measurements; 4. The gNB provides its Rx-Tx time difference measurement to the UE; 5. The UE performs PDC based on Rx-Tx time difference measurements from itself and the gNB. The following figure describes the signalling procedures of gNB-side RTT-based PDC: Figure 16.8-2: Signalling Procedure of gNB-side RTT-based PDC 1. The gNB provides measurement configurations to the UE; 2a/b. The gNB transmits TRS or PRS to the UE for measurements, and the UE transmits SRS to the gNB for measurement; 3a/b. Both the UE and the gNB perform Rx-Tx time difference measurements; 4. The UE reports its Rx-Tx time difference measurement to the gNB; 5. The gNB performs PDC based on Rx-Tx time difference measurements from itself and the UE. The gNB may also receive TSC Assistance Information (TSCAI), see TS 23.501[ System architecture for the 5G System (5GS) ] [3], from the Core Network, e.g. during QoS flow establishment, or from another gNB during handover. TSCAI contains additional information about the traffic flow such as burst arrival time, burst periodicity, and survival time. TSCAI knowledge may be leveraged in the gNB's scheduler to more efficiently schedule periodic, deterministic traffic flows either via Configured Grants, Semi-Persistent Scheduling or with dynamic grants, and/or to improve the associated link reliability to meet the survival time requirement (see TS 22.104[ Service requirements for cyber-physical control applications in vertical domains ] [39]). To support uplink periodic traffics of services with survival time requirement, configured grant resources can be used such that the mapping relation between the service and the configured grant is known to both gNB and UE, thus allowing the gNB to use configured grant retransmission scheduling (addressed by CS-RNTI) to trigger survival time state entry for the corresponding DRB. Upon survival time state entry, all RLC entities configured for the DRB are activated by the UE for duplication to prevent failure of subsequent messages and hence fulfilling the survival time requirement. If CA or DC duplication for the DRB is already activated, the DRB should enter survival time state when any retransmission grant for any of its active LCHs is received. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.8 |
3,708 | 5.15.20 Support of Network Slice Instance Replacement | The Network Slice Instance Replacement is used when a PDU Session for a given S-NSSAI is established using a selected Network Slice instance and the S-NSSAI corresponding to this Network Slice instance is associated with multiple Network Slice instances. In this case, the network may change the Network Slice instance for the S-NSSAI if the selected Network Slice instance is no longer available (e.g. due to overload). The AMF may subscribe with the NSSF for notifications when any of the Network Slice instances served by the AMF is congested or no longer available. In case of roaming, the NSSF of VPLMN subscribes with the NSSF of the HPLMN for notifications. When the NSSF notifies the AMF that a Network Slice instance is congested or no longer available, for some of PDU Sessions associated with the Network Slice instance that is no longer available, the AMF may delete old NSI ID corresponding to the Network Slice instance that is no longer available and the SMF of the PDU Session(s) selected by using such old NSI ID is informed by the AMF to release the PDU Session(s). Subsequently, the SMF triggers the impacted UE(s) to establish new PDU session(s) associated with the same S-NSSAI as described in clause 5.6.9.2 for PDU Session(s) of SSC Mode 2 and SSC Mode 3. The AMF selects a new Network Slice instance for the given S-NSSAI during PDU Session Establishment. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.20 |
3,709 | 5.5.1.2 S1-based handover 5.5.1.2.1 General | The S1-based handover procedure is used when the X2-based handover cannot be used. The source eNodeB initiates a handover by sending Handover Required message over the S1-MME reference point. This procedure may relocate the MME and/or the Serving GW. The source MME selects the target MME. The MME should not be relocated during inter-eNodeB handover unless the UE leaves the MME Pool Area where the UE is served. The MME (target MME for MME relocation) determines if the Serving GW needs to be relocated. If the Serving GW needs to be relocated the MME selects the target Serving GW, as specified in clause 4.3.8.2 on Serving GW selection function. The source eNodeB decides which of the EPS bearers are subject for forwarding of downlink and optionally also uplink data packets from the source eNodeB to the target eNodeB. The EPC does not change the decisions taken by the RAN node. Packet forwarding can take place either directly from the source eNodeB to the target eNodeB, or indirectly from the source eNodeB to the target eNodeB via the source and target Serving GWs (or if the Serving GW is not relocated, only the single Serving GW). The availability of a direct forwarding path is determined in the source eNodeB and indicated to the source MME. If X2 connectivity is available between the source and target eNodeBs, a direct forwarding path is available. If a direct forwarding path is not available, indirect forwarding may be used. The source MME uses the indication from the source eNodeB to determine whether to apply indirect forwarding. The source MME indicates to the target MME whether indirect forwarding should apply. Based on this indication, the target MME determines whether it applies indirect forwarding. If both source eNodeB and source MME support DAPS the source eNodeB may decide that some of the E-RABs are subject for DAPS handover as defined 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]; in this case, the source eNodeB provides the DAPS information indicating the request concerns a DAPS handover for that E-RAB as part of the Source to Target eNodeB Transparent Container. If the Target eNodeB accepts that the request concerns of DAPS handover and both Target eNodeB and Target MME support DAPS, the S1-based DAPS handover will be performed and the target eNodeB provides DAPS response information as part of the Target to Source eNodeB Transparent Container. If the MME receives a rejection to an S1 interface procedure (e.g. dedicated bearer establishment/modification/release; location reporting control; NAS message transfer; etc.) from the eNodeB with an indication that an S1 handover is in progress (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 MME shall reattempt the same S1 interface procedure when either the handover is complete or is deemed to have failed if the MME is still the serving MME, except in the case of Serving GW relocation. If the S1 handover changes the serving MME, the source MME shall terminate any other ongoing S1 interface procedures except the handover procedure. If the S1 handover includes the Serving GW relocation, and if the MME receives a rejection to a NAS message transfer for a Downlink NAS Transport or Downlink Generic NAS Transport message from the eNodeB with an indication that an S1 handover is in progress, the MME should resend the corresponding message to the target eNodeB when either the handover is complete or to the source eNodeB when the handover is deemed to have failed if the MME is still the serving MME. If the MME receives a rejection to a NAS message transfer for a CS Service Notification or to a UE Context modification Request message with a CS Fallback indication from the eNodeB with an indication that an S1 handover is in progress, the MME shall resend the corresponding message to the target eNodeB when either the handover is complete or to the source eNodeB when the handover is deemed to have failed if the MME is still the serving MME. In order to minimise the number of procedures rejected by the eNodeB, the MME should pause non-handover related S1 interface procedures (e.g. downlink NAS message transfer, E-RAB Setup/Modify/Release, etc.) while a handover is ongoing (i.e. from the time that a Handover Required has been received until either the Handover procedure has succeeded (Handover Notify) or failed (Handover Failure)) and continue them once the Handover procedure has completed if the MME is still the serving MME, except in the case of Serving GW relocation. If during the handover procedure the MME detects that the Serving GW or/and the MME needs be relocated, the MME shall reject any PDN GW initiated EPS bearer(s) request received since handover procedure started and shall include an indication that the request has been temporarily rejected due to handover procedure in progress. The rejection is forwarded by the Serving GW to the PDN GW, with the indication that the request has been temporarily rejected. Upon reception of a rejection for an EPS bearer(s) PDN GW initiated procedure with an indication that the request has been temporarily rejected due to handover procedure in progress, the PDN GW start a locally configured guard timer. The PDN GW shall re-attempt, up to a pre-configured number of times, when either it detects that the handover is completed or has failed using message reception or at expiry of the guard timer. If emergency bearer services are ongoing for the UE, handover to the target eNodeB is performed independent of the Handover Restriction List. The MME checks, as part of the Tracking Area Update in the execution phase, if the handover is to a restricted area and if so MME releases the non-emergency bearers as specified in clause 5.10.3. If emergency bearer services are ongoing for the UE, handover to the target CSG cell is performed independent of the UE's CSG subscription. If the handover is to a CSG cell that the UE is not subscribed, the target eNodeB only accepts the emergency bearers and the target MME releases the non-emergency PDN connections that were not accepted by the target eNodeB as specified in clause 5.10.3. For inter-PLMN handover to a CSG cell, if the source MME has the CSG-ID list of the target PLMN, the source MME shall use it to validate the CSG membership of the UE in the target CSG cell. Otherwise, based on operator's configuration the source MME may allow the handover by validating the CSG membership of the UE in the target CSG cell using the CSG-ID list of the registered PLMN-ID. If neither the CSG-ID list of the target PLMN nor the operator's configuration permits the handover, the source MME shall reject the handover due to no CSG membership information of the target PLMN-ID. As specified in clause 4.3.8.3, with regard to CIoT EPS Optimisations, the source MME attempts to perform handover to a target MME that can support the UE's Preferred Network Behaviour. For a UE that is using a Non-IP connection to a PDN Gateway, or a PDN connection to a SCEF, if these bearers cannot be supported by the target MME, the source MME does not attempt to handover those bearers, but instead releases them upon successful completion of the handover. If the MME does not have any bearer for the UE that can be transferred, then the MME sends an S1-AP Handover Preparation Failure message to the source eNodeB. For PDN connection of Ethernet Type, if the target MME does not support Ethernet PDN Type, the source MME does not attempt to handover those bearers, but instead releases them upon successful completion of the handover. NOTE 1: Inter-PLMN handover to a CSG cell in a PLMN which is not an equivalent PLMN for the UE is not supported. For handover the following applies related to handling of radio capabilities: - If the source eNodeB and target eNodeB support RACS as defined in clause 5.11.3a, the Source to Target transparent container need not carry the UE radio capabilities (instead the UE Radio Capability ID is supplied from the CN to the target eNodeB). However, if the source eNodeB has knowledge that the target eNodeB might not have a local copy of the Radio Capability corresponding to the UE Radio Capability ID (i.e. because the source eNodeB had itself to retrieve the UE's Radio Capability from the MME) then the source eNodeB may send some (or all) of the UE's Radio Capability to the target eNodeB (the size limit based on local configuration. In the case of inter-PLMN handover, when the source and target eNodeB support RACS as defined in clause 5.11.3a and the source eNodeB determines based on local configuration that the target PLMN does not support the UE Radio Capability ID assigned by the source PLMN, then the source eNodeB shall include the UE radio capabilities in the Source to Target transparent container. At such an inter-PLMN handover, the source CN node shall not provide the UE Radio Capability ID to the target CN node (or in intra-CN node case not to the target eNodeB). If the target eNodeB does not have a mapping between the UE Radio Capability ID received from the MME and the UE radio capabilities and no UE radio capability is provided in the Source to Target transparent container, it shall use the procedure described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36] to retrieve the mapping from the Core Network. If the target eNodeB received both the UE radio capabilities (in the Source to Target transparent container) and the UE Radio Capability ID (from the MME), then the target eNodeB shall use any locally stored UE radio capability information corresponding to the UE Radio Capability ID. If none are stored locally, the target eNodeB may request the full UE radio capability information from the core network. If the full UE radio capability information is not promptly received from the core network, or the target eNodeB chooses not to request it, then the target eNodeB shall proceed with the UE radio capabilities sent by the source RAN node. The target eNodeB shall not use the UE radio capability information received from the source RAN node for any other UE with the same UE Radio Capability ID. - If the target eNodeB knows (e.g. by configuration) that the UE's E-UTRA radio capabilities applicable to the target eNB may be different to the E-UTRA radio capabilities stored in the source eNodeB (e.g. for handover to/from an E-UTRA eNodeB that supports the NTN enhancements as defined 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]), then the target eNodeB shall trigger retrieval of the radio capability information again from the UE. NOTE 2: In order to support handover from an E-UTRA eNodeB that supports the NTN enhancements as defined 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] the target eNodeB needs to be upgraded to support the above behaviour. The Inter eNodeB S1 based handover procedure specified in clause 5.5.1.2.2 may also be used for intra-eNodeB handover. NOTE 3: One use case for intra-eNodeB handover to be performed by the Inter eNodeB S1 based handover procedure is when an eNodeB serves a satellite access system that covers more than one country. In such a situation, the UE might move from a "cell" in one country into a "cell" in another country, and the eNodeB may need to cause the MME to change to an MME serving the UE's new country. | 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.1.2 |
3,710 | 8.5.5 Session management | a) If the message is a DEACTIVATE PDP CONTEXT REQUEST, a DEACTIVATE PDP CONTEXT ACCEPT message shall be returned. All resources allocated for that context shall be released. b) If the message is a REQUEST PDP CONTEXT ACTIVATION, a REQUEST PDP CONTEXT ACTIVATION REJECT message with cause # 96 "Invalid mandatory information" shall be returned. c) If the message is an ACTIVATE PDP CONTEXT REQUEST, an ACTIVATE PDP CONTEXT REJECT message with cause # 96 "Invalid mandatory information" shall be returned. d) If the message is an ACTIVATE SECONDARY PDP CONTEXT REQUEST, an ACTIVATE SECONDARY PDP CONTEXT REJECT message with cause # 96 "Invalid mandatory information" shall be returned. e) If the message is a MODIFY PDP CONTEXT REQUEST, a MODIFY PDP CONTEXT REJECT message with cause # 96 "Invalid mandatory information" shall be returned. f) If the message is a REQUEST MBMS CONTEXT ACTIVATION, a REQUEST MBMS CONTEXT ACTIVATION REJECT message with cause # 96 "Invalid mandatory information" shall be returned. g) If the message is an ACTIVATE MBMS CONTEXT REQUEST, an ACTIVATE MBMS CONTEXT REJECT message with cause # 96 "Invalid mandatory information" shall be returned. h) If the message is a REQUEST SECONDARY PDP CONTEXT ACTIVATION, a REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message with cause # 96 "Invalid mandatory information" shall be returned. | 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.5.5 |
3,711 | 6.11B.2 Mapping to resource elements | The same antenna port shall be used for all symbols of the MWUS within a subframe. The UE shall not assume that the MWUS is transmitted on the same antenna port as any of the downlink reference signals or synchronization signals. If only one CRS port is configured by the eNB, the UE may assume the transmission of all MWUS subframes is using the same antenna port; otherwise, the UE may assume the same antenna port is used for MWUS transmission in downlink subframes w0 + 2n and w0 + 2n + 1, where w0 is the first downlink subframe of the MWUS transmission as specified in [4], and n=0, 1,…. The MWUS bandwidth is 2 consecutive PRBs, the frequency location of the lowermost PRB with is signaled by higher layers. For both PRB pairs in the frequency domain, for which MWUS is defined, the MWUS sequence shall be mapped to resource elements in sequence, starting with in increasing order of first the index , over the 12 assigned subcarriers and then the index in each subframe in which MWUS is transmitted. The MWUS sequence is mapped to the set of subframes in the actual MWUS duration as defined in [4], where in a subframe in which an MWUS PRB pair overlaps with any PRB pair carrying PSS, SSS, RSS, PBCH or PDSCH associated with SI-RNTI is transmitted, the subframe is counted in the MWUS mapping but not used for transmission of MWUS. In frame structure type 2, those special subframes, indicated as BL/CE DL subframes by higher layer fdd-DownlinkOrTddSubframeBitmapBR, are not counted in MWUS mapping and are not used for transmission of MWUS. A resource element overlapping with resource elements where cell-specific reference signals according to clause 6.10 are transmitted shall not be used for MWUS transmission but is counted in the mapping process. | 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.11B.2 |
3,712 | 5.2.2 Charging data transfer in online charging | In online charging, charging events mirroring the resource usage request of the user are transferred from the CTF to the OCF via the Ro reference point. The CTF determines whether the request corresponds to an user / network event (event based charging, e.g. MMS) or whether a session shall be started (session based charging, e.g. IP CAN bearer). Generally, this property is built into the network capability, or service, that the NE provides, and described in the middle tier TSs. Note that TS 23.078[ Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 ] [207] also specifies online charging capability in the SGSN and MSC based on CAMEL, i.e. using the CAP reference point towards the OCS. This functionality is outside the scope of the present document. In event based charging, a network / user event (e.g. MM submission) corresponds to a single chargeable event. In session based charging, at least two chargeable events are needed, one each to describe the start and the end of the session, respectively. Multiple interim events are possible in order to describe changes of session characteristics (e.g. change of IP CAN bearer QoS or change of IMS session media types), or when certain limits, e.g. time or volume, are exceeded. The CTF transforms each chargeable event into a charging event and forwards these charging events to the OCF in real-time. For event based charging, the Credit-Control procedure in the OCS may or may not involve reservation of units from the subscriber account, as described in clause 5.1. In the case of event based charging without reservation (IEC): - The CTF forwards the charging event to the OCS; - The OCS determines the value of the requested resource usage and debits this value from the subscriber account; - The OCS returns the resource usage authorisation to the network element; - The network element executes the resource usage according to the user request and the OCS authorisation. The following exceptions and abnormal cases are defined for the IEC scenario: 1) The OCS rejects the resource usage request. In this case, the NE disallows the resource usage. 2) Subsequent to resource usage authorisation and execution of the resource usage, the resource usage fails and the CTF may return the failure to the OCS to initiate a refund for the original resource usage. NOTE 1: The triggering of the refund action is implementation and service dependent. If the Credit-Control procedure does involve reservation (ECUR): - The CTF forwards the charging event to the OCS; - The OCS determines the value of the requested resource usage and reserves this value from the subscriber account; - The OCS returns the resource usage authorisation to the network element; - The network element executes the resource usage according to the user request and the OCS authorisation. - After completion (or failure) of the resource usage, the NE informs the OCS accordingly about the completion or failure; - In line with the result report from the network element, the OCS either debits the reserved amount from the subscriber account (success), or it returns the reserved amount back to the subscriber account (failure). The following exceptions and abnormal cases are defined for the ECUR scenario: 1) The OCS rejects the resource usage request. In this case, the NE disallows the resource usage. 2) The resource usage execution fails, e.g. due to network failure or user abort. In this case, the network element informs the OCS of the failure, and the previously reserved amounts are returned onto the subscriber account. NOTE 2: Returning previously reserved amounts of units to the user’s account is up to operator policy in the OCS. The authorization of multiple chargeable events as per the "event based charging" description in clause 5.1 is not yet covered in the above scenario. Session based online charging always involves reservation within the Credit-Control procedure (SCUR), as there is no way for the OCS to predict the amount of resource usage that occurs during the user session. To begin with, the CTF forward generates a charging chargeable event that corresponds to the resource usage request and maps onto the user session, and forwards it to the OCF. In the OCS, the online charging session is started and a certain amount reserved from the user subscriber account. This amount is determined by the OCS based on the information in the charging event and on local configuration, i.e. operator policy. A resource usage quota, matching the reserved amount, is then returned by the OCS, at which point the user session starts in the NE. Further charging events are sent from the NE to the OCS upon the detection of further chargeable events within the session .e.g. the expiry of in intervals configured on the NE or instructed by the OCS, or when the authorised quota expires, or when session characteristics change (e.g. change of QoS of an IP CAN bearer). The OCS then furnishes a new quota to the NE as required, or rejects the charging event, e.g. due to expiry of credit on the subscriber account. The OCS also furnishes the NE’s behaviour on quota expiry (termination action). When the user session terminates normally in the NE, a final statement on the actually used network resources is returned to the OCS, enabling the OCS to calculate the final value of the actual resource usage session and to properly debit the corresponding final amount from the subscriber account (possibly resulting in a re-crediting of previously reserved amounts). This also terminates the Credit-Control session for the particular user session. The following exceptions and abnormal cases are defined for the SCUR scenario: 1) For optimisation purposes, the network element may allow the user session to start prior to receiving the initial authorisation from the OCS, i.e. prior to the start of the Credit-Control session. 2) The OCS rejects the initial resource usage request at session start, i.e. no Credit-Control session is started. In this case, the NE disallows the start of the session or, if the session was already allowed to start as described in item 1 above, enforces the termination of the user session. 3) The OCS rejects the resource usage request in mid-session. In this case, the NE’s behaviour conforms to the instruction returned by the OCS, e.g.: - terminate the user session; - limit the characteristics of the user session, e.g. allow only Web/WAP pages that are free of charge; - direct the session to a special notification site or an account recharging server 4) The OCS may send unsolicited termination commands with the same effect as described in item 3 above. 5) Unexpected termination of user session, e.g. due to network failure or due to user abort. In this case, the behaviour of the network is as specified above for session termination, but all available information of the failure is returned to the OCS in the final statement. Further action of the OCS in regard of calculating the session value and debiting or crediting the user’s account depends on the exact circumstances and operator policy. In any of the above cases, the termination of the user session coincides with the termination of the Credit-Control session, e.g. even when a user session is allowed to continue upon account expiry, the Credit-Control session will also continue, but "zero" rated. NOTE 3: the intention of the above clause is not to enforce closing the user session when the Credit-Control session breaks down. It is important for operators to carefully consider the reservation policy on the OCS. On the one hand, if small amounts are reserved, the NE must renew the authorisation very frequently, creating high signalling and processing loads. Additionally, this policy has a comparatively high likelihood of longer, or higher-value, user sessions being forcefully terminated due to expiry of the subscriber account after many small quotas have been used for small chunks of the subscriber session. In contrast, assigning high reservations avoids the above problems, but may interdict the user from the execution of additional, parallel resource usages: due to the high previous reservation, there is no credit left on the account for another resource usage request. The situation described in this paragraph is particularly complex when correlation between multiple charging levels is necessary, see clause 5.3.4. A potential method of relieving this problem is the pooling of credit quotas as described in clause 5.5.2 below. The middle tier TSs specify the chargeable events and the content of the associated charging events and responses. TS 32.299[ Telecommunication management; Charging management; Diameter charging applications ] [50] specifies the interface application for the Ro reference point, including the message types and the domain / subsystem / service independent contents of the messages. In addition to the Credit-Control functions, the OCS may also be capable of producing CDRs based on the execution of the above Credit-Control procedures. To this end, the OCS must implement a CDF, and it uses the Ga and Bo reference points to forward its CDRs to a CGF and the CDR files to the BD. These functions of the OCS, however, are outside the scope of 3GPP standardisation. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.2.2 |
3,713 | 6.15.2 Requirements | The 5G access network shall support an energy saving mode with the following characteristics: - the energy saving mode can be activated/deactivated either manually or automatically; - service can be restricted to a group of users (e.g. public safety user, emergency callers). NOTE: When in energy saving mode the UE's and Access transmit power may be reduced or turned off (deep sleep mode), end-to-end latency and jitter may be increased with no impact on set of users or applications still allowed. The 5G system shall support mechanisms to improve battery life for a UE over what is possible in EPS. The 5G system shall optimize the battery consumption of a relay UE via which a UE is in indirect network connection mode. The 5G system shall support UEs using small rechargeable and single coin cell batteries (e.g. considering impact on maximum pulse and continuous current). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.15.2 |
3,714 | 6.5.2D.1 Error Vector Magnitude | For ProSe sidelink physical channels PSDCH, PSCCH, PSSCH, and PSBCH, the Error Vector Magnitude requirements shall be as specified for PUSCH in subclause 6.5.2.1 for the corresponding modulation and transmission bandwidth. When ProSe transmissions are shortened due to transmission gap of 1 symbol at the end of the subframe, the EVM measurement interval is reduced by one symbol, accordingly. For PSBCH the duration over which EVM is averaged shall be 24 subframes. This requirement is not applicable for ProSe physical signals PSSS and SSSS. | 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.5.2D.1 |
3,715 | 10.5.7.8 Device properties | The purpose of the Device properties information element is to indicate if the MS is configured for NAS signalling low priority. The network uses the Device properties information element for core-network congestion handling and for charging purposes. The Device properties information element is coded as shown in figure 10.5.7.8.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.7.8.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Device properties is a type 1 information element. Figure 10.5.7.8.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Device properties information element Table 10.5.7.8.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Device properties 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.7.8 |
3,716 | 8.5.1.2.5 Enhanced Downlink Control Channel Performance Requirement Type A - 2 Tx Antenna Ports under Asynchronous Network | For the parameters specified in Table 8.5.1-1 and Table 8.5.1.2.5-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.1.2.5-2. The purpose of this test is to verify the PHICH performance with 2 transmit antennas when the serving cell PHICH transmission is interfered by two interfering cells and applying interference model defined in clause B.5.2. In Table 8.5.1.2.5-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the agressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is not provided. Table 8.5.1.2.5-1: Test Parameters for PHICH Table 8.5.1.2.5-2: Minimum performance PHICH for Enhanced Downlink Control Channel Performance Requirement Type A | 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.5.1.2.5 |
3,717 | .1 Delete Bearer Command | A Delete Bearer Command message shall be sent on the S11 interface by the MME to the SGW and on the S5/S8 interface by the SGW to the PGW as a part of the eNodeB requested bearer release or MME-Initiated Dedicated Bearer Deactivation procedure. The message shall also be sent on the S4 interface by the SGSN to the SGW and on the S5/S8 interface by the SGW to the PGW as part of the MS and SGSN Initiated Bearer Deactivation procedure using S4. Table .1-1: Information Elements in Delete Bearer Command Table .1-2: Bearer Context within Delete Bearer Command Table 7.2.17.1-3: Overload Control Information within Delete Bearer Command | 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 | .1 |
3,718 | 6.9.4.4 AS key re-keying | The KgNB/KeNB re-keying procedure is initiated by the AMF. It may be used under the following conditions: - after a successful AKA run with the UE as part of activating a partial native 5G security context; or - as part of synchronizing the NAS and the AS security contexts as a part of handover procedure, if a handover is occuring; or - as part of re-activating a non-current full native 5G security context after handover from E-UTRAN according to clause 8.4; or - to create a new KgNB from the current KAMF. NOTE 1: To perform a key change on-the-fly of the entire key hierarchy, the AMF has to change the 5G NAS security context before changing the 5G AS security context. In order to be able to re-key the KgNB, the AMF requires a fresh uplink NAS COUNT from a successful NAS SMC procedure with the UE. In the case of creating a new KgNB from the current KAMF a NAS SMC procedure shall be run first to provide this fresh uplink NAS COUNT. This NAS SMC procedure does not have to change other parameters in the current EPS NAS security context. The AMF derives the new KgNB using the key derivation function as specified in Annex A.9 using the KAMF and the uplink NAS COUNT used in the most recent NAS Security Mode Complete message. The derived new KgNB is sent to the gNB/ng-eNB in an NGAP UE CONTEXT MODIFICATION REQUEST message triggering the gNB/ng-eNB to perform the AS key re-keying. The gNB/ng-eNB runs the key change on-the-fly procedure with the UE. During this procedure the gNB/ng-eNB shall indicate to the UE that a key change on-the-fly is taking place. The procedure used is based on an intra-cell handover, and hence the same KgNB derivation steps shall be taken as in a normal handover procedure. The gNB/ng-eNB shall indicate to the UE to change the current KgNB in intra-cell handover during this procedure. Network-side handling of AS key re-keying that occur as a part of Xn and N2 handovers are described is defined in clauses 6.9.2.3.2 and 6.9.2.3.3 of the present document. When the UE receives an indication that the procedure is a key change on-the-fly procedure, the UE shall derive a temporary KgNB by applying the key derivation function as specified in Annex A.9 using the KAMF from the current 5G NAS security context and the uplink NAS COUNT in the most recent NAS Security Mode Complete message. UE-side handling of AS key re-keying that occur as a part of Xn and N2 handovers is described in clause 6.9.2.3.4 of the present document. From this temporary KgNB the UE shall derive the KNG-RAN* as normal (see Annex A.11/A.12). The gNB/ng-eNB shall take the KgNB it received from the AMF, which is equal to the temporary KgNB, as basis for its KNG-RAN* derivations. From this step onwards, the key derivations continue as in a normal handover. If the AS level re-keying fails, then the AMF shall complete another NAS security mode procedure before initiating a new AS level re-keying. This ensures that a fresh KgNB is used. The NH parameter shall be handled according to the following rules: - The UE, AMF, and gNB/ng-eNB shall delete any old NH upon completion of the context modification. - The UE and AMF shall use the KAMF from the currently active 5G NAS security context for the computation of the fresh NH. The computation of NH parameter value sent in the Namf_Communication_CreateUEContext Request, NGAP HANDOVER REQUEST, and NGAP PATH SWITCH REQUEST ACKNOWLEDGE messages shall be done according to clauses 6.9.2.3.2 and 6.9.2.3.3. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.4.4 |
3,719 | 6.8.8.1 UMTS security context | A UMTS security context is only established for UMTS subscribers. At the network side, two cases are distinguished: a) In case of a PS intra SGSN Handover, the SGSN derives the 64-bit GSM cipher key Kc from the UMTS cipher/integrity keys CK and IK agreed during the latest UMTS AKA procedure (using the conversion function c3) and applies it if the selected GEA ciphering algorithm requires a 64-bit key. If the selected GEA ciphering algorithm requires a 128-bit key, the SGSN shall apply the 128-bit GSM cipher key Kc128 derived from the CK and IK agreed during the latest UMTS AKA. b) In case of a PS inter SGSN handover, the initial SGSN sends the UMTS cipher/integrity keys CK and IK agreed during the latest UMTS AKA procedure to the new SGSN. The new SGSN stores the keys, derives the 64-bit GSM cipher key Kc and applies the latter if the selected GEA ciphering algorithm requires a 64-bit key. If the selected GEA ciphering algorithm requires a 128-bit key, the SGSN shall apply the 128-bit GSM cipher key Kc128 derived from the CK and IK agreed during the latest UMTS AKA. The new SGSN becomes the new anchor point for the service. At the user side, in all cases, the ME applies the derived GSM cipher key Kc received from the USIM during the latest UMTS AKA procedure if the selected GEA ciphering algorithm requires a 64-bit key. If the selected GEA ciphering algorithm requires a 128-bit key, the ME shall apply the derived 128-bit GSM cipher key Kc128 from the key set agreed during the latest UMTS AKA. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.8.1 |
3,720 | H.1.4a Cause No. 13 "call completed elsewhere" | This cause indicates that the call is being cleared by the network towards the present device because the called user has responded to the call on another device. This cause only applies when the MSC/VLR is an MSC server enhanced for ICS as specified in 3GPP TS 24.292[ IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3 ] [163] and performs interworking with SIP as specified in 3GPP TS 29.292[ Interworking between the IP Multimedia (IM) Core Network (CN) subsystem (IMS) and MSC Server for IMS Centralized Services (ICS) ] [164]. | 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 | H.1.4a |
3,721 | 6.2.21 UE radio Capability Management Function (UCMF) | The UCMF is used for storage of dictionary entries corresponding to either PLMN-assigned or Manufacturer-assigned UE Radio Capability IDs. An AMF may subscribe with the UCMF to obtain from the UCMF new values of UE Radio Capability ID that the UCMF assigns for the purpose of caching them locally. Provisioning of Manufacturer-assigned UE Radio Capability ID entries in the UCMF is performed from an AF that interacts with the UCMF either directly or via the NEF (or via Network Management) using a procedure defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. A UCMF that serves both EPS and 5GS shall require provisioning the UE Radio Capability ID with the TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51] format or TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] format or both the formats of the UE radio capabilities. The UCMF also assigns the PLMN-assigned UE Radio Capability ID values. Each PLMN-assigned UE Radio Capability ID is also associated to the TAC of the UE model(s) that it is related to. When an AMF requests the UCMF to assign a UE Radio Capability ID for a set of UE radio capabilities, it indicates the TAC of the UE that the UE Radio Capability information is related to. The UCMF stores a Version ID value for the PLMN assigned UE Radio Capability IDs so it is included in the PLMN assigned UE Radio Capability IDs it assigns. This shall be configured in the UCMF. The UCMF may be provisioned with a dictionary of Manufacturer-assigned UE Radio Capability IDs which include a "Vendor ID" that applies to the Manufacturers of these UE, and a list of TACs for which the PLMN has obtained-Manufacturer-assigned UE Radio Capability IDs. A PLMN-assigned UE Radio Capability IDs is kept in the UCMF storage as long as it is associated with at least a TAC value. When a TAC value is related to a UE model that is earmarked for operation based on Manufacturer assigned UE Radio Capability IDs, this TAC value is disassociated in the UCMF from any PLMN assigned UE Radio Capability IDs. For the case that the PLMN is configured to store PLMN assigned IDs in the Manufacturer Assigned operation requested list defined in clause 4.4.1a, the UCMF does not remove from storage any PLMN assigned UE Radio Capability ID no longer used, and rather quarantines it to avoid any future reassignment. A UCMF dictionary entry shall include also the related UE Radio Capability for Paging for each RAT. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.21 |
3,722 | 4.3.27.1 Paging for Enhanced Coverage | Support of UEs in Enhanced Coverage is specified 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]. Whenever S1 is released and Information for Enhanced Coverage is available for the UE, the eNodeB sends it to the MME as described in clause 5.3.5. The MME stores the received Information for Enhanced Coverage and includes it in every subsequent Paging message for all eNodeBs selected by the MME for paging. If Enhanced Coverage is restricted for the UE as described in clause 4.3.28, the MME sends the Enhanced Coverage Restricted parameter as defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. | 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.27.1 |
3,723 | 5.4.4.1.1 Clearing when tones/announcements provided | When in-band tones/announcements are provided (see subclause 5.5.1), the call control entity of the network may initiate clearing by sending a DISCONNECT message containing progress indicator #8 "in-band information or appropriate pattern now available", starting timer T306, and entering the "disconnect indication" state. 5.4.4.1.1.1 Receipt of a DISCONNECT message with progress indicator #8 from the network The call control entity of the MS in any state except the "null" state, the "disconnect indication" state, and the "release request" state, shall, upon receipt of a DISCONNECT message with progress indicator #8: i) if an appropriate speech traffic channel is not connected, continue clearing as defined in subclause 5.4.4.1.2.1 without connecting to the in-band tone/announcement; ii) if an appropriate speech traffic channel is connected, attach the user connection for speech if it is not yet attached and enter the "disconnect indication" state. In that state, if upper layers request the clearing of the call, the call control entity of the MS shall proceed as defined in subclause 5.4.4.1.2.1. 5.4.4.1.1.2 Expiry of timer T306 The call control entity of the network, having entered the "disconnect indication" state after sending a disconnect message with the progress indicator #8, shall, upon expiry of timer T306, continue clearing by sending a RELEASE message with the cause number originally contained in the DISCONNECT message; starting timer T308; and entering the "release request" state. | 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.4.4.1.1 |
3,724 | 4.4.8.4 Architecture to support IETF Deterministic Networking | The 5G System is integrated with the Deterministic Network as defined in IETF RFC 8655 [150] as a logical DetNet transit router, see Figure 4.4.8.4-1. The TSCTSF performs mapping in the control plane between the 5GS internal functions and the DetNet controller. 5G System specific procedures in 5GC and RAN remain hidden from the DetNet controller. Figure 4.4.8.4-1: 5GS Architecture to support IETF Deterministic Networking On the device side, the UE is connected with a DetNet system, which may be a DetNet End System or a DetNet Node. The architecture does not require the DS-TT functionality to be supported in the device nor require the user plane NW-TT functionality to be supported in the UPF, however, it can co-exist with such functions. For the reporting of information of the network side ports, NW-TT control plane function is used. The architecture can be combined with architecture in clause 4.4.8.3 to support time synchronization and TSC. DetNet may be used in combination with time synchronization mechanisms as defined in clause 5.27, but it does not require usage of these mechanisms. 5GS acts as a DetNet router in the DetNet domain. Use cases where the 5GS acts as a sub-network (see clause 4.1.2 of IETF RFC 8655 [150]) are also possible but do not require any additional 3GPP standardization. A special case where the 5GS can act as a sub-network is when the 5GS acts as a TSN network, which is supported by the 3GPP specifications based on the architecture in clause 4.4.8.2. NOTE: For DetNet interworking, it is assumed that there is a business agreement to support the use of the DetNet controller so that it can be regarded trusted for the operator. Depending on the needs of a given deployment, functions such as the authentication, authorization and potential throttling of signalling from the DetNet controller can be achieved by including such functionalities in the TSCTSF. The routing of the downlink packets is achieved using the existing 3GPP functions. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.8.4 |
3,725 | 4.11.4.1 Handover from EPC/ePDG to 5GS | Figure 4.11.4.1-1: Handover from EPC/ePDG to 5GS 0. Initial status: one or more PDN Connections have been established between the UE and the EPC/ePDG via untrusted non-3GPP access as specified in clauses 7.2.4 and 7.6.3 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] with modification described in clauses 4.11.4.3.3 and 4.11.4.3.5. 1. For the UE to move its PDU session(s) from EPC/ePDG to 5GC/3GPP access, the UE's behaviour is as follows: - If the UE is operating in single-registration mode (as described in clause 5.17.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and the UE is attached to EPC/E-UTRAN: - the UE behaves as specified in clause 4.11.1 or clause 4.11.2 and gets registered to 5GC via 3GPP access. - otherwise i.e. either the UE is operating in single registration mode and is not attached to EPC/E-UTRAN, or the UE is operating in dual registration mode; and - if the UE is already registered in 5GS via 3GPP access, the UE skips to step 2. - otherwise (i.e UE is not registered in 5GS via 3GPP access), the UE performs Registration procedure of type initial registration in 5GS via 3GPP access as described in clause 4.2.2.2. 2. The UE initiates a UE requested PDU Session Establishment via 3GPP Access acording to clause 4.3.2.2 and includes the "Existing PDU Session" indication or "Existing Emergency PDU Session" and the PDU Session ID. For Request Type "Existing PDU Session", the UE provides a DNN, the PDU Session ID and S-NSSAI corresponding to the existing PDN connection it wants to transfer from EPC/ePDG to 5GS. The S-NSSAI and PLMN ID sent to the UE are set in the same way as for EPS to 5GS mobility as specified in clause 5.15.7.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the Request Type indicates "Existing Emergency PDU Session", the AMF shall use the Emergency Information containing SMF+PGW-C FQDN for the S2b interface it has received from the HSS+UDM. The SMF+PGW-C FQDN was sent by PGW-C when the Emergency PDN connection was established in EPC via ePDG and the AMF shall use the S-NSSAI locally configured in Emergency Configuration Data. 3. The combined PGW+SMF/UPF initiates a PDN GW initiated Resource Allocation Deactivation with GTP on S2b as described in clause 7.9.2 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] to release the EPC and ePDG resources when S6b is used. When S6b is not used between SMF+PGW-C and AAA, impacts to step 5 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] Figure 7.9.2-1 are captured in clause 4.11.4.3.6. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.4.1 |
3,726 | 4.11.5.4 UE or Network Requested PDU Session Modification procedure | For PDU Session via 3GPP, the following impacts are applicable to clause 4.3.3.2 (UE or network requested PDU Session Modification (non-roaming and roaming with local breakout)) to support interworking with EPS: - Step 1: In addition to the triggers listed in step 1 of clause 4.3.3.2, the procedure may be also triggered by the following event: - AMF initiated modification: If the support of EPS Interworking for this PDU Session has changed, e.g. the change of the UE's subscription data (e.g. Core Network Type Restriction to EPS), or change of 5GMM capability (e.g. "S1 mode supported"), the AMF invokes Nsmf_PDUSession_UpdateSMContext update the status of EPS interworking support in the to SMF. - Step 3a: This step also applies to AMF initiated modification. For AMF initiated modification, the SMF may determines whether the PDU session supports EPS interworking need be changed. If it need be changed, the SMF invokes Nudm_UECM_Update service operation to add or remove the PGW-C FQDN for S5/S8 interface from the UE context in SMF data stored at the UDM, For PDU Session via 3GPP, the following impacts are applicable to clause 4.3.3.3 (UE or network requested PDU Session Modification (home-routed roaming)) to support interworking with EPS: - Step 1a (AMF to V-SMF): Same impact as for step 1 of clause 4.3.3.2 above. - Step 1a (V-SMF to H-SMF): The V-SMF pass the status of EPS interworking support to the H-SMF. - Step 1a (H-SMF to V-SMF): Same impact as for clause 3a of 4.3.3.2 above. For interworking with the N26 interface, if status of interworking with EPS for a PDU session is changed at SMF+PGW-C, the SMF+PGW-C invokes EBI allocation or revocation as described in clause 4.11.1.4.1 and clause 4.11.1.4.2 respectively. For PDU Session via non-3GPP access, the AMF determines if EPS interworking is supported and sends the indication to the SMF in the same way as for PDU Session via 3GPP access. The SMF makes the final decision on the EPS interworking in the same way as for PDU Session via 3GPP access with the following modification: If the SMF does not receive the interworking indication, the SMF makes its decision based on subscription. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.5.4 |
3,727 | 4.22.6.2.4 EPS bearer ID revocation | Based on the clause 4.11.1.4.3, additionally the following procedures are updated to revoke the EPS bearer ID(s) assigned to the QoS Flow(s) in the MA PDU Session: - UE or network requested MA PDU Session Release (non-roaming and roaming with local breakout) in clause 4.22.10.2. - UE or network requested MA PDU Session Release (home-routed roaming) in clause 4.22.10.3. - UE or network requested MA PDU Session Modification (non-roaming and roaming with local breakout) in clause 4.22.8.2. - UE or network requested MA PDU Session Modification (home-routed roaming) in clause 4.22.8.3. - When the MA PDU Session is released over 3GPP access, the UE and the SMF locally release the EBI(s) for the MA PDU Session. The SMF notifies the AMF of the released EBI(s) by sending Nsmf_PDUSession_SMContextStatusNotify service operation if the MA PDU Session is established in the same PLMN. If the MA PDU Session is established in different PLMNs, the SMF notifies the release of the MA PDU Session and as a result, the AMF removes associated EBI(s). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.6.2.4 |
3,728 | 4.1.2.1 Attempted RRC connection re-establishments | a) This measurement provides the number of RRC connection re-establishment attempts for each re-establishment cause. b) CC. c) Receipt of an RRCConnectionReestablishmentRequest message by the eNodeB/RN from the UE. Each RRCConnectionReestablishmentRequest received is added to the relevant per reestablishment cause measurement. The possible causes are included in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. The sum of all supported per cause measurements shall equal the total number of RRC connection re-stablishment attempts. 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 RRC.ConnReEstabAtt.Cause where Cause identifies the reestablishment cause. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switching. h) 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.1.2.1 |
3,729 | 9.7.2.2 TDD | For the parameters specified in Table 9.7.2.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.7.2.2-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least % of the time but less than % for each sub-band; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.05. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each available downlink transmission instance for TDD. Table 9.7.2.2-1 Sub-band test for single antenna transmission (TDD) Table 9.7.2.2-2 Minimum requirement (TDD) | 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 | 9.7.2.2 |
3,730 | 2.2B Subscription Concealed Identifier (SUCI) | The SUCI is a privacy preserving identifier containing the concealed SUPI. It is defined in clause 6.12.2 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [124]. Figure 2.2B-1: Structure of SUCI The SUCI is composed of the following parts: 1) SUPI Type, consisting in a value in the range 0 to 7. It identifies the type of the SUPI concealed in the SUCI. The following values are defined: - 0: IMSI - 1: Network Specific Identifier (NSI) - 2: Global Line Identifier (GLI) - 3: Global Cable Identifier (GCI) - 4 to 7: spare values for future use. 2) Home Network Identifier, identifying the home network of the subscriber. When the SUPI Type is an IMSI, the Home Network Identifier is composed of two parts: - Mobile Country Code (MCC), consisting of three decimal digits. The MCC identifies uniquely the country of domicile of the mobile subscription; - Mobile Network Code (MNC), consisting of two or three decimal digits. The MNC identifies the home PLMN or SNPN of the mobile subscription. When the SUPI type is a Network Specific Identifier (NSI), a GLI or a GCI, the Home Network Identifier consists of a string of characters with a variable length representing a domain name as specified in clause 2.2 of IETF RFC 7542 [126]. For a GLI or a GCI, the domain name shall correspond to the realm part specified in the NAI format for SUPI in clauses 28.15.2 and 28.16.2. 3) Routing Indicator, consisting of 1 to 4 decimal digits assigned by the home network operator and provisioned in the USIM, that allow together with the Home Network Identifier to route network signalling with SUCI to AUSF and UDM instances capable to serve the subscriber. Each decimal digit present in the Routing Indicator shall be regarded as meaningful (e.g. value "012" is not the same as value "12"). If no Routing Indicator is configured on the USIM or the ME, this data field shall be set to the value 0 (i.e. only consist of one decimal digit of "0"). 4) Protection Scheme Identifier, consisting in a value in the range of 0 to 15 (see Annex C.1 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [124]). It represents the null scheme or a non-null scheme specified in Annex C of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [124] or a protection scheme specified by the HPLMN; the null scheme shall be used if the SUPI type is a GLI or GCI. 5) Home Network Public Key Identifier, consisting in a value in the range 0 to 255. It represents a public key provisioned by the HPLMN or SNPN and it is used to identify the key used for SUPI protection. This data field shall be set to the value 0 if and only if null protection scheme is used; 6) Scheme Output, consisting of a string of characters with a variable length or hexadecimal digits, dependent on the used protection scheme, as defined below. It represents the output of a public key protection scheme specified in Annex C of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [124] or the output of a protection scheme specified by the HPLMN. Figure 2.2B-2 defines the scheme output for the null protection scheme. Figure 2.2B-2: Scheme Output for the null protection scheme The Mobile Subscriber Identification Number ("MSIN") is defined in clause 2.2; the "username" corresponds to the username part of a NAI, and it is applicable to SUPI types Network-Specific Identifier (clause 28.7.2), GLI (clause 28.16.2) or GCI (clause 28.15.2). NOTE 1: For a SUCI with SUPI Type 2 or 3 (i.e. GLI or GCI), the SUCI can, based on subscription information, act as a pseudonym of the actual SUPI containing an IMSI (see 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [131], clauses 4.7.3 and 4.7.4). If so, the UDM derives the actual SUPI (IMSI) from the de-concealed SUCI (GLI/GCI). An anonymous SUCI is composed by setting the SUPI Type field to 1 (Network-Specific Identifier), using the null protection scheme, and where the scheme output corresponds to a username set to either the "anonymous" string or to an empty string (see IETF RFC 7542 [126], clause 2.4). The scheme output is formatted as a variable length of characters as specified for the username in clause 2.2 of IETF RFC 7542 [126]. NOTE 2: If the null protection scheme is used, the NFs can derive SUPI from SUCI when needed. The AMF derives SUPI used for AUSF discovery from SUCI when the Routing-Indicator is zero and the protection scheme is null. For an anonymous SUCI, an NF can derive an anonymous SUPI from an anonymous SUCI when needed; this is, the NF can derive a SUPI in NAI format for which the "username" part of the SUPI is "anonymous" or omitted. Figure 2.2B-3 defines the scheme output for the Elliptic Curve Integrated Encryption Scheme Profile A. Figure 2.2B-3: Scheme Output for Elliptic Curve Integrated Encryption Scheme Profile A The ECC ephemeral public key is formatted as 64 hexadecimal digits, which allows to encode 256 bits. The ciphertext value is formatted as a variable length of hexadecimal digits. The MAC tag value is formatted as 16 hexadecimal digits, which allows to encode 64 bits. Editor's Note: clause C.3.2 of TS 33.501[ Security architecture and procedures for 5G System ] specifies that the scheme output may contain other parameters (not further defined in the specification). It is FFS how to format these parameters. Figure 2.2B-4 defines the scheme output for the Elliptic Curve Integrated Encryption Scheme Profile B. Figure 2.2B-4: Scheme Output for Elliptic Curve Integrated Encryption Scheme Profile B The ECC ephemeral public key is formatted as 66 hexadecimal digits, which allows to encode 264 bits. The ciphertext value is formatted as a variable length of hexadecimal digits. The MAC tag value is formatted as 16 hexadecimal digits, which allows to encode 64 bits. Editor's Note: clause C.3.2 of TS 33.501[ Security architecture and procedures for 5G System ] specifies that the scheme output may contain other parameters (not further defined in the specification). It is FFS how to format these parameters. Figure 2.2B-5 defines the scheme output for Home Network proprietary protection schemes. Figure 2.2B-5: Scheme Output for Home Network proprietary protection schemes The Home Network defined scheme output is formatted as a variable length of hexadecimal digits. Its format is not further defined in 3GPP specifications. As examples, assuming the IMSI 234150999999999, where MCC=234, MNC=15 and MSISN=0999999999, the Routing Indicator 678, and a Home Network Public Key Identifier of 27: - the SUCI for the null protection scheme is composed of: 0, 234, 15, 678, 0, 0 and 0999999999 - the SUCI for the Profile <A> protection scheme is composed of: 0, 234, 15, 678, 1, 27, <EEC ephemeral public key value>, <encryption of 0999999999> and <MAC tag value> | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.2B |
3,731 | 6.3.13 NWDAF discovery and selection | Multiple instances of NWDAF may be deployed in a network. The NF consumers shall utilize the NRF to discover NWDAF instance(s) unless NWDAF information is available by other means, e.g. locally configured on NF consumers. NF consumers may make an additional query to UDM, when supported, as detailed below. The NWDAF selection function in NF consumers selects an NWDAF instance based on the available NWDAF instances. The NRF may return one or more candidate NWDAF instance(s) and each candidate NWDAF instance (based on its registered profile) supports the Analytics ID with a time that is less than or equal to the Supported Analytics Delay. The following factors may be considered by the NF consumer for NWDAF selection: - S-NSSAI. - Analytics ID(s). - Supported service(s), possibly with their associated Analytics IDs. - NWDAF Serving Area information, i.e. list of TAIs, for which the NWDAF can provide analytics, train ML models and provide trained ML models and/or data; for each item of this list, a weight may be defined in the NWDAF NF profile to indicate the priority of the NWDAF to cover the TA. NOTE 1: If all services provided by one NWDAF do not support the same Analytics ID, the NWDAF registers the Analytics IDs of the services at the service level. NOTE 2: Analytics ID(s) at service level take precedence over Analytics ID(s) at NF level. NOTE 3: For discovery of NWDAF supporting Nnwdaf_AnalyticsSubscription or Nnwdaf_AnalyticsInfo services, the Analytics IDs at the NWDAF NF profile are used. - (only when DCCF is hosted by NWDAF): - NF type of the data source. - NF Set ID of the data source. NOTE 4: Can be used when the NWDAF determines that it needs to discover another NWDAF which is responsible for co-ordinating the collection of required data. The NWDAF does a new discovery for a target NWDAF via NRF using NF Set ID of the data source. NOTE 5: For discovery of NWDAF supporting Nnwdaf_DataManagement service, at least the NWDAF Serving Area information from the NWDAF profile are used. NOTE 6: The presence of NF type of data source or NF set ID of the data source denotes that the NWDAF can collect data from such NF Sets or NF Types. - Supported Analytics Delay of the requested Analytics ID(s) (see clause 6.2.6.2). In the case of multiple instances of NWDAFs deployment, following factors may also be considered: - NWDAF Capabilities: - Analytics aggregation capability. - Analytics metadata provisioning capability. - Accuracy checking capability. Applicable when NF consumer cannot determine a suitable NWDAF instance based on NRF discovery response, and when NWDAF registration in UDM is supported, as defined in clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]: NF consumers may query UDM (Nudm_UECM_Get service operation) for determining the ID of the NWDAF serving the UE. The following factors may be considered by NF consumers to select an NWDAF instance already serving a UE for an Analytics ID: - SUPI. - Analytics ID(s). When selecting an NWDAF for ML model provisioning, the following additional factors may be considered by the NWDAF: - The ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest (see clause 5.2, TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]) for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID, if available. When selecting an NWDAF that supports Federated Learning, the following additional factors may be considered by the NWDAF: - Time Period of Interest: time interval [start…end], during which the Federated Learning will be performed. - when selecting FL client NWDAF: - FL capability type as FL client NWDAF per Analytics ID. - NF type(s) of the data source(s) where data can be collected as input for local model training. - NF Set ID(s) of the data source(s) where data can be collected as input for local model training. - ML Model Interoperability indicator. - when selecting FL server NWDAF: - FL capability type as FL server NWDAF per Analytics ID. - The ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]) for the trained ML model(s) per Analytics ID(s), if available. When selecting a NWDAF for roaming case, the detailed mechanism is defined in clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.13 |
3,732 | 8.2.2.3.5 Minimum Requirement 2 Tx Antenna Port (Superposed transmission) | The requirements are specified in Table 8.2.2.3.5-2, with the addition of the parameters in Table 8.2.2.3.5-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the minimun performance of open-loop spatial multiplexing with 2 transmitter antennas superposed with simultaneous PDSCH interference. Table 8.2.2.3.5-1: Test Parameters for Minimum Requirement 2 Tx Antenna Port - Superposed transmission (FRC) Table 8.2.2.3.5-2: Minimum Performance for Minimum Requirement 2 Tx Antenna Port - Superposed transmission (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.2.2.3.5 |
3,733 | 5.6.1.2.1 UE is not using 5GS services with control plane CIoT 5GS optimization | The UE initiates the service request procedure by sending a SERVICE REQUEST message to the AMF. The UE shall start timer T3517 and enter the state 5GMM-SERVICE-REQUEST-INITIATED. If the UE is sending the SERVICE REQUEST message from 5GMM-IDLE mode and the UE needs to send non-cleartext IEs, the UE shall send the SERVICE REQUEST message including the NAS message container IE as described in subclause 4.4.6. For cases a), b), and g) in subclause 5.6.1.1, the service type IE in the SERVICE REQUEST message shall be set to "mobile terminated services". For cases c), d), e), f), i), j), l), la, m), n), and q) in subclause 5.6.1.1, if the UE is a UE configured for high priority access in selected PLMN or SNPN, the service type IE in the SERVICE REQUEST message shall be set to "high priority access". For case a) in subclause 5.6.1.1: a) if the paging request includes an indication for non-3GPP access type, the Allowed PDU session status IE shall be included in the SERVICE REQUEST message. If the UE has PDU session(s) associated with non-3GPP access for which the associated S-NSSAI(s) are included in the allowed NSSAI for 3GPP access or the S-NSSAI associated with the PDU session is included in the partially allowed NSSAI for 3GPP access and the TAI where the UE is currently camped is in list of TAs for which the S-NSSAI is allowed, the UE shall indicate the PDU session(s) for which the UE allows the user-plane resources to be re-established over 3GPP access in the Allowed PDU session status IE. Otherwise, the UE shall not indicate any PDU session(s) in the Allowed PDU session status IE; and b) if the UE has uplink user data pending to be sent over 3GPP access, the Uplink data status IE shall be included in the SERVICE REQUEST message to indicate the PDU session(s) for which the UE has pending user data to be sent. Otherwise, the Uplink data status IE shall not be included in the SERVICE REQUEST message. For case b) in subclause 5.6.1.1: a) the Allowed PDU session status IE shall be included in the SERVICE REQUEST message. If the UE has PDU session(s) associated with non-3GPP access for which the associated S-NSSAI(s) are included in the allowed NSSAI for 3GPP access or the S-NSSAI associated with the PDU session is included in the partially allowed NSSAI for 3GPP access and the TAI where the UE is currently camped is in list of TAs for which the S-NSSAI is allowed, the UE shall indicate the PDU session(s) for which the UE allows the user-plane resources to be re-established over 3GPP access in the Allowed PDU session status IE. Otherwise, the UE shall not indicate any PDU session(s) in the Allowed PDU session status IE; and b) if the UE has uplink user data pending to be sent over 3GPP access, the Uplink data status IE shall be included in the SERVICE REQUEST message to indicate the PDU session(s) for which the UE has pending user data to be sent. Otherwise, the Uplink data status IE shall not be included in the SERVICE REQUEST message. For cases a) and b) in subclause 5.6.1.1, if the UE is in a non-allowed area or the UE is not in an allowed area, the UE shall set the Allowed PDU session status IE as specified in subclause 5.3.5.2. When the Allowed PDU session status IE is included in the SERVICE REQUEST message, the UE shall indicate that a PDU session is not allowed to be transferred to the 3GPP access if the 3GPP PS data off UE status is "activated" for the corresponding PDU session and the UE is not using the PDU session to send uplink IP packets for any of the 3GPP PS data off exempt services (see subclause 6.2.10). For case c) in subclause 5.6.1.1, the Uplink data status IE shall not be included in the SERVICE REQUEST message except if the UE has one or more active always-on PDU sessions associated with the access type over which the SERVICE REQUEST message is sent. If the UE is not a UE configured for high priority access in selected PLMN or SNPN and: a) if the SERVICE REQUEST message is triggered by a request for emergency services from the upper layer, the UE shall set the service type IE in the SERVICE REQUEST message to "emergency services"; or b) otherwise, the UE shall set the service type IE to "signalling". When the UE is in a non-allowed area or is not in an allowed area as specified in subclause 5.3.5 and: a) if the uplink signalling pending is to indicate a change of 3GPP PS data off UE status for a PDU session, the UE shall set the service type IE in the SERVICE REQUEST message to "elevated signalling", and shall not include the Uplink data status IE in the SERVICE REQUEST message even if the UE has one or more active always-on PDU sessions associated with the access type over which the SERVICE REQUEST message is sent; or b) otherwise, the UE shall not initiate service request procedure except for emergency services, high priority access or responding to paging or notification. For cases d) and e) in subclause 5.6.1.1, the Uplink data status IE shall be included in the SERVICE REQUEST message to indicate the PDU session(s) the UE has pending user data to be sent. If the UE is not a UE configured for high priority access in selected PLMN or SNPN: a) if there exists an emergency PDU session which is indicated in the Uplink data status IE the service type IE in the SERVICE REQUEST message shall be set to "emergency services"; or b) otherwise, the service type IE in the SERVICE REQUEST message shall be set to "data". NOTE 1: For a UE in NB-N1 mode, the Uplink data status IE cannot be used to request the establishment of user-plane resources such that there will be user-plane resources established for a number of PDU sessions that exceeds the UE's maximum number of supported user-plane resources. For case f) in subclause 5.6.1.1: a) if the UE has uplink user data pending to be sent, the Uplink data status IE shall be included in the SERVICE REQUEST message to indicate the PDU session(s) the UE has pending user data to be sent. If the UE is not a UE configured for high priority access in selected PLMN or SNPN, the service type IE in the SERVICE REQUEST message shall be set to "data"; b) otherwise, if the UE is not a UE configured for high priority access in selected PLMN or SNPN, the service type IE in the SERVICE REQUEST message shall be set to "signalling". For case g) in subclause 5.6.1.1, if the UE has uplink user data pending to be sent, the Uplink data status IE shall be included in the SERVICE REQUEST message to indicate the PDU session(s) the UE has pending user data to be sent. For case h) in subclause 5.6.1.1, the UE shall send a SERVICE REQUEST message with service type set to "emergency services fallback" and without an Uplink data status IE. For case i) in subclause 5.6.1.1, if the UE is not configured for high priority access in selected PLMN or SNPN, the UE shall set the Service type IE in the SERVICE REQUEST message as follows: a) if the pending message is an UL NAS TRANSPORT message with the Request type IE set to "initial emergency request" or "existing emergency PDU session", the UE shall set the Service type IE in the SERVICE REQUEST message to "emergency services"; or b) otherwise, the UE shall set the Service type IE in the SERVICE REQUEST message to "signalling". For case j) in subclause 5.6.1.1: a) the UE shall include the Uplink data status IE in the SERVICE REQUEST message indicating the PDU session(s) for which the UE has uplink user data pending and the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication or "RRC Connection failure" indication from the lower layers, if any; and b) if the UE is not a UE configured for high priority access in selected PLMN or SNPN, the UE shall set the Service type IE in the SERVICE REQUEST message as follows: 1) if there is an emergency PDU session which is indicated in the Uplink data status IE, the UE shall set the Service type IE in the SERVICE REQUEST message to "emergency services"; or 2) if there is no emergency PDU session which is indicated in the Uplink data status IE, the UE shall set the Service type IE in the SERVICE REQUEST message to "data". For cases l), la, n), and q) in subclause 5.6.1.1, if the UE is not a UE configured for high priority access in selected PLMN or SNPN: a) if there exists an emergency PDU session which is indicated in the Uplink data status IE the service type IE in the SERVICE REQUEST message shall be set to "emergency services"; or b) otherwise, the service type IE in the SERVICE REQUEST message shall be set to "signalling". For case m) in subclause 5.6.1.1, the UE shall not include the Paging restriction IE in the SERVICE REQUEST message and set Service type to "signalling". The UE may include the UE request type IE and set Request type to "NAS signalling connection release" to remove the paging restriction and request the release of the NAS signalling connection at the same time. If the UE requests the release of the NAS signalling connection, the UE shall not include the Uplink data status IE in the SERVICE REQUEST message. For cases o) and p) in subclause 5.6.1.1, the UE shall not include the Uplink data status IE and the Allowed PDU session status IE in the SERVICE REQUEST message. Further, - for case o in subclause 5.6.1.1, the UE shall set Request type to "NAS signalling connection release" in the UE request type IE and Service type to "signalling"; - for case p in subclause 5.6.1.1, the UE shall set Request type to "Rejection of paging" in the UE request type IE and Service type to "mobile terminated services"; and may include its paging restriction preference in the Paging restriction IE in the SERVICE REQUEST message. The UE shall include a valid 5G-S-TMSI in the 5G-S-TMSI IE of the SERVICE REQUEST message. For all cases except cases o) and p) in subclause 5.6.1.1, if the UE has one or more active always-on PDU sessions associated with the access type over which the SERVICE REQUEST message is sent and the user-plane resources for these PDU sessions are not established, the UE shall include the Uplink data status IE in the SERVICE REQUEST message and indicate that the UE has pending user data to be sent for those PDU sessions. If the UE has one or more active PDU sessions which are not accepted by the network as always-on PDU sessions and no uplink user data pending to be sent for those PDU sessions, the UE shall not include those PDU sessions in the Uplink data status IE in the SERVICE REQUEST message. The Uplink data status IE may be included in the SERVICE REQUEST message to indicate which PDU session(s) associated with the access type the SERVICE REQUEST message is sent over have pending user data to be sent or are associated with active multicast MBS session(s). If the UE is located outside the LADN service area of a PDU session, the UE shall not include the PDU session for LADN in the Uplink data status IE. If the UE is in a non-allowed area or the UE is not in an allowed area, the UE shall apply the restrictions for the inclusion of the Uplink data status IE specified in subclause 5.3.5.2. The PDU session status information element may be included in the SERVICE REQUEST message to indicate: - the single access PDU session(s) not in 5GSM state PDU SESSION INACTIVE in the UE associated with the access type the SERVICE REQUEST message is sent over; and - the MA PDU session(s) not in 5GSM state PDU SESSION INACTIVE and having the corresponding user plane resources being established or established in the UE on the access the SERVICE REQUEST message is sent over. If the SERVICE REQUEST message includes a NAS message container IE, the AMF shall process the SERVICE REQUEST message that is obtained from the NAS message container IE as described in subclause 4.4.6. If the UE has an emergency PDU session over the non-current access, it shall not initiate the SERVICE REQUEST message with the service type IE set to "emergency services" over the current access, unless the SERVICE REQUEST message has to be initiated to perform handover of an existing emergency PDU session from the non-current access to the current access. NOTE 2: Transfer of an existing emergency PDU session between 3GPP access and non-3GPP access is needed e.g. if the UE determines that the current access is no longer available. | 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.1.2.1 |
3,734 | 4.23.5 Handling multiple tracking area codes from the lower layers | When a UE camps on a satellite NG-RAN cell, the UE may receive multiple TACs from the lower layers. The UE shall construct TAIs from the multiple TACs (i.e. concatenate the identity of the current PLMN and each of the TACs) and select a TAI as follows: a) if at least one TAI belongs to the current registration area of the UE, the UE shall select a TAI which belongs to the current registration area of the UE according to the followings. If there are multiple TAIs which belong to the current registration area of the UE, the UE shall select a TAI as follows: 1) if there is a TAI which belongs to the list of "allowed tracking area" (if any) and does not belong to the list of "non-allowed tracking areas" (if any), the UE shall select a TAI which belongs to the list of "allowed tracking area" (if any) and does not belong to the list of "non-allowed tracking areas" (if any). In this case, if there are multiple TAIs which belong to the list of "allowed tracking area" (if any) and does not belong to the list of "non-allowed tracking areas" (if any), then the UE shall consider each of these TAIs equal and select a TAI in an implementation-specific way (e.g. taking into account LADN service area information). If these multiple TAIs contain the previous current TAI, the current TAI can be left unchanged. 2) if there is no TAI which belongs to the list of "allowed tracking area" (if any) and does not belong to the list of "non-allowed tracking areas" (if any) or neither the list of "allowed tracking area" nor the list of "non-allowed tracking areas" is available, then the UE shall consider each of these TAIs equal and select a TAI in an implementation-specific way (e.g. taking into account LADN service area information). If these multiple TAIs contain the previous current TAI, the current TAI can be left unchanged. b) if the current registration area is not available in the UE or no TAI belongs to the current registration area of the UE and: 1) there is a TAI which belongs to neither the list of "5GS forbidden tracking areas for roaming" nor the list of "5GS forbidden tracking areas for regional provision of service", the UE shall select a TAI which belongs to neither the list of "5GS forbidden tracking areas for roaming" nor the list of "5GS forbidden tracking areas for regional provision of service". In this case, if there are multiple TAIs which belong to neither the list of "5GS forbidden tracking areas for roaming" nor the list of "5GS forbidden tracking areas for regional provision of service", then the UE shall consider each of these TAIs equal and select a TAI in an implementation-specific way. 2) all TAIs belong to the list of "5GS forbidden tracking areas for roaming" or the list of "5GS forbidden tracking areas for regional provision of service", then the UE shall consider each of these TAIs equal and select a TAI in an implementation-specific way. The UE shall consider the selected TAI as the current TAI. The UE shall select a TAI when: a) the UE receives multiple TACs from the lower layers; or b) the UE has received multiple TACs from the lower layers upon starting to camping on the current cell and the registration area, the list of "allowed tracking areas", the list of "non-allowed tracking areas", the list of "5GS forbidden tracking areas for roaming", or the list of "5GS forbidden tracking areas for regional provision of service" is updated. Handling of the list of "5GS forbidden tracking areas for roaming" and the list of "5GS forbidden tracking areas for regional provision of service" is specified in subclause 5.3.13. | 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.23.5 |
3,735 | P.2 Security aspects of DNS | It is recommended that the UE and DNS server(s) support DNS over (D)TLS as specified in RFC 7858 [83] and RFC 8310 [84]. The DNS server(s) that are deployed within the 3GPP network can enforce the use of DNS over (D)TLS. The UE can be pre-configured with the DNS server security information (out-of-band configurations specified in the IETF RFCs like, credentials to authenticate the DNS server, supported security mechanisms, port number, etc.), or the core network can configure the DNS server security information to the UE. NOTE: The use of DNS over (D)TLS with DNS server(s) that are deployed outside the 3GPP network is outside the scope of this document. When DNS over (D)TLS is used, a TLS cipher suite that supports integrity protection needs to be negotiated. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | P.2 |
3,736 | 5.6.1 Description | According to clause 5.3 of the present document, airspace administration shall be able to query the UTM for identity, location, and associated information about a UAS. However, local broadcast of a UAS identity provides a backup means of ID and tracking if the network is compromised, degraded, or unavailable. If UAS were to locally broadcast their identity and other information, this would allow airspace enforcement or other authorized personnel with the appropriate equipment to discover UAS within proximity. Figure 5.6.1-1: Data acquisition by law enforcement | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.6.1 |
3,737 | 8.3.20.8 Extended protocol configuration options | This IE shall be included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network, and: a) the UE is in NB-S1 mode; b) the requested PDN Type is non-IP or Ethernet; or c) the requested APN is for UAS services. This IE shall be included if: a) the UE supports local IP address in traffic flow aggregate description and TFT filter, the UE is in NB-S1 mode and the requested PDN Type is different from non-IP and Ethernet; or b) the UE supports local IP address in traffic flow aggregate description and TFT filter, the requested PDN Type is different from non-IP and Ethernet, and the requested APN is for UAS services. This IE shall not be included if the Protocol configuration options IE is included in the message. | 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 | 8.3.20.8 |
3,738 | 7.7.0 Handling Piggybacked Messages | For piggybacked initial messages, the following general rule shall apply: the triggered response message carrying the piggybacked message shall be processed first, according to the following clauses. Subsequently, the piggybacked initial message shall be processed independently. If the processing of dedicated bearer activation message results in an error, this shall not affect the default bearer establishment. If the default bearer establishment fails, the dedicated bearer activation related message shall be discarded. | 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 | 7.7.0 |
3,739 | 5.5.4.23 Event A3H1 (Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes higher than a threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when both condition A3H1-1 and condition A3H1-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A3H1-3 or condition A3H1-4, i.e. at least one of the two, as specified below, is fulfilled; 1> use the SpCell for Mp, Ofp and Ocp. NOTE 1: The cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this event which may be different from the NR SpCell measObjectNR. Inequality A3H1-1 (Entering condition 1) Mn + Ofn + Ocn – Hys1 > Mp + Ofp + Ocp + Off Inequality A3H1-2 (Entering condition 2) Ms – Hys2 > Thresh Inequality A3H1-3 (Leaving condition 1) Mn + Ofn + Ocn + Hys1 < Mp + Ofp + Ocp + Off Inequality A3H1-4 (Leaving condition 2) Ms + Hys2 < Thresh The variables in the formula are defined as follows: Mn is the measurement result of the neighbouring cell, not taking into account any offsets. Ofn is the measurement object specific offset of the reference signal of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell). Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell. Mp is the measurement result of the SpCell, not taking into account any offsets. Ofp is the measurement object specific offset of the SpCell (i.e. offsetMO as defined within measObjectNR corresponding to the SpCell). Ocp is the cell specific offset of the SpCell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell. Hys1 is the hysteresis parameter for this event (i.e. a3-Hysteresis as defined within reportConfigNR for this event). Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigNR for this event). Ms is the Aerial UE altitude relative to the sea level. Hys2 is the hysteresis parameter for this event (i.e. h1-Hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. h1-Threshold as defined within reportConfigNR for this event). Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, Hys1, Ofp, Ocp, Off are expressed in dB. Ms, Hys2, Thresh are expressed in meters. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.23 |
3,740 | 5.8.10.2.4 Sidelink measurement object removal | The UE shall: 1> for each sl-MeasObjectId included in the received sl-MeasObjectToRemoveList that is part of sl-MeasObjectList in VarMeasConfigSL: 2> remove the entry with the matching sl-MeasObjectId from the sl-MeasObjectList within the VarMeasConfigSL; 2> remove all sl-MeasId associated with this sl-MeasObjectId from the sl-MeasIdList within the VarMeasConfigSL, if any; 2> if a sl-MeasId is removed from the sl-MeasIdList: 3> remove the measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included; 3> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId. NOTE: The UE does not consider the message as erroneous if the sl-MeasObjectToRemoveList includes any sl-MeasObjectId value that is not part of the current UE configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.2.4 |
3,741 | 1.7.2.2 Packet services in Iu mode (Iu mode only) | An MS attached to packet switched domain may operate in one of the following MS operation modes, see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]: - CS/PS mode of operation; or - PS mode of operation. The terms 'CS/PS mode of operation' and 'PS mode of operation' are not used in the present document with some exceptions. Instead the terms 'MS operation mode A' and 'MS operation mode C' are used. In network operation mode I and II (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]), an MS in CS/PS mode of operation shall use the same procedures as for a GPRS MS operating in MS operation mode A, unless it is explicitly stated for A/Gb mode only or Iu mode only. In network operation mode I and II, an MS in PS mode of operation shall use the same procedures as for a GPRS MS operating in MS operation mode C, unless it is explicitly stated for A/Gb mode only or Iu mode only. | 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 | 1.7.2.2 |
3,742 | 5.5.3.2.2 Mapping to physical resources for additional SRS | An additional SRS spans one or more SC-FDMA symbols in the time domain, where - the starting SC-FDMA symbol within the subframe is given by the higher-layer parameter srs-StartPosAdd; - the duration in number of SC-FDMA symbols, including potential guard symbols, is given by the higher-layer parameter srs-DurationAdd. Mapping to physical resources shall be done according to clause 5.5.3.2.1 with the following exceptions: - frequency hopping between SC-FDMA symbols is supported and if a UE is configured by higher layer parameter srs-GuardSymbolFH-Add, a guard symbol is added between every frequency hop; - antenna switching within a subframe is supported and if a UE is configured by higher layer parameter srs-GuardSymbolAS-Add, a guard symbol is added between every antenna switching; - where is the additional SRS transmission number not counting guard symbol(s) within the subframe with corresponding to the starting SC-FDMA symbol , and is the repetition factor given by the higher-layer parameter srs-RepNumAdd; - is given by the higher-layer parameter srs-BandwidthAdd; - is given by the higher-layer parameter srs-HoppingBandwidthAdd; - is the number of frequency hops with the same antenna/antenna pair for additional SRS, derived from if antenna switching is not configured for additional SRS, and from if antenna switching is configured for additional SRS, where is the repetition factor given by the higher-layer parameter srs-RepNumAdd, is the number of antenna switches for additional SRS defined in 8.2 of [4], is the guard-symbol configuration for antenna switching given by the higher-layer parameter srs-GuardSymbolAS, is the guard symbol configuration for frequency hopping given by the higher-layer parameter srs-GuardSymbolFH, and is given by the higher-layer parameter srs-DurationAdd; - is given by the higher-layer parameter srs-FreqDomainPosAdd; - is given by the higher-layer parameter srs-AntennaPortAdd; - is given by the higher-layer parameter srs-CyclicShiftAdd; - is given by the higher-layer parameter srs-TransmissionCombNumAdd; - is given by the higher-layer parameter srs-TransmissionCombAdd. | 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 | 5.5.3.2.2 |
3,743 | W.5 Security protection for interworking between 5MBS and eMBMS | Interworking between 5G MBS and eMBMS is supported at service layer. The procedures for inter system mobility with interworking at service layer is specified in clause 7.4 in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [103]. The joint BM-SC+MBSF/MBSTF functionality provides the security protection for MBS traffic. During inter-system mobility, when the target system is EPS, the security protection specified in TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102] applies. The security protection specified in present document applies to the case when the target system is 5GS. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | W.5 |
3,744 | 8.6.3 Repeated IEs | If an information element with format T, TV, or TLV is repeated in a message in which repetition of the information element is not specified in clause 9 of the present document, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. The network should follow the same procedures. | 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.6.3 |
3,745 | 16.14.2.2 Timing Advance and Frequency Pre-compensation | For the serving cell, the network broadcast valid ephemeris information and Common TA parameters. The UE shall have valid GNSS position as well as ephemeris and Common TA before connecting to an NTN cell. To achieve synchronisation, before and during connection to an NTN cell, the UE shall compute the RTT between UE and the RP based on the GNSS position, the ephemeris, and the Common TA parameters (see clause 4.2 in TS 38.213[ NR; Physical layer procedures for control ] [38]), and autonomously pre-compensate the TTA for the RTT between the UE and the RP as illustrated in Figure 16.14.2.1-1 (see clause 4.3 of TS 38.211[ NR; Physical channels and modulation ] [52]). The UE shall compute the frequency Doppler shift of the service link, and autonomously pre-compensate for it in the uplink transmissions, by considering UE position and the ephemeris. If the UE does not have a valid GNSS position and/or valid ephemeris and Common TA, it shall not transmit until both are regained. In connected mode, the UE shall be able to continuously update the Timing Advance and frequency pre-compensation. The UE may be configured to report Timing Advance during Random Access procedures or in connected mode. In connected mode, event-triggered reporting of the Timing Advance is supported. Figure 16.14.2.2-1: Void While the pre-compensation of the instantaneous Doppler shift experienced on the service link is to be performed by the UE, the management of Doppler shift experienced over the feeder link and transponder frequency error is left to the network implementation. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.2.2 |
3,746 | 8.19.2 Remote UE RRC Reestablishment | The signalling flow for Remote UE RRC Reestablishment is shown in Figure 8.19.2-1. Figure 8.19.2-1: Remote UE RRC Reestablishment procedure 1. The U2N Remote UE and the U2N Relay UE perform discovery procedure, and establish PC5 connection using NR ProSe procedure. This step may be omitted if PC5 connection was established. 2. The U2N Remote UE sends an RRCReestablishmentRequest message to the U2N Relay UE via PC5 Relay RLC Channel. 3~10. The gNB-CU allocates the local ID of the U2N Remote UE if the U2N Relay UE does not have it. The details of those steps can be referred to clause 8.19.1. 11. After receiving the local ID of the U2N Remote UE, the U2N Relay UE sends the RRCReestablishmentRequest message of the U2N Remote UE to gNB-DU. 12. The gNB-DU allocates a C-RNTI and a gNB-DU UE F1AP ID for the U2N Remote UE and sends the INITIAL UL RRC MESSAGE TRANSFER message to gNB-CU by encapsulating the RRCReestablishmentRequest message of the U2N Remote UE. In addition, the local ID of the U2N Remote UE, the gNB-DU UE F1AP ID of the U2N Relay UE and the sidelink configuration container for at least the PC5 Relay RLC channel configuration for relaying of U2N Remote UE’s SRB1 are included in the INITIAL UL RRC MESSAGE TRANSFER message. 13. The gNB-CU configures the U2N Relay UE with PC5 Relay RLC channel, Uu Relay RLC channel and bearer mapping for relaying of U2N Remote UE’s SRB1. According to the configuration from gNB-CU, the U2N Relay UE establishes a PC5 Relay RLC channel for relaying of U2N Remote UE’s SRB1 over PC5 and establishes a Uu Relay RLC channel for relaying of U2N Remote UE’s SRB1 over Uu. NOTE 1: This step may be performed earlier, e.g., via steps 5~8. 14~23. The details of those steps can be referred to Steps 5~14 in clause 8.7. For L2 U2N relay, the RRC message(s) between the U2N Remote UE and the gNB-DU are relayed via the U2N Relay UE; Steps 18~19 may additionally perform the configurations of PC5 Relay RLC channel(s) for relaying of U2N Remote UE’s SRB1, SRB2 and DRBs. 24. The gNB-CU configures additional Uu Relay RLC channels between the gNB-DU and the U2N Relay UE, and additional PC5 Relay RLC channels for the U2N Relay UE for relaying of U2N Remote UE’s DRBs and SRBs. Also, such step may configure the bearer mapping between U2N Remote UE’s DRB/SRB and PC5/Uu Relay RLC channel at the U2N Relay UE. NOTE 2: This step may be performed earlier. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.19.2 |
3,747 | 9.11.4.21 5GSM congestion re-attempt indicator | The purpose of the 5GSM congestion re-attempt indicator information element is to indicate whether the back-off timer is applied in the registered PLMN or all PLMNs or in the registered SNPN or all equivalent SNPNs, and additionally to indicate whether the back-off timer is applied in the current access type or both 3GPP access type and non-3GPP access type. The 5GSM congestion re-attempt indicator information element is coded as shown in figure 9.11.4.21.1 and table 9.11.4.21.1. The 5GSM congestion re-attempt indicator is a type 4 information element with a length of 3 octets. Figure 9.11.4.21.1: 5GSM congestion re-attempt indicator Table 9.11.4.21.1: 5GSM congestion re-attempt indicator | 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.4.21 |
3,748 | 6.2.1 Composition of IMEI | The International Mobile station Equipment Identity (IMEI) is composed as shown in figure 10. Figure 10: Structure of IMEI The IMEI is composed of the following elements (each element shall consist of decimal digits only): - Type Allocation Code (TAC). Its length is 8 digits; - Serial Number (SNR) is an individual serial number uniquely identifying each equipment within the TAC. Its length is 6 digits; - Check Digit (CD) / Spare Digit (SD): If this is the Check Digit see paragraph below; if this digit is Spare Digit it shall be set to zero, when transmitted by the MS. The IMEI (14 digits) is complemented by a Check Digit (CD). The Check Digit is not part of the digits transmitted when the IMEI is checked, as described below. The Check Digit is intended to avoid manual transmission errors, e.g. when customers register stolen MEs at the operator's customer care desk. The Check Digit is defined according to the Luhn formula, as defined in annex B. NOTE: The Check Digit is not applied to the Software Version Number. The security requirements of the IMEI are defined in 3GPP TS 22.016[ International Mobile station Equipment Identities (IMEI) ] [32]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.1 |
3,749 | 5.19.7.3 DNN based congestion control | DNN based congestion control is designed for the purpose of avoiding and handling of NAS SM signalling congestion for the UEs with a back-off timer associated with or without a DNN regardless of the presence of an S-NSSAI. Both UE and 5GC shall support the functionality to enable DNN based congestion control. SMFs may apply DNN based congestion control towards the UE by rejecting PDU Session Establishment Request message, or PDU Session Modification Request message except for those sent for the purpose of reporting 3GPP PS Data Off status change for a specific DNN with a running back-off timer. The SMF may release PDU Sessions belonging to a congested DNN by sending a PDU Session Release Command message towards the UE with a DNN back-off timer. If a DNN back-off time is set in the PDU Session Release Command message, the cause value of "reactivation requested" shall not be set. If NWDAF is deployed, the SMF may make use of Session Management Congestion Control Experience analytics provided by NWDAF, as defined in clause 6.12 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86], to determine back-off timer provided to UEs. NOTE: For example, the SMF can apply a short back-off timer to the UEs in the list of high-experienced UEs while the SMF can apply a long back-off timer to the UEs in the list of low-experienced UEs. When DNN based congestion control is activated at AMF e.g. configured by OAM, the AMF provides a NAS Transport Error message for the NAS Transport message carrying an SM message, and in the NAS Transport Error message it includes a DNN back-off timer. The UE associates the received back-off time with the DNN (i.e. no DNN, DNN only) which the UE included in the uplink NAS MM message carrying the corresponding NAS SM request message. The UE associates the received back-off time with the DNN (i.e. no DNN, DNN only) in any PLMN unless the DNN associated with the back-off timer is an LADN DNN in which case the UE only associates it to the PLMN in which the back-off time was received. The UE behaves as follows when the DNN back-off timer is running: - If a DNN is associated with the back-off timer, the UE shall not initiate any Session Management procedures for the congested DNN. The UE may initiate Session Management procedures for other DNNs. The UE shall not initiate any Session Management procedure for the corresponding APN when UE moves to EPS. The UE may initiate Session Management procedures for other APNs when the UE moves to EPS; - If no DNN is associated with the back-off timer, the UE may only initiate Session Management requests of any PDU Session Type for a specific DNN; - Upon Cell/TA/PLMN/RAT change, change of untrusted non-3GPP access network or change of Access Type, the UE shall not stop the back-off timer; - The UE is allowed to initiate the Session Management procedures for high priority access and emergency services; - The UE is allowed to initiate the Session Management procedure for reporting Data Off status change to the network; - If the UE receives a network initiated Session Management message other than PDU Session Release Command for the congested DNN associated to a running back-off timer, the UE shall stop the back-off timer and respond to the 5GC; - If the UE receives a PDU Session Release Command message for the congested DNN, it shall stop the back-off timer unless it receives a new back-off time from SMF; - The UE is allowed to initiate PDU Session Release procedure (i.e. sending PDU Session Release Request message). The UE shall not stop the back-off timer when the related PDU Session is released; - The list above is not an exhaustive list, i.e. more details of the above actions and further conditions, if any, are specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. If UE initiates one of the Session Management procedures that are exempted from NAS congestion control, the UE indicates that the carried NAS SM message is exempted from NAS congestion control in the UL NAS Transport message as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. When the DNN based congestion control is activated at AMF, if the UE indicates that the NAS SM message in the UL NAS Transport message is exempted from NAS congestion control, the AMF shall not apply DNN based congestion control on the UL NAS Transport message and shall forward the NAS SM message to the corresponding SMF with an indication that the message was received with exemption indication. The SMF evaluates whether the NAS SM message is allowed to be exempted from DNN based congestion control. If it is not, the SMF rejects the message, e.g. the SMF shall reject PDU Session Modification received if it is not for Data Off status reporting). The UE shall maintain a separate back-off timer for each DNN that the UE may use. To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the 5GC should select the back-off timer value so that deferred requests are not synchronized. If the UE required to report 5GSM Core Network Capability change, or the Always-on PDU Session Requested indication while DNN based congestion control was running and was unable to initiate SM signalling, the UE defers the related SM signalling until the DNN based congestion control timer expires and initiates the necessary SM signalling after the expiry of the timer. The DNN based Session Management congestion control is applicable to the NAS SM signalling initiated from the UE in the Control Plane. The Session Management congestion control does not prevent the UE from sending and receiving data or initiating Service Request procedures for activating User Plane connection towards the DNN(s) that are under Session Management congestion control. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.19.7.3 |
3,750 | 4.6.3.2 Support of network slice admission control and interworking with EPC | If EPS counting is required for a network slice, the network performs network slice admission control for the S-NSSAI(s) subject to NSAC to monitor and control the number of UEs per network slice and number of PDU sessions per network slice during the PDN connection establishment procedure. If the maximum number of UEs on a network slice associated with an S-NSSAI or the maximum number of PDU sessions on a network slice associated with an S-NSSAI have already been reached, the network rejects the PDN connectivity request using ESM cause #26 "insufficient resources" as specifed in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. NOTE: If there are more than one S-NSSAI associated with the APN used in the PDN connectivity request and some of but not all associated S-NSSAIs are not available due to either maximum number of UEs reached or maximum number of PDU sessions reached, the network can use the associated S-NSSAI for which maximum number of UEs and maximum number of PDU sessions have not reached to avoid PDN connectivity request rejection. | 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.6.3.2 |
3,751 | 6.24.2 Requirements | The 3GPP system shall be able to support an Ethernet transport service. The 5G network shall support the routing of non-IP packet (e.g. Ethernet frame) efficiently for private communication between UEs within a 5G LAN-type service. The 5G network shall be able to provide the required QoS (e.g. reliability, latency, and bandwidth) for non-IP packet (e.g. Ethernet frame) for private communication between UEs within a 5G LAN-type service. The Ethernet transport service shall support routing based on information extracted from Virtual LAN (VLAN) ID by the 3GPP system. The Ethernet transport service shall support the transport of Ethernet frames between UEs that Ethernet devices are connected to. The Ethernet transport service shall support the transport of Ethernet frames between a UE that an Ethernet device is connected to and an Ethernet network in DN (Data Network). NOTE: If more than one Ethernet devices need to be connected to a UE, they can be connected using an Ethernet switch between the devices and the UE. The Ethernet transport service shall support the transport of Ethernet broadcast frames. The Ethernet transport service shall support traffic filtering and prioritization based on source and destination MAC addresses. The Ethernet transport service shall support traffic filtering and prioritization based on Ethertype (including multiple Ethertypes in double tagging). The Ethernet transport service shall support traffic filtering and prioritization based on 802.1Q VLAN tags (including double tagging). The Ethernet transport service shall support routing based on information extracted by the 3GPP system from the Bridge Protocol Data Units created in the Ethernet network based on a Spanning Tree Protocol (e.g. RSTP). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.24.2 |
3,752 | 4.4.7.2 UL cell PDCP SDU Data Volume | a) This measurement provides the Data Volume (amount of PDCP SDU bits) in the uplink delivered from PDCP layer to RLC layer. The measurement is calculated per PLMN ID and per E-RAB QoS profile (QCI, ARP and GBR). The unit is Mbit. b) CC c) This measurement is obtained by counting the number of bits entering the eNodeB/RN. The measurement is performed at the PDCP SDU level. The measurement is performed per configured PLMN ID per configured UL QoS profile criteria. (See 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] , clause 4.1.9). d) Each measurement is an integer value representing the number of bits measured in Mbits. The number of measurements is equal to the number of PLMNs multiplied by the number of QoS profiles. [Total no. of measurement instances] x [no. of filter values for all measurements] (DL and UL) ≤ 200. e) The measurement name has the form DRB.PdcpSduVolumeUl_Filter. Filter = PLMNID (1-6), QCImax (1-255), QCImin (1-255), ARPmax (1-15), ARPmin (1-15), GBR (n), where n ( ≥ 1) corresponds to an operator defined bitrate range. Example: A measurement with filter PLMN=2, QCImax=4, QCImin=2, ARPmax=10, ARPmin=1 and GBR=3 results in the measurement name: DRB.PdcpSduVolumeUl_Plmn2Qci2-4Arp1-10Gbr3. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) Can be used by MOP (see TS 32.130[ Telecommunication management; Network sharing; Concepts and requirements ] [22]) for cross-operator accounting in shared networks. | 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.4.7.2 |
3,753 | 4.3.1 Offline charging functions 4.3.1.0 General | Figure 4.3.1.0.1 provides an overview of the offline part of the common charging architecture of Figure 4.2.2.1. The figure 4.3.1.0.1 depicts the logical charging functions as well as the reference points between these functions and to the BD. CTF: Charging Trigger Function CDF: Charging Data Function CGF: Charging Gateway Function BD: Billing Domain. This may also be a billing system/ billing mediation device. Figure 4.3.1.0.1: Logical ubiquitous offline charging architecture NOTE: Although not visualised in this figure 4.3.1.0.1, the OCS can also produce CDRs, i.e. act as a domain / service / subsystem element with embedded CTF, see clause 4.3.2.3. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1 |
3,754 | 4.2.1.2 Other Cases | The state PLMN SEARCH is also entered in the following cases: - in state NO IMSI, a SIM/USIM is inserted; - in any state except NO IMSI, NO CELL AVAILABLE, NORMAL SERVICE and RECEIVING GROUP CALL (NORMAL SERVICE) after the user has asked for a PLMN selection; - in any state except NO IMSI and NO CELL AVAILABLE, coverage is lost; - roaming is denied; - optionally, when the mobile station is in the ATTEMPTING TO UPDATE state and is in Automatic Network Selection mode and location update attempt counter is greater than or equal to 4. The service state when the PLMN SEARCH is left depends on the outcome of the search and on the presence of the SIM/USIM as specified in subclause 4.2.1.1. | 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.2.1.2 |
3,755 | 5.4A.2.2 Subslot-SPUCCH | For subslot-SPUCCH formats 1a and 1b, one or two bits are communicated by SPUCCH resource selection. The resource set available for selection are configured by higher layers (see n1SubslotSPUCCH-AN-List and sr-SubslotSPUCCH-ResourceList in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]). For subslot-SPUCCH format 1, information is carried by the presence/absence of transmission of subslot-SPUCCH from the UE. The sequence is generated as described in clause 5.4.1, assuming . The block of complex-valued symbols shall be scrambled by as described in clause 5.4.1 assuming , , and with replaced by , defined in Table 5.4A.2.2-1. Table 5.4A.2.2-1: The quantity for subslot-SPUCCH formats 1a and 1b Resources used for transmission of SPUCCH format 1, 1a and 1b are identified by a resource index from which the cyclic shift is determined, as described in clause 5.4.2, assuming the condition is fulfilled.The resource set for subslot-SPUCCH format 1/1a/1b is configured by higher layers (see n1SubslotSPUCCH-AN-List in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]): - subslot-SPUCCH format 1: - subslot-SPUCCH format 1a: - subslot-SPUCCH format 1b: Each resource indicates (a) bit state(s) as defined by Table 5.4A.2.2-2. Table 5.4A.2.2-2: Subslot-SPUCCH resource for formats 1a and 1b | 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 | 5.4A.2.2 |
3,756 | 5.5.5.3 Sorting of cell measurement results | The UE shall determine the sorting quantity according to parameters of the reportConfig associated with the measId that triggered the reporting: 1> if the reportType is set to eventTriggered: 2> for an NR cell, consider the quantity used in the aN-Threshold (for eventA1, eventA2, eventA4, eventA4H1 and eventA4H2) or in the a5-Threshold2 (for eventA5, eventA5H1 and eventA5H2) or in the aN-Offset (for eventA3, eventA3H1, eventA3H2 and eventA6) or in the x1-Threshold2 (for eventX1) as the sorting quantity; 2> for an E-UTRA cell, consider the quantity used in the bN-ThresholdEUTRA as the sorting quantity; 2> for an UTRA-FDD cell, consider the quantity used in the bN-ThresholdUTRA-FDD as the sorting quantity; 2> for a candidate L2 U2N Relay UE, consider the y1-Threshold2-Relay (for eventY1-Relay) or y2-Threshold-Relay (for eventY2-Relay) or z1-Threshold2-Relay (for eventZ1) as the sorting quantity; 1> if the reportType is set to periodical: 2> determine the sorting quantity according to reportQuantityCell for an NR cell, and according to reportQuantity for an E-UTRA cell, as below: 3> if a single quantity is set to true: 4> consider this quantity as the sorting quantity; 3> else: 4> if rsrp is set to true; 5> consider RSRP as the sorting quantity; 4> else: 5> consider RSRQ as the sorting quantity; 2> determine the sorting quantity according to reportQuantityUTRA-FDD for UTRA-FDD cell, as below: 3> if a single quantity is set to true: 4> consider this quantity as the sorting quantity; 3> else: 4> consider RSCP as the sorting quantity. 2> for a candidate L2 U2N Relay UE, consider the reportQuantityRelay as the sorting quantity; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.5.3 |
3,757 | 5.5.2.4.3 Execution phase | Figure 5.5.2.4.3-1: GERAN A/Gb mode to E-UTRAN Inter RAT HO, execution phase NOTE: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 9 and 9a concern GTP based S5/S8. The source SGSN continues to receive downlink and uplink user plane PDUs. When source SGSN receives the Forward Relocation Response message it may start downlink N-PDU relay and duplication to the target eNodeB (for Direct Forwarding) or via the Serving GW (for Indirect Forwarding), and the target eNodeB may start blind transmission of downlink user data towards the UE over the allocated radio channels. 1. The Source SGSN completes the preparation phase towards Source BSS by sending the message PS HO Required Acknowledge (TLLI, List of Set Up PFCs, Target RNC to Source BSS Transparent Container, Cause). This message includes all PFIs that could be established on the Target side. The Cause includes the value from the RAN Cause IE received from the target MME. The Target RNC to Source BSS Transparent Container includes the value from the Target to Source Transparent Container received from the target MME. Before sending the PS Handover Required Acknowledge message, the source SGSN may suspend downlink data transfer for any EPS Bearer contexts. Before sending the PS Handover Command message to the UE the source BSS, may try to empty the downlink BSS buffer for any BSS PFCs. 2. The Source BSS will command the UE to handover to the target eNodeB via the message PS Handover Command. The access system specific message to UE includes a transparent container including radio aspect parameters that the Target eNodeB has set-up in the preparation phase. 3. Void. 4. The UE moves to the E-UTRAN and performs access procedures toward Target eNodeB. 5. When the UE has got access to Target eNodeB it sends the message HO to E-UTRAN Complete. The UE shall implicitly derive the EPS bearers for which an E-RAB was not established from the PS Handover Command and deactivate them locally without an explicit NAS message at this step. 6. When the UE has successfully accessed the Target eNodeB, the Target eNodeB informs the Target MME by sending the message Handover Notify (TAI+ECGI). As a separate activity the Target eNodeB retrieves the UE E-UTRA capability information using the procedure for UE Radio Capability Handling (see clause 5.11.2). If Dual Connectivity is activated for the UE, the PSCell ID shall be included in the Handover Notify message. 7. Then the Target MME knows that the UE has arrived to the target side and Target MME informs the Source SGSN by sending the Forward Relocation Complete Notification (ISR Activated, Serving GW change) message. If indicated, ISR Activated indicates to the source SGSN that it shall maintain the UE's contexts and activate ISR, which is only possible when the S-GW is not changed. The Source SGSN shall also acknowledge that information. When the Forward Relocation Complete Notification message has been received and there is no longer any need for the SGSN to forward data, the SGSN stops data forwarding. A timer in source SGSN is started to supervise when resources in the Source Serving GW (for Serving GW relocation) shall be released. Upon receipt of the Forward Relocation Complete Acknowledge message the target MME starts a timer if the target MME applies indirect forwarding. 8. The Target MME will now complete the Handover procedure by informing the Serving GW (for Serving GW relocation this will be the Target Serving GW) that the Target MME is now responsible for all the EPS bearers the UE have established. This is performed in the message Modify Bearer Request (Cause, MME Tunnel Endpoint Identifier for Control Plane, EPS Bearer ID(s), MME Address for Control Plane, eNodeB Address(es) and TEID(s) for User Traffic for the accepted EPS bearers and RAT type, ISR Activated, User Location Information, PSCell ID) per PDN connection. As it is a mobility from GERAN, if the target MME supports location information change reporting, the target MME shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If the PDN GW requested User CSG information (determined from the UE context), the MME also includes the User CSG Information IE in this message. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. If the Serving GW is not relocated but the Serving Network has changed or if the MME has not received any old Serving Network information from the old SGSN, the MME includes the new Serving Network IE in this message. If indicated, ISR Activated indicates that ISR is activated, which is only possible when the S-GW was not changed. When the Modify Bearer Request does not indicate ISR Activated and S-GW is not changed, the S-GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the S-GW reserved. If the MME has received PSCell ID in step 6, it shall include it in Modify Bearer Request. The MME releases the non-accepted dedicated bearers by triggering the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME. If the default bearer of a PDN connection has not been accepted by the target eNodeB and there are other PDN connections active, the MME shall handle it in the same way as if all bearers of a PDN connection have not been accepted. The MME releases these PDN connections by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3. 9. The Serving GW (for Serving GW relocation this will be the Target Serving GW) informs the PDN GW(s) the change of, for example, for Serving GW relocation or the RAT type, that e.g. can be used for charging, by sending the message Modify Bearer Request per PDN connection. The S-GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if they are present in step 8. Serving Network should be included if it is received in step 8 or in step 4 in clause 5.5.2.4.2. For Serving GW relocation, the Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers and PDN Charging Pause Support Indication shall be included. The PDN GW must acknowledge the request with the message Modify Bearer Response (Charging Id, MSISDN, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function), etc.) to the Serving GW. If location information change reporting is required and supported in the target MME, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response. If PCC infrastructure is used, the PDN GW informs the PCRF about the change of, for example, the RAT type. If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB. The source Serving GW shall forward the "end marker" packets to the source SGSN. 10. The Serving GW (for Serving GW relocation this will be the Target Serving GW) acknowledges the user plane switch to the Target MME via the message Modify Bearer Response (Cause, Serving GW Tunnel Endpoint Identifier for Control Plane, Serving GW (for Serving GW relocation this will be the Target Serving GW) Address for Control Plane, Protocol Configuration Options, MS Info Change Reporting Action). At this stage the user plane path is established for all bearers between the UE, Target eNodeB, Serving GW (for Serving GW relocation this will be the Target Serving GW) and PDN GW. If the Serving GW does not change, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB. 11. When the timer at the source SGSN started in step 7 expires the Source SGSN will clean-up all its resources towards Source BSS by performing the BSS Packet Flow Delete procedure. 12. The UE initiates a Tracking Area Update procedure when one of the conditions listed in clause "Triggers for tracking area update" applies. The target MME knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target MME performs only a subset of the TA update procedure, specifically it excludes the context transfer procedures between source SGSN and target MME. If the Subscription Data received from the HSS (during the TAU in step 12) contains information that is necessary for the E-UTRAN to be aware of (e.g. a restriction in the UE's permission to use NR as a secondary RAT, Unlicensed Spectrum in the form of LAA/LWA/LWIP/NR-U (as specified in clause 4.3.30) or a combination of them), or an existing UE context in the MME indicates that the UE is not permitted to use NR as a secondary RAT, Unlicensed Spectrum or a combination of them and the MME has not provided this information to the target eNodeB during step 5 of the handover preparation phase, then the MME sends an updated Handover Restriction List in the Downlink NAS Transport message that it sends to E-UTRAN. If the UE is not allowed to use NR as Secondary RAT, the MME indicates that to the UE in TAU Accept message. 13. When the timer at the source SGSN started in step 7 expires and if the source SGSN received the Serving GW change indication in the Forward Relocation Response message, it deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication) messages to the Source Serving GW. The operation Indication flag is not set, that indicates to the Source Serving GW that the Source Serving GW shall not initiate a delete procedure towards the PDN GW. The Source Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR has been activated before this procedure, the cause indicates to the Source S-GW that the Source S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. 14. If indirect forwarding was used then the expiry of the timer at source SGSN started at step 7 triggers the source SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the S-GW to release the temporary resources used for indirect forwarding. 15. If indirect forwarding was used and the Serving GW is relocated, then the expiry of the timer at target MME started at step 6 triggers the target MME to send a Delete Indirect Data Forwarding Tunnel Request message to the target S-GW to release temporary resources used for indirect forwarding. | 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.4.3 |
3,758 | 17.6.8 Abort-Session-Answer Command | The Abort-Session-Answer (ASA) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 274 and the message flags’ ‘R’ bit clear, is sent in response to the ASR. The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. Message Format <ASA> ::= < Diameter Header: 274, PXY > < Session-Id > { Result-Code } { Origin-Host } { Origin-Realm } [ Origin-State-Id ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] * [ Redirected-Host ] [ Redirected-Host-Usage ] [ Redirect-Max-Cache-Time ] * [ Proxy-Info ] | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.6.8 |
3,759 | 4.16.13.1 AMF-initiated UE Policy Association Termination | The following case is considered for UE Policy Association Termination: 1. UE Deregistration from the network when the UE is not registered in another access type. 2. The mobility with change of AMF (e.g. new AMF is in different PLMN or new AMF in the same PLMN). 3. [Optional] 5GS to EPS mobility with N26 if the UE is not connected to the 5GC over a non-3GPP access in the same PLMN. In the non-roaming case, the H-PCF may interact with the CHF in HPLMN. Figure 4.16.13.1-1: AMF-initiated UE Policy Association Termination This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case, the V-PCF is not involved and the role of the H-PCF is performed by the PCF. For the roaming scenarios, the V PCF interacts with the AMF. The V PCF contacts the H-PCF to request removing UE Policy Association. 1. The AMF decides to terminate the UE Policy Association. 2. The AMF sends the Npcf_UEPolicyControl_Delete service operation including UE Policy Association ID to the (V-)PCF. 3. The (V-)PCF removes the policy context for the UE and replies to the AMF with an Acknowledgement including success or failure. The V-PCF may interact with the H-PCF. The (V-)PCF may unsubscribe to subscriber policy data changes with UDR by Nudr_DM_Unsubscribe (Subscription Correlation Id). The AMF removes the UE Policy Context. If the PCF has previously registered to the BSF as the PCF that is serving this UE, the PCF shall deregister from the BSF if no AM Policy Association for this UE exists anymore. This is performed by using the Nbsf_Management_Deregister service operation, providing the Binding Identifier that was obtained earlier from the BSF when performing the Nbsf_Management_Register service operation. Step 4 and Step 5 apply only to the roaming case. 4. The V-PCF sends the Npcf_UEPolicyControl_Delete service operation including UE Policy Association ID to the H-PCF. 5. The H-PCF removes the policy context for the UE and replies to the V-PCF with an Acknowledgement including success or failure. The H-PCF may unsubscribe to subscriber policy data changes with UDR by Nudr_DM_Unsubscribe (Subscription Correlation Id) for subscriber policy changes. In the non-roaming case, the PCF may unsubscribe to analytics from NWDAF. The H-PCF may invoke the procedure defined in clause 4.16.8 to unsubscribe to policy counter status reporting or to modify the subscription to policy counter status reporting (if remaining Policy association for this subscriber requires policy counter status reporting). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.13.1 |
3,760 | 5.3.4B.6 MT-EDT procedure for Control Plane CIoT EPS Optimization | The procedure is used by the network to initiate MT-EDT procedure if the UE and the network support Control Plane CIoT EPS Optimisation and there is single DL data transmission for the UE. Figure 5.3.4B.6-1: MT-EDT procedure for Control Plane CIoT EPS Optimization The call flow is the same as the Mobile Terminated Data Transport procedure documented in clause 5.3.4B.3 procedure for Control Plane CIoT EPS Optimisation with the following changes: In step2, the Serving-GW may send the downlink data size to the MME if the downlink data is applicable for Control Plane CIoT EPS Optimisation and MT-EDT is applicable for this PDN Connection. In step3, if MT-EDT is applicable for the PDN Connection, the MME may include the downlink data size in the Paging message to assist eNodeB to use MT-EDT. In step 4, if data size is included in the Paging message from MME, the eNodeB may decide to use MT-EDT by adding a MT-EDT indication in the Paging message to the UE. In step 5, the UE, upon reception of MT-EDT indication in the Paging message, triggers MO-EDT by sending the RRCEarlyDataRequest message as defined 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]. In step 13, if downlink data is received from the S-GW, the MME may include End Indication for no further data in the S1-AP message including the Downlink data encapsulated in NAS PDU. | 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.3.4B.6 |
3,761 | 5.2.5.1 Link adaptation | Link adaptation (AMC: adaptive modulation and coding) with various modulation schemes and channel coding rates is applied to the PDSCH. The same coding and modulation is applied to all groups of resource blocks belonging to the same L2 PDU scheduled to one user within one transmission duration and within a MIMO codeword. For channel state estimation purposes, the UE may be configured to measure CSI-RS and estimate the downlink channel state based on the CSI-RS measurements. The UE feeds the estimated channel state back to the gNB to be used in link adaptation. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.5.1 |
3,762 | – FeatureSetDownlinkPerCC-Id | The IE FeatureSetDownlinkPerCC-Id identifies a set of features applicable to one carrier of a feature set. The FeatureSetDownlinkPerCC-Id of a FeatureSetDownlinkPerCC is the index position of the FeatureSetDownlinkPerCC in the featureSetsDownlinkPerCC. The first element in the list is referred to by FeatureSetDownlinkPerCC-Id = 1, and so on. FeatureSetDownlinkPerCC-Id information element -- ASN1START -- TAG-FEATURESETDOWNLINKPERCC-ID-START FeatureSetDownlinkPerCC-Id ::= INTEGER (1..maxPerCC-FeatureSets) -- TAG-FEATURESETDOWNLINKPERCC-ID-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,763 | 5.2.5.3.6 Npcf_PolicyAuthorization_Subscribe service operation | Service operation name: Npcf_PolicyAuthorization_Subscribe Description: provided by the PCF for NF consumers to explicitly subscribe the notification of events. Inputs, Required: (Set of) Event ID(s) as specified in Npcf_PolicyAuthorization_Notify service operation, target of PCF event reporting (defined below), NF ID, Event Reporting Information defined in Table 4.15.1-1 (only the Event Reporting mode and the immediate reporting flag when applicable), Notification Target Address (+ Notification Correlation ID). The target of PCF event reporting the subscription for an individual AF session: An UE IP address (IPv4 address or IPv6 prefix) optionally together with a (DNN, S-NSSAI) or with a UE ID (SUPI or GPSI). Inputs, Optional: Event Filter, Subscription Correlation ID (in the case of modification of the event subscription), Notification Target Address for PMIC/UMIC UPF event, Correlation ID for PMIC/UMIC UPF event. Outputs, Required: When the subscription is accepted: Subscription Correlation ID. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.3.6 |
3,764 | 8.2.6.16 EPS NAS message container | The UE operating in the single-registration mode shall include this information element as specified in subclause 5.5.1.3.2 if the UE performs mobility from S1 mode to N1 mode in 5GMM-IDLE mode. The content of this message container is the complete integrity protected TRACKING AREA UPATE REQUEST message, using EPS security context. The UE performing initial registration shall include this information element if a) the UE: 1) was previously registered in S1 mode before entering state EMM-DEREGISTERED; and 2) has received an "interworking without N26 interface not supported" indication from the network; and b) EPS security context and a valid 4G-GUTI are available. The content of this message container is the complete integrity protected ATTACH REQUEST message, using EPS security context. | 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 | 8.2.6.16 |
3,765 | 5.46.2 Member UE selection assistance functionality for application operation | 5G System may support Member UE selection assistance functionality to assist the AF to select member UE(s) that can be used in application operations such as AI/ML based applications (e.g. Federated Learning) as specified in clause 5.46.1 according to the AF's inputs. The Member UE selection assistance functionality shall be hosted by NEF, and the features of the Member UE selection assistance functionality hosted by the NEF include (see clause 4.15.13 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] for details of Member UE selection procedures): - Receiving a request from the AF that shall include a list of target member UE(s) (which may not necessarily be a part of the subsequent updated request), optionally (a) time window(s), and one or more filtering criteria as specified in Table 4.15.13.2-1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] (e.g. UE current location, UE historical location, UE direction, UE separation distance, QoS requirements, DNN, preferred access/RAT type, Desired end-to-end data volume transfer time performance, or Service Experience). - Referring to the filtering criteria provided by the AF and then interacting with 5GC NFs using existing services in order to have the corresponding data for all the UEs in the list of target member UE from relevant 5GC NFs (e.g. PCF, NWDAF, AMF, SMF) to derive the list(s) of candidate UE(s) (i.e. UE(s) among the list of target member UE(s) provided by the AF) which fulfil the filtering criteria. - Providing the AF with the Member UE selection assistance information, including one or more lists of candidate UE(s), and optionally other additional information (e.g. one or more recommended time window(s) for performing the application operation, QoS of each target UE, UE(s) location, Access/RAT type, or Service Experience). NEF may also provide the number of UEs per each filtering criterion that do not fulfil the corresponding filtering criterion. The Member UE selection assistance information provided by the NEF may be used by the AF to select member UE(s) used in application AI/ML operation. (See clause 5.2.6.32 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] for details of parameters). NOTE: The AF can decide whether to use the Member UE selection assistance functionality provided by NEF. Without using the Member UE selection assistance functionality, AF in either trusted or untrusted domain can select the Member UE(s) for e.g. participating in federating learning operation, by collecting the corresponding data using network exposure information as described in clause 4.15 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], e.g. UE location reporting from the AMF, user plane information from the UPF and network data analytics from NWDAF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.46.2 |
3,766 | 8.21 User Location Information (ULI) | User Location Information (ULI) is a extendable IE that is coded as depicted in Figure 8.21-1. The CGI, SAI, RAI, TAI, ECGI and LAI identity types are defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. Figure 8.21-1: User Location Information The ULI IE shall contain only one identity of the same type (e.g. more than one CGI cannot be included), but ULI IE may contain more than one identity of a different type (e.g. ECGI and TAI). The flags LAI, ECGI, TAI, RAI, SAI , CGI, Macro eNodeB ID, and Extended Macro eNodeB ID in octet 5 indicate if the corresponding type shall be present in a respective field or not. If one of these flags is set to "0", the corresponding field shall not be present at all. If more than one identity of different type is present, then they shall be sorted in the following order: CGI, SAI, RAI, TAI, ECGI, LAI, Macro eNodeB ID, Extended Macro eNodeB ID. Only one of the Macro eNodeB ID or Extended Macro eNodeB ID shall be present in the ULI IE. The following clauses specify the coding of the fields representing different identities. For each identity, if an Administration decides to include only two digits in the MNC, then "MNC digit 3" field of corresponding location shall be coded as "1111". | 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.21 |
3,767 | 12.3.1 Principles of overload control | The stage 2 requirements on GTP-C overload control are defined in clause 4.3.7.1a.2 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and clause 5.3.6.1a of 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35]. The high level principles are summarized below: a) Overload control is an optional feature; b) a GTP-C entity may signal its overload to its GTP-C peers by including Overload Control Information in GTP-C signalling which provides guidance to the receiving GTP-C entity to decide actions which lead to signalling traffic mitigation towards the sender of the information; c) the Overload Control Information may provide the overload information of a GTP-C entity, e.g. a PGW, or a specific APN(s) associated with the GTP-C entity; d) an MME/S4-SGSN may signal an overload to the PGW, via the SGW. An SGW may signal an overload to the MME/S4-SGSN and to the PGW. A PGW may signal an overload to the MME/S4-SGSN, via the SGW. For non-3GPP access based interfaces, a PGW may signal an overload to the ePDG and the TWAN; the ePDG and the TWAN may signal an overload to the PGW. NOTE 1: An MME/S4-SGSN will not signal an overload to the SGW (i.e. the SGW will not perform overload control towards the MME/S4-SGSN), as this is redundant with DDN throttling (see clause 12.3.3). e) the overload control feature should continue to allow for preferential treatment of priority users (eMPS) and emergency services; f) the Overload Control Information is piggybacked in GTP control plane request or response messages such that the exchange of the Overload Control Information does not trigger extra signalling; NOTE 2: The inclusion of Overload Control Information in existing messages means that the frequency increases as the signalling load increases, thus allowing faster feedback and better regulation. g) the computation and transfer of the Overload Control Information shall not add significant additional load to the GTP-C entity itself and to its corresponding peer GTP-C entities. The calculation of Overload Control Information should not severely impact the resource utilization of the GTP-C entity, especially considering the overload situation; h) clause 4.3.7.1a.2 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and clause 4.5 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45] provides examples of various potential overload mitigation actions based on the reception of the overload related information exchanged between GTP-C entities, for 3GPP access based interfaces and non-3GPP access based interfaces, respectively. However, the exact internal processing logics of a GTP-C entity will not be standardized; i) for the inter-PLMN case, local configuration may restrict the exchange and use of Overload Control Information across PLMNs; j) the GTP-C entity may decide to send different values of Overload Control Information on inter-network (roaming) and on intra-network (non-roaming) interfaces based on local configuration, i.e. the values sent on intra-network interfaces may differ from the values sent on inter-network interfaces. However, on intra-network interfaces, the GTP-C entity should send the same values between the 3GPP and non-3GPP access based interfaces; | 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.3.1 |
3,768 | – FR2-2-AccessParamsPerBand | The IE FR2-2-AccessParamsPerBand is used to convey FR2-2 related parameters specific for a certain frequency band (not per feature set or band combination). FR2-2-AccessParamsPerBand information element -- ASN1START -- TAG-FR2-2-ACCESSPARAMSPERBAND-START FR2-2-AccessParamsPerBand-r17 ::= SEQUENCE { -- R1 24-1: Basic FR2-2 DL support dl-FR2-2-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-1a: Basic FR2-2 UL support ul-FR2-2-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-2: 120KHz SSB support for initial access in FR2-2 initialAccessSSB-120kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-1b: Wideband PRACH for 120 kHz in FR2-2 widebandPRACH-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-1c: Multi-RB support PUCCH format 0/1/4 for 120 kHz in FR2-2 multiRB-PUCCH-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-1d: Multiple PDSCH scheduling by single DCI for 120kHz in FR2-2 multiPDSCH-SingleDCI-FR2-2-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-1e: Multiple PUSCH scheduling by single DCI for 120kHz in FR2-2 multiPUSCH-SingleDCI-FR2-2-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-4: 480KHz SCS support for DL dl-FR2-2-SCS-480kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-4a: 480KHz SCS support for UL ul-FR2-2-SCS-480kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-3: 480KHz SSB support for initial access in FR2-2 initialAccessSSB-480kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-4b: Wideband PRACH for 480 kHz in FR2-2 widebandPRACH-SCS-480kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-4c: Multi-RB support PUCCH format 0/1/4 for 480 kHz in FR2-2 multiRB-PUCCH-SCS-480kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-4f: Enhanced PDCCH monitoring for 480KHz in FR2-2 enhancedPDCCH-monitoringSCS-480kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-5: 960KHz SCS support for DL dl-FR2-2-SCS-960kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-5a: 960KHz SCS support for UL ul-FR2-2-SCS-960kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-5c: Multi-RB support PUCCH format 0/1/4 for 960 kHz in FR2-2 multiRB-PUCCH-SCS-960kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-5f: Enhanced PDCCH monitoring for 960KHz in FR2-2 enhancedPDCCH-monitoringSCS-960kHz-r17 SEQUENCE { pdcch-monitoring4-1-r17 ENUMERATED {supported} OPTIONAL, pdcch-monitoring4-2-r17 ENUMERATED {supported} OPTIONAL, pdcch-monitoring8-4-r17 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 24-6: Type 1 channel access procedure in uplink for FR2-2 with shared spectrum channel access type1-ChannelAccess-FR2-2-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-7: Type 2 channel access procedure in uplink for FR2-2 with shared spectrum channel access type2-ChannelAccess-FR2-2-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-10: Reduced beam switching time delay reduced-BeamSwitchTiming-FR2-2-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-8: 32 DL HARQ processes for FR 2-2 support32-DL-HARQ-ProcessPerSCS-r17 SEQUENCE { scs-120kHz-r17 ENUMERATED {supported} OPTIONAL, scs-480kHz-r17 ENUMERATED {supported} OPTIONAL, scs-960kHz-r17 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 24-9: 32 UL HARQ processes for FR 2-2 support32-UL-HARQ-ProcessPerSCS-r17 SEQUENCE { scs-120kHz-r17 ENUMERATED {supported} OPTIONAL, scs-480kHz-r17 ENUMERATED {supported} OPTIONAL, scs-960kHz-r17 ENUMERATED {supported} OPTIONAL } OPTIONAL, ..., [[ -- R4 15-1: 64QAM for PUSCH for FR2-2 modulation64-QAM-PUSCH-FR2-2-r17 ENUMERATED {supported} OPTIONAL ]] } -- TAG-FR2-2-ACCESSPARAMSPERBAND-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,769 | 4.3.1.4.6 Successful outgoing inter-frequency handovers – non gap-assisted measurement | This measurement provides the number of successful outgoing inter-frequency handovers, when measurement gaps are not used [12]. CC. Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source) eNB/RN, indicating a successful outgoing intra-eNB/RN inter-frequency handover when measurement gaps are not used (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), or receipt at the source eNB/RN of UE CONTEXT RELEASE [10] over the X2 from the target eNB or from DeNB following a successful inter-frequency handover when measurement gaps are not used, or if handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND[9] at the source eNB following a successful inter-frequency handover when measurement gaps are not used. A single integer value. HO.InterFreqNoMeasGapOutSucc EUtranCellFDD EUtranCellTDD 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.4.6 |
3,770 | I.9.2.3 Primary authentication using DCS | When the primary authentication is performed between the UE and the DCS, the authentication requirements and procedures defined in clause I.2 for Credential Holder shall apply with the DCS taking the role of the Credentials Holder. When the DCS uses AAA Server for primary authentication, AUSF directly selects the NSSAAF as specified in 23.501 [2]. In this case, the UDM is not involved in the procedure defined in clause I.2.2.2.2, and the step 3 to step 5 shall be skipped. When 5G AKA or EAP-AKA’ is used, the DCS shall act as a AUSF/UDM. The choice of primary authentication method used between the UE and the DCS is left to the decision of the DCS. When the primary authentication is performed between the UE and the DCS via the AUSF using EAP-TTLS, Annex U can be used. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.9.2.3 |
3,771 | C.3.2 Profile 2: management of sequence numbers which are not time-based | Generation of sequence numbers: This follows the scheme for the generation of sequence numbers specified in Annex C.1.1.2. The following parameter values are suggested for reference: Length of in bits = 5. Start conditions: SQNHE = 0 for all users. Verification of sequence numbers in the USIM: Length of the array: a = 32 Protection against wrap around: Choose = 228. Choosing = 228 means that an attack to force the counter in the USIM to wrap around would require at least SEQmax/ = 215 > 32.000 successful authentications (cf. note 6 of C.2.3). Note 7 of Annex C.2.3 does not apply. Age limit for sequence numbers: There is no clock here. So, the “age” limit would be interpreted as the maximum allowed difference between SQNMS (see section 6.3) and the sequence number received. The use of such a limit is optional. The choice of a value for the parameter L affects only the USIM. It has no impact on the choice of other parameters and it entirely up to the operator, depending on his security policy. Therefore no particular value is suggested here. User anonymity: the value of SQN may allow to trace the user over longer periods. If this is a concern then SQN has to be concealed by an anonymity key as specified in section 6.3. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | C.3.2 |
3,772 | 5.3.6.2.2 Mobile terminating multimedia call | At call setup the required call type, 3G-324M, is indicated by the network in the SETUP message, with the bearer capability IE parameter. Other Rate Adaption set to 'H.223 and H.245'. ITC is either '3,1 kHz audio ex PLMN' or 'UDI/RDI'. For analogue multimedia, if the network supports fallback to speech and the subscriber has subscription to speech, two bearer capability IEs, multimedia first and speech as the second BC are included in the SETUP message. The network shall indicate fallback to speech by these two BC IEs and the associated Repeat Indicator set to "support of fallback". For UDI/RDI multimedia, if the network supports fallback and service change, and the subscriber has subscription to speech, two bearer capability IEs, with the first BC as the preferred service are included in the SETUP message. The network shall indicate service change and fallback by these two BC IEs and the associated Repeat Indicator set to "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 capability IE(s) may (in the case of the single numbering scheme) be missing from the SETUP message. The bearer compatibility checking in the MS is according to subclause 5.3.4.2.2. The MS shall indicate the supported call type(s) in the CALL CONFIRMED message, which is the acknowledgement to SETUP. If the network offered an analogue multimedia call with fallback to speech, or a UDI/RDI multimedia call with fallback and service change, the MS has the following options for the inclusion of bearer capability IEs in the CALL CONFIRMED message: - if the MS/user accepts the offered analogue multimedia call and supports fallback to speech, both multimedia and speech bearer capability IEs shall be included; - if the MS/user accepts the offered UDI/RDI multimedia call, and supports fallback and service change, both multimedia and speech bearer capability IEs shall be included. The order of the BC IEs determines the preferred service, and the MS/user may reverse the order of these IEs; - if the MS/user accepts the offered multimedia call, but does not support fallback or service change, only a multimedia bearer capability IE shall be included; - if the MS/user wishes a speech (only) call a speech bearer capability IE is included; - for a UDI/RDI multimedia call, if the MS/user accepts the offered speech call and supports service change, both speech and multimedia bearer capability IEs shall be included. The order of the BC IEs determines the preferred service, and the MS/user may reverse the order of these IEs. If the network offered a multimedia call only, and the MS/user accepts the call, the MS shall always include a single multimedia bearer capability IE in the CALL CONFIRMED message. If the SETUP contained no bearer capability IE the network shall perform compatibility checking of the CALL CONFIRMED message in the same way as the compatibility checking of the SETUP message in the mobile originating call case, described in subclause 5.3.6.2.1. | 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.2 |
3,773 | 5.5.2.4.2 Preparation phase | Figure 5.5.2.4.2-1: GERAN A/Gb mode to E-UTRAN inter RAT HO, preparation phase 1. The source access system, Source BSS, 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 BSS, BSSGP PFC tunnel(s) between source BSS and source SGSN, GTP tunnel(s) between Source SGSN, 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 BSS sends the message PS handover Required (TLLI, Cause, Source Cell Identifier, Target eNodeB Identifier, Source eNodeB to Target eNodeB Transparent Container and active PFCs list) to Source SGSN to request the CN to establish resources in the Target eNodeB, Target MME and the Serving GW. NOTE 2: In contrast to most inter-RAT handover preparation phases, this Source to Target Transparent Container does not contain the UE's target RAT radio capabilities. 3. The Source SGSN determines from the 'Target eNodeB Identifier' IE that the type of handover is IRAT PS 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 message Forward Relocation Request (IMSI, Target Identification, MM Context, PDN Connections, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control plane, Source to Target Transparent Container, RAN Cause, Packet Flow ID, SNDCP XID parameters, LLC XID parameters, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, ISR Supported, Serving Network) to the target MME. 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. If indicated, the information ISR Supported indicates that the source SGSN and associated Serving GW are capable to activate ISR for the UE. 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 established in the source system. The EPS Bearer Contexts indicate the PFIs and the XID parameters related to those EPS Bearer Contexts, and the uplink Tunnel endpoint parameters of the Serving GW. The old Serving Network is sent to target MME to support the target MME to resolve if Serving Network is changed. In network sharing scenarios Serving Network denotes the serving core network. The RAN Cause includes the value from the Cause IE received from the source BSS. Source to Target Transparent Container includes the value from the Source eNodeB to Target eNodeB Transparent Container received from the source BSS. The MM context includes information on the EPS Bearer context(s). If none of the UE's EPS Bearers can be supported by the selected target MME, the source SGSN rejects the handover attempt by sending a PS Handover Required Negative Acknowledge (Cause) message to the Source BSS. NOTE 3: If the handover is successful, the source SGSN will signal to the SGW and/or SCEF to release any non-included EPS Bearers after step 6 of the Execution procedure. The non-included bearers are locally released by the UE following the Bearer Context Status synchronisation that occurs during the Tracking Area Update at step 12 of the Execution procedure. Prioritization of EPS Bearer Contexts is performed by the target core network node. 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 MM context contains security related information, e.g. supported ciphering algorithms as described in TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. Handling of security keys is described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]. For the EPS Bearer Context with traffic class equals 'Background', the source SGSN shall indicate via the Activity Status Indicator IE that radio bearers shall be established on the target side. 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. 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 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 will request the Target eNodeB to establish the Bearer(s) by sending the message Handover Request (UE Identifier, S1AP Cause, Integrity protection information (i.e. IK and allowed Integrity Protection algorithms), Encryption information (i.e. CK and allowed Ciphering algorithms), EPS Bearers to be setup list, Source to Target Transparent Container, Handover Restriction List). The Target MME ignores any Activity Status Indicator within an EPS Bearer Context and requests the eNodeB to allocate resources for all EPS Bearer Contexts received from the source side. The S1AP Cause includes the value from the RAN Cause IE received from the source SGSN. 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. Handover Restriction List is sent if it is available in the Target MME; it is described in clause 4.3.5.7. 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 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 ciphering and integrity protection keys will be sent transparently from the target eNodeB to the UE in the Target to Source Transparent Container, and in the message PS Handover Command from source BSS 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]. 5a. The Target eNodeB allocates the request resources and returns the applicable parameters to the Target MME in the message Handover Request Acknowledge (Target to Source Transparent Container, S1AP Cause, EPS Bearers setup list, EPS Bearers failed to setup list). 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. 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(es) and 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 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 PFCs, 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 RAN Cause includes the value from the S1AP Cause IE received from the target eNodeB. The Target to Source Transparent Container includes the value from the Target to Source Transparent Container received from the target eNodeB. If 'Direct Forwarding' applies or if 'Indirect Forwarding' but no relocation of Serving GW applies, then the IEs 'Address(es) and TEID(s) for Data Forwarding' contain the 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' contain the DL GTP-U tunnel endpoint parameters to the 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 packet 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.4.2 |
3,774 | – LTM-Candidate | The IE LTM-Candidate concerns a LTM candidate configuration to add or modify. LTM-Candidate information element -- ASN1START -- TAG-LTM-CANDIDATE-START LTM-Candidate-r18 ::= SEQUENCE { ltm-CandidateId-r18 LTM-CandidateId-r18, ltm-CandidatePCI-r18 PhysCellId, ltm-SSB-Config-r18 LTM-SSB-Config-r18 OPTIONAL, -- Need M ltm-CandidateConfig-r18 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Need M ltm-ConfigComplete-r18 ENUMERATED {true} OPTIONAL, -- Need R ltm-EarlyUL-SyncConfig-r18 SetupRelease { EarlyUL-SyncConfig-r18 } OPTIONAL, -- Need M ltm-EarlyUL-SyncConfigSUL-r18 SetupRelease { EarlyUL-SyncConfig-r18 } OPTIONAL, -- Need M ltm-NoResetID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Need M ltm-DL-OrJointTCI-StateToAddModList-r18 SEQUENCE (SIZE (1..maxNrofCandidateTCI-State-r18)) OF CandidateTCI-State-r18 OPTIONAL, -- Need N ltm-DL-OrJointTCI-StateToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofCandidateTCI-State-r18)) OF TCI-StateId OPTIONAL, -- Need N ltm-UL-TCI-StatesToAddModList-r18 SEQUENCE (SIZE (1..maxNrofCandidateUL-TCI-r18)) OF CandidateTCI-UL-State-r18 OPTIONAL, -- Need N ltm-UL-TCI-StatesToReleaseList-r18 SEQUENCE (SIZE (1.. maxNrofCandidateUL-TCI-r18)) OF TCI-UL-StateId-r17 OPTIONAL, -- Need N ltm-nzp-CSI-RS-ResourceToAddModList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource OPTIONAL, -- Need N ltm-nzp-CSI-RS-ResourceToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId OPTIONAL, -- Need N ltm-nzp-CSI-RS-ResourceSetToAddModList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet OPTIONAL, -- Need N ltm-nzp-CSI-RS-ResourceSetToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need N pathlossReferenceRS-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-r17 OPTIONAL, -- Need N pathlossReferenceRS-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-Id-r17 OPTIONAL, -- Need N ltm-UE-MeasuredTA-ID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Need M ... } LTM-SSB-Config-r18 ::= SEQUENCE { ssbFrequency-r18 ARFCN-ValueNR, subcarrierSpacing-r18 SubcarrierSpacing, ssb-Periodicity-r18 ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1} OPTIONAL, -- Need R ssb-PositionsInBurst-r18 CHOICE { shortBitmap BIT STRING (SIZE (4)), mediumBitmap BIT STRING (SIZE (8)), longBitmap BIT STRING (SIZE (64)) } OPTIONAL, -- Need R ss-PBCH-BlockPower-r18 INTEGER (-60..50) OPTIONAL, -- Need R ... } -- TAG-LTM-CANDIDATE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,775 | 12.2 Mutual authentication | For authentication between NEF and an AF that resides outside the 3GPP operator domain, mutual authentication based on client and server certificates shall be performed between the NEF and AF using TLS. Certificate based authentication shall follow the profiles given in 3GPP TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5], clause 6.1.3a. The identities in the end entity certificates shall be used for authentication and policy checks. The structure of the PKI used for the certificate is out of scope of the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 12.2 |
3,776 | 5.4.4.2.3 Clearing when tones/announcements are not provided and the network does not indicate that "CCBS activation is possible" | When in-band tones and announcements are not provided, and, the network does not wish to indicate in the Allowed Actions IE that "CCBS is possible", the call control entity of the network shall initiate call clearing by stopping all running call control timers, sending a DISCONNECT message without progress indicator, either without the Allowed Actions IE or with the Allowed Actions IE indicating that "CCBS is not possible", starting timer T305 and entering the "disconnect indication" state. 5.4.4.2.3.1 Receipt of a DISCONNECT message The call control entity of the mobile station in any state except the "null" state, the "disconnect indication" state, and the "release request" state, shall, upon the receipt of a DISCONNECT message either without progress indicator information element or with progress indicator different from #8, and, either without the Allowed Actions IE or with the Allowed Actions IE indicating that "CCBS is not possible": - stop all running call control timers; - send a RELEASE message; - start timer T308; and - enter the "release request" state. 5.4.4.2.3.2 Abnormal cases The call control entity of the network, having entered the "disconnect indication", shall upon expiry of timer T305: send a RELEASE message to the mobile station with the cause number originally contained in the DISCONNECT message; start timer T308; and enter the "release request" state. | 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.4.4.2.3 |
3,777 | 6.4.3.1 NAS input parameters to integrity algorithm | The input parameters to the NAS 128-bit integrity algorithms as described in Annex D shall be set as follows. The KEY input shall be equal to the KNASint key. The BEARER input shall be equal to the NAS connection identifier. The DIRECTION bit shall be set to 0 for uplink and 1 for downlink. The COUNT input shall be constructed as follows: COUNT := 0x00 || NAS COUNT Where NAS COUNT is the 24-bit NAS UL COUNT or the 24-bit NAS DL COUNT value, depending on the direction, that is associated to the current NAS connection identified by the value used to form the BEARER input. A NAS COUNT shall be constructed as follows: NAS COUNT := NAS OVERFLOW || NAS SQN Where - NAS OVERFLOW is a 16-bit value which is incremented each time the NAS SQN is incremented from the maximum value. - NAS SQN is the 8-bit sequence number carried within each NAS message. The use and mode of operation of the 128-bit integrity algorithms are specified in Annex D. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.3.1 |
3,778 | 5.17.5.2.2 Interworking without N26 interface | In addition to the interworking principles documented in clause 5.17.2.3, the additional behaviour at EPS to 5GS mobility in clause 5.17.5.2.1 also applies. When SCEF+NEF performs the procedure of monitoring via the AMF as described in clause 4.15.3.2.4 ("Exposure with bulk subscription") in TS 23.502[ Procedures for the 5G System (5GS) ] [3], if the AMF determines the interworking without N26 interface is supported, during mobility from 5GS to EPS, the AMF shall subscribe on behalf of SCEF+NEF for UDM+HSS notification of MME ID as described in clause 7.1.2 to trigger the SCEF+NEF to configure the monitoring request to the new MME. For single-registration mode, when UE's mobility from 5GS to EPS happens and Serving MME sends Update Location Request to the UDM+HSS, the UDM+HSS provides Serving MME ID to the SCEF+NEF which is the notification endpoint based on the subscription request from AMF. Then the SCEF+NEF performs the procedure of configuring monitoring via the MME for the same Monitoring Events as described in clause 5.6.2.1 of TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [36]. When SCEF+NEF performs the procedure of monitoring via the UDM+HSS as described in clause 4.15.3.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], when UE's mobility between 5GS and EPS happens, the UDM+HSS performs the procedure of configuring monitoring at the MME as described in clause 5.6.1.1 of TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [36] and at the AMF as described in clause 4.15.3.2.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.5.2.2 |
3,779 | 5.5.4.4 Event A3 (Neighbour becomes offset better than SpCell) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled; 1> use the SpCell for Mp, Ofp and Ocp. NOTE 1: The cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this event which may be different from the NR SpCell measObjectNR. Inequality A3-1 (Entering condition) Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off Inequality A3-2 (Leaving condition) Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off The variables in the formula are defined as follows: Mn is the measurement result of the neighbouring cell, not taking into account any offsets. Ofn is the measurement object specific offset of the reference signal of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell). Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell, or cellIndividualOffset as defined within reportConfigNR), and set to zero if not configured for the neighbour cell. Mp is the measurement result of the SpCell, not taking into account any offsets. Ofp is the measurement object specific offset of the SpCell (i.e. offsetMO as defined within measObjectNR corresponding to the SpCell). Ocp is the cell specific offset of the SpCell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event). Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigNR for this event). Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB. NOTE 2: The definition of Event A3 also applies to CondEvent A3. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.4 |
3,780 | 8.5.2.2.5 Enhanced Downlink Control Channel Performance Requirement Type A - 2 Tx Antenna Ports with Colliding CRS Dominant Interferer | For the parameters specified in Table 8.5.2-1 and Table 8.5.2.2.5-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.2.2.5-2. The purpose of this test is to verify the PHICH performance with 2 transmit antennas when the serving cell PHICH transmission is interfered by two interfering cells with the dominant interferer having the colliding CRS pattern and applying interference model defined in clause B.7.1. In Table 8.5.2.2.5-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.5.2.2.5-1: Test Parameters for PHICH Table 8.5.2.2.5-2: Minimum performance PHICH for Enhanced Downlink Control Channel Performance Requirement Type A | 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.5.2.2.5 |
3,781 | 5.3.4 Charging data correlation 5.3.4.0 General | The charging data correlation combines charging events generated by CTF while they are belong to the same bearer / session / service resource usage. The correlation provides an association of charging information for the mobile subscriber’s resource usage. The correlation is based on specific access network charging identifier: - Circuit Switched domain: MSC address and Call Reference Number; - Packet Switched domain: P-GW address and EPC Charging ID; - 5G Data connectivity domain: 5GC Charging ID; - Fixed Broadband Access: Multimedia Charging ID; - IM Subsystem: IMS Charging Identifier. The charging information has to be aggregate for the same charging session and correlate for the same service. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.3.4 |
3,782 | 12.4 RNC Identifier | An RNC node is uniquely identified by its RNC Identifier (RNC-Id). The RNC-Id of an RNC is used in the UTRAN, in a GERAN which is operating in GERAN Iu mode and between them. A BSC which is part of a GERAN operating in Iu mode is uniquely identified by its RNC Identifier (RNC-Id). The RNC-Id of a BSC is used in a GERAN which is operating in GERAN Iu mode, in the UTRAN and between them. RNC-Id together with the PLMN identifier globally identifies the RNC. The RNC-Id on its own or the RNC-Id together with the PLMN-Id is used as the RNC identifier in the UTRAN Iub, Iur and Iu interfaces. The SRNC-Id is the RNC-Id of the SRNC. The C-RNC-Id is the RNC-Id of the controlling RNC. The D-RNC-Id is the RNC Id of the drift RNC. - Global RNC-Id = PLMN-Id || RNC-Id The RNC-Id is defined by the operator, and set in the RNC via O&M For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [17]. For the usage of this identifier on Iur-g, see 3GPP TS 43.130[ None ] [43]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 12.4 |
3,783 | 5.5.2.10 Reference signal measurement timing configuration | The UE shall setup the first SS/PBCH block measurement timing configuration (SMTC) in accordance with the received periodicityAndOffset parameter (providing Periodicity and Offset value for the following condition) in the smtc1 configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the following condition: SFN mod T = (FLOOR (Offset/10)); if the Periodicity is larger than sf5: subframe = Offset mod 10; else: subframe = Offset or (Offset +5); with T = CEIL(Periodicity/10). If smtc2 is present, for cells indicated in the pci-List parameter in smtc2 in the same MeasObjectNR, the UE shall setup an additional SS/PBCH block measurement timing configuration (SMTC) in accordance with the received periodicity parameter in the smtc2 configuration and use the Offset (derived from parameter periodicityAndOffset) and duration parameter from the smtc1 configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the above condition. If smtc2-LP is present, for cells indicated in the pci-List parameter in smtc2-LP in the same frequency (for intra frequency cell reselection) or different frequency (for inter frequency cell reselection), the UE shall setup an additional SS/PBCH block measurement timing configuration (SMTC) in accordance with the received periodicity parameter in the smtc2-LP configuration and use the Offset (derived from parameter periodicityAndOffset) and duration parameter from the smtc configuration for that frequency. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell or serving cell (for cell reselection) meeting the above condition. If smtc3list is present, for cells indicated in the pci-List parameter in each SSB-MTC3 element of the list in the same MeasObjectNR, the IAB-MT shall setup an additional SS block measurement timing configuration in accordance with the received periodicityAndOffset parameter (using same condition as smtc1 to identify the SFN and the subframe for SMTC occasion) in each SSB-MTC3 configuration and use the duration and ssb-ToMeasure parameters from each SSB-MTC3 configuration. If smtc4list is present, for cells indicated in the pci-List parameter in each SSB-MTC4 element of the list in the same MeasObjectNR, the UE shall setup an additional SS/PBCH block measurement timing configuration (SMTC) in accordance with the received offset parameter in each SSB-MTC4 configuration and use the duration parameter and periodicity (derived from parameter periodicityAndOffset) from the smtc1 configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the above condition. On the indicated ssbFrequency, the UE shall not consider SS/PBCH block transmission in subframes outside the SMTC occasion for RRM measurements based on SS/PBCH blocks and for RRM measurements based on CSI-RS except for SFTD measurement (see TS 38.133[ NR; Requirements for support of radio resource management ] [14], clause 9.3.8). | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.10 |
3,784 | 9.5.1.1 FDD | The minimum performance requirement in Table 9.5.1.1-2 is defined as a) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be ≥ ; b) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 2 shall be ≥ ; For the parameters specified in Table 9.5.1.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.5.1.1-2. Table 9.5.1.1-1: RI Test (FDD) Table 9.5.1.1-2: Minimum requirement (FDD) | 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 | 9.5.1.1 |
3,785 | 5.3.8.4 HSS-initiated Detach procedure | The HSS-Initiated Detach procedure is initiated by the HSS. The HSS uses this procedure for operator-determined purposes to request the removal of a subscriber's MM and EPS bearer at the MME and also at the SGSN if both an MME and an SGSN are registered in the HSS. For UEs with emergency EPS bearers, the MME/SGSN shall not initiate detach procedure. Instead the MME/SGSN shall deactivate all the non-emergency PDN connection. If the HSS-Initiated Detach procedure is initiated, and UE is RLOS attached, the MME shall not initiate detach procedure. NOTE 1: HSS-initiated Detach can happen for a UE that camps on a cell in limited state due to UE moving to a forbidden area performs RLOS attach and the MME does not perform Purge procedure for the UE towards the HSS (as specified in clause 5.3.9.3). For subscription change, e.g. RAT restrictions to disallow one of the RATs, the Insert Subscription Data procedure shall be used towards the MME, and also towards the SGSN if both an MME and an SGSN are registered in the HSS. This procedure is not applied if a Cancel Location is sent to the MME or the SGSN with a cause other than Subscription Withdrawn. The HSS-Initiated Detach Procedure is illustrated in Figure 5.3.8.4-1. Figure 5.3.8.4-1: HSS-Initiated Detach Procedure NOTE 2: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 4, 5 and 6 concern GTP based S5/S8. NOTE 3: Procedure steps (B) are used by the procedure steps (F) in clause 5.3.2.1. NOTE 4: The steps below apply for an S4-SGSN. For Gn/Gp SGSN, the procedure specified in clause 6.6.2.2. of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] applies for the SGSN. 1. If the HSS wants to request the immediate deletion of a subscriber's MM contexts and EPS Bearers, the HSS shall send a Cancel Location (IMSI, Cancellation Type) message with Cancellation Type set to Subscription Withdrawn to the registered MME and also to the SGSN if an SGSN is also registered. When receiving the Cancel Location Message the MME/SGSN acknowledges with a Cancel Location ACK (IMSI) message to the HSS. 2. If Cancellation Type is Subscription Withdrawn, the MME/SGSN which has an active UE context informs the UE which is in ECM-CONNECTED state, that it has been detached, by sending Detach Request (Detach Type) message to the UE. If the Cancel Location message includes a flag to indicate re-attach is required, the MME/SGSN shall set the Detach Type to indicate that re-attach is required. If the UE is in ECM-IDLE state the MME pages the UE. NOTE 5: The UE will receive only one Detach Request message in the RAT where it currently camps on. 3a. If the UE has no activated PDN connection, then steps 3 to 7 are not executed. If the PLMN has configured secondary RAT usage data reporting, the MME shall wait for Step 8a, if applicable, and perform step 10a before step 3a. If the MME has an active UE context, for any PDN connection to the SCEF, the MME indicates to the SCEF that the PDN connection for the UE is no longer available according to TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] and steps 3 to 7 are not executed. For PDN connections to the P-GW, the MME sends a Delete Session Request (LBI, User Location Information (ECGI), NAS Release Cause if available, Secondary RAT usage data if available, PSCell ID if available) message per PDN connection to the Serving GW to deactivate the EPS Bearer Context information in the Serving GW. NAS Release Cause is only sent by the MME to the PDN GW if this is permitted according to MME operator's policy. If MME has received PSCell ID from eNodeB, the MME includes it in Delete Session Request. 3b. If the SGSN has an active UE context, the SGSN sends a Delete Session Request (LBI, User Location Information (CGI/SAI)) per PDN connection to the Serving GW to deactivate the EPS Bearer Context information in the Serving GW. 4. When the S-GW receives the first Delete Session Request message from the MME or SGSN in ISR activated state, the Serving GW deactivates ISR, releases the related EPS Bearer context information and responds with Delete Session Response in step 7. When the S-GW receives one or several Delete Session Request message(s) from the MME or SGSN in ISR deactivated state, the Serving GW releases the related EPS Bearer context information and sends a Delete Session Request (LBI, User Location Information (ECGI or CGI/SAI), NAS Release Cause if available, Secondary RAT usage data if PGW secondary RAT usage data reporting is active) message for each associated PDN connection to the PDN GW. NAS Release Cause is the one received in the Delete Session Request from the MME or SGSN. This message indicates that all bearers belonging to that PDN connection shall be released. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. If the MME and/or SGSN sends UE's Location Information and/or UE Time Zone Information in step 3a and/or step 3b, the S-GW includes the User Location Information and/or UE Time Zone with the least age in this message. 5. The PDN GW acknowledges with Delete Session Response (Cause and, optionally, APN Rate Control Status according to clause 4.7.7.3) message. 6. The PDN GW employs a PCEF initiated IP-CAN Session Termination procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] with the PCRF to indicate to the PCRF that the EPS bearer is released if a PCRF is configured. If requested by the PCRF the PDN GW indicates User Location Information and/or UE Time Zone Information and NAS Release Cause (if available) to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. 7. The Serving GW acknowledges with Delete Session Response (TEID and, optionally, APN Rate Control Status) message. If received, the MME stores the APN Rate Control Status in the MM context. 8. If the UE receives the Detach Request message from the MME/SGSN, the UE sends a Detach Accept message to the MME/SGSN any time after step 2. The message is sent either in E-UTRAN or GERAN/UTRAN access depending on which access the UE received the Detach Request. For the Detach Accept message from UE to MME the eNodeB forwards this NAS message to the MME along with the TAI+ECGI of the cell which the UE is using. If Dual Connectivity is active for the UE, the PSCell ID shall be included in the Uplink NAS Transport that carries the Detach Accept message. 9. Void. 10a. After receiving the Detach Accept message, the MME releases the S1-MME signalling connection for the UE by sending S1 Release Command (Cause) message to the eNodeB with Cause set to Detach. The details of this step are covered in the "S1 Release Procedure", as described in clause 5.3.5. NOTE 6: In the "S1 Release Procedure", if Dual Connectivity was active at the time of the release, the eNodeB includes the PSCell ID. 10b. After receiving the Detach Accept message, if Detach Type did not request the UE to make a new attach, then the 3G SGSN releases the PS signalling 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") | 5.3.8.4 |
3,786 | 4.22.6.3 Network Modification to MA PDU Session after a UE moving from EPC | Figure 4.22.6.3-1 describes procedure for Network Modification to MA PDU Session after a UE is moving from EPS. Figure 4.22.6.3-1: Network Modification to MA PDU Session after a UE moving from EPS 1. When the network supports interworking with N26 interface, a PDN Connection can be moved from EPS to 5GS as described in clause 4.11.1.2.2 and clause 4.11.1.3.3. 2. If the UE requests MA PDU session, or if no policy in the UE (e.g. no URSP rule) and no local restrictions mandate a single access for the PDU Session, the UE requests PDU Session Modification over 3GPP access as described in clause 4.22.8 with following modifications: - In step 1a, the UE provides Request Type as "MA PDU Request" in UL NAS Transport message, or, if no policy in the UE (e.g. no URSP rule) and no local restrictions mandate a single access for the PDU Session, the UE provides an "MA PDU Network-Upgrade Allowed" indication in UL NAS Transport message. The UE provides its ATSSS Capabilities, as defined in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] in PDU Session Modification Request message. If the AMF receives the "MA PDU Network-Upgrade Allowed" indication from the UE, the AMF may send it to the SMF. If the AMF determines that the UE is registered via both accesses in the same PLMN but the current S-NSSAI is not in the Allowed NSSAI for both accesses, the AMF shall reject the PDU session modification if the UE provides an "MA PDU Request" indication, or the AMF shall not forward "MA PDU Network-Upgrade Allowed" indication to the SMF if received from the UE. - In step 3a, if the SMF decides to change the PDU Session to MA PDU Session, the SMF includes ATSSS rule(s) in the PDU Session Modification Command message. The SMF may also include Measurement Assistance Information. When the SMF sends Nsmf_PDUSession_UpdateSMContext response, the SMF includes "MA PDU session Accepted" indication. The AMF marks the PDU Session as MA PDU Session based on the indication. If the SMF was informed in step 1a that the UE is registered over both accesses, then the SMF initiates the establishment of user-plane resources over non-3GPP access too. - In step 5, if the UE receives ATSSS rule(s) in the PDU Session Modification Command message, the UE stores that the PDU Session is MA PDU Session. 3. If the UE is registered to the different PLMN over 3GPP and non-3GPP access or the UE is not registered in non-3GPP access, the UE may trigger the UE requested PDU Session Establishment procedure as described in clause 4.22.7 over non-3GPP access to add second access to the MA PDU Session after the UE is registered in non 3GPP access. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.6.3 |
3,787 | – IABOtherInformation | The IABOtherInformation message is used by IAB-MT to request the network to allocate IP addresses for the collocated IAB-DU or inform the network about IP addresses allocated to the collocated IAB-DU. Signalling radio bearer: SRB1 or SRB3 RLC-SAP: AM Logical channel: DCCH Direction: IAB-MT to Network IABOtherInformation message -- ASN1START -- TAG-IABOTHERINFORMATION-START IABOtherInformation-r16 ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { iabOtherInformation-r16 IABOtherInformation-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } IABOtherInformation-r16-IEs ::= SEQUENCE { ip-InfoType-r16 CHOICE { iab-IP-Request-r16 SEQUENCE { iab-IPv4-AddressNumReq-r16 IAB-IP-AddressNumReq-r16 OPTIONAL, iab-IPv6-AddressReq-r16 CHOICE { iab-IPv6-AddressNumReq-r16 IAB-IP-AddressNumReq-r16, iab-IPv6-AddressPrefixReq-r16 IAB-IP-AddressPrefixReq-r16, ... } OPTIONAL }, iab-IP-Report-r16 SEQUENCE { iab-IPv4-AddressReport-r16 IAB-IP-AddressAndTraffic-r16 OPTIONAL, iab-IPv6-Report-r16 CHOICE { iab-IPv6-AddressReport-r16 IAB-IP-AddressAndTraffic-r16, iab-IPv6-PrefixReport-r16 IAB-IP-PrefixAndTraffic-r16, ... } OPTIONAL }, ... }, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } IAB-IP-AddressNumReq-r16 ::= SEQUENCE { all-Traffic-NumReq-r16 INTEGER (1..8) OPTIONAL, f1-C-Traffic-NumReq-r16 INTEGER (1..8) OPTIONAL, f1-U-Traffic-NumReq-r16 INTEGER (1..8) OPTIONAL, non-F1-Traffic-NumReq-r16 INTEGER (1..8) OPTIONAL, ... } IAB-IP-AddressPrefixReq-r16 ::= SEQUENCE { all-Traffic-PrefixReq-r16 ENUMERATED {true} OPTIONAL, f1-C-Traffic-PrefixReq-r16 ENUMERATED {true} OPTIONAL, f1-U-Traffic-PrefixReq-r16 ENUMERATED {true} OPTIONAL, non-F1-Traffic-PrefixReq-r16 ENUMERATED {true} OPTIONAL, ... } IAB-IP-AddressAndTraffic-r16 ::= SEQUENCE { all-Traffic-IAB-IP-Address-r16 SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL, f1-C-Traffic-IP-Address-r16 SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL, f1-U-Traffic-IP-Address-r16 SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL, non-F1-Traffic-IP-Address-r16 SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL } IAB-IP-PrefixAndTraffic-r16 ::= SEQUENCE { all-Traffic-IAB-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL, f1-C-Traffic-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL, f1-U-Traffic-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL, non-F1-Traffic-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL } -- TAG-IABOTHERINFORMATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,788 | 4.8 Non-Public Networks | A Non-Public Network (NPN) is a network for non-public use (see TS 22.261[ Service requirements for the 5G system ] [19]), which can be deployed as (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]): - a Stand-alone Non-Public Network (SNPN) when not relying on network functions provided by a PLMN; or - a Public Network Integrated (PNI) NPN when relying on the support of a PLMN. NOTE: As described in clause 5.30.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [3], there are several approaches in which PNI-NPNs can be made available via PLMNs. The only approach visible to AS, and hence the only approach that is addressed in AS specifications is the approach of using CAGs. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.8 |
3,789 | 19.4.3 Service and Protocol service names for 3GPP | A list of standardized "service-parms" names is required to identify a "service" as defined in clause 6.5 of IETF RFC 3958 [74]. The following table defines the names to be used in the procedures specified in 3GPP TS 29.303[ Domain Name System Procedures; Stage 3 ] [73]: Table 19.4.3.1: List of 'app-service' and 'app-protocol' names NOTE 1: The formats follow the experimental format as specified in IETF RFC 3958 [74]. For example, to find the S8 PMIP interfaces on a PGW the Service Parameter of "3gpp-pgw:x-s8-pmip" would be used as input in the procedures defined in IETF RFC 3958 [74]. NOTE 2: Currently 'app-service' names identify 3GPP node type and 'app-protocol' identify 3GPP interfaces, which differs from more common usage of S-NAPTR where app-protocol is used for transport protocol. Type of nodes (i.e PGW, SGW, SGSN, MME, MSC Server etc) and interfaces (i.e. S11, S5, S8, Sv, etc.) follow the standard names from 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [72] ,3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [6] and3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [92] with prefix "x-" added. NOTE 3: x-gn denotes an intra-PLMN interface using GTPv1-C, x-gp denotes an inter-PLMN interface using GTPv1-C. NOTE 4: The app-service of x-3gpp-pgw with app-protocols x-gn or x-gp identifies the co-located GGSN function on a PGW. The app-service of x-3gpp-ggsn with app-protocols x-gn or x-gp identifies a GGSN function that is not co-located with a PGW. NOTE 5: The app-service of x-3gpp-msc with app-protocol x-sv identifies the MSC Sv interface service. NOTE 6: The app-service of x-3gpp-amf with app-protocol x-n2 identifies the AMF N2 interface service. The app-service of x-3gpp-amf with app-protocol x-n26 identifies the AMF N26 interface service. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.3 |
3,790 | D.3 Interoperation procedures D.3.1 General | The interoperation procedures describe information flows for Gn/Gp SGSNs and other EPS network elements. All messages between Gn/Gp SGSN and MME, between Gn/Gp SGSN and HSS and between Gn/Gp SGSN and P-GW as well as the therein contained information elements are the same as specified for the adequate TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] procedures that are between Gn/Gp SGSNs. These messages and procedure step descriptions are taken from TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] for explanatory purposes only. These descriptions are in italic text and shall not be modified by the interoperation procedures. It cannot be assumed that the messages and procedure step descriptions that are taken from TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] will be updated when modifications or corrections are performed for TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. If there are any discrepancies for these messages and procedure step descriptions TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] takes precedence. The messages between the MME and any other node than the Gn/Gp SGSN as well as the therein contained information elements are the same as specified in the main body of this technical specification for the inter RAT Routing Area Update procedure. If there are any discrepancies for these messages the descriptions from the main body of this Technical Specification take precedence. An operator that has pre-Rel-8 SGSNs in its network should use separate EPS bearers for IPv4 and IPv6 addressing, such that both addresses can be maintained when moving to a pre-Rel-8 SGSN from a Rel-8 SGSN or MME (see clause 5.3.1). This is configured into the SGSN and MME nodes which set the Dual Address Bearer Flag depending on whether a UE may or may not be handed over to a pre-Rel-8 SGSN, as specified in clauses 5.3.2.1 and 5.10.2. An operator supporting emergency services shall not have pre-Rel-9 SGSNs in its network where a UE may be handed over. | 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") | D.3 |
3,791 | 6.6.3D Spurious emission for ProSe | When UE is configured for E-UTRA ProSe sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA ProSe operating bands specified in Table 5.5D-1, the requirements in subclause 6.6.3 apply. When UE is configured for simultaneous E-UTRA ProSe sidelink and E-UTRA uplink transmissions for inter-band E-UTRA ProSe / E-UTRA bands specified in Table 5.5D-2, the UE co-existence requirements in Table 6.6.3.2A-0 in subclause 6.6.3.2A apply as specified for the corresponding inter-band aggregation with uplink assigned to two bands. | 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.3D |
3,792 | 6.8A.5 Mapping to resource elements | The block of complex-valued symbols shall be mapped in sequence starting with to resource elements on the associated antenna port which meet all of the following criteria: - they are part of the EREGs assigned for the EPDCCH transmission, and - they are assumed by the UE not to be used for cell-specific reference signals, where the positions of the cell-specific reference signals are given by clause 6.10.1.2 with the number of antenna ports for and the frequency shift of cell-specific reference signals derived as described in clause 6.10.1.2 unless other values for these parameters are provided by clause 9.1.4.3 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and - they are assumed by the UE not to be used for transmission of: - zero-power CSI reference signals, where the positions of the CSI reference signals are given by clause 6.10.5.2. The configuration for zero power CSI reference signals is - obtained as described in clause 6.10.5.2 unless other values are provided by clause 9.1.4.3 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and - obtained by higher-layer configuration of up to five reserved CSI-RS resources as part of the discovery signal configuration following the procedure for zero-power CSI-RS in clause 6.10.5.2. - non-zero-power CSI reference signals for CSI reporting, except for non-zero power CSI reference signals configured by csi-RS-ConfigNZP-ApList, with the configuration for non-zero power CSI reference signals for CSI reporting obtained as described in clause 6.10.5.2, and - for frame structure type 1 and 2, the index in the first slot in a subframe fulfils where is given by clause 9.1.4.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and - for frame structure type 3, - if the higher layer parameter subframeStartPosition indicates 's07' and if the downlink transmission starts in the second slot of a subframe - the index in the second slot in the subframe fulfils where is given by clause 9.1.4.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], - otherwise - the index in the first slot in the subframe fulfils where is given by clause 9.1.4.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. The mapping to resource elements on antenna port meeting the criteria above shall be in increasing order of first the index and then the index, starting with the first slot and ending with the second slot in a subframe. For localized transmission, the single antenna port to use is given by Table 6.8A.5-1 with where is the lowest ECCE index used by this EPDCCH transmission in the EPDCCH set, equals the C-RNTI, and is the number of ECCEs used for this EPDCCH. Table 6.8A.5-1: Antenna port to use for localized EPDCCH transmission For distributed transmission, each resource element in an EREG is associated with one out of two antenna ports in an alternating manner, starting with antenna port 107, where for normal cyclic prefix and for extended cyclic prefix. | 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.8A.5 |
3,793 | 5.10.3 MRB configuration 5.10.3.1 General | The multicast MRB configuration procedure is used by the UE in RRC_INACTIVE state to configure PDCP, RLC, MAC entities and the physical layer upon PTM configuration update and moving to a cell providing SIB24. The UE may perform multicast MRB modification or release/establishment when PTM configuration is updated via MCCH or when it moves to a cell where the PDCP COUNT of the corresponding multicast MRB is not synchronized within the RNA. The UE may perform multicast MRB modification when it moves to a cell where the PDCP COUNT of the corresponding multicast MRB is synchronized within the RNA. The UE resets MAC upon cell-reselection. NOTE: How to perform modification of a multicast MRB which is already configured in the UE is left to UE implementation. Upon moving to a cell where the PDCP COUNT of a multicast MRB is not synchronized, an indication is sent to the lower layer to inform the PDCP COUNT non-synchronization of the corresponding multicast MRB. Upon transition from RRC_CONNECTED to RRC_INACTIVE in the same cell, the UE can continue using the multicast MRBs used in RRC_CONNECTED. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.10.3 |
3,794 | 8.2.2.4.1F Minimum Requirement Single-Layer Spatial Multiplexing 4 Tx Antenna Ports with CRS assistance information | The requirements are specified in Table 8.2.2.4.1F-2, with the addition of parameters in Table 8.2.2.4.1F-1. In Table 8.2.2.4.1F-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the closed loop single layer TM4 performance under assumption that UE applies CRS interference mitigation in the scenario with 4 CRS antenna ports in the serving and aggressor cells. Table 8.2.2.4.1F-1: Test Parameters Table 8.2.2.4.1F-2: Minimum Performance for PDSCH | 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.2.2.4.1F |
3,795 | 4.3.20.2.3 Attach for RN operation | To start relay operations, the normal attach procedure, with the following exceptions, is applied: - The RN and the USIM-RN perform local security operations (e.g. establishment of a secure channel between them) as specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]; - The RN selects a cell from the list acquired during Phase I; - The RN establishes an RRC connection with the DeNB, indicating that the connection is for a RN; - The DeNB is aware of the MMEs that support RN functionality. In all cases when the RN indication is received, the DeNB shall ensure that the current or (re)selected MME supports RN functionality; NOTE 1: The RN follows normal UE behaviour, e.g. the RN's NAS may use either an IMSI or a GUTI. Also, the RN's NAS may or may not provide an S-TMSI to the RN's AS, and hence, the RRCConnectionRequest may either contain an S-TMSI or a random value. - In the S1 interface Initial UE Message, the DeNB sends the RN indication to the MME. This message also carries the IP address of the S-GW/P-GW function embedded in the DeNB; - The subscription data supplied to the MME by the HSS for USIM-RN includes an indication that the subscription is permitted to be used by a RN. - If the S1 interface Initial UE Message indicates that this is a RN, but the subscription data does not indicate that the subscription includes a permission to operate as a RN, then the MME shall reject the NAS procedure (e.g. Attach Request, Tracking Area Update Request, Service Request, etc) with an appropriate cause value (e.g. one that avoids retries on this PLMN yet does not harm a RN that has unexpectedly performed PLMN reselection). NOTE 2: It is anticipated that the MME checks that the HPLMN of the USIM-RN is authorised to attach RNs to this MME. - The MME and RN perform the normal EPS Authentication procedures. - MME (RN) selects the S-GW/P-GW in DeNB for the RN based on the IP address included in the Initial UE Message (i.e. all GW selection and APN related procedures are bypassed during this phase). The MME performs S11 interface signalling with the S-GW/P-GW located in the DeNB; - The MME accepts the attach procedure and sets up an S1 context with the DeNB. When relay function is enabled, MMEs in a pool should all have the same relaying function capability in order to have consistent support for functions such as redundancy, load balancing. Figure 4.3.20.2-1: RN attach procedure The detach procedure for the RN is the same as the normal UE detach procedure, though the RN should ensure that no UE is connected to the RN cells before detaching. It is up to RN implementation how it ensures no UE is connected. | 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.20.2.3 |
3,796 | 5.11.4 UE Radio Capability for Paging Information | Depending upon the features implemented in the E-UTRAN, this procedure may assist the E-UTRAN in optimising the radio paging procedures, or this procedure can be essential for mobile terminating services to succeed. Using procedures specified in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36], the eNodeB shall upload the UE Radio Capability for Paging Information to the MME in the S1 interface UE CAPABILITY INFO INDICATION message (in a separate IE from the UE Radio Capability). As specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37], the UE Radio Capability for Paging Information may contain UE Radio Paging Information provided by the UE to the eNodeB, and other information derived by the eNodeB (e.g. band support information) from the UE Radio Capability information. The UE Radio Capability for Paging Information for NB-IoT and WB-E-UTRAN are separately stored in the MME. The RAT Type (derived from the UE's Tracking Area Code) is used to determine which RAT the information relates to. The handling of the UE Radio Capability for Paging Information with RACS is described in clause 5.11.3a. If a UE supports both NB-IoT and WB-E-UTRAN, the UE and eNodeB handle the UE Radio Capability for Paging Information as follows: - when the UE is camping on NB-IoT the UE provides only NB-IoT information to the network; - when the UE is camping on WB-E-UTRAN, the UE provides only WB-E-UTRAN information to the network. Typically, this information is sent to the MME at the same time as the eNodeB uploads the UE Radio Capability information. The MME stores the UE Radio Capability for Paging Information in the MME context. When it needs to page, the MME provides the UE Radio Capability for Paging Information for that RAT to the eNodeB as part of the S1 paging message. The eNodeB may use the UE Radio Capability for Paging Information to enhance the paging towards the UE and/or to calculate when or how to broadcast paging information or the Wake Up Signal to the UE, see TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34]. If the UE is performing an Attach procedure or a Tracking Area Update procedure for the "first TAU following GERAN/UTRAN/ Attach" or for "UE radio capability update", the MME shall delete all UE Radio Capability for Paging Information that it has stored for that UE. If the UE Radio Capability for Paging Information changes for either RAT, the UE shall follow the same procedures as if the UE Radio Capability changes. During a change of MME, the old MME includes in the MM context in the Context Response message the UE Radio Capability for Paging of the UE if available. If the RAT type is indicated by the new MME, then the old MME includes the UE Radio Capability for Paging for the corresponding RAT type, if available. In order to handle the situations of connected mode inter-MME change, the UE Radio Capability for Paging Information is sent to the target MME as part of the MM Context information. The UE Radio Capability for Paging Information is only applicable for MMEs, i.e. it is not applicable for SGSNs. Therefore, it will not be included by MME during context transfers towards SGSNs. | 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.11.4 |
3,797 | 5.7.1.8 AMBR/MFBR enforcement and rate limitation | UL and DL Session-AMBR (see clause 5.7.2.6) shall be enforced by the UPF, if the UPF receives the Session-AMBR values from the SMF as described in clause 5.8.2.7 and clause 5.8.5.4. For UL Classifier PDU Sessions, UL and DL Session-AMBR (see clause 5.7.2.6) shall be enforced in the SMF selected UPF that supports the UL Classifier functionality. In addition, the DL Session-AMBR shall be enforced separately in every UPF that terminates the N6 interface (i.e. without requiring interaction between the UPFs) (see clause 5.6.4). For multi-homed PDU Sessions, UL and DL Session-AMBR shall be enforced in the UPF that supports the Branching Point functionality. In addition, the DL Session-AMBR shall be enforced separately in every UPF that terminates the N6 interface (i.e. without requiring interaction between the UPFs) (see clause 5.6.4). NOTE: The DL Session-AMBR is enforced in every UPF terminating the N6 interface to reduce unnecessary transport of traffic which may be discarded by the UPF performing the UL Classifier/Branching Point functionality due to the amount of the DL traffic for the PDU Session exceeding the DL Session-AMBR. Discarding DL packets in the UL Classifier/Branching Point could cause erroneous PDU counting for support of charging The (R)AN shall enforce UE-AMBR (see clause 5.7.2.6) in UL and DL per UE for Non-GBR QoS Flows. The UE shall perform UL rate limitation on PDU Session basis for Non-GBR traffic using Session-AMBR, if the UE receives a Session-AMBR. MBR per SDF is mandatory for GBR QoS Flows but optional for Non-GBR QoS Flows. The MBR is enforced in the UPF. The MFBR is enforced in the UPF in the Downlink for GBR QoS Flows. The MFBR is enforced in the (R)AN in the Downlink and Uplink for GBR QoS Flows. For non-3GPP access, the UE should enforce MFBR in the Uplink for GBR QoS Flows. The QoS control for Unstructured PDUs is performed at the PDU Session level and in this Release of the specification there is only support for maximum of one 5G QoS Flow per PDU Session of Type Unstructured. When a PDU Session is set up for transferring unstructured PDUs, SMF provides the QFI which will be applied to any packet of the PDU Session to the UPF and UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1.8 |
3,798 | 8.2.2.4.3A Minimum Requirement Multi-Layer Spatial Multiplexing 4 Tx Antenna Port for dual connectivity | For dual connectivity the requirements are specified in Table 8.2.2.4.3A-3, for 2DL CCs, in Table 8.2.2.4.3A-4 for 3DL CCs, and Table 8.2.2.4.3A-5 for 4DL CCs, based on single carrier requirement specified in Table 8.2.2.4.3A-2, with the addition of the parameters in Table 8.2.2.4.3A-1 and the downlink physical channel setup according to Annex C.3.2.The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding by using dual connectivity. Table 8.2.2.4.3A-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for dual connectivity Table 8.2.2.4.3A-2: Single carrier performance for multiple dual connectivity configurations Table 8.2.2.4.3A-3: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity Table 8.2.2.4.3A-4: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity Table 8.2.2.4.3A-5: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity | 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.2.2.4.3A |
3,799 | 19.8 TWAN Operator Name | The TWAN Operator Name identifies the TWAN operator when the TWAN is not operated by a mobile operator. The TWAN Operator Name shall be encoded as a realm in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The TWAN Operator Name consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. NOTE: The TWAN Operator Name is encoded as a dotted string. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.8 |
3,800 | 5.3.4.4 UE mobility event notification | 5G System supports the functionality of tracking and reporting UE mobility events. The AMF provides the UE mobility related event reporting to NF that has been authorized to subscribe to the UE mobility event reporting service. Any NF service consumer such as SMF, NEF, TSCTSF or NWDAF that wants to be reported on the UE location is able to subscribe to the UE mobility event notification service to the AMF with the following parameters: - Event reporting type that specifies what to be reported on UE mobility (e.g. UE location, UE mobility on Area of Interest). - Event filters indicating the: - Area Of Interest that specifies a location area within 3GPP system. The Area Of Interest is represented by a list of Tracking Areas, list of cells or list of (R)AN node identifiers. In the case of LADN, the event consumer (e.g. SMF) provides the "LADN DNN" or "LADN DNN and S-NSSAI" to refer the LADN service area as the Area Of Interest. In the case of PRA, the event consumer (e.g. SMF or PCF) may provide an identifier for Area Of Interest to refer predefined area as the Area Of Interest. In the case of Partial Network Slice Support and Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas as described in clauses 5.15.17 and 5.15.18, the event consumer (e.g. SMF) provides the S-NSSAI to refer the slice restriction area (area restriction applies for the S-NSSAI) as the Area Of Interest. - The Area Of Interest may include a "RAN timing synchronization status change event" indicator, indicating that the presence in Area of Interest can be determined based on the most recent N2 connection. - The Area Of Interest may include an "Adjust AoI based on RA" indicator, indicating that the Area of Interest may be adjusted depending on UE's RA. - The Area Of Interest may include the "Notify the consumer considering UE identity" indicator, containing a list of UE identities or Internal Group ID, and informing the AMF to notify the NF consumer about Area of Interest events only if an event is for the UE belonging to the provided list UEs. The indicator may be included when the request is targeted to Any UE. - The Area Of Interest may include the "Notify the consumer considering DNN/S-NSSAI" indicator, containing one or more DNN(s)/S-NSSAI(s) and informing the AMF to notify the NF consumer about Area of Interest events only if an event is for the UE having a PDU sessions established for the specified DNN(s)/S-NSSAI(s). - S-NSSAI and optionally the NSI ID(s). - Event Reporting Information: event reporting mode, number of reports, maximum duration of reporting, event reporting condition (e.g. when the target UE moved into a specified Area Of Interest, immediate reporting flag). - Notification Endpoint of NF service consumer to be notified. - The target of event reporting that indicates a (list of) specific UE(s), a group of UE(s) or any UE (i.e. all UEs served by the AMF). Further details on the information provided by the NF service consumer are provided in clause 4.15 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If an NF service consumer subscribes to the UE mobility event notification service provided by AMF for reporting of UE presence in Area Of Interest, the AMF tracks UE's location considering UE's CM state and using NG-RAN procedures (if RRC_INACTIVE state applies to NG-RAN) in order to determine the UE presence in the Area Of Interest, as described in clause 4.15.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Upon detecting the change of the UE presence in the Area Of Interest, the AMF notifies the UE presence in the Area Of Interest and the new UE location to the subscribed NF service consumer. If the Area Of Interest in the subscription to the UE mobility event notification includes "RAN timing synchronization status change event" indicator as described in Table 5.2.2.3.1-1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], and the registration request from the UE includes a UE 5GMM Core Network Capability with an indication for "support for network reconnection due to RAN timing synchronization status change " as described in clause 5.4.4.a, the AMF reports the UE presence in Area of Interest based on the most recent N2 connection as described in Annex D of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the Area Of Interest in the subscription to the UE mobility event notification includes "Adjust AoI based on RA" indicator as described in Table 5.2.2.3.1-1 in TS 23.502[ Procedures for the 5G System (5GS) ] [3], the AMF reports the UE presence in Area of Interest based on the most recent N2 connection as described in Annex D in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When the AMF is changed, the subscription of mobility event for a UE or group of UEs is transferred from the old AMF. Subscriptions targeted to Any UE shall not be moved to another AMF due to UE mobility. The new AMF may decide not to notify the SMF with the current status related to the subscription of mobility event if the new AMF determines that, based on MM Context of the UE, the event is reported by the old AMF. In the network deployment where a UE may leave or enter the Area Of Interest without any notification to the 5GC in CM-CONNECTED state (i.e. in the case that RRC_INACTIVE state applies to the NG-RAN), the AMF may initiate the NG-RAN location reporting as described in clause 5.4.7 or N2 Notification as described in clause 4.8.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] to track the UE presence in the Area Of Interest. The AMF may provide UE mobility event reporting to PCF, using Policy Control Request Triggers defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.4.4 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.