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
β |
|---|---|---|---|---|---|---|---|
2,101 | 8.2.5 Intra-CU Backhaul RLF recovery for IAB-nodes in SA mode | The intra-CU backhaul RLF recovery procedure for IAB-nodes in SA mode enables migration of an IAB-node to another parent node underneath the same IAB-donor-CU, when the IAB-MT declares a backhaul RLF. The declaration of backhaul RLF is described in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [23]. NOTE: Determination of whether the recovery occurs at the same or at a different IAB-donor-CU is up to implementation. Figure 8.2.5-1 shows an example of the BH RLF recovery procedure for an IAB-node in SA mode. In this example, the IAB-node changes from its initial parent node to a new parent node, where the new parent node is served by an IAB-donor-DU different than the one serving its initial parent node. Figure 8.2.5-1: IAB intra-CU backhaul RLF recovery procedure for an IAB-node in SA mode 1. The IAB-MT declares BH RLF for the MCG as described in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [23], clause 5.3.10.3. 2. The IAB-MT undergoing recovery from RLF conducts the RRC re-establishment procedure at the new parent node, as defined in clause 8.7. In this procedure, the IAB-donor-CU may provide new TNL address(es), which is(are) anchored at the new IAB-donor-DU, to the IAB-MT via RRC signalling. Furthermore, the IAB-donor-CU may also provide a new default UL mapping which includes a default BH RLC channel and a default BAP Routing ID for UL F1-C/non-F1 traffic on the target path, to the IAB-node undergoing recovery from RLF via RRCReconfiguration message in this procedure. 3. The remaining part of the procedure follows the steps 11-15 of the intra-CU topology adaptation procedure defined in clause 8.2.3.1. Descendant node(s) of the IAB-node undergoing recovery from RLF may also need to switch to new TNL address(es) anchored in the target-path IAB-donor-DU following the same mechanism as described for IAB intra-CU topology adaptation procedure in clause 8.2.3.1. The descendant node(s) may also be provided with new default UL mapping via RRC, after the IAB-node undergoing recovery from RLF connects the IAB-donor-CU via the recovery path. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.5 |
2,102 | 9.9.3.34 UE network capability | The purpose of the UE network capability information element is to provide the network with information concerning aspects of the UE related to EPS or interworking with GPRS and 5GS. The contents might affect the manner in which the network handles the operation of the UE. The UE network capability information indicates general UE characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on. The UE network capability information element is coded as shown in figure 9.9.3.34.1 and table 9.9.3.34.1. The UE network capability is a type 4 information element with a minimum length of 4 octets and a maximum length of 15 octets. NOTE: The requirements for the support of UMTS security algorithms in the UE are specified in 3GPP TS 33.102[ 3G security; Security architecture ] [18], and the requirements for the support of EPS security algorithms in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]. Figure 9.9.3.34.1: UE network capability information element Table 9.9.3.34.1: UE network capability information element | 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 | 9.9.3.34 |
2,103 | 5.2.5.2 Npcf_AMPolicyControl service 5.2.5.2.1 General | Service description: NF Service Consumer, e.g. AMF, can create and manage an AM Policy Association in the PCF through which the NF Service Consumer receives access and mobility related policy information for a UE identified by a SUPI. As part of this service, the PCF may provide the NF Service Consumer, e.g. AMF, with AM policy information for a SUPI that may contain: - Access and mobility related policy information as defined in clause 6.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the case of roaming, this information is provided by V-PCF; - Policy Control Request Trigger of AM Policy Association as defined in clause 6.1.2.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the case of roaming, the V-PCF may subscribe to AMF. At Npcf_AMPolicyControl_Create, the NF Service Consumer, e.g. AMF requests the creation of a corresponding AM Policy Association with the PCF (Npcf_AMPolicyControl_Create) and provides relevant parameters about the UE context to the PCF. When the PCF has created the AM Policy Association, the PCF may provide access and mobility related policy information in the response. When a Policy Control Request Trigger condition is met the NF Service Consumer, e.g. AMF requests the update (Npcf_AMPolicyControl_Update) of the AM Policy Association by providing information on the condition(s) that have been met as defined in clause 6.1.2.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The PCF may provide updated access and mobility related policy information to the NF Service Consumer in the response. The PCF may at any time provide updated access and mobility related policy information (Npcf_AMPolicyControl_UpdateNotify); At UE deregistration the NF Service Consumer, e.g. AMF requests the deletion of the corresponding AM Policy Association (Npcf_AMPolicyControl_Delete). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.2 |
2,104 | 16a.4.5 STR Command | The STR command, defined in IETF RFC 6733 (Diameter Base) [111], is indicated by the Command-Code field set to 275 and the βRβ bit set in the Command Flags field. It is sent by the GGSN/P-GW to the Diameter server to terminate a DIAMETER session corresponding to an IP-CAN session of a certain user. The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. Message Format: <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Auth-Application-Id } { Termination-Cause } [ User-Name ] [ Destination-Host ] * [ Class ] [ Origin-State-Id ] * [ Proxy-Info ] * [ Route-Record ] * [ AVP ] | 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 | 16a.4.5 |
2,105 | 6.5.3 RRC UE capability transfer procedure | The network should activate AS security (i.e., perform a successful AS SMC procedure) before running the RRC UE capability transfer procedure. With the exception of unauthenticated emergency calls and the UEs using Control plane CIoT optimization,, if the network had acquired UE capabilities using RRC UE capability transfer procedure before AS security activation, then the network shall not store them locally for later use and shall not send them to other network entities. In that case, the network shall re-run the RRC UE capability transfer procedure after a successful AS SMC procedure. NOTE 1: For UEs without AS security (e.g., UEs using Control Plane CIoT optimization), RRC UE radio capability transfer procedure cannot be protected. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.5.3 |
2,106 | 5.19.3 AMF Load Balancing | The AMF Load Balancing functionality permits UEs that are entering into an AMF Region/AMF Set to be directed to an appropriate AMF in a manner that achieves load balancing between AMFs. This is achieved by setting a Weight Factor for each AMF, such that the probability of the 5G-AN selecting an AMF is proportional to Weight Factor of the AMF. The Weight Factor is typically set according to the capacity of an AMF node relative to other AMF nodes. The Weight Factor is sent from the AMF to the 5G-AN via NGAP messages (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]). NOTE 1: An operator may decide to change the Weight Factor after the establishment of NGAP connectivity as a result of changes in the AMF capacities. e.g. a newly installed AMF may be given a very much higher Weight Factor for an initial period of time making it faster to increase its load. NOTE 2: It is intended that the Weight Factor is NOT changed frequently. e.g. in a mature network, changes on a monthly basis could be anticipated, e.g. due to the addition of 5G-AN or 5GC nodes. NOTE 3: Weight Factors for AMF Load Balancing are associated with AMF Names. Load balancing by 5G-AN node is only performed between AMFs that belong to the same AMF set, i.e. AMFs with the same PLMN, AMF Region ID and AMF Set ID value. The 5G-AN node may have their Load Balancing parameters adjusted (e.g. the Weight Factor is set to zero if all subscribers are to be removed from the AMF, which will route new entrants to other AMFs within an AMF Set). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.19.3 |
2,107 | 5.24 3GPP PS Data Off | This feature, when activated by the user, prevents traffic via 3GPP access of all IP packets, Unstructured and Ethernet data except for those related to 3GPP PS Data Off Exempt Services. The 3GPP PS Data Off Exempt Services are a set of operator services, defined in TS 22.011[ Service accessibility ] [25] and TS 23.221[ Architectural requirements ] [23], that are the only allowed services when the 3GPP PS Data Off feature has been activated by the user. The 5GC shall support 3GPP PS Data Off operation in both non-roaming and roaming scenarios. UEs may be configured with up to two lists of 3GPP PS Data Off Exempt Services and the list(s) are provided to the UEs by HPLMN via Device Management or UICC provisioning. When the UE is configured with two lists, one list is valid for the UEs camping in the home PLMN and the other list is valid for any VPLMN the UE is roaming in. When the UE is configured with a single list, without an indication to which PLMNs the list is applicable, then this list is valid for the home PLMN and any PLMN the UE is roaming in. NOTE 1: The operator needs to ensure coordinated list(s) of 3GPP Data Off Exempt Services provisioned in the UE and configured in the network. The UE reports its 3GPP PS Data Off status in PCO (Protocol Configuration Option) to (H-)SMF during UE requested PDU Session Establishment procedure for establishment of a PDU Session associated with 3GPP access and/or non-3GPP access. The UE does not need to report PS Data Off status during the PDU Session Establishment procedure for handover of the PDU Session between 3GPP access and non 3GPP access if 3GPP PS Data Off status is not changed since the last report. The PS Data Off status for a PDU Session does not affect data transfer over non-3GPP access. If 3GPP PS Data Off is activated, the UE prevents the sending of uplink IP packets, Unstructured and Ethernet data except for those related to 3GPP PS Data Off Exempt Services, based on the pre-configured list(s) of Data Off Exempt Services. If 3GPP PS Data Off is activated for a UE with MA PDU Sessions established through the ATSSS feature (see clause 5.32), the data transferred over the non-3GPP access of the MA PDU sessions are unaffected, which is ensured by the policy for ATSSS Control as specified in clause 5.32.3. The UE shall immediately report a change of its 3GPP PS Data Off status in PCO by using UE requested PDU Session Modification procedure. This also applies to the scenario of inter-RAT mobility to NG-RAN and to scenarios where the 3GPP PS Data Off status is changed when the session management back-off timer is running as specified in clause 5.19.7.3 and clause 5.19.7.4. For UEs in Non-Allowed Area (or not in Allowed Area) as specified in clause 5.3.4.1, the UE shall also immediately report a change of its 3GPP PS Data Off status for the PDU Session. For UEs moving out of LADN area and the PDU Session is still maintained as specified in clause 5.6.5, the UE shall also immediately report a change of its 3GPP PS Data Off status for the PDU Session. The additional behaviour of the SMF for 3GPP PS Data Off is controlled by local configuration or policy from the PCF as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE 2: For the PDU Session used for IMS services, the 3GPP Data Off Exempt Services are enforced in the IMS domain as specified TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15]. Policies configured in the (H-)SMF/PCF need to ensure those services are always allowed when the 3GPP Data Off status of the UE is set to "activated". | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.24 |
2,108 | 5.3.4.4.3 Tracking of applications generating charging information | Based on operator policy, each application for which the hosting AS CTF is generating charging events on its behalf, shall include the address or identifier of the AS as described in clause 5.3.4.4.2 and its application identifier into the initial SIP request to be sent out within the trust domain. The final SIP response sent back by the last element of the trust domain shall contain the list of addresses and application identifiers received within the initial SIP request. The list of addresses or identifiers and application identifiers received in the final response shall be included in the charging event generated by the CTF. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.3.4.4.3 |
2,109 | 5.2.2 Physical-layer processing for physical downlink shared channel | The downlink physical-layer processing of transport channels consists of the following steps: - Transport block CRC attachment; - Code block segmentation and code block CRC attachment; - Channel coding: LDPC coding; - Physical-layer hybrid-ARQ processing; - Rate matching; - Scrambling; - Modulation: QPSK, 16QAM, 64QAM, 256QAM, and 1024QAM; - Layer mapping; - Mapping to assigned resources and antenna ports. The UE may assume that at least one symbol with demodulation reference signal is present on each layer in which PDSCH is transmitted to a UE, and up to 3 additional DMRS can be configured by higher layers. Phase Tracking RS may be transmitted on additional symbols to aid receiver phase tracking. The DL-SCH physical layer model is described in TS 38.202[ NR; Services provided by the physical layer ] [20]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2 |
2,110 | 4.2.1.9 Number of E-RABs attempted to establish for incoming HOs | This measurement provides the number of E-RABs attempted to establish for incoming HOs. The measurement is split into subcounters per E-RAB QoS level (QCI). CC On receipt by the eNB of a X2AP HANDOVER REQUEST or S1AP HANDOVER REQUEST message; or on transmission by the eNB of the RRCConnectionReconfiguration message to the UE triggering the intra-eNB handover (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), all E-RABs of this UE (but not only the E-RABs in the message) are counted for this measurement to the target E-UTRAN cell. Each E-RAB attempted to establish is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs attempted to setup. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. The measurement name has the form ERAB.EstabIncHoAttNbr.QCI where QCI identifies the E-RAB level quality of service class. 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.2.1.9 |
2,111 | 28.3.2.2.4 Visited Country FQDN for N3IWF | 28.3.2.2.4.1 General The Visited Country FQDN for N3IWF, used by a roaming UE to determine whether the visited country mandates the selection of an N3IWF in this country, shall be constructed as described below. The Visited Country FQDN shall contain a MCC that uniquely identifies the country in which the UE is located. The Visited Country FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The fourth label shall be "visited-country". The third label shall uniquely identify the MCC of the visited country. The first and second labels shall be "n3iwf.5gc". The resulting Visited Country FQDN of N3IWF shall be constructed as follows: "n3iwf.5gc.mcc<MCC>.visited-country.pub.3gppnetwork.org" The <MCC> coding used in this FQDN shall be: - <MCC> = 3 digits As an example, the Visited Country FQDN for MCC 345 is coded in the DNS as: "n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org". 28.3.2.2.4.2 Visited Country Emergency N3IWF FQDN The Visited Country Emergency N3IWF FQDN, used by a roaming UE shall be constructed as specified for the Visited Country FQDN for N3IWF in clause 28.3.2.2.4.1, with the addition of the label "sos" before the labels "n3iwf.5gc". The resulting Visited Country Emergency N3IWF FQDN shall be constructed as follows: "sos.n3iwf.5gc.mcc<MCC>.visited-country.pub.3gppnetwork.org" As an example, the Visited Country FQDN for MCC 345 is coded in the DNS as: "sos.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org". 28.3.2.2.4.3 Visited Country FQDN for N3IWF supporting Onboarding UE onboarding for access to SNPN services is specified in clause 5.30.2.12 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. Visited Country FQDN for N3IWF supporting Onboarding encoding is constructed by adding a label "onboarding" to Visited Country FQDN for N3IWF FQDN (see clause 28.3.2.2.4.1), indicating that the N3IWF identified by the N3IWF identifier in the DNS response shall supports onboarding. Visited Country FQDN for N3IWF supporting Onboarding is constructed as follows: "onboarding.n3iwf.5gc.mcc<MCC>.visited-country. pub.3gppnetwork.org" As an example, the Visited Country FQDN for N3IWF supporting Onboarding for MCC 345, is coded in the DNS as: "onboarding.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.2.4 |
2,112 | 17.8.3 Transient Failures | Errors that fall within the transient failures category are used to inform a peer that a request could not be satisfied at the time it was received, but it may be satisfied in the future. The Result-Code AVP values defined in Diameter Base IETF RFC 6733 [111] are applicable. Also the following specific Gmb Experimental-Result-Code value is defined for transient failures: DIAMETER_ERROR_OUT_OF_RESOURCES (4121) This error covers the case when a MBMS Session Start procedure could not be performed due to a temporary resource shortage in the GGSN. The BM-SC may re-try later. | 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.8.3 |
2,113 | 9.3.1.2.4 TDD (Modulation and TBS index Table 2 and 4-bit CQI Table 2 are used) | For the parameters specified in Table 9.3.1.2.4-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.1.2.4-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 TTI for FDD, each available downlink transmission instance for TDD. Sub-bands of a size smaller than full size are excluded from the test. In this test, 4-bit CQI Table 2 in Table 7.2.3-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6], and Modulation and TBS index table 2 in Table 7.1.7.1-1A for PDSCH in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] are applied. Table 9.3.1.2.4-1 Sub-band test for TDD Table 9.3.1.2.4-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.3.1.2.4 |
2,114 | 4.1 Relationship between minimum requirements and test requirements | The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 36.521[ None ] -1 Annex F defines Test Tolerances. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in this specification to create Test Requirements. The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle. The Shared Risk principle is defined in ITU-R M.1545 [3]. | 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 | 4.1 |
2,115 | 8.21.1 NCR Integration Procedure | A high-level flow chart for NCR integration is shown in Figure 8.22.1-1: Figure 8.21.1-1: The integration procedure for NCR Phase 1: NCR-MT setup. In this phase, the NCR-MT of the NCR (re-)selects a cell that broadcasts the NCR support indicator in SIB1. It then connects to the network as a UE, by performing the RRC connection setup procedure with the gNB-CU, and authentication with the 5GC. The NCR-MT includes the NCR indication in the RRCSetupComplete message. The gNB selects an appropriate AMF for the NCR. Upon receiving the NCR authorization information from 5GC, the gNB-CU provides the authorization information to the gNB-DU. NOTE: The signalling flow for UE initial access procedure as shown in Figure 8.1-1/Figure 8.9.1-1 is used for the setup of the NCR-MT. Phase 2: NCR configuration. The gNB-CU may configure the NCR via RRC. Phase 3: NCR Start Operation. After the NCR is configured, it may start serving the UE(s). | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.21.1 |
2,116 | 4.3.1.2.1 Attempted outgoing inter-eNB handover preparations | This measurement provides the number of attempted outgoing inter-eNB handover preparations, the forwarded handovers for RN in DeNB are exclusive. CC. Transmission of the X2AP message HANDOVER REQUEST from the source eNB to the target eNB (see TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]), indicating the attempt of an outgoing inter-eNB handover preparation or on transmission of S1AP message HANDOVER REQUIRED to the MME (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]), the forwarded X2AP message HANDOVER REQUEST and S1AP message HANDOVER REQUIRED for RN in DeNB are exclusive. A single integer value. HO.InterEnbOutPrepAtt 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.2.1 |
2,117 | 4.1.1.6 Specific requirements for MS configured to use timer T3245 | The following requirement applies for an MS that is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]): When the MS adds a PLMN identity to the "forbidden PLMN list" or the "forbidden PLMNs for GPRS service" list or sets the SIM/USIM as invalid for non-GPRS services or GPRS services or both, and timer T3245 is not running, the MS shall start timer T3245 with a random value, uniformly drawn from the range between 12h and 24h. Upon expiry of the timer T3245, the MS shall erase the "forbidden PLMN list" and the "forbidden PLMNs for GPRS service" list and set the SIM/USIM to valid for non-GPRS services and GPRS services. When the lists are erased, the MS performs a cell selection according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. If the MS is switched off when the timer T3245 is running, the MS shall behave as follows when the MS is switched on and the SIM/USIM in the MS remains the same: - let t1 be the time remaining for T3245 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 β t. If t1 is equal to or less than t, then the MS will follow the behaviour as defined in the paragraph above upon expiry of the timer T3245. If the MS is not capable of determining t, then the MS shall restart the timer with the value t1. | 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.1.1.6 |
2,118 | 5.2.21.2.5 Nnsacf_NSAC_QuotaUpdate service operation | Service Operation name: Nnsacf_NSAC_QuotaUpdate Description: Updates the NSACF at the VPLMN with the maximum number of Registered UEs to be enforced and/or the maximum number of LBO PDU sessions to be admitted. Inputs, Required: S-NSSAI, PLMN ID, Requested Quota attribute type. The S-NSSAI parameter is the network slice subject to NSAC, which is the mapped S-NSSAI in HPLMN. The PLMN ID is the serving PLMN of the UE. The Requested Quota attribute type indicates if the requested quota is for local maximum number of Registered UEs and/or local maximum number of PDU sessions. Inputs, Optional: None. Outputs, Required: Result indication. The Result indication parameter includes the outcome of the operation. Outputs, Optional: A maximum number of allowed Registered UEs per S-NSSAI subject to NSAC and/or a maximum number of allowed PDU sessions per S-NSSAI subject to NSAC. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.21.2.5 |
2,119 | 5.4.3.3 Identification response by the UE | A UE shall be ready to respond to an IDENTITY REQUEST message at any time whilst in 5GMM-CONNECTED mode. Upon receipt of the IDENTITY REQUEST message: a) if the Identity type IE in the IDENTITY REQUEST message is not set to "SUCI", the UE shall send an IDENTITY RESPONSE message to the network. The IDENTITY RESPONSE message shall contain the identification parameters as requested by the network; and b) if the Identity type IE in the IDENTITY REQUEST message is set to "SUCI", the UE shall: 1) if timer T3519 is not running, generate a fresh SUCI as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], send an IDENTITY RESPONSE message with the SUCI, start timer T3519 and store the value of the SUCI sent in the IDENTITY RESPONSE message; and 2) if timer T3519 is running, send an IDENTITY RESPONSE message with the stored SUCI. | 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.4.3.3 |
2,120 | 4.4.3.2 Replay protection | Replay protection shall be supported for received NAS messages both in the AMF and the UE. However, since the realization of replay protection does not affect the interoperability between nodes, no specific mechanism is required for implementation. Replay protection assures that one and the same NAS message is not accepted twice by the receiver. Specifically, for a given 5G NAS security context, a given NAS COUNT value shall be accepted at most one time and only if message integrity verifies correctly. Replay protection is not applicable when 5G-IA0 is used. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.3.2 |
2,121 | 5.16.3.8.1 UE originating SMS for IMS Capable UEs supporting SMS over IP | To allow for appropriate domain selection for SMS delivery, it should be possible to provision UEs with the following HPLMN operator preferences on how an IMS enabled UE is supposed to handle SMS services: - SMS is not to be invoked over IP networks: the UE does not attempt to deliver SMS over IP networks. The UE attempts to deliver SMS over NAS signalling. - SMS is preferred to be invoked over IP networks: the UE attempts to deliver SMS over IP networks. If delivery of SMS over IP networks is not available, the UE attempts to deliver SMS over NAS signalling. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.3.8.1 |
2,122 | 5.3.17 Service Gap Control | The network may control the frequency UEs can transit from EMM-IDLE mode to EMM-CONNECTED mode via the service gap control (SGC) as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the network supports service gap control (SGC) feature and the service gap time value is available in the EMM context of the UE, the MME shall consider SGC as active for the UE. The UE and the network negotiate usage of the service gap control (SGC) feature during the attach and tracking area updating procedures: - the UE supporting service gap control indicates its support for service gap control in the ATTACH REQUEST and TRACKING AREA UPDATE REQUEST message. If the UE supports service gap control and the SGC is active for the UE, the MME shall include service gap timer T3447 value in the ATTACH ACCEPT message and TRACKING AREA UPDATE ACCEPT message (see clause 5.5.1.2 and clause 5.5.3.2). The UE shall store the service gap time value; and - for UEs that do not support the optional SGC feature when the network rejects mobility management signalling requests due to service gap control is active in the network, the mechanism for general NAS level mobility management congestion control as specified in clause 5.3.9 applies. The UE shall start the SGC timer T3447 when the NAS signalling connection is released and if: - the UE supports SGC feature, and the service gap timer value is available in the UE and does not indicate zero; and - the NAS signalling connection released was not established for: - paging; - attach requests without PDN connection request; or - tracking area update requests without "active" or "signalling active" flag set. If the SGC is active in the network, after the UE transitions from EMM-CONNECTED mode to EMM-IDLE mode except when the UE was in EMM-CONNECTED mode due to: - paging; - attach requests without PDN connection request; or - tracking area update requests without "active" or "signalling active" flag set, the network shall start the SGC timer T3447: - with the service gap time value available in the EMM context minus 4 minutes, if the UE supports SGC feature and the service gap time value has been sent to the UE with a non-zero value; or - with the service gap time value available in the EMM context if the UE does not support SGC feature. When the SGC timer T3447 is running, the network allows: - requests for emergency bearer services; - requests for exception data reporting; - attach requests without PDN connection request; - tracking area update requests without "active" or "signalling active" flag set; - requests from UEs that were received via NAS signalling connections established with RRC establishment cause "High priority access AC 11 β 15"; and - mobile terminated service requests triggered by paging and subsequent MO signalling or MO data, if any, until the UE enters EMM-IDLE mode. If the MME determines that the UE operating in single-registration mode has performed an inter-system change from S1 mode to N1 mode and the timer T3447 is running in the MME, the MME stops the T3447. Upon inter-system change from N1 mode to S1 mode, if the UE supports service gap control, T3447 is running in the UE, and the T3447 value is included in the ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message received from the MME (see clause 5.5.1.2 and clause 5.5.3.2), the UE shall keep T3447 running. Additionally, the UE shall store and replace the currently stored T3447 value with the received T3447 value. Upon expiry of the running T3447 timer, the UE shall use the new value when starting T3447 again. The UE or the network with a running service gap timer shall keep the timer running when the UE transits from EMM-IDLE mode to EMM-CONNECTED mode. NOTE: If the UE transitions from EMM-IDLE mode to EMM-CONNECTED mode due to attach request without PDN connection request or tracking area update request without "active" or "signalling active" flag set, the UE initiates no further MO signalling except for tracking area update request without "active" or "signalling active" flag set until the UE receives network-initiated signalling (e.g. DOWNLINK NAS TRANSPORT message for MT SMS) or MT data over user plane, or after the UE has moved to EMM-IDLE state and the service gap timer is not running. If the timer T3447 is running when the UE enters state EMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE remains the same, then timer T3447 is kept running until it expires. If the UE is switched off when the timer T3447 is running, the UE shall behave as follows when the UE is switched on and the USIM in the UE remains the same: - let t1 be the time remaining for T3447 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 β t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.17 |
2,123 | 28.7.7 NAI used by N5CW devices via trusted non-3GPP access 28.7.7.0 General | While performing the EAP authentication procedure when a non 5G capable over WLAN (N5CW) device attempts to register to 5GCN via a trusted non-3GPP access network in a selected PLMN (see clause 4.12 b in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [120]), the N5CW device shall derive a NAI from the identity of the selected PLMN in the following format: "<5G_device_unique_identity>@nai.5gc-nn.mnc<MNC>.mcc<MCC>.3gppnetwork.org"; where: a) the username part <5G_device_unique_identity> is to identify the N5CW device and contains either: - SUCI as defined as the username part of the NAI format in clause 28.7.3, if the UE is not registered to 5GCN via NG-RAN; or - 5G-GUTI as defined as the username part of the NAI format in clause 28.7.8, if the N5CW device is registered to 5GCN via NG-RAN; and b) the label '5gc-nn' in the realm part indicates the NAI is used by N5CW devices via trusted non-3GPP access. <MNC> and <MCC> identify the PLMN (either HPLMN or VPLMN) to which the N5CW device attempts to connect via the trusted non-3GPP access network as described in clause 6.3.12 in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. While performing the EAP authentication procedure when a non 5G capable over WLAN (N5CW) device attempts to register to 5GCN via a trusted non-3GPP access network in a selected SNPN (see clause 5.30.2.13 in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]), the N5CW device shall derive a NAI from the identity of the selected SNPN in the following format: "<5G_device_unique_identity>@nai.5gc-nn.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org"; where: a) the username part <5G_device_unique_identity> is to identify the N5CW device and contains either: - SUCI as defined as the username part of the NAI format in clause 28.7.3; or - 5G-GUTI as defined as the username part of the NAI format in clause 28.7.8, if the N5CW device is registered to 5GCN via NG-RAN; and b) the label '5gc-nn' in the realm part indicates the NAI is used by N5CW devices via trusted non-3GPP access. <MNC>, <MCC> and <NID> identify the SNPN to which the N5CW device attempts to connect via the trusted non-3GPP access network. NOTE: As defined in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [124], an N5CW device is authenticated using EAP-AKA', thus, it has a USIM that stores the HPLMN identity. In roaming scenarios, the NAI shall use the decorated NAI format as specified in clause 28.7.7.1 or 28.7.7.2. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.7.7 |
2,124 | 5.5.3.2.6A Abnormal cases in the UE, SMS services not accepted | The UE shall proceed as follows: 1) if the tracking area update was successful for EPS services only and the TRACKING AREA UPDATE ACCEPT message contained a value included in the SMS services status IE not treated in clause 5.5.3.2.4A, the UE shall proceed as follows: a) The UE shall stop timer T3430 if still running. The tracking area updating attempt counter shall be incremented, unless it was already set to 5; b) If the tracking area updating attempt counter is less than 5: - the UE shall start timer T3411, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. When timer T3411 expires the normal tracking area updating procedure for EPS services and "SMS only" or the combined tracking area updating procedure for EPS services and "SMS only" is triggered; c) If the tracking area updating attempt counter is equal to 5: - the UE shall start timer T3402, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. When timer T3402 expires the normal tracking area updating procedure for EPS services and "SMS only" or the combined tracking area updating procedure for EPS services and "SMS only" is triggered; and 2) otherwise, the abnormal cases specified in clause 5.5.3.2.6 apply. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.3.2.6A |
2,125 | 5.21.2.2.2 AMF planned removal procedure without UDSF | An AMF can be taken graciously out of service as follows: - The AMF can forward registered UE contexts, UE contexts grouped by the same GUAMI value, to target AMF(s) within the same AMF set, including the source AMF name used for redirecting UE's MT transaction. The UE context includes the per AMF Set unique AMF UE NGAP ID. In order for the AMF planned removal procedure to work graciously, 5G-S-TMSI shall be unique per AMF set. If there are ongoing transactions (e.g. N1 procedure) for certain UE(s), AMF forwards the UE context(s) to the target AMF upon completion of an ongoing transaction. - The AMF deregister itself from NRF indicating due to AMF planned removal. NOTE 1: It is assumed that the UE contexts from the old AMF include all event subscriptions with peer CP NFs. NOTE 2: Before removal of AMF the overload control mechanism can be used to reduce the amount of ongoing transaction. An AMF shall be able to instruct the 5G-AN that it will be unavailable for processing transactions by including GUAMI(s) configured on this AMF and its corresponding target AMF(s). The target AMF shall be able to update the 5G-AN that the UE(s) served by the old GUAMI(s) are now served by target AMF. The target AMF provides the old GUAMI value that the 5G-AN can use to locate UE contexts served by the old AMF. Upon receipt of the indication that an old AMF is unavailable, 5G-AN shall take the following action: - 5G-AN should mark this AMF as unavailable and not consider the AMF for selection for subsequent N2 transactions until 5G-AN learns that it is available (e.g. as part of discovery results or by configuration). The associated GUAMIs are marked as unavailable. - During NGAP Setup, the AMF may include an additional indicator that the AMF will rebind or release the NGAP UE-TNLA-binding on per UE-basis. If that indicator is included and the 5G-AN supports timer mechanism, the 5G-AN starts a timer to control the release of NGAP UE-TNLA-binding(s). For the duration of the timer or until the AMF releases or re-binds the NGAP UE-TNLA-binding, the AN does not select a new AMF for subsequent transactions. Upon timer expiry, the 5G-AN releases the NGAP UE-TNLA-binding(s) with the corresponding AMF for the respective UE(s), for subsequent N2 message, the 5G-AN uses GUAMI which points to the target AMF that replaced the old unavailable AMF, to forward the N2 message to the corresponding target AMF(s). NOTE 3: For UE(s) in CM-CONNECTED state, after indicating that the AMF is unavailable for processing UE transactions and including an indicator that the AMF releases the NGAP UE-TNLA-binding on a per UE-basis, the AMF can either trigger a re-binding of the NGAP UE associations to an available TNLA on a different AMF within the same AMF set or use the NGAP UE-TNLA-binding per UE release procedure defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3] to release the NGAP UE-TNLA-binding on a per UE-basis while requesting the AN to maintain N3 (user plane connectivity) and UE context information. NOTE 4: The support and the use of timer mechanism in 5G-AN is up to implementation. If the instruction does not include the indicator, for UE(s) in CM-CONNECTED state, 5G-AN considers this as a request to release the NGAP UE UE-TNLA-binding(s) with the corresponding AMF for the respective UE(s) while maintaining N3 (user plane connectivity) and UE context information. For subsequent N2 message, the 5G-AN uses GUAMI based resolution which points to the target AMF that replaced the old unavailable AMF, to forward the N2 message to the corresponding target AMF(s). - For UE(s) in CM-IDLE state, when it subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a 5G S-TMSI or GUAMI, based resolution the 5G-AN uses 5G S-TMSI or GUAMI which points to the target AMF that has replaced the old unavailable AMF and, the 5G-AN forwards N2 message. An AMF shall be able to instruct other peer CP NFs, subscribed to receive such a notification, that it will be unavailable for processing transactions by including GUAMI(s) configured on this AMF and its corresponding target AMF(s). The target AMF shall update the CP NF that the old GUAMI(s) is now served by target AMF. The old AMF provides the old GUAMI value to target AMF and the target AMF can use to locate UE contexts served by the old AMF. If the CP NFs register with NRF for AMF unavailable notification, then the NRF shall be able to notify the subscribed NFs to receive such a notification (along with the corresponding target AMF(s)) that AMF identified by GUAMI(s) will be unavailable for processing transactions. Upon receipt of the notification that an AMF is unavailable, the other CP NFs shall take the following action: - Mark this AMF and its associated GUAMI(s) as unavailable while not changing the status of UE(s) associated to this AMF (UE(s) previously served by the corresponding AMF still remain registered in the network), and AMF Set information. - For the UE(s) that were associated to the corresponding AMF, when the peer CP NF needs to initiate a transaction towards the AMF that is marked unavailable and the old unavailable AMF was replaced by the target AMF, CP NF should forward the transaction together with the old GUAMI to the target AMF(s). If CP NF needs to send a notification to new AMF which is associated with a subscription from the old AMF, the CP NF shall exchange the old AMF information embedded in the Notification Address with the new AMF information, and use that Notification Address for subsequent communication. NOTE 5: If the CP NF does not subscribe to receive AMF unavailable notification (either directly with the AMF or via NRF), the CP NF may attempt forwarding the transaction towards the old AMF and detect that the AMF is unavailable after certain number of attempts. When it detects unavailable, it marks the AMF and its associated GUAMI(s) as unavailable. The following actions should be performed by the target AMF: - To allow AMF process ongoing transactions for some UE(s) even after it notifies unavailable status to the target AMF, the target AMF keeps the association of the old GUAMI(s) and the old AMF for a configured time. During that configured period, if target AMF receives the transaction from the peer CP NFs and cannot locate UE context, it rejects the transaction with old AMF name based on that association, and the indicated AMF is only used for the ongoing transaction. The peer CP NFs resend the transaction to the indicated AMF only for the ongoing transaction. For subsequent transactions, peer CP NFs should use the target AMF. When the timer is expired, the target AMF deletes that association information. - When there is a transaction with the UE the target AMF uses SUPI, 5G-GUTI or AMF UE NGAP ID to locate UE contexts and processes the UE transactions accordingly and updates the 5G-GUTI towards the UE, if necessary. For UE(s) in CM-CONNECTED state, it may also update the NGAP UE association with a new AMF UE NGAP ID towards the 5G-AN and replace the GUAMI in the UE context stored at the 5G-AN with the new GUAMI associated with the newly selected AMF if the 5G-GUTI has been updated. The AMF also informs the NG-RAN of the new UE Identity Index Value (derived from the new 5G-GUTI). - Target AMF shall not use old GUAMI to allocate 5G-GUTI for UE(s) that are being served by Target AMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.2.2.2 |
2,126 | 8.9.9.2 BH RLC Channel Mapping on BAP Layer | When traffic is forwarded on BAP layer as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2], the IAB-node performs the BH RLC channel mapping as defined in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [22]. The BH RLC channel mapping information is configured by the IAB-donor-CU. The BH RLC channel mappings can be configured as part of the UE Context Setup or UE Context Modification procedures. They may also be configured via the non-UE-associated BAP Configuration procedure. NOTE: Implementation must ensure the avoidance of potential race conditions, i.e. that no conflicting configurations are concurrently performed using UE-associated and non-UE-associated procedures. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.9.2 |
2,127 | 5.15.12 Support of subscription-based restrictions to simultaneous registration of network slices 5.15.12.1 General | The subscription information for a UE may include for each S-NSSAI Network Slice Simultaneous Registration Group (NSSRG) information constraining which S-NSSAIs can be simultaneously provided to the UE in the Allowed NSSAI. When S-NSSAIs have associated NSSRG information, then the S-NSSAIs in the Allowed NSSAI shall share at least one NSSRG. The NSSRG information, defining the association of S-NSSAIs to NSSRG, is provided as an additional and separate information. If the optional NSSRG information is not present for the S-NSSAIs of a subscription, and other restrictions do not apply e.g. availability at a specific location, then it is assumed that all the S-NSSAIs in the subscription information can be simultaneously provided to the UE in the Allowed NSSAI. However, if NSSRG information is present in the subscription information, at least one NSSRG shall be associated with each of the S-NSSAIs in the subscription information. At any time, if the AMF has received subscription information for a UE that includes NSSRG information, the Allowed NSSAI for the UE can only include S-NSSAIs which share a common NSSRG. NOTE 1: The AMF enforces NSSRG only for the access(es) the UE registered to the AMF. When the UE is registered to different PLMNs over 3GPP access and non-3GPP access, the AMF in one access cannot enforce a common NSSRG over both accesses. The default S-NSSAIs, if more than one is present, are associated with the same NSSRGs, i.e. the UE is always allowed to be registered with all the default S-NSSAIs simultaneously. The HPLMN only sends S-NSSAIs sharing all the NSSRGs of the Default S-NSSAIs to a non-supporting VPLMN as part of the subscription information, i.e. in addition to the default S-NSSAI(s), the HPLMN may send any other subscribed S-NSSAI which shares at least all the NSSRG defined for the default S-NSSAI(s), and the HPLMN sends no NSSRG information to the VPLMN. A subscription information that includes NSSRG information shall include at least one default S-NSSAI. A supporting AMF/NSSF, when it receives a Requested NSSAI, evaluates the S-NSSAIs of the HPLMN (in the mapping information of the Requested NSSAI, when a mapping information is applicable) based on any received NSSRG information for these S-NSSAIs, to determines whether they can be provided together in the Allowed NSSAI. NOTE 2: An HPLMN enabling support of subscription-based restrictions to simultaneous registration of network slices for a Subscriber, can set the subscribed S-NSSAI(s) already in the subscription information before the NSSRG information was added to the subscription information, to have the same NSSRGs defined for the default S-NSSAI(s) if it has to continue to support the same service behaviour for these S-NSSAIs. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.12 |
2,128 | 5.8.2.13.2 Support for unicast traffic forwarding update due to UE mobility | To enable the service continuity when the PSA UPF serving the UE changed, the following applies: - Keep the UE address unchanged if N6-based forwarding is not used. - Configure the UE's N4 Session with N4 rules (PDR, FAR) to detect and forward the traffic to this UE via its PDU Session tunnel(i.e. N3 tunnel) on the target PSA UPF. - If N19-based forwarding is applied: To switch the traffic towards this UE from the source PSA UPF to the target PSA UPF for N19-based forwarding, the SMF deletes the N4 rule (PDR) that detects the traffic towards this UE in the group-level N4 Session at UPFs involved in the 5G VN group (except the source PSA UPF), then adds or updates the PDR that detects the traffic towards this UE with the FAR containing the N19 tunnel information of the target PSA UPF in the group-level N4 Session at UPFs involved in the 5G VN group (except the target PSA UPF). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.13.2 |
2,129 | 5.3.19A.2 UE operating in SNPN access operation mode | The following requirements apply for a UE that is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]). When the UE adds an SNPN to the "permanently forbidden SNPNs" list or "temporarily forbidden SNPNs" list which are, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, or sets the selected entry of the "list of subscriber data" or the selected PLMN subscription as invalid for 3GPP access or non-3GPP access, and timer T3245 (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]) is not running, the UE shall start timer T3245 with a random value, uniformly drawn from the range between 12h and 24h. When the UE adds an SNPN to the "permanently forbidden SNPNs for access for localized services in SNPN" list or "temporarily forbidden SNPNs for access for localized services in SNPN" list which are associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription for 3GPP access or non-3GPP access, and timer T3245 is not running: a) if there is no next valid time period for the SNPN, the UE shall start timer T3245 with a random value, uniformly drawn from the range between 12h and 24h; or b) if there is next valid time period for the SNPN, the UE shall start timer T3245 with a random value uniformly drawn from the range between the start time point and the end time point of the next valid time period for localized services in SNPN. NOTE 1: The random value to calculate the value of timer T3245 can be UE implementation-specific value for the UE to perform SNPN selection for localized services in SNPN and receive localized services in the SNPN before the valid time of localized services ends. Upon expiry of the timer T3245, the UE shall erase the "permanently forbidden SNPNs" list(s) and "temporarily forbidden SNPNs" list(s) and set the selected entry of the "list of subscriber data" or the selected PLMN subscription to valid for 3GPP access and non-3GPP access. When the lists are erased, the UE performs cell selection according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28]. If the UE is switched off when the timer T3245 is running, the UE shall behave as follows when the UE is switched on and the selected entry of the "list of subscriber data" or the selected PLMN subscription remain the same: - let t1 be the time remaining for T3245 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 β t. If t1 is equal to or less than t, then the UE will follow the behaviour as defined in the paragraph above upon expiry of the timer T3245. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.19A.2 |
2,130 | 9.11.4.9 Maximum number of supported packet filters | The purpose of the Maximum number of supported packet filters information element is for the UE to indicate to the network the maximum number of packet filters, associated with signaled QoS rules, that can be supported by the UE for the PDU session that is being established, when the PDU session type "IPv4", "IPv6", "IPv4v6" or "Ethernet". The Maximum number of supported packet filters is coded as shown in figure 9.11.4.9.1 and table 9.11.4.9.1. The Maximum number of supported packet filters is a type 3 information element with a length of 3 octets. Figure 9.11.4.9.1: Maximum number of supported packet filters information element Table 9.11.4.9.1: Maximum number of supported packet filters information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.9 |
2,131 | 5.8.9.1a.4 Sidelink SRB addition | The UE shall: 1> if transmission of PC5-S message for a specific destination is requested by upper layers for sidelink SRB: 2> establish PDCP entity, RLC entity and the logical channel of a sidelink SRB for PC5-S message, as specified in clause 9.1.1.4; 1> if transmission of discovery message for a specific destination is requested by upper layers for sidelink SRB: 2> establish PDCP entity, RLC entity and the logical channel of a sidelink SRB4 for discovery message, as specified in clause 9.1.1.4; 1> if a PC5-RRC connection establishment for a specific destination is indicated by upper layers: 2> establish PDCP entity, RLC entity and the logical channel of a sidelink SRB for PC5-RRC message of the specific destination, as specified in clause 9.1.1.4; 2> consider the PC5-RRC connection is established for the destination. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1a.4 |
2,132 | 5.2.2.2.7 Namf_Communication_N1N2MessageTransfer service operation | Service operation name: Namf_Communication_N1N2MessageTransfer. Description: CN NF request to transfer downlink N1 and/or N2 message to the UE and/or AN through the AMF. Input, Required: CN NF ID, Message type (N1 or N2 or both), Message Container (s) where at least one of the message containers (N1 or N2) is required. Input, Optional: last message indication, Session ID, Paging Policy Indicator, ARP, Area of validity for the N2 SM information, 5QI, N1N2TransferFailure Notification Target Address, type of N2 SM information, type of N2 NRPPa information, Extended Buffering Support. MA PDU session Accepted indication, target access type (3GPP access or non-3GPP access), selected alternative H-SMF ID. Namf_Communication_N1N2MessageTransfer supports the transfer of only one N2 message. N2 SM information and N2 NRPPa information are mutually exclusive. Output, Required: Result indication. Output, Optional: Redirection information, Estimated Maximum wait time. If the UE is in CM-IDLE state, the AMF initiates the network triggered Service Request procedure as specified in clause 4.2.3.3 and responds to the consumer NF with a result indication, "attempting to reach UE". Otherwise, the AMF responds to the consumer NF, with a Namf_Communication_N1N2MessageTransfer response, providing a result indication of whether the AMF was able to successfully transfer the N1 and/or the N2 message towards the UE and/or the AN. A result indication of "N1/N2 transfer success" does not mean that N1 message is successfully received by the UE. It only means that the AMF is able to successfully send the N1 or N2 message towards the AN. The "Area of validity for the N2 SM information", if included is used by the AMF to determine whether the N2 SM information provided by the consumer NF can be used towards the AN based on the current location of the UE. If the location of the UE is outside the "Area of validity for the N2 SM information" indicated, the AMF shall not send the N2 SM information to the AN. If the consumer NF knows that a specific downlink N1 message is the last message to be transferred in this transaction, the consumer NF shall include the last message indication in the Namf_Communication_N1N2MessageTransfer service operation so that the AMF knows that the no more downlink N1 message need to be transferred for this transaction. The CN NF is implicitly subscribed to be notified of N1N2TransferFailure by providing the N1N2TransferFailure Notification Target Address. When AMF detects that the UE fails to respond to paging, or the UE responds to paging with a Reject Paging Indication, or the AMF determines the UE is temporarily unreachable e.g. due to extended idle mode DRX or MICO mode, the AMF invokes the Namf_Communication_N1N2TransferFailureNotification to provide the failure notification to the location addressed by N1N2TransferFailure Notification Target Address. The "Extended Buffering applies" indication, if included, is used by the AMF to include "Estimated Maximum Wait time" in Namf_Communication_N1N2 TransferFailureNotification if invoked due to the UE being unreachable. If the result of the service operation fails, the AMF shall set the corresponding cause value in the result indication which can be used by the NF consumer for further action. If the related UE is not served by AMF and the AMF knows which AMF is serving the UE, the AMF provides redirection information which can be used by the consumer NF to resend UE related message to the AMF that serves the UE. If the consumer NF is a SMF and he request includes N2 SM information, the SMF indicates the type of N2 SM information. If the consumer NF is a LMF and the request includes N2 NRPPa information, the LMF indicates the type of N2 NRPPa information. NOTE: The actual N2 SM information or N2 NRPPa information is not interpreted by the AMF. The selected alternative H-SMF ID information may be provided as described in clause 4.3.2.2.2. The Small Data Rate Control Status is included if a PDU Session is being released and the UPF or NEF provided Small Data Rate Control Status when the PDU Session was released for the AMF to store. For the usage of MA PDU session Accepted indication and target access type (3GPP access or non-3GPP access) see clauses 4.22.2, 4.22.3, 4.22.6.3 and 4.22.9.4. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.7 |
2,133 | 8.4.4.2 MN initiated SN Modification with SCG Activation or Deactivation | Figure 8.4.4.2-1: SCG Activation or Deactivation in MN initiated SN Modification procedure 1. SCG is deactivated or activated. 2. The MN sends the SN Modification Request message to the SN, indicates the request of SCG activation or deactivation. 3. The SN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the SN-CU-UP to notify the SCG activation or deactivation. 4. The SN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the SN-CU-CP. 5. The SN-CU sends the UE CONTEXT MODIFICATION REQUEST message to the SN-DU to indicate the request of SCG activation or deactivation. 6. The SN-DU may send the UE CONTEXT MODIFICATION RESPONSE message to the SN-CU, indicates the SCG status. 7. The SN-CU-CP sends the BEARER CONTEXT MODIFICATION REQUEST message to the SN-CU-UP to notify the SCG status. 8. The SN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the SN-CU-CP. NOTE: Step 7 and 8 may be skipped in case the SN-DU accepted the SCG activation or deactivation request. 9. The SN sends the SN Modification Request Acknowledge message towards the MN, indicates the SCG status. 10. The MN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the MN-CU-UP to notify the SCG status. 11. The MN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the MN-CU-CP. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.4.4.2 |
2,134 | 4.3.3.1 Charging Trigger Function (CTF) | The Charging Trigger Function (CTF) interacts with the Charging Function (CHF) of the Converged Charging System (CCS) using Nchf interface for consuming CHF services as defined in TS 32.290[ Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) ] [57]: - converged charging (Nchf_ConvergedCharging service) wich operates: - with quota management (online charging); - without quota management (offline charging); - offline only charging (Nchf_OfflineOnlyCharging service). The behaviour of the Charging Trigger Function (CTF) embedded in the service element, sub-system component or Core Network element is specified in the respective middle tier charging specifications. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.3.1 |
2,135 | 4.5.3.1 Release of associated RR connection | If all MM connections are released by their CM entities, and no RRLP procedure (see 3GPP TS 44.031[ None ] [23b]) and no LCS procedure over RRC (see 3GPP TS 25.331[ None ] [23c]) is ongoing, the mobile station shall set timer T3240 and enter the state WAIT FOR NETWORK COMMAND, expecting the release of the RR connection. If all MM connections are released by their CM entities and an RRLP procedure or LCS procedure over RRC is ongoing, the MS shall start the timer T3241 and enter the state RR CONNECTION RELEASE NOT ALLOWED. If the MS is expecting the release of the RR connection in MM state WAIT FOR NETWORK COMMAND and an RRLP procedure or LCS procedure over RRC is started, the MS shall stop the timer T3240, start the timer T3241 and enter the state RR CONNECTION RELEASE NOT ALLOWED. If the MS is in MM state RR CONNECTION RELEASE NOT ALLOWED and the ongoing RRLP procedure or LCS procedure over RRC is finished, the MS shall stop the timer T3241, reset and start the timer T3240 and shall enter the state WAIT FOR NETWORK COMMAND. If the MS receives the "Extended wait time" for CS domain from the lower layers when no location updating or CM service request procedure is ongoing, the MS shall ignore the "Extended wait time". In the network, if the last MM connection is released by its user, the MM sublayer may decide to release the RR connection. The RR connection may be maintained by the network, e.g. in order to establish another MM connection. If the RR connection is not released within a given time controlled by the timer T3240 or T3241, the mobile station shall abort the RR connection. In both cases, either after a RR connection release triggered from the network side or after a RR connection abort requested by the MS-side, the MS shall return to MM IDLE state; the service state depending upon the current update status as specified in subclause 4.2.3. If the UE determines a service state in which a Location Update procedure is required, the UE shall reset the location update attempt counter and immediately start the Location Updating procedure as specified in subclause 4.4.4. | 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.5.3.1 |
2,136 | 5.2.6.9.5 Nnef_AFsessionWithQoS_Update service operation | Service operation name: Nnef_AFsessionWithQoS Update Description: The consumer requests the network to update the parameters for an AF session for a UE or a list of UEs. Inputs, Required: Transaction Reference ID. Inputs, Optional: Flow description information (as described in clause 6.1.3.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) or External Application Identifier, QoS Reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], time period, traffic volume, Alternative Service Requirements (containing one or more QoS Reference parameters or Requested Alternative QoS Parameter Sets in a prioritized order), QoS Monitoring parameter(s) as defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Reporting frequency, Target of reporting and optional an indication of local event notification as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Only applicable for a single UE AF session: flow direction, Burst Arrival Time at UE (uplink) or UPF (downlink), Periodicity as described in clause 5.27.2 or clause 5.37.8.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Time domain, Survival Time, Packet Delay Variation requirements as described in clause 6.1.3.26 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], BAT Window or Capability for BAT adaptation, Periodicity Range, PDU Set QoS Parameters as described in clause 5.7.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Protocol Description (as described in clause 5.37.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), updated information for the Multi-modal Service Requirements information as described in clause 6.1.3.27.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Only applicable for a Multi-member AF session: a list of UE addresses (as described in clause 4.15.6.13), Consolidated Data Rate Threshold, a list of UE addresses subject to Consolidated Data Rate monitoring. NOTE 1: In this Release, when a list of UE addresses is provided, the Flow description information is common for all UE addresses in the list. Further details are described in clause 4.15.6.13.2. NOTE 2: If Consolidated Data Rate Threshold is provided, the QoS Monitoring parameter(s) indicates the Guaranteed Bitrate shall be provided. NOTE 3: When the AF request is for Consolidated Data Rate monitoring is set for event reporting, the QoS Flow data rate reporting for the list of UE addresses is provided to the AF by the NEF only when the Consolidated Data Rate threshold is exceeded. NOTE 4: When the Consolidated Data Rate threshold is provided, it applies to the list of UE addresses by default. However, if the list of UE addresses subject for Consolidated Data Rate monitoring is also provided, then such list has to be the subset of the list of UE addresses. NOTE 5: If AF wants to terminate the Consolidated Data Rate monitoring, AF does not include the Consolidated Data Rate threshold in the AF request. Outputs, Required: Success or Failure. Failure Cause in case of Failure., Transaction Reference ID if a list of UE is targeted. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.9.5 |
2,137 | 4.3.4.2 UE or network requested PDU Session Release for Non-Roaming and Roaming with Local Breakout | Figure 4.3.4.2-1 captures both the UE Requested PDU Session Release procedure and the network requested PDU Session Release procedure. The procedure allows the UE to request the release of one PDU Session. The procedure also allows the AMF, the SMF or the PCF to initiate the release of a PDU Session. In the case of LBO, the procedure is as in the case of non-roaming with the difference that the AMF, the SMF, the UPF and the PCF are located in the visited network. Figure 4.3.4.2-1: UE or network requested PDU Session Release for non-roaming and roaming with local breakout 1. The procedure is triggered by one of the following events: 1a. (UE requested) The UE initiates the UE Requested PDU Session Release procedure by the transmission of an NAS message (N1 SM container (PDU Session Release Request (PDU session ID)), PDU Session ID) message. The NAS message is forwarded by the (R)AN to the AMF with an indication of User Location Information. This message is relayed to the SMF corresponding to the PDU Session ID via N2 and the AMF. The AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation and provides the N1 SM container to the SMF together with User Location Information (ULI) received from the (R)AN. NOTE 1: Depending on the Access Type, when the UE is in CM-IDLE state, the UE can trigger a Service Request procedure before being able to release the PDU Session. 1b. (PDU Session Release initiated by the PCF) The PCF may invoke an SM Policy Association Termination procedure as defined in clause 4.16.6 to request the release of the PDU Session. 1c. The AMF may invoke the Nsmf_PDUSession_ReleaseSMContext service operation to request the release of the PDU Session in the case of mismatch of PDU Session status between UE and AMF or other cases where neither N1 nor N2 SM signalling is needed before the releasing of SM context. 1d. (R)AN may decide to indicate to the SMF that the PDU Session related resource is released, e.g. when all the QoS Flow(s) of the PDU Session are released. NOTE 2: In this case, it's up to SMF to decide whether to keep the PDU Session with user plane connection deactivated or release the PDU Session. 1e. (PDU Session Release initiated by the SMF). The SMF may decide to release a PDU Session under the following scenarios: - Based on a request from the DN (cancelling the UE authorization to access to the DN); - Based on a request from the UDM (subscription change) or from the CHF; - If the SMF received an event notification from the AMF that the UE is out of LADN service area; - Based on locally configured policy (e.g. the release procedure may be related with the UPF re-allocation for SSC mode 2 / mode 3); - If the SMF is notified by the (R)AN that the PDU Session resource establishment has failed during mobility procedure; - The SMF initiates release of an emergency PDU Session when the UPF reports detection of PDU Session inactivity for a specified period as specified in clause 4.4.2.2; - Based on PDU Session inactivity report from the UPF if the S-NSSAI of a PDU Session for non-roaming subscribers is subject to usage control as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; or - If the SMF is notified by the AMF that the S-NSSAI of the PDU Session with SSC mode 1 or SSC mode 2 is to be replaced with Alternative S-NSSAI, and if the SMF determines that a new PDU Session is to be established on the Alternative S-NSSAI, the SMF initiates release of the PDU Session, as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 1f. The AMF may invoke the Nsmf_PDUSession_UpdateSMContext service operation with a release indication to request the release of the PDU Session where N1 or N2 SM signalling may be needed before releasing the SM context with appropriate cause value (e.g. due to a change of the set of network slices for a UE where a network slice instance is no longer available as described in clause 5.15.5.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] or the AAA Server triggered Network Slice-Specific Re-authentication and Re-authorization procedure fails as specified in clause 4.2.9.2 or the AAA Server triggered Slice-Specific Authorization Revocation takes place as specified in clause 4.2.9.4 or AMF determines that Control Plane Only indication associated with PDU Session is not applicable any longer as described in clause 5.31.4.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) or the MBSR authorization state is changed from "authorized" to "not authorized" as described in clause 5.35A.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] or the Network Slice instance is congested or not available as described in clause 5.15.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the SMF receives one of the triggers in step 1a, 1b, 1c, 1e, or 1f, the SMF starts PDU Session Release procedure. If the cause value in step 1f indicates the Network Slice instance is congested or not available, the SMF triggers the impacted UE(s) to establish new PDU session(s) associated with the same S-NSSAI by using the procedures for PDU Session(s) of SSC mode 2 or SSC mode 3 as defined in clause 4.3.5. If interworking with TSN deployed in the transport network is supported the SMF/CUC shall initiate the release of TN streams via UNI. 2. The SMF releases the IP address / Prefix(es) that were allocated to the PDU Session and releases the corresponding User Plane resources: 2a. The SMF sends an N4 Session Release Request (N4 Session ID) message to the UPF(s) of the PDU Session. The UPF(s) shall drop any remaining packets of the PDU Session and release all tunnel resource and contexts associated with the N4 Session. If interworking with TSN deployed in the transport network is supported and the UPF supports CN-TL and TN streams are associated with the PDU session, the SMF/CUC shall initiate to the CN-TL the deletion of TN stream configurations. 2b. The UPF(s) acknowledges the N4 Session Release Request by the transmission of an N4 Session Release Response (N4 Session ID, [Small Data Rate Control Status], [APN Rate Control Status]) message to the SMF. If UPF/CN-TL has performed the deletion of TN stream based on the request received from the SMF/CUC in step 2a, the UPF/CN-TL shall confirm the deletion of TN stream configurations. The UPF includes Small Data Rate Control Status if the PDU Session used Small Data Rate Control. If a NEF has been selected as anchor of the Control Plane CIoT 5GS Optimisation enabled PDU session which is Unstructured PDU Session Type as described in clause 4.3.2.2 and the SMF-NEF Connection is released for this PDU Session. If interworking with TSN deployed in the transport network is supported and the NG-RAN supports AN-TL and TN streams are associated with the released PDU session, the SMF/CUC shall initiate to the AN-TL the deletion of TN stream configurations. NOTE 3: If there are multiple UPFs associated with the PDU Session (e.g. due to the insertion of UL CL or Branching Point, or redundant I-UPFs if the redundant I-UPFs are used for URLLC), the Session Release Request procedure (steps 2a and 2b) is done for each UPF. In order to avoid charging of PDUs that later get dropped, the SMF performs the N4 Session Release first with the UPF(s) performing usage reporting, before releasing the other UPF(s) that forward traffic for the same user plane resources. 3 If the PDU Session Release is initiated by the PCF and SMF and the SMF has been notified by the AMF that UE is unreachable, e.g. due to the UE is in MICO mode or periodical registration failure, the procedure continues in step 11 by SMF notifying the AMF that the PDU Session is released by invoking the Nsmf_PDUSession_SMContextStatusNotify. The rest of step 3 and the steps 4-10 are skipped. If the PDU Session Release procedure was triggered by steps 1a, 1b, 1d or 1e above, the SMF creates an N1 SM including PDU Session Release Command message (PDU Session ID, Cause, Alternative S-NSSAI). The Cause may indicate a trigger to establish a new PDU Session with the same characteristics (e.g. when procedures related with SSC mode 2 are invoked). .If the cause value indicates that a PDU Session re-establishment on the Alternative S-NSSAI is required the PDU Session Release Command message also includes the Alternative S-NSSAI. The UE establishes a new PDU Session on the Alternative S-NSSAI, as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the User Plane connection of the PDU Session is activated, the message sent by the SMF to the AMF shall include N2 SM Resource Release request. If the User Plane connection of the PDU Session is not activated, the message sent by the SMF to the AMF shall not include N2 SM Resource Release request. NOTE 4: SSC modes are defined in clause 5.6.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 3a. (If the PDU Session Release is initiated by the UE in step 1a or has been triggered by (R)AN in step 1d) The SMF responds to the AMF with the Nsmf_PDUSession_UpdateSMContext response (N2 SM Resource Release request, N1 SM container (PDU Session Release Command)). N2 SM Resource Release request is included if the PDU Session Release is initiated by the UE and if the UP connection of the PDU Session is active. Neither N2 SM Resource Release request nor N1 SM container is included if the PDU Session Release is triggered by (R)AN and the SMF decides to keep the PDU session with user plane connection deactivated and the subsequent steps are skipped. 3b. If the PDU Session Release is initiated by the SMF or the PCF, the SMF invokes the Namf_Communication_N1N2MessageTransfer service operation (N1 SM container (PDU Session Release Command), skip indicator). If the UP connection of the PDU Session is active, the SMF shall also include the N2 Resource Release request (PDU Session ID) in the Namf_Communication_N1N2MessageTransfer, to release the (R)AN resources associated with the PDU Session. The "skip indicator" tells the AMF whether it may skip sending the N1 SM container to the UE (e.g. when the UE is in CM-IDLE state). SMF includes the "skip indicator" in the Namf_Communication_N1N2MessageTransfer except when the procedure is triggered to change PDU Session Anchor of a PDU Session with SSC mode 2. If the UE is in CM-IDLE state and "skip indicator" is included in the Namf_Communication_N1N2MessageTransfer service operation or if the UE is in CM-IDLE state and "skip indicator" is not included in the Namf_Communication_N1N2MessageTransfer service operation but the AMF detects that the UE context contains Paging Restriction Information indicating that all paging is restricted, the AMF acknowledges the step 3b by sending an Namf_Communication_N1N2MessageTransfer Response message ("N1 SM Message Not Transferred") to SMF and steps 4 to 10 are skipped. 3c. If the PDU Session Release is initiated by the AMF in step 1c, i.e. the SMF received the Nsmf_PDUSession_ReleaseSMContext Request from the AMF, the SMF responds to the AMF with the Nsmf_PDUSession_ReleaseSMContext response, optionally including the Small Data Rate Control Status and APN Rate Control Status. If the UPF included APN Rate Control Status and/or Small Data Rate Control Status in step 2 then the SMF includes APN Rate Control and/or Small Data Rate Control Status and the AMF stores the Small Data Rate Control Status and/or the APN Rate Control Status in the UE context in AMF. The AMF and SMF shall remove all contexts (including the PDU Session ID) associated with the PDU Session which are indicated as released at the UE. The SMF shall remove any event subscriptions on the AMF by the SMF that becomes no more needed due to the PDU Session Release. The steps 4 to 11 are skipped. 3d. If the PDU Session Release is initiated by the AMF in step 1f, i.e. the SMF received the Nsmf_PDUSession_UpdateSMContext Request from the AMF with a release indication to request the release of the PDU Session, the SMF responds to the AMF with the Nsmf_PDUSession_UpdateSMContext Response which may contain the N1 SM container (PDU Session Release Command) to release the PDU session at the UE. If the UP connection of the PDU Session is active, the Nsmf_PDUSession_UpdateSMContext Response shall also include the N2 Resource Release request (PDU Session ID) to release the (R)AN resources associated with the PDU Session. 4. If the UE is in CM-IDLE state and "N1 SM delivery can be skipped" is not indicated, the AMF initiates the network triggered Service Request procedure to transmit the NAS message (PDU Session ID, N1 SM container) to the UE and the steps 6, 7 are skipped. If the message received from the SMF in step 3 does not include N2 SM Resource Release request, the AMF transmits the NAS message (PDU Session ID, N1 SM container) to the UE and the steps 6, 7 are skipped. If the PDU Session is Control Plane CIoT 5GS Optimisation enabled, the SMF shall not include N2 SM Resource Release request in the message sent to the AMF, the AMF transmits the NAS message (PDU Session ID, N1 SM container) to the UE and the steps 6, 7 are skipped. If the UE is in CM-CONNECTED state and the received message from the SMF in step 3 includes N2 SM Resource Release request, the AMF transfers the SM information received from the SMF in step 4 (N2 SM Resource Release request, N1 SM container) to the (R)AN. If the message from the SMF includes Small Data Rate Control Status then the AMF stores it in the UE Context in AMF. 5. When the (R)AN has received an N2 SM request to release the AN resources associated with the PDU Session it issues AN specific signalling exchange(s) with the UE to release the corresponding AN resources. In the case of a NG-RAN, the NAS message is sent to the UE in an RRC message which may take place with the UE releasing the NG-RAN resources related to the PDU Session. If NG-RAN resources do not need to be released (i.e. the User Plane of the PDU Session is deactivated), the NAS message is sent to the UE in an RRC message which does not release the NG-RAN resources related to the PDU Session. During this procedure, the (R)AN sends any NAS message (N1 SM container (PDU Session Release Command)) received from the AMF in step 5. For PDU Session for non-roaming subscribers, if the S-NSSAI of the released PDU Session is subject to network slice usage control as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and there is no other PDU Session using the S-NSSAI, the UE starts slice deregistration inactivity timer for the S-NSSAI. 6. [Conditional] If the (R)AN had received a N2 SM request to release the AN resources, the (R)AN acknowledges the N2 SM Resource Release Request by sending an N2 SM Resource Release Ack (User Location Information, Secondary RAT usage data) Message to the AMF. If the PLMN has configured secondary RAT usage reporting, the NG-RAN node may provide RAN Usage Data Report. If NG-RAN/AN-TL has performed the deletion of TN stream based on the request received from the SMF/CUC in step 3, the NG-RAN/AN-TL shall confirm the deletion of TN stream configurations. 7a. The AMF invokes the Nsmf_PDUSession_UpdateSMContext (N2 SM Resource Release Ack (Secondary RAT usage data), User Location Information) to the SMF. 7b. The SMF responds to the AMF with an Nsmf_PDUSession_UpdateSMContext response. 8. The UE acknowledges the PDU Session Release Command by sending a NAS message (PDU Session ID, N1 SM container (PDU Session Release Ack)) message over the (R)AN. 9. [Conditional] The (R)AN forwards the NAS message from the UE by sending a N2 NAS uplink transport (NAS message (PDU Session ID, N1 SM container (PDU Session Release Ack)), User Location Information) to the AMF. 10a. The AMF invokes the Nsmf_PDUSession_UpdateSMContext (N1 SM container (PDU Session Release Ack, User Location Information) to the SMF. 10b. The SMF responds to the AMF with an Nsmf_PDUSession_UpdateSMContext response. Steps 8-10 may happen before steps 6-7. 11. If steps 3a, 3b or 3d were performed, the SMF waits until it has received replies to the N1 and N2 information provided in step 3, as needed. The SMF invokes Nsmf_PDUSession_SMContextStatusNotify to notify AMF that the SM context for this PDU Session is released. If the UPF included Small Data Rate Control Status and/or APN Rate Control Status in step 2 then the SMF includes Small Data Rate Control Status and/or APN Rate Control Status in its request to the AMF in this step. The AMF releases the association between the SMF ID and the PDU Session ID, DNN, as well as S-NSSAI and stores the Small Data Rate Control Status and/or the APN Rate Control Status in the UE context in AMF. The SMF shall remove any event subscriptions on the AMF that becomes no more needed due to the PDU Session Release. NOTE 5: The UE and the 5GC will get synchronized about the status of the (released) PDU Session at the next Service Request or Registration procedure. For PDU Session for non-roaming subscribers, if the S-NSSAI of the released PDU Session is subject to network slice usage control and if the SMF indicates cause of slice inactivity and there is no other PDU Session using the S-NSSAI, then AMF may remove the S-NSSAI from the Allowed NSSAI or start slice deregistration inactivity timer for the S-NSSAI as described in clause 5.15.15.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 12. If Dynamic PCC applied to this session the SMF invokes an SM Policy Association Termination procedure as defined in clause 4.16.6 to delete the PDU Session. 13. SMF notifies any entity that has subscribed to User Location Information related with PDU Session change. 14. If it is the last PDU Session the SMF is handling for the UE for the associated (DNN, S-NSSAI), the SMF unsubscribes from Session Management Subscription data changes notification with the UDM by means of the Nudm_SDM_Unsubscribe (SUPI, DNN, S-NSSAI) service operation. The UDM may unsubscribe the subscription notification from UDR by Nudr_DM_Unsubscribe (SUPI, Subscription Data, Session Management Subscription data, DNN, S-NSSAI). 15. The SMF invokes the Nudm_UECM_Deregistration service operation including the DNN and the PDU Session Id. The UDM removes the association it had stored between the SMF identity and the associated DNN and PDU Session Id. The UDM may update this information by Nudr_DM_Update (SUPI, Subscription Data, UE context in SMF data). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.4.2 |
2,138 | 4.20 UE Parameters Update via UDM Control Plane Procedure 4.20.1 General | The purpose of the control plane solution for update of UE parameters is to allow the HPLMN, SNPN, or CH to update the UE with a specific set of parameters, generated and stored in the UDM, by delivering protected UDM Update Data via NAS signalling. The HPLMN, SNPN, or CH updates such parameters based on the operator policies. The UDM Update Data that the UDM delivers to the UE may contain: - one or more UE parameters including: - the updated Default Configured NSSAI (final consumer of the parameter is the ME); - the updated Routing Indicator Data (final consumer of the parameter is the USIM when the related credential is stored in the USIM, i.e. for PLMN or SNPN credentials; or final consumer of the parameter is the ME when the related credential is stored in the ME, i.e. for SNPN credentials); - indication of whether disaster roaming is enabled in the UE if UE MINT support indicator is received or UE is registered for Disaster Roaming service currently; and - indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' if UE MINT support indicator is received or UE is registered for Disaster Roaming service currently. - a "UE acknowledgement requested" indication. - a "re-registration requested" indication. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.20 |
2,139 | 10.5.5.25 Requested MS information | The purpose of the Requested MS information information element is to indicate whether certain feature-related information is requested from the MS by the network. If this IE is not included then no information is requested. The Requested MS information information element is coded as shown in figure 10.5.151/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.166/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Requested MS information is a type 1 information element. Figure 10.5.151/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Requested MS information information element Table 10.5.166/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Requested MS information 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.5.25 |
2,140 | 4.18.2.2 PFD management based on PFD Determination analytics | Figure 4.18.2.2-1 shows the procedure that NEF (PFDF) determines the PFD information for the known Application Identifier(s), based on the PFD Determination analytics information notified/responded from the subscribed/requested NWDAF. The procedure enables the NEF (PFDF) to determine whether to create/update/delete PFD information corresponding to the known Application Identifier(s). Figure 4.18.2.2-1: Procedure for PFD management based on PFD Determination analytics 1. The NWDAF notifies/responds to PFD Determination analytics to the NEF (PFDF) as Consumer NF with PFD Information defined in clause 6.16.3 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. 2. The NEF (PFDF) fetches the PFD information currently in use from UDR if not available in NEF (PFDF) as described from step 2 to step 3 of clause 4.18.3.1. 3. The NEF (PFDF) compares the PFD information from UDR with PFD information from the NWDAF to determine whether to create/update/delete PFD information corresponding to the Application Identifier. 4. If the NEF (PFDF) has determined in step 3 to create/update/delete PFD information corresponding to the Application Identifier, the NEF (PFDF) invokes the Nudr_DM_Create/Update/Delete (Application Identifier, one or more sets of PFDs) to the UDR to create/update/delete PFD information corresponding to the Application Identifier, i.e. from step 3 to step 5 of clause 4.18.2.1 are executed. The NEF (PFDF) may forward new/updated PFD information to UPF via SMF to detect a known application, as defined in clause 6.1.2.3.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.18.2.2 |
2,141 | 10.6 PSCell change | In MR-DC, a PSCell change does not always require a security key change. If a security key change is required, this is performed through a synchronous SCG reconfiguration procedure towards the UE involving random access on PSCell and a security key change, during which the MAC entity configured for SCG is reset and RLC configured for SCG is re-established regardless of the bearer type(s) established on SCG. For SN terminated bearers, PDCP is re-established. In all MR-DC options, to perform this procedure within the same SN, the SN Modification procedure as described in clause 10.3 is used, setting the PDCP Change Indication to indicate that a S-KgNB (for EN-DC, NGEN-DC and NR-DC) or S-KeNB (for NE-DC) update is required when the procedure is initiated by the SN or including the SgNB Security Key / SN Security Key when the procedure is initiated by the MN. In all MR-DC options, to perform a PSCell change between different SN nodes, the SN Change procedure as described in clause 10.5 is used. If a security key change is not required (only possible in EN-DC, NGEN-DC and NR-DC), this is performed through a synchronous SCG reconfiguration procedure without security key change towards the UE involving random access on PSCell, during which the MAC entity configured for SCG is reset and RLC configured for SCG is re-established regardless of the bearer type(s) established on SCG. For DRBs using RLC AM mode PDCP data recovery applies, and for DRBs using RLC UM no action is performed in PDCP. For SRB3 PDCP may discard all stored SDUs and PDUs. Unless MN terminated SCG or split bearers are configured, this does not require MN involvement. In this case, if location information was requested for the UE, the SN informs the MN about the PSCell change (as part of location information) using the SN initiated SN modification procedure independently from the reconfiguration of the UE. In case of MN terminated SCG or split bearers, the SN initiated SN Modification procedure as described in clause 10.3 is used, setting the PDCP Change Indication to indicate that a PDCP data recovery is required. If the MN subscribes to PSCell changes to retrieve the SCG UE history information, the SN informs the MN about the SCG UE history information using the SN initiated SN modification procedure when the SCG UE history information changes. A Conditional PSCell Change (CPC) is defined as a PSCell change that is executed by the UE when execution condition(s) is met. The UE starts evaluating the execution condition(s) upon receiving the CPC configuration, and stops evaluating the execution condition(s) once PSCell change or PCell change is triggered. Intra-SN CPC without MN involvement, inter-SN CPC initiated either by MN or SN are supported. The following principles apply to CPC: - The CPC configuration contains the configuration of CPC candidate PSCell(s) and execution condition(s) and may contain the MCG configuration for inter-SN CPC, to be applied when CPC execution is triggered. - An execution condition may consist of one or two trigger condition(s) (see CondEvent, as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4] or TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]). Only single RS type and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be used for the evaluation of CPC execution condition of a single candidate PSCell. - Before any CPC execution condition is satisfied, upon reception of PSCell change command or PCell change command, the UE executes the PSCell change procedure as described in clause 10.3 and 10.5 or the PCell change procedure as described in clause 9.2.3.2 in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] or clause 10.1.2.1 in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2], regardless of any previously received CPC configuration. Upon the successful completion of PSCell change procedure or PCell change procedure, the UE releases all stored CPC configurations. - While executing CPC, the UE is not required to continue evaluating the execution condition of other candidate PSCell(s) or PCell(s). - Once the CPC procedure is executed successfully, the UE releases all stored conditional reconfigurations (i.e. for CPC and for CHO, as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] or TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2]). - Upon the release of SCG, the UE releases the stored CPC configurations. - MN can inform SN of the maximum number of conditional reconfigurations the SN is allowed to configure for SN initiated CPC including both intra-SN and inter-SN CPC. CPC configuration in HO command, in PSCell addition/change command or within any conditional reconfiguration (i.e CPA, CPC or CHO configuration) is not supported. An SCG LTM is defined as a PSCell cell switch procedure that the network triggers via MAC CE based on L1 measurements. Only intra-SN SCG LTM without MN involvement is supported. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.6 |
2,142 | β SearchSpace | The IE SearchSpace defines how/where to search for PDCCH candidates. Each search space is associated with one ControlResourceSet. For a scheduled SCell in the case of cross carrier scheduling, except for nrofCandidates, all the optional fields are absent (regardless of their presence conditions). For a scheduled SpCell in the case of the cross carrier scheduling, if the search space is linked to another search space in the scheduling SCell, all the optional fields of this search space in the scheduled SpCell are absent (regardless of their presence conditions) except for nrofCandidates. SearchSpace information element -- ASN1START -- TAG-SEARCHSPACE-START SearchSpace ::= SEQUENCE { searchSpaceId SearchSpaceId, controlResourceSetId ControlResourceSetId OPTIONAL, -- Cond SetupOnly monitoringSlotPeriodicityAndOffset CHOICE { sl1 NULL, sl2 INTEGER (0..1), sl4 INTEGER (0..3), sl5 INTEGER (0..4), sl8 INTEGER (0..7), sl10 INTEGER (0..9), sl16 INTEGER (0..15), sl20 INTEGER (0..19), sl40 INTEGER (0..39), sl80 INTEGER (0..79), sl160 INTEGER (0..159), sl320 INTEGER (0..319), sl640 INTEGER (0..639), sl1280 INTEGER (0..1279), sl2560 INTEGER (0..2559) } OPTIONAL, -- Cond Setup4 duration INTEGER (2..2559) OPTIONAL, -- Need S monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL, -- Cond Setup nrofCandidates SEQUENCE { aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8} } OPTIONAL, -- Cond Setup searchSpaceType CHOICE { common SEQUENCE { dci-Format0-0-AndFormat1-0 SEQUENCE { ... } OPTIONAL, -- Need R dci-Format2-0 SEQUENCE { nrofCandidates-SFI SEQUENCE { aggregationLevel1 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel2 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel4 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel8 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel16 ENUMERATED {n1, n2} OPTIONAL -- Need R }, ... } OPTIONAL, -- Need R dci-Format2-1 SEQUENCE { ... } OPTIONAL, -- Need R dci-Format2-2 SEQUENCE { ... } OPTIONAL, -- Need R dci-Format2-3 SEQUENCE { dummy1 ENUMERATED {sl1, sl2, sl4, sl5, sl8, sl10, sl16, sl20} OPTIONAL, -- Cond Setup dummy2 ENUMERATED {n1, n2}, ... } OPTIONAL -- Need R }, ue-Specific SEQUENCE { dci-Formats ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1}, ..., [[ dci-Formats-MT-r16 ENUMERATED {formats2-5} OPTIONAL, -- Need R dci-FormatsSL-r16 ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1, formats3-0, formats3-1, formats3-0-And-3-1} OPTIONAL, -- Need R dci-FormatsExt-r16 ENUMERATED {formats0-2-And-1-2, formats0-1-And-1-1And-0-2-And-1-2} OPTIONAL -- Need R ]], [[ dci-FormatsMC ENUMERATED {formats0-3, formats1-3, formats0-3-And-1-3} OPTIONAL, -- Need R dci-FormatsNCR-r18 ENUMERATED {formats2-8} OPTIONAL -- Need R ]] } } OPTIONAL -- Cond Setup2 } SearchSpaceExt-r16 ::= SEQUENCE { controlResourceSetId-r16 ControlResourceSetId-r16 OPTIONAL, -- Cond SetupOnly2 searchSpaceType-r16 SEQUENCE { common-r16 SEQUENCE { dci-Format2-4-r16 SEQUENCE { nrofCandidates-CI-r16 SEQUENCE { aggregationLevel1-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel2-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel4-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel8-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel16-r16 ENUMERATED {n1, n2} OPTIONAL -- Need R }, ... } OPTIONAL, -- Need R dci-Format2-5-r16 SEQUENCE { nrofCandidates-IAB-r16 SEQUENCE { aggregationLevel1-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel2-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel4-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel8-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel16-r16 ENUMERATED {n1, n2} OPTIONAL -- Need R }, ... } OPTIONAL, -- Need R dci-Format2-6-r16 SEQUENCE { ... } OPTIONAL, -- Need R ... } } OPTIONAL, -- Cond Setup3 searchSpaceGroupIdList-r16 SEQUENCE (SIZE (1.. 2)) OF INTEGER (0..1) OPTIONAL, -- Need R freqMonitorLocations-r16 BIT STRING (SIZE (5)) OPTIONAL -- Need R } SearchSpaceExt-v1700 ::= SEQUENCE { monitoringSlotPeriodicityAndOffset-v1710 CHOICE { sl32 INTEGER (0..31), sl64 INTEGER (0..63), sl128 INTEGER (0..127), sl5120 INTEGER (0..5119), sl10240 INTEGER (0..10239), sl20480 INTEGER (0..20479) } OPTIONAL, -- Cond Setup5 monitoringSlotsWithinSlotGroup-r17 CHOICE { slotGroupLength4-r17 BIT STRING (SIZE (4)), slotGroupLength8-r17 BIT STRING (SIZE (8)) } OPTIONAL, -- Need R duration-r17 INTEGER (4..20476) OPTIONAL, -- Need R searchSpaceType-r17 SEQUENCE{ common-r17 SEQUENCE { dci-Format4-0-r17 SEQUENCE { ... } OPTIONAL, -- Need R dci-Format4-1-r17 SEQUENCE { ... } OPTIONAL, -- Need R dci-Format4-2-r17 SEQUENCE { ... } OPTIONAL, -- Need R dci-Format4-1-AndFormat4-2-r17 SEQUENCE { ... } OPTIONAL, -- Need R dci-Format2-7-r17 SEQUENCE { nrofCandidates-PEI-r17 SEQUENCE { aggregationLevel4-r17 ENUMERATED {n0, n1, n2, n3, n4} OPTIONAL, -- Need R aggregationLevel8-r17 ENUMERATED {n0, n1, n2} OPTIONAL, -- Need R aggregationLevel16-r17 ENUMERATED {n0, n1} OPTIONAL -- Need R }, ... } OPTIONAL -- Need R } } OPTIONAL, -- Need R searchSpaceGroupIdList-r17 SEQUENCE (SIZE (1.. 3)) OF INTEGER (0.. maxNrofSearchSpaceGroups-1-r17) OPTIONAL, -- Cond DedicatedOnly searchSpaceLinkingId-r17 INTEGER (0..maxNrofSearchSpacesLinks-1-r17) OPTIONAL -- Cond DedicatedOnly } SearchSpaceExt-v1800 ::= SEQUENCE { searchSpaceType-r18 SEQUENCE { common-r18 SEQUENCE { dci-Format2-9-r18 SEQUENCE { ... } OPTIONAL, -- Need R ... } } OPTIONAL, -- Need R ... } -- TAG-SEARCHSPACE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,143 | 4.3.2.2.4 Multiple PDU Sessions towards the same DNN and S-NSSAI | A UE may establish multiple PDU Sessions associated with the same DNN and S-NSSAI and the AMF may select the same SMF or different SMFs as specified in clause 6.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. During PDU Session establishment, the AMF checks if the SMF selection subscription data indicates that the same SMF is required for multiple PDU Sessions and if required, the AMF checks if any SMF is already selected for the same DNN and S-NSSAI, if so, the same SMF will be used for the additional PDU Session. NOTE 1: The SMF ID can be notified from UDM to the AMF when one AMF is selected for 3GPP access in VPLMN and a different AMF is selected in HPLMN for non-3GPP access. NOTE 2: The same SMF is selected for multiple PDU Sessions towards the same DNN and S-NSSAI to facilitate the selection of the same PCF e.g. for the purpose of usage monitoring. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.2.2.4 |
2,144 | Annex B (normative): Single IMSI architecture for EU Roaming B.0 General | To enable the sale of regulated roaming services, an architecture based on 3GPP has been defined in the high-level technical specification EU Roaming regulation III; Structural Solutions; High Level Technical Specifications [298]. A real-time interface has been defined in EU Roaming regulation III; Interface & Protocol; Detailed Technical Specifications [299] for retailing billing of voice calls between a Domestic Service Provider and an Alternative Roaming Provider. For the purposes of this annex, the following definitions apply: Alternative Roaming Provider (ARP): A roaming provider different from the domestic provider. Domestic Service Provider (DSP): An undertaking that provides a roaming customer with domestic mobile communications services, either a Mobile Network Operator or a Mobile Virtual Network Operator. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | Annex |
2,145 | 4.13.2.10 Number of successful reconfigurations of LWA DRB | a) This measurement provides the number of successful reconfigurations of LWA DRB. b) CC c) On receipt of RRCConnectionReconfigurationComplete message (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [6]) by the eNB, corresponding to transmitted RRCConnectionReconfiguration message which triggered the measurement "Number of attempted reconfigurations of LWA DRB" (see clause 4.13.2.9). d) An integer value e) LWI.LwaDrbReconfSucc f) WLANMobilitySet g) Valid for packet switched traffic 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.13.2.10 |
2,146 | 9.2.3.2.2 U-Plane Handling | The U-plane handling during the Intra-NR-Access mobility activity for UEs in RRC_CONNECTED takes the following principles into account to avoid data loss during HO: - During HO preparation, U-plane tunnels can be established between the source gNB and the target gNB; - During HO execution, user data can be forwarded from the source gNB to the target gNB; - Forwarding should take place in order as long as packets are received at the source gNB from the UPF or the source gNB buffer has not been emptied. - During HO completion: - The target gNB sends a path switch request message to the AMF to inform that the UE has gained access and the AMF then triggers path switch related 5GC internal signalling and actual path switch of the source gNB to the target gNB in UPF; - The source gNB should continue forwarding data as long as packets are received at the source gNB from the UPF or the source gNB buffer has not been emptied. For RLC-AM bearers: - For in-sequence delivery and duplication avoidance, PDCP SN is maintained on a per DRB basis and the source gNB informs the target gNB about the next DL PDCP SN to allocate to a packet which does not have a PDCP sequence number yet (either from source gNB or from the UPF). - For security synchronisation, HFN is also maintained and the source gNB provides to the target one reference HFN for the UL and one for the DL i.e. HFN and corresponding SN. - In both the UE and the target gNB, a window-based mechanism is used for duplication detection and reordering. - The occurrence of duplicates over the air interface in the target gNB is minimised by means of PDCP SN based reporting at the target gNB by the UE. In uplink, the reporting is optionally configured on a per DRB basis by the gNB and the UE should first start by transmitting those reports when granted resources are in the target gNB. In downlink, the gNB is free to decide when and for which bearers a report is sent and the UE does not wait for the report to resume uplink transmission. - The target gNB re-transmits and prioritizes all downlink data forwarded by the source gNB (i.e. the target gNB should first send all forwarded PDCP SDUs with PDCP SNs, then all forwarded downlink PDCP SDUs without SNs before sending new data from 5GC), excluding PDCP SDUs for which the reception was acknowledged through PDCP SN based reporting by the UE. NOTE 1: Lossless delivery when a QoS flow is mapped to a different DRB at handover, requires the old DRB to be configured in the target cell. For in-order delivery in the DL, the target gNB should first transmit the forwarded PDCP SDUs on the old DRB before transmitting new data from 5GC on the new DRB. In the UL, the target gNB should not deliver data of the QoS flow from the new DRB to 5GC before receiving the end marker on the old DRB from the UE. - The UE re-transmits in the target gNB all uplink PDCP SDUs starting from the oldest PDCP SDU that has not been acknowledged at RLC in the source, excluding PDCP SDUs for which the reception was acknowledged through PDCP SN based reporting by the target. - In case of handovers involving Full Configuration, the following description below for RLC-UM bearers applies for RLC-AM bearers instead. Data loss may happen. For RLC-UM bearers: - The PDCP SN and HFN are reset in the target gNB, unless the bearer is configured with DAPS handover; - No PDCP SDUs are retransmitted in the target gNB; - The target gNB prioritises all downlink SDAP SDUs forwarded by the source gNB over the data from the core network; NOTE 2: To minimise losses when a QoS flow is mapped to a different DRB at handover, the old DRB needs to be configured in the target cell. For in-order delivery in the DL, the target gNB should first transmit the forwarded PDCP SDUs on the old DRB before transmitting new data from 5GC on the new DRB. In the UL, the target gNB should not deliver data of the QoS flow from the new DRB to 5GC before receiving the end marker on the old DRB from the UE. - The UE does not retransmit any PDCP SDU in the target cell for which transmission had been completed in the source cell. For DAPS handover: A DAPS handover can be used for an RLC-AM or RLC-UM bearer. For a DRB configured with DAPS, the following principles are additionally applied. Downlink: - During HO preparation, a forwarding tunnel is always established. - The source gNB is responsible for allocating downlink PDCP SNs until the SN assignment is handed over to the target gNB and data forwarding in 9.2.3.2.3 takes place. That is, the source gNB does not stop assigning PDCP SNs to downlink packets until it receives the HANDOVER SUCCESS message and sends the SN STATUS TRANSFER message to the target gNB. - Upon allocation of downlink PDCP SNs by the source gNB, it starts scheduling downlink data on the source radio link and also starts forwarding downlink PDCP SDUs along with assigned PDCP SNs to the target gNB. - For security synchronisation, HFN is maintained for the forwarded downlink SDUs with PDCP SNs assigned by the source gNB. The source gNB sends the EARLY STATUS TRANSFER message to convey the DL COUNT value, indicating PDCP SN and HFN of the first PDCP SDU that the source gNB forwards to the target gNB. - HFN and PDCP SN are maintained after the SN assignment is handed over to the target gNB. The SN STATUS TRANSFER message indicates the next DL PDCP SN to allocate to a packet which does not have a PDCP sequence number yet, even for RLC-UM. - During handover execution period, the source and target gNBs separately perform ROHC header compression, ciphering, and adding PDCP header. - During handover execution period, the UE continues to receive downlink data from both source and target gNBs until the source gNB connection is released by an explicit release command from the target gNB. - During handover execution period, the UE PDCP entity configured with DAPS maintains separate security and ROHC header decompression functions associated with each gNB, while maintaining common functions for reordering, duplicate detection and discard, and PDCP SDUs in-sequence delivery to upper layers. PDCP SN continuity is supported for both RLC AM and UM DRBs configured with DAPS. Uplink: - The UE transmits UL data to the source gNB until the random access procedure toward the target gNB has been successfully completed. Afterwards the UE switches its UL data transmission to the target gNB. - Even after switching its UL data transmissions towards the target gNB, the UE continues to send UL layer 1 CSI feedback, HARQ feedback, layer 2 RLC feedback, ROHC feedback, HARQ data (re-)transmissions, and RLC data (re-)transmissions to the source gNB. - During handover execution period, the UE maintains separate security context and ROHC header compressor context for uplink transmissions towards the source and target gNBs. The UE maintains common UL PDCP SN allocation. PDCP SN continuity is supported for both RLC AM and UM DRBs configured with DAPS. - During handover execution period, the source and target gNBs maintain their own security and ROHC header decompressor contexts to process UL data received from the UE. - The establishment of a forwarding tunnel is optional. - HFN and PDCP SN are maintained in the target gNB. The SN STATUS TRANSFER message indicates the COUNT of the first missing PDCP SDU that the target should start delivering to the 5GC, even for RLC-UM. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.3.2.2 |
2,147 | 5.15.16 Optimized handling of temporarily available network slices | A network slice may be available for all UEs or a limited number of UEs only for a limited time that is known at the network in advance e.g. by OAM or subscription. The limited time duration may be due to, for example, the fact that network slice is only temporarily or periodically active in the deployment (e.g. for a limited time to serve an event or a UE may be only authorized to access the network slice for a limited time known in advance), or the network slice is being decommissioned at a known future time. This feature is enabled by S-NSSAI validity time that the network and the UE can handle to reduce the signalling load associated to the transitions in RM and SM states for the network slice. The UE may indicate its support for temporarily available network slices in the UE MM Core Network Capability (see clause 5.4.4a) in the Registration Request. The AMF, based on OAM configuration or information received from the UDM or NSSF, may indicate to a supporting UE the validity time for one or more S-NSSAIs in the Configured NSSAI in the Registration Accept message or via the UE Configuration Update procedure. In roaming case, the AMF my include the validity time for an S-NSSAI in the Configured NSSAI either because of limited availability of the VPLMN S-NSSAI or the mapped S-NSSAI of the HPLMN. NOTE 1: When the validity time changes or a validity time is determined for a S-NSSAI in the configured NSSAI, the PLMN provides the new validity time for the S-NSSAIs in the Configured NSSAI to a supporting UE. If a supporting UE is configured with validity time for an S-NSSAI: a) If the validity time indicates the S-NSSAI is available, the UE may request the S-NSSAI in a Requested NSSAI in a Registration request and, if the S-NSSAI is included in the Allowed NSSAI or in the Partially Allowed NSSAI, the UE may establish PDU sessions associated with the S-NSSAI. b) If the validity time indicates the S-NSSAI is not available - The UE shall not include the S-NSSAI in the Requested NSSAI for any Access Types regardless of the validity time information was received; - If the S-NSSAI is already part of the Allowed NSSAI or Partially Allowed NSSAI, the UE shall remove the S-NSSAI from the locally stored Allowed NSSAI or Partially Allowed NSSAI and the UE shall also locally release any PDU sessions associated with the S-NSSAI. - If the validity time indicates the S-NSSAI will not be available again, the UE shall remove the S-NSSAI from the locally stored Configured NSSAI. NOTE 2: Subject to implementation decisions outside 3GPP scope, the UE may also use the validity time information to e.g. attempt to use another PDU sessions to continue supporting the connectivity with another connectivity option if possible according to the URSP rules, or, if not possible, e.g. provide implementation-dependent information on the availability of connectivity for specific applications affected by an impending connectivity loss, so the UE can let the end user prepare for the loss of connectivity. For a supporting UE, if validity time applies to an S-NSSAI, an AMF supporting temporarily available network slices shall: - If the S-NSSAI is provided in a Requested NSSAI in a Registration Request by the UE and the validity time indicates the S-NSSAI is not available, but it is going to become available again (i.e. the UE is detected as not having up to date validity time), then the AMF sends the Configured NSSAI to the UE including the validity time for the S-NSSAI in the Registration Accept message. If the validity time indicates the S-NSSAI is not available and will not become available again, then the AMF sends the Configured NSSAI to the UE, excluding the S-NSSAI from the Configured NSSAI. - If the S-NSSAI is in the Allowed NSSAI or the Partially Allowed NSSAI for the UE and the validity time indicates that the S-NSSAI is not available, then locally remove (i.e. without sending any signalling to the UE) the S-NSSAI from the Allowed NSSAI or Partially Allowed NSSAI. If there is any PDU session established for the S-NSSAI, the AMF requests the SMF to release the PDU session: - If the UE is in CM-CONNECTED state, the AMF releases the PDU session for the S-NSSAI by sending to the SMF, as per step 1f in clause 4.3.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], a Nsmf_PDUSession_UpdateSMContext Request with a release indication to request the release of the PDU Session and then the AMF forwards the N2 SM request to release the AN resources associated with the PDU session - If the UE is in CM-IDLE state, the AMF locally releases the PDU session without paging the UE and causes the SMF to locally release the SM context for the UE by a Nsmf_PDUSession_ReleaseSMContext, as in step 1c in clause 4.3.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The PDU Session status is synchronized at next time when the UE connects to the network. For a non-supporting UE, if validity time applies to an S-NSSAI, an AMF supporting temporarily available network slices shall: - If the validity time indicates the S-NSSAI is available, allow or partially allow the network slice when requested, establish PDU sessions when requested. - If the S-NSSAI is provided in a Requested NSSAI in a Registration Request by the UE and the validity time indicates the S-NSSAI is not available, reject the S-NSSAI and remove the S-NSSAI from the Configured NSSAI by providing an updated Configured NSSAI in the Registration Accept message. - If the S-NSSAI is in the UE in the Allowed NSSAI or Partially Allowed NSSAI and the validity time indicates the S-NSSAI is not available, remove the S-NSSAI from the Configured NSSAI and the Allowed NSSAI or Partially Allowed NSSAI by a UE Configuration Update procedure. If there is any PDU session established for the S-NSSAI, the AMF requests the SMF to release the PDU session in the network: - If the UE is in CM-CONNECTED state, the AMF releases the PDU session for the S-NSSAI by sending to the SMF, as in step 1f in clause 4.3.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], a Nsmf_PDUSession_UpdateSMContext Request with a release indication to request the release of the PDU Session and then the AMF forwards the N2 SM request to release the AN resources associated with the PDU session - If the UE is in CM-IDLE, the AMF locally releases the PDU session without paging the UE and causes the SMF to locally release the SM context for the UE by a Nsmf_PDUSession_ReleaseSMContext, as in step 1c in clause 4.3.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The PDU Session status is synchronized at next time when the UE connects to the network NOTE 3: If the network slice becomes unavailable, and a large number of UEs are impacted, the AMF can send the updates to the non-supporting UEs in a manner that avoids surge in signalling (e.g. next time the UE becomes connected). - If the AMF detects from the validity time of a S-NSSAI that it is available again, then update the Configured NSSAI to include the S-NSSAI via a UE Configuration Update procedure. NOTE 4: The AMF, for the case of UE not performing any actions despite the validity timing information provided by the network, can terminate PDU Session(s) associated with S-NSSAI subject to be terminated according to the validity time by explicitly releasing the PDU Sessions associated with the S-NSSAI. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.16 |
2,148 | 5.8.7 Sidelink communication reception | A UE capable of NR sidelink communication that is configured by upper layers to receive NR sidelink communication shall: 1> if the conditions for NR sidelink communication operation as defined in 5.8.2 are met: 2> if the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt in RRCReconfiguration message or sl-FreqInfoList/sl-FreqInfoListSizeExt included in SIB12: 3> if the UE is configured with sl-RxPool included in RRCReconfiguration message with reconfigurationWithSync (i.e. handover): 4> configure lower layers to monitor sidelink control information and the corresponding data using the pool(s) of resources indicated by sl-RxPool; 3> else if the cell chosen for NR sidelink communication provides SIB12: 4> configure lower layers to monitor sidelink control information and the corresponding data using the pool(s) of resources indicated by sl-RxPool in SIB12; 2> else: 3> configure lower layers to monitor sidelink control information and the corresponding data using the pool(s) of resources that were preconfigured by sl-RxPool in SL-PreconfigurationNR, as defined in clause 9.3. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.7 |
2,149 | 5.3.5.5.13 Uu Relay RLC channel addition/modification | For each Uu-RelayRLC-ChannelConfig received in the uu-RelayRLC-ChannelToAddModList the L2 U2N Relay UE or N3C relay UE shall: 1> if the current configuration contains a Uu Relay RLC channel with the same uu-RelayRLC-ChannelID within the same cell group: 2> if reestablishRLC is received: 3> re-establish the RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4]; 2> reconfigure the RLC entity in accordance with the received rlc-Config; 2> reconfigure the logical channel in accordance with the received mac-LogicalChannelConfig; 1> else (a logical channel with the given uu-RelayRLC-ChannelID was not configured before within the same cell group): 2> establish an RLC entity in accordance with the received rlc-Config; 2> configure this MAC entity with a logical channel in accordance to the received mac-LogicalChannelConfig. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.5.13 |
2,150 | 9.11.3.4 5GS mobile identity | The purpose of the 5GS mobile identity information element is to provide either the SUCI, the 5G-GUTI, the IMEI, the IMEISV, the 5G-S-TMSI, the MAC address or the EUI-64. The 5GS mobile identity information element is coded as shown in figures 9.11.3.4.1, 9.11.3.4.2, 9.11.3.4.3, 9.11.3.4.4, 9.11.3.4.5, 9.11.3.4.6, 9.11.3.4.8 and 9.11.3.4.7, and table 9.11.3.4.1. The 5GS mobile identity is a type 6 information element with a minimum length of 4. Figure 9.11.3.4.1: 5GS mobile identity information element for type of identity "5G-GUTI" Figure 9.11.3.4.2: 5GS mobile identity information element for type of identity "IMEI" or "IMEISV" Figure 9.11.3.4.3: 5GS mobile identity information element for type of identity "SUCI" and SUPI format "IMSI" Figure 9.11.3.4.3a: Scheme output for type of identity "SUCI", SUPI format "IMSI" and Protection scheme Id "Null scheme" Figure 9.11.3.4.4: 5GS mobile identity information element for type of identity "SUCI" and SUPI format "Network specific identifier", "GCI" or "GLI" Figure 9.11.3.4.5: 5GS mobile identity information element for type of identity "5G-S-TMSI" Figure 9.11.3.4.6: 5GS mobile identity information element for type of identity "No identity" Figure 9.11.3.4.7: 5GS mobile identity information element for type of identity "MAC address" Figure 9.11.3.4.8: 5GS mobile identity information element for type of identity "EUI-64" Table 9.11.3.4.1: 5GS mobile identity information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.4 |
2,151 | 5.5.3.2 Layer 3 filtering | The UE shall: 1> for each cell measurement quantity, each beam measurement quantity, each sidelink measurement quantity as needed in clause 5.8.10, for each CLI measurement quantity that the UE performs measurements according to 5.5.3.1, for each candidate L2 U2N Relay UE measurement quantity according to 5.5.3.4, for evaluating the detected NR sidelink U2N Relay UEs according to 5.8.15.3, for evaluating the SyncRef UE according to 5.8.5 and 5.8.6, and for evaluating the detected NR sidelink U2U Relay UEs according to 5.8.17.4: 2> filter the measured result, before using for evaluation of reporting criteria, for measurement reporting, for U2N/U2U Relay (re)selection evaluation or for evaluating the SyncRef UE, by the following formula: Fn = (1 β a)*Fn-1 + a*Mn where Mn is the latest received measurement result from the physical layer; Fn is the updated filtered measurement result, that is used for evaluation of reporting criteria, for measurement reporting, for U2N/U2U Relay (re)selection evaluation or for evaluating the SyncRef UE; Fn-1 is the old filtered measurement result, where F0 is set to M1 when the first measurement result from the physical layer is received; and for MeasObjectNR, a = 1/2(ki/4), where ki is the filterCoefficient for the corresponding measurement quantity of the i:th QuantityConfigNR in quantityConfigNR-List, and i is indicated by quantityConfigIndex in MeasObjectNR; for other measurements, a = 1/2(k/4), where k is the filterCoefficient for the corresponding measurement quantity received by the quantityConfig; for UTRA-FDD, a = 1/2(k/4), where k is the filterCoefficient for the corresponding measurement quantity received by quantityConfigUTRA-FDD in the QuantityConfig; 2> adapt the filter such that the time characteristics of the filter are preserved at different input rates, observing that the filterCoefficient k assumes a sample rate equal to X ms; The value of X is equivalent to one intra-frequency L1 measurement period as defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14] assuming non-DRX operation, and depends on frequency range. NOTE 1: If k is set to 0, no layer 3 filtering is applicable. NOTE 2: The filtering is performed in the same domain as used for evaluation of reporting criteria, for measurement reporting, for U2N Relay (re)selection evaluation or for evaluating the SyncRef UE, i.e., logarithmic filtering for logarithmic measurements. NOTE 3: The filter input rate is implementation dependent, to fulfil the performance requirements set in TS 38.133[ NR; Requirements for support of radio resource management ] [14]. For further details about the physical layer measurements, see TS 38.133[ NR; Requirements for support of radio resource management ] [14]. NOTE 4: For CLI-RSSI measurement, it is up to UE implementation whether to reset filtering upon BWP switch. NOTE 5: For SSB measurements when multiple altitude range-based ssb-ToMeasure are configured, it is up to UE implementation whether to reset filtering upon entering a different altitude range. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.3.2 |
2,152 | 6.1.3.9.1 MBMS context deactivation initiated by the network | In order to request an MBMS context deactivation, the network sends a DEACTIVATE PDP CONTEXT REQUEST message to the MS, enters the state MBMS-INACTIVE-PENDING and starts timer T3395. The message contains the transaction identifier (TI) in use for the MBMS context to be deactivated and a cause code that typically indicates one of the following causes: # 36: regular deactivation; # 38: network failure; # 47: multicast group membership time-out. The MS shall reply with a DEACTIVATE PDP CONTEXT ACCEPT message and enter the state PDP-INACTIVE. Upon receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the network shall stop the timer T3395 and enter the state PDP-INACTIVE. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.9.1 |
2,153 | 13.5A Private Service Identity | The Private Service Identity is applicable to a PSI user and is similar to a Private User Identity in the form of a Network Access Identifier (NAI), which is defined in IETF RFC 4282 [53]. The Private Service Identity is operator defined and although not operationally used for registration, authorisation and authentication in the same way as Private User Identity, it enables Public Service Identities to be associated to a Private Service Identity which is required for compatibility with the Cx procedures. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.5A |
2,154 | 5.2.1.6 Call connected | Upon receiving an indication that the call has been accepted, the call control entity of the network shall: through connect the traffic channel (including the connection of an interworking function, if required) and send a CONNECT message to its peer entity at the calling mobile station; start timer T313 and enter the "connect indication" state. This message indicates to the call control entity of the calling mobile station that a connection has been established through the network. The call control entity of the mobile station in the "call initiated" state, in the "mobile originating call proceeding" state or in the "call delivered" state, shall, upon receipt of a CONNECT message: - attach the user connection; - return a CONNECT ACKNOWLEDGE message; - stop any locally generated alerting indication (if applied); - clear any H.324 call established to receive multimedia CAT during the alerting phase (if applied) , as specified in subclause 5.3.6.4 - stop timer T303 and T310 (if running); - enter the "active" state. Abnormal cases: On the mobile station side, if timer T303 or T310 expires, the call control entity of the mobile station shall initiate call clearing as described in subclause 5.4. NOTE: The mobile station may have applied an additional internal alerting supervision which causes initiation of call clearing prior to the expiry of T303 or T310. The call control of the network in the "connect indication" state, shall, upon receipt of a CONNECT ACKNOWLEDGE message: - stop timer T313 and enter the "active" state. Abnormal cases: On the network side, if timer T313 elapses before a CONNECT ACKNOWLEDGE message has been received, the network shall perform the clearing procedure as described in subclause 5.4. Figure 5.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Call acceptance sequence at mobile originating call establishment | 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.2.1.6 |
2,155 | 4.10.1.1 Wideband CQI distribution | a) This measurement provides the distribution of the Wideband CQI (Channel Quality Indicator) reported by UEs in the cell. b) CC. c) This measurement is obtained by incrementing the appropriate measurement bin when a wideband CQI value is reported by a UE in the cell. When spatial multiplexing is used, CQI for both code words should be considered. d) A single integer value. e) CARR.WBCQIDist.BinX where X represents the CQI value (0 to 15). 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.10.1.1 |
2,156 | 4.3.2 Change of UE mode of operation 4.3.2.1 General | The UE mode of operation can change as a result of e.g.: - a change of UE's usage setting for a CS voice capable UE; - a change of voice domain preference for E-UTRAN as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [13B] for a CS voice capable UE; - a change in the UE's availability for voice calls in the IMS; or - a change in UE configuration regarding the use of SMS as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [13B]. Figure 4.3.2.1.1 and figure 4.3.2.1.2 illustrate the transitions between different UE mode of operations when UE's usage settings, voice domain preference for E-UTRAN or configuration regarding SMS changes. NOTE 1: The UE may transit from CS/PS mode 1 to PS mode 1 or from CS/PS mode 2 to PS mode 2 if "CS domain not available" is received. After the transition to PS mode 1 or PS mode 2 due to "CS domain not available", the UE can transit back to CS/PS mode 1 or CS/PS mode 2, e.g. due to change of PLMN which is not in the list of the equivalent PLMNs. NOTE 2: Not all possible transitions are shown in this figure. Figure 4.3.2.1.1: Change of UE mode of operation for a CS voice capable UE NOTE: Not all possible transitions are shown in this figure. Figure 4.3.2.1.2: Change of UE mode of operation for a UE with no CS voice capability | 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 | 4.3.2 |
2,157 | 9.3.22 Retrieve Reject | This message is sent by the network to indicate the inability to perform the requested retrieve function. See table 9.69d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] for the content of the RETRIEVE REJECT message. For the use of this message, see 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]. Message type: RETRIEVE REJECT Significance: local Direction: network to mobile station Table 9.69d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : RETRIEVE REJECT message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.22 |
2,158 | 20.5a.12 MBMS-Cell-List AVP | The MBMS-Cell-List AVP (AVP code 934) is of type OctetString. It contains the MBMS Cell Listthat the E-UTRAN uses to determine a set of radio resources to be used for the broadcast. Based on the cell ID list, the set of radio resources selected may be reduced from the full set of resources defined by the MBMS service area. The AVP shall consist of two octets indicating the number of cell identifiers in the list, followed by a sequence of maximum 4096 cell identifiers, coded as E-CGIs. The ECGI and its semantics are defined in subclause 19.6 of 3GPP TS 23.003[ Numbering, addressing and identification ] [40]. | 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 | 20.5a.12 |
2,159 | 4.3.5.2 Abort procedure in the mobile station | At the receipt of the ABORT message the mobile station shall abort any MM connection establishment or call re-establishment procedure and release all MM connections (if any). If cause value #6 is received the mobile station shall delete any TMSI, LAI and ciphering key sequence number stored in the SIM/USIM, set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2) and consider the SIM/USIM invalid until switch off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. As a consequence the mobile station enters state MM IDLE, substate NO IMSI after the release of the RR connection. The mobile station shall then wait for the network to release the RR connection - see subclause 4.5.3.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.3.5.2 |
2,160 | 9.9.2.2.2 TDD | For the parameters specified in Table 9.9.2.2.2-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in 9.9.2.2.2-2 and by the following a) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP and that obtained when transmitting the transport format indicated by each reported wideband CQI index subject to a white Gaussian noise source shall be β₯ ο§ο ; b) when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP, the average BLER for the indicated transport formats shall be greater than or equal to 2%. Table 9.9.2.2.2-1 Fading test for single antenna (TDD) Table 9.9.2.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.9.2.2.2 |
2,161 | D.2.1.1 Inputs and outputs | The input parameters to the ciphering algorithm are a 128-bit cipher key named KEY, a 32-bit COUNT, a 5-bit bearer identity BEARER, the 1-bit direction of the transmission i.e. DIRECTION, and the length of the keystream required i.e. LENGTH. The DIRECTION bit shall be 0 for uplink and 1 for downlink. Figure D.2.1.1-1 illustrates the use of the ciphering algorithm NEA to encrypt plaintext by applying a keystream using a bit per bit binary addition of the plaintext and the keystream. The plaintext may be recovered by generating the same keystream using the same input parameters and applying a bit per bit binary addition with the ciphertext. Figure D.2.1.1-1: Ciphering of data Based on the input parameters the algorithm generates the output keystream block KEYSTREAM which is used to encrypt the input plaintext block PLAINTEXT to produce the output ciphertext block CIPHERTEXT. The input parameter LENGTH shall affect only the length of the KEYSTREAM BLOCK, not the actual bits in it. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | D.2.1.1 |
2,162 | 6.2.5G Configured transmitted power for V2X Communication | When UE is configured for E-UTRA V2X sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA V2X operating bands specified in Table 5.5G-1, the V2X UE is allowed to set its configured maximum output power PCMAX,c for component carrier c. The configured maximum output power PCMAX,c is set within the following bounds: PCMAX_L,c β€ PCMAX,c β€ PCMAX_H,c with PCMAX_L,c = MIN {PEMAX,c β οTC,c, PPowerClass ββ MAX(MPRc + A-MPRc + ΞTIB,c + οTC,c + οTProSe, P-MPRc), PRegulatory,c } PCMAX_H,c = MIN {PEMAX,c, PPowerClass, PRegulatory,c } where - For the total transmitted power PCMAX,c of PSSCH and PSCCH, PEMAX,c is the value given by IE maxTxPower, defined by [7], when the UE is not associated with a serving cell on the V2X carrier. - For, PEMAX,c is the value given by the IE maxTxPower in [7] when the UE is not associated with a serving cell on the V2X carrier. - For, the value is as calculated for and applying the MPR for SSSS as specified in Section 6.2.3D. - PPowerClass is the maximum UE power specified in Table 6.2.2-1 without taking into account the tolerance specified in the Table 6.2.2-1; - MPRc and A-MPRc for serving cell c are specified in subclause 6.2.3G and subclause 6.2.4G, respectively; - ο οTIB,c, οTC,c, οTProSe and P-MPRc are specified in subclause 6.2.5 - PRegulatory,cο = 10 - Gpost connector dBm when the V2X UE is within the protected zone [13] of CEN DSRC tolling system and operating in Band 47; PRegulatory,cο = 33 - Gpost connector dBm otherwise. The maximum output power PCMAX,PSSCH and PCMAX,PSCCH are derived from PCMAX,c based on the PSD offset following subclause 14.1.1.5 in [6]. For all cases, the PSD difference between PSCCH and PSSCH shall be the same as the PSD offset value. For the measured configured maximum output power PUMAX,c for E-UTRA V2X sidelink transmissions non-concurrent with E-UTRA uplink transmissions, the same requirement as in subclause 6.2.5 shall be applied. When a UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the UE is allowed to set its configured maximum output power PCMAX,c,E-UTRA and PCMAX,c,V2X for the configured E-UTRA uplink carrier and the configured E-UTRA V2X carrier, respectively, and its total configured maximum output power PCMAX,c. The ο οTIB,c of PCMAX,c,E-UTRA is specified in Table 6.2.5G-1. The configured maximum output power PCMAX c,E-UTRA(p) in subframe p for the configured E-UTRA uplink carrier shall be set within the bounds: PCMAX_L,c,E-UTRA (p) β€ PCMAX,c,E-UTRA (p) β€ PCMAX_H,c,E-UTRA (p) where PCMAX_L,c,E-UTRA and PCMAX_H,c,E-UTRA are the limits for a serving cell c as specified in subclause 6.2.5. The configured maximum output power PCMAX c,V2X (q) in subframe q for the configured E-UTRA V2X carrier shall be set within the bounds: PCMAX,c,V2X (q) β€ PCMAX_H,c,V2X (q) where PCMAX_H,c,V2X is the limit as specified in subclause 6.2.5G. The total UE configured maximum output power PCMAX (p,q) in a subframe p of an E-UTRA uplink carrier and a subframe q of an E-UTRA V2X sidelink that overlap in time shall be set within the following bounds for synchronous and asynchronous operation unless stated otherwise: PCMAX_L (p,q) β€ PCMAX (p,q) β€ PCMAX_H (p,q) with PCMAX_L (p,q) = PCMAX_L,c,E-UTRA (p) PCMAX_H (p,q) = 10 log10 [pCMAX_H,c,E-UTRA (p) + pCMAX_H,c,V2X (q)] where pCMAX_H,c,V2X and pCMAX_H,c,E-UTRA are the limits PCMAX_H,c,V2X (q) and PCMAX_H,c,E-UTRA (p) expressed in linear scale. The measured total maximum output power PUMAX over both the E-UTRA uplink and E-UTRA V2X carriers is PUMAX = 10 log10 [pUMAX,c,E-UTRA + pUMAX,c,V2X], where pUMAX,c,E-UTRA denotes the measured output power of serving cell c for the configured E-UTRA uplink carrier, and pUMAX,c,V2X denotes the measured output power for the configured E-UTRA V2X carrier expressed in linear scale. When a UE is configured for synchronous V2X sidelink and uplink transmissions, PCMAX_L(p, q) β TLOW (PCMAX_L(p, q)) β€ PUMAX β€ PCMAX_H(p, q) + THIGH (PCMAX_H(p, q)) where PCMAX_L (p,q) and PCMAX_H (p,q) are the limits for the pair (p,q) and with the tolerances TLOW(PCMAX) and THIGH(PCMAX) for applicable values of PCMAX specified in Table 6.2.5G-2. PCMAX_L may be modified for any overlapping portion of subframes (p, q) and (p +1, q+1). When a UE is configured for asynchronous V2X and uplink transmissions, the subframe p for the E-UTRA uplink carrier and subframe q for the E-UTRA V2X carrier overlap in time and 1. if uplink carrier leads in time over q and V2X UE sidelink transmission has SCI whose βPriorityβ field is set to a value less than the high layer parameter thresSL-TxPrioritization, then p is the reference subframe and the (p,q) and (p,q-1) pairs are considered for determining the PCMAX tolerance 2. if uplink carrier leads in time over q and V2X UE sidelink transmission has SCI whose βPriorityβ field is set to a value larger than the high layer parameter thresSL-TxPrioritization, then q is the reference subframe and the (p,q) and (p+1,q) pairs are considered for determining the PCMAX tolerance 3. if V2X carrier leads in time over p and V2X UE sidelink transmission has SCI whose βPriorityβ field is set to a value less than the high layer parameter thresSL-TxPrioritization, then p is the reference subframe and the (p,q) and (p,q+1) pairs are considered for determining the PCMAX tolerance 4. if V2X carrier leads in time over p and V2X UE sidelink transmission has SCI whose βPriorityβ field is set to a value larger than the high layer parameter thresSL-TxPrioritization,, then q is the reference subframe and the (p-1,q) and (p,q) pairs are considered for determining the PCMAX tolerance For the reference subframe p duration when uplink carrier leads: P'CMAX_L = PCMAX_L,,cE-UTRA (p) P'CMAX_H = MAX {PCMAX_H (p,q-1) , PCMAX_H (p,q)} For the reference subframe p duration when V2X carrier leads: P'CMAX_L = PCMAX_L,c,E-UTRA (p) P'CMAX_H = MAX {PCMAX_H (p,q) , PCMAX_H (p,q+1)} For the reference subframe q duration when uplink carrier leads: P'CMAX_L = PCMAX_L,c, E-UTRA (q) P'CMAX_H = MAX {PCMAX_H (p,q) , PCMAX_H (p+1,q)} For the reference subframe q duration when V2X carrier leads: P'CMAX_L = PCMAX_L,c, E-UTRA (p) P'CMAX_H = MAX {PCMAX_H (p-1,q) , PCMAX_H (p,q)} where PCMAX_L,,cE-UTRA (p) and PCMAX_H are the applicable limits for each overlapping subframe pairs above 4case with (p,q), (p, q-1) or (p,q), (p, q+1) or (p,q), (p+1,q) or (p,q), (p-1, q). The measured total configured maximum output power PUMAX shall be within the following bounds: PβCMAX_L β TLOW (PβCMAX_L) β€ PUMAX β€ PβCMAX_H + THIGH (PβCMAX_H) with the tolerances TLOW(PCMAX) and THIGH(PCMAX) for applicable values of PCMAX specified in Table 6.2.5G-2. For intra-band contiguous multi-carrier operation, MPRc = MPR and A-MPRc = A-MPR with MPR and A-MPR specified in subclause 6.2.3G and subclause 6.2.4G respectively. There is one power management term for the UE, denoted P-MPR, and P-MPR c = P-MPR. PCMAX,c is calculated under the assumption that the transmit power is increased by the same amount in dB on all component carriers. The total configured maximum output power PCMAX shall be set within the following bounds: PCMAX_L β€ PCMAX β€ PCMAX_H PCMAX_L = MIN{10 log10 β pEMAX,c - οTC , PPowerClass β MAX(MPR + A-MPR + ΞTIB,c + οTC + οTProSe, P-MPR ), PRegulatory } PCMAX_H = MIN{10 log10 β pEMAX,c , PPowerClass, PRegulatory } where - pEMAX,c is the linear value of PEMAX,c which is given by IE maxTxPower in [7]; - PPowerClass is the maximum UE power specified in Table 6.2.2G-1 without taking into account the tolerance specified in the Table 6.2.2G-1; - MPR and A-MPR are specified in subclause 6.2.3G and subclause 6.2.4G respectively; - οTIB,c is the additional tolerance for serving cell c as specified in Table 6.2.5-2; - P-MPR is the power management term for the UE; - οTC is the highest value οTC,c among all serving cells c in the subframe over both timeslots. οTC,c = 1.5 dB when NOTE 2 in Table 6.2.2-1 applies, otherwise οTC,c = 0 dB; - οTProSe applies as specified in subclause 6.2.5. - PRegulatoryο = 10 - Gpost connector dBm when V2X UE is within the protected zone [13] of CEN DSRC tolling system and operating in Band 47; PRegulatoryο = 33 - Gpost connector dBm otherwise. NOTE: The supported post antenna connector gain Gpost connector declared by the UE following the principle described in annex I. Table 6.2.5G-1: ΞTIB,c for inter-band con-current V2X operation (two bands) For V2X UE supporting Transmit Diversity, the transmitted power is configured per each UE. If the UE transmits on two antenna connectors at the same time, the tolerance is specified in Table 6.2.5G-2 and 6.2.5G-3 for PC2 and PC3 V2X UE respectively. Table 6.2.5G-2: PCMAX,c tolerance in Transmit Diversity scheme for PC2 V2X UE Table 6.2.5G-3: PCMAX,c tolerance in Transmit Diversity scheme for PC3 V2X UE If the UE transmits on one antenna connector at a time, the requirements in Table 6.2.5-1 apply to the active antenna connector. | 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.2.5G |
2,163 | A.20 Use case of RSRQ | E-UTRAN RSRQ measurement can be used to calculate signal quality distribution. According to signal quality dstribution and other measurements like AOA, UE Rx-Tx time diffrence, the general signal quality information of cells can be learned, so that interference heavy area can be found more easily by driving test. Also it can be used to evaluate user satisfaction to some extent. So it is necessary to define the RSRQ measurements. In order to reduce the transmission bandwidth requirement, according to network optimization experience, 1dB granularity of measurement is enough. | 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 | A.20 |
2,164 | 16.1.3 Packet Duplication | When duplication is configured for a radio bearer by RRC, at least one secondary RLC entity is added to the radio bearer to handle the duplicated PDCP PDUs as depicted on Figure 16.1.3-1, where the logical channel corresponding to the primary RLC entity is referred to as the primary logical channel, and the logical channel corresponding to the secondary RLC entity(ies), the secondary logical channel(s). All RLC entities have the same RLC mode. Duplication at PDCP therefore consists in submitting the same PDCP PDUs multiple times: once to each activated RLC entity for the radio bearer. With multiple independent transmission paths, packet duplication therefore increases reliability and reduces latency and is especially beneficial for URLLC services. Figure 16.1.3-1: Packet Duplication NOTE: PDCP control PDUs are not duplicated and always submitted to the primary RLC entity. When configuring duplication for a DRB, RRC also sets the state of PDCP duplication (either activated or deactivated) at the time of (re-)configuration. After the configuration, the PDCP duplication state can then be dynamically controlled by means of a MAC control element and in DC, the UE applies the MAC CE commands regardless of their origin (MCG or SCG). When duplication is configured for an SRB the state is always active and cannot be dynamically controlled. When configuring duplication for a DRB with more than one secondary RLC entity, RRC also sets the state of each of them (i.e. either activated or deactivated). Subsequently, a MAC CE can be used to dynamically control whether each of the configured secondary RLC entities for a DRB should be activated or deactivated, i.e. which of the RLC entities shall be used for duplicate transmission. Primary RLC entity cannot be deactivated. When duplication is deactivated for a DRB, all secondary RLC entities associated to this DRB are deactivated. When a secondary RLC entity is deactivated, it is not re-established, the HARQ buffers are not flushed, and the transmitting PDCP entity should indicate to the secondary RLC entity to discard all duplicated PDCP PDUs. When activating duplication for a DRB, NG-RAN should ensure that at least one serving cell is activated for each logical channel associated with an activated RLC entity of the DRB; and when the deactivation of SCells leaves no serving cells activated for a logical channel of the DRB, NG-RAN should ensure that duplication is also deactivated for the RLC entity associated with the logical channel. When duplication is activated, the original PDCP PDU and the corresponding duplicate(s) shall not be transmitted on the same carrier. The logical channels of a radio bearer configured with duplication can either belong to the same MAC entity (referred to as CA duplication) or to different ones (referred to as DC duplication). CA duplication can also be configured in either or both of the MAC entities together with DC duplication when duplication over more than two RLC entities is configured for the radio bearer. In CA duplication, logical channel mapping restrictions are used in a MAC entity to ensure that the different logical channels of a radio bearer in the MAC entity are not sent on the same carrier. When CA duplication is configured for an SRB, one of the logical channels associated to the SRB is mapped to SpCell. When CA duplication is deactivated for a DRB in a MAC entity (i.e. none or only one of RLC entities of the DRB in the MAC entity remains activated), the logical channel mapping restrictions of the logical channels of the DRB are lifted for as long as CA duplication remains deactivated for the DRB in the MAC entity. When an RLC entity acknowledges the transmission of a PDCP PDU, the PDCP entity shall indicate to the other RLC entity(ies) to discard it. In addition, in case of CA duplication, when an RLC entity restricted to only SCell(s) reaches the maximum number of retransmissions for a PDCP PDU, the UE informs the gNB but does not trigger RLF. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.1.3 |
2,165 | 5.8.9.7.2 PC5 Relay RLC channel addition/modification | Upon PC5-RRC connection establishment between the L2 U2N Relay UE and L2 U2N Remote UE, the L2 U2N Relay UE shall: 1> establish a SRAP entity as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66], if no SRAP entity has been established; 1> apply RLC specified configuration of SL-RLC0 as specified in clause 9.1.1.4: 1> apply RLC default configuration of SL-RLC1 as defined in clause 9.2.4 if the L2 U2N Relay UE is in RRC_IDLE/INACTIVE state; Upon PC5-RRC connection establishment between the L2 U2U Remote UE and L2 U2U Relay UE, and PC5-RRC connection establishment between the L2 U2U Relay UE and peer L2 U2U Remote UE, the L2 U2U Remote UE or L2 U2U Relay UE shall: 1> establish a SRAP entity as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66], if no SRAP entity has been established; 1> apply RLC specified configuration of SL-U2U-RLC as specified in clause 9.1.1.4; The UE shall: 1> if the PC5 Relay RLC channel addition/modification was triggered due to the reception of the RRCReconfigurationSidelink message; or 1> after receiving the RRCReconfigurationCompleteSidelink message, if the PC5 Relay RLC channel addition/modification was triggered due to the configuration received within the sl-ConfigDedicatedNR; or 1> after receiving the RRCReconfigurationCompleteSidelink message, if the PC5 Relay RLC channel addition/modification was triggered for an end-to-end sidelink DRB based on the configuration in SIB12 or SidelinkPreconfigNR: 2> if the current configuration contains a PC5 Relay RLC channel with the received sl-RLC-ChannelID or sl-RLC-ChannelID-PC5; or 2> if the configuration in SIB12 or SidelinkPreconfigNR has updated, based on which the PC5 Relay RLC channel is derived: 3> reconfigure the sidelink RLC entity in accordance with the received sl-RLC-Config or sl-RLC-ConfigPC5; 3> reconfigure the sidelink MAC entity with a logical channel in accordance with the received sl-MAC-LogicalChannelConfig or sl-MAC-LogicalChannelConfigPC5; 2> else (a PC5 Relay RLC channel with the received sl-RLC-ChannelID or sl-RLC-ChannelID-PC5 was not configured before): 3> establish a sidelink RLC entity in accordance with the received sl-RLC-Config (in sl-ConfigDedicatedNR, or SIB12, or SidelinkPreconfigNR) or sl-RLC-ConfigPC5; 3> configure the sidelink MAC entity with a logical channel in accordance with the received sl-MAC-LogicalChannelConfig or sl-MAC-LogicalChannelConfigPC5. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.7.2 |
2,166 | 4.3.17.7 High latency communication | Functions for High latency communication may (depending on operator configuration) be used to handle mobile terminated (MT) communication with UEs being unreachable while using power saving functions (e.g. UE Power Saving Mode (see clause 4.3.22) or extended idle mode DRX (see clause 5.13a)) or UEs that are using a satellite access with discontinuous coverage. "High latency" refers to the initial response time before normal exchange of packets is established. That is, the time it takes before a UE has woken up from its power saving state and responded to the initial downlink packet(s). The feature is described in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. The High latency communication includes invoking extended buffering of MT data at the Serving GW when the UE is in a power saving state and not reachable. The handling is specified in the Network Triggered Service Request procedure, clause 5.3.4.3. Establishing the user plane for delivering the buffered data when the UE contacts the MME or SGSN by signalling shall be done in the Tracking Area Update and Routing Area Update procedures. The MME/SGSN uses its parameter DL Data Buffer Expiration Time in the MM context information to remember if there is buffered DL data to be delivered when the UE becomes reachable. When set, the DL Data Buffer Expiration Time shall be cleared at any user plane setup to the RAN, i.e. buffered DL data can been delivered. At TAU/RAU procedures with MME/SGSN change, the old MME/SGSN shall indicate in the context response to the new MME/SGSN that buffered DL data is waiting and hence the new MME/SGSN shall establish the user plane for delivery of the buffered DL data. When the DL Data Buffer Expiration Time has expired, the MME/SGSN considers no DL data to be buffered and no indications of Buffered DL Data Waiting are sent during context transfers at TAU procedures. At TAU/RAU procedures with Serving GW change, the buffered DL data is forwarded to the new Serving GW or Gn/Gp-SGSN. For Control Plane CIoT EPS Optimisation, the High latency communication includes invoking the buffering of MT data at the Serving GW or the MME as specified in Mobile Terminated Data Transport in Control Plane CIoT EPS Optimisation with P-GW connectivity, clause 5.3.4B.3. When the UE contacts MME, MME delivers the buffered data using NAS PDUs. If MT data is buffered in MME, at TAU procedures with MME change the buffered data in the old MME is discarded. The High latency communication also includes sending event notifications to application servers that have requested "UE Reachability" or "Availability after DDN failure" monitoring events. Event notifications are sent when a UE becomes reachable, for example as part of the Attach Procedure, TAU/RAU procedures and the UE triggered Service Request procedure. When "UE Reachability" monitoring is requested for UE's that are using extended idle mode DRX, an event notification is sent to the application server when the UE is about to become reachable for paging. If the MME is aware that some signalling or data is pending in the network for an UE that is known as being unreachable for a long duration, e.g. for UE's having extended idle mode DRX or PSM enabled, the MME may include a Pending Data indication in the next S1-AP message towards an eNodeB. If the eNodeB receives this indication, the eNodeB may take this information into account when determining user inactivity. At inter-RAN node handovers, if some signalling or data are still pending, the target MME may send a Pending Data indication to the target RAN node. | 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.17.7 |
2,167 | 5.5a.1.3 Reception of the LoggedMeasurementConfiguration by the UE | Upon receiving the LoggedMeasurementConfiguration message the UE shall: 1> discard the logged measurement configuration as well as the logged measurement information as specified in 5.5a.2; 1> store the received loggingDuration, reportType and areaConfiguration, if included, in VarLogMeasConfig; 1> If the UE is registered in SNPN: 2> if the LoggedMeasurementConfiguration message includes snpn-ConfigList: 3> set the snpn-ConfigIDList in VarLogMeasReport to include the current registered SNPN ID as well as SNPN IDs in snpn-ConfigList; 2> else: 3> set the snpn-ConfigIDList in VarLogMeasReport to include the current registered SNPN ID; 1> else if the LoggedMeasurementConfiguration message includes plmn-IdentityList: 2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN as well as the PLMNs included in plmn-IdentityList; 1> else: 2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN; 1> store the received absoluteTimeInfo, traceReference, traceRecordingSessionRef, and tce-Id in VarLogMeasReport; 1> store the received bt-NameList, if included, in VarLogMeasConfig; 1> store the received wlan-NameList, if included, in VarLogMeasConfig; 1> store the received sensor-NameList, if included, in VarLogMeasConfig; 1> start timer T330 with the timer value set to the loggingDuration; 1> store the received sigLoggedMeasType, if included, in VarLogMeasReport; 1> store the received earlyMeasIndication, if included, in VarLogMeasConfig; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5a.1.3 |
2,168 | D.5.1 Service area and connection density | It is relatively hard to provide estimates for the service area dimension. One reason is that it depends on the placement of the base station relative to the RSUs. Also, the RSUs can, in principle, act as relay nodes for each other. The service area dimension stated in table 7.2.3.2-1 indicates the size of the typical data collection area of an RSU (2 km along a road), from which the minimum spacing of RSUs can be inferred. The connection density can be quite high in case data is relayed between RSUs, i.e. along the road (1000 km-2). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | D.5.1 |
2,169 | 5.3.5.6.5 DRB addition/modification | The UE shall: 1> for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration (DRB establishment including the case when full configuration option is used): 2> establish a PDCP entity and configure it in accordance with the received pdcp-Config; 2> if the PDCP entity of this DRB is not configured with cipheringDisabled: 3> if target RAT of handover is E-UTRA/5GC; or 3> if the UE is connected to E-UTRA/5GC: 4> if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC: 5> configure the PDCP entity with the ciphering algorithm and KUPenc key configured/derived as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; 4> else (i.e., a UE capable of NGEN-DC): 5> configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the key (KUPenc) associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable; 3> else (i.e., UE connected to NR or UE connected to E-UTRA/EPC): 4> configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the KUPenc key associated with the master key (KeNB/KgNB) or the secondary key (S-KgNB/S-KeNB) as indicated in keyToUse; 2> if the PDCP entity of this DRB is configured with integrityProtection: 3> configure the PDCP entity with the integrity protection algorithms according to securityConfig and apply the KUPint key associated with the master (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse; 2> if an sdap-Config is included: 3> if an SDAP entity with the received pdu-Session does not exist: 4> establish an SDAP entity as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24] clause 5.1.1; 4> if an SDAP entity with the received pdu-Session did not exist prior to receiving this reconfiguration: 5> indicate the establishment of the user plane resources for the pdu-Session to upper layers; 3> configure the SDAP entity in accordance with the received sdap-Config as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24] and associate the DRB with the SDAP entity; 3> for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB; 2> if the DRB is associated with an eps-BearerIdentity: 3> if the DRB was configured with the same eps-BearerIdentity either by NR or E-UTRA prior to receiving this reconfiguration: 4> associate the established DRB with the corresponding eps-BearerIdentity; 3> else: 4> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers; 1> for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration and configured as DAPS bearer: 2> reconfigure the PDCP entity to configure DAPS with the ciphering function, integrity protection function and ROHC function of the target cell group as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5] and configure it in accordance with the received pdcp-Config; 2> if the masterKeyUpdate is received: 3> if the ciphering function of the target cell group PDCP entity is not configured with cipheringDisabled: 4> configure the ciphering function of the target cell group PDCP entity with the ciphering algorithm according to securityConfig and apply the KUPenc key associated with the master key (KgNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received from the target cell group and sent to the target cell group by the UE; 3> if the integrity protection function of the target cell group PDCP entity is configured with integrityProtection: 4> configure the integrity protection function of the target cell group PDCP entity with the integrity protection algorithms according to securityConfig and apply the KUPint key associated with the master key (KgNB) as indicated in keyToUse; 2> else: 3> configure the ciphering function and the integrity protection function of the target cell group PDCP entity with the same security configuration as the PDCP entity for the source cell group; 2> if the sdap-Config is included and when indication of successful completion of random access towards target cell is received from lower layers as specified in [3]: 3> reconfigure the SDAP entity in accordance with the received sdap-Config as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24]; 3> for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB; 1> for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration and not configured as DAPS bearer: 2> if the reestablishPDCP is set: 3> if target RAT of handover is E-UTRA/5GC; or 3> if the UE is connected to E-UTRA/5GC: 4> if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC: 5> if the PDCP entity of this DRB is not configured with cipheringDisabled: 6> configure the PDCP entity with the ciphering algorithm and KUPenc key configured/derived as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.4.2.3, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE; 4> else (i.e., a UE capable of NGEN-DC): 5> if the PDCP entity of this DRB is not configured with cipheringDisabled: 6> configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master key (KeNB) or the secondary key (S-KgNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE; 3> else (i.e., UE connected to NR or UE connected to E-UTRA/EPC (in EN-DC or capable of EN-DC)): 4> if the PDCP entity of this DRB is not configured with cipheringDisabled: 5> configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master key (KeNB/ KgNB) or the secondary key (S-KgNB/S-KeNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE; 4> if the PDCP entity of this DRB is configured with integrityProtection: 5> configure the PDCP entity with the integrity protection algorithms according to securityConfig and apply the KUPint key associated with the master key (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse; 3> if drb-ContinueROHC is included in pdcp-Config: 4> indicate to lower layer that drb-ContinueROHC is configured; 3> if drb-ContinueEHC-DL is included in pdcp-Config: 4> indicate to lower layer that drb-ContinueEHC-DL is configured; 3> if drb-ContinueEHC-UL is included in pdcp-Config: 4> indicate to lower layer that drb-ContinueEHC-UL is configured; 3> if drb-ContinueUDC is included in pdcp-Config: 4> indicate to lower layer that drb-ContinueUDC is configured; 3> re-establish the PDCP entity of this DRB as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5], clause 5.1.2; 2> else, if the recoverPDCP is set: 3> trigger the PDCP entity of this DRB to perform data recovery as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 2> if the pdcp-Config is included: 3> reconfigure the PDCP entity in accordance with the received pdcp-Config. 2> if the sdap-Config is included: 3> reconfigure the SDAP entity in accordance with the received sdap-Config as specified in TS37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24]; 3> for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB; NOTE 1: Void. NOTE 2: When determining whether a drb-Identity value is part of the current UE configuration, the UE does not distinguish which RadioBearerConfig and DRB-ToAddModList that DRB was originally configured in. To re-associate a DRB with a different key (KeNB to S-KgNB, KgNB to S-KeNB, KgNB to S-KgNB, or vice versa), the network provides the drb-Identity value in the (target) drb-ToAddModList and sets the reestablishPDCP flag. The network does not list the drb-Identity in the (source) drb-ToReleaseList. NOTE 3: When setting the reestablishPDCP flag for a radio bearer, the network ensures that the RLC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. It does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old RLC entity or by releasing the old RLC entity. NOTE 4: In this specification, UE configuration refers to the parameters configured by NR RRC unless otherwise stated. NOTE 5: Ciphering and integrity protection can be enabled or disabled for a DRB. The enabling/disabling of ciphering or integrity protection can be changed only by releasing and adding the DRB. NOTE 6: In DAPS handover, the UE may perform PDCP entity re-establishment (if reestablishPDCP is set) or the PDCP data recovery (if recoverPDCP is set) for a non-DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]. In this case, the UE suspends data transmission and reception for all non-DAPS bearers in the source MCG for duration of the DAPS handover. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.6.5 |
2,170 | 4.5.4.2 Access control and checking in 5GMM-CONNECTED mode and in 5GMM-CONNECTED mode with RRC inactive indication | When the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication, upon detecting one of events 1) through 8) listed in subclause 4.5.1, the NAS shall categorize the corresponding access attempt into access identities and an access category following: a) subclause 4.5.2, table 4.5.2.1 and table 4.5.2.2, and subclause 4.5.3, if the UE is not operating in SNPN access operation mode over 3GPP access ; or b) subclause 4.5.2A, table 4.5.2A.1 and table 4.5.2A.2, and subclause 4.5.3, if the UE is operating in SNPN access operation mode over 3GPP access , and provide the access identities and the access category to the lower layers for the purpose of access control checking. In this request to the lower layer the NAS can also provide to the lower layer the RRC establishment cause determined as specified in subclause 4.5.6 of this specification. NOTE 1: As an implementation option, the NAS can provide the RRC establishment cause to the lower layers after being informed by the lower layers that the access attempt is allowed. If the UE has uplink user data pending for one or more PDU sessions when it builds a REGISTRATION REQUEST or SERVICE REQUEST message for the access attempt, the UE shall indicate the respective PDU sessions in the Uplink data status IE as specified in subclause 5.5.1.3.2 and 5.6.1.2, regardless of the access category for which the access barring check is performed. NOTE 2: The UE indicates pending user data for all the respective PDU sessions, even if barring timers are running for some of the corresponding access categories. If the lower layers indicate that the access attempt is allowed, the NAS shall take the following action depending on the event which triggered the access attempt: a) if the event which triggered the access attempt was an MO-MMTEL-voice-call-started indication, an MO-MMTEL-video-call-started indication, an MO-SMSoIP-attempt-started indication, or an MO-IMS-registration-related-signalling-started indication, the NAS shall notify the upper layers that the access attempt is allowed; b) if the event which triggered the access attempt was a request from upper layers to send a mobile originated SMS over NAS, 5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send the SMS in an UL NAS TRANSPORT message; c) if the event which triggered the access attempt was a request from upper layers to establish a new PDU session, 5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send the PDU SESSION ESTABLISHMENT REQUEST message; d) if the event which triggered the access attempt was a request from upper layers to modify an existing PDU session, 5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send the PDU SESSION MODIFICATION REQUEST message; e) if the event which triggered the access attempt was a request to re-establish the user-plane resources for an existing PDU session, 5GMM shall initiate the service request procedure as specified in subclause 5.6.1; f) if the event which triggered the access attempt was an uplink user data packet to be sent for a PDU session with suspended user-plane resources, 5GMM shall consider that the uplink user data packet is allowed to be sent; g) if the event which triggered the access attempt was a request from upper layers to send a mobile originated location request, 5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send an LCS message in an UL NAS TRANSPORT message; and h) if the event which triggered the access attempt was a request from upper layers to send a mobile originated signalling transaction towards the PCF by sending an UL NAS TRANSPORT message including a UE policy container (see 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B] and 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]), 5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send the signalling transaction via an UL NAS TRANSPORT message. If the lower layers indicate that the access attempt is barred, the NAS shall take the following action depending on the event which triggered the access attempt: a) if the event which triggered the access attempt was an MO-MMTEL-voice-call-started indication, an MO-MMTEL-video-call-started indication or an MO-SMSoIP-attempt-started indication, or an MO-IMS-registration-related-signalling-started indication: 1) if the UE is operating in the dual-registration mode, the UE may proceed in S1 mode with the appropriate EMM specific procedures and ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.3 and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; 2) otherwise, the NAS shall notify the upper layers that the access attempt is barred. In this case, upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS shall notify the upper layers that the barring is alleviated for the access category; NOTE 3: In this case prohibiting the initiation of the MMTEL voice session, MMTEL video session or prohibiting sending of the SMS over IP or the IMS registration related signalling is performed by the upper layers. b) if the event which triggered the access attempt was a request from upper layers to send a mobile originated SMS over NAS, 5GMM shall not initiate the NAS transport procedure as specified in subclause 5.4.5 to send the SMS in an UL NAS TRANSPORT message. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, 5GMM may initiate the NAS transport procedure as specified in subclause 5.4.5 to send the SMS in an UL NAS TRANSPORT message, if still needed; c) if the event which triggered the access attempt was a request from upper layers to establish a new PDU session, 5GMM shall not initiate the NAS transport procedure to send the PDU SESSION ESTABLISHMENT REQUEST message. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS may initiate the NAS transport procedure as specified in subclause 5.4.5, if still needed; d) if the event which triggered the access attempt was a request from upper layers to modify an existing PDU session modification, 5GMM shall not initiate the NAS transport procedure to send the PDU SESSION MODIFICATION REQUEST message. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS may initiate the NAS transport procedure as specified in subclause 5.4.5, if still needed; e) if the event which triggered the access attempt was a request to re-establish the user-plane resources for an existing PDU session, the NAS shall not initiate the service request procedure as specified in subclause 5.6.1. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS may initiate the service request procedure as specified in subclause 5.6.1, if still needed; f) if the event which triggered the access attempt was an uplink user data packet to be sent for a PDU session with suspended user-plane resources, 5GMM shall consider that the uplink user data packet is not allowed to be sent. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS shall consider that the barring is alleviated for the access category; g) if the event which triggered the access attempt was a request from upper layers to send a mobile originated location request, 5GMM shall not initiate the NAS transport procedure as specified in subclause 5.4.5 to send an LCS message in an UL NAS TRANSPORT message. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, 5GMM may initiate the NAS transport procedure as specified in subclause 5.4.5 to send the LCS message in an UL NAS TRANSPORT message, if still needed; and h) if the event which triggered the access attempt was a request from upper layers to send a mobile originated signalling transaction towards the PCF by sending an UL NAS TRANSPORT message including a UE policy container (see 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B] and 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]), 5GMM shall not initiate the NAS transport procedure as specified in subclause 5.4.5 to send the mobile originated signalling transaction via an UL NAS TRANSPORT message. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, 5GMM may initiate the NAS transport procedure as specified in subclause 5.4.5 to send the mobile originated signalling transaction via an UL NAS TRANSPORT message, if still needed. | 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.5.4.2 |
2,171 | 5.4.7 Network slice-specific authentication and authorization procedure 5.4.7.1 General | The purpose of the network slice-specific authentication and authorization procedure is to enable the authentication, authorization and accounting server (AAA-S) via the Network Slice Specific and SNPN Authentication and Authorization Function (NSSAAF) to (re-)authenticate or (re-)authorize the upper layers of the UE. The network slice-specific authentication and authorization procedure can be invoked for a UE supporting network slice-specific authentication and authorization procedure and for a HPLMN S-NSSAI or an SNPN S-NSSAI (see subclauses 5.15.10 and 5.30.2.9 in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and subclause 4.2.9.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]). The network (re-)authenticates the UE using the EAP as specified in IETF RFC 3748 [34]. EAP has defined four types of EAP messages: a) an EAP-request message; b) an EAP-response message; c) an EAP-success message; and d) an EAP-failure message. The EAP-request message is transported from the network to the UE using the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message of the network slice-specific EAP message reliable transport procedure. The EAP-response message to the EAP-request message is transported from the UE to the network using the NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message of the network slice-specific EAP message reliable transport procedure. If the (re-)authentication of the UE completes successfully or unsuccessfully, the EAP-success message or the EAP-failure message, respectively, is transported from the network to the UE using the NETWORK SLICE-SPECIFIC AUTHENTICATION RESULT message of the network slice-specific result message transport procedure. There can be several rounds of exchange of an EAP-request message and a related EAP-response message for the AAA-S via the NSSAAF to complete the (re-)authentication and (re-)authorization of the request for an S-NSSAI (see example in figure 5.4.7.1.1). The AMF shall set the authenticator retransmission timer specified in subclause 4.3 of IETF RFC 3748 [34] to infinite value. NOTE: The network slice-specific authentication and authorization procedure provides a reliable transport of EAP messages and therefore retransmissions at the EAP layer of the AMF do not occur. Figure 5.4.7.1.1: Network slice-specific authentication and authorization procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.7 |
2,172 | 11.2.2 Access to networks handling Non-IP data services through Packet Domain | The support of Non-IP data is part of the CIoT EPS optimisations (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77]) and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]). A PDN/PDP Type "Non-IP" is used for Non-IP data. The Non-IP data delivery to the network handling Non-IP data services is accomplished by one of two mechanisms: - Delivery using SCEF - Delivery using a Point-to-Point (PtP) SGi tunnel Data delivery using SCEF is further described in 3GPP TS 29.128[ Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications ] [110]. In order to allow Non-IP delivery data using SGi PtP tunnelling based on UDP/IP (see subclause 11.8), the Packet Domain may offer direct transparent access to the Non-IP Packet Data Network with the following characteristics: - The IPv4 address and/or IPv6 prefix is assigned as part of the PDN connection establishment and identifies the PDN connection of the UE within the PLMN domain. - IP address allocation procedures for the UE (i.e. PDN connection) are performed by the GGSN/P-GW based on APN configuration. Only a single IP address is used (i.e. either IPv4 or IPv6 prefix+Interface Identifier is allocated/assigned). In case of IPv6 the GGSN/P-GW assigns an Interface Identifier for the PDN connection. The IP address or IP prefix is not provided to the UE (i.e. SLAAC / Router Advertisements are not performed. DHCP or DHCPv6 are not used). - The assigned IPv4 address or IPv6 prefix is used for UDP/IP encapsulation for PtP tunneling between the Non-IP network and the GGSN/P-GW (see subclause 11.8). - Stateless Address Autoconfiguration does not apply for IPv6. Both IPv4 and IPv6 addresses belong to the operator addressing space. User authentication and encryption of user data when accessing networks handling Non-IP data services is outside 3GPP specification. | 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 | 11.2.2 |
2,173 | 5.18.2a PLMN list and SNPN list handling for network sharing | The AMF prepares lists of PLMN IDs or SNPN IDs suitable as target PLMNs or target SNPNs for use at idle mode cell (re)selection and for use at handover and RRC Connection Release with redirection. The AMF: - provides the UE with the list of PLMNs or list of SNPNs that the UE shall consider as Equivalent to the serving PLMN or the serving SNPN (see TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]); and - provides the NG-RAN with a prioritised list of permitted PLMNs or a prioritized list of permitted SNPNs. When prioritising these PLMNs or SNPNs, the AMF may consider the following information: HPLMN of the UE or the subscribed SNPN of the UE, the serving PLMN or the serving SNPN, a preferred target PLMN (e.g. based on last used EPS PLMN) or a preferred target SNPN, or the policies of the operator(s). For a UE registered in an SNPN, the AMF shall not provide a list of equivalent PLMNs to the UE and shall not provide a list of permitted PLMNs to NG-RAN. For a UE registered in a PLMN, the AMF shall not provide a list of equivalent SNPNs to the UE and shall not provide a list of permitted SNPNs to NG-RAN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.18.2a |
2,174 | 16.10.4 Group Scheduling | The following logical channels are used for MBS delivery: - MTCH: A PTM downlink channel for transmitting MBS data of either multicast session or broadcast session from the network to the UE; - DTCH: A PTP channel defined in clause 6.2.2 for transmitting MBS data of a multicast session from the network to the UE; - MCCH: A PTM downlink channel used for transmitting MBS broadcast or MBS multicast control information associated to one or several MTCH(s) from the network to the UE. Broadcast MCCH and multicast MCCH are independent channels. The multicast MCCH is used only for multicast reception in RRC_INACTIVE state. The following connections between logical channels and transport channels for PTM transmission exist: - MCCH can be mapped to DL-SCH; - MTCH can be mapped to DL-SCH. The following depicts the usage of RNTI for PTM transmission: - A UE can receive different services using same or different G-RNTIs; - A UE can receive different services using same or different G-CS-RNTIs. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.4 |
2,175 | 10.5.4.8 Called party subaddress | The purpose of the Called party subaddress is to identify the subaddress of the called party of a call. For the definition of a subaddress see ITU-T Rec. I.330 [48]. The Called party subaddress information element is coded as shown in figure 10.5.92/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and Table 10.5.119/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The called party subaddress is a type 4 information element with a minimum length of 2 octets and a maximum length of 23 octets. Figure 10.5.92/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Called party subaddress Table 10.5.119/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Called party subaddress | 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.4.8 |
2,176 | 4.5.1.6.2 Abnormal cases | Mobile station side: a) Random access failure or RR connection establishment failure If the mobile station detects a random access failure or RR connection establishment failure during the re-establishment of an MM connection, the re-establishment is aborted and all MM connections are released. b) RR connection failure If a RR connection failure occurs, timer T3230 is stopped, the re-establishment is aborted and all active MM connections are released. c) IMSI deactivation If the IMSI deactivated during the re-establishment attempt then timer T3230 is stopped, the re-establishment is aborted and all MM connections are released. d) T3230 expires If T3230 expires (i.e. no response is given but a RR connection is available) the re-establishment is aborted, all active MM connections are released and the mobile station proceeds as described in subclause 4.5.3.1. e) Reject causes #96, #97, #99, #100, #111 received The mobile station shall perform the same actions as if timer T3230 had expired. Network side: a) RR connection failure If a RR connection failure occurs after receipt of the CM RE-ESTABLISHMENT REQUEST the network shall release all MM connections. b) Invalid message content Upon reception an invalid initial of message or a CM RE-ESTABLISHMENT REQUEST message with invalid content, a CM SERVICE REJECT message shall be returned with one of the following appropriate Reject cause indications: #96: Mandatory information element error #99: Information element non-existent or not implemented #100: Conditional IE error #111: Protocol error, unspecified When the CM SERVICE REJECT message has been sent, the network shall release the RR connection. | 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.5.1.6.2 |
2,177 | β AerialParameters | The IE AerialParameters is used to convey the capabilities supported by the UE for aerial operation. AerialParameters information element -- ASN1START -- TAG-AERIALPARAMETERS-START AerialParameters-r18 ::= SEQUENCE { -- Support of Aerial UE features aerialUE-Capability-r18 ENUMERATED {supported} OPTIONAL, -- Support of altitude measurement and event H1/H2-triggered reporting altitudeMeas-r18 ENUMERATED {supported} OPTIONAL, -- Support of altitude based measurement configuration of SSB-ToMeasure altitudeBasedSSB-ToMeasure-r18 ENUMERATED {supported} OPTIONAL, -- Support of events A3H1, A3H2, A4H1, A4H2, A5H1, A5H2 eventAxHy-r18 ENUMERATED {supported} OPTIONAL, -- Support of flight path reporting flightPathReporting-r18 ENUMERATED {supported} OPTIONAL, -- Support of flight path availability indication via UAI flightPathAvailabilityIndicationUAI-r18 ENUMERATED {supported} OPTIONAL, -- Support of numberOfTriggeringCells for eventA3, eventA4, and eventA5, and additionally, if the UE supports eventAxHy-r18, -- support of numberOfTriggeringCells for eventA3H1, eventA3H2, eventA4H1, eventA4H2, eventA5H1, and eventA5H2 multipleCellsMeasExtension-r18 ENUMERATED {supported} OPTIONAL, -- Support aerial-specific Ns and Pmax list broadcasted by the cell nr-NS-PmaxListAerial-r18 ENUMERATED {supported} OPTIONAL, -- Editor's Note: -- Understanding is that a UE that doesn't support any frequency band that requires an aerial specific NS value doesn't need to -- implement the procedure for aerial specific NS value. Whether indication is needed is still FFS. This is only shown as -- placeholder. Support of reporting only the measurement report corresponding to the event with the smallest value between the -- altitude of the UAV and the altitude threshold for which the altitude-related entering condition e.g. A3H1-2 is satisfied, when -- multiple events of the same type (Hx or AxHy) for the same MO (for AxHy) are triggered simultaneously. simulMultiTriggerSingleMeasReport-r18 ENUMERATED {supported} OPTIONAL, -- Support of A2X service(s) using PC5 Sidelink and dedicated resource pool for A2X service(s) sl-A2X-Service-r18 ENUMERATED {brid, daa, bridAndDAA} OPTIONAL, -- Editor's Note: Granularity of this capability, e.g. per UE/band/FS is still FFS. Depending on the conclusion, this may need to -- be moved. ... } -- TAG-AERIALPARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,178 | 5.6.7 Application Function influence on traffic routing 5.6.7.1 General | The content of this clause applies to non-roaming and to LBO deployments i.e. to cases where the involved entities (AF, PCF, SMF, UPF) belong to the Serving PLMN or AF belongs to a third party with which the Serving PLMN has an SLA agreement. AF influence on traffic routing may apply in the case of Home Routed deployments with Session Breakout (HR SBO) as defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. In that case when an AF belonging to the V-PLMN (or with an offloading SLA with the V PLMN) desires to provide Traffic Influence policies it may invoke at the V-NEF the API defined in this clause and provide the information listed in Table 5.6.7-1 below but the corresponding Traffic Influence information is provided directly from V-NEF to V-SMF bypassing the PCF. This is further defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130] clause 6.7.2. and the rest of the clause 5.6.7.1 does not address how information related with AF influence on traffic routing may be provided to the SMF in the case of HR SBO. PCF shall not apply AF requests to influence traffic routing to PDU Sessions established in Home Routed mode. The AF may determine the common EAS/DNAI for the UE set in order to indicate a common EAS or common local part of DN, and provide the common EAS/DNAI to the 5GS. An AF may send requests to influence SMF routing decisions for traffic of PDU Session. The AF requests may influence UPF (re)selection and (I-)SMF (re)selection and allow routing user traffic to a local access to a Data Network (identified by a DNAI). The AF may issue requests on behalf of applications not owned by the PLMN serving the UE. If the operator does not allow an AF to access the network directly, the AF shall use the NEF to interact with the 5GC, as described in clause 6.2.10. The AF may be in charge of the (re)selection or relocation of the applications within the local part of the DN (as defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]). Such functionality is not defined. For this purpose, the AF may request to get notified about events related with PDU Sessions. In the case of AF instance change, the AF may send request of AF relocation information. The AF requests are sent to the PCF via N5 (in the case of requests targeting specific on-going PDU Sessions of individual UE(s), for an AF allowed to interact directly with the 5GC NFs) or via the NEF. The AF requests that target existing or future PDU Sessions of multiple UE(s) or of any UE are sent via the NEF and may target multiple PCF(s), as described in clause 6.3.7.2. The PCF(s) transform(s) the AF requests into policies that apply to PDU Sessions. When the AF has subscribed to UP path management event notifications from SMF(s) (including notifications on how to reach a GPSI over N6), such notifications are sent either directly to the AF or via an NEF (without involving the PCF). For AF interacting with PCF directly or via NEF, the AF requests may contain the information as described in the Table 5.6.7-1: Table 5.6.7-1: Information element contained in AF request For each information element mentioned above in the AF request, the detailed description is as follows: 1) Information to identify the traffic. The traffic can be identified in the AF request by - Either a DNN and possibly slicing information (S-NSSAI) or an AF-Service-Identifier - When the AF provides an AF-Service-Identifier i.e. an identifier of the service on behalf of which the AF is issuing the request, the 5G Core maps this identifier into a target DNN and slicing information (S-NSSAI) - When the NEF processes the AF request the AF-Service-Identifier may be used to authorize the AF request. - An application identifier or traffic filtering information (e.g. IP 5 Tuple). The application identifier refers to an application handling UP traffic and is used by the UPF to detect the traffic of the application. When the AF request is for influencing SMF routing decisions, the information is to identify the traffic to be routed. When the AF request is for subscription to notifications about UP path management events, the information is to identify the traffic that the events relate to. The AF request may include a PLMN ID of the PLMN that the DNN and S-NSSAI belong to, as described in clause 4.3.6.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. 2) Information about the N6 traffic routing requirements for traffic identified as defined in 1). This includes: - Information about the N6 traffic routing requirements that is provided per DNAI: for each DNAI, the N6 traffic routing requirements may contain a routing profile ID and/or N6 traffic routing information. - An optional indication of traffic correlation, when the information in 4) identifies a group of UEs. This implies the targeted PDU Sessions should be correlated by a common DNAI in the user plane for the traffic identified in 1). If this indication is provided by the AF, the 5GC should select a common DNAI for the target PDU Sessions from the list of DNAI(s) specified in 3). NOTE 1: The N6 traffic routing requirements are related to the mechanism enabling traffic steering in the local access to the DN. The routing profile ID refers to a pre-agreed policy between the AF and the 5GC. This policy may refer to different steering policy ID(s) sent to SMF and e.g. based on time of the day etc. NOTE 2: The mechanisms enabling traffic steering in the local access to the DN are not defined. 3) Potential locations of applications towards which the traffic routing should apply. The potential location of application is expressed as a list of DNAI(s). If the AF interacts with the PCF via the NEF, the NEF may map the AF-Service-Identifier information to a list of DNAI(s). The DNAI(s) may be used for UPF (re)selection and (I-)SMF (re)selection. When only one DNAI is included, and the Indication of traffic correlation is available, the DNAI is used as common DNAI for UEs identified by AF request. The AF request may include a PLMN ID of the PLMN that the list of DNAI(s) belongs to, as described in clause 4.3.6.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. 4) Information on the set of target UE(s). This may correspond to: - Individual UEs (i.e. one or a list of UEs) identified using GPSI, or an IP address/Prefix or a MAC address. - Group(s) of UEs identified by External Group Identifier(s) as defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [36] when the AF interacts via the NEF, or Internal-Group Identifier (see clause 5.9.7) when the AF interacts directly with the PCF. - Any UE accessing the combination of DNN, S-NSSAI and DNAI(s). - External Group ID(s) or any UE can both be complemented with External Subscriber Category(s) for a more granular selection of UEs. NEF may map this to Internal Group ID(s) or a combination of Internal Group ID(s) and Subscriber Category(s), defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE 3: Only NEF is aware of the External Subscriber Category. As a user can be associated with multiple Subscriber Category(s), some values of Subscriber Category(s) can correspond to an SLA between an application provider represented by an AF and the 5GC operator. In the NEF API, the combination of application identifier and External Subscriber Category can also be used to refer to this SLA. When the PDU Session type is IPv4 or IPv6 or IPv4v6, and the AF provides an IP address and/or an IP Prefix, or when the PDU Session type is Ethernet and the AF provides a MAC address, this allows the PCF to identify the PDU Session for which this request applies and the AF request applies only to that specific PDU Session of the UE. In this case, additional information such as the UE identity may also be provided to help the PCF to identify the correct PDU Session. Otherwise, the request targets multiple UE(s) and shall apply to any existing or future PDU Sessions that match the parameters in the AF request. When the AF request targets an individual or a list of UE(s) and GPSI is provided within the AF request, the GPSI is mapped to SUPI according to the subscription information received from UDM. When the AF request targets any UE or a group of UE, the AF request is likely to influence multiple PDU Sessions possibly served by multiple SMFs and PCFs. When the AF request targets a group of UE it provides one or several group identifiers in its request. The group identifiers provided by the AF are mapped to Internal-Group identifiers. Members of the group have Group Identifier(s) in their subscription. The Internal-Group Identifier(s) is(are) stored in UDM, retrieved by SMF from UDM and passed by SMF to PCF at PDU Session set-up. The PCF can then map the AF request with user subscription and determine whether an AF request targeting a Group of users applies to a PDU Session. When External Subscriber Category(s) is provided, the NEF maps External Subscriber Category(s) into Subscriber Category(s), the PCF can map the AF request with user subscription and then creates PCC rules for UEs that have the Subscriber Category(s) in their subscription. When the AF request is for influencing SMF routing decisions, the information is to identify UE(s) whose traffic is to be routed. When the AF request is for subscription to notifications about UP path management events, the information is to identify UE(s) whose traffic the events relate to. When the AF request is for traffic forwarding in a PDU Session serving for TSC, the MAC address used by the PDU Session is determined by the AF to identify UE whose traffic is to be routed according to the previously stored binding relationship of the 5GS Bridge and the port number of the traffic forwarding information received from TSN network. 5) Indication of application relocation possibility. This indicates whether an application can be relocated once a location of the application is selected by the 5GC. If application relocation is not possible, the 5GC shall ensure that for the traffic related with an application, no DNAI change takes place once selected for this application. 6) Temporal validity condition. This is provided in the form of time interval(s) or duration(s) during which the AF request is to be applied. When the AF request is for influencing SMF routing decisions, the temporal validity condition indicates when the traffic routing is to apply. When the AF request is for subscription to notifications about UP path management events, the temporal validity condition indicates when the notifications are to be generated. 7) Spatial validity condition on the UE(s) location. This is provided in the form of validity area(s). If the AF interacts with the PCF via the NEF, it may provide geographical area (e.g. a civic address or shapes) and the NEF maps the information to areas of validity based on pre-configuration. The PCF in turn determines area(s) of interest based on validity area(s). When the AF request is for influencing SMF routing decisions, the spatial validity condition indicates that the request applies only to the traffic of UE(s) located in the specified location. When the AF request is for subscription to notifications about UP path management events, the spatial validity condition indicates that the subscription applies only to the traffic of UE(s) located in the specified location. 8) Information on AF subscription to corresponding SMF events. The AF may request to be subscribed to change of UP path associated with traffic identified in the bullet 1) above. The AF request contains: - A type of subscription (subscription for Early and/or Late notifications). The AF subscription can be for Early notifications and/or Late notifications. In the case of a subscription for Early notifications, the SMF sends the notifications before the (new) UP path is configured. In the case of a subscription for Late notifications, the SMF sends the notification after the (new) UP path has been configured. - Notification target address for receiving event notification. - Optionally, an indication of "AF acknowledgment to be expected". The indication implies that the AF will provide a response to the notifications of UP path management events to the 5GC. The SMF may, according to this indication, determine to wait for a response from the AF before the SMF configures in the case of early notification, or activates in the case of late notification, the new UP path as described in clause 5.6.7.2. - Optionally, an immediate reporting flag. The immediate reporting flag is included when AF subscribe for candidate DNAI(s) of UE for common EAS/DNAI selection. With this flag, SMF should immediately response AF with the candidate DNAI(s) using Notification of user plane management event as described in clause 4.3.6.3 in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The AF subscription can also request to receive information associating the GPSI of the UE with the IP address(es) of the UE and/or with actual N6 traffic routing to be used to reach the UE on the PDU Session; in this case the corresponding information is sent by the SMF regardless of whether a DNAI applies to the PDU Session. 9) An AF transaction identifier referring to the AF request. This allows the AF to update or remove the AF request and to identify corresponding UP path management event notifications. The AF transaction identifier is generated by the AF. When the AF interacts with the PCF via the NEF, the NEF maps the AF transaction identifier to an AF transaction internal identifier, which is generated by the NEF and used within the 5GC to identify the information associated to the AF request. The NEF maintains the mapping between the AF transaction identifier and the AF transaction internal identifier. The relation between the two identifiers is implementation specific. When the AF interacts with the PCF directly, the AF transaction identifier provided by the AF is used as AF transaction internal identifier within the 5GC. 10) Indication of UE IP address preservation. This indicates UE IP address related to the traffic identified in bullet 1) should be preserved. If this indication is provided by the AF, the 5GC should preserve the UE IP address by preventing reselection of PSA UPF for the identified traffic once the PSA UPF is selected. 11) Information for EAS IP Replacement in 5GC. This indicates the Source EAS identifier and Target EAS identifier (i.e. IP addresses and port numbers of the source and target EAS) for a service subject to Edge Computing. 12) User Plane Latency Requirement. This includes AF requirements for User Plane latency. (see clause 6.3.6 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]). 13) Information on AF change. The AF relocation information includes: - AF Identifier: the identifier of the target AF instance. NOTE 4: The AF relocation information is applicable for interaction with NEF only and it is not stored in UDR or transferred to PCF, even for the case AF directly interacts with PCF. 14) Indication for EAS relocation. This indicates the application(s) are to be relocated. 15) Indication for Simultaneous Connectivity over source and target PSA at Edge Relocation (see clause 6.3.4 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]). Indicates that source and target PSA should coexist for some time at PSA relocation, and may influence the establishment of a temporary N9 forwarding tunnel between the source UL CL and target UL CL. It may also provide guidance for the time interval after the described traffic ceases when the connectivity over the source PSA may be removed. 16) Traffic Correlation ID. Identification of a set of UEs subjecting to the AF request and accessing the application identified by the Traffic Description. UEs associated with the same Traffic Correlation ID and accessing the application identified by the Traffic Description should connect to a common EAS or EAS(es) corresponding to a common DNAI. The following attributes may be provided with the Traffic Correlation ID: - EAS Correlation indication. Indicates selecting a common EAS for a set of UEs identified by Traffic Correlation ID and accessing the application identified by the Traffic Description. - Common EAS IP address. IP address of the common EAS to be accessed by the UEs in the set of UEs subject to AF request, for the application identified by the Traffic Description. NOTE 5: In the case of common EAS selection, if Traffic Correlation ID is provided, either EAS Correlation indication or Common EAS will be included in AF request. - FQDN(s). FQDN(s) corresponding to the application to be accessed by a set of UEs. When FQDN(s) is included, it is used for influencing EAS discovery procedure as defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. - Indication of traffic correlation as described in 2). An AF may send requests to influence SMF routing decisions, for event subscription or for both. The AF may request to be subscribed to notifications about UP path management events, i.e. a UP path change occurs for the PDU Session. The corresponding notification about a UP path change sent by the SMF to the AF may indicate the DNAI and /or the N6 traffic routing information and/or common EAS that has changed as described in clause 4.3.6.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. It may include the AF transaction internal identifier, the type of notification (i.e. early notification or late notification), the Identity of the source and/or target DNAI, the IP address/prefix of the UE or the MAC address used by the UE, the GPSI and the N6 traffic routing information related to the 5GC UP. The AF may subscribe for notifications of candidate DNAI(s) for UE if AF selection of common EAS/DNAI for a set of UEs is used. NOTE 6: The change from the UP path status where no DNAI applies to a status where a DNAI applies indicates the activation of this AF request; the change from the UP path status where a DNAI applies to a status where no DNAI applies indicates the de-activation of this AF request. In the case of IP PDU Session Type, the IP address/prefix of the UE together with N6 traffic routing information indicates to the AF how to reach over the User Plane the UE identified by its GPSI. N6 traffic routing information indicates any tunnelling that may be used over N6. The nature of this information depends on the deployment. NOTE 7: N6 traffic routing information can e.g. correspond to the identifier of a VPN or to explicit tunnelling information such as a tunnelling protocol identifier together with a Tunnel identifier. NOTE 8: In the case of Unstructured PDU Session type the nature of the N6 traffic routing information related to the 5GC UP is described in clause 5.6.10.3. In the case of Ethernet PDU Session Type, the MAC address of the UE together with N6 traffic routing information indicates to the AF how to reach over the User Plane the UE identified by its GPSI. The UE MAC address (es) is reported by the UPF as described in clause 5.8.2.12. The N6 traffic routing information can be, e.g. a VLAN ID or the identifier of a VPN or a tunnel identifier at the UPF. When notifications about UP path management events are sent to the AF via the NEF, if required, the NEF maps the UE identify information, e.g. SUPI, to the GPSI and the AF transaction internal identifier to the AF transaction identifier before sending the notifications to the AF. The PCF, based on information received from the AF, operator's policy, optionally service experience analytics per UP path received from NWDAF, etc. authorizes the request received from the AF and determines for each DNAI, a traffic steering policy ID (derived from the routing profile ID provided by the AF) and/or the N6 traffic routing information (as provided by the AF) to be sent to the SMF as part of the PCC rules. The traffic steering policy IDs are configured in the SMF or in the UPF. The traffic steering policy IDs are related to the mechanism enabling traffic steering to the DN. The DNAIs are related to the information considered by the SMF for UPF selection and (I-)SMF (re)selection, e.g. for diverting (locally) some traffic matching traffic filters provided by the PCF. The PCF acknowledges a request targeting an individual PDU Session to the AF or to the NEF. For PDU Session that corresponds to the AF request, the PCF provides the SMF with a PCC rule that is generated based on the AF request, Local routing indication from the PDU Session policy control subscription information and taking into account UE location presence in area of interest (i.e. Presence Reporting Area). The PCC rule contains the information to identify the traffic, information about the DNAI(s) towards which the traffic routing should apply and optionally, an indication of traffic correlation and/or an indication of application relocation possibility and/or indication of UE IP address preservation. The PCC rule also contains per DNAI a traffic steering policy ID and/or N6 traffic routing information, if the N6 traffic routing information is explicitly provided in the AF request. If Traffic Correlation ID is included in the AF request, with EAS Correlation Indication or Common EAS, and FQDN(s) parameters, the Traffic Correlation ID and the EAS Correlation Indication or Common EAS, and FQDN(s) will be included in the PCC rule sent to SMF. The SMF can use the Traffic Correlation ID to determine that the UE belongs to a set of UEs identified by Traffic Correlation ID and a common EAS should be selected for the set of UE for the traffic identified by Traffic Descriptor as described in clause 6.2.3.2.5 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. If Traffic Correlation ID is included in the AF request, NEF updates the AF influence data in the UDR with the NEF Notification Endpoint to indicate it as responsible of the set of UEs associated with the Traffic correlation ID and to be notified with 5GC determined information as described in clause 6.2.3.2.7 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. The PCF provides in the PCC rule with information including the NEF Notification Endpoint for the SMF to notify to the NEF with 5GC determined information related to the UE members of the set of UEs identified by traffic correlation ID. If Traffic Correlation ID, and traffic correlation indication and FQDN(s) is included in the AF request, the Traffic Correlation ID and the traffic correlation indication will be included in the PCC rule sent to SMF. The SMF can use the Traffic Correlation ID to determine that the UE belongs to a set of UEs identified by Traffic Correlation ID and the UE needs to connect to EAS(s) corresponding to a common DNAI selected for the set of UE for the traffic identified by Traffic Descriptor, as described in clause 6.2.3.2.6 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. The PCF may also provide in the PCC rule information to subscribe the AF (or the NEF) to SMF events (UP path changes) corresponding to the AF request in which case it provides the information on AF subscription to corresponding SMF events received in the AF request. This is done by providing policies at PDU Session set-up or by initiating a PDU Session Modification procedure. When initiating a PDU Session set-up or PDU Session Modification procedure, the PCF considers the latest known UE location to determine the PCC rules provided to the SMF. The PCF evaluates the temporal validity condition of the AF request and informs the SMF to activate or deactivate the corresponding PCC rules according to the evaluation result. When policies specific to the PDU Session and policies general to multiple PDU Sessions exist, the PCF gives precedence to the PDU Session specific policies over the general policies. The PCF authorizes the AF request of User Plane Latency Requirements. If the PCF determines that the requirements can't be authorized, the PCF rejects the AF request. The spatial validity condition is resolved at the PCF. In order to do that, the PCF subscribes to the SMF to receive notifications about change of UE location in an area of interest (i.e. Presence Reporting Area). The subscribed area of interest may be the same as spatial validity condition, or may be a subset of the spatial validity condition (e.g. a list of TAs) based on the latest known UE location. When the SMF detects that UE entered the area of interest subscribed by the PCF, the SMF notifies the PCF and the PCF provides to the SMF the PCC rules described above by triggering a PDU Session Modification. When the SMF becomes aware that the UE left the area subscribed by the PCF, the SMF notifies the PCF and the PCF provides updated PCC rules by triggering a PDU Session Modification. SMF notifications to the PCF about UE location in or out of the subscribed area of interest are triggered by UE location change notifications received from the AMF or by UE location information received during a Service Request or Handover procedure. When the PCC rules are activated, the SMF may, based on local policies, take the information in the PCC rules and, optionally, the Service Experience analytics and/or DN Performance analytics per UP path (including UPF and/or DNAI and/or AS instance) as defined in clause 6.4.3 and clause 6.14.3, respectively, of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86] into account to: - (re)select UP paths (including DNAI(s)) for PDU Sessions. The SMF is responsible for handling the mapping between the UE location (TAI / Cell-Id) and DNAI(s) associated with UPF and applications and the selection of the UPF(s) that serve a PDU Session. This is described in clause 6.3.3. If the PDU Session is of IP type and if Indication of UE IP address preservation is included in the PCC rules, the SMF should preserve the UE IP address, by not reselecting the related PSA UPF once the PSA UPF is selected, for the traffic identified in the PCC rule. If the user plane latency requirement is included in the PCC rules, the SMF chooses the PSA UPF that satisfies the user plane latency requirement. If the PCC rules are related to a 5G VN group served by the SMF and if the PCC rule includes an indication of traffic correlation, the SMF should select a common DNAI for the PDU Sessions of the 5G VN group, see clause 5.29. - configure traffic steering at UPF, including activating mechanisms for traffic multi-homing or enforcement of an UL Classifier (UL CL). Such mechanisms are defined in clause 5.6.4. This may include that the SMF is providing the UPF with packet handling instructions (i.e. PDRs and FARs) for steering traffic to the local access to the DN. The packet handling instructions are generated by the SMF using the traffic steering policy ID and/or the N6 traffic routing information in the PCC rules corresponding to the applied DNAI. In the case of UP path reselection, the SMF may configure the source UPF to forward traffic to the UL CL/BP so that the traffic is steered towards the target UPF. - if Information on AF subscription to corresponding SMF events has been provided in the PCC rule, inform the AF of the (re)selection of the UP path (UP path change). If the information includes an indication of "AF acknowledgment to be expected", the SMF may decide to wait for a response from the AF before it activates the new UP path, as described in clause 5.6.7.2. When an I-SMF is inserted for a PDU Session, the I-SMF insertion, relocation or removal to a PDU session shall be transparent (i.e. not aware) to the PCF and to the AF. The processing of the AF influence on traffic routing is described in clause 5.34 and detailed procedure is described in clause 4.23.6 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.6.7 |
2,179 | 8.4 Cause | Cause IE is coded as depicted in Figure 8.4-1. Figure 8.4-1: Cause Cause is a variable length IE, which may have either of the following two lengths values: - If n = 2, a = 0 and the Cause IE shall be 6 octets long. Therefore, octets "a(n+1) to a(n+4)" will not be present. - If n = 6, a = 1 and the Cause IE will be 10 octets long. For PMIP based S5/S8, the SGW/MAG shall do the mapping between GTPv2 Cause IE and respective PMIPv6 IE as specified in 3GPP TS 29.275[ Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3 ] [26]. The following bits within Octet 6 indicate: - Bits 8 to 4: Spare, for future use and set to zero - Bit 1 β CS (Cause Source): If this bit is set to 1, it indicates that the corresponding error cause is originated by the remote node (i.e., the MME/SGSN to a PGW, or the PGW to an MME/SGSN). This bit is set to 0 to denote that the corresponding error cause is originated by the node sending the message. The CS should be set to 1 by the SGW when the SGW relay a response message with cause value from the MME/SGSN to the PGW or from the PGW to the MME/SGSN. For PMIP based S5/S8, the SGW shall set the CS bit to 1 when the SGW/MAG relay a response message with the cause value from the PGW/LMA to the MME/SGSN. - Bit 2 β BCE (Bearer Context IE Error): If this bit is set to 1, it indicates that the corresponding rejection cause is due to the error in the Bearer Context IE. This bit shall be discarded if the cause value is one of Acceptance cause value as given in table 8.4-1. - Bit 3 β PCE (PDN Connection IE Error): If this bit is set to 1, it indicates that the corresponding rejection cause is due to the error in the PDN Connection IE. This bit shall be discarded if the cause value is one of Acceptance cause value as given in table 8.4-1. The Cause value shall be included in a response message. In a response message, the Cause value indicates the acceptance or the rejection of the corresponding request message. The Cause value indicates the explicit reason for the rejection. If the rejection is due to a mandatory IE or a verifiable conditional IE is faulty or missing, the offending IE shall be included within an additional field "a(n+1) to a(n+4)". Only Type and Instance fields of the offending IE that caused the rejection have a meaning. The length in the Octet 8-9 and spare bits in the Octet 10 shall be set to "0". In this case, the value of "n" shall be "6". Otherwise, the value of "n" is equal to "2". The Cause may also be included in the request message. In a request message, the Cause value indicates the reason for the request. "Request accepted" is returned when the GTPv2 entity has accepted a control plane request. "Context Not Found" is used in the response message by a GTP entity when it receives a message for which it does not have context, e.g. TEID-C or EBI is not known. When "Context Not Found" is received at Bearer Context IE level, it means the bearer context is unknown in the peer. When "Context Not Found" is received at message level together with a known TEID-C in the GTPv2-C header in the response message, this indicates some bearer contexts are not known in the peer; the sender of the request message should further determine, based on the bearer context(s) included in the request message, that: - if the default bearer is unknown, this means the PDN connection is not known in the peer; - if one or more dedicated bearers are unknown, this means only those dedicated bearer contexts are not known in the peer. "Context Not Found" may be used by the PGW in the Create Session Response message during the non-3GPP to 3GPP access handover procedures, if the request corresponds to the handover of a PDN connection which does not exist in the PGW. "Context Not Found" may be used by the PGW in the Create Session Response message during the 3GPP to non-3GPP access handover procedures, if the request corresponds to the handover of a PDN connection which does not exist in the PGW. "Service not supported" is used by the GTP entity when it receives a message, which corresponds to a feature or a service which is not supported by the node. "Service denied" is used when the requested service cannot be granted. "System failure" is used by the GTP entity to indicate a generic error condition. "No resources available" is used by the GTP entity to indicate the temporary unavailability of the resource(s) to process the received request. "Semantic error in the TFT operation", "Syntactic error in the TFT operation", "Semantic errors in packet filter(s)", "Syntactic errors in packet filters(s)", "UE context without TFT already activated", "Semantic error in the TAD operation" and "Syntactic error in the TAD operation" are indications of error cases involving TFT(s)/TAD(s) as specified in clause 7.7.11 in this specification. "Missing or unknown APN" is used by the PGW when it does not support the Access Point Name, received in Create Session Request message. "Relocation failure" is used by the target MME/S4-SGSN to indicate the source MME/S4-SGSN that the relocation has failed. "Relocation failure due to NAS message redirection" is used by the new MME/S4-SGSN to indicate to the old MME/S4-SGSN that the TAU/RAU procedure is not successful due to NAS message redirection as described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3], or used by the initial AMF to indicate to the old MME that the context transfer procedure is not successful due to NAS message redirection as described in clause 4.11.1.3.4 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [83]. "Denied in RAT" is used by the GTP entity to indicate that the requested service is not accepted in the RAT. "Preferred PDN type not supported" is used by the PGW to indicate that the PDN type received in the Create Session Request message is not supported by the PGW for the PDN corresponding to the received Access Point Name. "Protocol type not supported" is used by the SGW to indicate that the S5/S8 protocol type requested by the MME/S4-SGSN is not supported by it. "UE not responding" is used by the MME/S4-SGSN to indicate that the UE is not responding to the request initiated by the network, e.g. Paging. "UE refuses" is used by the GTP entity to indicate that the UE, without specifying further detail, rejected the request from the network. "Unable to page UE" is used by the MME/S4-SGSN to indicate its inability to page the UE, temporarily. "User authentication failed" is used by the GTP entity to indicate that the request is rejected due to a failure in the authentication/security procedure, or because the required user authentication cannot be performed (when the UE does not support secondary DN authentication and authorization over EPC but such a procedure is mandatory due to local policies in a combined PGW-C/SMF), or is used by a combined PGW-C/SMF for an UUAA-SM during PDN connection establishment procedure as described in clause 5.2.3.3 of 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [90] or in authorization for C2 procedure as described in clause 5.2.5.3 of 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [90]. "APN access denied β no subscription" is used to indicate that the PGW has denied the user access to an APN because a subscription is required, but the subscriber does not have the necessary subscription. "Remote peer not responding" is used by the SGW for the messages spanning through two interfaces. This cause value is returned by the SGW to the MME/S4-SGSN or PGW in a response message where no response message is received from the PGW or MME/S4-SGSN. "Collision with network initiated request" is used by the PGW to indicate that the UE-initiated bearer resource allocation/modification request is rejected since the PGW has requested a bearer resource allocation/modification for the same service using a network-initiated procedure. "Unable to page UE due to Suspension" is used by the MME/S4-SGSN to indicate that the UE has not been paged because the bearers of the UE are in a suspended state. "APN Restriction type Incompatible with currently active PDN connection" is used by the PGW to indicate that the newly requested PDN connection has APN restriction value that is not compatible with the currently active PDN connection(s)'s APN restriction value(s). "Invalid peer" is used by the SGW to indicate that currently the UE is being managed by the different node (e.g. MME/S4-SGSN) than the node (e.g. S4-SGSN/MME) which has sent the Delete Session Request message. "Invalid Reply from remote peer" is used by the SGW for the messages spanning through two interfaces. This cause value is returned by the SGW to the MME/SGSN or PGW in a reply message where the corresponding reply message on S5/S8 or S11/S4 from the PGW or MME/SGSN is not decoded as valid. "Temporarily rejected due to handover/TAU/RAU procedure in progress" is used by the MME/S4-SGSN for the bearer related procedure initiated by the PGW. When the handover/TAU/RAU with/without SGW change and/or MME/S4-SGSN change is in progress, the MME/S4-SGSN may receive Create / Update / Delete Bearer request message for the bearer creation, modification or deletion initiated by the PGW. If the handover/TAU/RAU procedure results in the SGW and/or MME/S4-SGSN change, then the bearer related procedure cannot be handled temporarily by the MME/S4-SGSN till the handover/TAU/RAU procedure is completed. In that case the MME/S4-SGSN shall reject the bearer related procedure with this rejection cause. This cause is also used to indicate that the Downlink Data Notification message is rejected temporarily due to the mobility procedures with MME or SGSN change in progress as specified in clause 5.3.4.3 in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. The usage of "Fallback to GTPv1" is specified in clause 7.10 "Fallback to GTPv1 mechanism". In the PGW initiated bearer deactivation procedure for the default bearer, the PGW may include the Cause IE in the Delete Bearer Request with values "RAT changed from 3GPP to Non-3GPP", "Reactivation requested" or "Reactivation disallowed to APN". "APN Congestion" is used by the PGW and it indicates that the PGW has detected congestion for the requested APN and performs overload control for that APN which does not allow the PDN connection to be established. "GTP-C Entity Congestion" is used to indicate that the GTP-C entity has detected node level congestion and performs overload control at the node level, which does not allow the request to be processed. "UE already re-attached" is used by MME/S4-SGSN for the network triggered service restoration procedure as specified in 3GPP TS 23.007[ Restoration procedures ] [17]. The MME/S4-SGSN may send the Downlink Data Notification Acknowledge or Downlink Data Notification Failure Indication with this cause as part of the network triggered service restoration procedure. "PDP connection inactivity timer expires" is used by the PGW in Delete Bearer Request(s) to indicate that all the bearer(s) for the emergency PDN connection are deleted upon the inactivity timer expiry as specified in 3GPP TS 23.203[ Policy and charging control architecture ] [48]. "Network failure" is used by the SGSN or MME in the Delete Session Request to indicate that the message is sent due to a network problem. "QoS parameter mismatch" is used by the SGSN or MME in the Delete Session Request to indicate that the PDN connection can not be established due to a QoS parameter mismatch. "MME/SGSN refuses due to VPLMN policy" is used by the MME/SGSN in the VPLMN to indicate to the PGW in the Create Bearer Response or Update Bearer Response that it does not allow the establishment or modification of the bearer due to VPLMN operator's policy. The listed cause values for rejection response message descriptions in clause 7 are not meant to be exhaustive lists. Therefore a GTPv2 node shall use the most appropriate matching rejection response cause value that is listed in Table 8.4-1. If a Bearer Resource Command message is related to an established PDN connection for LIPA or for SIPTO at the local network, the LGW shall reject the Bearer Resource Command with the cause value of "Bearer handling not supported". "Multiple PDN connections for a given APN not allowed" is used by SGW for reply message to the MME/S4-SGSN when PMIP-based S5/S8 is used. If either SGW or PGW does not support the multiple PDN connections to the same APN function, the SGW shall reject the PDN connectivity request procedure with this rejection cause when receiving Create Session Request for additional PDN connectivity to the given APN from the same UE. As specified in clause 5.3.1.1 in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and clause 9.2.1 in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35], the cause value "New PDN type due to network preference" indicates that the UE has requested PDN type IPv4v6 and only IPv4 or IPv6 address is allowed for the PDN based on PGW operator policy. As specified in clause 5.3.1.1 in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and clause 9.2.1 in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35], the cause value "New PDN type due to single address bearer only" indicates that the MS has requested PDN type IPv4v6 and both IPv4 and IPv6 addressing is possible in the PDN but the Dual Address Bearer Flag of the Indication IE is set to 0 or the Indication IE is absent, or only single IP version addressing is possible in the PDN. "PGW not responding" is used by the SGW in PGW Restart Notification to indicate that the peer PGW has failed and not restarted as specified in clause 7.9.5. "UE context without TFT already activated" is used by the PGW in the Bearer Resource Failure Indication message to indicate that the PGW has received the Bearer Resource Command message without TAD IE in the secondary PDP Context Activation procedure. "Target access restricted for the subscriber" is used by the MME/SGSN in the Context Response message to indicate that the target access is prohibited for the subscriber, based on the subscription profile. "P-TMSI Signature mismatch" is used by the SGSN or MME in the Identification Response and Context Response message if the P-TMSI Signature stored in the old SGSN or MME does not match the value sent by the UE via the new SGSN or MME. "Late Overlapping Request" is used by the PGW in the Create Session Response to indicate that the incoming request collides with an existing session which has a more recent time stamp than the time stamp of the new request, as specified in clause 13.2. "Timed Out Request" is used by the SGW and PGW in the Create Session Response to indicate that the incoming request is known to have already timed out at the originating entity, as specified in clause 13.3. "UE is temporarily not reachable due to power saving" is used by the MME/SGSN in the Create/Update Bearer Response message to reject the corresponding network initiated procedures for a Delay Tolerant PDN connection and also request the PGW to hold the network initiated procedure until it receives the subsequent Modify Bearer Request message with the UASI flag indicating that the UE is available for end to end signalling. "UE not authorised by OCS or external AAA Server" is used by the PGW in the Create Session Response to reject the corresponding UE initiated procedures when the OCS or an external AAA Server on SGi did not authorise it and the support of the Cause Code was indicated by the SGSN/MME within the Create Session Request. If a Create Session Request message requests the addition of an access to a PDN connection, and NBIFOM is not supported by the MME/SGSN, SGW or TWAN, the PGW should reject the request with the cause value of "Multiple accesses to a PDN connection not allowed". This cause is also used by the PGW in the Delete Bearer Request message to initiate the removal of 3GPP access from the PDN connection due to detection of the MME/SGSN or SGW not supporting NBIFOM at the inter-PLMN mobility procedure. "Request rejected due to UE capability" is used by the MME in the Create Bearer Response to reject the request to add an EPS bearer that would exceed the UE capability (e.g. a NB-IoT UE can only support up to 2 EPS bearers). This cause value does not prevent the PGW from sending Create Bearer Request later. "S1-U Path Failure" is used by the SGW in the Create Session Response, or in the Modify Bearer Response message, or in the Modify Access Bearer Response message to report an S1-U path failure. The SGW may include this cause code in a Downlink Data Notification message and/or a Delete Bearer Request message to report the S1-U path failure. See clause 20.3 in 3GPP TS 23.007[ Restoration procedures ] [17]. "EPS to 5GS Mobility" is used by the PGW, and it indicates that PGW initiated bearer deactivation procedure is due to EPS to 5GS mobility procedures. "5GC not allowed" is used by the source MME in the Context Response message sent to the target AMF during an EPS to 5GS idle mode mobility procedure, to indicate that the UE is not allowed for 5GC, based on the subscription profile. "PGW mismatch with network slice subscribed by the UE" is used by the PGW in the Create Session Response message during an EPS to 5GS mobility procedure, to indicate that the PGW is not serving the network slice subscribed by the UE for the APN/DNN. "Rejection due to paging restriction" is used by the MME to indicate that the UE has not been paged because the MME holds stored Paging Restriction information for the UE that restricts the Downlink Data from causing paging as specified in clause 4.3.33.6 in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] or the UE has rejected the page as specified in clause 4.3.33.4 in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. Table 8.4-1: Cause values The mapping at the MME/S4-SGSN between GTP cause values received over the S11/S4 interface and the NAS cause values sent to the UE is specified in Annex C. | 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.4 |
2,180 | 4.23.4 5GS session management via a satellite NG-RAN cell | For 5GS session management via a satellite NG-RAN cell the UE shall apply the value of the applicable NAS timer indicated in table 10.2.1 for access via a satellite NG-RAN cell. NOTE 1: The applied NAS timer values are based on the current satellite NG-RAN access RAT type determined based on information from lower layers. The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure, and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. If the use of extended NAS timer for access via a satellite NG-RAN cell is indicated by the AMF (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]), the SMF shall calculate the value of the applicable NAS timer indicated in table 10.3.2 for access via a satellite NG-RAN cell. The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. | 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.4 |
2,181 | 5.2.16.3.3 Nnssf_NSSAIAvailability_Notify service operation | Service operation name: Nnssf_NSSAIAvailability_Notify Description: This service operation enables the NSSF to update a NF Service Consumer (e.g. AMF) with any S-NSSAIs restricted per validity time, or per TA and if needed subsequently lift any restriction per TA. This service operation also enables the NSSF to notify to the NF Service Consumer (e.g. AMF or NSSF in the VPLMN) that an S-NSSAI has to be replaced by an Alternative S-NSSAI or a Network Slice instance should be replaced. Inputs, Required: Subscription Correlation ID. Inputs, Conditional Required: If this service operation is invoked by subscription for changes in the status of the NSSAI availability information, then the following inputs are required: - a list of TAIs and the S-NSSAIs for which the status is changed (restricted/unrestricted) per each TAI. If this service operation is invoked by subscription for event notification for Network Slice Replacement, then the following inputs are required: - For replacement of an S-NSSAI of the serving PLMN: an Alternative S-NSSAI and the corresponding mapping to the S-NSSAI to be replaced. - For replacement of an HPLMN S-NSSAI: an Alternative S-NSSAI and the corresponding mapping to the S-NSSAIs of the HPLMN, PLMN ID. - For termination of the Network Slice replacement: 1) indication to stop the Network Slice replacement for new UEs; or 2) indication to terminate the Network Slice replacement and move back the UEs and PDU Sessions from the Alternative S-NSSAI to the S-NSSAI. If this service operation is invoked by subscription for event notification for Network Slice Instance Replacement, then the following inputs are required: - The S-NSSAI(s) and NSI ID(s) for which the status is changed (e.g. congested or no longer available). If this service operation is invoked by subscription for event notification for update of slice validity time, then the following inputs are required: - The S-NSSAI(s) and associated validity time for each S-NSSAI. Inputs, Optional: - NSI IDs in the S-NSSAI for which the status is changed (restricted/unrestricted) per each TAI. If this service operation is invoked by subscription for event notification for Network Slice Replacement or Network Slice Instance Replacement, then the following inputs are optional: - For replacement due to congestion: congestion mitigation information. Outputs, Required: None. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.16.3.3 |
2,182 | β LocationMeasurementIndication | The LocationMeasurementIndication message is used to indicate that the UE is going to either start or stop location related measurement which requires measurement gaps. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network LocationMeasurementIndication message -- ASN1START -- TAG-LOCATIONMEASUREMENTINDICATION-START LocationMeasurementIndication ::= SEQUENCE { criticalExtensions CHOICE { locationMeasurementIndication LocationMeasurementIndication-IEs, criticalExtensionsFuture SEQUENCE {} } } LocationMeasurementIndication-IEs ::= SEQUENCE { measurementIndication SetupRelease {LocationMeasurementInfo}, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-LOCATIONMEASUREMENTINDICATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,183 | 5.2.5.6.2 Npcf_UEPolicyControl_Create service operation | Service operation name: Npcf_UEPolicyControl_Create Description: NF Service Consumer can request the creation of a UE Policy Association by providing relevant parameters about the UE context to the PCF. Inputs, Required: Notification endpoint, SUPI. Inputs, Optional: H-PCF ID (if the NF service producer is V-PCF and AMF is NF service consumer), information provided by the AMF as define in clause 6.2.1.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], such as Access Type, Permanent Equipment Identifier, GPSI, User Location Information, UE Time Zone, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), RAT type, LBO Information (see clause 6.1.2.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), UE policy information including the list of PSIs, OS id, UE capability of reporting URSP rule enforcement to network (see clause 6.6.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) and Internal Group (see TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Satellite Backhaul Category (see clause 5.43 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), "5GS to EPS Mobility" indication, request to update the UE policies, request to be notified when updated UE policies have been provided to the UE. Outputs, Required: Success or Failure, UE Policy Association ID. Outputs, Optional: Policy Control Request Trigger of UE Policy Association. In the case of H-PCF is producer, UE policy information (see clause 5.2.5.6.1). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.6.2 |
2,184 | 8.2.1.4.3 Minimum Requirement Multi-Layer Spatial Multiplexing 4 Tx Antenna Port | For single carrier, the requirements are specified in Table 8.2.1.4.3-2, with the addition of the parameters in Table 8.2.1.4.3-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 2 DL CCs, the requirements are specified in Table 8.2.1.4.3-4, with the addition of the parameters in Table 8.2.1.4.3-3 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. For CA with 3 DL CCs, the requirements are specified in Table 8.2.1.4.3-6, based on single carrier requirement specified in Table 8.2.1.4.3-5, with the addition of the parameters in Table 8.2.1.4.3-3 and the downlink physical channel setup according to Annex C.3.2. For CA with4 DL CCs, the requirements are specified in Table 8.2.1.4.3-7, based on single carrier requirement specified in Table 8.2.1.4.3-5, with the addition of the parameters in Table 8.2.1.4.3-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, the requirements are specified in Table 8.2.1.4.3-8, based on single carrier requirement specified in Table 8.2.1.4.3-5, with the addition of the parameters in Table 8.2.1.4.3-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 6 DL CCs, the requirements are specified in Table 8.2.1.4.3-9, based on single carrier requirement specified in Table 8.2.1.4.3-5, with the addition of the parameters in Table 8.2.1.4.3-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 7 DL CCs, the requirements are specified in Table 8.2.1.4.3-10, based on single carrier requirement specified in Table 8.2.1.4.3-5, with the addition of the parameters in Table 8.2.1.4.3-3 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.1.4.3-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) Table 8.2.1.4.3-2: Minimum performance Multi-Layer Spatial Multiplexing (FRC) Table 8.2.1.4.3-3: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.2.1.4.3-4: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for CA with 2DL CCs Table 8.2.1.4.3-5: Single carrier performance for multiple CA configurations Table 8.2.1.4.3-6: Minimum performance (FRC) based on single carrier performance for CA with 3 DL CCs Table 8.2.1.4.3-7: Minimum performance (FRC) based on single carrier performance for CA with 4 DL CCs Table 8.2.1.4.3-8: Minimum performance (FRC) based on single carrier performance for CA with 5 DL CCs Table 8.2.1.4.3-9: Minimum performance (FRC) based on single carrier performance for CA with 6 DL CCs Table 8.2.1.4.3-10: Minimum performance (FRC) based on single carrier performance for CA with 7 DL CCs | 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.4.3 |
2,185 | 5.3.10.3 Detection of radio link failure | The UE shall: 1> if any DAPS bearer is configured and T304 is running: 2> upon T310 expiry in source SpCell; or 2> upon random access problem indication from source MCG MAC; or 2> upon indication from source MCG RLC that the maximum number of retransmissions has been reached; or 2> upon consistent uplink LBT failure indication from source MCG MAC: 3> consider radio link failure to be detected for the source MCG i.e. source RLF; 3> suspend the transmission and reception of all DRBs and multicast MRBs in the source MCG; 3> reset MAC for the source MCG; 3> release the source connection. 1> else: 2> during a DAPS handover: the following only applies for the target PCell; 2> upon T310 expiry in PCell; or 2> upon T312 expiry in PCell; or 2> upon random access problem indication from MCG MAC while neither T300, T301, T304, T311 nor T319 are running and SDT procedure is not ongoing; or 2> upon indication from MCG RLC that the maximum number of retransmissions has been reached while SDT procedure is not ongoing; or 2> if connected as an IAB-node, upon BH RLF indication received on BAP entity from the MCG; or 2> upon consistent uplink LBT failure indication from MCG MAC while T304 is not running: 3> if the indication is from MCG RLC and CA duplication is configured and activated for MCG, and for the corresponding logical channel allowedServingCells only includes SCell(s): 4> initiate the failure information procedure as specified in 5.7.5 to report RLC failure. 3> else: 4> consider radio link failure to be detected for the MCG, i.e. MCG RLF; 4> discard any segments of segmented RRC messages stored according to 5.7.6.3; NOTE: Void. 4> if AS security has not been activated: 5> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'other';- 4> else if AS security has been activated but SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, have not been setup: 5> store the radio link failure information in the VarRLF-Report as described in clause 5.3.10.5; 5> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'; 4> else: 5> store the radio link failure information in the VarRLF-Report as described in clause 5.3.10.5; 5> if T316 is configured; and 5> if SCG transmission is not suspended; and 5> if the SCG is not deactivated; and 5> if neither PSCell change nor PSCell addition is ongoing (i.e. timer T304 for the NR PSCell is not running in case of NR-DC or timer T307 of the E-UTRA PSCell is not running as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.10.10, in NE-DC): 6> initiate the MCG failure information procedure as specified in 5.7.3b to report MCG radio link failure. 5> else: 6> initiate the connection re-establishment procedure as specified in 5.3.7. A L2/L3 U2N Relay UE shall: 1> upon detecting radio link failure: 2> either indicate to upper layers (to trigger PC5 unicast link release) or send NotificationMessageSidelink to the connected L2/L3 U2N Remote UE(s) in accordance with 5.8.9.10. The UE shall: 1> upon T310 expiry in PSCell; or 1> upon T312 expiry in PSCell; or 1> upon random access problem indication from SCG MAC; or 1> upon indication from SCG RLC that the maximum number of retransmissions has been reached; or 1> if connected as an IAB-node, upon BH RLF indication received on BAP entity from the SCG; or 1> upon consistent uplink LBT failure indication from SCG MAC: 2> if the indication is from SCG RLC and CA duplication is configured and activated for SCG, and for the corresponding logical channel allowedServingCells only includes SCell(s): 3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure. 2> else: 3> consider radio link failure to be detected for the SCG, i.e. SCG RLF; 3> if the SCG is deactivated: 4> stop radio link monitoring on the SCG; 4> indicate to lower layers to stop beam failure detection on the PSCell; 3> if MCG transmission is not suspended: 4> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure. 3> else: 4> if the UE is in NR-DC: 5> initiate the connection re-establishment procedure as specified in 5.3.7; 4> else (the UE is in (NG)EN-DC): 5> initiate the connection re-establishment procedure as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.7; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.10.3 |
2,186 | β ULInformationTransferIRAT | The ULInformationTransferIRAT message is used for the uplink transfer of information terminated at NR MCG but specified by another RAT. In this version of the specification, the message is used for V2X sidelink communication messages specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to network ULInformationTransferIRAT message -- ASN1START -- TAG-ULINFORMATIONTRANSFERIRAT-START ULInformationTransferIRAT-r16 ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { ulInformationTransferIRAT-r16 ULInformationTransferIRAT-r16-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } ULInformationTransferIRAT-r16-IEs ::= SEQUENCE { ul-DCCH-MessageEUTRA-r16 OCTET STRING OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-ULINFORMATIONTRANSFERIRAT-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,187 | 5.3.7 RRC connection re-establishment 5.3.7.1 General | Figure 5.3.7.1-1: RRC connection re-establishment, successful Figure 5.3.7.1-2: RRC re-establishment, fallback to RRC establishment, successful The purpose of this procedure is to re-establish the RRC connection. A UE in RRC_CONNECTED, for which AS security has been activated with SRB2 and at least one DRB/multicast MRB setup or, for IAB and NCR, SRB2, may initiate the procedure in order to continue the RRC connection. The connection re-establishment succeeds if the network is able to find and verify a valid UE context or, if the UE context cannot be retrieved, and the network responds with an RRCSetup according to clause 5.3.3.4. The network applies the procedure e.g as follows: - When AS security has been activated and the network retrieves or verifies the UE context: - to re-activate AS security without changing algorithms; - to re-establish and resume the SRB1; - When UE is re-establishing an RRC connection, and the network is not able to retrieve or verify the UE context: - to discard the stored AS Context and release all RBs and BH RLC channels and Uu Relay RLC channels; - to fallback to establish a new RRC connection. If AS security has not been activated, the UE shall not initiate the procedure but instead moves to RRC_IDLE directly, with release cause 'other'. If AS security has been activated, but SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, are not setup, the UE does not initiate the procedure but instead moves to RRC_IDLE directly, with release cause 'RRC connection failure'. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.7 |
2,188 | 4.4 NAS security 4.4.1 General | This clause describes the principles for the handling of 5G NAS security contexts in the UE and in the AMF, the procedures used for the security protection of NAS messages between the UE and the AMF, and the procedures used for the protection of NAS IEs between the UE and the UDM. Security protection involves integrity protection and ciphering of the 5GMM messages. 5GSM messages are security protected indirectly by being piggybacked by the security protected 5GMM messages (i.e. UL NAS TRANSPORT message and the DL NAS TRANSPORT message). The signalling procedures for the control of NAS security are part of the 5GMM protocol and are described in detail in clause 5. NOTE: The use of ciphering in a network is an operator option. In this subclause, for the ease of description, it is assumed that ciphering is used, unless explicitly indicated otherwise. Operation of a network without ciphering is achieved by configuring the AMF so that it always selects the "null ciphering algorithm", 5G-EA0. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4 |
2,189 | 9.5.2.2 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 the MS or the network or both 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 as well as the network support for Local IP address in TFTs for all active PDP contexts sharing the same PDP Address and APN, if the PDN type is different from Non-IP, and 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.2.2 |
2,190 | β UECapabilityInformation | The IE UECapabilityInformation message is used to transfer UE radio access capabilities requested by the network. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network UECapabilityInformation message -- ASN1START -- TAG-UECAPABILITYINFORMATION-START UECapabilityInformation ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { ueCapabilityInformation UECapabilityInformation-IEs, criticalExtensionsFuture SEQUENCE {} } } UECapabilityInformation-IEs ::= SEQUENCE { ue-CapabilityRAT-ContainerList UE-CapabilityRAT-ContainerList OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-UECAPABILITYINFORMATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,191 | β DLDedicatedMessageSegment | The DLDedicatedMessageSegment message is used to transfer one segment of the RRCResume or RRCReconfiguration messages. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE DLDedicatedMessageSegment message -- ASN1START -- TAG-DLDEDICATEDMESSAGESEGMENT-START DLDedicatedMessageSegment-r16 ::= SEQUENCE { criticalExtensions CHOICE { dlDedicatedMessageSegment-r16 DLDedicatedMessageSegment-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } DLDedicatedMessageSegment-r16-IEs ::= SEQUENCE { segmentNumber-r16 INTEGER(0..4), rrc-MessageSegmentContainer-r16 OCTET STRING, rrc-MessageSegmentType-r16 ENUMERATED {notLastSegment, lastSegment}, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-DLDEDICATEDMESSAGESEGMENT-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,192 | Update Bearer Response | An Update Bearer Response shall be sent from a MME/SGSN to a SGW and forwarded to the PGW, and from TWAN/ePDG to the PGW as a response to an Update Bearer Request message. Table -1 specifies the presence requirements and the conditions of the IEs in the message. Cause IE indicates if an EPS bearer has been modified in the MME/SGSN/TWAN/ePDG or not. The EPS Bearer has not been modified in the MME/SGSN/TWAN/ePDG if the Cause IE value differs from "Request accepted" or "Request accepted partially". Possible Cause values are specified in Table 8.4-1. Message specific cause values are: "Request accepted". "Request accepted partially" "Context not found" "Semantic error in the TFT operation". "Syntactic error in the TFT operation". "Semantic errors in packet filter(s)". "Syntactic errors in packet filter(s)". - "Denied in RAT". - "UE refuses". "Unable to page UE". "UE not responding". "Unable to page UE due to Suspension". "Temporarily rejected due to handover/TAU/RAU procedure in progress". "MME/SGSN refuses due to VPLMN Policy". "UE is temporarily not reachable due to power saving" Table -1: Information Elements in an Update Bearer Response Table -2: Bearer Context within Update Bearer Response Table 7.2.16-3: Overload Control Information within Update Bearer Response | 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 | Update |
2,193 | β VarMeasIdleConfig | The UE variable VarMeasIdleConfig includes the configuration of the measurements to be performed by the UE while in RRC_IDLE or RRC_INACTIVE for NR inter-frequency and inter-RAT (i.e. EUTRA) measurements. VarMeasIdleConfig UE variable -- ASN1START -- TAG-VARMEASIDLECONFIG-START VarMeasIdleConfig-r16 ::= SEQUENCE { measIdleCarrierListNR-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 OPTIONAL, measIdleCarrierListEUTRA-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 OPTIONAL, measIdleDuration-r16 ENUMERATED {sec10, sec30, sec60, sec120, sec180, sec240, sec300, spare}, validityAreaList-r16 ValidityAreaList-r16 OPTIONAL } -- TAG-VARMEASIDLECONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,194 | 4.3.17.3 Optimising periodic TAU Signalling | To reduce network load from periodic TAU signalling and to increase the time until the UE detects a potential need for changing the RAT or PLMN (e.g. due to network problems) the longer values of the periodic TAU timer and Mobile Reachable timer shall be supported. A long periodic RAU/TAU timer value may be locally configured at MME or may be stored as part of the subscription data in HSS. During Attach and TAU procedures the MME allocates the periodic RAU/TAU timer value as periodic TAU timer to the UE based on VPLMN operator policy, low access priority indication from the UE, periodic RAU/TAU timer value requested by UE, subscription information received from the HSS and Start of Unavailability Period and/or Unavailability Period Duration if using a RAN that provides discontinuous coverage (see clause 4.13.8.2). If MME receives a subscribed periodic RAU/TAU timer value from the HSS it allocates the subscribed value to the UE as periodic TAU timer. A visited PLMN MME may use subscribed periodic RAU/TAU timer value, if available, as an indication to decide for allocating a locally configured periodic RAU/TAU timer value to the UE. If no subscribed periodic RAU/TAU timer value is received from the HSS, the MME should: - if the periodic RAU/TAU timer value requested by UE is within the boundaries of the VPLMN operator policy, allocate the value requested by the UE; - if the periodic RAU/TAU timer value requested by UE is higher than allowed per the VPLMN operator policy, allocate the highest allowed value per the VPLMN operator policy; - if the periodic RAU/TAU timer value requested by UE is lower than allowed per the VPLMN operator policy, allocate the lowest allowed value per the VPLMN operator policy. | 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.17.3 |
2,195 | 4.3.17 Support for Machine Type Communications (MTC) 4.3.17.1 General | This clause provides an overview about functionality for Machine Type Communications according to service requirements described in TS 22.368[ Service requirements for Machine-Type Communications (MTC); Stage 1 ] [66]. The specific functionality is described in the affected procedures and features of this and other specifications. For discrepancies between this overview clause and the detailed procedure and function descriptions, the latter take precedence. MTC functionality is provided by the visited and home networks when the networks are configured to support machine type communication. It applies to both the non-roaming case and the roaming case and some functionality may be dependent upon the existence of appropriate roaming agreements between the operators. Some of the MTC functions are controlled by subscriber data. Other MTC functions are based on indicators sent by the UE to the network. MTC functionality is performed by UEs that are configured to support different options as described in clause 4.3.17.4. Though motivated by scenarios and use cases defined in TS 22.368[ Service requirements for Machine-Type Communications (MTC); Stage 1 ] [66], the functions added to support MTC have general applicability and are in no way constrained to any specific scenario or use case except where explicitly stated. Unless otherwise stated in this specification, MTC functionality also applies over satellite access. | 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.17 |
2,196 | 6.6.2.2.4 Minimum requirement (network signalled value "NS_33" or βNS_34β) | The additional spectrum mask in Table 6.6.2.2.4-1 applies for E-UTRA V2X UE within 5 855 MHz to 5 950 MHz according to ETSI EN 302 571. Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. When "NS_33" or βNS_34β is indicated in the cell, the power of any V2X UE emission shall not exceed the levels specified in Table 6.6.2.2.4-1. Table 6.6.2.2.4-1: Additional requirements for 10MHz channel bandwidth NOTE 1: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. NOTE 2: Additional SEM for V2X overrides any other requirements in frequency range 5855-5950MHz. NOTE 3: The EIRP requirement is converted to conducted requirement depend on the supported post antenna connector gain Gpost connector declared by the UE following the principle described in annex I. | 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.2.2.4 |
2,197 | 9.9.3.28 Short MAC | The purpose of the Short MAC information element is to protect the integrity of a SERVICE REQUEST message. The integrity protection shall include octet 1 and 2 of the SERVICE REQUEST message. For the used algorithm and other input parameters to the algorithm see clause 9.5. Only the 2 least significant octets of the resulting message authentication code are included in the information element. The Short MAC information element is coded as shown in figure 9.9.3.28.1 and table 9.9.3.28.1. The Short MAC is a type 3 information element with a length of 3 octets. Figure 9.9.3.28.1: Short MAC information element Table 9.9.3.28.1: Short MAC information element | 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 | 9.9.3.28 |
2,198 | 5.2.2.2.5 Namf_Communication_N1N2MessageSubscribe service operation | Service operation name: Namf_Communication_N1N2MessageSubscribe. Description: An NF can subscribe with the AMF to get notified of a particular N1 message type or a specific N2 information type about the UE. Input, Required: CN NF ID, N1 Message Type Input, Optional: SUPI. Output, Required: None. Output, Optional: None. The consumer NF invokes the Namf_Communication_N1MessageSubscribe service operation (NF ID, N1 message type or N2 information type to subscribe) on the AMF. The consumer NF shall provide a SUPI for UE associated N1 message subscriptions. If the consumer NF is allowed to subscribe for the type of N1/N2 message requested, the AMF creates a binding for the consumer NF to deliver subsequent Namf_Communication_N1MessageNotify or Namf_Communication_N2InfoNotify towards that NF. NOTE: Whether Subscription Ack need a separate message or be realized in the transport layer will be determined in TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ] [18]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.5 |
2,199 | 16.6.3 Subscription/unsubscription procedure of NSACF notification service | Figure 16.6.3-1: Subscription/unsubscription of NSACF notification procedure 0. Authentication of the AF: the AF is authenticated based on the description in clause 13 or clause 12. The AF authorization is based on clause 13 or clause 12 or local configuration at the NEF. If a token based authorization mechanism is used, a token is generated for the AF after authentication and authorization. 1. To subscribe or unsubscribe for the number of UEs or the number of PDU Sessions per network slice notification with the NSACF, the AF sends Nnef_EventExposure_Subscribe/Unsubscribe Request (Event ID, Event Filter, Event Reporting information) message to the NEF as described in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The Event Filter parameter shall be AF-Service-Identifier for an AF deployed outside the 3GPP operator domain. Other parameters are specified in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. 2. The NEF confirms with Nnef_ SliceStatusEventExposure _Subscribe/Unsubscribe Response message to the AF. The Event Filter parameter is the mapped AF-Service-Identifier for the AF deployed outside the 3GPP operator domain. 3. The NEF checks whether the AF is authorised for the requested subscription based on the AF token. It needs to check whether the token claims match the AFβs identity and the Event Filter parameter. If authorised, the NEF may query the NRF to find the NSACF responsible for the requested S-NSSAI (NEF needs to map to S-NSSAI based on AF-Service-Identifier for the AF deployed outside the 3GPP operator domain). 4. The NEF forwards the request to the NSACF with Nnsacf_SliceEventExposure_Subscribe/Unsubscribe Request (Event ID, Event Filter, Event Reporting information). The Event Filter parameter shall be the mapped S-NSSAI for the AF deployed outside the 3GPP operator domain. 5. The NSACF confirms with Nnsacf_SliceEventExposure_Subscribe/Usubscribe Response message to the NEF as in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. 6-7a. The NSACF triggers a notification towards the AF and sends the Nnsacf_SliceEvent Exposure_Notify (Event ID, Event Filter, Event Reporting information) message to the NEF as described in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. 7b-9. The NEF forwards the message to the AF for single NSACF or aggregates reporting information for multiple NSACFs in the Nnef_EventExposure_Notify (Event ID, Event Filter, Event Reporting information) message as described in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The Event Filter parameter shall be the mapped AF-Service-Identifier from the S-NSSAI for the AF deployed outside the 3GPP operator domain. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 16.6.3 |
2,200 | β RF-ParametersMRDC | The IE RF-ParametersMRDC is used to convey RF related capabilities for MR-DC. RF-ParametersMRDC information element -- ASN1START -- TAG-RF-PARAMETERSMRDC-START RF-ParametersMRDC ::= SEQUENCE { supportedBandCombinationList BandCombinationList OPTIONAL, appliedFreqBandListFilter FreqBandList OPTIONAL, ..., [[ srs-SwitchingTimeRequested ENUMERATED {true} OPTIONAL, supportedBandCombinationList-v1540 BandCombinationList-v1540 OPTIONAL ]], [[ supportedBandCombinationList-v1550 BandCombinationList-v1550 OPTIONAL ]], [[ supportedBandCombinationList-v1560 BandCombinationList-v1560 OPTIONAL, supportedBandCombinationListNEDC-Only BandCombinationList OPTIONAL ]], [[ supportedBandCombinationList-v1570 BandCombinationList-v1570 OPTIONAL ]], [[ supportedBandCombinationList-v1580 BandCombinationList-v1580 OPTIONAL ]], [[ supportedBandCombinationList-v1590 BandCombinationList-v1590 OPTIONAL ]], [[ supportedBandCombinationListNEDC-Only-v15a0 SEQUENCE { supportedBandCombinationList-v1540 BandCombinationList-v1540 OPTIONAL, supportedBandCombinationList-v1560 BandCombinationList-v1560 OPTIONAL, supportedBandCombinationList-v1570 BandCombinationList-v1570 OPTIONAL, supportedBandCombinationList-v1580 BandCombinationList-v1580 OPTIONAL, supportedBandCombinationList-v1590 BandCombinationList-v1590 OPTIONAL } OPTIONAL ]], [[ supportedBandCombinationList-v1610 BandCombinationList-v1610 OPTIONAL, supportedBandCombinationListNEDC-Only-v1610 BandCombinationList-v1610 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-r16 BandCombinationList-UplinkTxSwitch-r16 OPTIONAL ]], [[ supportedBandCombinationList-v1630 BandCombinationList-v1630 OPTIONAL, supportedBandCombinationListNEDC-Only-v1630 BandCombinationList-v1630 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1630 BandCombinationList-UplinkTxSwitch-v1630 OPTIONAL ]], [[ supportedBandCombinationList-v1640 BandCombinationList-v1640 OPTIONAL, supportedBandCombinationListNEDC-Only-v1640 BandCombinationList-v1640 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1640 BandCombinationList-UplinkTxSwitch-v1640 OPTIONAL ]], [[ supportedBandCombinationList-UplinkTxSwitch-v1670 BandCombinationList-UplinkTxSwitch-v1670 OPTIONAL ]], [[ supportedBandCombinationList-v1700 BandCombinationList-v1700 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1700 BandCombinationList-UplinkTxSwitch-v1700 OPTIONAL ]], [[ supportedBandCombinationList-v1720 BandCombinationList-v1720 OPTIONAL, supportedBandCombinationListNEDC-Only-v1720 SEQUENCE { supportedBandCombinationList-v1700 BandCombinationList-v1700 OPTIONAL, supportedBandCombinationList-v1720 BandCombinationList-v1720 OPTIONAL } OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1720 BandCombinationList-UplinkTxSwitch-v1720 OPTIONAL ]], [[ supportedBandCombinationList-v1730 BandCombinationList-v1730 OPTIONAL, supportedBandCombinationListNEDC-Only-v1730 BandCombinationList-v1730 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1730 BandCombinationList-UplinkTxSwitch-v1730 OPTIONAL ]], [[ supportedBandCombinationList-v1740 BandCombinationList-v1740 OPTIONAL, supportedBandCombinationListNEDC-Only-v1740 BandCombinationList-v1740 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1740 BandCombinationList-UplinkTxSwitch-v1740 OPTIONAL ]], [[ supportedBandCombinationList-v1770 BandCombinationList-v1770 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1770 BandCombinationList-UplinkTxSwitch-v1770 OPTIONAL ]], [[ supportedBandCombinationList-v1800 BandCombinationList-v1800 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1800 BandCombinationList-v1800 OPTIONAL ]] } RF-ParametersMRDC-v15g0 ::= SEQUENCE { supportedBandCombinationList-v15g0 BandCombinationList-v15g0 OPTIONAL, supportedBandCombinationListNEDC-Only-v15g0 BandCombinationList-v15g0 OPTIONAL } RF-ParametersMRDC-v15n0 ::= SEQUENCE { supportedBandCombinationList-v15n0 BandCombinationList-v15n0 OPTIONAL } RF-ParametersMRDC-v16e0 ::= SEQUENCE { supportedBandCombinationList-UplinkTxSwitch-v16e0 BandCombinationList-UplinkTxSwitch-v16e0 OPTIONAL } -- TAG-RF-PARAMETERSMRDC-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.