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
⌀ |
|---|---|---|---|---|---|---|---|
4,901 | 5.15.11.2.1 Non- Hierarchical NSAC architecture | The NSACF keeps track of the current number of PDU Sessions per network slice so that it can ensure it does not exceed the maximum number of PDU session allowed to be served by the network slice. When an event related to a UE causes the current number of PDU sessions established within the network slice is to increase, the NSACF checks whether the maximum number of PDU sessions per network slice for that network slice has already been reached and if it has, the NSACF applies admission control policies. The anchor SMF triggers a request to NSACF for maximum number of PDU sessions per network slice control during PDU session establishment/release procedures in clauses 4.3.2 and 4.3.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The SMF provides the Access Type to the NSACF when triggering a request to increase or decrease the number of PDU Sessions. The NSACF takes Access Type into account for increasing and decreasing the current number of PDU Sessions depending on the applicability of the Access Type for the NSAC for maximum number of PDU Sessions for the S-NSSAI. NOTE 1: For MA PDU Session, the SMF provides the Access Type to NSACF when the user plane connection is about to be established or released in the corresponding access network. With this, the SMF provides one or two Access Types for the MA PDU Session in the same request message to the NSACF. The NSACF can reject a single or both Access Types depending on the applicability of the Access Type for the NSAC. NOTE 2: I-SMF does not interact with NSCAF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.2.1 |
4,902 | I.2.3 Requirements for handling user plane data | An RNC in an exposed location has to cipher and decipher user plane packets between the Uu reference point and the Iu reference point and to handle integrity protection for user plane packets for the Iu reference point. 1. User plane data ciphering/deciphering and integrity handling shall take place inside the secure environment where the related keys are stored. 2. The transport of user data over Iu shall be integrity, confidentiality-, and replay-protected from unauthorized parties. If this is to be accomplished by cryptographic means, Annex I.3 shall be applied. NOTE: Protection for user data extends between the UE and the serving RNC, hence no separate requirement for the protection of user plane data transferred between a serving RNC and a potentially present drift RNC (cf. TS 25.420[ UTRAN Iur interface general aspects and principles ] [38]) is needed. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | I.2.3 |
4,903 | 6.6.2.2.6 Minimum requirement (network signalled value "NS_28”) | When "NS_28” is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.2.2.6-1 for E-UTRA channels assigned within the frequency ranges 5150-5350 and 5470-5725 MHz. Table 6.6.2.2.6-1: Additional requirements NOTE: 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. | 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.6 |
4,904 | 4.5.1.1 MM connection establishment initiated by the mobile station | Upon request of a CM entity to establish an MM connection the MM sublayer first decides whether to accept, delay, or reject this request: - An MM connection establishment may only be initiated by the mobile station when the following conditions are fulfilled: - Its update status is UPDATED. - The MM sublayer is in one of the states MM IDLE, RR CONNECTION RELEASE NOT ALLOWED or MM connection active but not in MM connection active (Group call). An exception from this general rule exists for emergency calls (see subclause 4.5.1.5). A further exception is defined in the following clause. - If an MM specific procedure is running at the time the request from the CM sublayer is received, and the LOCATION UPDATING REQUEST message has been sent, the request will either be rejected or delayed, depending on implementation, until the MM specific procedure is finished and, provided that the network has not sent a "follow-on proceed" indication, the RR connection is released. If the LOCATION UPDATING REQUEST message has not been sent, the mobile station may include a "follow-on request" indicator in the message. The mobile station shall then delay the request until the MM specific procedure is completed, when it may be given the opportunity by the network to use the RR connection: see subclause 4.4.4.6. In order to establish an MM connection, the mobile station proceeds as follows: a) If no RR connection exists, the MM sublayer requests the RR sublayer to establish an RR connection and enters MM sublayer state WAIT FOR RR CONNECTION (MM CONNECTION). This request contains an establishment cause and a CM SERVICE REQUEST message. When the establishment of an RR connection is indicated by the RR sublayer, the MM sublayer of the mobile station starts timer T3230, gives an indication to the CM entity that requested the MM connection establishment, and enters MM sublayer state WAIT FOR OUTGOING MM CONNECTION. b) If an RR connection is available, the MM sublayer of the mobile station sends a CM SERVICE REQUEST message to the network, starts timer T3230, stops and resets timer T3241, gives an indication to the CM entity that requested the MM connection establishment, and enters: - MM sublayer state WAIT FOR OUTGOING MM CONNECTION, if no MM connection is active; - MM sublayer state WAIT FOR ADDITIONAL OUTGOING MM CONNECTION, if at least one MM connection is active; - If an RR connection exists but the mobile station is in the state WAIT FOR NETWORK COMMAND then any requests from the CM layer that are received will either be rejected or delayed until this state is left. c) Only applicable for mobile stations supporting VGCS talking: If a mobile station which is in the MM sublayer state MM IDLE, service state RECEIVING GROUP CALL (NORMAL SERVICE), receives a request from the GCC sublayer to perform an uplink access, the MM sublayer requests the RR sublayer to perform an uplink access procedure and enters MM sublayer state WAIT FOR RR CONNECTION (GROUP TRANSMIT MODE). When a successful uplink access is indicated by the RR sublayer, the MM sublayer of the mobile station gives an indication to the GCC sublayer and enters MM sublayer state MM CONNECTION ACTIVE (GROUP TRANSMIT MODE). When an uplink access reject is indicated by the RR sublayer, the MM sublayer of the mobile station gives an indication to the GCC sublayer and enters the MM sublayer state MM IDLE, service state RECEIVING GROUP CALL (NORMAL SERVICE). In the network, if an uplink access procedure is performed, the RR sublayer in the network provides an indication to the MM sublayer together with the mobile subscriber identity received in the TALKER INDICATION message. The network shall then enter the MM sublayer state MM CONNECTION ACTIVE (GROUP TRANSMIT MODE). d) When the MS is IMSI attached for CS services via EMM combined procedures, as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], and the MS is camping on an E-UTRAN cell, and if T3246 is not running, the MM sublayer requests EMM to initiate a service request procedure for CS fallback. The MM connection establishment is delayed until the MS changes to a GERAN or UTRAN cell. If the MS enters a GERAN or UTRAN cell, then the MS shall initiate the MM connection establishment and send a CM SERVICE REQUEST message. The MS shall include the Additional update parameters information element indicating "CS fallback mobile originating call". If the MS determines that it is in a different location area than the stored location area, the MS shall first initiate a normal location updating procedure regardless of Network Mode of Operation. If the location area of the current cell is not available, the MS may initiate a normal location updating procedure directly. The MM connection establishment is delayed until successful completion of the normal location updating procedure. Additionally the MS performs routing area updating as specified in subclause 4.7.5. If the normal location updating procedure is initiated, the MS shall indicate the "follow-on request pending", shall include the Additional update parameters information element indicating"CS fallback mobile originating call", and shall not include the MS network feature support information element in the LOCATION UPDATING REQUEST message. In case a, b and d, the CM SERVICE REQUEST message contains the: - mobile identity according to subclause 10.5.1.4; - mobile station classmark 2; - ciphering key sequence number; and - CM service type identifying the requested type of transaction (e.g. mobile originating call establishment, emergency call establishment, short message service, supplementary service activation, location services). A MS supporting eMLPP may optionally include a priority level in the CM SERVICE REQUEST message. For MM connection establishment involving a shared GERAN network in A/Gb mode, if the MS is a GERAN network sharing supporting MS, the chosen PLMN identity shall be indicated to the GERAN in the CM SERVICE REQUEST message using the Skip Indicator IE as specified in subclause 10.3.1. A collision may occur when a CM layer message is received by the mobile station in MM sublayer state WAIT FOR OUTGOING MM CONNECTION or in WAIT FOR ADDITIONAL OUTGOING MM CONNECTION. In this case the MM sublayer in the MS shall establish a new MM connection for the incoming CM message as specified in subclause 4.5.1.3. Upon receiving a CM SERVICE REQUEST message, the network shall analyse its content. The type of semantic analysis may depend on other on going MM connection(s). Depending on the type of request and the current status of the RR connection, the network may start any of the MM common procedures and RR procedures. In A/Gb mode, the network may initiate the classmark interrogation procedure, for example, to obtain further information on the mobile station's encryption capabilities. The identification procedure (see subclause 4.3.3) may be invoked for instance if a TMSI provided by the mobile station is not recognized. The network may invoke the authentication procedure (see subclause 4.3.2) depending on the CM service type. In A/Gb mode, the network decides also if the ciphering mode setting procedure shall be invoked (see subclause 3.4.7 in 3GPP TS 44.018[ None ] [84]). In Iu mode, the network decides also if the security mode control procedure shall be invoked (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). NOTE 1: If the CM_SERVICE_REQUEST message contains a priority level the network may use this to perform queuing and pre-emption as defined in 3GPP TS 23.067[ enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 ] [88]. In A/Gb mode, the MS shall consider the MM connection establishment to be completed when: - receiving an indication from the RR sublayer that the ciphering mode setting procedure is completed; or - receiving a CM SERVICE ACCEPT message. In Iu mode, the MS shall consider the MM connection establishment to be completed when - receiving an indication from the RR sublayer that the security mode control procedure is completed, except for the case when it is the first security mode control procedure after successful inter-system change received in MM sublayer state WAIT FOR ADDITIONAL OUTGOING MM CONNECTION; or - receiving a CM SERVICE ACCEPT message. The procedures in subclause 4.1.1.1.1 shall always have precedence over this subclause. In Iu mode, during a MM connection establishment for all services, except for emergency call (see subclause 4.1.1.1.1), the security mode control procedure with activation of integrity protection shall be invoked by the network unless integrity protection is already started (see subclause 4.1.1.1.1). The MM connection establishment is completed, timer T3230 shall be stopped, the CM entity that requested the MM connection shall be informed, and MM sublayer state MM CONNECTION ACTIVE is entered. The MM connection is considered to be active. If the service request cannot be accepted, the network returns a CM SERVICE REJECT message to the mobile station. The reject cause information element (see subclause 10.5.3.6 and annex G) indicates the reason for rejection. The following cause values may apply: #4: IMSI unknown in VLR #6: Illegal ME #17: Network failure #22: Congestion #25 Not authorized for this CSG #32: Service option not supported #33: Requested service option not subscribed #34: Service option temporarily out of order If the service request is rejected due to general NAS level mobility management congestion control, the network shall set the MM cause value to #22 "congestion" and assign a back-off timer T3246 (see 3GPP TS 23.012[ Location management procedures ] [140]). If no other MM connection is active, the network may start the RR connection release (see subclause 3.5 of 3GPP TS 44.018[ None ] [84] (A/Gb mode only), 3GPP TS 25.331[ None ] [23c] (UTRAN Iu mode only), or in 3GPP TS 44.118[ None ] [111] (GERAN Iu mode only) when the CM SERVICE REJECT message is sent. If a CM SERVICE REJECT message is received by the mobile station, timer T3230 shall be stopped, the requesting CM sublayer entity informed. Then the mobile station shall proceed as follows: - If the cause value is not #4 or #6 or #25 received from a CSG cell and the MS is in UTRAN Iu mode, the MM sublayer returns to the previous state (the state where the request was received). Other MM connections shall not be affected by the CM SERVICE REJECT message. - If cause value #4 is received, the mobile station aborts any MM connection, deletes any TMSI, LAI and ciphering key sequence number in the SIM/USIM, changes the update status to NOT UPDATED (and stores it in the SIM/USIM according to subclause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. If subsequently the RR connection is released or aborted, this will force the mobile station to initiate a normal location updating). Whether the CM request shall be memorized during the location updating procedure, is a choice of implementation. - If cause value #6 is received, the mobile station aborts any MM connection, deletes any TMSI, LAI and ciphering key sequence number in the SIM/USIM, changes the update status to ROAMING NOT ALLOWED (and stores it in the SIM/USIM according to subclause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. The mobile station shall consider the SIM/USIM as invalid for non-GPRS services 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. - If cause value #22 is received, the T3246 value IE is present in the CM SERVICE REJECT message and the value indicates that this timer is neither zero nor deactivated, the MS shall check whether the CM SERVICE REJECT message with cause #22 is integrity protected and shall stop timer T3246 if it is running. If the message is integrity protected, the MS shall start timer T3246 with the value provided in the T3246 value IE. Otherwise, the MS shall start timer T3246 with a random value from the default range specified in table 11.1.The MS stays in the current serving cell and applies normal cell reselection process. The service request procedure may be started by CM layer, if it is still necessary, when timer T3246 expires or is stopped. If cause value #22 is received, the T3246 value IE is not present in the CM SERVICE REJECT message or if the T3246 value IE the value indicates that this timer is zero or deactivated, the same actions as on timer expiry in subclause 4.5.1.2 shall be taken by the mobile station. - If cause value #25 is received from a CSG cell and the MS is in UTRAN Iu mode, the MS shall check whether the CM SERVICE REJECT message with cause #25 is integrity protected. If the message is not integrity protected, the MS shall discard the message. Otherwise, the MS shall abort any MM connection, remove the entry corresponding to the CSG ID and associated PLMN identity of the cell where the MS has sent the CM SERVICE REQUEST message from the Allowed CSG list if the CSG ID and associated PLMN identity are contained in the Allowed CSG list, and enter the MM sublayer state WAIT FOR NETWORK COMMAND. If the CSG ID and associated PLMN identity of the cell where the MS has sent the CM SERVICE REQUEST message is contained in the Operator CSG list, the MS shall proceed as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] subclause 3.1A. Subsequently, after the RR connection is released or aborted, the MS applies normal cell reselection process. If cause value #25 is received and the cell is not a CSG cell or the MS is not in UTRAN Iu mode, the MS shall discard the CM SERVICE REJECT message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.1.1 |
4,905 | 5.8.6.3 Sidelink communication transmission reference cell selection | A UE capable of NR sidelink communication/discovery that is configured by upper layers to transmit NR sidelink communication/discovery shall: 1> for the frequency used to transmit NR sidelink communication/discovery, select a cell to be used as reference for synchronization in accordance with the following: 2> if the frequency concerns the primary frequency: 3> use the PCell or the serving cell as reference; 2> else if the frequency concerns a secondary frequency: 3> use the concerned SCell as reference; 2> else if the UE is in coverage of the concerned frequency: 3> use the DL frequency paired with the one used to transmit NR sidelink communication/discovery as reference; 2> else (i.e., out of coverage on the concerned frequency): 3> use the PCell or the serving cell as reference, if needed; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.6.3 |
4,906 | 6.40.2.2 Requirements for direct device connection | Based on user consent, operator policy and trusted 3rd party request, the 5G system shall support a means to authorize specific UEs to transmit data (e.g. AI-ML model data for a specific application,) via direct device connection in a certain location and time. Based on user consent, operator policy, and trusted 3rd party’s request, the 5G system shall be able to provide means for an operator to authorize specific UEs who participate in the same service (e.g. for the same AI-ML FL task) to exchange data with each other via direct device connection, e.g. when direct network connection cannot fulfil the required QoS. Based on user consent, operator policy and trusted 3rd party request, the 5G system shall be able to dynamically add or remove specific UEs to/from the same service (e.g. a AI-ML federated learning task) when communicating via direct device connection. Based on user consent and operator policy, the 5G system shall be able to provide means for the network to configure and modify remote UEs’ communication QoS, when a relay UE is involved, e.g., to satisfy end to end latency for proximity-based work task offloading. NOTE: for proximity-based work task offloading, the data packet size transmitted over the sidelink and Uu parts of the UE indirect network connection can be different. Subject to user consent and operator policy, the 5G system shall be able to support configuration of the QoS (e.g., latency, reliability, data rate) of a communication path using direct device connection, e.g., for AI-ML data transfer. Based on user consent, operator policy and trusted 3rd party request, the 5G system shall be able to support means to monitor the QoS characteristics (e.g. data rate, latency) of traffic transmitted via direct device connection or relayed by a UE, and 5G network expose the monitored information to the 3rd party. NOTE: The monitoring information doesn’t include user position-related data. Subject to user consent, operator policy and trusted 3rd party request, the 5G system shall be able to provide means the network to predict and expose QoS information changes for UEs’ traffic using direct or indirect network connection (e.g., bitrate, latency, reliability).The 5G system shall be able to support a mechanism for a trusted third-party to negotiate with the 5G system for a suitable QoS for direct device connections of multiple UEs exchanging data with each other (e.g. a group of UEs using the same AI-ML service). Based on user consent, operator policy and trusted 3rd party’s request, the 5G system shall be able to support and provision an aggregated QoS for multiple remote UEs served by a relay UE. Based on user consent, operator policy and trusted 3rd party’s request, the 5G system shall be able to support configuring specific QoS limitations applied to multiple UEs communicating via direct device connection (e.g. part of a joint AI-ML inference task). NOTE: the above requirement assumes unicast type of communication. Subject to user consent, regulation, trusted 3rd party’s request and operator policy, the 5G network shall be able to expose information to assist the 3rd party to determine candidate UEs for data transmission via direct device connection (e.g. for AIML model transfer for a specific application). NOTE: the information does not include user’s specific positioning and can include QoS information Subject to user consent, operator policy, regulation and trusted 3rd party’s request, the 5G network shall be able to expose information of certain UEs using the same service to the 3rd party (e.g. to assist a joint AIML task of UEs in a specific area using direct device communication) NOTE: the information does not include user’s exact positioning information. The 5G system shall be able to support charging mechanisms for multiple UEs exchanging data for the same service using the direct device connection (e.g. for AI-ML applications). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.40.2.2 |
4,907 | 9.12.2.1 FDD | For the parameters specified in Table 9.12.2.1-1, Table 9.12.2.1-2, and Table 9.12.2.1-3 using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.12.2.1-4 by the following a) a CQI index not in the set {median CQI -1, median CQI, median CQI +1} shall be reported at least % of the time; b) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index and that obtained when transmitting a fixed transport format configured according to the wideband CQI median shall be ≥ ; c) when transmitting the transport format indicated by each reported wideband CQI index, the average BLER for the indicated transport formats shall be greater or equal to [0.02]. Table 9.12.2.1-1: Fading test for slot-PDSCH (FDD) Table 9.12.2.1-2: Fading test for subslot-PDSCH (FDD) Table 9.12.2.1-3: SPDCCH parameters (FDD) Table 9.12.2.1-4: Minimum requirement for slot/subslot-PDSCH (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.12.2.1 |
4,908 | 7.9 KPIs for ranging based services | In several scenarios, it can be beneficial to determine the distance between two UEs and/or the direction of one UE from the other one via direct communication connection. The functional requirements related to ranging based services can be found in clause 6.37. Performance requirements for ranging based services in different scenarios can be found in table 7.9-1. Key performance indicators and key attributes for ranging are defined as follows: - Ranging accuracy: describes the absolute value of the deviation of the measured distance and/or direction between two UEs to the true distance and/or direction value. - Confidence level: describes the percentage of all the possible measured distance and/or direction that can be expected to include the true distance and/or direction considering the ranging accuracy. - Effective ranging distance: the largest distance between the UE who initiates the ranging and target UEs in the ranging operation. - Line-of-sight (LOS) Environment: the environment between the UE who initiates the ranging and target UEs, such as LOS and non-LOS (NLOS). - Coverage: type of radio coverage conditions of the UEs who are involved in ranging, such as in coverage (IC), partial coverage (PC) and out of coverage (OOC). See also figure 6.37.1-1. NOTE: If using licensed spectrum, ranging is only permitted in network coverage under the full control of the operator who provides the coverage, except for public safety networks with dedicated spectrum where ranging might be allowed out of coverage or in partial coverage as well. - Relative UE velocity: the target UE can be either static or mobile relative to the UE who initiates the ranging. In the latter, the attribute shall also provide some elements about its motion, e.g. maximum speed, trajectory. - Availability: percentage value of the amount of time when a ranging system is able to provide the required ranging-related data within the performance targets or requirements divided by the amount of time the system is expected to provide the ranging service in a targeted service area. - Latency: time elapsed between the event that triggers the determination of the ranging-related data and the availability of the ranging-related data at the ranging system interface. - Ranging interval: time difference between two consecutive ranging operations. Table 7.9-1: Performance requirements for ranging based services | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.9 |
4,909 | 6.3.3G Transmit OFF 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 shall meet the Transmit OFF power in subclause 6.3.3D. When 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 requirements in subclause 6.3.3A apply for as specified for the corresponding inter-band con-current operation with uplink assigned to two bands. For intra-band contiguous E-UTRA V2X multiple carrier transmissions, the requirements in subclause 6.3.3A apply as specified for the corresponding intra band contiguous carrier aggregation. The transmit OFF power is defined as the mean power at each transmit antenna connector. The transmit OFF power at each transmit antenna connector shall not exceed the values specified for single carrier. | 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.3.3G |
4,910 | S.3.2 5G NSWO procedures | Figure: S.3-1: Authentication procedure for NSWO in 5GS 1. The UE establishes a WLAN connection between the UE and the WLAN Access Network (AN), using procedures specified in IEEE 802.11[80]. 2. The WLAN AN sends an EAP Identity/Request to the UE. 3. The UE sends an EAP Response/Identity message. If the UE determines to use the NSWO service, the UE shall use the SUCI in NAI format (as specified in TS 23.003[ Numbering, addressing and identification ] [19], clause 28.7.12 and clause 28.7.9.2) as its identity irrespective of whether SUPI Type configured on the USIM is IMSI or NAI. If the SUPI Type configured on the USIM is IMSI, the UE shall construct the SUCI in NAI format with username containing the encrypted MSIN and the realm part containing the MCC/MNC. 4. The EAP Response/Identity message shall be routed over the SWa interface towards the NSWOF based on the realm part of the SUCI. NOTE 1: NSWOF acts as SBI/AAA proxy between the AUSF and the WLAN Access Network. 5. The NSWOF shall send the message Nausf_UEAuthentication_Authenticate Request with SUCI, Access Network Identity and NSWO indicator towards the AUSF. NSWO_indicator is used to indicate to the AUSF that the authentication request is for Non-seamless WLAN offload purposes. The NSWOF shall set the Access Network Identity to "5G:NSWO". 6. Based on the NSWO_indicator, the AUSF (acting as the EAP authentication server) shall send a Nudm_UEAuthentication_Get Request to the UDM, including SUCI and the Access Network Identity and NSWO indicator. 7. Upon reception of the Nudm_UEAuthentication_Get Request, the UDM shall invoke SIDF. SIDF shall de-conceal SUCI to gain SUPI before UDM can process the request. Based on the NSWO indicator, the UDM/ARPF shall select the EAP-AKA´ authentication method and generate an authentication vector using the Access Network Identity as the KDF input parameter. The UDM shall include the EAP-AKA’ authentication vector (RAND, AUTN, XRES, CK´ and IK´) and may include SUPI to AUSF in a Nudm_UEAuthentication_Get Response message. 8. The AUSF shall store XRES for future verification. The AUSF shall send the EAP-Request/AKA'-Challenge message to the NSWOF in a Nausf_UEAuthentication_Authenticate Response message. NOTE: The Access Network Identity is carried in the AT_KDF_INPUT attribute in EAP-AKA' as defined in RFC 5448 [12]. 9. The NSWOF shall send the EAP-Request/AKA'-Challenge message to the WLAN AN over the SWa interface. 10. The WLAN AN forwards the EAP-Request/AKA'-Challenge message to the UE. 11. At receipt of the RAND and AUTN in the EAP-Request/AKA'-Challenge message, the ME shall obtain the Access Network Identity from the EAP signalling and the USIM in the UE shall verify the freshness of the AV' by checking whether AUTN can be accepted as described in TS 33.102[ 3G security; Security architecture ] [40]. If so, the USIM computes a response RES. The USIM shall return RES, CK, IK to the ME. The ME shall derive CK' and IK' using the Access Network Identity as the KDF input parameter. If the verification of the AUTN fails on the USIM, then the USIM and ME shall proceed as described in sub-clause 6.1.3.3. The UE may derive MSK from CK’ and IK’ as per Annex F and as described in RFC 5448[12]. When the UE is performing NSWO authentication, the KAUSF shall not be generated by the UE. 12. The UE shall send the EAP-Response/AKA'-Challenge message to the WLAN AN. 13. The WLAN AN forwards the EAP-Response/AKA'-Challenge message over the SWa interface to the NSWOF. 14. The NSWOF shall send the Nausf_UEAuthentication_Authenticate Request with EAP-Response/AKA'-Challenge message to AUSF. 15. The AUSF shall verify if the received response RES matches the stored and expected response XRES. If the AUSF has successfully verified, it continues as follows to step 16, otherwise it returns an error to the NSWOF. The AUSF shall derive the required MSK key from CK’ and IK’ as per Annex F and as described in RFC 5448[12], based on the NSWO indicator received in step 5. The AUSF shall not generate the KAUSF. 16. The AUSF shall send Nausf_UEAuthentication_Authenticate Response message with EAP-Success and MSK key to NSWOF. The AUSF may optionally provide the SUPI to NSWOF. The AUSF/UDM shall not perform the linking increased home control to subsequent procedures (as stated in present document clause 6.1.4). 17. The NSWOF shall send the EAP-success and MSK to WLAN AN over the SWa interface. The EAP-Success message is forwarded from WLAN AN to the UE. 18. Upon receiving the EAP-Success message, the UE derives the MSK as specified in step 11, if it has not derived the MSK earlier. The UE uses the first 256-bit of MSK as PMK to perform 4-way handshake to establish a secure connection with the WLAN AN. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | S.3.2 |
4,911 | 8.10.4.1.2 TDD | The parameters specified in Table 8.10.4.1.2-1 are valid for all TDD distributed EPDCCH tests with 4Rx unless otherwise stated. Table 8.10.4.1.2-1: Test Parameters for Distributed EPDCCH with 4Rx For the parameters specified in Table 8.10.4.1.2-1 the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.10.4.1.2-2. The downlink physical setup is in accordance with Annex C.3.2. Table 8.10.4.1.2-2: Minimum performance Distributed EPDCCH with 4Rx Antenna ports | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.4.1.2 |
4,912 | 8.2.2.1 Inter-gNB-DU Mobility using MCG SRB | This procedure is used for the case the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU when only MCG SRB is available during EN-DC operation. Figure 8.2.2.1-1 shows the inter-gNB-DU mobility procedure using MCG SRB in EN-DC. Figure 8.2.2.1-1: Inter-gNB-DU Mobility using MCG SRB in EN-DC 1. The UE sends an ULInformationTransferMRDC message to the MeNB. 2. The MeNB sends RRC TRANSFER message to the gNB-CU. 3. The gNB-CU may send UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU to query the latest SCG configuration. 4. The source gNB-DU responds with an UE CONTEXT MODIFICATION RESPONSE message that includes full configuration information. 5. The gNB-CU sends an UE CONTEXT SETUP REQUEST message to the target gNB-DU to create an UE context and setup one or more data bearers. The UE CONTEXT SETUP REQUEST message includes a CG ConfigInfo. 6. The target gNB-DU responds the gNB-CU with an UE CONTEXT SETUP RESPONSE message. 7. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU indicating to stop the data transmission to the UE. The source gNB-DU also sends a Downlink Data Delivery Status frame to inform the gNB-CU about the unsuccessfully transmitted downlink data to the UE. 8. The source gNB-DU responds the gNB-CU with an UE CONTEXT MODIFICATION RESPONSE message. 9. The gNB-CU sends an SGNB MODIFICATION REQUIRED message to the MeNB. 10/11. The MeNB Initiated SgNB Modification procedure may be triggered by the SgNB Initiated SgNB Modification procedure (e.g. to provide information such as data forwarding addresses, new SN security key, measurement gap, etc...). 12. The MeNB and the UE perform RRC Connection Reconfiguration procedure. 13. The MeNB sends an SGNB MODIFICATION CONFIRM message to the gNB-CU. 14. Random Access procedure is performed at the target gNB-DU. The target gNB-DU sends a Downlink Data Delivery Status frame to inform the gNB-CU. Downlink packets, which may include PDCP PDUs not successfully transmitted in the source gNB-DU, are sent from the gNB-CU to the target gNB-DU. Downlink packets are sent to the UE. Also, uplink packets are sent from the UE, which are forwarded to the gNB-CU through the target gNB-DU. NOTE: It is up to gNB-CU implementation whether to start sending DL User Data to gNB-DU before or after reception of the Downlink Data Delivery Status. 15. The gNB-CU sends an UE CONTEXT RELEASE COMMAND message to the source gNB-DU. 16. The source gNB-DU releases the UE context and responds the gNB-CU with an UE CONTEXT RELEASE COMPLETE message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.2.1 |
4,913 | 4.13.4 Verification of UE location | In order to ensure that the regulatory requirements are met, the network may be configured to enforce that the selected PLMN is allowed to operate in the current UE location by verifying the UE location during EMM and ESM procedures. In this case, when the MME receives the User Location Information (ULI) for a UE using satellite access for Cellular IoT, the MME may decide to verify the UE location. If the MME determines based on the Selected PLMN ID and the identity of the cell serving this UE that it is not allowed to operate at the present UE location the MME should reject any NAS request with a suitable Cause value. If the UE is already registered to the network when the MME determines that the UE is not allowed to operate at the present UE location, the MME may initiate an explicit detach of the UE. The MME should not reject the request or detach the UE unless it has sufficiently accurate UE location information to determine that the UE is located in a geographical area where the PLMN is not allowed to operate. NOTE: The area where the PLMN is allowed to operate can be determined based on local regulations and licensing conditions. If the MME is not able to determine the UE location with sufficient accuracy to make a decision or if the received ULI is not sufficiently reliable, the MME proceeds with the Mobility Management or Session Management procedure and may initiate UE location procedure after the Mobility Management or Session Management procedure is complete, as specified in clause 9.1.17 of TS 23.271[ Functional stage 2 description of Location Services (LCS) ] [57], to determine the UE location. The MME shall be prepared to detach the UE if the information received from the E SMLC indicates that the UE is registered to a PLMN that is not allowed to operate in the UE location. In case of a NAS procedure, the MME should either reject any NAS request targeted towards a PLMN that is not allowed to operate in the known UE location and indicate a suitable cause value, or accept the NAS procedure and initiate the Detach procedure once the UE location is known. In the Detach Request message to the UE, the MME shall include a suitable cause value. | 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.13.4 |
4,914 | 5.22.4 QoS Mechanisms applied to established QoS Flows | Mechanisms applied to established QoS Flows: - (R)AN: QoS Flows requested in the Xn "Handover Request" or N2 "Handover Request" which are marked as entitled to priority by virtue of inclusion of an ARP value from the set allocated by the Service Provider for prioritised services are given priority over requests for QoS Flows which do not include an ARP from the set as specified in clause 4.9 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - SMF: Congestion management procedures in the SMF will provide priority to QoS Flows established for sessions during periods of extreme overload. Prioritised services are exempt from any session management congestion controls. See clause 5.19. - AMF: Congestion management procedures in the AMF will provide priority to any Mobility Management procedures required for the prioritised services during periods of extreme overload. Prioritised services are exempt from any Mobility Management congestion controls. See clause 5.19.5. - QoS Flows whose ARP parameter is from the set allocated by the Service Provider for prioritised services' use shall be exempt from release during QoS Flow load rebalancing. - (R)AN, UPF: IMS Signalling Packets associated with prioritised services' use are handled with priority. Specifically, during times of severe congestion when it is necessary to drop packets on the IMS Signalling QoS Flow, or QoS Flow supporting MPS for Data Transport Service signalling, to ensure network stability, these FEs shall drop packets not associated with priority signalling such as MPS or Mission Critical services before packets associated with priority signalling. See clauses 5.16.5 and 5.16.6. - (R)AN, UPF: During times of severe congestion when it is necessary to drop packets on a media QoS Flow to ensure network stability, these FEs shall drop packets not associated with priority sessions such as MPS or Mission Critical services before packets associated with priority sessions. See clauses 5.16.5 and 5.16.6. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.22.4 |
4,915 | – UEPositioningAssistanceInfo | The UEPositioningAssistanceInfo message is used to provide positioning assistance information as requested by the Network. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network UEPositioningAssistanceInfo message -- ASN1START -- TAG-UEPOSITIONINGASSISTANCEINFO-START UEPositioningAssistanceInfo-r17 ::= SEQUENCE { criticalExtensions CHOICE { uePositioningAssistanceInfo-r17 UEPositioningAssistanceInfo-r17-IEs, criticalExtensionsFuture SEQUENCE {} } } UEPositioningAssistanceInfo-r17-IEs ::= SEQUENCE { ue-TxTEG-AssociationList-r17 UE-TxTEG-AssociationList-r17 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UEPositioningAssistanceInfo-v1720-IEs OPTIONAL } UEPositioningAssistanceInfo-v1720-IEs::= SEQUENCE { ue-TxTEG-TimingErrorMarginValue-r17 ENUMERATED {tc0, tc2, tc4, tc6, tc8, tc12, tc16, tc20, tc24, tc32, tc40, tc48, tc56, tc64, tc72, tc80} OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } UE-TxTEG-AssociationList-r17 ::= SEQUENCE (SIZE (1..maxNrOfTxTEGReport-r17)) OF UE-TxTEG-Association-r17 UE-TxTEG-Association-r17 ::= SEQUENCE { ue-TxTEG-ID-r17 INTEGER (0..maxNrOfTxTEG-ID-1-r17), nr-TimeStamp-r17 NR-TimeStamp-r17, associatedSRS-PosResourceIdList-r17 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResourceId-r16, servCellId-r17 ServCellIndex OPTIONAL } NR-TimeStamp-r17 ::= SEQUENCE { nr-SFN-r17 INTEGER (0..1023), nr-Slot-r17 CHOICE { scs15-r17 INTEGER (0..9), scs30-r17 INTEGER (0..19), scs60-r17 INTEGER (0..39), scs120-r17 INTEGER (0..79) }, ... } -- TAG-UEPOSITIONINGASSISTANCEINFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,916 | 5.4A.4.1 Slot-SPUCCH | The block of bits shall be scrambled according to clause 5.4.2B. The block of scrambled bits shall be QPSK modulated as described in Clause 7.1, resulting in a block of complex-valued modulation symbols where . The block of complex-valued symbols is divided into (defined in Table 5.4A.4.1-1) sets, each corresponding to one SC-FDMA symbol. Transform precoding shall be applied according to clause 5.4.2B replacing with and replacing with . The variable, where represents the bandwidth of the SPUCCH format 4 in terms of resource blocks in the frequency domain, and is determined by higher layer signalling (n4numberOfPRB-r15, see TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4, Table 10.1.1-2] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]), and shall fulfil , where, is a set of non-negative integers. Table 5.4A.4.1-1: The quantity . | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4A.4.1 |
4,917 | 5.40.2 UE configuration and provisioning for Disaster Roaming | A UE supporting Disaster Roaming is configured with the following information: - Optionally, indication of whether disaster roaming is enabled in the UE; - Optionally, indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN'; - Optionally, list of PLMN(s) to be used in Disaster Condition. The Activation of Disaster Roaming is performed by the HPLMN by setting the indication of whether Disaster roaming is enabled in the UE to "disaster roaming is enabled in the UE" using the UE Parameters Update Procedure as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The UE shall only perform disaster roaming if the HPLMN has configured the UE with the indication of whether disaster roaming is enabled in the UE and set the indication to "disaster roaming is enabled in the UE". The UE, registered for Disaster Roaming service, shall deregister from the PLMN providing Disaster Roaming service if the received indication of whether disaster roaming is enabled in the UE is set to "disaster roaming is disabled in the UE". The optional 'list of PLMN(s) to be used in Disaster Condition' may be pre-configured in USIM or provided by the HPLMN during and after a successful registration procedure over 3GPP access or non-3GPP access via Registration Request procedure or UE Configuration Update procedure as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The 'list of PLMN(s) to be used in Disaster Condition' may be configured over non-3GPP access before disaster condition has occurred. While roaming (i.e. not in HPLMN), the Registered PLMN may provide the 'list of PLMN(s) to be used in Disaster Condition' during and after a successful registration procedure to the UE via Registration Request procedure or UE Configuration Update procedure as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. This list shall not alter any list provided by the HPLMN and shall only be used if the UE is configured by the HPLMN using the UE Parameters Update Procedure as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3] with the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' set to "True". The details of the UE behaviour regarding the usage of this list are described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. If the UE is not configured with 'list of PLMN(s) to be used in Disaster Condition', the UE follows the procedure described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] to select PLMN to be used in Disaster Condition. The HPLMN may use UE Parameters Update Procedure as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3] to update the Disaster Roaming information configuration in UE, if the UDM has received MINT support indication as indicated in 5GMM capability from the AMF. The UE indicates the support of MINT in 5GMM capability as specified in clause 5.4.4a, during registration procedure as defined in 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.40.2 |
4,918 | 8.2.2.3.1C Enhanced Performance Requirement Type C - 2 Tx Antenna Ports with TM1 interference | The requirements are specified in Table 8.2.2.3.1C-2, with the addition of parameters in Table 8.2.2.3.1C-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of open-loop spatial multiplexing performence with 2 transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell with transmission mode 1. In Table 8.2.2.3.1C-1, Cell 1 is the serving cell, and Cell 2 is interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2 respectively. Table 8.2.2.3.1C-1 Test parameters for Larger Delay CDD (FRC) with TM1 interference Table 8.2.2.3.1C-2 Enhanced Performance Requirement Type C, Larger Delay CDD (FRC) with TM1 interference | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.3.1C |
4,919 | 4.12 Supporting up to 15 EPS bearers per UE | A UE attached to WB-E-UTRAN access, including for dual connectivity using E-UTRAN access as described in clause 4.3.2a, may support 8 or 15 EPS bearers. To enable support of establishing 15 EPS bearers, it requires the EPC connected to the E-UTRAN access to support 15 EPS bearers for such UEs. If the UE supports 15 EPS bearers, then the UE shall indicate this to the MME in NAS signalling as defined in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. The network shall support E-UTRAN idle mode mobility and handover procedures in such PLMNs, where only part of the network nodes have been upgraded to support 15 EPS bearers. In the case of mobility procedures involving target nodes not supporting 15 EPS bearers, additional bearers not supported by the non-upgraded nodes should be thus released. The network shall homogeneously support 15 EPS bearers per UE, at least per MME pool area/SGW serving area, in order to avoid EPS bearer deactivations and attempts from services to re-activate the deactivated EPS bearers caused by UE mobility within that area, by defining the tracking areas accordingly (see clause 4.3.5.3). The MME shall provide the UE with a TAI List such that it triggers the UE to perform the TAU procedure, as defined in clause 5.3.3.0, when the UE enters and exits the area with support for 15 EPS bearers per UE. The TAU procedure execution enables the nodes in the supporting area to identify a supporting UE when it enters the area. When exiting the area, also enables the nodes to remove bearer resources for the UE towards nodes without support for 15 EPS bearers per UE. NOTE 1: In order for the above TAI List handling to be fully successful, the network requires the PGWs the UE is connected to from these MME pool area/SGW serving area to be upgraded to support 15 EPS bearers. For a UE supporting 15 EPS bearers, mobility to UTRAN or GERAN may also lead to selective release of EPS bearers, due to the lack of support of 15 PDP contexts in the GPRS core network and Radio Access networks. NOTE 2: EPS bearers need to be released either because the UE has more than 8 active EPS bearers, or because they are identified by EPS Bearer Identities not supported. In order to minimize the impact from release of bearers not supported by the target nodes during mobility, the MME should be able to allocate the EPS bearer IDs in such way that the bearers with higher operator preference will be preserved in the case of mobility involving legacy target nodes. This prioritised bearer allocation should be based on, at least, the Allocation Retention Priority of the EPS bearers and may take other bearer parameters (e.g. QCI, APN) into consideration. All PDN GWs in a PLMN shall support 15 EPS bearers. MME may be configured to take into account additional PDN GW information such as whether the HPLMN supports 15 EPS bearers when selecting PDN GW (e.g. in the case of roaming users Home Routed PDN GW selection) for UEs supporting 15 EPS bearers. For inter-PLMN handover, support of 15 EPS bearers is based on MME configuration according to operator policy (e.g. bilateral agreements between operators). | 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.12 |
4,920 | 10.2.1 EN-DC | The Secondary Node Addition procedure is initiated by the MN and is used to establish a UE context at the SN to provide resources from the SN to the UE. For bearers requiring SCG radio resources, this procedure is used to add at least the first cell of the SCG. This procedure can also be used to configure an SN terminated MCG bearer (where no SCG configuration is needed). In case of CPA, the Conditional Secondary Node Addition procedure can be used for CPA configuration and CPA execution. Secondary Node Addition Figure 10.2.1-1 shows the Secondary Node Addition procedure. Figure 10.2.1-1: Secondary Node Addition procedure 1. The MN decides to request the SN to allocate resources for a specific E-RAB, indicating E-RAB characteristics (E-RAB parameters, TNL address information corresponding to bearer type). In addition, for bearers requiring SCG radio resources, MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the latest measurement results for SN to choose and configure the SCG cell(s). The MN may request the SN to allocate radio resources for split SRB operation. The MN always provides all the needed security information to the SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. In case of bearer options that require X2-U resources between the MN and the SN, the MN provides X2-U TNL address information for the respective E-RAB, X2-U DL TNL address information for SN terminated bearers, X2-U UL TNL address information for MN terminated bearers. In case of SN terminated split bearers the MN provides the maximum QoS level that it can support. The MN may request the SCG to be activated or deactivated. The SN may reject the addition request. NOTE 1: For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MNs decision is reflected in step 1 by the E-RAB parameters signalled to the SN, which may differ from E-RAB parameters received over S1. NOTE 2: For a specific E-RAB, the MN may request the direct establishment of an SCG or a split bearer, i.e., without first having to establish an MCG bearer. It is also allowed that all E-RABs can be configured as SN terminated bearers, i.e. there is no E-RAB established as an MN terminated bearer. 2. If the RRM entity in the SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer option, respective transport network resources. For bearers requiring SCG radio resources, the SN triggers Random Access so that synchronisation of the SN radio resource configuration can be performed. The SN decides the PSCell and other SCG SCells and provides the new SCG radio resource configuration to the MN in a NR RRC configuration message contained in the SgNB Addition Request Acknowledge message. In case of bearer options that require X2-U resources between the MN and the SN, the SN provides X2-U TNL address information for the respective E-RAB, X2-U UL TNL address information for SN terminated bearers, X2-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the SN provides the S1-U DL TNL address information for the respective E-RAB and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided. If the MN requested the SCG to be deactivated, the SN may keep the SCG activated. If the MN requests the SCG to be activated, the SN shall keep the SCG activated. NOTE 3: For the SN terminated split bearer option, the SN may either decide to request resources from the MN of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MN and the SN together, or even more. The SNs decision is reflected in step 2 by the E-RAB parameters signalled to the MN, which may differ from E-RAB parameters received in step 1. The QoS level requested from the MN shall not exceed the level that the MN offered when setting up the split bearer in step 1. NOTE 4: In case of MN terminated bearers, transmission of user plane data may take place after step 2. NOTE 5: In case of SN terminated bearers, data forwarding and the SN Status Transfer may take place after step 2. 3. The MN sends to the UE the RRCConnectionReconfiguration message including the NR RRC configuration message, without modifying it. Within the MN RRCConnectionReconfiguration message, the MN can indicate the SCG is deactivated. 4. The UE applies the new configuration and replies to MN with RRCConnectionReconfigurationComplete message, including a NR RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. 5. The MN informs the SN that the UE has completed the reconfiguration procedure successfully via SgNB ReconfigurationComplete message, including the encoded NR RRC response message, if received from the UE. 6. If configured with bearers requiring SCG radio resources and the SCG is not deactivated, the UE performs synchronisation towards the PSCell of the SN. The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure. 7. If PDCP termination point is changed to the SN for bearers using RLC AM, and when RRC full configuration is not used, the MN sends the SN Status Transfer message. 8. For SN terminated bearers moved from the MN, dependent on the bearer characteristics of the respective E-RAB, the MN may take actions to minimise service interruption due to activation of EN-DC (Data forwarding). 9-12. If applicable, the update of the UP path towards the EPC is performed. Conditional Secondary Node Addition Figure 10.2.1-2 shows the Conditional Secondary Node Addition procedure. Figure 10.2.1-2: Conditional Secondary Node Addition procedure 1. The MN decides to configure CPA for the UE and requests the candidate SN(s) to allocate resources for a specific E-RAB, indicating E-RAB characteristics (E-RAB parameters, TNL address information corresponding to bearer type), indicating that the request is for CPAC and providing the upper limit for the number of PSCells that can be prepared by the candidate SN. In addition, for the bearers requiring SCG radio resources, the MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN to choose from and configure the SCG cell(s). The MN may request the candidate SN to allocate radio resources for split SRB operation. The MN always provides all the needed security information to the candidate SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. In case of bearer options that require X2-U resources between the MN and the candidate SN, the MN provides X2-U TNL address information for the respective E-RAB, X2-U DL TNL address information for SN terminated bearers, X2-U UL TNL address information for MN terminated bearers. In case of SN terminated split bearers the MN provides the maximum QoS level that it can support. The candidate SN may reject the addition request. NOTE 6: For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MN decision is reflected in step 1 by the E-RAB parameters signalled to the candidate SN, which may differ from E-RAB parameters received over S1. NOTE 7: For a specific E-RAB, the MN may request the direct establishment of an SCG or a split bearer, i.e., without first having to establish an MCG bearer. It is also allowed that all E-RABs can be configured as SN terminated bearers, i.e. there is no E-RAB established as an MN terminated bearer. 2. If the RRM entity in the candidate SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer option, respective transport network resources, and provides the prepared PSCell ID(s) to the MN. For bearers requiring SCG radio resources, the candidate SN configures Random Access so that synchronisation of the SN radio resource configuration can be performed at the CPA execution. From the list of cells indicated within the measurement results provided by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides SCG SCells and provides the corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message contained in the SgNB Addition Request Acknowledge message. The candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates. In case of bearer options that require X2-U resources between the MN and the candidate SN, the candidate SN provides X2-U TNL address information for the respective E-RAB, X2-U UL TNL address information for SN terminated bearers, X2-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the candidate SN provides the S1-U DL TNL address information for the respective E-RAB and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided. NOTE 8: For the SN terminated split bearer option, the candidate SN may either decide to request resources from the MN of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MN and the candidate SN together, or even more. The candidate SN decision is reflected in step 2 by the E-RAB parameters signalled to the MN, which may differ from E-RAB parameters received in step 1. The QoS level requested from the MN shall not exceed the level that the MN offered when setting up the split bearer in step 1. NOTE 9: In case of SN terminated bearers, early data forwarding may take place after step 2. For the early data forwarding of SN terminated bearers, the MN forwards the PDCP SDU to the candidate SN and also sends the Early Status Transfer message. For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN. 3. The MN sends to the UE an RRCConnectionReconfiguration message including the CPA configuration, i.e. a list of RRCConnectionReconfiguration* messages and associated execution conditions. Each RRCConnectionReconfiguration* message contains the SCG configuration in the RRCReconfiguration** message received from the candidate SN in step 2 and possibly an MCG configuration. Besides, the RRCConnectionReconfiguration message can also include an updated MCG configuration, e.g., to configure the required conditional measurements. 4. The UE applies the RRCConnectionReconfiguration message received in step 3, stores the CPA configuration and replies to the MN with an RRCConnectionReconfigurationComplete message. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. 4a. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCConnectionReconfiguration* message corresponding to the selected candidate PSCell, and sends an RRCConnectionReconfigurationComplete* message, including an NR RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. 5a-5c. The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via SgNB Reconfiguration Complete message, including the RRCReconfigurationComplete** message. The MN sends the SgNB Release Request message(s) to cancel CPA in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. 6. The UE performs synchronisation towards the PSCell indicated in the RRCConnectionReconfiguration* message applied in step 4a. The order the UE sends the RRCConnectionReconfigurationComplete* message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure. 7. If PDCP termination point is changed to the SN for bearers using RLC AM, and when RRC full configuration is not used, the MN sends the SN Status Transfer message. 8. For SN terminated bearers moved from the MN, dependent on the bearer characteristics of the respective E-RAB, the MN may take actions to minimise service interruption due to activation of EN-DC (Data forwarding). 9-12. If applicable, the update of the UP path towards the EPC is performed. | 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.2.1 |
4,921 | 4.7.5.1.5 Abnormal cases in the MS | The following abnormal cases can be identified: a) Access barred because of access class control, EAB or ACDC If the routing area updating procedure is started in response to a paging request from the network, access class barring, EAB or ACDC is not applicable. The routing area updating procedure shall not be started. The MS stays in the current serving cell and applies the normal cell reselection process. The procedure is started as soon as possible and if still necessary, i.e. when the barred state is removed or because of a cell change. If access is barred because of access class control, the upper layers request PS signalling connection, ACDC is applicable to the request and the MS supports ACDC, then the routing area updating procedure shall be started according to subclause 4.7.5.1.1. If access is barred for a certain ACDC category, and if the upper layers request PS signalling connection for a higher ACDC category and the MS supports ACDC, then the routing area updating procedure shall be started according to subclause 4.7.5.1.1. If an access request for an uncategorized application is barred due to ACDC , and if the upper layers request PS signalling connection for a certain ACDC category and the MS supports ACDC, then the routing area updating procedure shall be started according to subclause 4.7.5.1.1. b) Lower layer failure without "Extended Wait Time" received from lower layers before the ROUTING AREA UPDATE ACCEPT or ROUTING AREA UPDATE REJECT message is received The procedure shall be aborted and the MS shall proceed as described below, except in the following implementation option cases b.1 and b.2. b.1) Release of PS signalling connection before the completion of the routing area updating procedure The routing area updating procedure shall be initiated again, if the following conditions apply: i) The original routing area update procedure was initiated over an existing PS signalling connection; and ii) The routing area update procedure was not due to timer T3330 expiry; and iii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection were (e.g. PS authentication procedure, see subclause 4.7.7) received after the ROUTING AREA UPDATE REQUEST message was transmitted. b.2) RR release in Iu mode (i.e. RRC connection release) with, for example, cause "Normal", or "User inactivity" or "Direct signalling connection re-establishment" (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) The routing area updating procedure shall be initiated again, if the following conditions apply: i) The original routing area update procedure was initiated over an existing RRC connection; and ii) The routing area update procedure was not due to timer T3330 expiry; and iii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the ROUTING AREA UPDATE REQUEST message was transmitted. NOTE 1: The RRC connection release cause that triggers the re-initiation of the routing area update procedure is implementation specific. c) T3330 time-out The procedure is restarted four times, i.e. on the fifth expiry of timer T3330, the MS shall abort the procedure and, in Iu mode, release the PS signalling connection (see 3GPP TS 25.331[ None ] [23c]). The MS shall proceed as described below. d) ROUTING AREA UPDATE REJECT, other causes than those treated in subclause 4.7.5.1.4, and cases of GMM cause values #22 and #25, if considered as abnormal cases according to subclause 4.7.5.1.4 If the routing area updating request is not for initiating a PDN connection for emergency bearer services, upon reception of the cause codes # 95, # 96, # 97, # 99 and # 111 the MS should set the routing area updating attempt counter to 5. The MS shall proceed as described below. e) If a routing area border is crossed, when the MS is in state GMM-ROUTING-AREA-UPDATE-INITIATED, the routing area updating procedure shall be aborted and re-initiated immediately. The MS shall set the GPRS update status to GU2 NOT UPDATED. f) In A/Gb mode, if a cell change occurs within the same RA, when the MS is in state GMM-ROUTING-AREA-UPDATE-INITIATED, the cell update procedure is performed, before completion of the routing area updating procedure. g) Routing area updating and detach procedure collision GPRS detach containing detach type "re-attach required" or "re-attach not required": If the MS receives a DETACH REQUEST message before the routing area updating procedure has been completed, the routing area updating procedure shall be aborted and the GPRS detach procedure shall be progressed. If the DETACH REQUEST message contains detach type "re-attach not required" and GMM cause #2 "IMSI unknown in HLR", the MS will follow the procedure as described below for the detach type "IMSI detach". GPRS detach containing detach type "IMSI detach": If the MS receives a DETACH REQUEST message before the routing area updating procedure has been completed, the routing area updating procedure shall be progressed, i.e. the DETACH REQUEST message shall be ignored. The MS shall proceed as described below. h) Routing area updating and P-TMSI reallocation procedure collision If the MS receives a P-TMSI REALLOCATION C0MMAND message before the routing area updating procedure has been completed, the P-TMSI reallocation procedure shall be aborted and the routing area updating procedure shall be progressed. i) "Extended wait time" for PS domain from the lower layers If the ROUTING AREA UPDATE REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall start timer T3346 with the "Extended wait time" value and reset the routing area updating attempt counter. In other cases the MS shall ignore the "Extended wait time". The MS shall abort the routing area updating procedure, stay in the current serving cell, set the GPRS update status to GU2 NOT UPDATED, change the state to GMM-REGISTERED.ATTEMPTING-TO-UPDATE and apply the normal cell reselection process. If the MS had used eDRX before initiating routing area updating procedure, then the MS shall continue to use the eDRX with the extended DRX parameters IE received during the last attach or routing area updating procedure. The MS shall proceed as described below. j) Timer T3346 is running The MS shall not start the routing area updating procedure unless: - the MS is an MS configured to use AC11 – 15 in selected PLMN; - the MS is in PMM-CONNECTED mode (Iu mode); - the MS receives a paging; - the MS has a PDN connection for emergency bearer services established; - the MS is establishing a PDN connection for emergency bearer services; or - the MS has a PDN connection established without the NAS signalling low priority indication or is establishing a PDN connection without the NAS signalling low priority indication and if the timer T3346 was started due to rejection of a NAS request message (e.g. ATTACH REQUEST, ROUTING AREA UPDATE REQUEST or SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority". The MS stays in the current serving cell and applies the normal cell reselection process. NOTE 2: It is considered an abnormal case if the MS needs to initiate an routing area updating procedure while timer T3346 is running independent on whether timer T3346 was started due to an abnormal case or a non successful case. If the stored RAI is different to the RAI of the current serving cell or the TIN indicates "GUTI", the MS shall set the GPRS update status to GU2 NOT UPDATED and change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE. The MS shall proceed as described below. k) Mobile originated detach required GPRS detach due to removal of the USIM or due to switch off: If the MS is in the state GMM-ROUTING-AREA-UPDATE-INITIATED, the routing area updating procedure shall be aborted and the GPRS detach procedure shall be performed (see subclause 4.7.4.1). GPRS detach not due to removal of the USIM and not due to switch off: The MS shall initiate the MS initiated detach procedure after successful completion of the routing area updating procedure. l) Routing area updating and paging for non-GPRS services procedure collision If a GPRS MS in MS operation mode B receives a paging for non-GPRS services before the normal or periodic routing area updating procedure has been completed, the MS shall progress the routing area updating procedure and respond to the paging for non-GPRS services when it has completed the routing area updating procedure or aborted the procedure for other reasons. In cases b, c, d, e, g with detach type "re-attach required" or "re-attach not required" with GMM cause other than #2 "IMSI unknown in HLR", and i, the MS shall stop any ongoing transmission of user data. In cases b, c, d, i and j the MS shall proceed as follows: Timer T3330 shall be stopped if still running. For the cases b, c, d, and i when the "Extended wait time" is ignored, if the routing area updating request is not for initiating a PDN connection for emergency bearer services, the routing area updating attempt counter shall be incremented. If the routing area updating attempt counter is less than 5, and the stored RAI is equal to the RAI of the current serving cell and the GPRS update status is equal to GU1 UPDATED and the TIN does not indicate "GUTI": - the MS shall keep the GPRS update status to GU1 UPDATED and changes state to GMM-REGISTERED.NORMAL-SERVICE. The MS shall start timer T3311. - If in addition the ROUTING AREA UPDATE REQUEST message indicated "periodic updating", none of the other reasons for initiating the routing area updating procedure listed in subclause 4.7.5.1 was applicable, and the ROUTING AREA UPDATE REQUEST message did not include a Requested READY timer value IE, T3324 value IE, T3312 extended value IE or Extended DRX parameters IE, - in Iu mode, the timer T3311 may be stopped when the MS enters PMM-CONNECTED mode; - in A/Gb mode, the timer T3311 may be stopped when the READY timer is started. - If timer T3311 expires the routing area updating procedure is triggered again. If the routing area updating attempt counter is less than 5, and the stored RAI is different to the RAI of the current serving cell or the GPRS update status is different to GU1 UPDATED or the TIN indicates "GUTI": - for the cases i and j, the routing area updating procedure is started, if still necessary, when timer T3346 expires or is stopped. - for the cases b, c, d, and i when the "Extended wait time" is ignored, if the routing area updating request is not for initiating a PDN connection for emergency bearer services, the MS shall start timer T3311, shall set the GPRS update status to GU2 NOT UPDATED and changes state to GMM-REGISTERED.ATTEMPTING-TO-UPDATE. - If S1 mode is supported by the MS, the MS shall in addition handle the EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the abnormal case when a normal or periodic tracking area updating procedure fails and the tracking area updating attempt counter is less than 5 and the EPS update status is different from EU1 UPDATED. If the routing area updating attempt counter is greater than or equal to 5: - the MS shall start timer T3302, and shall set the GPRS update status to GU2 NOT UPDATED. An MS which is a GPRS MS in MS operation modes C shall also delete the list of equivalent PLMNs. The MS shall also enter the state GMM-REGISTERED.ATTEMPTING-TO-UPDATE or optionally the GMM-REGISTERED.PLMN-SEARCH state (see subclause 4.2.5.1.8) in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. - If S1 mode is supported by the MS, the MS shall in addition handle the EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the abnormal case when a normal or periodic tracking area updating procedure fails and the tracking area updating attempt counter is equal to 5. - If the MS does not enter the state GMM-REGISTERED.PLMN-SEARCH, then - a GPRS MS operating in MS operation mode A in network operation mode I shall proceed with appropriate MM specific procedures. If the MS operating in MS operation mode A is in an ongoing circuit-switched transaction, it shall initiate the appropriate MM specific procedure after the circuit-switched transaction has been released. The MM sublayer of the MS operating in MS operation mode A shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered; - if the update type is "periodic updating", a GPRS MS operating in MS operation mode B in network operation mode I shall proceed with appropriate MM specific procedures. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered; and - a GPRS MS operating in MS operation mode A or B in network operation mode II which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, and which did not perform a successful generic location updating procedure since the last intersystem change from S1 mode to A/Gb or Iu mode shall proceed with appropriate MM specific procedures. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.5.1.5 |
4,922 | 4.7.5 Application of PCC in the Evolved Packet System | The Evolved Packet System applies the PCC framework as defined in TS 23.203[ Policy and charging control architecture ] [6] for QoS policy and charging control. PCC functionality is present in the AF, PCEF and PCRF. An EPS needs to both PCEF and PCRF functionality to enable dynamic policy and charging control by means of installation of PCC rules based on user and service dimensions. However, an EPS may only PCEF functionality in which case it shall static policy and charging control. NOTE: The local configuration of PCEF static policy and charging control functionality is not subject to standardization. The PCEF static policy and control functionality is not based on subscription information. The following applies to the use of dynamic policy and charging control in EPS: - The service level (per SDF) QoS parameters are conveyed in PCC rules (one PCC rule per SDF) over the Gx reference point. The service level QoS parameters consist of a QoS Class Identifier (QCI) Allocation and Retention Priority (ARP) and authorised Guaranteed and Maximum Bit Rate values for uplink and downlink. The QCI is a scalar that represents the QoS characteristics that the EPS is expected to provide for the SDF. ARP is an indicator of the priority for the SDF that is used to decide about the assignment of resources due to resource limitations. The service level ARP assigned by PCRF in a PCC rule may be different from the bearer level ARP stored in subscription data; - The set of standardized QCIs and their characteristics that the PCRF in an EPS can select from is provided in TS 23.203[ Policy and charging control architecture ] [6]. It is expected that the PCRF selects a QCI in such a way that the IP-CAN receiving it can support it; - It is not required that an IP-CAN supports all standardized QCIs; - In the case of IP address configuration subsequent to initial attachment, i.e. through DHCP mechanism to complete the IP address configuration, the PDN GW/PCEF shall notify the PCRF of the UE's IP address by means of an IP-CAN Session Modification procedure or IP-CAN Session Establishment procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] when it is assigned. If the PCRF response leads to an EPS bearer modification the PDN GW should initiate a bearer update procedure; - For local breakout, the visited network has the capability to reject the QoS authorized by the home network based on operator policies. The following applies regardless of whether dynamic or static policy and charging control is used in EPS: - For E-UTRAN the value of the ARP of an EPS bearer is identical to the value of the ARP of the SDF(s) mapped to that EPS bearer; - For the same UE/PDN connection: SDFs associated with different QCIs or with the same service-level QCI but different ARP shall not be mapped to the same EPS bearer; - The bearer level QCI of an EPS bearer is identical to the value of the QCI of the SDF(s) mapped to that EPS bearer. | 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.7.5 |
4,923 | 4.4.4.9 Abnormal cases on the mobile station side | The different abnormal cases that can be identified are the following: a) Access barred because of access class control or EAB The location updating procedure is not started. The mobile station stays in the current serving cell and applies normal cell reselection process. The procedure is started as soon as possible and if still necessary (when the barred state is ended or because of a cell change). b) The answer to random access is an IMMEDIATE ASSIGNMENT REJECT message (A/Gb mode only) The location updating is not started. The mobile station stays in the chosen cell and applies normal cell selection process. The waiting timer T3122 is reset when a cell change occurs. The procedure is started as soon as possible after T3122 timeout if still necessary. c) Random access failure (A/Gb mode only) Timer T3213 is started. When it expires the procedure is attempted again if still necessary. NOTE 1: As specified in 3GPP TS 45.008[ None ] [34], a cell reselection then takes place, with return to the cell inhibited for 5 seconds if there is at least one other suitable cell. Typically the selection process will take the mobile station back to the cell where the random access failed after 5 seconds. If at the expiry of timer T3213 a new cell has not been selected due to the lack of valid information (see 3GPP TS 45.008[ None ] [34]), the mobile station may as an option delay the repeated attempt for up to 8 seconds to allow cell re-selection to take place. In this case the procedure is attempted as soon as a new cell has been selected or the mobile station has concluded that no other cell can be selected. If random access failure occurs for two successive random access attempts for location updating the mobile station proceeds as specified below. d) RR connection failure The procedure is aborted and the mobile station proceeds as specified below. e) T3210 timeout The procedure is aborted, the RR connection is aborted and the MS proceeds as specified below. f) RR release without "Extended Wait Time" received from lower layers before the normal end of procedure The procedure is aborted and the mobile station proceeds as specified below, except in the following implementation option case f.1. f.1) RR release in Iu mode (i.e. RRC connection release) with, for example, cause "Normal", "User inactivity" or "Directed signalling connection re-establishment" (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) The location updating procedure shall be initiated again, if the following conditions apply: i) The original location updating procedure was initiated over an existing RRC connection; and ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the CS signalling connection (e.g. CS authentication procedures, see subclause 4.3.2), were received after the LOCATION UPDATING REQUEST message was transmitted. NOTE 2: The RRC connection release cause that triggers the re-initiation of the location updating procedure is implementation specific. g) Location updating reject, other causes than those treated in subclause 4.4.4.7, and cases of MM cause values #22 and #25, if considered as abnormal cases according to subclause 4.4.4.7 Upon reception of the cause codes #22, # 95, # 96, # 97, # 99 and # 111 the MS should set the location update attempt counter to 4. The MS waits for release of the RR connection as specified in subclause 4.4.4.8. The MS shall proceed as described below. h) RR connection establishment failure without "Extended Wait Time" received from lower layers (Iu mode only) The procedure is aborted and the mobile station proceeds as specified below. NOTE 3: Case h) covers all cases when the signalling connection cannot be established, including random access failure and access reject. As the RRC protocol has error specific retransmission mechanisms (see 3GPP TS 25.331[ None ] [23c]), there is no need to distinguish between the different error cases within MM. i) "Extended wait time" for CS domain from the lower layers The MS shall abort the location updating procedure and stop timer T3210 if still running. If the LOCATION UPDATING REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall start timer T3246 with the "Extended wait time" value and reset the location update attempt counter. In other cases the MS shall ignore the "Extended wait time". Additionally, the MS shall set the MM update status to U2 NOT UPDATED and change to state MM IDLE sub-state ATTEMPTING TO UPDATE. The MS stays in the current serving cell and applies normal cell reselection process. The location updating procedure is started, if still necessary, when timer T3246 expires or is stopped, and the MS proceeds as specified below. j) Timer T3246 is running The location updating procedure shall not be initiated unless the MS is establishing an emergency call or the MS is an MS configured to use AC11 – 15 in selected PLMN. The MS stays in the current serving cell and applies normal cell reselection process. The location updating procedure is started, if still necessary, when timer T3246 expires or is stopped. In cases d) to i) (except in the case f.1 and except in the case i) when timer T3246 is started) above, and, for repeated failures as defined in c) above, the mobile station proceeds as follows. Timer T3210 is stopped if still running. The RR Connection is aborted in case of timer T3210 timeout. The location update attempt counter is incremented. The next actions depend on the Location Area Identities (stored and received from the BCCH of the current serving cell) and the value of the location update attempt counter. – the update status is UPDATED, and the stored LAI is equal to the one received on the BCCH from the current serving cell and the location update attempt counter is smaller than 4: The mobile station shall keep the update status to UPDATED, the MM IDLE sub-state after the RR connection release is NORMAL SERVICE. The mobile station shall memorize the location updating type used in the location updating procedure. It shall start timer T3211 when the RR connection is released. When timer T3211 or T3246 expires the location updating procedure is triggered again with the memorized location updating type; – either the update status is different from UPDATED, or the stored LAI is different from the one received on the BCCH from the current serving cell, or the location update attempt counter is greater or equal to 4: When the RR connection is released the mobile station shall delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM, and set the update status to NOT UPDATED. A mobile station which is not a GPRS MS shall also delete the list of equivalent PLMNs. The mobile station shall enter the MM IDLE sub-state ATTEMPTING TO UPDATE (see subclause 4.2.2.2 for the subsequent actions) or optionally the MM IDLE sub-state PLMN SEARCH (see subclause 4.2.1.2) in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If the location update attempt counter is smaller than 4, the mobile station shall memorize that timer T3211 is to be started when the RR connection is released, otherwise it shall memorize that timer T3212 is to be started when the RR connection is released. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.4.9 |
4,924 | 16a.4.4 ACA Command | The ACA command, defined in Diameter Base (IETF RFC 6733 [111]), is indicated by the Command-Code field set to 271 and the ‘R’ bit cleared in the Command Flags field., It is sent by the Diameter server to the GGSN/P-GW in response to the ACR command. 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: <AC-Answer> ::= < Diameter Header: 271, PXY > < Session-Id > { Result-Code } { Origin-Host } { Origin-Realm } { Accounting-Record-Type } { Accounting-Record-Number } [ Acct-Application-Id ] [ User-Name ] [ Event-Timestamp ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] [ Origin-State-Id ] [ NAS-Identifier ] [ NAS-IP-Address ] [ NAS-IPv6-Address ] [ NAS-Port ] [ NAS-Port-Id ] [ NAS-Port-Type ] [ Service-Type ] [ Accounting-Realtime-Required ] [ Acct-Interim-Interval ] * [ Class ] * [ 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.4 |
4,925 | 4.22 ATSSS Procedures 4.22.1 General | This clause specifies the procedures that enable the support of Access Traffic Steering, Switching and Splitting (ATSSS), as defined in clause 5.32 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. These procedures can be applied only by ATSSS-capable UEs and 5GC networks. The key enabler of ATSSS is the Multi Access-PDU (MA PDU) Session. As specified in clause 5.32.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], a MA PDU Session is a PDU Session associated with two independent N3/N9 tunnels between the PSA and RAN/AN and with multiple access types, i.e. with one 3GPP access and one non-3GPP access both connected to 5GC. A MA PDU Session may also be a PDU Session associated with one 3GPP access connected to EPC and one non-3GPP access connected to 5GC, or a PDU Session associated with one non-3GPP access connected to EPC and one 3GPP access connected to 5GC. The traffic of a MA PDU Session can be transferred over 3GPP access, or over non-3GPP access, or over both accesses. How the traffic is transferred over the available accesses of a MA PDU Session is governed by the applicable policy created by the 5GC network. The UE determines whether ATSSS is supported by the network based on the MA PDU Session Support indicator provided by the AMF during the Registration procedures, as specified in clause 4.22.9.1. If the network does not support ATSSS, the UE shall not initiate the following procedures in this network: - establishment of a MA PDU Session (clause 4.22.2); - establishment of a PDU Session with "MA PDU Network-Upgrade Allowed" indication (clause 4.22.3); - addition of user-plane resources over one access for an existing MA PDU Session, which has been established over the other access in a different network (clause 4.22.7); or - PDU Session Modification with Request Type of "MA PDU request" or with "MA PDU Network-Upgrade Allowed" indication after moving from EPC to 5GC (clause 4.22.6.3). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22 |
4,926 | 10.5.1.2 Ciphering Key Sequence Number | In a GSM authentication challenge, the purpose of the Ciphering Key Sequence Number information element is to make it possible for the network to identify the ciphering key Kc which is stored in the mobile station without invoking the authentication procedure. The ciphering key sequence number is allocated by the network and sent with the AUTHENTICATION REQUEST or AUTHENTICATION AND CIPHERING REQUEST message to the mobile station where it is stored together with the calculated keys, e.g. Kc, CK, IK, Kc128, Kint. The Ciphering Key Sequence Number information element is coded as shown in figure 10.5.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . In a UMTS authentication challenge, the purpose of the Ciphering Key Sequence Number information element is to make it possible for the network to identify the ciphering key CK and integrity key IK which are stored in the MS without invoking the authentication procedure. CK and IK form a Key Set Identifier (KSI) (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]) which is encoded the same as the CKSN and is therefore included in the CKSN field. The ciphering key sequence number is a type 1 information element. Figure 10.5.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Ciphering Key Sequence Number information element Table 10.5.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Ciphering Key Sequence Number information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.1.2 |
4,927 | 6.41.2.10 Multicast/Broadcast | The operator of a hosting network shall support a mechanism allowing different service providers of localized services to disseminate their services and content over broadcast/multicast transport. This mechanism should also provide means to include diverse content in the same transmission, e.g., to include advertisements with other content, or to include multiple content in the same media delivered to the user. A hosting network shall provide multicast and broadcast services in an energy efficient manner to UEs receiving this service. A hosting network shall support resource efficient content delivery through multicast/broadcast. A hosting network shall support a mechanism to provide low latency signalling for efficient content delivery to many UEs. Subject to home operator policy, a hosting network shall be able to prioritize specific multicast and broadcast services for local access over home routed access, even if the same service is available in both networks. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.41.2.10 |
4,928 | 5.2.6.26.6 Nnef_EASDeployment_Subscribe service operation | Service operation name: Nnef_EASDeployment_Subscribe Description: provided by the NEF for NF consumers to explicitly subscribe the notification of changes of EAS Deployment Information. Inputs, Required: Event ID, Notification Target Address(+Notification Correlation ID). Inputs, Optional: DNN, S-NSSAI, Application Identifier, Internal Group Identifier. Outputs, Required: Result Indication. When the subscription is accepted: Subscription Correlation ID (reference of the subscription). Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.26.6 |
4,929 | 5.4.3.6 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure. Upon detection of a lower layer failure before the IDENTITY RESPONSE is received, the network shall abort any ongoing 5GMM procedure. b) Expiry of timer T3570. The network shall, on the first expiry of the timer T3570, retransmit the IDENTITY REQUEST message and reset and restart the timer T3570. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3570, the network shall abort the identification procedure and any ongoing 5GMM procedure. c) Collision of an identification procedure with a registration procedure for initial registration. If the network receives a REGISTRATION REQUEST message indicating either "initial registration" or "emergency registration" in the 5GS registration type IE before the ongoing identification procedure has been completed and no registration procedure is pending on the network (i.e. no REGISTRATION ACCEPT/REJECT message has still to be sent as an answer to a REGISTRATION REQUEST message), the network shall proceed with the registration procedure for initial registration. d) Collision of an identification procedure with a registration procedure for initial registration when the identification procedure has been caused by a registration procedure for initial registration. If the network receives a REGISTRATION REQUEST message indicating either "initial registration" or "emergency registration" in the 5GS registration type IE before the ongoing identification procedure has been completed and a registration procedure for initial registration is pending (i.e. a REGISTRATION ACCEPT/REJECT message has to be sent as an answer to an earlier REGISTRATION REQUEST message), then: - If one or more of the information elements in the REGISTRATION REQUEST message differ from the ones received within the previous REGISTRATION REQUEST message, the network shall proceed with the new registration procedure for initial registration; or - If the information elements do not differ, then the network shall not treat any further this new REGISTRATION REQUEST message. e) Collision of an identification procedure with a registration procedure for mobility and periodic registration update. If the network receives a REGISTRATION REQUEST message indicating either "mobility registration updating" or "periodic registration updating" in the 5GS registration type IE before the ongoing identification procedure has been completed, the network shall progress both procedures. f) Collision of an identification procedure with a UE initiated de-registration procedure. If the network receives a DEREGISTRATION REQUEST message with "switch off" indication in the De-registration type IE before the ongoing identification procedure has been completed, the network shall abort the identification procedure and shall progress the UE-initiated de-registration procedure; Else the network shall complete the identification procedure and shall respond to the UE-initiated de-registration procedure as described in subclause 5.5.2.2. | 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.6 |
4,930 | 9.6.1.3 TDD-FDD CA with FDD PCell | The following requirements apply to UE Category ≥5. For TDD-FDD CA with FDD PCell with 2 DL CC, for the parameters specified in Table 9.6.1.3-1 and Table 9.6.1.3-2, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell reported shall be such that wideband CQIPCell – wideband CQISCell ≥ 2 for more than 90% of the time. Table 9.6.1.3-1: Parameters for PUCCH 1-0 static test on multiple cells (TDD-FDD CA with FDD PCell, 2 DL CA) Table 9.6.1.3-2: PUCCH 1-0 static test (TDD-FDD CA with FDD PCell, 2 DL CA) The following requirements for 3DL CA apply to UE Category ≥5. For TDD-FDD CA with FDD PCell with 3 DL CC, for the parameters specified in Table 9.6.1.3-3 and Table 9.6.1.3-4, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell1 and SCell2 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 for more than 90% of the time. The following requirements for 4DL CA apply to UE Cateogry ≥8. For TDD-FDD CA with FDD PCell with 4 DL CC, for the parameters specified in Table 9.6.1.3-3 and Table 9.6.1.3-5, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell1 and SCell2, and SCell1 and SCell3 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 wideband CQISCell1 – wideband CQISCell3 ≥ 2 for more than 90% of the time. Table 9.6.1.3-3: PUCCH 1-0 static test on multiple cells (TDD-FDD CA with FDD PCell, 3 and 4 DL CA) Table 9.6.1.3-4: PUCCH 1-0 static test (TDD-FDD CA with FDD PCell, 3 DL CA) Table 9.6.1.3-5: PUCCH 1-0 static test (TDD-FDD CA with FDD PCell, 4 DL CA) The following requirements for 5DL CA apply to UE Category 8 and ≥11. For TDD-FDD CA with FDD PCell with 5 DL CC, for the parameters specified in Table 9.6.1.3-6 and Table 9.6.1.3-7, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell1 and SCell2, SCell1 and SCell3, and SCell 1 and SCell 4 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 wideband CQISCell1 – wideband CQISCell3 ≥ 2 wideband CQISCell1 – wideband CQISCell4 ≥ 2 for more than 90% of the time. Table 9.6.1.3-6: PUCCH 1-0 static test on multiple cells (TDD-FDD CA with FDD PCell, 5 DL CA) Table 9.6.1.3-7: PUCCH 1-0 static test (TDD-FDD CA with FDD PCell, 5 DL CA) The following requirements for 6DL CA apply to UE Category 8 and ≥11. For TDD-FDD CA with FDD PCell with 6 DL CC, for the parameters specified in Table 9.6.1.3-8 and Table 9.6.1.3-9, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell1 and SCell2, SCell1 and SCell3, SCell 1 and SCell 4, and SCell 1 and SCell 5 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 wideband CQISCell1 – wideband CQISCell3 ≥ 2 wideband CQISCell1 – wideband CQISCell4 ≥ 2 wideband CQISCell1 – wideband CQISCell5 ≥ 2 for more than 90% of the time. Table 9.6.1.3-8: PUCCH 1-0 static test on multiple cells (TDD-FDD CA with FDD PCell, 6 DL CA) Table 9.6.1.3-9: PUCCH 1-0 static test (TDD-FDD CA with FDD PCell, 6 DL CA) The following requirements for 7DL CA apply to UE Category 8 and ≥11. For TDD-FDD CA with FDD PCell with 7 DL CC, for the parameters specified in Table 9.6.1.3-10 and Table 9.6.1.3-11, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell1 and SCell2, SCell1 and SCell3, SCell 1 and SCell 4, SCell 1 and SCell 5, SCell 1 and SCell 6 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 wideband CQISCell1 – wideband CQISCell3 ≥ 2 wideband CQISCell1 – wideband CQISCell4 ≥ 2 wideband CQISCell1 – wideband CQISCell5 ≥ 2 wideband CQISCell1 – wideband CQISCell6 ≥ 2 for more than 90% of the time. Table 9.6.1.3-10: PUCCH 1-0 static test on multiple cells (TDD-FDD CA with FDD PCell, 7 DL CA) Table 9.6.1.3-11: PUCCH 1-0 static test (TDD-FDD CA with FDD PCell, 7 DL CA) | 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.6.1.3 |
4,931 | 4.5.8.1 Maximum carrier transmit power | a) This measurement provides the maximum carrier transmit power in the measurement granularity interval. b) SI c) This measurement is obtained by retaining the maximum value of the total carrier power transmitted in the cell within the measurement granularity period. The power includes all radio power transmitted, included common channels, traffic channels, control channels. The value is expressed in dBm. d) Float in dBm. e) CARR.MaxTxPwr 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.5.8.1 |
4,932 | K.2 Operation of isolated public safety networks using a Local EPC K.2.1 General Description | This approach to the provision of isolated operation (e.g. when there is no S1 connectivity to the macro EPC) assumes that the IOPS-capable eNodeB is co-sited with, or can reach, a Local EPC instance which is used in IOPS mode. The Local EPC instance includes at least MME, SGW/PDN GW and HSS functionality. A PLMN identity is dedicated to IOPS mode of operation and is broadcast in System Information by the eNodeB when IOPS mode is in operation. Only authorized IOPS-enabled UEs can access a PLMN indicated as an IOPS PLMN. Support of application services over the IOPS network will be based upon the LTE-Uu radio interface and EPS bearer services supported by the Local EPC. An IOPS network will provide local connectivity services, i.e. for an IP PDN type, IP address assignment and local routing in the IOPS network. For an IP PDN type, During the attachment procedure to the local EPC a local IP address is assigned to the UE as per the standard procedure when attaching to a Macro EPC. The Local EPC acts as a router among the UEs locally attached to the same IOPS network. When operating in IOPS mode IOPS-enabled UEs only use the appropriate USIM credentials defined in the UICC, i.e. those defined exclusively for use in an IOPS PLMN. | 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") | K.2 |
4,933 | 4.4.2.1.2 UE leaving state 5GMM-DEREGISTERED | If the UE is capable of registration over a single access only, the UE shall mark the 5G NAS security context on the USIM or in the non-volatile memory as invalid when the UE initiates an initial registration procedure as described in subclause 5.5.1.2 or when the UE leaves state 5GMM-DEREGISTERED for any other state except 5GMM-NULL. If the UE is capable of registration over both 3GPP access and non-3GPP access and was last registered on the same PLMN over both 3GPP access and the non-3GPP access, the UE in the state 5GMM-DEREGISTERED over both 3GPP access and non-3GPP access shall mark the 5G NAS security contexts in record 1 of the 3GPP access and the non-3GPP access on the USIM or in the non-volatile memory as invalid when the UE initiates an initial registration procedure over either 3GPP access or non-3GPP access as described in subclause 5.5.1.2 or when the UE leaves state 5GMM-DEREGISTERED for any other state except 5GMM-NULL over either 3GPP access or non-3GPP access. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.2.1.2 |
4,934 | A.27 Use case of UE IP throughput Distribution | Operator may want to monitor the information of the user experience of the network during the monitoring period. In some scenarios which the network load becomes very high in short time, although the average IP thoughput measured during the monitoring period is satisfactory. the user experience may not be always satisfactory because the UE IP throughput may significantly vary during the monitoring period. It would be useful for operators to know the distribution information on the UE IP throughput. This distribution information could also help in the root cause analysis in case when the application problems are caused by load bursts. The UE IP throughput distribution information could show the mean throughput and the peak throughput. The median throughput is within the range of the bin that got the highest number of samples and the peak throughput is within the range of the “highest” bin that got >0 samples. With the information of UE IP throughput distribution, operator may consider to optimize the network if needed. | 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.27 |
4,935 | 28.3.2.3.2 Format of NRF FQDN | The NRF FQDN for an NRF in an operator's PLMN shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the PLMN in which the NRF is located with the label "nrf." as described below: - nrf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org If the SUPI of the UE for construction of the NRF FQDN is of a type other than IMSI (e.g., NSI such as [email protected]), the NRF FQDN of an NRF in an operator's SNPN, if not pre-configured in the NF, shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the SNPN in which the NRF is located with the label "nrf."e.g. - nrf.operator.com : - nrf.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org (for SNPN scenarios where NID is available) If the SUPI of the UE for construction of the NRF FQDN is of type IMSI, the NID is not available to the NF. Therefore, the NRF FQDN of an NRF in an operator’s SNPN, if not pre-configured in the NF, is that of the NRF of the PLMN that owns the MCC and MNC as described below: - nrf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.3.2 |
4,936 | 21.2.5 Per-slice QoE Measurement | When a service is provided within a configured slice, the QoE Measurement for this service type can also be configured together with the corresponding slice scope, so that the user experience of this service can also be evaluated on a per-slice basis. Multiple QoE measurement configurations can be configured for the same service type, and each configuration can pertain to different slices, where each QoE measurement configuration is identified with a QoE reference. The UE includes the network slice identifier inside the QoE report container when reporting QoE measurement reports. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 21.2.5 |
4,937 | 4.23.5.4 SMF triggered I-SMF selection or removal | Figure 4.23.5.4-1: SMF triggered I-SMF selection or removal 1. The PCF sends to the SMF PCC rule(s) which may include DNAI(s) for the PDU sessions by invoking Npcf_SMPolicyControl_UpdateNotify service operation. Based on the received DNAI(s), the SMF may subscribe to UE mobility event notification from the AMF (e.g. UE moves into or out of Area of Interest corresponding to the received DNAI(s)). The SMF may determine the target DNAI(s) which are applicable to the current UE location and which can be based on common DNAI (if applicable) as described in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. Then the SMF may decide a target DNAI finally. NOTE: It is also possible that the SMF determines that there is no any target DNAI can be used based on PCC rule(s), e.g. when the updated PCC rules removes previously provided DNAI(s). 2. The SMF invokes a Nsmf_PDUSession_SMContextStatusNotify service operation (or Nsmf_PDUSession_StatusNotify) in the following cases: - if the SMF (or the associated old I-SMF) cannot serve the target DNAI, or - if an I-SMF is used for the PDU Session and the SMF decides that the DNAI currently served by I-SMF is no longer be used for the PDU Session anymore hence the existing I-SMF is not needed, or - if an I-SMF is used for the PDU Session and the SMF decides that the SMF itself can serve the target DNAI hence the existing I-SMF is not needed. The content of the message includes the target DNAI information. The target DNAI information which indicates that the I-SMF selection or removal is expected and may include a target DNAI. This is to trigger the AMF to (re)select a suitable I-SMF, or remove the existing I-SMF (if the AMF decides that the SMF can serve the Target DNAI, or the AMF receive a target DNAI information without including target DNAI) for the PDU Session. The target DNAI is used for selecting (I-)SMF, which controls UPF connecting to that DNAI. If there is an I-SMF serving the PDU session, the SMF invokes Nsmf_PDUSession_StatusNotify and then the I-SMF invokes Nsmf_PDUSession_SMContextStatusNotify message to send the target DNAI information for existing PDU session to AMF. 3. If the I-SMF selection or removal is expected, the AMF selects a new I-SMF which can serve the target DNAI or remove the existing I-SMF (if the AMF decides that the SMF can serve the Target DNAI, or if the AMF receiveS a target DNAI information without including target DNAI) for the existing PDU Session as described in clause 5.34.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 4. The AMF sends a Nsmf_PDUSession_CreateSMContext Request to the new I-SMF as described in step 3 of clause 4.23.4.3, or to the SMF as described in step 10 of clause 4.23.4.3, with the following enhancement: The AMF includes target DNAI received from SMF in the message. When the UE is in CONNECTED state the AMF also include indication of no NG-RAN change. 5. The procedure described in clauses 4.23.4.3 (case: I-SMF insertion or I-SMF change) starting from step 4 takes place with the following difference: In step 4a, the (target) new I-SMF sends the indication of no NG-RAN change to the old I-SMF or SMF as it is received from AMF. In step 4b, when the old I-SMF or SMF receives indication of no NG-RAN change it include the additional Downlink Tunnel Info of NG-RAN in the SM context of the PDU Session. In step 5, the I-SMF selects the I-UPF based on target DNAI. In step 6, the target I-SMF should reuse the downlink Tunnel Info of serving RAN node if received from old I-SMF/SMF as described in clause 4.23.4.3. In step 9, if the new I-SMF receives the Downlink Tunnel Info of NG-RAN, the N2 SM information includes PDU Session Resource Modification message. The procedure described in clause 4.23.4.3 (case: I-SMF removal) starting from step 11 takes place with the following difference: In step 11a, the SMF sends an indication of no NG-RAN change to the old I-SMF as it received from AMF. In step 11b, when the old I-SMF receives indication of no NG-RAN change it include the additional Downlink Tunnel Info of NG-RAN in the SM context of the PDU Session. In step 12, the SMF selects a new I-UPF based on target DNAI. In step 16, if the SMF receives the Downlink Tunnel Info of NG-RAN, the N2 SM information includes PDU Session Resource Modification message. If the UE is in IDLE state the step 17-21 are skipped. Steps 17a and 17b are still performed to release the old I-SMF. 6. [Conditional] In the case that I-SMF insertion or I-SMF change is performed in step 5, the PSA and UL CL/BP controlled by I-SMF is inserted as described from steps 2 to 11 in figure 4.23.9.1-1 with the following difference: In step 2, the I-SMF selects a new PDU Session Anchor (PSA2) based on the target DNAI received in step 4. For the case of I-SMF removal, the PSA and UL CL/BP controlled by SMF is inserted as described from steps 2 to 8 in Figure 4.3.5.4-1 with the following difference: In step 2, the SMF selects a new PDU Session Anchor (PSA2) based on the target DNAI if received in step 4. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.5.4 |
4,938 | Update Bearer Request | The direction of this message shall be from PGW to SGW and/or from SGW to MME/S4-SGSN, and/or from PGW to TWAN/ePDG (see Table 6.1-1). For GTP based S5/S8, the Update Bearer Request shall be sent by the PGW to the SGW and forwarded to the MME as part of the following procedures: - PGW Initiated Bearer Modification with Bearer QoS Update - HSS Initiated Subscribed QoS Modification - PGW Initiated Bearer Modification without Bearer QoS Update - UE Request Bearer Resource Modification procedure (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23]) - UE requested bearer resource allocation procedure (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23]) - P-CSCF restoration for 3GPP access (see 3GPP TS 23.380[ IMS Restoration Procedures ] [61]) - USS UAV Authorization/Authentication (UUAA) procedure during Attach or UE-requested PDN connectivity procedures (see 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [90]) - USS initiated UAV Re-authorization procedure in EPS (see 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [90]) - Secondary DN authentication and authorization in EPS Interworking case (see clause 5.17.2.5 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [82] and Annex H of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [83]) The message shall also be sent on the S5/S8 interface by the PGW to the SGW and on the S4 interface by the SGW to the SGSN as part of the following procedures: - PGW Initiated EPS Bearer Modification - Execution part of MS-Initiated EPS Bearer Modification - SGSN-Initiated EPS Bearer Modification Procedure using S4 - P-CSCF restoration for 3GPP access (see 3GPP TS 23.380[ IMS Restoration Procedures ] [61]) The message shall also be sent on the S2a/S2b interface by the PGW to the TWAN/ePDG as part of the following procedures: - PGW Initiated Bearer Modification - HSS Initiated Subscribed QoS Modification - P-CSCF restoration for WLAN access (see 3GPP TS 23.380[ IMS Restoration Procedures ] [61]) For PMIP based S5/S8, the Update Bearer Request shall be sent on the S11 interface by the SGW to the MME and on the S4 interface by the SGW to the SGSN. The message shall also be sent on the S5/S8 or S2a/S2b interface by the PGW to the SGW or to the TWAN/ePDG and on the S11/S4 interface by the SGW to the MME/S4-SGSN as part of the Network-initiated IP flow mobility procedure or the UE-initiated IP flow mobility procedure, as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71]. Table -1 specifies the presence requirements and the conditions of the IEs in the message. Table -1: Information Elements in an Update Bearer Request NOTE: In the case that the procedure was initiated by a UE Requested Bearer Resource Modification Procedure or UE Requested Bearer Resource Allocation Procedure for an E-UTRAN or MS initiated EPS bearer modification procedure, then there will be only one instance of the Bearer Contexts IE in the Update Bearer Request. Table -2: Bearer Context within Update Bearer Request Table 7.2.15-3: Load Control Information within Update Bearer Request Table 7.2.15-4: Overload Control Information within Update Bearer Request Table 7.2.15-5: PGW Change Info within Update Bearer Request | 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 |
4,939 | 4.1.4.2 Maximum RRC connection setup time | This measurement provides the maximum time per establishment cause it takes to establish an RRC connection. GAUGE. This measurement is obtained by monitoring the time intervals for each successful RRC connection establishment between the receipt of a RRCConnectionRequest and the corresponding RRCConnectionSetupComplete message by the eNodeB/RN over the granularity period. The high tide mark of this time will be stored in a gauge, the gauge shall be reinitialised at the beginning of each granularity period. The measurement is split into subcounters per establishment cause, and the possible causes are included in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. Each measurement is an integer value (in milliseconds). The measurement name has the form RRC.ConnEstabTimeMax.Cause where Cause identifies the establishment cause EUtranCellFDD EUtranCellTDD Valid for packet switching. EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.1.4.2 |
4,940 | 4.4.1.3 Ga | The Ga reference point supports interaction between a CDF and a CGF. The following information may flow across this reference point: - CDRs are sent from the CDF to the CGF; - Acknowledgements for these CDRs are returned from the CGF to the CDF. The protocol(s) crossing this reference point shall support the following capabilities: - Near real-time transactions; - Send one or more CDRs in a single request message; - Changeover to secondary destinations (alternate CGFs) in case of the primary CGF not being reachable; - Provide its own reliability mechanisms, e.g. retransmission of charging events, to run also on unreliable transport. This interface application is defined in TS 32.295[ Telecommunication management; Charging management; Charging Data Record (CDR) transfer ] [54]. The content of the CDRs, and the CDR trigger conditions, are specific to the domain / subsystem / service and are detailed in the middle tier TSs. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.1.3 |
4,941 | A.22 Use case of UE Rx–Tx time difference related measurements | UE Rx – Tx time difference measurement can be used to calculate distance distribution between UE and serving eNodeB. It is useful to analyze traffic distribution in geographic area and to do trouble shooting of extending coverage and blind coverage spot. The probability of extending coverage and blind coverage should be analyzed by the ratio of the number of UE Rx – Tx time difference that is larger than or equal to threshold to the total number of it. Threshold is configurable according to the cases to be analyzed, Cases includes dense urban area macro cell, suburban area macro cell and rural area cell.So it is necessary to define the UE Rx–Tx time difference related measurements. For TDD mode, propagation distance of 1Ts is nearly 9.77m. According to optimization experience, several granularity of this measurement is proposed. Minimize granularity of 10Ts is enough to analyze distance distribution for near base station, namely UE Rx–Tx time difference is less than 200Ts. For UE Rx–Tx time difference is larger than 200Ts and less than 1000Ts, the corresponding propagation distance is from 1953m to 9766m, the granularity of 40Ts is enough to do trouble shooting of extending coverage. For UE Rx–Tx time difference is larger than 1000Ts and less than 2000Ts. the granularity is 200Ts. And for UE Rx–Tx time difference is larger than 2000Ts and less than 4096Ts, the granularity is 1048Ts. | 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.22 |
4,942 | 14.4 Decorated NAI | The Decorated NAI shall take the form of a NAI and shall have the form 'homerealm!username@otherrealm' as specified in clause 2.7 of the IETF RFC 4282 [53]. The realm part of Decorated NAI consists of 'otherrealm', see the IETF draft 2486-bisRFC 4282 [53]. 'Homerealm' is the realm as specified in clause 14.2, using the HPLMN ID ('homeMCC' + 'homeMNC)'. 'Otherrealm' is the realm built using the PLMN ID (visitedMCC + visited MNC) of the PLMN selected as a result of WLAN PLMN selection (see 3GPP TS 24.234[ 3GPP system to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3 ] [48]). The username part format of the Root NAI shall comply with IETF RFC 4187 [50] when EAP AKA authentication is used and with IETF RFC 4186 [51], when EAP SIM authentication is used. When the username part of Decorated NAI includes the IMSI, it shall be built following the same steps specified for Root NAI in clause 14.3. The result will be a decorated NAI of the form: "wlan.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org !0<IMSI>@wlan.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org", for EAP AKA authentication and " wlan.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org !1<IMSI>@wlan.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org ", for EAP SIM authentication For example, for EAP AKA authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15) and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71 then the Decorated NAI takes the form wlan.mnc015.mcc234.3gppnetwork.org!0234150999999999@wlan.mnc071.mcc610.3gppnetwork.org. NOTE: the 'otherrealm' specified in the present document is resolved by the WLAN AN. If the WLAN AN does not have access to the GRX, then the WLAN AN should resolve the realm by other means e.g. static look-up table, private local DNS server acting as an authoritative name server for that sub-domain. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 14.4 |
4,943 | 5.8.9.1.8 Reception of an RRCReconfigurationFailureSidelink by the UE | The UE shall perform the following actions upon reception of the RRCReconfigurationFailureSidelink: 1> stop timer T400 for the destination, if running; 1> continue using the configuration used prior to corresponding RRCReconfigurationSidelink message; 1> if UE is in RRC_CONNECTED: 2> perform the sidelink UE information for NR sidelink communication procedure, as specified in 5.8.3.3 or clause 5.10.15 in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1.8 |
4,944 | C.2 Storage of 5GMM information for UEs operating in SNPN access operation mode | The 5GMM information for UEs operating in SNPN access operation mode and not registering or registered for the onboarding service in SNPN are stored according to the following conditions: - if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs, the following 5GMM parameters shall be stored per subscribed SNPN in a non-volatile memory in the ME together with the subscriber identifier associated with the SNPN identity of the SNPN in the "list of subscriber data" configured in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) or with the SUPI from the USIM if no subscriber identifier is configured in the entry of the "list of subscriber data" associated with the SNPN identity and the UE has a valid USIM;and - if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the following 5GMM parameters shall be stored in a non-volatile memory in the ME per: i) the subscribed SNPN together with the subscriber identifier associated with the selected entry in the "list of subscriber data" configured in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) or with the SUPI from the USIM if no subscriber identifier is configured in the selected entry of the "list of subscriber data" configured in the ME and the UE has a valid USIM; or ii) if the UE supports access to an SNPN using credentials from a credentials holder, the PLMN subscription together with the SUPI from the USIM which is associated with the PLMN subscription: a) 5G-GUTI;a1) NID of the registered SNPN; b) last visited registered TAI; c) 5GS update status; d) 5G NAS security context parameters from a full native 5G NAS security context (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]); e) KAUSF and KSEAF (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]); f) UE parameter update counter (see subclause 9.11.3.53A); g) configured NSSAI(s); g1) NSSRG information; g2) S-NSSAI time validity information; g3) S-NSSAI location validity information; g4) network slice usage control information; h) NSSAI inclusion mode(s); i) MPS indicator; j) MCS indicator; k) operator-defined access category definitions; l) network-assigned UE radio capability IDs; m) zero or more instances of signalled URSP (see 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]), each associated with a non-subscribed SNPN, the subscribed SNPN or the HPLMN, which provided the URSP; m1) zero or more instances of pre-configured URSP rules (see 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]), each associated with the subscribed SNPN or the HPLMN, which provided the URSP; n) optionally a non-subscribed SNPN signalled URSP handling indication indicating whether the UE is allowed to accept URSP signalled by non-subscribed SNPNs; o) permanently forbidden SNPNs list; o1) permanently forbidden SNPNs for access for localized services in SNPN; p) temporarily forbidden SNPNs; p1) temporarily forbidden SNPNs for access for localized services in SNPN; q) SOR counter (see subclause 9.11.3.51); r) SOR-CMCI; and s) optionally, the SNPN selection parameters associated with the PLMN subscription (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] subclause 4.9.3.0). The 5GMM information for UEs operating in SNPN access operation mode and registering or registered for the onboarding service in SNPN are stored as follows: a) 5G-GUTI; b) last visited registered TAI; c) 5GS update status; d) 5G NAS security context parameters from a full native 5G NAS security context (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]); e) KAUSF and KSEAF (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]); f) UE parameter update counter (see subclause 9.11.3.53A); g) network-assigned UE radio capability IDs; h) "permanently forbidden SNPNs" list for onboarding services; and i) "temporarily forbidden SNPNs" list for onboarding services. The 5GMM information for UEs operating in SNPN access operation mode are stored according to the following conditions: - if the UE does not support access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the following 5GMM parameters should be stored per subscribed SNPN in a non-volatile memory in the ME together with the subscriber identifier associated with the SNPN identity of the SNPN in the "list of subscriber data" configured in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) or with the SUPI from the USIM if no subscriber identifier is configured in the entry of the "list of subscriber data" associated with the SNPN identity and the UE has a valid USIM; and - if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the following 5GMM parameters should be stored in a non-volatile memory in the ME per: i) the subscribed SNPN together with the subscriber identifier associated with the selected entry in the "list of subscriber data" configured in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) or with the SUPI from the USIM if no subscriber identifier is configured in the selected entry of the "list of subscriber data" configured in the ME and the UE has a valid USIM; or ii) if the UE supports access to an SNPN using credentials from a credentials holder, the PLMN subscription together with the SUPI from the USIM which is associated with the PLMN subscription: a) allowed NSSAI(s). If the 5GMM parameters are associated with the PLMN subscription, then the 5GMM parameters can only be used if the SUPI from the USIM which is associated with the selected PLMN subscription matches the SUPI stored in the non-volatile memory; else the UE shall delete the 5GMM parameters. If the 5GMM parameters are associated with the subscribed SNPN of the entry in the "list of subscriber data", then the 5GMM parameters can only be used if the subscriber identifier of the selected entry of the "list of subscriber data" matches the subscriber identifier stored in the non-volatile memory or if the subscriber identifier from the USIM matches the subscriber identifier stored in the non volatile memory, no subscriber identifier is configured in the selected entry of the "list of subscriber data" configured in the ME and the UE has a valid USIM. Each configured NSSAI consists of S-NSSAI(s) stored together with an SNPN identity, if it is associated with an SNPN. A configured NSSAI may be associated with NSSRG information, S-NSSAI time validity information, S-NSSAI location validity information, NSAG information and network slice usage control information. Each NSSAI inclusion mode is associated with an SNPN identity and access type. The MPS indicator is stored together with an SNPN identity of the SNPN that provided it, and is valid in that registered SNPN or equivalent SNPN. The MCS indicator is stored together with an SNPN identity of the SNPN that provided it, and is valid in that registered SNPN or equivalent SNPN. Operator-defined access category definitions are stored together with an SNPN identity of the SNPN that provided them, and are valid in that SNPN or equivalent SNPN. The maximum number of stored operator-defined access category definitions is UE implementation dependent. Each network-assigned UE radio capability ID is stored together with an SNPN identity of the SNPN that provided it as well as a mapping to the corresponding UE radio configuration, and is valid in that SNPN. The UE shall be able to store at least the last 16 received network-assigned UE radio capability IDs. There shall be only one network-assigned UE radio capability ID stored for a given combination of SNPN identity and UE radio configuration and any existing UE radio capability ID shall be deleted when a new UE radio capability ID is added for the same combination of SNPN identity and UE radio configuration. If the UE receives a network-assigned UE radio capability ID with a Version ID value different from the value included in the network-assigned UE radio capability ID(s) stored at the UE for the serving SNPN, the UE may delete these stored network-assigned UE radio capability ID(s). The handling of the SOR-CMCI stored in the non-volatile memory in the ME is specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. The allowed NSSAI(s) can be stored in a non-volatile memory in the ME. Allowed NSSAI consists of S-NSSAI(s) stored together with an SNPN identity, if it is associated with an SNPN. The partially allowed NSSAI(s) can be stored as allowed NSSAI(s) in a non-volatile memory in the ME. Partially allowed NSSAI consists of S-NSSAI(s) and a list of TAs for which the S-NSSAI is allowed, stored together with an SNPN identity, if it is associated with an SNPN. | 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 | C.2 |
4,945 | 6.15a.2.2 Requirements | Subject to operator’s policy, the 5G system shall support subscription policies that define a maximum energy credit limit for services without QoS criteria. Subject to operator’s policy, the 5G system shall support a means to associate energy consumption information with charging information based on subscription policies for services without QoS criteria. Subject to operator’s policy, the 5G system shall support a mechanism to perform energy consumption credit limit control for services without QoS criteria. NOTE 1: The result of the credit control is not specified by this requirement. NOTE 2: Credit control [49] compares against a credit control limit. It is assumed charging events are assigned a corresponding energy consumption and this is compared against a policy of energy credit limit. It is assumed there can be a new policy to limit energy consumption allowed. Subject to operator’s policy, the 5G system shall support a means to define subscription policies and means to enforce the policy that define a maximum energy consumption (i.e. quantity of energy for a specified period of time) for services without QoS criteria. NOTE 3: The granularity of the subscription policies can either apply to the subscriber (all services), or to particular services. The 5G system shall provide a mechanism to include Energy related information as part of charging information. Subject to operator policy and agreement with 3rd party, the 5G system shall provide a mechanism to support the selection of an application server based on energy related information associated with a set of application servers. Subject to user consent and operator policy, 5G system shall be able to provide means to modify a communication service based on energy related information criteria based on subscription policies. Subject to user consent, operator policy and regulatory requirements, the 5G system shall be able to provide means to operate part or the whole network according to energy consumption requirements, which may be based on subscription policies or requested by an authorized 3rd party. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.15a.2.2 |
4,946 | 10.2.1.2 UE in RM-DEREGISTERED state requests a PDU Session for IMS Emergency services | The UE shall first initiate a normal initial registration procedure to register with the 5G network. Upon successful normal registration, the UE initiates the UE requested PDU session establishment procedure to establish a PDU Session to receive emergency services as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. At the time of registration, the security mode control procedure shall be applied to authenticate the UE and setup NAS and AS security. Thus, integrity protection (and optionally ciphering) shall be applied to the emergency bearers as for normal bearers. If authentication fails for any reason, it shall be treated the same way as any registration. Once the IMS Emergency Session is in progress with NAS and AS integrity protection (and optionally ciphering) applied, failure of integrity checking or ciphering (for both NAS and AS) is an unusual circumstance and shall be treated as in the case of a normal bearer. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 10.2.1.2 |
4,947 | 6.4.4 EPS bearer context deactivation procedure 6.4.4.1 General | The purpose of the EPS bearer context deactivation procedure is to deactivate an EPS bearer context or disconnect from a PDN by deactivating all EPS bearer contexts to the PDN. The EPS bearer context deactivation procedure is initiated by the network, and it may be triggered by the UE by means of the UE requested bearer resource modification procedure or UE requested PDN disconnect procedure. In the case of EPS bearer context deactivation with reactivation requested for a PDN connection, if no NAS signalling connection exists, the MME follows the procedures for re-establishing the NAS signalling connection and deactivating the EPS bearer contexts to the PDN with reactivation requested, as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] clauses 5.4.4.1 and 5.10.3 and 3GPP TS 23.380[ IMS Restoration Procedures ] [33] clause 5.4.2.1. If a UE is receiving emergency bearer services from a CSG cell, and the CSG subscription expires or is removed, the MME shall deactivate all non-emergency EPS bearers if any. The MME shall not deactivate the emergency EPS bearers. If a detach is requested by the HSS for a UE that has bearers for emergency services, the MME shall send a DEACTIVATE EPS BEARER CONTEXT REQUEST message to the UE for all bearers that are not allocated for emergency services. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.4 |
4,948 | 6.1 Identification by temporary identities 6.1.1 General | This mechanism allows the identification of a user on the radio access link by means of a temporary mobile subscriber identity (TMSI/P-TMSI). A TMSI /P-TMSI has local significance only in the location area or routing area in which the user is registered. Outside that area it should be a accompanied by an appropriate Location Area Identification (LAI) or Routing Area Identification (RAI) in order to avoid ambiguities. The association between the permanent and temporary user identities is kept by the Visited Location Register (VLR/SGSN) in which the user is registered. The TMSI/P-TMSI, when available, is normally used to identify the user on the radio access path, for instance in paging requests, location update requests, attach requests, service requests, connection re-establishment requests and detach requests. The procedures and mechanisms are described in 3GPP TS 43.020[ Security related network functions ] [8] and TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [9]. The following sections contain a summary of this feature. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1 |
4,949 | 5.5A Operating bands for CA | E-UTRA carrier aggregation is designed to operate in the operating bands defined in Tables 5.5A-1, 5.5A-2, 5.5A-2a, 5.5A-2b, 5.5A-2c, 5.5A-2d, 5.5A-3, 5.5A-4 and 5.5A-5. Table 5.5A-1: Intra-band contiguous CA operating bands Table 5.5A-2: Inter-band CA operating bands (two bands) Table 5.5A-2a: Inter-band CA operating bands (three bands) Table 5.5A-2b: Inter-band CA operating bands (four bands) Table 5.5A-2c: Inter-band CA operating bands (five bands) Table 5.5A-2d: Inter-band CA operating bands (six bands) Table 5.5A-3: Intra-band non-contiguous CA operating bands (with two sub-blocks) Table 5.5A-4: Intra-band non-contiguous CA operating bands (with three sub-blocks) Table 5.5A-5: Intra-band non-contiguous CA operating bands (with four sub-blocks) | 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 | 5.5A |
4,950 | 4.6 Network slicing 4.6.1 General | The 5GS supports network slicing as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. Within a PLMN or SNPN, a network slice is identified by an S-NSSAI, which is comprised of a slice/service type (SST) and a slice differentiator (SD). Inclusion of an SD in an S-NSSAI is optional. A set of one or more S-NSSAIs is called the NSSAI. The following S-NSSAIs and NSSAIs are defined in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]: a) configured NSSAI; b) requested NSSAI; c) allowed NSSAI; d) subscribed S-NSSAIs; e) pending NSSAI; f) alternative S-NSSAIs; and g) partially allowed NSSAI. The following NSSAIs are defined in the present document: a) rejected NSSAI for the current PLMN or SNPN; b) rejected NSSAI for the current registration area; c) rejected NSSAI for the failed or revoked NSSAA; d) rejected NSSAI for the maximum number of UEs reached; e) alternative NSSAI; and f) partially rejected NSSAI. In roaming scenarios, rejected NSSAI for the current PLMN or SNPN, rejected NSSAI for the current registration area, rejected NSSAI for the maximum number of UEs reached, or partially rejected NSSAI includes one or more S-NSSAIs for the current PLMN and also contains a set of mapped S-NSSAI(s). An S-NSSAI included in the rejected NSSAI for the failed or revoked NSSAA is an HPLMN S-NSSAI. In case of a PLMN, a serving PLMN may configure a UE with: a) the configured NSSAI per PLMN; b) NSSRG information if the UE has indicated that it supports the subscription-based restrictions to simultaneous registration of network slices feature; c) network slice usage control information if the UE has indicated it supports the network slice usage control feature; d) S-NSSAI time validity information if the UE has indicated that it supports S-NSSAI time validity information; and e) S-NSSAI location validity information if the UE has indicated that it supports S-NSSAI location validity information. In addition, the HPLMN may configure a UE with a single default configured NSSAI and consider the default configured NSSAI as valid in a PLMN for which the UE has neither a configured NSSAI nor an allowed NSSAI. The support for NSSRG information by the UE and the network, respectively, is optional. NOTE 0: The network slice usage control feature is not supported in roaming scenarios. NOTE 1: The value(s) used in the default configured NSSAI are expected to be commonly decided by all roaming partners, e.g., values standardized by 3GPP or other bodies. In case of an SNPN, the SNPN may configure a UE which is neither registering nor registered for onboarding services in SNPN with: a) a configured NSSAI applicable to the SNPN; b) NSSRG information if the UE has indicated that it supports the subscription-based restrictions to simultaneous registration of network slices feature; c) S-NSSAI time validity information if the UE has indicated that it supports S-NSSAI time validity information; d) network slice usage control information if the UE has indicated it supports the network slice usage control feature; and e) S-NSSAI location validity information if the UE has indicated that it supports S-NSSAI location validity information. In addition, the credential holder may configure a single default configured NSSAI associated with the selected entry of the "list of subscriber data" or the PLMN subscription and consider the default configured NSSAI as valid in a SNPN for which the UE has neither a configured NSSAI nor an allowed NSSAI. If the UE is registering or registered for onboarding services in SNPN, the serving SNPN shall not provide a configured NSSAI to the UE. The support for NSSRG information by the UE and the network, respectively, is optional. The allowed NSSAI and the rejected NSSAI for the current registration area are managed per access type independently, i.e. 3GPP access or non-3GPP access, and is applicable for the registration area. If the UE does not have a valid registration area, the rejected NSSAI for the current registration area is applicable to the tracking area on which it was received. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, the allowed NSSAI, the rejected NSSAI for the current registration area, rejected NSSAI for the failed or revoked NSSAA and rejected NSSAI for the maximum number of UEs reached are applicable to these PLMNs in this registration area. The allowed NSSAI that is associated with a registration area containing TAIs belonging to different PLMNs, which are equivalent PLMNs, can be used to form the requested NSSAI for any of the equivalent PLMNs when the UE is outside of the registration area where the allowed NSSAI was received. When the network slice-specific authentication and authorization procedure is to be initiated for one or more S-NSSAIs in the requested NSSAI or the network slice-specific authentication and authorization procedure is ongoing for one or more S-NSSAIs, these S-NSSAI(s) will be included in the pending NSSAI. When the network slice-specific authentication and authorization procedure is completed for an NSSAI that has been in the pending NSSAI, the S-NSSAI will be moved to the allowed NSSAI or rejected NSSAI depending on the outcome of the procedure. The AMF sends the updated allowed NSSAI to the UE over the same access of the requested S-NSSAI. The AMF sends the updated partially allowed NSSAI to the UE only over the 3GPP access. The AMF sends the updated rejected NSSAI over either 3GPP access or non-3GPP access. The pending NSSAI is managed regardless of access type i.e. the pending NSSAI is applicable to both 3GPP access and non-3GPP access for the current PLMN even if sent over only one of the accesses. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, the pending NSSAI is applicable to these PLMNs in this registration area. The rejected NSSAI for the current PLMN or SNPN is applicable for the whole registered PLMN or SNPN regardless of the access type. The AMF shall only send a rejected NSSAI for the current PLMN when the registration area consists of TAIs that only belong to the registered PLMN. If the UE receives a rejected NSSAI for the current PLMN, and the registration area also contains TAIs belonging to different PLMNs, the UE shall treat the received rejected NSSAI for the current PLMN as applicable to the whole registered PLMN. The rejected NSSAI for the failed or revoked NSSAA includes one or more S-NSSAIs that have failed the network slice-specific authentication and authorization or for which the authorization have been revoked, and are applicable for the whole registered PLMN or SNPN regardless of the access type. The rejected NSSAI for the maximum number of UEs reached is applicable for the whole registered PLMN or SNPN, and the access type over which the rejected NSSAI was sent. The AMF shall send a rejected NSSAI including S-NSSAI(s) with the rejection cause "S-NSSAI not available due to maximum number of UEs reached", when one or more S-NSSAIs are indicated that the maximum number of UEs has been reached. If the timer T3526 associated with the S-NSSAI(s) was started upon reception of the rejected NSSAI for the maximum number of UEs reached, the UE may remove the S-NSSAI(s) from the rejected NSSAI including S-NSSAI(s) with the rejection cause "S-NSSAI not available due to maximum number of UEs reached", if the timer T3526 associated with the S-NSSAI(s) expires. If one or more S-NSSAIs are removed from the rejected NSSAI for the maximum number of UEs reached, the timer T3526 associated with the removed S-NSSAI(s) shall be stopped, if running. The UE shall not stop the timer T3526 if the UE selects an E-UTRA cell connected to EPC. If the UE receives a rejected NSSAI for the maximum number of UEs reached, the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, the UE shall treat the received rejected NSSAI for the maximum number of UEs reached as applicable to these equivalent PLMNs when the UE is in this registration area. If the UE has indicated that the UE supports network slice replacement feature and the AMF determines to provide the mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI to the UE, the network shall provide the UE with the alternative NSSAI. The alternative NSSAI is managed per access type independently, i.e. 3GPP access or non-3GPP access, and is applicable for the registration area. If the UE has indicated that the UE supports the partial network slice feature and includes the S-NSSAI(s) in the requested NSSAI, the AMF determines the S-NSSAI(s) to be included in the partially allowed NSSAI or the partially rejected NSSAI as specified in subclause 4.6.2.11. When the AMF provides both the partially allowed NSSAI and the partially rejected NSSAI to the UE, each S-NSSAI shall be either in the partially allowed NSSAI or in the partially rejected NSSAI but not both. The number of S-NSSAIs included in the partially allowed NSSAI or the partially rejected NSSAI shall not exceed 7. The number of S-NSSAI stored in the partially allowed NSSAI and the allowed NSSAI shall not exceed 8. The partially allowed NSSAI is only applicable to 3GPP access and is applicable for the registration area. The partially rejected NSSAI is only applicable to 3GPP access and is applicable for the registration area. NOTE 2: Based on local policies, the UE can remove an S-NSSAI from the rejected NSSAI for the failed or revoked NSSAA when the UE wants to register to the slice identified by this S-NSSAI. NOTE 3: Based on network local policy, network slice-specific authentication and authorization procedure can be initiated by the AMF for an S-NSSAI in rejected NSSAI for the failed or revoked NSSAA when the S-NSSAI is requested by the UE based on its local policy. NOTE 4: At least one S-NSSAI in the default configured NSSAI or at least one default S-NSSAI is recommended as not subject to network slice-specific authentication and authorization, in order to ensure that at least one PDU session can be established to access service, even when Network Slice-specific Authentication and Authorization fails. NOTE 5: At least one S-NSSAI in the default configured NSSAI or at least one default S-NSSAI is recommended as not subject to network slice admission control, in order to ensure that at least one PDU session can be established to access service. NOTE 6: The rejected NSSAI can be provided by the network via either Rejected NSSAI IE or the Extended rejected NSSAI IE. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.6 |
4,951 | 2.1.1 Random values | In a number of places in the present document, it is mentioned that some value must take a "random" value, in a given range, or more generally with some statistical distribution. Such cases interest only the Mobile Station. It is required that there is a low probability that two MSs in the same conditions (including the case of two MSs of the same type from the same manufacturer) will choose the same value. Moreover, it is required that, if it happens that two MSs in similar conditions choose the same value, the probability of their choices being identical at the next occasion is the same as if their first choices had been different. The meaning of such a specification is that any statistical test for these values, done on a series of similar events, will obtain a result statistically compatible with the specified distribution. This shall hold even in the cases where the tests are conducted with a subset of possible events, with some common parameters. Moreover, basic tests of independence of the values within the series shall pass. Data against which correlation with the values shall not be found are the protocol state, or the IMSI, or identities or other unrelated information broadcast by the network, or the current TDMA frame number. | 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 | 2.1.1 |
4,952 | – MeasGapConfig | The IE MeasGapConfig specifies the measurement gap configuration and controls setup/release of measurement gaps. MeasGapConfig information element -- ASN1START -- TAG-MEASGAPCONFIG-START MeasGapConfig ::= SEQUENCE { gapFR2 SetupRelease { GapConfig } OPTIONAL, -- Need M ..., [[ gapFR1 SetupRelease { GapConfig } OPTIONAL, -- Need M gapUE SetupRelease { GapConfig } OPTIONAL -- Need M ]], [[ gapToAddModList-r17 SEQUENCE (SIZE (1..maxNrofGapId-r17)) OF GapConfig-r17 OPTIONAL, -- Need N gapToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofGapId-r17)) OF MeasGapId-r17 OPTIONAL, -- Need N posMeasGapPreConfigToAddModList-r17 PosMeasGapPreConfigToAddModList-r17 OPTIONAL, -- Need N posMeasGapPreConfigToReleaseList-r17 PosMeasGapPreConfigToReleaseList-r17 OPTIONAL -- Need N ]] } GapConfig ::= SEQUENCE { gapOffset INTEGER (0..159), mgl ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6}, mgrp ENUMERATED {ms20, ms40, ms80, ms160}, mgta ENUMERATED {ms0, ms0dot25, ms0dot5}, ..., [[ refServCellIndicator ENUMERATED {pCell, pSCell, mcg-FR2} OPTIONAL -- Cond NEDCorNRDC ]], [[ refFR2ServCellAsyncCA-r16 ServCellIndex OPTIONAL, -- Cond AsyncCA mgl-r16 ENUMERATED {ms10, ms20} OPTIONAL -- Cond PRS ]] } GapConfig-r17 ::= SEQUENCE { measGapId-r17 MeasGapId-r17, gapType-r17 ENUMERATED {perUE, perFR1, perFR2}, gapOffset-r17 INTEGER (0..159), mgl-r17 ENUMERATED {ms1, ms1dot5, ms2, ms3, ms3dot5, ms4, ms5, ms5dot5, ms6, ms10, ms20}, mgrp-r17 ENUMERATED {ms20, ms40, ms80, ms160}, mgta-r17 ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot75}, refServCellIndicator-r17 ENUMERATED {pCell, pSCell, mcg-FR2} OPTIONAL, -- Cond NEDCorNRDC refFR2-ServCellAsyncCA-r17 ServCellIndex OPTIONAL, -- Cond AsyncCA preConfigInd-r17 ENUMERATED {true} OPTIONAL, -- Need R ncsgInd-r17 ENUMERATED {true} OPTIONAL, -- Need R gapAssociationPRS-r17 ENUMERATED {true} OPTIONAL, -- Need R gapSharing-r17 MeasGapSharingScheme OPTIONAL, -- Need R gapPriority-r17 GapPriority-r17 OPTIONAL, -- Need R ... } PosMeasGapPreConfigToAddModList-r17 ::= SEQUENCE (SIZE (1..maxNrofPreConfigPosGapId-r17)) OF PosGapConfig-r17 PosMeasGapPreConfigToReleaseList-r17 ::= SEQUENCE (SIZE (1..maxNrofPreConfigPosGapId-r17)) OF MeasPosPreConfigGapId-r17 PosGapConfig-r17 ::= SEQUENCE { measPosPreConfigGapId-r17 MeasPosPreConfigGapId-r17, gapOffset-r17 INTEGER (0..159), mgl-r17 ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20}, mgrp-r17 ENUMERATED {ms20, ms40, ms80, ms160}, mgta-r17 ENUMERATED {ms0, ms0dot25, ms0dot5}, gapType-r17 ENUMERATED {perUE, perFR1, perFR2}, ... } MeasPosPreConfigGapId-r17 ::= INTEGER (1..maxNrofPreConfigPosGapId-r17) -- TAG-MEASGAPCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,953 | 16.10.5.6 DRX | The following DRX configurations for PTM/PTP transmission by RRC_CONNECTED UEs are possible: - For PTM transmission, multicast DRX is configured per G-RNTI/G-CS-RNTI which is independent of UE-specific DRX; - For PTP transmission, UE-specific DRX is reused, i.e., UE-specific DRX is used for both unicast transmission and PTP transmission of MBS multicast. For PTM retransmission via PTP, UE monitors PDCCH scrambled by C-RNTI/CS-RNTI during UE-specific DRX's Active Time. The following DRX configuration for PTM transmission by RRC_INACTIVE UEs is possible: - For PTM transmission, multicast DRX is configured per G-RNTI. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.5.6 |
4,954 | 4.15.9.4 Procedures for management of 5G access stratum time distribution | The AF can use the procedure to activate, update or delete the 5G access stratum time distribution for one UE or a group of UEs. The AF may query the status of the 5G access stratum time distribution using Nnef_ASTI_Get service operation. The Nnef_ASTI_Create and Nnef_ASTI_Update request may contain the parameters as described in Table 4.15.9.4-1. The AF may subscribe to 5G access stratum time synchronization status via Nnef_ASTI_Subscribe service operation. The AF may receive 5G access stratum time distribution status updates via Nnef_ASTI_UpdateNotify service operation. Table 4.15.9.4-1: Description of 5G access stratum time distribution parameters Figure 4.15.9.4-1: Management of 5G access stratum time information 1. AM Policy Association establishment as described in clause 4.16.1. 2. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): - To create a new request, the AF provides access stratum time distribution parameters to the NEF using the Nnef_ASTI_Create service operation (together with the AF identifier and potentially further inputs as specified in table 4.15.9.4-1), including a target (one UE identified by SUPI or GPSI, a group of UEs identified by an External Group Identifier. The NEF forwards the GPSI or the External Group Identifier to the TSCTSF by including it inside the Ntsctsf_ASTI_Create request. - To update or remove an existing request, the AF invokes an Nnef_ASTI_Update or Nnef_ASTI_Delete service operation providing the corresponding time synchronization configuration id. - To query the status of the access stratum time distribution, the AF invokes Nnef_ASTI_Get service operation providing the target (a list of UE identities (SUPI or GPSIs) or an External Group Identifier). - If the AF includes clock quality detail level, the request creates a subscription at the TSCTSF for notifications for the changes in 5G access stratum time distribution status. - To subscribe to NG-RAN timing synchronization status updates, the AF can subscribe to notifications as described in clause 4.15.9.5.1. The AF that is part of operator's trust domain may invoke the services directly with the TSCTSF and identifies the targeted UE(s) using SUPI(s) or an Internal Group Identifier. If the request includes a spatial validity condition and the AF uses a geographical area as a spatial validity condition, the NEF transforms this information into 3GPP identifiers (e.g. TAI(s)) based on pre-configuration. NOTE 1: Steps 1 and 2 can occur in any order. NOTE 2: It is assumed that AFs within the operator's domain is aware of TAs that can be used to formulate a spatial validity condition for Time Synchronization Coverage Area (see clause 5.27.1.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). 3. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): - The NEF authorizes the request. After successful authorization, the NEF invokes the Ntsctsf_ASTI_Create/Update/Delete/Get service operation with the TSCTSF discovered and selected as described in clause 6.3.24 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - The TSCTSF determines whether the targeted UE is part of a PTP instance in 5GS, if so the TSCTSF rejects the request (steps 4-11 are skipped). - The TSCTSF checks whether the AF requested parameters comply with the stored Time Synchronization Subscription Data as defined in clause 5.27.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - The TSCTSF calculates the Uu time synchronization error budget as described in clause 5.27.1.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. This does not apply in case of Ntsctsf_ASTI_Delete service operation. (When the procedure is triggered by PTP instance activation or modification in the TSCTSF): - The TSCTSF calculates the Uu time synchronization error budget as described in clause 5.27.1.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] for corresponding SUPIs that are part of the PTP instance. 4. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): If the AF targeted UE(s) are identified by GPSI(s) or an External/Internal Group Identifier, the TSCTSF uses the Nudm_SDM_Get request to retrieve the subscription information (SUPI(s)) from the UDM using each GPSI or the External Group Identifier as received from the NEF, or an Internal Group Identifier as provided by the AF directly. 5. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): The UDM provides the Nudm_SDM_Get response containing SUPI(s) that are mapped from each received GPSI or the External/Internal Group Identifier and identify the targeted UEs. 6a. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): If the Ntsctsf_ASTI_Create request in step 2 contains a spatial validity condition, then the TSCTSF performs the following operations: - For each target UE, TSCTSF checks with the stored Time Synchronization Subscription data if the spatial validity condition is allowed. The TSCTSF determines whether the TSCTSF has subscribed for the UE presence in Area of Interest composed by the TAs list in the spatial validity condition. If not, the TSCTSF may either discover the AMF(s) serving in the TAs comprising the spatial validity condition or discovers the serving AMF(s) for each UE identified by a GPSI/SUPI as described in clause 5.27.1.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Then the TSCTSF subscribes to the AMF(s) to receive notifications about the UE presence in Area of Interest using Namf_EventExposure operation with the corresponding event filters as described in clause 5.2.2.3 and in clause 5.3.4.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The subscribed area of interest may be the same as the 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. - In order to ensure that a TAI list specifying the AoI for the AMF is aligned with UE's Registration Area (RA), the following steps shall be performed: - When invoking the subscription with the AMF(s), the TSCTSF may provide an indication, a new Parameter Type = "Adjust AoI based on RA", that the AMF may adjust the received AoI depending on UE's RA. - After receiving the Namf_EventExposure_Subscribe request from the TSCTSF with the Parameter Type = "Adjust AoI based on RA" and specified AoI, the AMF compares TAs from the AoI with the UE's Registration Area (RA). If the AoI includes one or more TA(s) that are part of UE's current RA, the AMF reports the UE is inside the Area Of Interest, otherwise the AMF reports the UE is outside the Area Of Interest, as described in Annex D. - The AMF notifies the TSCTSF about the UE's presence in the AoI using the Namf_EventExposure_Notify service operation. - Based on the notification from the AMF and spatial validity condition received in step 1, the TSCTSF determines whether to activate time synchronization service for this UE: - If the UE location is within the spatial validity condition, the TSCTSF determines to enable access stratum time distribution for the UE. - If the UE location is outside the spatial validity condition, the TSCTSF determines to disable access stratum time distribution for the UE. If the Ntsctsf_ASTI_Create request in step 2 contains a temporal validity condition with a start-time and/or the stop-time that is in the future, the TSCTSF maintains the start-time and stop-time for the time synchronization service for the corresponding time synchronization configuration. If the start-time is in the past, the TSCTSF treats the request as if the time synchronization service was activated immediately. When the start-time is reached, the TSCTSF proceeds with the subsequent steps. When the stop-time is reached for active time synchronization service configuration, the TSCTSF proceeds as if Nnef_ASTI_Delete was received. 6b. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): The TSCTSF checks the AF request with the stored Time Synchronization Subscription data as described in clause 5.27.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] for any targeted UE. If the AF is not authorized, steps 7-11 are skipped. 7. The TSCTSF searches the PCF for the UE using Nbsf_Management_Subscribe with a SUPI as an input parameter, indicating that it is searching for the PCF that handles the AM Policy Association of the UE. 8. The BSF provides to the TSCTSF the identity of the PCF for the UE for the requested SUPI via an Nbsf_Management_Notify operation. If matching entries already existed in the BSF when step 6 is performed, this shall be immediately reported to the TSCTSF. 9. The TSCTSF sends to the PCF for the UE its request for the AM policy of the UE (identified by SUPI) using Npcf_AMPolicyAuthorization request, containing the 5G access stratum time distribution indication (enable, disable), optionally the calculated Uu time synchronization error budget, optionally the clock quality detail level and clock quality acceptance criteria. (When the procedure is triggered by PTP instance activation, modification, or deactivation in the TSCTSF): The TSCTSF ensures the 5G access stratum time distribution for the UE is enabled if at least one of the PTP instances the UE is part of is active. 10. If the PCF receives multiple time synchronization error budgets for a given UE, then the PCF picks the most stringent budget. The PCF takes a policy decision and then the PCF may initiate an AM Policy Association Modification procedure for the UE as described in clause 4.16.2.2 to provide AMF the 5G access stratum time distribution parameters. As part of this, the AMF shall, if supported, store the 5G access stratum time distribution indication (enable, disable), the Uu time synchronization error budget, clock quality detail level and clock quality acceptance criteria, and the UE reconnection indication in the UE context in AMF and send the 5G access stratum time distribution indication (enable, disable), the Uu time synchronization error budget, clock quality detail level and clock quality acceptance criteria when they are available, to NG-RAN during mobility registration, AM policy modification, Service Request, N2 Handover and Xn handover as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. The NG-RAN node shall, if supported, store the information in the UE Context. Based on this information, the NG-RAN node provides the 5GS access stratum time to the UE according to the Uu time synchronization error budget as provided by the TSCTSF (if supported by UE and NG-RAN) and NG-RAN provides timing synchronization status reports to the UE (as described in clause 4.15.9.5.2). If the UE has indicated a support for network reconnection due to RAN timing synchronization status change as described in clause 5.4.4a of TS 23.501[ System architecture for the 5G System (5GS) ] [2], and if the AMF received "clock quality detail level" as part of an AM Policy Association Modification procedure, the AMF sets the "UE reconnection indication" for the UE to connect to the network in the case when the UE later detects that the NG-RAN timing synchronization status has changed while the UE is in CM-IDLE or CM-CONNECTED with RRC_INACTIVE state. The AMF shall send the UE reconnection indication to the UE updating the UE configuration as defined in clause 4.2.4.2. If the AMF receives Uu time synchronization error budget in the Access Stratum Time Synchronization Service Authorization as part of the Access and Mobility Subscription data during registration procedure (see clause 4.28.2.1) and in the AM Policy, the AMF should use the value received from the AM policy. NOTE 3: This release of the specification assumes that deployments ensure that the targeted UEs and the NG-RAN nodes serving those UEs support Rel-17 propagation delay compensation as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]. 11. The PCF of the UE replies to the TSCTSF with the result of Npcf_AMPolicyAuthorization operation. 12. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): The TSCTSF responds the AF with the Ntsctsf_ASTI_Create/Update/Delete/Get service operation response. 13. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): The NEF informs the AF about the result of the Nnef_ASTI_Create/Update/Delete/Get service operation performed in step 2. 14. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): If TSCTSF received spatial validity condition as part of the Ntsctsf_ASTI_Create request in step 2, upon the reception of a change in the UE presence in Area of Interest notification, the TSCTSF determines if the spatial validity condition shall trigger an activation or deactivation of the access stratum time distribution: - If the UE has moved inside the Time Synchronization Coverage Area, then the TSCTSF determines to enable access stratum time distribution for the UE. - If the UE has moved outside the Time Synchronization Coverage Area, then the TSCTSF determines to disable access stratum time distribution for the UE. If TSCTSF received clock quality acceptance criteria as part of the Ntsctsf_ASTI_Create request in step 2, upon a reception of a UE presence in Area of Interest notification, the TSCTSF determines if the UE is impacted correlating UE presence in Area of Interest notifications provided by the serving AMF and the timing synchronization status received (e.g. degradation, failure, recovery) as described in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 15-16. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): If TSCTSF determines to modify access stratum time distribution for the UE in step 14 for which the AF requested access stratum time distribution, the TSCTSF notifies the service status to AF. If the TSCTSF determines a change in the support of the clock quality acceptance criteria for the UE in step 14 for which the AF requested access stratum time distribution, the TSCTSF includes the clock quality acceptance criteria result to the notification to the AF. Based on this notification, the AF decides whether to modify the ASTI service configured for the UE using Ntsctsf_ASTI_Update service. 17. If there was a failure/degradation/improvement event in step 14, the NG-RAN provides timing synchronization status reports to the UE (as described in clause 4.15.9.5.2). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.9.4 |
4,955 | 4.7.1.6.1 Change of network mode of operation in A/Gb mode (A/Gb mode only) | Whenever an MS moves to a new RA, the procedures executed by the MS depend on the network mode of operation in the old and new routing area. In case the MS is in state GMM REGISTERED or GMM ROUTING AREA UPDATING INITIATED and is in operation mode A or B, the MS shall execute according to table 4.7.1.6.1-1: Table 4.7.1.6.1-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Mode A or B (*) Intended to remove the Gs association in the MSC/VLR. (**) Intended to establish the Gs association in the MSC/VLR. (***) If the MS that needs only GPRS services and "SMS-only service" moves to a new routing area, see subclause 4.1.1.2.2. Further details are implementation issues. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.1.6.1 |
4,956 | D.3.7 E-UTRAN to GERAN A/Gb mode Inter RAT handover D.3.7.1 General | The interoperation procedures describe information flows for Gn/Gp SGSNs and other EPS network elements. All messages between SGSN and MME, between SGSN and BSS, between SGSN and HSS and between SGSN and P-GW (GGSN in TS 43.129[ None ] [8]) as well as the therein contained information elements are the same as specified for the adequate TS 43.129[ None ] [8] procedures. These messages and procedure step descriptions are taken from TS 43.129[ None ] [8] for explanatory purposes only. These descriptions are in italic text and shall not be modified by the interoperation procedures. It cannot be assumed that the messages and procedure step descriptions that are taken from TS 43.129[ None ] [8] will be updated when modifications or corrections are performed for TS 43.129[ None ] [8]. If there are any discrepancies for these messages and procedure step descriptions TS 43.129[ None ] [8] takes precedence. The messages between the MME and any other node than the Gn/Gp SGSN as well as the therein contained information elements are the same as specified in the main body of this technical specification for the IRAT handover E-UTRAN to/from GERAN A/Gb mode procedure (clauses 5.5.2.3 and 5.5.2.4). These descriptions are in bold italic text and should be modified simultaneously when clauses 5.5.2.3 or 5.5.2.4 are updated. If there are any discrepancies, the procedure step descriptions in clauses 5.5.2.3 or 5.5.2.4 take precedence. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.3.7 |
4,957 | 4.2.11.6 Update of local maximum number in Hierarchical NSAC Architecture | Figure 4.2.11.6-1: Update of local maximum number in hierarchical NSAC architecture At any time the Primary NSACF may update the allocated local Maximum number of UE and/or PDU sessions configured at the NSACFs as follow: 1. The Primary NSACF decides to update the local maximum number of UE or PDU session values at the NSACF(s), i.e. the configured value at NSACF(s) based on the current registered UE/PDU session number at NSACFs and based on operator policy. 2. The Primary NSACF invokes Nnsacf_NSAC_LocalNumberUpdate Request to the NSACF(s). The message includes the new configured value of local Maximum number of UE or PDU sessions. NOTE: The new configured value(s) of local maximum number given by the Primary NSACF can be lower than the existing local maximum number configured at the NSACF(s). 3. The NSACF replaces the local maximum number with the received new local maximum number value. 4. The NSACF returns the Nnsacf_NSAC_LocalNumberUpdate Response to the Primary NSACF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.11.6 |
4,958 | 6.3.5 Mapping to resource elements | For each of the antenna ports used for transmission of the physical channel, the block of complex-valued symbols shall conform to the downlink power allocation specified in clause 5.2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4] and be mapped in sequence starting with to resource elements which meet all of the following criteria in the current subframe: - they are in the physical resource blocks corresponding to the virtual resource blocks assigned for transmission, and - they are not used for transmission of the core part of PBCH, synchronization signals, and - they are assumed by the UE not to be used for cell-specific reference signals, where the positions of the cell-specific reference signals are given by clause 6.10.1.2 with the number of antenna ports for and the frequency shift of cell-specific reference signals derived as described in clause 6.10.1.2 4, and The mapping to resource elements on antenna port not reserved for other purposes shall be in increasing order of first the index over the assigned physical resource blocks and then the index, starting with the first slot in a subframe. For BL/CE UEs, if the higher layer parameter ce-punctured-subcarriers-DL is configured, then in case of MPDCCH or PDSCH transmission associated with C-RNTI or SPS C-RNTI, - The parameter ce-punctured-subcarriers-DL indicates the number of subcarriers (1 or 2) and their position (lower or higher edge) to puncture at the downlink narrowband edges: - If the value is '00', then the number of punctured subcarriers on the higher edge of narrowbands above the DC subcarrier is 2 and the number of punctured subcarriers on the higher edge of narrowbands below the DC subcarrier is 1. - If the value is '01', then the number of punctured subcarriers on the higher edge of narrowbands above the DC subcarrier is 1 and the number of punctured subcarriers on the higher edge of narrowbands below the DC subcarrier is 0. - If the value is '10', then the number of punctured subcarriers on the lower edge of narrowbands above the DC subcarrier is 0 and the number of punctured subcarriers on the lower edge of narrowbands below the DC subcarrier is 1. - If the value is '11', then the number of punctured subcarriers on the lower edge of narrowbands above the DC subcarrier is 1 and the number of punctured subcarriers on the lower edge of narrowbands below the DC subcarrier is 2. - In the mapping to resource elements, when a subcarrier k is punctured according to the above, the resource elements (k,l) shall be counted but not used for transmission. - The subcarrier puncturing is applied to transmission of the following physical signals and channels when the transmission is aligned with a narrowband edge. - MPDCCH - PDSCH - CSI reference signals - No subcarrier puncturing is applied to transmissions that are not aligned with a narrowband edge. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.5 |
4,959 | 6.4.3.2 EPS bearer context modification initiated by the network | The MME shall initiate the EPS bearer context modification procedure by sending a MODIFY EPS BEARER CONTEXT REQUEST message to the UE, starting the timer T3486, and entering the state BEARER CONTEXT MODIFY PENDING (see example in figure 6.4.3.2.1). The MME shall include an EPS bearer identity that identifies the EPS bearer context to be modified in the MODIFY EPS BEARER CONTEXT REQUEST message. If this procedure was initiated by a UE requested bearer resource allocation procedure or a UE requested bearer resource modification procedure, the MODIFY EPS BEARER CONTEXT REQUEST shall contain the procedure transaction identity (PTI) value received by the MME in the BEARER RESOURCE ALLOCATION REQUEST or BEARER RESOURCE MODIFICATION REQUEST message respectively. If the UE indicated "Control plane CIoT EPS optimization supported" and "Header compression for control plane CIoT EPS optimization supported" in the UE network capability IE in the latest ATTACH REQUEST message or the TRACKING AREA UPDATE REQUEST message, and the MME supports Control plane CIoT EPS optimization and Header compression for control plane CIoT EPS optimization, the MME may include the Header compression configuration IE in the MODIFY EPS BEARER CONTEXT REQUEST message to re-negotiate header compression configuration associated to an EPS bearer context. Figure 6.4.3.2.1: EPS bearer context modification procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.3.2 |
4,960 | 4.6.3.5 Session management for optimized handling of temporarily available network slices | A network slice can be available temporarily. Subclause 4.6.2.8 addresses how the allowed NSSAI and partially allowed NSSAI are managed based on the S-NSSAI time validity information. If the S-NSSAI time validity information indicates that the S-NSSAI is available, the UE may initiate a UE-requested PDU session establishment procedure to establish a PDU session associated with the S-NSSAI. If the S-NSSAI time validity information indicates that the S-NSSAI is not available, then the UE shall: a) initiate UE-requested PDU session release procedure to release any PDU session associated with the S-NSSAI, if the UE is in 5GMM-CONNECTED mode or in 5GMM-CONNECTED mode with RRC inactive indication; or b) locally release any PDU session associated with the S-NSSAI, if the UE is in 5GMM-IDLE mode. When the S-NSSAI time validity information in the AMF indicates that the S-NSSAI is not available, independent of whether the UE is in 5GMM-CONNECTED mode, 5GMM-CONNECTED mode with RRC inactive indication or in 5GMM-IDLE mode, the AMF shall request the SMF to release any PDU session associated with the S-NSSAI. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.6.3.5 |
4,961 | – SIB19 | SIB19 contains satellite assistance information for NTN access. SIB19 information element -- ASN1START -- TAG-SIB19-START SIB19-r17 ::= SEQUENCE { ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R t-Service-r17 INTEGER (0..549755813887) OPTIONAL, -- Need R referenceLocation-r17 ReferenceLocation-r17 OPTIONAL, -- Need R distanceThresh-r17 INTEGER(0..65525) OPTIONAL, -- Need R ntn-NeighCellConfigList-r17 NTN-NeighCellConfigList-r17 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ ntn-NeighCellConfigListExt-v1720 NTN-NeighCellConfigList-r17 OPTIONAL -- Need R ]], [[ movingReferenceLocation-r18 ReferenceLocation-r17 OPTIONAL, -- Need R satSwitchWithReSync-r18 SatSwitchWithReSync-r18 OPTIONAL -- Need R ]] } NTN-NeighCellConfigList-r17 ::= SEQUENCE (SIZE(1..maxCellNTN-r17)) OF NTN-NeighCellConfig-r17 NTN-NeighCellConfig-r17 ::= SEQUENCE { ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R carrierFreq-r17 ARFCN-ValueNR OPTIONAL, -- Need R physCellId-r17 PhysCellId OPTIONAL -- Need R } SatSwitchWithReSync-r18 ::= SEQUENCE { ntn-Config-r18 NTN-Config-r17, t-ServiceStart-r18 INTEGER (0..549755813887) OPTIONAL, -- Need R ssb-TimeOffset-r18 INTEGER (0..159) OPTIONAL -- Need R } -- TAG-SIB19-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,962 | 10.2.4.4 Mapping to resource elements | The block of complex-valued symbols for each antenna port is transmitted in subframe 0 for frame structure type 1 or subframe 9 for frame structure type 2 during 64 consecutive radio frames starting in each radio frame fulfilling . The quantity for normal cyclic prefix. Define as the block of complex-valued symbols to be transmitted in subframe 0 for frame structure type 1 or subframe 9 for frame structure type 2 of radio frame , as , with for normal cyclic prefix, and where the scrambling sequence , is given by clause 7.2, and shall be initialized at the start of each radio frame with . The block of complex-valued symbols shall be mapped in sequence starting with to resource elements . The mapping to resource elements not reserved for transmission of reference signals shall be in increasing order of first the index, then the index . The first three OFDM symbols in a subframe shall not be used in the mapping process. For the purpose of the mapping, the UE shall assume cell-specific reference signals for antenna ports 0-3 and narrowband reference signals for antenna ports 2000 and 2001 being present irrespective of the actual configuration. The frequency shift of the cell-specific reference signals shall be calculated by replacing with in the calculation of in clause 6.10.1.2. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.4.4 |
4,963 | 8.7.10 TDD (4 Rx) | The parameters specified in Table 8.7.10-1 are valid for all TDD tests for 4Rx capable UEs unless otherwise stated. Table 8.7.10-1: Common Test Parameters (TDD) For UE not supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.10-2 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.10-3 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the requirement with 64QAM is not applicable. The TB success rate is defined as 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks. The TB success rate shall be sustained during at least 300 frames. Table 8.7.10-2: Per-CC FRC for SDR test(TDD 64QAM) Table 8.7.10-3: Per-CC FRC for SDR test (TDD 256QAM) CA configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. - Select one CA bandwidth combination among all supported CA configurations with bandwidth combination and MIMO layer on each CC that leads to largest equivalent aggregated bandwidth among all CA bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as where is number of CCs, and is MIMO layer and bandwidth of CC . - When there are multiple sets of {CA configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer CCs. - The procedure applies also for single carrier using operating band instead of CA configuration, and bandwidth instead of bandwidth combination. Table 8.7.10-4: Void Table 8.7.10-5: Void | 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.7.10 |
4,964 | 5.9.1.2 MCCH scheduling | The MCCH information (i.e. information transmitted in messages sent over MCCH) is transmitted periodically, using a configurable repetition period and within a configured transmission window. MCCH transmissions (and the associated radio resources and MCS) are indicated via the PDCCH addressed to MCCH-RNTI. PDCCH monitoring occasion(s) for MCCH transmission are determined according to the common search space indicated by searchspaceMCCH. If searchspaceMCCH is set to zero, PDCCH monitoring occasions for MCCH message reception in the MCCH transmission window are the same as PDCCH monitoring occasions for SIB1 where the mapping between PDCCH monitoring occasions and SSBs is specified in TS 38.213[ NR; Physical layer procedures for control ] [13]. If searchspaceMCCH is not set to zero, PDCCH monitoring occasions for MCCH message are determined based on search space indicated by searchspaceMCCH. PDCCH monitoring occasions for MCCH message which are not overlapping with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are sequentially numbered from one in the MCCH transmission window. The [x×N+K]th PDCCH monitoring occasion for MCCH message in MCCH transmission window corresponds to the Kth transmitted SSB, where x = 0, 1, ...X-1, K = 1, 2, …N, N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 and X is equal to CEIL(number of PDCCH monitoring occasions in MCCH transmission window/N). The actual transmitted SSBs are sequentially numbered from one in ascending order of their SSB indexes. The UE assumes that, in the MCCH transmission window, PDCCH for an MCCH message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB and thus the selection of SSB for the reception MCCH messages is up to UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.1.2 |
4,965 | 6.19.2 Requirements | The following set of requirements complement the requirements listed in 3GPP TS 22.011[ Service accessibility ] [3], clause 3.2. The 5G system shall support selection among any available PLMN/RAT combinations, identified through their respective PLMN identifier and Radio Access Technology identifier, in a prioritised order. The priority order may, subject to operator policies, be provisioned in an Operator Controlled PLMN Selector lists with associated RAT identifiers, stored in the 5G UE. The 5G system shall support, subject to operator policies, a User Controlled PLMN Selector list stored in the 5G UE, allowing the UE user to specify preferred PLMNs with associated RAT identifier in priority order. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.19.2 |
4,966 | 19.4.2.8 DNS subdomain for operator usage in EPC | The EPC nodes DNS subdomain (DNS zone) shall be derived from the MNC and MCC by adding the label "node" to the beginning of the Home Network Realm/Domain (see clause 19.2) and shall be constructed as: node.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org This DNS subdomain is formally placed into the operator's control. 3GPP shall never take this DNS subdomain back or any zone cut/subdomain within it for any purpose. As a result the operator can safely provision any DNS records it chooses under this subdomain without concern about future 3GPP standards encroaching on the DNS names within this zone. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.8 |
4,967 | 5.5.2.8 Quantity configuration | The UE shall: 1> for each RAT for which the received quantityConfig includes parameter(s): 2> set the corresponding parameter(s) in quantityConfig within VarMeasConfig to the value of the received quantityConfig parameter(s); 1> for each measId included in the measIdList within VarMeasConfig: 2> remove the measurement reporting entry for this measId from the VarMeasReportList, if included; 2> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.8 |
4,968 | 8.50 PLMN ID | Octets 5-7 shall contain a non-transparent copy of the " PLMN Identity" parameter in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. Figure 8.50-1: PLMN ID The encoding of the PLMN ID field is shown in Figures 8.50-2 and 8.50-3. If three digits are included in the MNC, octets 5 to 7 shall be encoded as shown in Figure 8.50-2. Figure 8.50-2: PLMN ID Parameter with 3-digit MNC If only two digits are included in the MNC, octets 5 to 7 shall be encoded as shown in Figure 8.50-3 with bits 5 to 8 of octet 6 (MNC digit 3) coded as "1111". Figure 8.50-3: PLMN ID Parameter with 2-digit MNC NOTE: The encoding is different from elsewhere in this document and is specified according to 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. | 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.50 |
4,969 | 4.14.3 Public network integrated non-public network (PNI-NPN) | A PNI-NPN is made available by means of e.g. dedicated DNNs or by one or more S-NSSAIs allocated for it. A CAG can be optionally used in order to prevent UEs not allowed to access a PNI-NPN from accessing the PNI-NPN. The key enablers for the CAG in the NAS layer are as follows: a) CAG selection (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]); and b) provisioning of a "CAG information list" as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], from network to UE via the generic UE configuration update procedure, the registration procedure, the service request procedure, and the network-initiated de-registration procedure. The "CAG information list" provisioned by the network, if available, is stored in the non-volatile memory in the ME as specified in annex C. The "CAG information list" stored in the ME is kept when the UE enters 5GMM-DEREGISTERED state. Annex C specifies condition under which the "CAG information list" stored in the ME is deleted. Additionally, when a USIM is inserted, if: - no "CAG information list" is stored in the non-volatile memory of the ME; or - the SUPI from the USIM does not match the SUPI stored together with the "CAG information list" in the non-volatile memory of the ME; and the UE has a "CAG information list" stored in the USIM (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]), the UE shall store the "CAG information list" from the USIM into the ME, as specified in annex C. The "Allowed CAG list" included in the entry for the HPLMN or EHPLMN in "CAG information list" stored in the USIM can contain a range of CAG-IDs. The UE supporting CAG may perform the initial registration for emergency services via a non-CAG cell in a PLMN for which the UE has an "indication that the UE is only allowed to access 5GS via CAG cells" or via a CAG cell for which none of CAG-ID(s) is authorized based on the "Allowed CAG list" (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) for the selected PLMN. If a UE supporting CAG having an emergency PDU session is camping on: a) a CAG cell and none of the CAG-ID(s) of the CAG cell is authorized based on the "Allowed CAG list" for the current PLMN in the UE's subscription; or b) a non-CAG cell in a PLMN for which the UE's subscription contains an "indication that the UE is only allowed to access 5GS via CAG cells"; the AMF shall behave as specified in subclause 5.4.4.2, 5.5.1.3.4 or 5.6.1.4.1. NOTE: The emergency services in a PLMN for which the UE's subscription contains an "indication that the UE is only allowed to access 5GS via CAG cells" can be subject to local regulation. Proximity based services (5G ProSe as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]) are not supported in this release of the specification when a UE is camping on a CAG cell. If a UE supporting enhanced CAG information is in a CAG cell with a CAG-ID which: a) was authorized based on the "Allowed CAG list" associated with the current PLMN in the "CAG information list" stored in the ME; and b) becomes not authorized based on the "Allowed CAG list" (e.g., time validity information no longer matches UE's current time); and none of the CAG-ID(s) supported by the current CAG cell is currently authorized based on the "Allowed CAG list" of the entry for the current PLMN in the stored "CAG information list", and: a) the entry for the current PLMN in the "CAG information list" does not include an "indication that the UE is only allowed to access 5GS via CAG cells", then the UE shall abort ongoing UE initialted 5GMM procedures, if any, locally release the NAS signalling connection, if any, enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the stored "CAG information list"; or b) the entry for the current PLMN in the stored "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells" and: 1) one or more CAG-ID(s) are authorized based on the "Allowed CAG list" of the entry for the current PLMN in the stored "CAG information list", the UE shall abort ongoing UE initialted 5GMM procedures, if any, locally release the NAS signalling connection, if any, enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the stored "CAG information list"; or 2) no CAG-ID is authorized based on the "Allowed CAG list" of the entry for the current PLMN in the stored "CAG information list" and: i) the UE does not have an emergency PDU session, then the UE shall abort ongoing UE initialted 5GMM procedures, if any, locally release the NAS signalling connection, if any, enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the stored "CAG information list"; or ii) the UE has an emergency PDU session, then the UE shall perform a local release of all PDU sessions associated with 3GPP access except for the emergency PDU session and enter the state 5GMM-REGISTERED.LIMITED-SERVICE; | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.14.3 |
4,970 | 5.9.2.2 Reporting at Presence Reporting Area entering and leaving | In some use cases policy control/charging decisions, such as QoS modification or charging rate change depend on whether the UE is located inside or outside a specific area of interest (Presence Reporting Area), and especially on whether the UE enters or leaves that specific area of interest. A Presence Reporting Area can be: - Either a "UE-dedicated Presence Reporting Area", defined in the subscriber profile and composed of a short list of TAs/RAs, or eNodeBs and/or cells/SAs in a PLMN; - Or a "Core Network predefined Presence Reporting Area", predefined in MME/SGSN and composed of a short list of TAs/RAs, or eNodeBs and/or cells/SAs in a PLMN. NOTE 1: eNodeBs are identified via the Global eNodeB ID IE defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. NOTE 2: Change of UE presence in Presence Reporting Area reporting does not apply to roaming. The reporting of changes of UE presence in Presence Reporting Area is for a specific UE and is triggered as defined in TS 23.203[ Policy and charging control architecture ] [6]. The PDN GW may request to Start/Stop reporting of changes of UE presence for one or more Presence Reporting Area(s) by using the Presence Reporting Area Action parameter. For UE-dedicated Presence Reporting Areas, the reporting request (Start) shall contain the PRA identifier(s) and the list(s) of TAs/RAs, or eNodeBs and/or cells/SAIs composing the Presence Reporting Area(s). For Core Network predefined Presence Reporting Areas, the reporting request (Start) shall contain the PRA identifier(s). The request to Stop a reporting contains the PRA identifier(s). Each Core Network predefined Presence Reporting Area can be configured with a priority level in the MME/S4-SGSN. In order to prevent overload, the MME/S4-SGSN may set the reporting for one or more of the received Presence Reporting Area(s) to inactive under consideration of the priority configured for each of Core Network predefined Presence Reporting Area(s), while storing the reporting request for this Presence Reporting Area in the user context. Upon reception of a request for change of UE presence in Presence Reporting Area reporting, the MME/S4-SGSN shall report to the PDN GW via the SGW the Presence Reporting Area Information comprising the PRA identifier(s) and indication(s) on whether the UE is inside or outside the Presence Reporting Area(s). If the UE is in ECM-IDLE state, the MME may either bring the UE into ECM-CONNECTED state, or, report based on the UE's last known location and when the UE was there. One or more Presence Reporting Area may be set for a given PDN connection at a time. The serving node if needed only sets the reporting of UE presence in a Presence Reporting Area to inactive when receiving the reporting request for this Presence Reporting Area. If the MME/S4-SGSN decides to set the reporting of UE presence in one or more of the received Presence Reporting Area(s) to inactive, the MME/S4-SGSN shall also report the inactive Presence Reporting Area(s). The MME/S4-SGSN shall notify the PDN GW when the UE enters or leaves a Presence Reporting Area, and no notifications are sent for UE movements inside or outside a Presence Reporting Area. The report of the change of UE presence in Presence Reporting Area shall contain the Presence Reporting Area Information comprising the PRA identifier(s) and indication(s) on whether the UE is inside or outside the area(s). A report shall be sent if the UE presence is different to the last one reported. The MME/S4-SGSN may be configured with a PRA identifier which refers to a Set of Core Network predefined Presence Reporting Areas. The PDN GW may request Start reporting for this Set of Presence Reporting Areas by only indicating this PRA identifier in the Presence Reporting Area Action. When the Presence Reporting Area(s) to be reported belong to a set of Core Network predefined Presence Reporting Areas in which the MME/S4-SGSN is requested to report on change of UE presence, the MME/S4-SGSN shall additionally add to the report the PRA identifier of the Set of Core Network predefined Presence Reporting Areas. Upon change of serving EPC node (MME, S4-SGSN), the PRA identifier(s) and if provided by the PDN GW the list(s) of Presence Reporting Area elements are transferred for all PDN connections as part of MM Context information to the target serving node during the mobility procedure. If one or more Presence Reporting Area(s) was set to inactive, the target serving node may decide to reactivate one or more of the inactive Presence Reporting Area(s). The target serving node indicates per PDN connection to the corresponding PDN GW the PRA identifier(s) and whether the UE is inside or outside the Presence Reporting Area(s) as well as the inactive Presence Reporting Area(s), if any. NOTE 3: The target serving node cannot set the Presence Reporting Area(s) received from the source serving node to inactive. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.9.2.2 |
4,971 | 4.4.3.5 NAS COUNT wrap around | If, when increasing the NAS COUNT as specified above, the AMF detects that either its downlink NAS COUNT or the UE's uplink NAS COUNT is "close" to wrap around, (close to 224), the AMF shall take the following actions: - If there is no non-current native 5G NAS security context with sufficiently low NAS COUNT values, the AMF shall initiate a new primary authentication and key agreement procedure with the UE, leading to a new established 5G NAS security context and the NAS COUNT being reset to 0 in both the UE and the AMF when the new 5G NAS security context is activated; - Otherwise, the AMF can activate a non-current native 5G NAS security context with sufficiently low NAS COUNT values or initiate a new primary authentication and key agreement procedure as specified above. If for some reason a new KAMF has not been established using primary authentication and key agreement procedure before the NAS COUNT wraps around, the node (AMF or UE) in need of sending a NAS message shall instead release the NAS signalling connection. Prior to sending the next uplink NAS message, the UE shall delete the ngKSI indicating the current 5G NAS security context. When the 5G-IA0 is used as the NAS integrity algorithm, the UE and the AMF shall allow NAS COUNT wrap around. If NAS COUNT wrap around occurs, the following requirements apply: a) the UE and the AMF shall continue to use the current 5G NAS security context; b) the AMF shall not initiate the primary authentication and key agreement procedure; c) the AMF shall not release the NAS signalling connection; and d) the UE shall not perform a local release of the NAS signalling connection. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.3.5 |
4,972 | 17.5.8 Trace Session Activation procedure | The Trace Session Activation procedure occurs when the GGSN indicates to the BM-SC that a Trace Session needs to be activated. Figure 33: Trace Session Activation procedure 1. When the GGSN has received a Trace Activation message from the SGSN, in a Create MBMS Context Request/Update MBMS Context Request, that requires the activation of a Trace Session in the BM-SC, the GGSN sends an AAR message (containing the IMSI and the Additional MBMS Trace Info AVPs) to activate a trace session in the BM-SC. 2. Upon reception of an AAR from a GGSN to activate a Trace Session, the BM-SC responds with an AAA message. | 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.5.8 |
4,973 | 15.5.2.3 Inter-system Unnecessary HO | One of the purposes of inter-system Mobility Robustness Optimisation is the detection of a non-optimal use of network resources. In particular, in case of inter-system operations and when NR is considered, the case known as Unnecessary HO to another system is identified. The problem is defined as follows: - UE is handed over from NR to E-UTRAN even though quality of the NR coverage was sufficient for the service used by the UE. The handover may therefore be considered as unnecessary HO to another system (i.e. EPS) (too early inter-system HO without connection failure). In inter-system HO, if the serving cell threshold (NR cell) is set too high, and cell in another system (i.e. EPS) with good signal strength is available, a handover to another system may be triggered unnecessarily, resulting in an inefficient use of the networks. With a lower threshold the UE could have continued in the source system (5GS). To be able to detect the Unnecessary HO to another system, a gNB node may choose to put additional coverage and quality condition information into the HANDOVER REQUIRED message in the Handover Preparation procedure when an inter-system HO from gNB to another system occurs. The RAN node in the other system, upon receiving this additional coverage and quality information, may instruct the UE to continue measuring the cell(s) in source system during a period of time, while being connected to another system, and send periodic or single measurement reports to the node in other system. When the period of time indicated by the node in source system expires, the RAN node in the other system, may evaluate the received measurement reports with the coverage/quality condition received during the inter-system HO procedure and decide if an inter-system unnecessary HO report should be sent to the gNB in the source system. The inter-system unnecessary HO report shall only be sent in cases where, in all UE measurement reports collected during the measurement period, any cells in the source system exceed the radio coverage and/or quality threshold (the radio threshold RSRP, RSRQ or/and SINR and the measurement period are indicated in the additional coverage and quality information in the Handover Preparation procedure). If an inter-system handover towards 5GS is executed from EPS within the indicated measurement period, the measurement period expires. In this case, the eNB in EPS may also send the HO Report. No HO Report shall be sent in case no NR cell could be included, or if the indicated period of time is interrupted by an inter-system handover to a system different than 5GS. The RAN node in the source system (5GS) upon receiving of the report, can decide if/how its parameters (e.g., threshold to trigger Inter-system HO) should be adjusted. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.2.3 |
4,974 | 5.2.5.3 Npcf_PolicyAuthorization Service 5.2.5.3.1 General | Service description: This service is to authorise an AF request and to create policies as requested by the authorized AF for the PDU Session to which the AF session is bound. Additionally, this service allows an AF or TSCTSF to exchange port management information with DS-TT and NW-TT. This service allows the NF consumer to subscribe/unsubscribe the notification of events, which are defined in clause 6.1.3.18 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") | 5.2.5.3 |
4,975 | 5.1.1.1 Number of RNReconfiguration attempts | a) This measurement provides the number of RNReconfiguration attempts sent by DeNB. b) CC c) On transmission by the DeNB of a RNReconfiguration message to RN. Each RNReconfiguration message received is added to the relevant measurement. The message is included in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. d) Each measurement is an integer value. e) The measurement name has the form RRC.RNReconAttNbr. f) DeNBCapability 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 | 5.1.1.1 |
4,976 | 6.2.4.4 Additional requirements of the UE acting as 5G ProSe layer-3 UE-to-network relay UE for IP address allocation | If a UE acting as 5G ProSe layer-3 UE-to-network relay needs to indicate "IPv6 Router" or "DHCPv4 Server & IPv6 Router" in the IP address configuration IE as specified in 3GPP 24.554 [19E], the UE shall support acting as a "Requesting Router" as described in IETF RFC 8415 [33D] to request additional IPv6 prefixes (i.e. prefixes in addition to the /64 default prefix which was allocated via stateless IPv6 address autoconfiguration as specified in subclause 6.2.4.1) from the SMF as specified in subclause 5.5.2 of 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]. When the UE acting as 5G ProSe layer-3 UE-to-network relay UE requests additional prefixes using DHCPv6, the UE shall perform procedures described in subclause 6.2.4.2a. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.4.4 |
4,977 | 4.3.1.4.4 Successful outgoing inter-frequency handovers – gap-assisted measurement | This measurement provides the number of successful outgoing inter-frequency handovers, when measurement gaps are used [12]. CC. Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source) eNB/RN, indicating a successful outgoing intra-eNB/RN inter-frequency handover when measurement gaps are used (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), or receipt at the source eNB/RN of UE CONTEXT RELEASE [10] over the X2 from the target eNB or DeNB following a successful inter-frequency handover when measurement gaps are used, or if handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND[9] at the source eNB following a successful inter-frequency handover when measurement gaps are used. A single integer value. HO.InterFreqMeasGapOutSucc EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.4.4 |
4,978 | – RACH-ConfigTwoTA | The IE RACH-ConfigTwoTA is used to specify random access parameters for each additional PCI configured for the serving cell. RACH-ConfigTwoTA information element -- ASN1START -- TAG-RACH-CONFIGTWOTA-START RACH-ConfigTwoTA-r18 ::= SEQUENCE { rach-ConfigTwoTAIndex-r18 RACH-ConfigTwoTAIndex-r18, additionalPCIIndex-r18 AdditionalPCIIndex-r17, rach-ConfigGeneric-r18 RACH-ConfigGeneric, ssb-perRACH-Occasion-r18 ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} OPTIONAL, -- Need R prach-RootSequenceIndex-r18 CHOICE { l839 INTEGER (0..837), l139 INTEGER (0..137) } OPTIONAL, -- Need R msg1-SubcarrierSpacing-r18 SubcarrierSpacing OPTIONAL, -- Need R ... } RACH-ConfigTwoTAIndex-r18 ::= INTEGER(1.. maxNrofAdditionalPRACHConfigs-r18) -- TAG-RACH-CONFIGTWOTA-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,979 | – SL-CBR-CommonTxDedicated-SL-PRS-RP-List | The IE SL-CBR-CommonTxConfigListDedicated-SL-PRS-RP indicates the list of SL PRS transmission parameters (such as Maximum SL PRS transmission power, Maximum Number of SL PRS (re-)transmissions, and CR limit) in sl-CBR-SL-PRS-TxConfigList, and the list of CBR ranges in sl-CBR-RangeConfigList-Dedicated-SL-PRS-RP, to configure congestion control to the UE for sidelink positioning. SL-CBR-CommonTxDedicatedSL-PRS-RP-List information element -- ASN1START -- TAG- SL-CBR-COMMONTXDEDICATEDSL-PRS-RP-LIST-START SL-CBR-CommonTxDedicatedSL-PRS-RP-List-r18 ::= SEQUENCE { sl-CBR-RangeDedicatedSL-PRS-RP-List-r18 SEQUENCE (SIZE (1..maxCBR-ConfigDedSL-PRS-1-r18)) OF SL-CBR-LevelsDedicatedSL-PRS-RP-r18 OPTIONAL, -- Need M sl-CBR-SL-PRS-TxConfigList-r18 SEQUENCE (SIZE (1.. maxNrofSL-PRS-TxConfig-r18)) OF SL-CBR-SL-PRS-TxConfig-r18 OPTIONAL -- Need M } SL-CBR-LevelsDedicatedSL-PRS-RP-r18 ::= SEQUENCE (SIZE (0..maxCBR-LevelDedSL-PRS-1-r18)) OF SL-CBR-Dedicated-SL-PRS-RP-r18 SL-CBR-SL-PRS-TxConfig-r18 ::= SEQUENCE { sl-PRS-CR-Limit-r18 INTEGER(0..10000) OPTIONAL, -- Need M sl-PRS-MaxTx-power-r18 INTEGER (-30..33) OPTIONAL, -- Need M sl-PRS-MaxNum-Transmissions-r18 INTEGER(1..32) OPTIONAL -- Need M } SL-CBR-Dedicated-SL-PRS-RP-r18 ::= INTEGER (0..100) -- TAG-SL-CBR-COMMONTXDEDICATEDSL-PRS-RP-LIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,980 | 16.2 Authorization for network slice access | This clause specifies the relationship between primary authentication (as described in Clause 6.1) and authorization for network slice access (as described in TS 23.502[ Procedures for the 5G System (5GS) ] [8]) for a UE. Authorization from a home/serving PLMN is required for a UE to gain access to a network slice, identified by an S-NSSAI. An authorized S-NSSAI (i.e. allowed S-NSSAI) shall be granted to a UE only after the UE has completed successfully primary authentication. At the end of the primary authentication, the AMF and UE may receive a list of allowed S-NSSAI, which the UE is authorized to access. For certain S-NSSAIs, additional Network Slice Specific Authentication and Authorization (NSSAA) is required. This clause in addition specifies the pre-requisite for an NSSAA procedure that is described in clause 16.3, with reference to the following figure 16.2-1. Figure 16.2-1: Relationship between primary authentication and NSSAA 1. UE sends a Registration Request with a list of S-NSSAIs. UE shall not include those S-NSSAIs for which NSSAA procedures are ongoing, regardless of access types (c.f. TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 5.15.5.2.1 and TS 23.502[ Procedures for the 5G System (5GS) ] [8], clause 4.2.2.2.2). 2. For an initial Registration Request, the AMF/SEAF shall invoke Primary authentication as described in clause 6.1.2 of the present document. For a subsequent Registration Request, the Primary authentication may be skipped if the UE has already been authenticated and the AMF has valid security context. 3. AMF shall determine whether NSSAA is required for each of S-NSSAIs, based on information stored locally or from UDM. For example, the NSSAA for an S-NSSAI may be omitted 1) if it is not required based on the subscription information, 2) if UE has previously performed NSSAA successfully, regardless of access type and the result is still valid, or 3) NSSAA for UE is ongoing 4. AMF sends the Registration Accept message to the UE (c.f. TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 5.15.5.2.1 and TS 23.502[ Procedures for the 5G System (5GS) ] [8], clause 4.2.2.2.2, step 21). Optionally UE sends a Registration Complete. 5. The EAP based NSSAA procedure for each S-NSSAI if required, as determined in step 3, is executed in this step. 6. Based on the results of step 5, AMF sends UE Configuration Update to update the requested S-NSSAI status based on the NSSAA results. The procedure for step 5, i.e., the NSSAA procedure is specified in clause 16.3. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 16.2 |
4,981 | 16.10.6.6 Physical Layer | A CFR configured by SIB is defined for broadcast scheduling as an 'MBS frequency region' with a number of contiguous PRBs with a bandwidth equal to or larger than CORESET0, with the same numerology as CORESET0, and broadcast scheduling may have specific characteristics (e.g., PDCCH and PDSCH configurations). The maximum number of MIMO layers is one for MBS broadcast scheduling. RB-level rate matching, and RE-level rate matching around LTE-CRS configured by higher layer signalling are supported for MCCH and MTCH. Slot-level repetition is supported for MTCH. HARQ-ACK feedback is not supported for MBS broadcast. Only dynamic scheduling is supported for MBS broadcast. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.6.6 |
4,982 | 5.5.3 Performing measurements 5.5.3.1 General | An RRC_CONNECTED UE shall derive cell measurement results by measuring one or multiple beams associated per cell as configured by the network, as described in 5.5.3.3. For all cell measurement results, except for RSSI, and CLI measurement results in RRC_CONNECTED, the UE applies the layer 3 filtering as specified in 5.5.3.2, before using the measured results for evaluation of reporting criteria, measurement reporting or the criteria to trigger conditional reconfiguration execution. For cell measurements, the network can configure RSRP, RSRQ, SINR, RSCP or EcN0 as trigger quantity. For CLI measurements, the network can configure SRS-RSRP or CLI-RSSI as trigger quantity. For cell and beam measurements, reporting quantities can be any combination of quantities (i.e. only RSRP; only RSRQ; only SINR; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR; only RSCP; only EcN0; RSCP and EcN0), irrespective of the trigger quantity, and for CLI measurements, reporting quantities can be either SRS-RSRP or CLI-RSSI. For conditional reconfiguration execution, the network can configure up to 2 quantities, both using same RS type. The UE does not apply the layer 3 filtering as specified in 5.5.3.2 to derive the CBR measurements. The UE does not apply the layer 3 filtering as specified in 5.5.3.2 to derive the Rx-Tx time difference measurements. The network may also configure the UE to report measurement information per beam (which can either be measurement results per beam with respective beam identifier(s) or only beam identifier(s)), derived as described in 5.5.3.3a. If beam measurement information is configured to be included in measurement reports, the UE applies the layer 3 beam filtering as specified in 5.5.3.2. On the other hand, the exact L1 filtering of beam measurements used to derive cell measurement results is implementation dependent. The UE shall: 1> whenever the UE has a measConfig, perform RSRP and RSRQ measurements for each serving cell for which servingCellMO is configured as follows: 2> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains an rsType set to ssb and ssb-ConfigMobility is configured in the measObject indicated by the servingCellMO: 3> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains a reportQuantityRS-Indexes and maxNrofRS-IndexesToReport and contains an rsType set to ssb: 4> derive layer 3 filtered RSRP and RSRQ per beam for the serving cell based on SS/PBCH block, as described in 5.5.3.3a; 3> derive serving cell measurement results based on SS/PBCH block, as described in 5.5.3.3; 2> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains an rsType set to csi-rs and CSI-RS-ResourceConfigMobility is configured in the measObject indicated by the servingCellMO: 3> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains a reportQuantityRS-Indexes and maxNrofRS-IndexesToReport and contains an rsType set to csi-rs: 4> derive layer 3 filtered RSRP and RSRQ per beam for the serving cell based on CSI-RS, as described in 5.5.3.3a; 3> derive serving cell measurement results based on CSI-RS, as described in 5.5.3.3; 1> for each serving cell for which servingCellMO is configured, if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains SINR as trigger quantity and/or reporting quantity: 2> if the reportConfig contains rsType set to ssb and ssb-ConfigMobility is configured in the servingCellMO: 3> if the reportConfigcontains a reportQuantityRS-Indexes and maxNrofRS-IndexesToReport: 4> derive layer 3 filtered SINR per beam for the serving cell based on SS/PBCH block, as described in 5.5.3.3a; 3> derive serving cell SINR based on SS/PBCH block, as described in 5.5.3.3; 2> if the reportConfig contains rsType set to csi-rs and CSI-RS-ResourceConfigMobility is configured in the servingCellMO: 3> if the reportConfigcontains a reportQuantityRS-Indexes and maxNrofRS-IndexesToReport: 4> derive layer 3 filtered SINR per beam for the serving cell based on CSI-RS, as described in 5.5.3.3a; 3> derive serving cell SINR based on CSI-RS, as described in 5.5.3.3; 1> for each measId included in the measIdList within VarMeasConfig: 2> if the reportType for the associated reportConfig is set to reportCGI and timer T321 is running: 3> if useAutonomousGaps is configured for the associated reportConfig: 4> perform the corresponding measurements on the frequency and RAT indicated in the associated measObject using autonomous gaps as necessary; 3> else: 4> perform the corresponding measurements on the frequency and RAT indicated in the associated measObject using available idle periods; 3> if the cell indicated by reportCGI field for the associated measObject is an NR cell and that indicated cell is broadcasting SIB1 (see TS 38.213[ NR; Physical layer procedures for control ] [13], clause 13): 4> try to acquire SIB1 in the concerned cell; 3> if the cell indicated by reportCGI field is an E-UTRA cell: 4> try to acquire SystemInformationBlockType1 in the concerned cell; 2> if the ul-DelayValueConfig is configured for the associated reportConfig: 3> ignore the measObject; 3> for each of the configured DRBs, configure the PDCP layer to perform corresponding average UL PDCP packet delay measurement per DRB; 2> if the ul-ExcessDelayConfig is configured for the associated reportConfig: 3> ignore the measObject; 3> for each of the configured DRBs, configure the PDCP layer to perform corresponding UL PDCP Excess Packet Delay delay measurement according to the configured threshold per DRB; 2> if the reportType for the associated reportConfig is periodical, eventTriggered; or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the MCG VarMeasConfig and is indicated in the condExecutionCond or in the condExecutionCondPSCell associated to a condReconfigId in the MCG VarConditionalReconfig (for CHO, CPA or MN-initiated inter-SN CPC in NR-DC); or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in the condExecutionCond associated to a condReconfigId in the SCG VarConditionalReconfig (for intra-SN CPC); or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in the condExecutionCondSCG associated to a condReconfigId in the MCG VarConditionalReconfig (for SN-initiated inter-SN CPC in NR-DC); or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in the triggerConditionSN associated to a condReconfigurationId in VarConditionalReconfiguration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] (for SN-initiated inter-SN CPC in EN-DC): 3> if a measurement gap configuration is setup, or 3> if the UE does not require measurement gaps to perform the concerned measurements: 4> if s-MeasureConfig is not configured, or 4> if s-MeasureConfig is set to ssb-RSRP and the NR SpCell RSRP based on SS/PBCH block, after layer 3 filtering, is lower than ssb-RSRP, or 4> if s-MeasureConfig is set to csi-RSRP and the NR SpCell RSRP based on CSI-RS, after layer 3 filtering, is lower than csi-RSRP: 5> if the measObject is associated to NR and the rsType is set to csi-rs: 6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured: 7> derive layer 3 filtered beam measurements only based on CSI-RS for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a; 6> derive cell measurement results based on CSI-RS for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3; 5> if the measObject is associated to NR and the rsType is set to ssb: 6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured: 7> derive layer 3 beam measurements only based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a; 6> derive cell measurement results based on SS/PBCH block for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3; 5> if the measObject is associated to E-UTRA: 6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned measObject, as described in 5.5.3.2; 5> if the measObject is associated to UTRA-FDD: 6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned measObject, as described in 5.5.3.2; 5> if the measObject is associated to L2 U2N Relay UE: 6> perform the corresponding measurements associated to candidate Relay UEs on the frequencies indicated in the concerned measObject, as described in 5.5.3.4; 4> if the measRSSI-ReportConfig is configured in the associated reportConfig: 5> perform the RSSI and channel occupancy measurements on the frequency configured by rmtc-Frequency in the associated measObject; NOTE 0: The network avoids configuring UEs supporting only CHO and/or Rel-16 CPC with measurements not referred to by any execution condition. 2> if the reportType for the associated reportConfig is set to reportSFTD and the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than one: 3> if the reportSFTD-Meas is set to true: 4> if the measObject is associated to E-UTRA: 5> perform SFTD measurements between the PCell and the E-UTRA PSCell; 5> if the reportRSRP is set to true; 6> perform RSRP measurements for the E-UTRA PSCell; 4> else if the measObject is associated to NR: 5> perform SFTD measurements between the PCell and the NR PSCell; 5> if the reportRSRP is set to true; 6> perform RSRP measurements for the NR PSCell based on SSB; 3> else if the reportSFTD-NeighMeas is included: 4> if the measObject is associated to NR: 5> if the drx-SFTD-NeighMeas is included: 6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associated measObject using available idle periods; 5> else: 6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associated measObject; 5> if the reportRSRP is set to true: 6> perform RSRP measurements based on SSB for the NR neighbouring cell(s) detected based on parameters in the associated measObject; 2> if the reportType for the associated reportConfig is cli-Periodical or cli-EventTriggered: 3> perform the corresponding measurements associated to CLI measurement resources indicated in the concerned measObjectCLI; 2> perform the evaluation of reporting criteria as specified in 5.5.4, except if reportConfig is condTriggerConfig. The UE acting as a L2 U2N Remote UE whenever configured with measConfig shall: 1> perform the corresponding measurements associated to the serving L2 U2N Relay UE, as described in 5.5.3.4; NOTE 1: The evaluation of conditional reconfiguration execution criteria is specified in 5.3.5.13. The UE capable of Rx-Tx time difference measurement when configured with measObjectRxTxDiff shall: 1> perform the corresponding Rx-Tx time difference measurements associated with downlink reference signals indicated in the concerned measObjectRxTxDiff. The UE capable of CBR measurement when configured to transmit NR sidelink communication/discovery/positioning shall: 1> If the frequency used for NR sidelink communication/discovery/positioning is included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12 or included in sl-PosConfigCommonNR within SIB23: 2> if the UE is in RRC_IDLE or in RRC_INACTIVE: 3> if configured with NR sidelink communication and the cell chosen for NR sidelink communication provides SIB12 which includes sl-TxPoolSelectedNormal or sl-TxPoolExceptional for the concerned frequency; or 3> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides SIB12 which includes sl-TxPoolSelectedNormal or sl-TxPoolExceptional but does not include sl-DiscTxPoolSelected for the concerned frequency: 4> perform CBR measurement on pool(s) in sl-TxPoolSelectedNormal or sl-TxPoolExceptional for the concerned frequency in SIB12; 3> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides SIB12 which includes sl-DiscTxPoolSelected for the concerned frequency: 4> perform CBR measurement on pools in sl-DiscTxPoolSelected and sl-TxPoolExceptional for the concerned frequency in SIB12; 3> if configured with NR sidelink positioning and the cell chosen for NR sidelink positioning provides SIB23 which includes sl-PRS-TxPoolSelectedNormal or sl-PRS-TxPoolExceptional for the concerned frequency: 4> perform CBR measurement on pool(s) in sl-TxPoolSelectedNormal or sl-TxPoolExceptional for the concerned frequency in SIB23; 2> if the UE is in RRC_CONNECTED: 3> if tx-PoolMeasToAddModList is included in VarMeasConfig: 4> perform CBR measurements on each transmission resource pool indicated in the tx-PoolMeasToAddModList; 3> if sl-DiscTxPoolSelected, sl-TxPoolSelectedNormal, sl-TxPoolScheduling or sl-TxPoolExceptional is included in sl-ConfigDedicatedNR for the concerned frequency within RRCReconfiguration: 4> perform CBR measurement on pool(s) in sl-DiscTxPoolSelected, sl-TxPoolSelectedNormal, sl-TxPoolScheduling and sl-TxPoolExceptional if included in sl-ConfigDedicatedNR for the concerned frequency within RRCReconfiguration; 3> else: 4> if configured with NR sidelink communication and the cell chosen for NR sidelink communication provides SIB12 which includes sl-TxPoolSelectedNormal or sl-TxPoolExceptional for the concerned frequency; or 4> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides SIB12 which includes sl-TxPoolSelectedNormal or sl-TxPoolExceptional but does not provide sl-DiscTxPoolSelected for the concerned frequency: 5> perform CBR measurement on pool(s) in sl-TxPoolSelectedNormal or sl-TxPoolExceptional for the concerned frequency in SIB12; 4> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides SIB12 which includes sl-DiscTxPoolSelected for the concerned frequency: 5> perform CBR measurement on pools in sl-DiscTxPoolSelected and sl-TxPoolExceptional for the concerned frequency in SIB12; 4> if configured with NR sidelink positioning and the cell chosen for NR sidelink positioning provides SIB23 which includes sl-PRS-TxPoolSelectedNormal or sl-PRS-TxPoolExceptional for the concerned frequency: 5> perform CBR measurement on pool(s) in sl-PRS-TxPoolSelectedNormal or sl-PRS-TxPoolExceptional for the concerned frequency in SIB23 1> else: 2> if configured with NR sidelink communication and sl-TxPoolSelectedNormal is included in SidelinkPreconfigNR for the concerned frequency; or 2> if configured with NR sidelink discovery and sl-TxPoolSelectedNormal is included in SidelinkPreconfigNR but sl-DiscTxPoolSelected is not included in SidelinkPreconfigNR for the concerned frequency: 3> perform CBR measurement on pool(s) in sl-TxPoolSelectedNormal in SidelinkPreconfigNR for the concerned frequency. 2> if configured with NR sidelink discovery and sl-DiscTxPoolSelected is included in SidelinkPreconfigNR for the concerned frequency: 3> perform CBR measurement on pools in sl-DiscTxPoolSelected if included in SidelinkPreconfigNR. 2> if configured with NR sidelink communication/positioning and sl-PRS-TxPoolSelectedNormal is included in SL-PosPreconfigurationNR for the concerned frequency: 3> perform CBR measurement on pool(s) in sl-PRS-TxPoolSelectedNormal in SidelinkPreconfigNR for the concerned frequency. NOTE 2: In case the configurations for NR sidelink communication and CBR measurement are acquired via the E-UTRA, configurations for NR sidelink communication in SIB12, sl-ConfigDedicatedNR within RRCReconfiguration used in this clause are provided by the configurations in SystemInformationBlockType28, sl-ConfigDedicatedForNR within RRCConnectionReconfiguration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], respectively. NOTE 3: If a UE that is configured by upper layers to transmit V2X sidelink communication is configured by NR with transmission resource pool(s) and the measurement objects concerning V2X sidelink communication (i.e. by sl-ConfigDedicatedEUTRA-Info), it shall perform CBR measurement as specified in clause 5.5.3 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], based on the transmission resource pool(s) and the measurement object(s) concerning V2X sidelink communication configured by NR. NOTE 4: For V2X sidelink communication, each of the CBR measurement results is associated with a resource pool, as indicated by the poolReportId (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]), that refers to a pool as included in sl-ConfigDedicatedEUTRA-Info or SIB13. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.3 |
4,983 | 6.4.3.4 EPS bearer context modification not accepted by the UE | Upon receipt of the MODIFY EPS BEARER CONTEXT REQUEST message, the UE may reject the request from the MME by sending a MODIFY EPS BEARER CONTEXT REJECT message to the MME. The message shall include the EPS bearer identity and an ESM cause value indicating the reason for rejecting the EPS bearer context modification request. The MODIFY EPS BEARER CONTEXT REJECT message contains an ESM cause that typically indicates one of the following ESM cause values: #26: insufficient resources; #41: semantic error in the TFT operation; #42: syntactical error in the TFT operation; #43: invalid EPS bearer identity; #44: semantic error(s) in packet filter(s); #45: syntactical error(s) in packet filter(s); or #95 – 111: protocol errors. The UE shall check the TFT in the request message for different types of TFT IE errors as follows: a) Semantic errors in TFT operations: 1) TFT operation = "Create a new TFT" when there is already an existing TFT for the EPS bearer context. 2) When the TFT operation is an operation other than "Create a new TFT", the EPS bearer context being modified is the default EPS bearer content and there is no TFT for the default EPS bearer context. 3) TFT operation = "Delete packet filters from existing TFT" when it would render the TFT empty. 4) TFT operation = "Delete existing TFT" for a dedicated EPS bearer context. In case 4 the UE shall reject the modification request with ESM cause #41 "semantic error in the TFT operation". In the other cases the UE shall not diagnose an error and perform the following actions to resolve the inconsistency: In case 1 the UE shall further process the new activation request to create a new TFT and, if it was processed successfully, delete the old TFT. In case 2 the UE shall: - process the new request and if the TFT operation is "Delete existing TFT" or "Delete packet filters from existing TFT", and if no error according to items b, c, and d was detected, consider the TFT as successfully deleted; - process the new request as an activation request, if the TFT operation is "Add packet filters in existing TFT" or "Replace packet filters in existing TFT". In case 3, if the packet filters belong to a dedicated EPS bearer context, the UE shall process the new deletion request and, if no error according to items b, c, and d was detected, the UE shall reject the modification request with ESM cause #41 "semantic error in the TFT operation". In case 3, if the packet filters belong to the default EPS bearer context, the UE shall process the new deletion request and if no error according to items b, c, and d was detected then delete the existing TFT, this corresponds to using match-all packet filter for the default EPS bearer context. b) Syntactical errors in TFT operations: 1) When the TFT operation = "Create a new TFT", "Add packet filters in existing TFT", "Replace packet filters in existing TFT" or "Delete packet filters from existing TFT" and the packet filter list in the TFT IE is empty. 2) TFT operation = "Delete existing TFT" or "No TFT operation" with a non-empty packet filter list in the TFT IE. 3) TFT operation = "Replace packet filters in existing TFT" when the packet filter to be replaced does not exist in the original TFT. 4) TFT operation = "Delete packet filters from existing TFT" when the packet filter to be deleted does not exist in the original TFT. 5) Void. 6) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list. In case 3 the UE shall not diagnose an error, further process the replace request and, if no error according to items c and d was detected, include the packet filters received to the existing TFT. In case 4 the UE shall not diagnose an error, further process the deletion request and, if no error according to items c and d was detected, consider the respective packet filter as successfully deleted. Otherwise the UE shall reject the modification request with ESM cause #42 "syntactical error in the TFT operation". NOTE: An implementation that strictly follows packet filter list as defined in subclause 10.5.6.12 in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] might not detect case 2). c) Semantic errors in packet filters: 1) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document. 2) When the resulting TFT, which is assigned to a dedicated EPS bearer context, does not contain any packet filter applicable for the uplink direction among the packet filters created on request from the network. The UE shall reject the modification request with ESM cause #44 "semantic errors in packet filter(s)". d) Syntactical errors in packet filters: 1) When the TFT operation = "Create a new TFT", "Add packet filters to existing TFT", or "Replace packet filters in existing TFT" and two or more packet filters in the resultant TFT would have identical packet filter identifiers. 2) When the TFT operation = "Create a new TFT", "Add packet filters to existing TFT" or "Replace packet filters in existing TFT", and two or more packet filters among all TFTs associated with this PDN connection would have identical packet filter precedence values. 3) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. In case 1, if two or more packet filters with identical packet filter identifiers are contained in the new request, the UE shall reject the modification request with ESM cause #45 "syntactical errors in packet filter(s)". Otherwise, the UE shall not diagnose an error, further process the new request and, if it was processed successfully, delete the old packet filters which have the identical packet filter identifiers. In case 2, if the old packet filters do not belong to the default EPS bearer context, the UE shall not diagnose an error, shall further process the new request and, if it was processed successfully, shall delete the old packet filters which have identical filter precedence values. Furthermore, the UE shall perform a UE requested bearer resource modification procedure to delete the packet filters in the network corresponding to the packet filters it has deleted on the UE side. In case 2, if one or more old packet filters belong to the default EPS bearer context, the UE shall release the relevant PDN connection. If the relevant PDN connection is the last one that the UE has and EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the UE shall detach and re-attach to the network. Otherwise the UE shall reject the modification request with ESM cause #45 "syntactical errors in packet filter(s)". Upon receipt of the MODIFY EPS BEARER CONTEXT REJECT message with ESM cause value other than #43 "invalid EPS bearer identity" in state BEARER CONTEXT MODIFY PENDING, the MME shall stop the timer T3486, enter the state BEARER CONTEXT ACTIVE and abort the EPS bearer context modification procedure. If the network receives the MODIFY EPS BEARER CONTEXT REJECT message with ESM cause #43 "invalid EPS bearer identity", the MME locally deactivates the EPS bearer context(s) without peer-to-peer ESM signalling. When the MME detects that after the failed EPS bearer context modification there is a misalignment between the EPS bearer configuration and the EPS bearer context configuration or between the QoS on NAS and AS level, the MME should initiate the necessary procedures to achieve a re-alignment. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.3.4 |
4,984 | – ULDedicatedMessageSegment | The ULDedicatedMessageSegment message is used to transfer segments of the UECapabilityInformation or MeasurementReportAppLayer message. SRB1 is used at transfer of segments of UECapabilityInformation and SRB4 or SRB5 is used at transfer of segments of MeasurementReportAppLayer. Signalling radio bearer: SRB1, SRB4 or SRB5 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network ULDedicatedMessageSegment message -- ASN1START -- TAG-ULDEDICATEDMESSAGESEGMENT-START ULDedicatedMessageSegment-r16 ::= SEQUENCE { criticalExtensions CHOICE { ulDedicatedMessageSegment-r16 ULDedicatedMessageSegment-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } ULDedicatedMessageSegment-r16-IEs ::= SEQUENCE { segmentNumber-r16 INTEGER (0..15), rrc-MessageSegmentContainer-r16 OCTET STRING, rrc-MessageSegmentType-r16 ENUMERATED {notLastSegment, lastSegment}, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-ULDEDICATEDMESSAGESEGMENT-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,985 | 17.5.10 MBMS UE Context Modification Procedure | During the multicast MBMS bearer service activation, the MBMS UE Context is stored in the BM-SC. Later, the MBMS UE Context shall be updated when the UE enters a new Routeing Area (RA) served by a new SGSN or the UE is transitioning between UTRAN and A/Gb mode GERAN or vice versa (Inter-system Intra-SGSN change). See 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [65] and 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24]. GGSN shall pass the relevant data via the Gmb interface to enable the BM-SC to update its MBMS UE context accordingly. Figure 35; Modification of an MBMS UE Context in BM-SC 1, On request from SGSN, the MBMS UE Context is updated in the GGSN. 2. The GGSN sends updated MBMS UE Context parameters (RAI, and CGI/SAI as specified in clause 17.6.1) to BM-SC in an AAR message. 3. The BM-SC updates its MBMS UE Context fields and responds with an AAA message. If the GGSN receives new or updated trace information in step 1, then the above procedure may be followed by a Trace Session Activation procedure (see clause 17.5.8) or a Trace Session Deactivation procedure (see clause 17.5.9). | 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.5.10 |
4,986 | 5.5.1.2.8 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure If a lower layer failure occurs before the REGISTRATION COMPLETE message has been received from the UE and timer T3550 is running, the AMF shall locally abort the registration procedure for initial registration, enter state 5GMM-REGISTERED and shall not resend the REGISTRATION ACCEPT message. If a new 5G-GUTI was assigned to the UE in the registration procedure for initial registration, the AMF shall consider both the old and the new 5G-GUTI as valid until the old 5G-GUTI can be considered as invalid by the AMF or the 5GMM context which has been marked as deregistered in the AMF is released. If the old 5G-GUTI was allocated by an AMF other than the current AMF, the current AMF does not need to retain the old 5G-GUTI. During this period the network may use the identification procedure followed by a generic UE configuration update procedure if the old 5G-GUTI is used by the UE in a subsequent message. b) Protocol error If the REGISTRATION REQUEST message is received with a protocol error, the AMF shall return a REGISTRATION REJECT message with one of the following 5GMM cause values: #96 invalid mandatory information; #99 information element non-existent or not implemented; #100 conditional IE error; or #111 protocol error, unspecified. c) T3550 time-out On the first expiry of the timer, the AMF shall retransmit the REGISTRATION ACCEPT message and shall reset and restart timer T3550. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3550, the registration procedure for initial registration shall be aborted and the AMF enters state 5GMM-REGISTERED. If a new 5G-GUTI was allocated in the REGISTRATION ACCEPT message, the AMF shall consider both the old and the new 5G-GUTIs as valid until the old 5G-GUTI can be considered as invalid by the AMF or the 5GMM context which has been marked as de-registered in the AMF is released. If the old 5G-GUTI was allocated by an AMF other than the current AMF, the current AMF does not need to retain the old 5G-GUTI. During this period, if the old 5G-GUTI is used by the UE in a subsequent message, the AMF acts as specified for case a) above. d) REGISTRATION REQUEST message received after the REGISTRATION ACCEPT message has been sent and before the REGISTRATION COMPLETE message is received, if the REGISTRATION COMPLETE message is expected. 1) If one or more of the information elements in the REGISTRATION REQUEST message differ from the ones received within the previous REGISTRATION REQUEST message, the previously initiated the registration procedure for initial registration shall be aborted if the REGISTRATION COMPLETE message has not been received and the new registration procedure for initial registration shall be progressed; or 2) if the information elements do not differ, then the REGISTRATION ACCEPT message shall be resent and the timer T3550 shall be restarted. In that case, the retransmission counter related to T3550 is not incremented. e) More than one REGISTRATION REQUEST message with 5GS registration type IE set to "initial registration" received and no REGISTRATION ACCEPT message or REGISTRATION REJECT message has been sent. 1) If one or more of the information elements in the REGISTRATION REQUEST message with 5GS registration type IE set to "initial registration" differs from the ones received within the previous REGISTRATION REQUEST message with 5GS registration type IE set to "initial registration", the previously initiated the registration procedure for initial registration shall be aborted and the new the registration procedure for initial registration shall be executed; 2) if the information elements do not differ, then the network shall continue with the previous the registration procedure for initial registration and shall ignore the second REGISTRATION REQUEST message. f) REGISTRATION REQUEST message with 5GS registration type IE set to "initial registration" received in state 5GMM-REGISTERED. If a REGISTRATION REQUEST message with 5GS registration type IE set to "initial registration" is received in state 5GMM-REGISTERED the network may initiate the 5GMM common procedures; if it turned out that the REGISTRATION REQUEST message was sent by a genuine UE that has already been registered, the 5GMM context, if any, are deleted and the new REGISTRATION REQUEST is progressed, otherwise if network considers REGISTRATION REQUEST message was not sent by a genuine UE based on authentication procedure the network shall maintain the 5GMM-context, if any, unchanged. NOTE 1: The network can determine that the UE is genuine by executing the authentication procedure as described in subclause 5.4.1. g) REGISTRATION REQUEST message with 5GS registration type IE set to "mobility registration updating" or "periodic registration updating" received before REGISTRATION COMPLETE message, if the REGISTRATION COMPLETE message is expected. Timer T3550 shall be stopped. The allocated 5G-GUTI in the registration procedure for initial registration shall be considered as valid and the registration procedure for mobility and periodic registration update shall be progressed as described in subclause 5.5.1.3. h) DEREGISTRATION REQUEST message received before REGISTRATION COMPLETE message, if the REGISTRATION COMPLETE message is expected. The AMF shall abort the registration procedure for initial registration and shall progress the de-registration procedure as described in subclause 5.5.2.2. i) UE security capabilities invalid or unacceptable If the REGISTRATION REQUEST message is received with invalid or unacceptable UE security capabilities (e.g. no 5GS encryption algorithms (all bits zero), no 5GS integrity algorithms (all bits zero), mandatory 5GS encryption algorithms not supported or mandatory 5GS integrity algorithms not supported, etc.), the AMF shall return a REGISTRATION REJECT message. NOTE 2: 5GMM cause value to be used in REGISTRATION REJECT message is up to the network implementation. j) Based on operator policy, if the initial registration request from a UE not supporting CAG is rejected due to CAG restrictions, the network shall reject the initial registration with a 5GMM cause value other than the 5GMM cause #76 (Not authorized for this CAG or authorized for CAG cells only). NOTE 3: 5GMM cause #7 (5GS services not allowed), 5GMM cause #11 (PLMN not allowed), 5GMM cause #27 (N1 mode not allowed), 5GMM cause #73 (Serving network not authorized) can be used depending on the subscription of the UE and whether the UE roams or not. | 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.5.1.2.8 |
4,987 | 6.1.3.11 Handling of APN based congestion control | The network may detect and start performing the APN based congestion control when one or more APN congestion criteria as specified in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] are met. The network may store an APN congestion back-off time on a per MS and congested APN basis. If the MS does not provide an APN for the PDP context activation, then the SGSN uses the APN which is used in GGSN/PDN GW selection procedure as congested APN. When APN based congestion control is active, the network may reject session management requests except the modify PDP context requests from UEs or deactivate existing PDP contexts with SM cause value #26 "insufficient resources". In the MS, session management timers T3396 for APN based congestion control are started and stopped on a per APN basis. The APN associated with T3396 is the APN sent by the MS when the PDN connection is established. If no APN is included in the ACTIVATE PDP CONTEXT REQUEST message, then T3396 is associated with no APN. For this purpose the MS shall memorize the APN provided to the network during the PDP context activation. The timer T3396 associated with no APN will never be started due to any SM procedure related to an emergency PDN connection. If the timer T3396 associated with no APN is running, it does not affect the ability of the MS to request an emergency PDN connection. If timer T3396 is running or is deactivated, and the MS is an MS configured to use AC11 – 15 in selected PLMN, then the MS is allowed to initiate any session management procedure for the respective APN. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.11 |
4,988 | 7.2.24 Modify Access Bearers Request | The direction of this message shall be from MME to SGW (see Table 6.1-1). If both the SGW and the MME support the MABR feature (see clause 8.83), an MME may send a Modify Access Bearer Request message on the S11 interface to an SGW as part of the following procedures: - UE triggered Service Request if there is no suspended bearer for that UE, - S1-based Handover without SGW relocation, - X2-based handover without SGW relocation, - Inter-MME E-UTRAN Tracking Area Update without SGW Change, - Intra-MME E-UTRAN Tracking Area Update without SGW Change with Active Flag; - E-UTRAN Initiated E-RAB modification procedure - Mobile Originated Data transport in Control Plane CIoT EPS optimisation with P-GW connectivity - Mobile Terminated Data Transport in Control Plane CIoT EPS optimisation with P-GW connectivity - Connection Resume procedure (see clause 5.3.5A of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]) - Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS optimisation procedure (see clause 5.3.4B.4 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]). if all the following conditions are fulfilled: - the RAT type has not changed; - the Serving Network has not changed; - the MME does not need to report a H(e)NB local IP address and UDP port number information change; - the MME does not need to send UE's location and/or User CSG information or/and UE Time Zone and/or Presence Reporting Area information to the PDN GW; - the MME does not need to send an MME-FQ-CSID as per the requirements specified in 3GPP TS 23.007[ Restoration procedures ] [17]; - ISR is not activated, if the Modify Access Bearers Request is sent as part of a UE triggered Service Request; - ISR was not activated in the old MME which is indicated by the ISRAU flag in the Context Response, if the Modify Access Bearers Request is sent as part of an Inter-MME E-UTRAN Tracking Area Update without SGW change. - the support of ePCO has not be changed during inter MME mobility. - Secondary RAT Usage Data Report(s) is not required to be forwarded to the PGW(s) for any active PDN Connections. The Modify Access Bearers Request message shall include all the bearer contexts of all the PDN connections of the UE. Support of this message is optional for the MME and SGW. Table 7.2.24-1: Information Elements in a Modify Access Bearers Request Table 7.2.24-2: Bearer Context to be modified within Modify Access Bearers Request Table 7.2.24-3: Bearer Context to be removed within Modify Access Bearers Request | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.2.24 |
4,989 | 6.2.7 Narrowbands and widebands | A narrowband is defined as six non-overlapping consecutive physical resource blocks in the frequency domain. The total number of downlink narrowbands in the downlink transmission bandwidth configured in the cell is given by The narrowbands are numbered in order of increasing physical resource-block number where narrowband is composed of physical resource-block indices where and is according to Table 6.2.7-1 for the narrowbands used for PDSCH resource allocation in CEModeB if the higher-layer parameter ce-PDSCH-FlexibleStartPRB-AllocConfig is set, otherwise . If , a wideband is defined as four non-overlapping narrowbands in the frequency domain. The total number of downlink widebands in the downlink transmission bandwidth configured in the cell is given by and the widebands are numbered in order of increasing narrowband number where wideband is composed of narrowband indices where . If , then and the single wideband is composed of the non-overlapping narrowband(s). Table 6.2.7-1: Shift of narrowbands for PDSCH resource allocation in CEModeB when higher layer parameter ce-PDSCH-FlexibleStartPRB-AllocConfig is set. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.7 |
4,990 | V.1.2 Relationship between end-users and subscriber | It is assumed that the user consent is obtained from the end-users. The end-user(s) is the subscriber itself or authorize the subscriber to provide consent on behalf of the end-users. Alternatively, the end-users are authorized by the subscriber to provide the consent. That means user consent is always tied to the subscription information. How authorization is provided between the subscriber and the end-users is out-of-scope of this specification. NOTE: The term end-user is defined in TR 21.905 [1]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | V.1.2 |
4,991 | – SchedulingRequestConfig | The IE SchedulingRequestConfig is used to configure the parameters, for the dedicated scheduling request (SR) resources. SchedulingRequestConfig information element -- ASN1START -- TAG-SCHEDULINGREQUESTCONFIG-START SchedulingRequestConfig ::= SEQUENCE { schedulingRequestToAddModList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddMod OPTIONAL, -- Need N schedulingRequestToReleaseList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestId OPTIONAL -- Need N } SchedulingRequestToAddMod ::= SEQUENCE { schedulingRequestId SchedulingRequestId, sr-ProhibitTimer ENUMERATED {ms1, ms2, ms4, ms8, ms16, ms32, ms64, ms128} OPTIONAL, -- Need S sr-TransMax ENUMERATED { n4, n8, n16, n32, n64, spare3, spare2, spare1} } SchedulingRequestConfig-v1700 ::= SEQUENCE { schedulingRequestToAddModListExt-v1700 SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddModExt-v1700 OPTIONAL -- Need N } SchedulingRequestToAddModExt-v1700 ::= SEQUENCE { sr-ProhibitTimer-v1700 ENUMERATED { ms192, ms256, ms320, ms384, ms448, ms512, ms576, ms640, ms1082, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL -- Need R } -- TAG-SCHEDULINGREQUESTCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,992 | 10.5.6.7 Linked TI | The purpose of the Linked TI information element is to specify the active PDP context from which the PDP address for the new PDP context could be derived by the network. The Linked TI is a type 4 information element with a minimum length of 3 octets and a maximum length of 4 octets. The Linked TI information element is coded as shown in figure 10.5.140/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.140/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Linked TI information element The coding of the TI flag, the TI value and the EXT bit is defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. | 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.6.7 |
4,993 | 9.9.1.4.1 FDD | The following requirements apply to UE Category ≥5. For the parameters specified in table 9.9.1.4.1-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 – Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 – 1 and median CQI1 – 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.9.1.4.1-1: PUCCH 1-1 static test (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.9.1.4.1 |
4,994 | 4.17.11 Indirect Communication without delegated discovery Procedure | This clause provides the call flow for indirect communication model without delegated discovery. Figure 4.17.11-1: Procedure for Indirect Communication without delegated discovery The NF/NF service discovery procedure is defined in clauses 4.17.4 and 4.17.5. In a successful discovery the NF service consumer gets the NF profile(s) matching the search criteria provided in the Nnrf_NFDiscovery_Request message. 1. When the NF Service Consumer needs to send a Service Request and has obtained an endpoint address for the appropriate resources of the NF service producer from the reply to a previous service operation, the NF Service Consumer should indicate that endpoint address as target for the Service Request. Otherwise, if the NF Service Consumer has stored results from the Discovery Procedure, the NF Service Consumer selects an appropriate NF Producer / NF Service Producer instance from the list of NF profiles provided by the NRF. The NF Service Consumer considers the NF and NF service parameters (e.g. TAI, S-NSSAI, locality, priority etc) in the NF profiles. The NF Service consumer requests service from the NF Service producer by sending a service request message to the NF service producer via the SCP and the NF Service Consumer may provide a Routing Binding Indication with the same contents as the previously received Binding Indication. 2. If the Routing Binding Indication is provided by the NF Service Consumer, SCP (re-)selects as specified in Table 6.3.1.0-1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and routes the service request to target accordingly. If the Routing Binding Indication is not provided by the NF Service Consumer, then the SCP routes the service request based on routing information available. 3. The NF Service Producer responds via SCP. 4. SCP forwards the response. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.11 |
4,995 | 5.5.3.3 Derivation of cell measurement results | The network may configure the UE in RRC_CONNECTED to derive RSRP, RSRQ and SINR measurement results per cell associated to NR measurement objects based on parameters configured in the measObject (e.g. maximum number of beams to be averaged and beam consolidation thresholds) and in the reportConfig (rsType to be measured, SS/PBCH block or CSI-RS). The network may configure the UE in RRC_IDLE or in RRC_INACTIVE to derive RSRP and RSRQ measurement results per cell associated to NR carriers based on parameters configured in measIdleCarrierListNR within VarMeasIdleConfig for measurements performed according to 5.7.8.2a. The UE shall: 1> for each cell measurement quantity to be derived based on SS/PBCH block: 2> if nrofSS-BlocksToAverage is not configured in the associated measObject in RRC_CONNECTED or in the associated entry in measIdleCarrierListNR within VarMeasIdleConfig in RRC_IDLE/RRC_INACTIVE; or 2> if absThreshSS-BlocksConsolidation is not configured in the associated measObject in RRC_CONNECTED or in the associated entry in measIdleCarrierListNR within VarMeasIdleConfig in RRC_IDLE/RRC_INACTIVE; or 2> if the highest beam measurement quantity value is below or equal to absThreshSS-BlocksConsolidation: 3> derive each cell measurement quantity based on SS/PBCH block as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215[ NR; Physical layer measurements ] [9]; 2> else: 3> derive each cell measurement quantity based on SS/PBCH block as the linear power scale average of the highest beam measurement quantity values above absThreshSS-BlocksConsolidation where the total number of averaged beams shall not exceed nrofSS-BlocksToAverage, and where each beam measurement quantity is described in TS 38.215[ NR; Physical layer measurements ] [9]; 2> if in RRC_CONNECTED, apply layer 3 cell filtering as described in 5.5.3.2; 1> for each cell measurement quantity to be derived based on CSI-RS: 2> consider a CSI-RS resource to be applicable for deriving cell measurements when the concerned CSI-RS resource is included in the csi-rs-CellMobility including the physCellId of the cell in theCSI-RS-ResourceConfigMobility in the associated measObject; 2> if nrofCSI-RS-ResourcesToAverage in the associated measObject is not configured; or 2> if absThreshCSI-RS-Consolidation in the associated measObject is not configured; or 2> if the highest beam measurement quantity value is below or equal to absThreshCSI-RS-Consolidation: 3> derive each cell measurement quantity based on applicable CSI-RS resources for the cell as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215[ NR; Physical layer measurements ] [9]; 2> else: 3> derive each cell measurement quantity based on CSI-RS as the linear power scale average of the highest beam measurement quantity values above absThreshCSI-RS-Consolidation where the total number of averaged beams shall not exceed nrofCSI-RS-ResourcesToAverage; 2> apply layer 3 cell filtering as described in 5.5.3.2. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.3.3 |
4,996 | 4.3.8.1 PDN GW selection function (3GPP accesses) | The PDN GW selection function allocates a PDN GW that shall provide the PDN connectivity for the 3GPP access. The function uses subscriber information provided by the HSS and possibly additional criteria such as SIPTO/LIPA support per APN configured in the SGSN/MME, UE support for dual connectivity with NR, 15 EPS bearers support by the UE, CIoT EPS Optimisation(s) impacting PDN GW e.g. Non-IP support, Ethernet support, NB-IoT RAT support (for generation of accounting information), etc. NOTE 1: Selection of PDN GWs optimised for different RATs (e.g. NB-IoT) can be achieved by the allocation of different APNs to subscribers allowed to use specific RATs and/or using the UE Usage Type. The criteria for PDN GW selection may include load balancing between PDN GWs. When the PDN GW IP addresses returned from the DNS server include Weight Factors, the MME should use it if load balancing is required. The Weight Factor is typically set according to the capacity of a PDN GW node relative to other PDN GW nodes serving the same APN. For further details on the DNS procedure see TS 29.303[ Domain Name System Procedures; Stage 3 ] [61]. When the MME supports the GTP-C Load Control feature, it takes into account the Load Information received from the PDN GW in addition to the Weight Factors received from the DNS server to perform selection of an appropriate PDN GW. NOTE 2: How Weight Factors can be used in conjunction with Load Information received via GTP control plane signalling is left up to Stage 3. The PDN subscription contexts provided by the HSS contain: - the identity of a PDN GW and an APN (PDN subscription contexts with subscribed PDN GW address are not used when there is interoperation with pre Rel-8 2G/3G SGSN), or - an APN and an indication for this APN whether the allocation of a PDN GW from the visited PLMN is allowed or whether a PDN GW from the home PLMN shall be allocated. Optionally an identity of a PDN GW may be contained for handover with non-3GPP accesses. - optionally for an APN, an indication of whether SIPTO above RAN, or SIPTO at the Local Network, or both, is allowed or prohibited for this APN. - optionally for an APN, an indication of whether LIPA is conditional, prohibited, or only LIPA is supported for this APN. In the case of static address allocation, a static PDN GW is selected by either having the APN configured to map to a given PDN GW, or the PDN GW identity provided by the HSS indicates the static PDN GW. The HSS also indicates which of the PDN subscription contexts is the Default one for the UE. To establish connectivity with a PDN when the UE is already connected to one or more PDNs, the UE provides the requested APN for the PDN GW selection function. If one of the PDN subscription contexts provided by the HSS contains a wild card APN (see TS 23.003[ Numbering, addressing and identification ] [9]), a PDN connection with dynamic address allocation may be established towards any APN requested by the UE. An indication that SIPTO (above RAN, at the local network, or both) is allowed or prohibited for the wild card APN allows or prohibits SIPTO for any APN that is not present in the subscription data. If the HSS provides the identity of a statically allocated PDN GW, or the HSS provides the identity of a dynamically allocated PDN GW and the Request Type indicates "Handover", no further PDN GW selection functionality is performed. If the HSS provides the identity of a dynamically allocated PDN GW, the HSS also provides information that identifies the PLMN in which the PDN GW is located. NOTE 3: The MME uses this information to determine an appropriate APN-OI and S8 protocol type (PMIP or GTP) when the MME and PDN GW are located in different PLMNs. If the HSS provides the identity of a dynamically allocated PDN GW and the Request Type indicates "initial Request", either the provided PDN GW is used or a new PDN GW is selected. When a PDN connection for an APN with SIPTO-allowed is requested, the PDN GW selection function shall ensure the selection of a PDN GW that is appropriate for the UE's location. The PDN GW identity refers to a specific PDN GW. If the PDN GW identity includes the IP address of the PDN GW, that IP address shall be used as the PDN GW IP address; otherwise the PDN GW identity includes an FQDN which is used to derive the PDN GW IP address by using Domain Name Service function, taking into account the protocol type on S5/S8 (PMIP or GTP). NOTE 4: Provision of a PDN GW identity of a PDN GW as part of the subscriber information allows also for a PDN GW allocation by HSS. If the HSS provides a PDN subscription context that allows for allocation of a PDN GW from the visited PLMN for this APN and, optionally, the MME is configured to know that the visited VPLMN has a suitable roaming agreement with the HPLMN of the UE, the PDN GW selection function derives a PDN GW identity from the visited PLMN. If a visited PDN GW identity cannot be derived, or if the subscription does not allow for allocation of a PDN GW from the visited PLMN, then the APN is used to derive a PDN GW identity from the HPLMN. The PDN GW identity is derived from the APN, subscription data and additional information by using the Domain Name Service function. If the PDN GW identity is a logical name instead of an IP address, the PDN GW address is derived from the PDN GW identity, protocol type on S5/S8 (PMIP or GTP) by using the Domain Name Service function. The S8 protocol type (PMIP or GTP) is configured per HPLMN in MME/SGSN. In order to select the appropriate PDN GW for SIPTO above RAN service, the PDN GW selection function uses the TAI (Tracking Area Identity), the serving eNodeB identifier, or TAI together with serving eNodeB identifier depending on the operator's deployment during the DNS interrogation as specified in TS 29.303[ Domain Name System Procedures; Stage 3 ] [61] to find the PDN GW identity. In roaming scenario PDN GW selection for SIPTO is only possible when a PDN GW in the visited PLMN is selected. Therefore in a roaming scenario with home routed traffic, PDN GW selection for SIPTO is not performed. In order to select the appropriate GW for SIPTO at the local network service with a stand-alone GW (with S-GW and L-GW collocated), the PDN GW selection function uses the APN and the Local Home Network ID during the DNS interrogation as specified in TS 29.303[ Domain Name System Procedures; Stage 3 ] [61] to find the PDN GW identity. The Local Home Network ID is provided to the MME by the (H)eNB in every INITIAL UE MESSAGE and every UPLINK NAS TRANSPORT control message as specified in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. The MME uses the Local Home Network ID to determine if the UE has left its current local network and if S-GW relocation is needed. For SIPTO at the Local Network with L-GW function collocated with the (H)eNB the PDN GW selection function uses the L-GW address proposed by the (H)eNB in the S1-AP message, instead of DNS interrogation. In order to select the appropriate L-GW for LIPA service, if permitted by the CSG subscription data and if the UE is roaming, the VPLMN LIPA is allowed, the PDN GW selection function uses the L-GW address proposed by HeNB in the S1-AP message, instead of DNS interrogation. If no L-GW address is proposed by the HeNB and the UE requested an APN with LIPA permissions set to "LIPA-only", the request shall be rejected. If no L-GW address is proposed by the HeNB and the UE requested an APN with LIPA permissions set to "LIPA-conditional", the MME uses DNS interrogation for PDN GW selection to establish a non-LIPA PDN connection. The PDN subscription context for an APN with LIPA permissions set to "LIPA-only" shall not contain a statically configured PDN address or a statically allocated PDN GW. A static PDN address or a static PDN GW address, if configured by HSS for an APN with LIPA permissions set to "LIPA-conditional", is ignored by MME when the APN is established as a LIPA PDN connection. When establishing a PDN connection for a LIPA APN, the VPLMN Address Allowed flag is not considered. The PDN GW domain name shall be constructed and resolved by the method described in TS 29.303[ Domain Name System Procedures; Stage 3 ] [61], which takes into account any value received in the APN-OI Replacement field for non-roaming or home routed traffic. Otherwise, or when the resolution of the above PDN GW domain name fails, the PDN GW domain name shall be constructed by the serving node using the method specified in Annex A of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] and clause 9 of TS 23.003[ Numbering, addressing and identification ] [9]. If the Domain Name Service function provides a list of PDN GW addresses, one PDN GW address is selected from this list. If the selected PDN GW cannot be used, e.g. due to an error, then another PDN GW is selected from the list. The specific interaction between the MME/SGSN and the Domain Name Service function may include functionality to allow for the retrieval or provision of additional information regarding the PDN GW capabilities (e.g. whether the PDN GW supports PMIP-based or GTP-based S5/S8, or both). NOTE 5: The APN as constructed by the MME/SGSN for PDN GW resolution takes into account the APN-OI Replacement field. This differs from the APN that is provided in charging data to another SGSN and MME over the S3, S10 and S16 interfaces as well as to Serving GW and PDN GW over the S11, S4 and S5/S8 interfaces, in that the APN-OI Replacement field is not applied. See clause 5.7.2 of the present document for more details. If the UE provides an APN for a PDN, this APN is then used to derive the PDN GW identity as specified for the case of HSS provided APN if one of the subscription contexts allows for this APN. If there is an existing PDN connection to the same APN used to derive the PDN GW address, the same PDN GW shall be selected. As part of PDN GW selection, an IP address of the assigned PDN GW may be provided to the UE for use with host based mobility as defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2], if the PDN GW supports host-based mobility for inter-access mobility towards accesses where host-based mobility can be used. If a UE explicitly requests the address of the PDN GW and the PDN GW supports host based mobility then the PDN GW address shall be returned to the UE. When DCNs with dedicated PDN GWs are used, the DNS procedure (TS 29.303[ Domain Name System Procedures; Stage 3 ] [61]) for PDN GW selection may be used such that a PDN GW belonging to a DCN serving a particular category of UEs, e.g. identified by UE Usage Type, is selected. When UEs with the same UE Usage type are served by multiple DCNs, it shall also be possible to select the PDN GW belonging to the DCN serving the particular UE. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.8.1 |
4,997 | 5.17.2 Interworking with EPC 5.17.2.1 General | Interworking with EPC in this clause refers to mobility procedures between 5GC and EPC/E-UTRAN, except for clause 5.17.2.4. Network slicing aspects for EPS Interworking are specified in clause 5.15.7 In order to interwork with EPC, the UE that supports both 5GC and EPC NAS can operate in single-registration mode or dual-registration mode: - In single-registration mode, UE has only one active MM state (either RM state in 5GC or EMM state in EPC) and it is either in 5GC NAS mode or in EPC NAS mode (when connected to 5GC or EPC, respectively). UE maintains a single coordinated registration for 5GC and EPC. Accordingly, the UE maps the EPS-GUTI to 5G GUTI during mobility between EPC and 5GC and vice versa following the mapping rules in Annex B. To enable re-use of a previously established 5G security context when returning to 5GC, the UE also keeps the native 5G-GUTI and the native 5G security context when moving from 5GC to EPC. - In dual-registration mode, UE handles independent registrations for 5GC and EPC using separate RRC connections. In this mode, UE maintains 5G-GUTI and EPS-GUTI independently. In this mode, UE provides native 5G-GUTI, if previously allocated by 5GC, for registrations towards 5GC and it provides native EPS-GUTI, if previously allocated by EPC, for Attach/TAU towards EPC. In this mode, the UE may be registered to 5GC only, EPC only, or to both 5GC and EPC. Dual-registration mode is intended for interworking between EPS/E-UTRAN and 5GS/NR. A dual-registered UE should not send its E-UTRA connected to 5GC and E-UTRAN radio capabilities to NR access when connected to 5GS/NR to avoid being handed over to 5GC-connected E-UTRA or to E-UTRAN. NOTE 1: This is to prevent the dual registered UE from being connected to the same E-UTRA cell either connected to EPC or 5GC simultaneously using separate RRC connections via single RAN node as a result of handover. If a dual- registered UE implementation chooses to send its E-UTRA capability when connected to 5GS/NR, the UE and the network behaviour when UE enters a 5GC-connected E-UTRA is not further specified. If however the UE is registered with 5GS/NR only, the UE can send its E-UTRA capability in order to allow inter-RAT handover to E-UTRA/5GC and Dual Connectivity with multiple RATs. If a dual-registered UE had not sent its E-UTRA connected to 5GC and E-UTRAN radio capabilities to 5GS and the UE needs to initiate emergency services, it shall locally re-enable its E-UTRA connected to 5GC and E-UTRAN radio capabilities in order to perform domain selection for emergency services as defined in TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [18]. NOTE 2: However even in this case, the UE is still not expected to connect to E-UTRAN/EPC and E-UTRA/5GC simultaneously using separate RRC connection via single RAN node as a result of the domain selection for emergency services. The support of single registration mode is mandatory for UEs that support both 5GC and EPC NAS. During E-UTRAN Initial Attach, UE supporting both 5GC and EPC NAS shall indicate its support of 5G NAS in UE Network Capability described in clause 4.11.1.5.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. During registration to 5GC, UE supporting both 5GC and EPC NAS shall indicate its support of EPC NAS. NOTE 3: This indication may be used to give the priority towards selection of SMF+PGW-C for UEs that support both EPC and 5GC NAS. If the UE supports 5GC NAS, at PDN connection establishment in EPC, the UE may allocate a PDU Session ID and sends it via PCO, regardless of N1 mode status (i.e. enabled or disabled) in the UE. NOTE 4: UE providing a PDU Session ID at PDN connection establishment even when N1 mode is disabled allows for IP address preservation during EPC to 5GC mobility once the UE re-enables N1 mode. NOTE 5: For the case the MME has selected a standalone PGW for a PDN connection, if the UE re-enables N1 mode and reports the change in UE Network Capability, the MME can initiate PDN disconnection with reactivation required as described in clause 4.11.0a.8 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] to allow selection of SMF+PGW-C thus session continuity at EPC to 5GC mobility. If the EPC supports "Ethernet" PDU Session Type, and the 5GSM Capabilities indicate that the UE supports Ethernet PDN type in EPC, then PDU Session type "Ethernet" is transferred to EPC as "Ethernet". Otherwise, PDU Session types "Ethernet" and "Unstructured" are transferred to EPC as "non-IP" PDN type (when supported by UE and network). If the UE or EPC does not support Ethernet PDN type in EPC, the UE sets the PDN type to non-IP when it moves from 5GS to EPS and after the transfer to EPS, and the UE and the SMF shall maintain information about the PDU Session type used in 5GS, i.e. information indicating that the PDN Connection with "non-IP" PDN type corresponds to PDU Session type Ethernet or Unstructured respectively. This is done to ensure that the appropriate PDU Session type will be used if the UE transfers to 5GS. PDN type "non-IP" is transferred to 5GS as "Unstructured" PDU Session type if it is successfully transferred. It is assumed that if a UE supports Ethernet PDU Session type and/or Unstructured PDU Session type in 5GS it will also support non-IP PDN type in EPS. If this is not the case, the UE shall locally delete any EBI(s) corresponding to the Ethernet/Unstructured PDU Session(s) to avoid that the Ethernet/Unstructured PDU Session(s) are transferred to EPS. MTU size consideration for PDU Sessions and PDN Connections towards a SMF+PGW-C follows the requirements in clause 5.6.10.4. Networks that support interworking with EPC, may support interworking procedures that use the N26 interface or interworking procedures that do not use the N26 interface. Interworking procedures with N26 support provides IP address continuity on inter-system mobility to UEs that support 5GC NAS and EPC NAS and that operate in single registration mode. Networks that support interworking procedures without N26 shall support procedures to provide IP address continuity on inter-system mobility to UEs operating in both single-registration mode and dual-registration mode. In such networks, AMF shall provide the indication that interworking without N26 is supported to UEs during initial Registration in 5GC or MME may optionally provide the indication that interworking without N26 is supported in the Attach procedure in EPC as defined in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. If the network does not support interworking with EPC, network shall not indicate support for "interworking without N26" to the UE. When the HSS+UDM is required to provide the subscription data to the MME, for each APN, only one SMF+PGW-C FQDN and associated APN is provided to the MME according to TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. For interworking without N26 interface: - if the PDU session supports interworking, the SMF+PGW-C stores the SMF+PGW-C FQDN to SMF context in HSS+UDM when the SMF is registered to HSS+UDM. - For an APN, the HSS+UDM selects one of the stored SMF+PGW-C FQDN based on operator's policy. For interworking with N26 interface: - For a DNN, AMF determines PDU session(s) associated with 3GPP access in only one SMF+PGW-C supporting EPS interworking via EBI allocation procedure as described in clause 4.11.1.4.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - If the network supports EPS interworking of non-3GPP access connected to 5GC, the AMF serving 3GPP access notifies the UDM to store the association between DNN and SMF+PGW-C FQDN which supports EPS interworking as Intersystem continuity context, to avoid MME receiving inconsistent SMF+PGW-C FQDN from AMF and HSS+UDM. - The AMF updates Intersystem continuity context if the SMF+PGW-C and DNN association is changed due to the AMF selecting another SMF+PGW-C for EPS interworking for the same DNN. - If the SMF+PGW-C FQDN and associated DNN exists in Intersystem continuity context, the HSS+UDM provides MME with SMF+PGW-C FQDN and associated APN. It does not assume that the HSS+UDM is aware of whether N26 is deployed in the serving network. The HSS+UDM check the Intersystem continuity context first. If no SMF+PGW-C FQDN associated with an DNN exists in Intersystem continuity context, the HSS+UDM selects one of the SMF+PGW-C FQDN for the APN from SMF context based on operator's policy. In entire clause 5.17.2 the terms "initial attach", "handover attach" and "TAU" for the UE procedures in EPC can alternatively be combined EPS/IMSI Attach and combined TA/LA depending on the UE configuration defined in TS 23.221[ Architectural requirements ] [23]. If a UE in MICO mode moves to E-UTRAN connected to EPC and any of the triggers defined in clause 5.4.1.3 occur, then the UE shall locally disable MICO mode and perform the TAU or Attach procedure as defined in clause 5.17.2. The UE can renegotiate MICO when it returns to 5GS during (re-)registration procedure. IP address preservation for IP PDU sessions cannot be ensured on subsequent mobility from EPC/E-UTRAN to GERAN/UTRAN to a UE that had initially registered in 5GS and moved to EPC/E-UTRAN. NOTE 6: The SMF+PGW-C might not include the GERAN/UTRAN PDP Context anchor functionality. Also, 5GC does not provide GERAN/UTRAN PDP Context parameters to the UE when QoS Flows of PDU Session are setup or modified in 5GS. Hence, the UE might not be able to activate the PDP contexts when it transitions to GERAN/UTRAN. IP address preservation for IP PDU sessions cannot be ensured on subsequent mobility from EPC/E-UTRAN to 5GS for a 5GS NAS capable UE that had initially established a PDP context via GERAN/UTRAN and moved to EPC/E-UTRAN. IP address preservation for IP PDU session mobility between EPC/E-UTRAN and 5GS may be re-ensured as specified in clause 5.17.2.4 when UE moves from GERAN/UTRAN into EPC/E-UTRAN. NOTE 7: The PGW acting as a GGSN might not support SMF+PGW-C functionality. GPRS does not support 5GS parameters transfer between UE and SMF+PGW-C (e.g. providing of PDU session ID and 5GS QoS information). When a PDU session is moved from 5GS to EPS, the SMF+PGW-C keeps the registration and subscription in HSS+UDM until the corresponding PDN connection is released. The SMF+PGW-C receives notification of subscription update regarding the 5G parameters (e.g. DNNs, S-NSSAIs) which are associated with the established PDN connection(s) connecting via EPS. If the subscription regarding DNN, QoS profile or PDN connection type associated with the PDN connection is updated, then the MME receives the subscription update and triggers corresponding actions according to TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. If the SMF+PGW-C receives subscription updates (e.g. change of 5GS Subscribed NSSAI) from the UDM the SMF+PGW-C triggers corresponding actions for the PDN connection. This may include (depending on the modified parameter) to: - update the UPF (e.g. for a change of Framed Route information); or - release the PDN connection with an appropriate cause (e.g. for change of EPS/5GS interworking support, for subscription removal of S-NSSAI associated with the PDN connection); - do nothing about changes to DNN and/or PDU Session type that are handled by the MME. If header compression is used for Control Plane CIoT EPS/5GS Optimisations and when the UE moves from EPS to 5GS or from 5GS to EPS, the UE may initiate the PDU Session Modification Procedure or UE requested bearer resource modification procedure to renegotiate the header compression configuration and to establish the compression context between the UE and MME/SMF, see TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. If the UE is moving from 5GS to EPS and the RAT type is also moving from a "broadband" RAT (e.g. NR or WB-E-UTRA) to NB-IoT in EMM-IDLE state, the UE should set the mapped EPS bearer context for which the EPS bearer is a dedicated EPS bearer to state BEARER CONTEXT INACTIVE as for NB-IoT UEs in EPS only support the default bearers. In addition, UE shall locally deactivate the related bearers according to the maximum number of supported UP resources and send the latest bearer context status in the TAU Request. If APN Rate Control is used when the UE moves from EPC to 5GC then the P-GW/SCEF and UE store the current APN Rate Control Status for an APN. If while connected to 5GC the last PDU Session to a DNN that is the same as the APN identified in the APN Rate Control Status is released then the APN Rate Control Status may be stored in the AMF in addition to the Small Data Rate Control Status and the UE discards the APN Rate Control Status. The APN Rate Control Status is stored in the AMF so it can be provided to the MME during mobility to EPC and subsequently applied at establishment of a new first PDN Connection to the same APN, if valid. The APN Rate Control Status is provided to the UPF+PGW-U if a first new PDU Session is established towards the DNN that is the same as the APN identified in the APN Rate Control Status if the UE moves back to EPC, taking into account its validity period. The UE may be provided with initial APN Rate Control parameters by the SMF when a first new PDU Session is established for a DNN and S-NSSAI that supports interworking with EPS and the DNN matches an APN. The SMF provides the APN Rate Control Status for the APN that matches the DNN, if available at the SMF, otherwise the configured APN Rate Control parameters for the APN that matches the DNN are provided as the initially applied parameters. If the initially applied parameters differ from the configured APN Rate Control parameters and the first APN Rate Control validity period expires, the UE is updated with the configured APN Rate Control parameters once the UE has moved to EPC. NOTE 8: If the APN Rate Control Status is provided to a UPF+PGW-U it is not used for Small Data Rate Control while the UE is connected to 5GC, it is only used as the APN Rate Control Status if the UE moves to EPC. NOTE 9: Encoding of APN and DNN specified in TS 23.003[ Numbering, addressing and identification ] [19] allows the comparison of EPS APN and 5GS DNN. If a Service Gap timer is running in the AMF when the UE moves from 5GC to EPC, the AMF stops the running Service Gap timer. If the UE returns to 5GC from EPC the AMF provides the Service Gap Time to the UE as described in clause 5.31.16. If a Service Gap timer is running in the MME when the UE moves from EPC to 5GC, the MME stops the running Service Gap timer. If the UE returns to E-UTRAN connected to EPC from 5GC the MME provides the Service Gap Time to the UE as described in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. If a Service Gap timer is running in the UE when the UE moves to from 5GC to EPC and if Service Gap Time is received from the MME, the UE stores the received Service Gap Time for later use when the timer needs to be started next time, and the Service Gap timer that was started before the system change is kept running in the UE and applied for EPC. If a Service Gap timer is running in the UE when the UE moves to 5GC and if Service Gap Time is received from the AMF, the UE stores the received Service Gap Time for later use when the timer needs to be started next time, and the Service Gap timer that was started before the system change is kept running in the UE and applied in 5GS. For UE currently served by EPC, a SMF+PGW-C may support L2TP tunnelling on N6, as described in clause 5.8.2.16. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.2 |
4,998 | 4.15.13.3.3 Member UE Selection Assistance with QoS filtering criteria for real-time QoS Monitoring | At the reception of Nnef_MemberUESelectionAsistance_Subscribe request of step 1, in order to detect the list of UEs that fulfil the QoS filtering criteria in real time, NEF performs real-time QoS monitoring. Unless the QoS flow to be monitored is associated with a default QoS flow, QoS Monitoring needs to be activated in SMF for that QoS Flow before (e.g. by AF Session with required QoS) (see clause 4.15.4.5.1 for details). Figure 4.15.13.3.3-1: 5GC assistance to Member UE selection for real-time QoS monitoring 1. AF subscribes to the Member UE selection assistance functionality by sending Nnef_MemberUESelectionAssistance_subscribe request including its AF ID, a list of target UE(s) and the QoS filtering criteria. 2. NEF uses the AF ID to verify the authorization of the AF request and identifies which information needs to be collected based on the QoS filtering criteria provided by the AF. 3. If S-NSSAI/DNN are not included in the request from the AF, the NEF derives the S-NSSAI and DNN which this Application has access to. NEF discovers the SMFs that are deployed in the Area of Interest by querying UDM and NRF. The NEF may also restrict the discovery to those SMFs that serve some S-NSSAI and DNN combination. 4. For each target SMF, NEF sends an Nsmf_EventExposure_Subscribe request (Event: 'QoS monitoring', target member UEs, optionally a traffic descriptor (e.g. Application ID), optionally indication for default QoS flows monitoring, S-NSSAI, DNN, Notification Target Address set to NEF, etc.). Alternatively, NEF may send an Nudm_EventExposure_Subscribe request to the UDM (not shown in Figure 4.15.13.3.3-1). 5. The SMF may need to send an N4 Session Modification request to UPF for requesting the QoS monitoring for certain flows. 6. UPF sends an Nupf_EventExposure_Notify request to NEF including an Event Exposure notification, according to the subscription received from SMF. 7. Based on the Event Exposure reports received from the UPFs, NEF consolidates the received results and derives the list(s) of candidate UE(s) and additional information which fulfil the QoS filtering criteria provided by the AF. 8. NEF sends a Nnef_MemberUESelectionAssistance_Notify request to the AF including the list(s) of candidate UE(s) and additional information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.13.3.3 |
4,999 | 4.16.8.5 Spending Limit Report | This clause describes the signalling flow for the CHF to notify the change of the status of the subscribed policy counters available at the CHF for that subscriber. Alternatively, the signalling flow can be used by the CHF to provide one or more pending statuses for a subscribed policy counter together with the time they have to be applied. Figure 4.16.8.5.1: Spending Limit Report 1. The CHF detects that the status of a policy counter(s) has changed and the PCF subscribed to notifications of changes in the status of this policy counter. Alternatively, the CHF may detect that a policy counter status will change at a future point in time and decides to instruct the PCF to apply one or more pending statuses for a requested policy counter. 2. The CHF sends Nchf_SpendingLimitControl_Notify with the SUPI, Notification Target Address and in the Event Information the policy counter status and optionally pending policy counter statuses and their activation times, for each policy counter that has changed and for which the PCF subscribed to spending limit reporting. Alternatively, the CHF sends one or more pending statuses for any of the subscribed policy counters together with the time they have to be applied. 3. The PCF acknowledges sending Nchf_SpendingLimitControl_Notify response and takes that information into account as input for a policy decision. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.8.5 |
5,000 | 21.2.3 Format of HA-APN Operator Identifier | The HA-APN Operator Identifier is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label distinguishes the domain name as a HA-APN. For each operator, there is a default HA-APN Operator Identifier (i.e. domain name). This default HA-APN Operator Identifier is derived from the IMSI as follows: "ha-apn.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" where: "mnc" and "mcc" serve as invariable identifiers for the following digits. <MNC> and <MCC> are derived from the components of the IMSI defined in clause 2.2. Alternatively, the default HA-APN Operator Identifier is derived using the MNC and MCC of the VPLMN. In order to guarantee inter-PLMN DNS translation, the <MNC> and <MCC> coding used in the "ha-apn.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" format of the HA-APN OI shall be: - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the HA-APN OI. As an example, the HA-APN OI for MCC 345 and MNC 12 is coded in the DNS as: "ha-apn.mnc012.mcc345.pub.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 21.2.3 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.