Search is not available for this dataset
doc_id
int64 1
6.72k
β | Section
stringlengths 5
247
β | Content
stringlengths 501
147k
β | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
β |
|---|---|---|---|---|---|---|---|
3,001 | 5.15.11.3 Network Slice Admission Control for Roaming 5.15.11.3.0 General | In the case of roaming, depending on operator's policy, a roaming agreement or an SLA between the VPLMN and the HPLMN, NSAC of roaming UEs is performed by one of the following modes of NSAC admission: - VPLMN NSAC Admission; or - VPLMN with HPLMN assistance NSAC Admission; or - HPLMN NSAC Admission. The VPLMN (AMF and SMF) identifies the mode to apply from the AMF subscription data at UE registration, and from the SMF subscription data at PDU session establishment. For all the above modes, for NSAC of roaming UEs for maximum number of UEs per network slice and/or maximum number of PDU Sessions per network slice managed by the VPLMN, each S-NSSAI of the HPLMN that is subject to NSAC is mapped to a corresponding S-NSSAI of the VPLMN subject to NSAC. For both VPLMN NSAC Admission and VPLMN with HPLMN assistance NSAC Admission modes, each configured S-NSSAI that is subject to NSAC and that is mapped from the HPLMN S-NSSAI, the SMF performs NSAC for home routed PDU sessions according to the principles described in clause 5.15.11.2. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.3 |
3,002 | D.2 Factory automation β other use cases D.2.0 General | Factory automation encompasses all types of production that result in discrete products: cars, chocolate bars, etc. Automation that addresses the control of flows and chemical reactions is referred to as process automation (see clause D.3). Discrete automation requires communications for supervisory and open-loop control applications, as well as process monitoring and tracking of operations inside an industrial plant. In these applications, a large number of sensors, which are distributed over the plant, forward measurement data to process controllers on a periodic or event-driven base. Traditionally, wireline field bus technologies have been used to interconnect sensors and control equipment. Due to the sizable extension of a plant (up to10 km2), the large number of sensors, rotary joints, and the high deployment complexity of wired infrastructure, wireless solutions have made inroads into industrial process automation. The related use cases require support of a large number of sensor devices per plant, as well as high communication service availability (99,99%). Furthermore, power consumption is relevant since some sensor devices are battery-powered with a targeted battery lifetime of several years (while providing measurement updates every few seconds). Range also becomes a critical factor due to the low transmit power levels of the sensors, the large size of the plant, and the high-reliability requirements on transport. End-to-end latency requirements typically range between 10 ms and 1 s. User-experienced data rates can be rather low since each transaction typically comprises less than 256 bytes. However, there has been a shift from field busses featuring somewhat modest data rates (~ 2 Mbit/s) to those with higher data rates (~ 10 Mbit/s) due to the increasing number of distributed applications and "data-hungry" applications. An example for the latter is the visual control of production processes. For this application, the user experienced data rate is typically around 10 Mbit/s and the transmitted packets are much larger than what was stated earlier. Existing wireless technologies for factory automation rely on unlicensed bands. Communication is therefore vulnerable to interference caused by other technologies (e.g. WLAN). With the stringent requirements on transport reliability, such interference is detrimental to proper operation. The use of licensed spectrum could overcome the vulnerability to same-band interference and therefore enable higher reliability. Utilization of licensed spectrum can be confined to those events where high interference bursts in unlicensed bands jeopardizes communication service availability and end-to-end latency constraints. This allows sharing the licensed spectrum between process automation and conventional mobile services. Multi-hop topologies can provide range extension and mesh topologies can increase reliability through path redundancy. Clock synchronization will be highly beneficial since it enables more power-efficient sensor operation and mesh forwarding. The corresponding industrial communication solutions are referred to as fieldbuses. The related standard suite is IEC 61158. A typical discrete automation application supports downstream and upstream data flows between process controllers and sensors/actuators. The communication consists of individual transactions. The process controller resides in the plant network. This network interconnects via base stations to the wireless (mesh-) network which hosts the sensor/actuator devices. Typically, each transaction uses less than 256 bytes. An example of a controller-initiated transaction service flow is: 1. The process controller requests sensor data (or an actuator to conduct actuation). The request is forwarded via the plant network and the wireless network to the sensors/actuators. 2. The sensors/actuators process the request and send a replay in upstream direction to the controller. This reply can contain an acknowledgement or a measurement reading. An example of a sensor/actuator device-initiated transaction service flow: 1. The sensor sends a measurement reading to the process controller. The request is forwarded via the wireless (mesh) network and the plant network. 2. The process controller can send an acknowledgement in opposite direction. For both controller- and sensor/actuator-initiated service flows, upstream and downstream transactions can occur asynchronously. Figure D.2.0-1 depicts how communication can occur in discrete automation. In this use case, communication runs between process controller and sensor/actuator device via the plant network and the wireless (mesh) network. The wireless (mesh) network can also support access for handheld devices for supervisory control or process monitoring purposes. Figure D.2.0-1: Communication path for service flows between process controllers and sensor/actuator devices. Left-hand side: Step 1 (red) β the sensor/actuator (S/A) sends measurement report autonomously, Step 2 (blue) controller acknowledges. Right-hand side: Step 1 (red) - controller requests sensor data (or an actuator to conduct actuation), Step 2 (blue): S/A sends measurement information (or acknowledges actuation) to controller. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | D.2 |
3,003 | 15.3.1.3 Application layer initialization | Once SCTP connectivity has been established, the NG-RAN node and the AMF shall exchange application level configuration data over NGAP with the NG Setup procedure, which is needed for these two nodes to interwork correctly on the NG interface: - The NG-RAN node provides the relevant configuration information to the AMF, which includes list of supported TA(s), etc.; - The AMF provides the relevant configuration information to the NG-RAN node, which includes PLMN ID, etc.; - When the application layer initialization is successfully concluded, the dynamic configuration procedure is completed and the NG-C interface is operational. After the application layer initialization is successfully completed, the AMF may add or update or remove SCTP endpoints to be used for NG-C signalling between the AMF and the NG-RAN node pair as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.3.1.3 |
3,004 | 5.4.1 UL Grant reception | In order to transmit on the UL-SCH the MAC entity must have a valid uplink grant (except for non-adaptive HARQ retransmissions) which it may receive dynamically on the PDCCH or in a Random Access Response or which may be configured semi-persistently or preallocated by RRC or provided by RRC for transmission using PUR (see clause 5.4.7). To perform requested transmissions, the MAC layer receives HARQ information from lower layers. When the physical layer is configured for uplink spatial multiplexing, the MAC layer can receive up to two grants (one per HARQ process) for the same TTI from lower layers. If the MAC entity has a C-RNTI, a Semi-Persistent Scheduling C-RNTI, a UL Semi-Persistent Scheduling V-RNTI, a AUL C-RNTI, or a Temporary C-RNTI, the MAC entity shall for each TTI and for each Serving Cell belonging to a TAG that has a running timeAlignmentTimer and for each grant received for this TTI and for each SPS configuration that is indicated by the PDCCH addressed to UL Semi-Persistent Scheduling V-RNTI; or if the MAC entity has Preconfigured Uplink Resource RNTI, the MAC entity shall for each TTI and for each grant received for this TTI: - if an uplink grant for this TTI and this Serving Cell has been received on the PDCCH for the MAC entity's C-RNTI, Preconfigured Uplink Resource RNTI or Temporary C-RNTI; or - if an uplink grant for this TTI has been received in a Random Access Response: - if the uplink grant is for MAC entity's C-RNTI and if the previous uplink grant delivered to the HARQ entity for the same HARQ process was either an uplink grant received for the MAC entity's Semi-Persistent Scheduling C-RNTI, for the MAC entity's UL Semi-Persistent Scheduling V-RNTI, or a configured uplink grant for which the UL HARQ operation was not autonomous: - consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the NDI. - deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI. - else, if an uplink grant for this TTI has been received for this Serving Cell on the PDCCH for the MAC entity's Semi-Persistent Scheduling C-RNTI or for the MAC entity's UL Semi-Persistent Scheduling V-RNTI; or if an uplink grant for this TTI has been received for this Serving Cell on the PDCCH for the MAC entity's AUL C-RNTI: - if the NDI in the received HARQ information is 1: - consider the NDI for the corresponding HARQ process not to have been toggled; - deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI. - else if the NDI in the received HARQ information is 0: - if PDCCH contents indicate AUL release: - trigger an AUL confirmation; - if an uplink grant for this TTI has been configured: - consider the NDI bit for the corresponding HARQ process to have been toggled; - deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI; - else if PDCCH contents indicate AUL activation: - trigger an AUL confirmation; - store the uplink grant and the associated HARQ information as configured uplink grant; - initialise (if not active) or re-initialise (if already active) the configured uplink grant to start in this TTI and to recur according to rules in clause 5.23; - consider the NDI bit for the corresponding HARQ process to have been toggled; - deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI. - else if PDCCH contents indicate SPS release: - if the MAC entity is configured with skipUplinkTxSPS: - trigger an SPS confirmation; - if an uplink grant for this TTI has been configured: - consider the NDI bit for the corresponding HARQ process to have been toggled; - deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI; - else: - clear the corresponding configured uplink grant (if any). - else: - if the MAC entity is configured with skipUplinkTxSPS: - trigger an SPS confirmation; - store the uplink grant and the associated HARQ information as configured uplink grant; - initialise (if not active) or re-initialise (if already active) the configured uplink grant to start in this TTI, or in TTI according to N=0 in clause 5.10.2 for short TTI, and to recur according to rules in clause 5.10.2; - if UL HARQ operation is asynchronous, set the HARQ Process ID to the HARQ Process ID associated with this TTI; - consider the NDI bit for the corresponding HARQ process to have been toggled; - deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI. - else, if an uplink grant for this TTI has been configured for the Serving Cell and if UL HARQ operation is autonomous for the corresponding HARQ process: - if the HARQ_FEEDBACK is set to ACK for the corresponding HARQ process or if there is no uplink grant previously delivered to the HARQ entity for the same HARQ process: - consider the NDI bit for the corresponding HARQ process to have been toggled. - if the aul-RetransmissionTimer is not running: - if there is no uplink grant previously delivered to the HARQ entity for the same HARQ process; or - if the previous uplink grant delivered to the HARQ entity for the same HARQ process was not an uplink grant received for the MAC entity's C-RNTI; or - if the HARQ_FEEDBACK is set to ACK for the corresponding HARQ process: - deliver the configured uplink grant, and the associated HARQ information to the HARQ entity for this TTI. - else: - if this Serving Cell is the SpCell and an uplink grant for this TTI has been preallocated for the SpCell; or - except for preconfigured uplink grant for PUR, if an uplink grant for this TTI has been configured for this Serving Cell: - if UL HARQ operation is asynchronous, set the HARQ Process ID to the HARQ Process ID associated with this TTI; - consider the NDI bit for the corresponding HARQ process to have been toggled; - deliver the configured or preallocated uplink grant, and the associated HARQ information to the HARQ entity for this TTI. NOTE 1: The period of configured uplink grants is expressed in TTIs. NOTE 2: If the MAC entity receives both a grant in a Random Access Response and a grant for its C-RNTI or Semi persistent scheduling C-RNTI requiring transmissions on the SpCell in the same UL subframe, the MAC entity may choose to continue with either the grant for its RA-RNTI or the grant for its C-RNTI or Semi persistent scheduling C-RNTI. NOTE 3: When a configured uplink grant is indicated during a measurement gap and indicates an UL-SCH transmission during a measurement gap, the MAC entity processes the grant but does not transmit on UL-SCH. When a configured uplink grant is indicated during a Sidelink Discovery gap for reception and indicates an UL-SCH transmission during a Sidelink Discovery gap for transmission with a SL-DCH transmission, the MAC entity processes the grant but does not transmit on UL-SCH. When a configured uplink grant indicates an UL-SCH transmission during a V2X sidelink communication transmission and transmission of V2X sidelink communication is prioritized as described in clause 5.14.1.2.2, the MAC entity processes the grant but does not transmit on UL-SCH. NOTE 4: The NDI transmitted in the PDCCH for the MAC entity's AUL C-RNTI is set to '0' (TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [5]). Except for NB-IoT, for configured uplink grants without harq-ProcID-offset, if UL HARQ operation is not autonomous, the HARQ Process ID associated with this TTI is derived from the following equation for asynchronous UL HARQ operation: - if the TTI is a subframe TTI: - HARQ Process ID = [floor(CURRENT_TTI/semiPersistSchedIntervalUL)] modulo numberOfConfUlSPS-Processes, where CURRENT_TTI=[(SFN * 10) + subframe number] and it refers to the subframe where the first transmission of a bundle takes place. - else: - HARQ Process ID = [floor(CURRENT_TTI/semiPersistSchedIntervalUL-sTTI)] modulo numberOfConfUlSPS-Processes-sTTI, where CURRENT_TTI = [(SFN * 10 * sTTI_Number_Per_Subframe) + subframe number * sTTI_Number_Per_Subframe + sTTI_number] and it refers to the short TTI occasion where the first transmission of a bundle takes place. Refer to 5.10.2 for sTTI_Number_Per_Subframe and sTTI_number. For preallocated uplink grants the HARQ Process ID associated with this TTI is derived from the following equation for asynchronous UL HARQ operation: HARQ Process ID = [floor(CURRENT_TTI/ul-SchedInterval)] modulo numberOfConfUL-Processes, where CURRENT_TTI=subframe number and it refers to the subframe where the first transmission of a bundle takes place. For configured uplink grants, if UL HARQ operation is autonomous, the HARQ Process ID associated with this TTI for transmission on this Serving Cell is selected by the UE implementation from the HARQ process IDs that are configured for autonomous UL HARQ operation by upper layers in aul-HARQ-Processes (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). For configured uplink grants with harq-ProcID-offset, the HARQ Process ID associated with this TTI is derived from the following equation for asynchronous UL HARQ operation: - if the TTI is a subframe TTI: - HARQ Process ID = [floor(CURRENT_TTI/semiPersistSchedIntervalUL)] modulo numberOfConfUlSPS-Processes + harq-ProcID-offset, where CURRENT_TTI = [(SFN * 10) + subframe number] and it refers to the subframe where the first transmission of a bundle takes place. - else: - HARQ Process ID = [floor(CURRENT_TTI/semiPersistSchedIntervalUL-sTTI)] modulo numberOfConfUlSPS-Processes-sTTI + harq-ProcID-offset, where CURRENT_TTI = [(SFN * 10 * sTTI_Number_Per_Subframe) + subframe number * sTTI_Number_Per_Subframe + sTTI_number] and it refers to the short TTI occasion where the first transmission of a bundle takes place. Refer to 5.10.2 for sTTI_Number_Per_Subframe and sTTI_number. For NB-IoT, for configured uplink grants for BSR, the HARQ Process ID is set to 0. If the MAC entity is configured with Short Processing Time or short TTI and if current_TTI is a subframe TTI, the HARQ Process ID associated with this TTI is derived from the following equation for synchronous UL HARQ operation: HARQ Process ID = [SFN * number_of_UL_PUSCH_SFs_per_radio_frame + index_of_UL_PUSCH_SF] modulo number_of_UL_HARQ_processes. where number_of_UL_PUSCH_SFs_per_radio_frame is the number of subframes that can be used for PUSCH (UL PUSCH subframe) per radio frame: - For FDD serving cells and serving cells operating according to Frame structure Type 3, all 10 subframes in a radio frame represent UL PUSCH subframes; - For TDD serving cells, all uplink subframes of the TDD UL/DL configuration indicated by tdd-Config, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] of the cell represent UL PUSCH subframes and additionally the subframes including UpPTS if the cell is configured with symPUSCH-UpPts-r14; and index_of_UL_PUSCH_SF is the index of a subframe that can be used for PUSCH within the radio frame, and number_of_UL_HARQ_processes is the number of parallel HARQ processes per HARQ entity for subframe TTI as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], clause 8. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.1 |
3,005 | 4.13.6.1 EPS fallback for IMS voice | Figure 4.13.6.1-1 describes the EPS fallback procedure for IMS voice. When the UE is served by the 5G System, the UE has one or more ongoing PDU Sessions each including one or more QoS Flows. The serving PLMN AMF has sent an indication towards the UE during the Registration procedure that IMS voice over PS session is supported, see clause 5.16.3.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the UE has registered in the IMS. If N26 is not supported, the serving PLMN AMF sends an indication towards the UE during the Registration procedure that interworking without N26 is supported, see clause 5.17.2.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Figure 4.13.6.1-1: EPS Fallback for IMS voice 1. UE camps on NG-RAN in the 5GS and an MO or MT IMS voice session establishment has been initiated. 2. Network initiated PDU Session modification to setup QoS flow for voice reaches the NG-RAN (see N2 PDU Session Request in clause 4.3.3). 3. NG-RAN is configured to support EPS fallback for IMS voice and decides to trigger fallback to EPS, taking into account UE capabilities, indication from AMF that "Redirection for EPS fallback for voice is possible" (received as part of initial context setup, handover resource allocation or path switch request acknowledge as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]), network configuration (e.g. N26 availability configuration) and radio conditions. If NG-RAN decides not to trigger fallback to EPS, then the procedure stops here and following steps are not executed. NG-RAN may initiate measurement report solicitation from the UE including E-UTRAN as target. NOTE 1: If AMF has indicated that "Redirection for EPS fallback for voice is not possible", then EPS fallback for IMS voice is not performed in step 5. If NG-RAN has not received indication "Redirection for EPS fallback for voice", the decision to execute EPS fallback for IMS voice or not is based on network configuration (e.g. based on N26 availability and other criteria). 4. NG-RAN responds indicating rejection of the PDU Session modification to setup QoS flow for IMS voice received in step 2 by PDU Session Modification Response message towards the SMF+PGW-C (or H-SMF+P-GW-C via V-SMF, in the case of home routed roaming scenario) via AMF with an indication that mobility due to fallback for IMS voice is ongoing. The SMF+PGW-C maintains the PCC rule(s) associated with the QoS Flow(s) and reports the EPS Fallback event to the PCF if PCF has subscribed to this event. 5. NG-RAN initiates either handover (see clause 4.11.1.2.1), or AN Release via inter-system redirection to EPS (see clause 4.2.6 and clause 4.11.1.3.2), taking into account UE capabilities. The SMF+PGW-C reports change of the RAT type if subscribed by PCF as specified in clause 4.11.1.2.1, or clause 4.11.1.3.2.6. When the UE is connected to EPS, either 6a or 6b is executed 6a. In the case of 5GS to EPS handover, see clause 4.11.1.2.1 and in the case of inter-system redirection to EPS with N26 interface, see clause 4.11.1.3.2. In either case the UE initiates TAU procedure and the UE includes active flag in the request in the case of inter-system redirection to EPS; or 6b. In the case of inter-system redirection to EPS without N26 interface, see clause 4.11.2.2. If the UE supports Request Type flag "handover" for PDN connectivity request during the attach procedure as described in clause 5.3.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] and has received the indication that interworking without N26 is supported, then the UE initiates Attach with PDN connectivity request with request type "handover". In the case of inter-system redirection for the emergency service, the UE uses the emergency indication in the RRC message as specified in clause 6.2.2 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] and E-UTRAN provides the emergency indication to MME during Tracking Area Update or Attach procedure. For the handover procedure see clause 4.11.1.2.1, step 1. 7. After completion of the mobility procedure to EPS or as part of the 5GS to EPS handover procedure, the SMF+PGW-C re-initiates the setup of the dedicated bearer(s) for the maintained PCC rule(s) in step 4 including of the dedicated bearer for IMS voice, mapping the 5G QoS to EPC QoS parameters as specified in clause 4.11.1.2.1. The SMF+PGW-C reports about Successful Resource Allocation and Access Network Information if subscribed by PCF. The IMS signalling related to IMS voice call establishment continues after step 1 as specified in the TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [55]. At least for the duration of the voice call in EPS the E-UTRAN is configured to not trigger any handover to 5GS. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.6.1 |
3,006 | 4.2.2.3.3 Network-initiated Deregistration | The procedure depicted in Figure 4.2.2.3.3-1 shows Network-initiated Deregistration procedure. The AMF can initiate this procedure for either explicit (e.g. by O&M intervention or if the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE or the UE's registered PLMN is not allowed to operate in the present UE location or if a disaster condition is no longer being applicable, the AMF initiates Network-initiated Deregistration to trigger the return of UEs to the PLMN that had a Disaster Condition) or implicit (e.g. expiring of Implicit Deregistration timer). The UDM can trigger this procedure for operator-determined purposes (e.g. if a disaster condition is no longer being applicable as specified in clause 5.40.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) to request the removal of a subscriber's RM context and PDU Session(s) of the UE. If the Network-initiated Deregistration procedure is triggered for MBSR IAB-UE that is registered with authorization to act as MBSR, the AMF behaves as described in clause 5.35A.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Figure 4.2.2.3.3-1: Network-initiated Deregistration 1. [Conditional] If the UDM wants to request the immediate deletion of a subscriber's RM contexts and PDU Sessions, the UDM shall send a Nudm_UECM_DeregistrationNotification (SUPI, Access Type, Removal Reason) message with Removal Reason set to Subscription Withdrawn to the registered AMF. The Access Type may indicate 3GPP Access, non-3GPP Access or both. 2. If the AMF receives Nudm_UECM_DeregistrationNotification in Step 1 with Removal Reason as Subscription Withdrawn, the AMF executes Deregistration procedure over the access(es) the Access Type indicates. The AMF-initiated Deregistration procedure is either explicit (e.g. by O&M intervention or if the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE) or implicit. The AMF does not send the Deregistration Request message to the UE for Implicit Deregistration. If the UE is in CM-CONNECTED state, the AMF may explicitly deregister the UE by sending a Deregistration Request message (Deregistration type, Access Type, [list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value]) to the UE. The Deregistration type may be set to Re-registration in which case the UE should re-register at the end of the Deregistration procedure. Access Type indicates whether Deregistration procedure applies to the 3GPP access or non-3GPP access, or both. If the Deregistration Request message is sent over 3GPP access and the UE is in CM-IDLE state in 3GPP access, the AMF pages the UE. The list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value, is provided if the AMF determines that no S-NSSAI can be provided to the UE in the Allowed NSSAI. If the UE has established PDU Session associated with emergency service, the AMF shall not initiate Deregistration procedure. In this case, the AMF performs network requested PDU Session Release for any PDU session associated with non-emergency service as described in clause 4.3.4. For NR satellite access, the AMF initiates Network-initiated Deregistration if it detects that the UE's registered PLMN is not allowed to operate in the present UE location. In this case, the AMF shall provide the appropriate cause value indicating the PLMN is not allowed to operate in the present UE location, see clause 5.4.11.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the network de-registration is triggered for a UE registered for Disaster Roaming due to a disaster condition no longer being applicable, the Deregistration Request shall contain the cause value "PLMN not allowed" and include a disaster return wait range as described in clause 5.5.2.3.1 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25] and as specified in clause 5.40.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the network, shall organise the return of the Disaster Roaming UEs in a manner that does not cause overload (e.g. of signalling) in the PLMN that previously had the Disaster Condition. If the MBSR authorization state changes for a MBSR (IAB-UE) registered in network as specified in clause 5.35A.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], based on operator configuration, the AMF triggers Deregistration procedure. 3. [Conditional] If the Deregistration procedure is triggered by UDM (Step 1), the AMF acknowledges the Nudm_UECM_DeRegistrationNotification to the UDM. If Access Type indicates 3GPP Access or non-3GPP Access and AMF does not have UE context for another access type, or if Access Type indicates both, the AMF unsubscribes with the UDM using Nudm_SDM_Unsubscribe service operation. 4. [Conditional] If the UE has any established PDU Session over the target access for deregistration indicated in step 2, then step 2 ~ step 5 of UE-initiated Deregistration procedure in clause 4.2.2.3.2 is performed. 5. [Conditional] As in step 6 of Figure 4.2.2.3.2-1. 5a. [Conditional] As in step 6a of Figure 4.2.2.3.2-1. 6. [Conditional] If the UE receives the Deregistration Request message from the AMF in step 2, the UE sends a Deregistration Accept message to the AMF any time after step 2. The NG-RAN forwards this NAS message to the AMF along with the TAI+ Cell identity of the cell which the UE is using. 7. [Conditional] AMF to AN: N2 UE Context Release Request (Cause): as in step 8 of Figure 4.2.2.3.2. If the UE is deregistered over only 3GPP access or non-3GPP access and the AMF does not have UE context for the other, or if the procedure applies to both access types, then at any time, AMF can unsubscribe from the UDM, otherwise the AMF can deregister from UDM using Nudm_UECM_Deregistration request by indicating its associating access type. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.2.3.3 |
3,007 | 5.2.2.2.11 Namf_Communication_CreateUEContext service operation | Service operation name: Namf_Communication_CreateUEContext Description: This service operation is used by a source AMF to create the UE context in a target AMF during handover procedures or an initial AMF to relocate the UE context to a target AMF during inter PLMN handover procedure. Input, Required: 5G-GUTI, UE context of the identified UE. As described in Table 5.2.2.2.2-1, the UE context may include the SUPI, DRX parameters, AM policy information, UE Radio Capability ID, PCF ID, UE network capability, used N1 security context information, event subscriptions by other consumer NF and the list of SM PDU Session IDs along with the SMF handling the PDU Session, N2 information including source to target RAN transparent container, Endpoint information of S-AMF to receive N2 information notification about handover complete (i.e. N2 notify URI). Input, Optional: allocated EBI information, PCF ID, MS Classmark 2, STN-SR, C MSISDN, the Supported Codec IE, NWDAF ID(s) (i.e. Instance ID or Set ID)with the corresponding Subscription Correlation ID(s), Analytics ID (s) and Analytics specific data as defined in Table 5.2.2.2.2-1. Output, Required: Cause, N2 information including Target to Source transparent container, N2 SM information (PDU Sessions failed to be setup list and the N3 DL forwarding information), handle for the UE context created, PCF ID. Output, Optional: Target AMF ID. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.11 |
3,008 | 8.2.4 Intra-CU topological redundancy procedure | The intra-CU topological redundancy procedure enables the establishment and release of redundant paths in the IAB-topology underneath the same IAB-donor-CU. The redundant paths may use different IAB-donor-DUs. They may also have common intermediate nodes. Since topological redundancy uses NR-DC for the IAB-MT, it is only supported for IAB-nodes operating in SA mode. Figure 8.2.4-1 shows an example for an IAB topology, where one IAB-node, referred to as the dual-connecting IAB-node, has two paths towards the IAB-donor via different IAB-donor-DUs. Figure 8.2.4-1: Example for IAB topology with two redundant paths Figure 8.2.4-2: Procedure for establishment of redundant path in IAB topology Figure 8.2.4-2 shows the procedure for the establishment of the second path. This procedure has the following steps: 1. The dual-connecting IAB-MT sends a MeasurementReport message to the first parent node IAB-DU. This report is based on a Measurement Configuration the dual-connecting IAB-MT received from the IAB-donor-CU before. 2. The first parent node IAB-DU sends an UL RRC MESSAGE TRANSFER message to the IAB-donor-CU to convey the received MeasurementReport. 3. The IAB-donor-CU sends the UE CONTEXT SETUP REQUEST message to the second parent node IAB-DU, to create the UE context for the dual-connecting IAB-MT and to set up one or more bearers. These bearers can be used by the dual-connecting IAB-MT for its own signalling, and, optionally, data traffic. 4. The second parent node IAB-DU responds to the IAB-donor-CU with a UE CONTEXT SETUP RESPONSE message. 5. The IAB-donor-CU sends a DL RRC MESSAGE TRANSFER message to the first parent node IAB-DU, which includes a generated RRCReconfiguration message. The RRCReconfiguration message may contain one or more TNL address(es) for the dual-connecting IAB-DU, which are anchored at the second-path IAB-donor-DU. The IAB-donor-CU can proactively obtain these TNL addresses from the second-path IAB-donor-DU. In case IPsec tunnel mode is used to protect the F1 and non-F1 traffic, the allocated TNL address is the outer IP address. The TNL address allocation is not necessary if the first and second paths use the same IAB-donor-DU. 6. The first parent node IAB-DU forwards the received RRCReconfiguration message to the dual-connecting IAB-MT. 7. The dual-connecting IAB-MT responds to the first parent node IAB-DU with an RRCReconfigurationComplete message. 8. The first parent node IAB-DU sends an UL RRC MESSAGE TRANSFER message to the IAB-donor-CU, to convey the received RRCReconfigurationComplete message. 9. A Random Access procedure is performed at the second parent node IAB-DU. 10. The IAB-donor-CU configures BH RLC channels and BAP-layer route entries on the second path between dual-connecting IAB-node and second-path IAB-donor-DU. These configurations may be performed at an earlier stage, e.g. immediately after step 3. 11. The new TNL addresses allocated in step 5 (if any) are added to the dual-connecting IAB-DUβs F1-C association(s) with the IAB-donor-CU. The IAB-donor-CU may configure new UL BH information on the second path for F1AP messages. If new TNL addresses for F1-C traffic are configured, new SCTP association(s) between the dual-connecting IAB-node and the IAB-donor-CU may be established using the new TNL address information of the dual-connecting IAB-node. The dual-connecting IAB-node sends an F1AP gNB-DU CONFIGURATION UPDATE message to the IAB-donor-CU, which may include new (outer) IP addresses and corresponding new (inner) IP address for the F1-U traffic to be switched to the target path. 12. The IAB-donor-CU may migrate the F1-U tunnels it has with the dual-connecting IAB-DU from the first path to the second path via the UE CONTEXT MODIFICATION REQUEST message. 13. The dual-connectivity IAB-DU replies with a UE CONTEXT MODIFICATION RESPONSE message. Steps 12 and 13 can be performed for a subset of UE bearers, e.g., to balance the load between the first and the second path. In case the second path is used for the dual-connecting IAB-nodeβs descendant node(s), Steps 10 and 11 are also performed for the descendant node(s), as follows: When the second path uses a different IAB-donor-DU, the IAB-donor-CU shall configure the descendent IAB-DU(s) with one or more new TNL addresses, which are anchored on the IAB-donor-DU of the second path. If needed, the IAB-donor-CU configures BH RLC channels, BAP-layer route entries on the target path for the descendant nodes and the BH RLC channel mappings on the descendant nodes in the same manner as described for the dual-connecting IAB-node in step 10. The descendant nodesβ new TNL addresses (if any) are added to the descendant node IAB-DUβs F1-C association(s) with the IAB-donor-CU. The IAB-donor-CU may configure UL BH information for the second path to carry F1AP messages. The IAB-donor-CU may migrate the F1-U tunnels it has with the dual-connecting IAB-nodeβs descendant node(s) from the first path to the second path, as described for step 12. Based on implementation, these steps can be performed after or in parallel with the redundant path addition of the dual connecting IAB-node. The IAB-donor-CU may initiate the release of the redundant path by releasing the BAP routing entries and modifying/releasing the BH RLC channels on that path. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.4 |
3,009 | 12.3.4.2 Elements of APN overload control | For allowing the effective APN overload control, at least the following information (in addition to the other applicable information for overload control as defined in clause 12.3.5.1.2) are required to be advertised by the source node, as part of the APN level overload information: APN: The APN for which the source node wants to advertise the overload information; APN-Overload-Reduction-Metric: It indicates the requested overload reduction for the signalling traffic corresponding to a particular APN, as a percentage. Its computation is implementation dependent and it has the same characteristics as the "Overload-Reduction-Metric", described in clause12.3.5.1.2.1, when applied at APN level. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.3.4.2 |
3,010 | 7.7.1G Minimum requirements for V2X | The throughput shall be β₯ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.8.2 with parameters specified in Tables 7.7.1G-1. Table 7.7.1G-1: Spurious response parameters Table 7.7.1G-2: Spurious response When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA downlink reception for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 7.7.1G apply for the E-UTRA V2X sidelink reception and the requirements in subclause 7.7.1 apply for the E-UTRA downlink reception while all downlink carriers are active. For intra-band contiguous multi-carrier operation, the V2X UE throughput shall be β₯ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.8.2 with parameters specified in Table 7.7.1G-3 and Table 7.7.1G-4. Table 7.7.1G-3: Spurious response parameters for intra-band contiguous multi-carrier for V2X UE Tables 7.7.1G-4: Spurious response for intra-band contiguous multi-carrier for V2X UE | 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 | 7.7.1G |
3,011 | 16.12.6.3 Switching from indirect to indirect path | The gNB can select an L2 U2N Relay UE in any RRC state i.e., RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED, as a target L2 U2N Relay UE for indirect to indirect path switch. For service continuity of L2 U2N Remote UE, the following procedure is used, in case of the L2 U2N Remote UE switching from indirect path via L2 U2N Relay UE to indirect path via a target L2 U2N Relay UE in RRC_CONNECTED: Figure 16.12.6.3-1: Procedure for L2 U2N Remote UE intra-gNB switching from indirect to indirect path via a target L2 U2N Relay UE in RRC_CONNECTED 1. The L2 U2N Remote UE reports one or multiple candidate L2 U2N Relay UE(s) and the measurement result(s) between L2 U2N Remote UE and the candidate L2 U2N Relay UE(s). The detailed reporting components can be referred to the cases for switching from direct to indirect path (see clause 16.12.6.2). The L2 U2N Remote UE can provide information to the gNB according to the measurement configuration on which the gNB can decide indirect path switching. 2. The gNB decides to switch the L2 U2N Remote UE to a target L2 U2N Relay UE under the same gNB. 3. The gNB sends an RRCReconfiguration message to the target L2 U2N Relay UE, which includes at least the L2 U2N Remote UE's local ID and L2 ID, Uu and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration. 4. The gNB sends the RRCReconfiguration message to the L2 U2N Remote UE. The RRCReconfiguration message includes at least the target L2 U2N Relay UE ID, Remote UE's local ID, PC5 Relay RLC channel configuration for relay traffic, and the associated end-to-end radio bearer(s). The L2 U2N Remote UE stops UP and CP transmission over the indirect path via the Source L2 U2N Relay UE after the reception of the RRCReconfiguration message from the gNB. 5. The L2 U2N Remote UE establishes PC5-RRC connection with the target L2 U2N Relay UE. 6. The L2 U2N Remote UE completes the path switch procedure by sending the RRCReconfigurationComplete message to the gNB via the target L2 U2N Relay UE. 7. The gNB sends the RRCReconfiguration message to the Source L2 U2N Relay UE to reconfigure the connection between the Source L2 U2N Relay UE and the gNB. The RRCReconfiguration message to the Source L2 U2N Relay UE can be sent any time after step 4 based on gNB implementation (e.g., to release Uu and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration related to the L2 U2N Remote UE). 8. Either Source L2 U2N Relay UE's AS layer or L2 U2N Remote UE's AS layer indicates upper layers to release PC5 unicast link after receiving the RRCReconfiguration message from the gNB. The timing to execute link release is up to UE implementation after step 4 or step7. 9. The data path is switched from the source relay UE to the target relay UE between the L2 U2N Remote UE and the gNB. This step can be any time after step 6. In case that the selected L2 U2N Relay UE for indirect to indirect path switch is in RRC_IDLE or RRC_INACTIVE, the specific operation of the L2 U2N Remote UE and the selected L2 U2N Relay UE is the same as the case of direct to indirect path switch (see clause 16.12.6.2). For service continuity of L2 U2N Remote UE between inter-gNBs, the following procedure is used, in case of the L2 U2N Remote UE, which is connected to indirect path, switching to another indirect path via a target L2 U2N Relay UE in RRC_CONNECTED under another gNB: Figure 16.12.6.3-2: Procedure for L2 U2N Remote UE inter-gNB switching from indirect to indirect path via a target L2 U2N Relay UE in RRC_CONNECTED 1. The L2 U2N Remote UE reports one or multiple candidate L2 U2N Relay UE(s) and Uu measurements to the source gNB, after it measures/discovers the candidate L2 U2N Relay UE(s): - The L2 U2N Remote UE filters the appropriate L2 U2N Relay UE(s) according to relay selection criteria before reporting. The L2 U2N Remote UE shall report only the L2 U2N Relay UE candidate(s) that fulfil the higher layer criteria; - The reporting includes at least a L2 U2N Relay UE ID, a L2 U2N Relay UE's serving cell ID, and a sidelink measurement quantity information. SD-RSRP is used as sidelink measurement quantity. 2. The source gNB decides to trigger the L2 U2N Remote UE to switch to an indirect path of another gNB. 3. The source gNB sends a HANDOVER REQUEST message to the target gNB to prepare the path switch at the target side. The HANDOVER REQUEST message includes Remote UE L2 ID and a list of candidate target relay UE IDs belonging to one cell. NOTE: In order to support the DL lossless handover for the L2 U2N Remote UE, the source gNB may not discard the DL data even though the delivery of the data has been acknowledged by the source L2 U2N Relay UE based on the gNB implementation. Then, the source gNB forwards the buffered DL data to the target gNB during the data forwarding procedure. 4. Admission Control may be performed by the target gNB. 5. The target gNB selects one target Relay UE from the list of candidate Relay UEs provided by the source gNB, sends the RRCReconfiguration message to the L2 U2N Relay UE for relaying configuration, which includes at least the L2 U2N Remote UE's local ID and L2 ID, Uu Relay RLC channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration. 6. The target gNB sends the HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which contains new RRC configuration for L2 U2N Remote UE. 7. The source gNB sends the RRCReconfiguration message to the L2 U2N Remote UE, which includes at least the target L2 U2N Relay UE ID, Remote UE's local ID, PC5 Relay RLC channel configuration for relay traffic and the associated end-to-end Uu radio bearer(s). The L2 U2N Remote UE stops User Plane and Control plane transmission over the (source) indirect path after reception of the RRCReconfiguration message from the source gNB. 8. The source gNB sends the SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of the L2 U2N Remote UE's DRBs for which PDCP status preservation applies (i.e. for RLC AM). 9. The L2 U2N Remote UE establishes PC5 connection to the target L2 U2N Relay UE. 10. The L2 U2N Remote UE sends the RRCReconfigurationComplete message to the target gNB via the target L2 U2N Relay UE. 11. The data path is switched from indirect path to indirect path between the L2 U2N Remote UE and the target gNB via the target L2 U2N Relay UE. 12. The target gNB sends the UE CONTEXT RELEASE message to inform the source gNB about the success of the path switch. 13. The source gNB sends the RRCReconfiguration message to the source L2 U2N Relay UE to reconfigure the connection between the source L2 U2N Relay UE and the source gNB. The RRCReconfiguration message to the source L2 U2N Relay UE can be sent any time after step 7 based on source gNB implementation (e.g., to release Uu Relay RLC channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration related to the L2 U2N Remote UE). 14. Either L2 U2N Relay UE or L2 U2N Remote UE's AS layer indicates upper layer to release PC5 unicast link after receiving the RRCReconfiguration message from the source gNB. The timing to execute link release is up to UE implementation. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.6.3 |
3,012 | 6.2.9A TNGF | The functionality of TNGF in the case of trusted non-3GPP access includes the following: - Terminates the N2 and N3 interfaces. - Terminates the EAP-5G signalling and behaves as authenticator when the UE attempts to register to 5GC via the TNAN. - Implements the AMF selection procedure. - Transparently relays NAS messages between the UE and the AMF, via NWt. - Handles N2 signalling with SMF (relayed by AMF) for supporting PDU sessions and QoS. - Transparently relays PDU data units between the UE and UPF(s). - Implements a local mobility anchor within the TNAN. - Packet marking in the downlink, and the uplink on N2 and N3, as for the N3IWF (clause 6.2.9). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.9A |
3,013 | K.2.4 IOPS network establishment/termination | The decision by an IOPS-capable eNodeB to enter IOPS mode of operation is made in accordance with the local policies of the RAN operator. Such policies can be affected by any RAN sharing agreements that are in place. In situations when the backhaul to the Macro EPC is lost and an eNodeB can start IOPS mode of operation based on local policies, or an eNodeB is deployed as part of a Nomadic EPS, the following eNodeB behaviour is expected: - If the eNodeB can reach a Local EPC for IOPS mode of operation, the eNodeB uses the Local EPC. - If the eNodeB cannot reach a Local EPC, then the eNodeB enters a state where UEs do not attempt to select the cells under its control. In this release of the specification IOPS networks will be established by the independent actions of each eNodeB entering IOPS mode of operation. An IOPS network comprising two or more eNodeBs will be established as a result of multiple eNodeBs entering IOPS mode of operation and establishing S1-MME paths to the local MME of the same Local EPC instance. An eNodeB in IOPS mode of operation, indicates/broadcasts the IOPS PLMN cell(s) as "Not Barred" & "Reserved for Operator Use", for the IOPS PLMN identity, as defined in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34]. This "Cell Reserved for Operator Use" feature will allow the IOPS-enabled UEs to get access to the IOPS network while barring other non-IOPS-enabled UEs in the same area. The dedicated IOPS USIM application configuration (clause K.2.2) is restricted to use only by users authorised to access a network in IOPS mode of operation. When a backhaul to the Macro EPC is re-established, the S1 connections to the Local EPC are released according to the local IOPS network policies, to move the UEs to Idle mode, and IOPS mode of operation ceases. The PLMN identity of the Macro EPC is announced by the eNodeB so that UEs reselect the normal PLMN and attach afresh to the Macro EPC. Figure K.2.4-1 provides an example of the basic steps involved in IOPS network establishment, access and termination. Figure K.2.4-1: Example of Local EPC based IOPS operation 1) The UE is attached to the Macro EPC accessing normal application (e.g. MCPTT) services. 2) The eNodeB detects loss of the backhaul to the Macro EPC and in accordance with local operator policies decides to activate IOPS mode of operation. The eNodeB prevents any UEs from selecting the cell, using a suitable mechanism such as cell barring, until step 3 and step 4 are completed. 3) Local EPC is activated. NOTE 1: Steps 1, 2 and 3 are not applicable for the Nomadic EPS case. 4) The eNodeB establishes an S1 link to the Local EPC. 5) The eNodeB broadcasts the PLMN identity for IOPS operation with the Local EPC and indicates the IOPS PLMN cell(s) as "Not Barred" & "reserved" for operator use. 6) The UE detects the IOPS PLMN-Id and a decision is made to switch USIM application and the UE activates the IOPS USIM application. NOTE 2: It is out of scope of this specification how the decision is made to switch USIM application. 7) The UE selects the IOPS PLMN-Id. 8) The UE attaches to the Local EPC and, for an IP PDN type, obtains a local IP address, if authorised. 9) Public safety services supported by the IOPS network can be accessed at this time. 10) At some point in time the eNodeB detects that the backhaul to the Macro EPC has been restored. 11) S1 connections to the Local EPC are released according to the IOPS network policies to move the UEs to idle mode. 12) The eNodeB stops its IOPS mode of operation and the Local EPC is de-activated. 13) The eNodeB establishes an S1 link to the Macro EPC. 14) The PLMN-Id of the Macro EPC is announced and the normal TAIs of the Macro EPC are advertised by the eNodeB so that UEs reselect the normal PLMN. 15) The UE detects the PLMN-Id of the Macro EPC and a decision is made to switch USIM application and the UE activates the normal USIM application. NOTE 3: It is out of scope of this specification how the decision is made to switch USIM application. 16) The UE selects the normal PLMN-Id. 17) The UE attaches as normal to the Macro EPC, if authorised. | 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 |
3,014 | 8.11.1.2.2 Closed-loop spatial multiplexing performance (User-Specific Reference Symbols) | 8.11.1.2.2.1 Single-layer Spatial Multiplexing For single-layer transmission on antenna ports 7 or 8 upon detection of a PDCCH with DCI format 6-1A, the requirements are specified in Table 8.11.1.2.2.1-2 with the addition of the parameters in Table 8.11.1.2.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify rank-1 performance on one of the antenna ports 7 or 8. Table 8.11.1.2.2.1-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) Table 8.11.1.2.2.1-2: Minimum performance for CDM-multiplexed DM RS without simultaneous transmission (FRC) with multiple CSI-RS configurations | 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.11.1.2.2 |
3,015 | 6.3.8 UDM discovery and selection | The NF consumer or the SCP performs UDM discovery to discover a UDM instance that manages the user subscriptions. If the NF consumer performs discovery and selection, the NF consumers shall utilize the NRF to discover the UDM instance(s) unless UDM information is available by other means, e.g. locally configured on NF consumers. The UDM selection function in NF consumers selects a UDM instance based on the available UDM instances (obtained from the NRF or locally configured). The UDM selection functionality is applicable to both 3GPP access and non-3GPP access. The UDM selection functionality in NF consumer or in SCP should consider one of the following factors: 1. Home Network Identifier (e.g. MNC and MCC, realm) of SUCI/SUPI, along with the selected NID (provided by the NG-RAN) in the case of SNPN, UE's Routing Indicator and optionally Home Network Public Key identifier (e.g. in the case that Routing Indicator is not enough to provide SUPI range granularity). NOTE 1: The UE provides the SUCI to the AMF, which contains the Routing Indicator and Home Network Public Key identifier as defined in TS 23.003[ Numbering, addressing and identification ] [19] during initial registration. The AMF provides the UE's Routing Indicator and optionally Home Network Public Key identifier to other NF consumers (of UDM) as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 2: The usage of Home Network Public Key identifier for UDM discovery is limited to the scenario where the NF consumers belong to the same PLMN as AUSF. NOTE 3: In the case of SNPN and the UE provides an IMSI type SUCI to the AMF and the SUCI provided by UE or the SUPI derived from the SUCI is for an SNPN served by the AMF, the AMF uses the selected NID provided by the NG-RAN together with the selected PLMN ID (from IMSI) or the Routing Indicator provided by the UE within the SUCI for UDM selection. In the case of SNPN and the UE provides an NSI type SUCI to the AMF, the AMF uses the Home Network Identifier and Routing Indicator of SUCI/SUPI for selection of UDM. When the UE's Routing Indicator is set to its default value as defined in TS 23.003[ Numbering, addressing and identification ] [19], the UDM NF consumer can select any UDM instance within the home network of the SUCI/SUPI. 2. UDM Group ID of the UE's SUPI. NOTE 4: The AMF can infer the UDM Group ID the UE's SUPI belongs to, based on the results of UDM discovery procedures with NRF. The AMF provides the UDM Group ID the SUPI belongs to other UDM NF consumers as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. 3. SUPI or Internal Group ID; the UDM NF consumer selects a UDM instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI or Internal Group ID as input for UDM discovery. 4. GPSI or External Group ID; UDM NF consumers which manage network signalling not based on SUPI/SUCI (e.g. the NEF) select a UDM instance based on the GPSI or External Group ID range the UE's GPSI or External Group ID belongs to or based on the results of a discovery procedure with NRF using the UE's GPSI or External Group ID as input for UDM discovery. In the case of delegated discovery and selection in SCP, NF consumer shall include one of these factors in the request towards SCP. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.8 |
3,016 | 5.2.6.23.2 Nnef_AMInfluence_Create operation | Service operation name: Nnef_AMInfluence_Create Description: Authorize the request and store the AM influence data in the UDR, potentially translating GSPI to SUPI and External Group Identifier to Internal Group Identifier. Inputs, Required: AF Transaction Id. The AF Transaction Id refers to the request. Inputs, Optional: List of (DNN, S-NSSAI)(s), Target (GPSI, or External Group Identifier(s), or any UE, or any inbound roaming UEs identified by their PLMN ID(s)), throughput requirements, service coverage requirements, policy duration, List of External Application Identifiers, subscribed event(s). The subscribed event(s) includes Event ID(s) as specified in Nnef_AMInfluence_Notify service operation, Event Reporting Information defined in Table 4.15.1-1 (only the Event Reporting mode and the immediate reporting flag when applicable), Notification Target Address. When a list of External Application Identifiers is provided, the throughput requirement, service coverage requirements, policy duration and subscribed event(s) are assigned the same value for all External Application Identifiers. Outputs, Required: Operation execution result indication. Outputs, Optional: None. NOTE: "any UE" refers to the UEs within the PLMN of the NEF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.23.2 |
3,017 | 8.4.1.2.7 Enhanced Downlink Control Channel Performance Requirement Type B - 2 Tx Antenna Port with Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type B for PDCCH/PCFICH with 2 transmit antennas for the case of dominant interferer with the colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.1-1 and Table 8.4.1.2.7-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.1.2.7-2. In Table 8.4.1.2.7-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the agressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.4.1.2.7-1: Test Parameters for PDCCH/PCFICH Table 8.4.1.2.7-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type B | 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.4.1.2.7 |
3,018 | 4.17.1 NF service Registration | NOTE 1: The term "NF service consumer" in this clause refers to the consumer of the NRF services and should not be confused with the role of the NF (consumer or producer). Figure 4.17.1-1: NF Service Registration procedure 1. NF service consumer, i. e. an NF instance sends Nnrf_NFManagement_NFRegister Request message to NRF to inform the NRF of its NF profile when the NF service consumer becomes operative for the first time. See clause 5.2.7.2.2 for relevant NF profile parameters NOTE 2: NF service consumer's NF profile is configured by OAM system. 2. The NRF stores the NF profile of NF service consumer and marks the NF service consumer available. NOTE 3: Whether the NF profile sent by NF service consumer to NRF needs to be integrity protected by the NF service consumer and verified by the NRF is to be decided by SA3. 3. The NRF acknowledge NF Registration is accepted via Nnrf_NFManagement_NFRegister response. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.1 |
3,019 | 5.6.1.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 a SERVICE REJECT message has been sent to the UE or the service request procedure has been completed by the AMF, the AMF enters/stays in 5GMM-IDLE. b) Protocol error. If the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message is received with a protocol error, the AMF shall return a SERVICE 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. The AMF stays in the current 5GMM mode. c) More than one SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message received before the procedure has been completed (i.e., before SERVICE REJECT message has been sent or service request procedure has been completed). - If one or more of the information elements in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message differs from the ones received within the previous SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message, the previously initiated service request procedure shall be aborted, and the new service request procedure shall be progressed; - If the information elements do not differ, then the AMF shall continue with the previous service request procedure and shall not treat any further this SERVICE REQUEST message or this CONTROL PLANE SERVICE REQUEST message. d) REGISTRATION REQUEST message received with "initial registration" or "emergency registration" in the 5GS registration type IE before a SERVICE REJECT message has been sent or the service request procedure has been completed. If a REGISTRATION REQUEST message with "initial registration" or "emergency registration" in the 5GS registration type IE is received and the service request procedure has not been completed or a SERVICE REJECT message has not been sent, the AMF may initiate the 5GMM common procedures, e.g. the primary authentication and key agreement procedure. The AMF may e.g. after a successful primary authentication and key agreement procedure execution, abort the service request procedure, delete the 5GMM context, indicate towards the SMF that the 5GMM context has been deleted and progress the new REGISTRATION REQUEST message. e) REGISTRATION REQUEST message received with "mobility registration updating" or "periodic registration updating" in the 5GS registration type IE received before the service request procedure has been completed or a SERVICE REJECT message has been sent. If a REGISTRATION REQUEST message with "mobility registration updating" or "periodic registration updating" in the 5GS registration type IE is received and the service request procedure has not been completed or a SERVICE REJECT message has not been sent, the AMF may initiate the 5GMM common procedures, e.g. the primary authentication and key agreement procedure. The AMF may e.g. after a successful primary authentication and key agreement procedure execution, abort the service request procedure and progress the new REGISTRATION REQUEST message. f) If a CONTROL PLANE SERVICE REQUEST message with Control plane service type indicating "mobile originating request" is received after the AMF initiated a paging procedure, the AMF shall treat this CONTROL PLANE SERVICE REQUEST as a paging response and handle the message according to subclauses 5.6.1.4 and 5.6.1.5. g) CONTROL PLANE SERVICE REQUEST message received with the Data type field indicates "control plane user data" in the CIoT small data container IE or received with Payload container type IE set to "CIoT user data container" and: 1) the AMF does not have a PDU session routing context for the PDU session ID and the UE; or 2) the AMF unsuccessfully attempted to forward the user data container and the PDU session ID, then the AMF may send back to the UE the CIoT user data container or control plane user data which was not forwarded as specified in subclause 5.4.5.3.1 case l1) or case l2). h) Based on operator policy, if the service request from a UE not supporting CAG is rejected due to CAG restrictions, the network shall reject the service request with a 5GMM cause value other than the 5GMM cause #76 (Not authorized for this CAG or authorized for CAG cells only). NOTE: 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. i) CIoT user data received for a PDU session ID which is inactive in the network. If a CONTROL PLANE SERVICE REQUEST message is received with CIoT user data for a PDU session that is inactive in the network, the AMF shall discard the CIoT user data. The AMF shall send the SERVICE ACCEPT message and indicate that this PDU session ID is inactive using the PDU session status 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 | 5.6.1.8 |
3,020 | 5.17.8 URSP Provisioning in EPS | When the UE registers in 5GS, the UE includes the Indication of URSP Provisioning Support in EPS in the UE Policy Container carried in Registration Request. On receiving this indication in the UE Policy Container, the PCF will provision the URSP to UE in EPS. The UE may include the indication of URSP Provisioning Support in EPS in PCO or ePCO to the SMF+PGW-C during: - Initial Attach with default PDN connection establishment (according to clause 5.3.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]). - Any UE requested PDN connectivity request to an additional PDN (according to clause 5.10.2 of 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 supports URSP provisioning in EPS, it provides the Indication of URSP Provisioning Support in EPS in ePCO in the Create Session Response message. The UE ensures that there is only one PDN connection used for URSP rule delivery in EPS. When the UE receives an indication of URSP provisioning support in EPS in the PDN Connectivity Accept message and this PDN connection is not released, then for any subsequent PDN connectivity requests the UE does not include an indication of URSP Provisioning Support in EPS. When the UE receives the Indication of URSP Provisioning Support in EPS included in ePCO in the PDN Connectivity Accept message, then the UE initiates the UE requested bearer resource modification without QoS update procedure and includes the UE Policy Container ePCO in the Request Bearer Resource Modification message, the UE Policy Container in ePCO will be further forwarded by MME to SMF+PGW-C. When the UE Policy Container ePCO is received by SMF+PGW-C, it forwards transparently the UE Policy Container to PCF for the PDU Session, then the PCF for the PDU Session establishes the UE Policy Association with PCF for the UE. The PCF for the UE generates the corresponding URSP rules in a similar way as it is done in 5GS and sends the URSP rules to UE in the UE Policy Container as described in clause 4.11.0a.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 1: The UE includes the Indication of URSP Provisioning Support in EPS in PCO or ePCO in the PDN connectivity request according to clause 6.6.1.1 of TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [13]. NOTE 2: The MME and Serving-GW can be configured to prioritize the selection of a SMF+PGW-C that support URSP Rule provisioning in EPS. If the UE does not receive the Indication of URSP Provisioning Support in EPS in ePCO in the PDN Connectivity Accept message, then the UE does not initiate the UE requested bearer resource modification procedure to send the UE Policy Container. The PDN Connection used by UE and SMF+PGW-C to convey UE Policy Container PCO shall be kept when the UE is in the CONNECTED mode. When the UE is attached to EPS, the PCF for the PDU Session retrieves the PCRTs for UE Policy from PCF for the UE and subscribes to the applicable PCRTs to SMF+PGW-C. The PCF for the PDU Session sends the UE Policy Container in the same PDN connection/PDU session in which the UE Policy Container was received. During EPS to 5GS mobility with N26, the UE Policy Association is terminated by PCF for PDU Session when it receives the indication of RAT type change from the SMF+PGW-C. During 5GS to EPS mobility with N26, the PCF for the PDU Session determines whether the UE supports URSP delivery in EPS by checking UE context policy control subscription information in UDR. The PCF for the PDU Session discovers the address of PCF for the UE serving the UE by querying BSF. The PCF for the UE recovers the information about the PSI list in the UE and the subscribed PCRTs in 5GS from former UE Policy Association for the UE after receiving the UE Policy Association Establishment request including a UE Policy Container only including an indication about the trigger for the UE Policy Association Establishment ("5GS to EPS mobility"). After the 5GS to EPS mobility, if PCF for the UE needs to provision the URSP to UE, the PCF for the UE sends the UE Policy Container in Npcf_UEPolicyControl_UpdateNotify Request to the PCF for the PDU Session as described in clause 4.11.0a.2a.10 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In case there are more than one PDN connections for the UE, then the PCF for the PDU Session selects any of the ongoing PDN Connections via a SMF+PGW-C supporting URSP delivery in EPS for the UE. Then via the selected PDN Connection, the SMF+PGW-C sends the UE Policy Container via ePCO to UE by initiating the PDN GW initiated bearer modification without QoS update procedure as defined in clause 5.4.3 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. NOTE 3: At 5GS to EPS mobility with N26, the guard timer in the AMF (as specified in clauses 4.11.1.2.1 and 4.11.1.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) ensures that the UE Policy Association remains until the PCF for the UE detects that a UE Policy Association establishment is received from a PCF for the PDU Session indicating 5GS to EPS mobility. NOTE 4: In the case that the UE is still registered and reachable over non-3GPP access, the PCF for UE can have two UE policy associations for one UE, and based on local configuration the PCF can decide to use one of the UE policy associations to update URSP rule to the UE. The UE can receive URSP Rules over any of these two accesses. When the PCF for the UE decides to update the URSPs in the UE via EPS, the PCF for the UE sends the updated URSP rules in UE Policy Container to the PCF for the PDU Session, then the PCF for the PDU Session forwards it to the SMF+PGW-C. The SMF+PGW-C transfers the received UE Policy Container via ePCO to the UE by triggering PDN-GW initiated Bearer without QoS Modification procedure as described in clause 5.4.3 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. After update the UE policy provided by the PCF, the UE response about the delivery result via ePCO to the network. The SMF+PGW-C transparently forwards the UE response to the PCF for the PDU Session via Update Bearer Response message, and then the PCF for the PDU Session forwards it to the PCF for the UE via Npcf_UEPolicyControl_Update Request. If the SMF+PGW-C receives a rejection for Update Bearer Request message (e.g. due to paging failure), the delivery failure result is sent to PCF for the PDU Session and the PCF for the UE. To request to forward the result of delivery of UE policies, "Result of UE Policy Container delivery via EPS" PCRT is applied to the PCF for the PDU Session and the SMF+PGW-C as described in clause 4.11.0a.2a.10 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.8 |
3,021 | 5.3.4 Registration areas | Within the 5GS, the registration area is managed independently per access type, i.e., 3GPP access or non-3GPP access. The AMF assigns a registration area to the UE during the registration procedure. A registration area is defined as a set of tracking areas and each of these tracking areas consists of one or more cells that cover a geographical area. Within the 5GS, the concept of "registration to multiple tracking areas" applies: a) A tracking area is identified by a TAI which is broadcast in the cells of the tracking area. The TAI is constructed from a TAC and a PLMN identity. In case of a shared network: 1) one or more TACs; and 2) any of the following: i) multiple PLMN identities; ii) multiple SNPN identities; or iii) one or more PLMN identities and one or more SNPN identities; are broadcast. b) In order to reduce the tracking area update signalling within the 5GS, the AMF can assign several tracking areas to the UE. These tracking areas construct a list of tracking areas which is identified by a TAI list. When generating the TAI list, the AMF shall include only TAIs that are applicable on the access where the TAI list is sent. The AMF shall be able to allocate a TAI list over different NG-RAN access technologies. The AMF shall not allocate a TAI list containing both tracking areas in NB-N1 mode and tracking areas not in NB-N1 mode. c) The UE considers itself registered to a list of tracking areas and does not need to trigger the registration procedure for mobility and periodic registration update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message) as long as the UE stays in one of the tracking areas of the list of tracking areas received from the AMF. d) The UE will consider the TAI list stored in the UE as valid, until it receives a new TAI list in the next registration procedure for mobility and periodic registration update or generic UE configuration update procedure, or the UE is commanded by the network to delete the TAI list by a reject message or it is deregistered from the 5GS. If the registration request is accepted or the TAI list is reallocated by the AMF, the AMF shall provide at least one entry in the TAI list. If the new and the old TAI list are identical, the AMF does not need to provide the new TAI list to the UE during mobility registration update or periodic registration update. e) The TAI list can be reallocated by the AMF. f)- When the UE is deregistered from the 5GS, the UE shall delete the TAI list stored in the UE. g) The UE includes the last visited registered TAI, if available, to the AMF. The last visited registered TAI is stored in a non-volatile memory in the USIM if the corresponding file is present in the USIM, else in the non-volatile memory in the ME, as described in annex C. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.4 |
3,022 | .1 PDN GW initiated bearer modification with bearer QoS update | The PDN GW initiated bearer modification procedure (including EPS Bearer QoS update) for a GTP based S5/S8 is depicted in figure 5.4.2.1-1. This procedure is used in cases when one or several of the EPS Bearer QoS parameters QCI, GBR, MBR or ARP are modified (including the QCI or the ARP of the default EPS bearer e.g. due to the HSS Initiated Subscribed QoS Modification procedure, as described in clause 5.4.2.2) or to modify the APN-AMBR. Modification from a QCI of resource type non-GBR to a QCI of resource type GBR and vice versa is not supported by this procedure. NOTE 1: The QCI of an existing dedicated bearer should only be modified if no additional bearer can be established with the desired QCI. Figure 5.4.2.1-1: Bearer Modification Procedure with Bearer QoS Update NOTE 2: Steps 3-10 are common for architecture variants with GTP based S5/S8 and PMIP-based S5/S8. For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 1, 2, 11 and 12 concern GTP based S5/S8. 1. If dynamic PCC is deployed, the PCRF sends a PCC decision provision (QoS policy) message to the PDN GW. This corresponds to the initial steps of the PCRF-Initiated IP-CAN Session Modification procedure or to the PCRF response in the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6], up to the point that the PDN GW requests IP-CAN Bearer Signalling. The PCC decision provision message may indicate that User Location Information and/or UE Time Zone Information is to be provided to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. If dynamic PCC is not deployed, the PDN GW may apply local QoS policy. 2. The PDN GW uses this QoS policy to determine that the authorized QoS of a service data flow has changed or that a service data flow shall be aggregated to or removed from an active bearer. The PDN GW generates the TFT and updates the EPS Bearer QoS to match the traffic flow aggregate. The PDN GW then sends the Update Bearer Request (PTI, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, TFT, Maximum Packet Loss Rate (UL, DL)) message to the Serving GW. The Procedure Transaction Id (PTI) parameter is used when the procedure was initiated by a UE Requested Bearer Resource Modification Procedure - see clause 5.4.5. For APN-AMBR, the EPS bearer identity must refer to a non-GBR bearer. For a QCI=1 bearer, the Maximum Packet Loss Rate (UL, DL) may be provided by the PDN GW as described in TS 23.203[ Policy and charging control architecture ] [6]. 3. The Serving GW sends the Update Bearer Request (PTI, EPS Bearer Identity, EPS Bearer QoS, TFT, APN-AMBR, Maximum Packet Loss Rate (UL, DL)) message to the MME. If the UE is in ECM-IDLE state the MME will trigger the Network Triggered Service Request from step 3 (which is specified in clause 5.3.4.3). In that case the following steps 4-7 may be combined into Network Triggered Service Request procedure or be performed stand-alone. If only the QoS parameter ARP is modified and if the UE is in ECM IDLE state the MME shall skip the Network Triggered Service Request. In that case the following steps 4-9 are also skipped and the MME sends an Update Bearer Response to the Serving GW. If extended idle mode DRX is enabled for the UE, the MME will trigger Network Triggered Service Request from step 3 (which is specified in clause 5.3.4.3), and start a timer which is configured to a value smaller than the GTP re-transmission timer. If the MME receives no response from the UE before the timer expires, the MME sends an Update Bearer Response with a rejection cause indicating that the UE is temporarily not reachable due to power saving and, if a Delay Tolerant Connection indication was set for the PDN connection, the MME sets the internal flag Pending Network Initiated PDN Connection Signalling. The rejection is forwarded by the Serving GW to the PDN GW. In this case, the steps 4-11 are skipped. NOTE 3: If ISR is activated and the Serving GW does not have a downlink S1-U and the SGSN has notified the Serving GW that the UE has moved to PMM-IDLE or STANDBY state, the Serving GW sends Downlink Data Notification to trigger MME and SGSN to page the UE (as specified in clause 5.3.4.3) before sending the Update Bearer Request message. 4. The MME builds a Session Management Request including the PTI, EPS Bearer QoS parameters (excluding ARP), TFT, APN-AMBR, EPS Bearer Identity and a WLAN offloadability indication. If the UE has UTRAN or GERAN capabilities and the network supports mobility to UTRAN or GERAN, the MME uses the EPS Bearer QoS parameters to derive the corresponding PDP context parameters QoS Negotiated (R99 QoS profile), Radio Priority and Packet Flow Id and includes them in the Session Management Request. If the UE indicated in the UE Network Capability it does not support BSS packet flow procedures, then the MME shall not include the Packet Flow Id. If the APN-AMBR has changed the MME may update the UE-AMBR if appropriate. The MME then sends the Bearer Modify Request (EPS Bearer Identity, EPS Bearer QoS, Session Management Request, UE-AMBR, Maximum Packet Loss Rate (UL, DL)) message to the eNodeB. The MME may include an indication whether the traffic of this PDN Connection is allowed to be offloaded to WLAN as described in clause 4.3.23. 5. The eNodeB maps the modified EPS Bearer QoS to the Radio Bearer QoS. It then signals a RRC Connection Reconfiguration (Radio Bearer QoS, Session Management Request, EPS RB Identity) message to the UE. The UE shall store the QoS Negotiated, Radio Priority, Packet Flow Id, which it received in the Session Management Request, for use when accessing via GERAN or UTRAN. If the APN-AMBR has changed, the UE stores the modified APN-AMBR value and sets the MBR parameter of the corresponding non-GBR PDP contexts (of this PDN connection) to the new value. The UE uses the uplink packet filter (UL TFT) to determine the mapping of traffic flows to the radio bearer. The UE may provide EPS Bearer QoS parameters to the application handling the traffic flow(s). The application usage of the EPS Bearer QoS is implementation dependent. The UE shall not reject the Radio Bearer Modify Request on the basis of the EPS Bearer QoS parameters contained in the Session Management Request. The UE shall set its TIN to "GUTI" if the modified EPS bearer was established before ISR activation. NOTE 4: The details of the Radio Bearer QoS are specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. 6. The UE acknowledges the radio bearer modification to the eNodeB with a RRC Connection Reconfiguration Complete message. 7. The eNodeB acknowledges the bearer modification to the MME with a Bearer Modify Response (EPS Bearer Identity, PSCell ID) message. With this message, the eNodeB indicates whether the requested EPS Bearer QoS could be allocated or not. The MME shall be prepared to receive this message either before or after the Session Management Response message (sent in step 9). The PSCell ID is included if Dual Connectivity is active for the UE in the RAN. 8. The UE NAS layer builds a Session Management Response including EPS Bearer Identity. The UE then sends a Direct Transfer (Session Management Response) message to the eNodeB. 9. The eNodeB sends an Uplink NAS Transport (Session Management Response) message to the MME. 10. Upon reception of the Bearer Modify Response message in step 7 and the Session Management Response message in step 9, the MME acknowledges the bearer modification to the Serving GW by sending an Update Bearer Response (EPS Bearer Identity, User Location Information (ECGI), PSCell ID) message. 11. The Serving GW acknowledges the bearer modification to the PDN GW by sending an Update Bearer Response (EPS Bearer Identity, User Location Information (ECGI)) message. 12. If the Bearer modification procedure was triggered by a PCC Decision Provision message from the PCRF, the PDN GW indicates to the PCRF whether the requested PCC decision (QoS policy) could be enforced or not by sending a Provision Ack message allowing the completion of the PCRF-Initiated IP-CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6], after the completion of IP-CAN bearer signalling. If requested by the PCRF the PDN GW indicates User Location Information and/or UE Time Zone Information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. If the Bearer modification is rejected with a cause indicating that the UE is temporarily not reachable due to power saving, then the PDN GW re-attempts the same procedure after it receives the indication that the is UE available for end to end signalling in the subsequent Modify Bearer Request message. NOTE 5: The exact signalling of step 1 and 12 (e.g. for local break-out) is outside the scope of this specification. This signalling and its interaction with the bearer activation procedure are to be specified in TS 23.203[ Policy and charging control architecture ] [6]. Steps 1 and 12 are included here only for completeness. | 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") | .1 |
3,023 | 13.4.4 QoE Measurement Continuity for Mobility | For ongoing sessions, QoE measurement continuity is ensured during mobility in NR-DC, e.g., during inter-MN handover (with/without SN change) and SN change scenarios. To ensure QoE measurement continuity during SN change, the SN-initiated SN modification procedure and/or the MN-initiated SN modification procedure can be used to provide the information about the SN-associated QMC configurations to the MN. The MN can then transfer this information to the new SN during the SN Addition procedure. To ensure QoE measurement continuity during inter-MN handover with SN change, the source SN should provide the information about the SN-associated QMC configurations to the source MN. During the handover procedure, the target MN is provided with all the information that the source MN has about the SN-associated QMC configuration. If the MN configured the UE with QoE measurements, every subsequent MN serving the UE can configure and release the RAN visible QoE measurements. | 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 | 13.4.4 |
3,024 | 4.2.2.3 Deregistration procedures 4.2.2.3.1 General | The Deregistration procedure allows: - the UE to inform the network that it does not want to access the 5GS any longer; and - the network to inform the UE that it does not have access to the 5GS any longer; or - the network to inform the UE that the UE's Registered PLMN is not allowed to operate at the UE location. The Deregistration request by the UE and Deregistration request by the network include whether the Deregistration applies to the 3GPP access, to the non-3GPP access, or to both. When the UE is registered to both accesses in the same PLMN, the Deregistration message can be sent over any access regardless of the access the Deregistration is applied to. Network-initiated Deregistration may be initiated if the UE's registered PLMN is not allowed to operate in the present UE location. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.2.3 |
3,025 | 5.8.16.3 Neighbor UE(s) in proximity conditions | A UE capable of NR sidelink U2U Relay UE operation and is performing U2U Relay Discovery with Model A as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65] shall: 1> for each of potential neighbor UE(s): 2> if the SL-RSRP of the UE is available and is above sl-RSRP-Thresh-DiscConfig if configured; or 2> if the SD-RSRP of the UE is available and is above sd-RSRP-Thresh-DiscConfig if configured: 3> consider the UE as neighbor UE in discovery message to be transmitted as defined in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65]. NOTE: The interaction with upper layers is left to UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.16.3 |
3,026 | 5.2.2.3.1 Response to SETUP | Having entered the "call present state" the call control entity of the mobile station shall - with the exception of the cases described below - acknowledge the SETUP message by a CALL CONFIRMED message, and enter the "mobile terminating call confirmed" state. If the mobile station supports multicall, it shall include the Stream Identifier (SI) information element in the CALL CONFIRMED message. If the mobile station is located in the network supporting multicall, it shall never include the SI that is in use and shall include with either of the following two values: - SI="no bearer"; - SI=new value (not used by any of the existing bearers). If the mobile station supporting multicall is located in the network not supporting multicall, it shall include the SI with value 1. The call control entity of the mobile station may include in the CALL CONFIRMED message to the network one or two bearer capability information elements to the network, either preselected in the mobile station or corresponding to a service dependent directory number (see 3GPP TS 29.007[ General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) ] [38]). The mobile station may also use the backup bearer capability IE, if provided by the network, to deduce the requested service (see 3GPP TS 27.001[ General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) ] [36], subclause 8.3.3.1). The mobile station may also include one or two bearer capabilities in the CALL CONFIRMED message to define the radio channel requirements. In any case the rules specified in subclause 9.3.2.2 shall be followed. NOTE: The possibility of alternative responses (e.g., in connection with supplementary services) is for further study. For speech calls the mobile station shall indicate all codecs that it supports for UTRAN in the Supported Codec List information element. Codecs for GERAN shall be indicated in the Bearer Capability information element, if this information element is included. Additionally, if the mobile station supports codecs for GERAN and UTRAN, it shall indicate the codecs for GERAN also in the Supported Codec List information element. If the MS supports the enhanced network-initiated in-call modification procedure as specified in subclause 5.3.4.3, the MS shall indicate this in the Call Control Capabilities IE in the CALL CONFIRMED message. A busy MS which satisfies the compatibility requirements indicated in the SETUP message shall respond either with a CALL CONFIRMED message if the call setup is allowed to continue or a RELEASE COMPLETE message if the call setup is not allowed to continue, both with cause #17 "user busy". If the mobile user wishes to refuse the call, a RELEASE COMPLETE message shall be sent with the cause #21 "call rejected". In the cases where the mobile station responds to a SETUP message with RELEASE COMPLETE message the mobile station shall release the MM connection and enter the "null" state after sending the RELEASE COMPLETE message. The network shall process the RELEASE COMPLETE message in accordance with subclause 5.4. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.2.3.1 |
3,027 | 10.5.3.6 Reject cause | The purpose of the Reject Cause information element is to indicate the reason why a request from the mobile station is rejected by the network. The Reject Cause information element is coded as shown in figure 10.5.81/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.95/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Reject Cause is a type 3 information element with 2 octets length. Figure 10.5.81/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Reject Cause information element Table 10.5.95/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Reject Cause 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.3.6 |
3,028 | β MAC-CellGroupConfig | The IE MAC-CellGroupConfig is used to configure MAC parameters for a cell group, including DRX. MAC-CellGroupConfig information element -- ASN1START -- TAG-MAC-CELLGROUPCONFIG-START MAC-CellGroupConfig ::= SEQUENCE { drx-Config SetupRelease { DRX-Config } OPTIONAL, -- Need M schedulingRequestConfig SchedulingRequestConfig OPTIONAL, -- Need M bsr-Config BSR-Config OPTIONAL, -- Need M tag-Config TAG-Config OPTIONAL, -- Need M phr-Config SetupRelease { PHR-Config } OPTIONAL, -- Need M skipUplinkTxDynamic BOOLEAN, ..., [[ csi-Mask BOOLEAN OPTIONAL, -- Need M dataInactivityTimer SetupRelease { DataInactivityTimer } OPTIONAL -- Cond MCG-Only ]], [[ usePreBSR-r16 ENUMERATED {true} OPTIONAL, -- Need R schedulingRequestID-LBT-SCell-r16 SchedulingRequestId OPTIONAL, -- Need R lch-BasedPrioritization-r16 ENUMERATED {enabled} OPTIONAL, -- Need R schedulingRequestID-BFR-SCell-r16 SchedulingRequestId OPTIONAL, -- Need R drx-ConfigSecondaryGroup-r16 SetupRelease { DRX-ConfigSecondaryGroup-r16 } OPTIONAL -- Need M ]], [[ enhancedSkipUplinkTxDynamic-r16 ENUMERATED {true} OPTIONAL, -- Need R enhancedSkipUplinkTxConfigured-r16 ENUMERATED {true} OPTIONAL -- Need R ]], [[ intraCG-Prioritization-r17 ENUMERATED {enabled} OPTIONAL, -- Cond LCH-PrioWithReTxTimer drx-ConfigSL-r17 SetupRelease { DRX-ConfigSL-r17 } OPTIONAL, -- Need M drx-ConfigExt-v1700 SetupRelease { DRX-ConfigExt-v1700 } OPTIONAL, -- Need M schedulingRequestID-BFR-r17 SchedulingRequestId OPTIONAL, -- Need R schedulingRequestID-BFR2-r17 SchedulingRequestId OPTIONAL, -- Need R schedulingRequestConfig-v1700 SchedulingRequestConfig-v1700 OPTIONAL, -- Need M tar-Config-r17 SetupRelease { TAR-Config-r17 } OPTIONAL, -- Need M g-RNTI-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxG-RNTI-r17)) OF MBS-RNTI-SpecificConfig-r17 OPTIONAL, -- Need N g-RNTI-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxG-RNTI-r17)) OF MBS-RNTI-SpecificConfigId-r17 OPTIONAL, -- Need N g-CS-RNTI-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxG-CS-RNTI-r17)) OF MBS-RNTI-SpecificConfig-r17 OPTIONAL, -- Need N g-CS-RNTI-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxG-CS-RNTI-r17)) OF MBS-RNTI-SpecificConfigId-r17 OPTIONAL, -- Need N allowCSI-SRS-Tx-MulticastDRX-Active-r17 BOOLEAN OPTIONAL -- Need M ]], [[ schedulingRequestID-PosMG-Request-r17 SchedulingRequestId OPTIONAL, -- Need R drx-LastTransmissionUL-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ posMG-Request-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ drx-ConfigExt2-v1800 SetupRelease { DRX-ConfigExt2-v1800 } OPTIONAL, -- Need M additionalBSR-TableAllowed-r18 BIT STRING (SIZE (maxNrofLCGs-r18)) OPTIONAL, -- Need R dsr-ConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLCGs-r18)) OF LCG-DSR-Config-r18 OPTIONAL, -- Need N dsr-ConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLCGs-r18)) OF LCG-Id-r18 OPTIONAL, -- Need N tar-Config-r18 SetupRelease { TAR-Config-r18 } OPTIONAL -- Need M ]] } DataInactivityTimer ::= ENUMERATED {s1, s2, s3, s5, s7, s10, s15, s20, s40, s50, s60, s80, s100, s120, s150, s180} MBS-RNTI-SpecificConfig-r17 ::= SEQUENCE { mbs-RNTI-SpecificConfigId-r17 MBS-RNTI-SpecificConfigId-r17, groupCommon-RNTI-r17 CHOICE { g-RNTI RNTI-Value, g-CS-RNTI RNTI-Value }, drx-ConfigPTM-r17 SetupRelease { DRX-ConfigPTM-r17 } OPTIONAL, -- Need M harq-FeedbackEnablerMulticast-r17 ENUMERATED {dci-enabler, enabled} OPTIONAL, -- Need S harq-FeedbackOptionMulticast-r17 ENUMERATED {ack-nack, nack-only} OPTIONAL, -- Cond HARQFeedback pdsch-AggregationFactor-r17 ENUMERATED {n2, n4, n8} OPTIONAL -- Cond G-RNTI } MBS-RNTI-SpecificConfigId-r17 ::= INTEGER (0..maxG-RNTI-1-r17) LCG-DSR-Config-r18 ::= SEQUENCE { lcg-Id-r18 LCG-Id-r18, remainingTimeThreshold-r18 INTEGER (1..64) } LCG-Id-r18 ::= INTEGER (0..maxLCG-ID) -- TAG-MAC-CELLGROUPCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
3,029 | 5.34.4 Usage of an UL Classifier for a PDU Session controlled by I-SMF | This clause applies only in the case of non-roaming or LBO roaming as control of UL CL/BP in VPLMN is not supported in HR case. When I-SMF is involved for a PDU Session, it is possible that the UL CL controlled by I-SMF is inserted into the data path of the PDU Session. The usage of an ULCL controlled by I-SMF in the data path of a PDU Session is depicted in Figure 5.34.4-1. Figure 5.34.4-1: User plane Architecture for the Uplink Classifier controlled by I-SMF The I-SMF determines whether UL CL will be inserted based on information received from SMF, and the I-SMF selects the UPFs acting as UL CL and/or PDU Session Anchor providing local access to the Data Network. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.34.4 |
3,030 | 8.7 Sustained downlink data rate provided by lower layers | The purpose of the test is to verify that the Layer 1 and Layer 2 correctly process in a sustained manner the received packets corresponding to the maximum number of DL-SCH transport block bits received within a TTI for the UE category indicated. The sustained downlink data rate shall be verified in terms of the success rate of delivered PDCP SDU(s) by Layer 2. The test case below specifies the RF conditions and the required success rate of delivered TB by Layer 1 to meet the sustained data rate requirement. The size of the TB per TTI corresponds to the largest possible DL-SCH transport block for each UE category using the maximum number of layers for spatial multiplexing. Transmission modes 1 and 3 are used with radio conditions resembling a scenario where sustained maximum data rates are available. Test case is selected according to table 8.7-1 depending on UE capability for CA and EPDCCH. Table 8.7-1: SDR test applicability | 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 |
3,031 | 7.5.1H Minimum requirements for LTE based 5G terrestrial broadcast | The UE shall fulfil the minimum requirement specified in Table 7.5.1H-1 for all values of an adjacent channel interferer up to β22 dBm. However it is not possible to directly measure the ACS, instead the lower and upper range of test parameters are chosen in Table 7.5.1H-2 and Table 7.5.1H-3 where the throughput shall be β₯ 95% of the maximum throughput as represented by a reported BLER of <5% for the reference measurement channels as specified in Annex A.3.18. Table 7.5.1H-1: Adjacent channel selectivity for LTE based 5G terrestrial broadcast Table 7.5.1H-2: Test parameters for Adjacent channel selectivity, Case 1 Table 7.5.1H-3: Test parameters for Adjacent channel selectivity, Case 2 | 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 | 7.5.1H |
3,032 | β SIB5 | SIB5 contains information relevant only for inter-RAT cell re-selection i.e. information about E-UTRA frequencies and E-UTRAs neighbouring cells relevant for cell re-selection. The IE includes cell re-selection parameters common for a frequency. SIB5 information element -- ASN1START -- TAG-SIB5-START SIB5 ::= SEQUENCE { carrierFreqListEUTRA CarrierFreqListEUTRA OPTIONAL, -- Need R t-ReselectionEUTRA T-Reselection, t-ReselectionEUTRA-SF SpeedStateScaleFactors OPTIONAL, -- Need S lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ carrierFreqListEUTRA-v1610 CarrierFreqListEUTRA-v1610 OPTIONAL -- Need R ]], [[ carrierFreqListEUTRA-v1700 CarrierFreqListEUTRA-v1700 OPTIONAL, -- Need R idleModeMeasVoiceFallback-r17 ENUMERATED{true} OPTIONAL -- Need R ]], [[ carrierFreqListEUTRA-v1800 CarrierFreqListEUTRA-v1800 OPTIONAL -- Need R ]] } CarrierFreqListEUTRA ::= SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA CarrierFreqListEUTRA-v1610 ::= SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA-v1610 CarrierFreqListEUTRA-v1700 ::= SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA-v1700 CarrierFreqListEUTRA-v1800 ::= SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA-v1800 CarrierFreqEUTRA ::= SEQUENCE { carrierFreq ARFCN-ValueEUTRA, eutra-multiBandInfoList EUTRA-MultiBandInfoList OPTIONAL, -- Need R eutra-FreqNeighCellList EUTRA-FreqNeighCellList OPTIONAL, -- Need R eutra-ExcludedCellList EUTRA-FreqExcludedCellList OPTIONAL, -- Need R allowedMeasBandwidth EUTRA-AllowedMeasBandwidth, presenceAntennaPort1 EUTRA-PresenceAntennaPort1, cellReselectionPriority CellReselectionPriority OPTIONAL, -- Need R cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need R threshX-High ReselectionThreshold, threshX-Low ReselectionThreshold, q-RxLevMin INTEGER (-70..-22), q-QualMin INTEGER (-34..-3), p-MaxEUTRA INTEGER (-30..33), threshX-Q SEQUENCE { threshX-HighQ ReselectionThresholdQ, threshX-LowQ ReselectionThresholdQ } OPTIONAL -- Cond RSRQ } CarrierFreqEUTRA-v1610 ::= SEQUENCE { highSpeedEUTRACarrier-r16 ENUMERATED {true} OPTIONAL -- Need R } CarrierFreqEUTRA-v1700 ::= SEQUENCE { eutra-FreqNeighHSDN-CellList-r17 EUTRA-FreqNeighHSDN-CellList-r17 OPTIONAL -- Need R } CarrierFreqEUTRA-v1800 ::= SEQUENCE { eutra-MultiBandInfoListAerial-r18 EUTRA-MultiBandInfoListAerial-r18 OPTIONAL, -- Need R tn-AreaIdList-r18 SEQUENCE (SIZE (1..maxTN-AreaInfo-r18)) OF TN-AreaId-r18 OPTIONAL -- Need R } EUTRA-FreqNeighHSDN-CellList-r17 ::= SEQUENCE (SIZE (1..maxCellEUTRA)) OF EUTRA-PhysCellIdRange EUTRA-FreqExcludedCellList ::= SEQUENCE (SIZE (1..maxEUTRA-CellExcluded)) OF EUTRA-PhysCellIdRange EUTRA-FreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellEUTRA)) OF EUTRA-FreqNeighCellInfo EUTRA-FreqNeighCellInfo ::= SEQUENCE { physCellId EUTRA-PhysCellId, dummy EUTRA-Q-OffsetRange, q-RxLevMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R q-QualMinOffsetCell INTEGER (1..8) OPTIONAL -- Need R } -- TAG-SIB5-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
3,033 | 6.3.2 SMF discovery and selection | The SMF selection functionality is supported by the AMF and SCP and is used to allocate an SMF that shall manage the PDU Session. The SMF selection procedures are described in clause 4.3.2.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The SMF discovery and selection functionality follows the principles stated in clause 6.3.1. If the AMF does discovery, the AMF shall utilize the NRF to discover SMF instance(s) unless SMF information is available by other means, e.g. locally configured on AMF. The AMF provides UE location information to the NRF when trying to discover SMF instance(s). The NRF provides NF profile(s) of SMF instance(s) to the AMF. In addition, the NRF also provides the SMF service area of SMF instance(s) to the AMF. The SMF selection functionality in the AMF selects an SMF instance and an SMF service instance based on the available SMF instances obtained from NRF or on the configured SMF information in the AMF. NOTE 1: Protocol aspects of the access to NRF are specified in TS 29.510[ 5G System; Network function repository services; Stage 3 ] [58]. The SMF selection functionality is applicable to both 3GPP access and non-3GPP access. The SMF selection for Emergency services is described in clause 5.16.4.5. The following factors may be considered during the SMF selection: a) Selected Data Network Name (DNN). In the case of the home routed roaming, the DNN is not applied for the V-SMF selection. b) S-NSSAI of the HPLMN (for non-roaming and home-routed roaming scenarios), and S-NSSAI of the VPLMN (for roaming with local breakout and home-routed roaming scenarios). c) NSI-ID. NOTE 2: The use of NSI -ID in the network is optional and depends on the deployment choices of the operator. If used, the NSI ID is associated with S-NSSAI. d) Access technology being used by the UE. e) Support for Control Plane CIoT 5GS Optimisation. f) Subscription information from UDM, e.g. - per DNN: whether LBO roaming is allowed. - per DNN: whether HR-SBO roaming is allowed. - per S-NSSAI: the subscribed DNN(s). - per (S-NSSAI, subscribed DNN): whether LBO roaming is allowed. - per (S-NSSAI, subscribed DNN): whether HR-SBO roaming is allowed. - per (S-NSSAI, subscribed DNN): whether EPC interworking is supported. - per (S-NSSAI, subscribed DNN): whether selecting the same SMF for all PDU sessions to the same S-NSSAI and DNN is required. - per (S-NSSAI, DNN) associated with 5G VN group: Service Area (LADN service area) for the 5G VN group. In the case of SMF selection for a PDU Session targeting 5G VN group, the AMF may prefer candidate SMF(s) that have an intersection with the LADN service area of the 5G VN group. g) Void. h) Local operator policies. NOTE 3: These policies can take into account whether the SMF to be selected is an I-SMF or a V-SMF or a SMF. i) Load conditions of the candidate SMFs. j) Analytics (i.e. statistics or predictions) for candidate SMFs' load as received from NWDAF (see TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]), if NWDAF is deployed. k) UE location (i.e. TA). l) Service Area of the candidate SMFs. m) Capability of the SMF to support a MA PDU Session. n) If interworking with EPS is required. o) Preference of V-SMF support. This is applicable only for V-SMF selection in the case of home routed roaming. p) Target DNAI. q) Capability of the SMF to support User Plane Remote Provisioning (see clause 5.30.2.10.4.3). r) Supported DNAI list. s) HR-SBO support (according to clause 6.7 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]). t) Capability of the SMF (V-SMF and H-SMF) to support non-3GPP access path switching. To support the allocation of a static IPv4 address and/or a static IPv6 prefix as specified in clause 5.8.2.2.1, a dedicated SMF may be deployed for the indicated combination of DNN and S-NSSAI and registered to the NRF, or provided by the UDM as part of the subscription data. In the case of delegated discovery, the AMF, shall send all the available factors a)-d), k) and n) to the SCP. In addition, the AMF may indicate to the SCP which NRF to use (in the case of NRF dedicated to the target slice). If there is an existing PDU Session and the UE requests to establish another PDU Session to the same DNN and S-NSSAI of the HPLMN, and the UE subscription data indicates the support for interworking with EPS for this DNN and S-NSSAI of the HPLMN or UE subscription data indicates the same SMF shall be selected for all PDU sessions to the same S-NSSAI, DNN, the same SMF in non roaming and LBO case or the same H-SMF in home routed roaming case, shall be selected. In addition, if the UE Context in the AMF provides a SMF ID for an existing PDU session to the same DNN, S-NSSAI, the AMF uses the stored SMF ID for the additional PDU Session. In any such a case where the AMF can determine which SMF should be selected, if delegated discovery is used, the AMF shall indicate a desired NF Instance ID so that the SCP is able to route the message to the relevant SMF. Otherwise, if UE subscription data does not indicate the support for interworking with EPS for this DNN and S-NSSAI, a different SMF in non roaming and LBO case or a different H-SMF in home routed roaming case, may be selected. For example, to support a SMF load balancing or to support a graceful SMF shutdown (e.g. a SMF starts to no more take new PDU Sessions). In the home-routed roaming case, the SMF selection functionality selects an SMF in VPLMN based on the S-NSSAI of the VPLMN, as well as an SMF in HPLMN based on the S-NSSAI of the HPLMN. This is specified in clause 4.3.2.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the HR-SBO roaming is allowed for the PDU Session, the DNN is also considered for V-SMF selection. When the UE requests to establish a PDU Session to a DNN and an S-NSSAI of the HPLMN, if the UE MM Core Network Capability indicates the UE supports EPC NAS and optionally, if the UE subscription indicates the support for interworking with EPS for this DNN and S-NSSAI of the HPLMN, the selection functionality (in AMF or SCP) selects a combined SMF+PGW-C. Otherwise, a standalone SMF may be selected. If the UDM provides a subscription context that allows for handling the PDU Session in the VPLMN (i.e. using LBO) for this DNN and S-NSSAI of the HPLMN and, optionally, the AMF is configured to know that the VPLMN has a suitable roaming agreement with the HPLMN of the UE, the following applies: - If the AMF does discovery, the SMF selection functionality in AMF selects an SMF from the VPLMN. - If delegated discovery is used, the SCP selects an SMF from the VPLMN. If an SMF in the VPLMN cannot be derived for the DNN and S-NSSAI of the VPLMN, or if the subscription does not allow for handling the PDU Session in the VPLMN using LBO, then the following applies: - If the AMF does discovery, both an SMF in VPLMN and an SMF in HPLMN are selected, and the DNN and S-NSSAI of the HPLMN is used to derive an SMF identifier from the HPLMN. - If delegated discovery is used: - The AMF performs discovery and selection of H-SMF from NRF. The AMF may indicate the maximum number of H-SMF instances to be returned from NRF, i.e. SMF selection at NRF. - The AMF sends Nsmf_PDUSession_CreateSMContext Request to SCP, which includes the endpoint (e.g. URI) of the selected H-SMF, and the discovery and selection parameters as defined in this clause, i.e. parameter for V-SMF selection. The SCP performs discovery and selection of the V-SMF and forwards the request to the selected V-SMF. - The V-SMF sends the Nsmf_PDUSession_Create Request towards the H-SMF via the SCP; the V-SMF uses the received endpoint (e.g. URI) of the selected H-SMF to construct the target destination to be addressed. The SCP forwards the request to the H-SMF. - Upon reception of a response from V-SMF, based on the received V-SMF ID the AMF obtains the Service Area of the V-SMF from NRF. The AMF uses the Service Area of the V-SMF to determine the need for V-SMF relocation upon subsequent UE mobility. If the initially selected SMF in VPLMN (for roaming with LBO) detects it does not understand information in the UE request, it may reject the N11 message (related with a PDU Session Establishment Request message) with a proper N11 cause triggering the AMF to select both a new SMF in the VPLMN and a SMF in the HPLMN (for home routed roaming). The AMF selects SMF(s) considering support for CIoT 5GS optimisations (e.g. Control Plane CIoT 5GS Optimisation). In the case of onboarding of UEs for SNPNs, when the UE is registered for SNPN onboarding the AMF selects SMF(s) of Onboarding Network considering the Capability of SMF to support User Plane Remote Provisioning. Additional details of AMF selection of an I-SMF are described in clause 5.34. In the case of home routed scenario, the AMF selects a new V-SMF if it determines that the current V-SMF cannot serve the UE location. The selection/relocation is same as an I-SMF selection/relocation as described in clause 5.34. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.2 |
3,034 | 5.7.10.5 RA information determination | The UE shall, for the last successfully completed or last failed random-access procedure, set the content in ra-InformationCommon as follows: 1> set the absoluteFrequencyPointA to indicate the absolute frequency of the reference resource block associated to the random-access resources used in the random-access procedure; 1> set the locationAndBandwidth and subcarrierSpacing associated to the UL BWP of the random-access resources used in the random-access procedure; 1> if contention based random-access resources are used in the random-access procedure: 2> set the msgA_RO-FrequencyStart and msgA-RO-FDM and msgA-SubcarrierSpacing associated to the 2 step random- access resources if used in the random-access procedure; 2> if msgA-SubcarrierSpacing associated to the 2 step random-access resources used in the random-access procedure is available: 3> set the msgA-SubcarrierSpacing associated to the 2 step random-access resources used in the random-access procedure; 2> else if only 2 step random-access resources are available in the UL BWP used in the random-access procedure: 3> set the msgA-SCS-From-prach-ConfigurationIndex to the subcarrier spacing as derived from the msgA-PRACH-ConfigurationIndex used in the 2-step random-access procedure; 2> else: 3> set the msg1-SubcarrierSpacing associated to the 4 step random-access resources used in the random-access procedure; 2> set the msg1-FrequencyStart associated to the 4 step random-access resources if used in the random-access procedure, and if its value is different from the value of msgA-RO-FrequencyStart if it is included in the ra-InformationCommon; 2> set the msg1-FDM associated to the 4 step random-access resources if used in the random-access procedure, and if its value is different from the value of msgA-RO-FDMCFRA if it is included in the ra-InformationCommon; 2> if msg1-SubcarrierSpacing associated to the 4 step random-access resources used in the random-access procedure is available, and if its value is different from the value of msgA-SubcarrierSpacing if it is included in the ra-InformationCommon: 3> set the msg1-SubcarrierSpacing associated to the 4 step random-access resources used in the random-access procedure; 2> else: 3> set the msg1-SCS-From-prach-ConfigurationIndex to the subcarrier spacing as derived from the prach-ConfigurationIndex used in the 4-step random-access procedure, and if its value is different from the value of msgA-SCS-From-prach-ConfigurationIndex if it is included in the ra-InformationCommon; 1> if contention free random-access resources are used in the random-access procedure: 2> set the msg1-FrequencyStartCFRA and msg1-FDMCFRA associated to the 4 step random-access resources if used in the random-access procedure; 2> if msg1-SubcarrierSpacing associated to the 4 step random-access resources used in the random-access procedure is available: 3> set the msg1-SubcarrierSpacingCFRA associated to the 4 step random-access resources used in the random-access procedure; 2> else: 3> set the msg1-SCS-From-prach-ConfigurationIndexCFRA to the subcarrier spacing as derived from the prach-ConfigurationIndex used in the 4 step random-access procedure; 2> set the msgA-RO-FrequencyStartCFRA and msgA-RO-FDMCFRA associated to the 2 step contention free random access resources if used in the random-access procedure; 2> set the msgA-MCS, the nrofPRBs-PerMsgA-PO, the msgA-PUSCH-TimeDomainAllocation, the frequencyStartMsgA-PUSCH, the nrofMsgA-PO-FDM associated to the 2 step random-access resources if used in the random-access procedure; 2> if msgA-SubcarrierSpacing associated to the 2 step random-access resources used in the random-access procedure is available: 3> set the msgA-SubcarrierSpacing associated to the 2 step random-access resources used in the random-access procedure; 2> else if only 2 step random-access resources are available in the UL BWP used in the random-access procedure: 3> set the msgA-SCS-From-prach-ConfigurationIndex to the subcarrier spacing as derived from the msgA-PRACH-ConfigurationIndex used in the 2-step random-access procedure; 2> else: 3> set the msg1-SubcarrierSpacing associated to the 4 step random-access resources used in the random-access procedure; 1> if the random access procedure is initialized with RA_TYPE set to 2-stepRA as described in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]: 2> set the dlPathlossRSRP to the measeured RSRP of the DL pathloss reference obtained at the time of RA_Type selection stage of the initialization of the RA procedure as captured in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 2> if the configuration for the random access msgA-TransMax was configured in RACH-ConfigDedicated for this random access procedure, and raPurpose is set to reconfigurationWithSync: 3> set msgA-TransMax to the value of msgA-TransMax in RACH-ConfigDedicated; 2> else if msgA-TransMax was configured in RACH-ConfigCommonTwoStepRA: 3> set msgA-TransMax to the value of msgA-TransMax in RACH-ConfigCommonTwoStepRA; 2> set the msgA-PUSCH-PayloadSize to the size of the overall payload available in the UE buffer at the time of initiating the 2 step RA procedure; 1> if the purpose of the random access procedure is to request on-demand system information (i.e., if the raPurpose is set to requestForOtherSI or msg3RequestForOtherSI): 2> set the intendedSIBs to indicate the SIB(s) the UE wanted to receive as a result of the SI request; 2> set the ssbsForSI-Acquisition to indicate the SSB(s) used to receive the SI message; 2> if the on-demand system information acquisition was successful: 3> set the onDemandSISuccess to true; 1> if one or more of the features including RedCap and/or Slicing and/or SDT and/or MSG3 repetition are applicable for this random-access procedure as specified in clause 5.1.1b of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]: 2> set the triggeredFeatureCombination to indicate all the features triggering this random-access procedure as below: 3> if this random-access procedure is triggered by RedCap, includes redCap; 3> if this random-access procedure is triggered by SDT, includes smallData; 3> if this random-access procedure is triggered by Msg3 repetition, includes msg3-Repetitions; 3> if this random-access procedure is triggered by slicing, set nsag to the NSAG ID applied in the random-access procedure and set the triggered-S-NSSAI-List to include all the S-NSSAI(s) associated to the slices triggering the access attempt in the random-access procedure; 2> if the value of used feature or combination of features is different from the triggeredFeatureCombination: 3> set the usedFeatureCombination to indicate one or more features of FeatureCombination associated to the random-access resource used in the random-access procedure as below: 4> if RedCap is part of the used FeatureCombination, include redCap; 4> if SDT is part of the used FeatureCombination, include smallData; 4> if Msg3 repetition is part of the used FeatureCombination, include msg3-Repetitions; 4> if NSAG(s) is part of the used FeatureCombination, set NSAG-List to include the NSAG-ID(s) configured for the used FeatureCombination; 1> if the random-access procedure is initiated for SDT and the SDT transmission was failed: 3> include the sdt-Failed; 1> set the parameters associated to the successive random-access attempts associated to the selected beam in the perRAInfoList as follows: 2> if the random-access resource used is associated to a SS/PBCH block, set the associated random-access parameters for the successive random-access attempts associated to the same SS/PBCH block for one or more random-access attempts as follows: 3> set the ssb-Index to include the SS/PBCH block index associated to the used random-access resource; 3> set the numberOfPreamblesSentOnSSB to indicate the number of successive random-access attempts associated to the SS/PBCH block; 3> if all preamble transmissions for the successive random-access attempts associated to this SS/PBCH block were blocked by LBT: 4> include allPreamblesBlocked; 3> else: 4> if LBT failure indication was received from lower layers for the last random-access preamble transmission attempt in the SS/PBCH block associated to the ssb-Index, before changing the SS/PBCH block for random access preamble transmission: 5> include lbt-Detected; 3> for each random-access attempt performed on the random-access resource, except the random-access attempts for which LBT failure indication was received from lower layers, include the following parameters in the chronological order of the random-access attempt: 4> if the random-access attempt is performed on the contention based random-access resource and if raPurpose is not equal to 'requestForOtherSI', include contentionDetected as follows: 5> if contention resolution was not successful as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6] for the transmitted preamble: 6> set the contentionDetected to true; 5> else: 6> set the contentionDetected to false; 4> if the random access attempt is a 2-step random access attempt: 5> if fallback from 2-step random access to 4-step random access occurred during the random access attempt: 6> set fallbackToFourStepRA to true; 4> if the random-access attempt is performed on the contention based random-access resource; or 4> if the random-access attempt is performed on the contention free random-access resource and if the random-access procedure was initiated due to the PDCCH ordering: 5> if the random access attempt is a 4-step random access attempt and the SS/PBCH block RSRP of the SS/PBCH block corresponding to the random-access resource used in the random-access attempt is above rsrp-ThresholdSSB; or 5> if the random access attempt is a 2-step random access attempt and the SS/PBCH block RSRP of the SS/PBCH block corresponding to the random-access resource used in the random-access attempt is above msgA-RSRP-ThresholdSSB: 6> set the dlRSRPAboveThreshold to true; 5> else: 6> set the dlRSRPAboveThreshold to false; 2> else if the random-access resource used is associated to a CSI-RS, set the associated random-access parameters for the successive random-access attempts associated to the same CSI-RS for one or more random-access attempts as follows: 3> set the csi-RS-Index to include the CSI-RS index associated to the used random-access resource; 3> set the numberOfPreamblesSentOnCSI-RS to indicate the number of successive random-access attempts associated to the CSI-RS; 3> if all preamble transmissions for the successive random-access attempts associated to this CSI-RS were blocked by LBT: 4> include allPreamblesBlocked; 3> else: 4> if LBT failure indication was received from lower layers for the last random-access preamble transmission attempt in the CSI-RS associated to the csi-RS-Index, before changing the CSI-RS for random access preamble transmission: 5> include lbt-Detected; 1> if at least one LBT failure indication has been received from lower layers during the random-access procedure: 2> set the numberOfLBTFailures to indicate the total number of random-access attempts for which LBT failure indications have been received from lower layers in the random-access procedure. The UE shall, for all the BWPs in which consistent LBT failures are triggered and not cancelled at the moment of successful RA completion or for all the BWPs in which consistent LBT failures are detected prior the RLF/HOF, set the below parameters in attemptedBWP-InfoList in the chronological order of BWP selection: 1> set the locationAndBandwidth and subcarrierSpacing associated to the UL BWP. NOTE 1: Void. NOTE 2: If allPreamblesBlocked is included, it is left to UE implementation how to set the numberOfPreamblesSentOnSSB-r16, numberOfPreamblesSentOnCSI-RS-r16 and the perRAAttemptInfoList-r16. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.10.5 |
3,035 | 9.2.7.1 Frame structure type 3 wth FDD Pcell | The following requirements apply to UE Category β₯1. For the parameters specified in Table 9.2.7.1-1, Table 9.2.7.1-2and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, two sets of CQI reports are obtained for LAA Scell, The first one is obtained by reports whose reference resource is in the downlink subframes with 6 dB transmission power boost, i.e., high power subframes. The second one is obtained by reports whose reference resource is in the downlink subframe with 0 dB transmission power boost, i.e., low power subframe. In the test, PDSCH transport format in high power subframe is determined by first set of CQI reports and PDSCH transport format in low power subframe is determined by second set of CQI reports. The reported CQI value in the first set of reports shall be in the range of Β±1 of the reported median more than 90% of the first set of reports. The reported CQI value in the second set of reports shall be in the range of Β±1 of the reported median more than 90% of the second set of reports. If the PDSCH BLER in the high power subframes using the transport format indicated by wideband CQI median is less than or equal to 0.1, the BLER in high power subframes using the transport format indicated by the (wideband CQI median + 1) shall be greater than 0.1. If the PDSCH BLER in high power subframes using the transport format indicated by the wideband CQI median is greater than 0.1, the BLER in high power subframes using transport format indicated by (wideband CQI median β 1) shall be less than or equal to 0.1. If the PDSCH BLER in the low power subframes using the transport format indicated by wideband CQI median is less than or equal to 0.1, the BLER in low power subframes using the transport format indicated by the (wideband CQI median + 1) shall be greater than 0.1. If the PDSCH BLER in the low power subframes using the transport format indicated by the wideband CQI median is greater than 0.1, the BLER in low power subframes using transport format indicated by (wideband CQI median β 1) shall be less than or equal to 0.1. The value of the wideband CQI for the first set of CQI report minus the wideband CQI median for second set of CQI shall be larger than or equal to 2 in Test 1 and Test 2. Table 9.2.7.1-1: Parameters for PUSCH 3-1 static test on FDD Pcell Table 9.2.7.1-2: PUSCH 3-1 static test on LAA Scell | 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.2.7.1 |
3,036 | 8.3.2.4.4 Minimum requirement with Different Cell ID and non-Colliding CRS (with single NZP CSI-RS resource and CRS assistance information is configured) | The requirements are specified in Table 8.3.2.4.4-3, with the additional parameters in Table 8.3.2.4.4-1 and Table 8.3.2.4.4-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario where three transmission points have different Cell ID and non-colliding CRS. In particular the test verifies that the UE, configured with quasi co-location type B, performs correct tracking and compensation of the frequency difference and time difference between two transmission points, channel parameters estimation and rate matching behaviour according to the βPDSCH RE Mapping and Quasi-Co-Location Indicatorβ signalling defined in [6]. Further, the test verifies that the UE, configured with the CRS assistance information [7], can mitigate interference from CRS for demodulation. The CRS assistance information [7] includes TP 3. In Table 8.3.2.4.4-1, transmission point 1 (TP 1) is serving cell transmitting PDCCH, synchronization signals and PBCH, transmission point 2 (TP 2) transmits PDSCH with different Cell ID, and Transmission point 3 (TP 3) is the aggressor transmission point. The downlink physical channel setup for TP 1 is according to Table C.3.4-1, for TP 2 is according to Table C.3.4-2, and for TP 3 is according to Annex C.3.2. Table 8.3.2.4.4-1: Test Parameters for quasi co-location type B with different Cell ID and non-colliding CRS when CRS assistance information is configured Table 8.3.2.4.4-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.3.2.4.4-3: Performance Requirements for quasi co-location type B with different Cell ID and non-Colliding CRS when CRS assistance information is configured | 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.3.2.4.4 |
3,037 | 5.5.4.9 Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2) | The UE shall: 1> consider the entering condition for this event to be satisfied when both condition B2-1 and condition B2-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition B2-3 or condition B2-4, i.e. at least one of the two, as specified below, is fulfilled; Inequality B2-1 (Entering condition 1) Mp + Hys < Thresh1 Inequality B2-2 (Entering condition 2) Mn + Ofn + Ocn β Hys > Thresh2 Inequality B2-3 (Leaving condition 1) Mp β Hys > Thresh1 Inequality B2-4 (Leaving condition 2) Mn + Ofn + Ocn + Hys < Thresh2 The variables in the formula are defined as follows: Mp is the measurement result of the PCell, not taking into account any offsets. Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets. Ofn is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. eutra-Q-OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the inter-RAT neighbour cell, utra-FDD-Q-OffsetRange as defined within the measObjectUTRA-FDD corresponding to the frequency of the neighbour inter-RAT cell). Ocn is the cell specific offset of the inter-RAT neighbour cell (i.e. cellIndividualOffset as defined within the measObjectEUTRA corresponding to the neighbour inter-RAT cell, or cellIndividualOffset as defined within reportConfigInterRAT), and set to zero if not configured for the neighbour cell. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event). Thresh1 is the threshold parameter for this event (i.e. b2-Threshold1 as defined within reportConfigInterRAT for this event). Thresh2 is the threshold parameter for this event (i.e. b2-Threshold2EUTRA as defined within reportConfigInterRAT for this event, b2-Threshold2UTRA-FDD as defined for UTRA-FDD within reportConfigInterRAT for this event). Mp is expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR. Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell. Ofn, Ocn, Hys are expressed in dB. Thresh1 is expressed in the same unit as Mp. Thresh2 is expressed in the same unit as Mn. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.9 |
3,038 | 8.21.3 RAI field | The coding of RAI (Routing Area Identity) is depicted in Figure 8.21.3-1. Only zero or one RAI field shall be present in ULI IE. Figure 8.21.3-1: RAI field The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet c+3 is the most significant bit and bit 1 of Octet c+4 the least significant bit. The coding of the location area code is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used (see 3GPP TS 23.003[ Numbering, addressing and identification ] [2]). The Routing Area Code (RAC) consists of 2 octets. Only Octet c+5 contains the RAC. Octet c+6 is coded as all 1's (11111111). The RAC is defined by the operator. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used (see 3GPP TS 23.003[ Numbering, addressing and identification ] [2]). | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.21.3 |
3,039 | β PTRS-UplinkConfig | The IE PTRS-UplinkConfig is used to configure uplink Phase-Tracking-Reference-Signals (PTRS). PTRS-UplinkConfig information element -- ASN1START -- TAG-PTRS-UPLINKCONFIG-START PTRS-UplinkConfig ::= SEQUENCE { transformPrecoderDisabled SEQUENCE { frequencyDensity SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need S timeDensity SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, -- Need S maxNrofPorts ENUMERATED {n1, n2}, resourceElementOffset ENUMERATED {offset01, offset10, offset11 } OPTIONAL, -- Need S ptrs-Power ENUMERATED {p00, p01, p10, p11} } OPTIONAL, -- Need R transformPrecoderEnabled SEQUENCE { sampleDensity SEQUENCE (SIZE (5)) OF INTEGER (1..276), timeDensityTransformPrecoding ENUMERATED {d2} OPTIONAL -- Need S } OPTIONAL, -- Need R ..., [[ maxNrofPorts-SDM-r18 ENUMERATED {n1, n2} OPTIONAL -- Need R ]] } -- TAG-PTRS-UPLINKCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
3,040 | 7.9.5 PGW Restart Notification | The direction of this message shall be from SGW to MME/S4-SGSN (see Table 6.1-1). If both the SGW and the MME/S4-SGSN support the PRN feature (see clause 8.83), a PGW Restart Notification shall be sent when the SGW detects that the peer PGW has restarted, and a PGW Restart Notification may be sent when the SGW detects that the peer PGW has failed and not restarted, as specified in 3GPP TS 23.007[ Restoration procedures ] [17]. Table 7.9.5-1 specifies the presence of IEs in this message. Table 7.9.5-1: Information Elements in PGW Restart Notification | 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.9.5 |
3,041 | 6.3.11 Handling of Reliable Data Service | If the UE supports Reliable Data Service (see 3GPP TS 24.250[ Protocol for Reliable Data Service; Stage 3 ] [51]), the UE may request data transfer using Reliable Data Service for a PDN connection in the Extended protocol configuration options IE during attach and UE-requested PDN connectivity procedures (see clause 5.5.1 and 6.5.1). The Reliable Data Service may only be used with PDN connections for which the "Control plane only" indicator is set or with PDN connections using the control plane CIoT EPS optimization when the MME does not move such PDN connections to the user plane. The SCEF or P-GW shall inform the UE about the acceptance of UE's request for Reliable Data Service usage during the activation of the default bearer of a PDN connection (see clause 6.4.1) in the Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. If the SCEF or P-GW accepts the use of Reliable Data Service to transfer data for the specified PDN connection, the UE shall use this PDN connection exclusively for data transfer using Reliable Data Service; otherwise the UE shall not use this PDN connection for data transfer using Reliable Data Service. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.11 |
3,042 | 4.13.8.4 Coverage availability information provisioning to the MME | The MME may use satellite coverage availability information to support satellite access by UEs with discontinuous coverage operation. Satellite coverage availability information may be provisioned to the MME by O&M. NOTE: In this release of the specification there is no support for provisioning of satellite coverage availability information to an MME from an AF. The satellite coverage availability information provisioned to the MME describes when and where satellite coverage is expected to be available in an area. The satellite coverage availability information is not UE specific and can be applied by the MME for any UE in the affected area. | 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.8.4 |
3,043 | 5.21.2.1 AMF Addition/Update | The 5G System should support establishment of association between AMF and 5G-AN node. A new AMF can be added to an AMF set and association between AMF and GUAMI can be created and/or updated as follows: - AMF shall be able to dynamically update the NRF with the new or updated GUAMI(s) to provide mapping between GUAMI(s) and AMF information. Association between GUAMI(s) and AMF is published to NRF. In addition, to deal with planned maintenance and failure, an AMF may optionally provide backup AMF information, i.e. it act as a backup AMF if the indicated GUAMI associated AMF is unavailable. It is assumed that the backup AMF and the original AMF are in the same AMF set as they have access to the same UE context. Based on that information one GUAMI is associated with an AMF, optionally with a backup AMF used for planned removal and/or another (same or different) backup AMF used for failure. - Upon successful update, the NRF considers the new and/or updated GUAMI(s) for providing AMF discovery results to the requester. Requester can be other CP network functions. - The new AMF provides its GUAMI to 5G-AN and 5G-AN store this association. If the association between the same GUAMI and another AMF exists in the 5G-AN (e.g. due to AMF planned removal), the previously stored AMF is replaced by the new AMF for the corresponding GUAMI association. Information about new AMF should be published and available in the DNS system. It should allow 5G-AN to discover AMF and setup associations with the AMF required. N2 setup procedure should allow the possibility of AMFs within the AMF Set to advertise the same AMF Pointer and/or distinct AMF Pointer value(s) to the 5G-AN node. To support the legacy EPC core network entity (i.e. MME) to discover and communicate with the AMF, the information about the AMF should be published and available in the DNS system. Furthermore, GUMMEI and GUAMI encoding space should be partitioned to avoid overlapping values in order to enable MME discover an AMF without ambiguity. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.2.1 |
3,044 | 13a Interworking with IMS 13a.1 General | Interworking with the IP Multimedia Core Network Subsystem (IMS) puts additional requirements on the GGSN/P-GW. When the MS/UE connects to the IP Multimedia Core Network Subsystem (IMS), specific parameters in Session Management messages may be handled. The IMS specific parameters are: IMS signalling flag, P-CSCF address request, P-CSCF restoration support, returned P-CSCF address(es) and flow identifier(s). For interworking with the IMS, the Gx interface (see 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [75]) is used to correlate the session (SIP/SDP) and the bearer (PDP Contexts). The mechanisms in GGSN/P-GW to support IMS shall be: - P-CSCF discovery. - Dedicated signalling bearer (e.g. PDP contexts) (with or without enhanced QoS) for IMS signalling; with associated packet filters to permit signalling to/from designated servers. - Gx interface for policy and charging control of bearer (e.g. PDP contexts) for IMS media flows. - P-CSCF restoration. These mechanisms are however not restricted to the IMS and could be used for other services that could benefit from these mechanisms. The P-GW shall not modify the fields Type of Service (IPv4) and Traffic Class (IPv6) of the received downlink packets. NOTE: The P-CSCF can support paging policy differentiation for different traffic or service types over LTE by marking the fields Type of Service (IPv4) and Traffic Class (IPv6) (see clause L.3.2.4 of 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [47]). | 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 | 13a |
3,045 | 8.6.2 Mapping of an EPS security context to a 5G security context | The derivation of a mapped 5G security context from an EPS security is done as described below. - The KAMF' key, taken as the KAMF, shall be derived from the KASME using the EPS NAS Uplink COUNT of the TAU message included in the Registration Request message in idle mode mobility or the NH value in handovers as described in clause A.15. - The ngKSI for the newly derived KAMF key shall be defined such as the value field is taken from the eKSI and the type field is set to indicate a mapped security context. - The 5G NAS COUNT values in the mapped 5G security context shall be set to 0. NOTE: The selection of the 5G NAS algorithms is performed by the AMF and signalled to the UE either in the NAS Container during handovers as described in clause 8.4, or in a NAS SMC during idle mode mobility as described in clause 8.2. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 8.6.2 |
3,046 | 9.3.2.1.1 FDD | For the parameters specified in Table 9.3.2.1.1-1 and Table 9.3.2.1.1-3, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.2.1.1-2 and Table 9.3.2.1.1-4 and 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 The applicability of the requirement with 5MHz bandwidth as specificed in Table 9.3.2.1.1-3 and Table 9.3.2.1.1-4 is defined in 9.1.1.1. Table 9.3.2.1.1-1 Fading test for single antenna (FDD) Table 9.3.2.1.1-2 Minimum requirement (FDD) Table 9.3.2.1.1-3 Fading test for single antenna (FDD) Table 9.3.2.1.1-4 Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.2.1.1 |
3,047 | 8.2.1.2.5 Enhanced Performance Requirement Type B - 2 Tx Antenna Ports with TM2 interference model | The requirements are specified in Table 8.2.1.2.5-2, with the addition of parameters in Table 8.2.1.2.5-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of two interfering cells applying transmission mode 2 interference model defined in clause B.6.1. In Table 8.2.1.2.5-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.2.1.2.5-1: Test Parameters for Transmit Diversity Performance (FRC) with TM2 interference model Table 8.2.1.2.5-2: Minimum Performance for Enhanced Performance Requirement Type B, Transmit Diversity (FRC) with TM2 interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.2.5 |
3,048 | β SL-BWP-PoolConfigCommon | The IE SL-BWP-PoolConfigCommon is used to configure the cell-specific NR sidelink communication resource pool. SL-BWP-PoolConfigCommon information element -- ASN1START -- TAG-SL-BWP-POOLCONFIGCOMMON-START SL-BWP-PoolConfigCommon-r16 ::= SEQUENCE { sl-RxPool-r16 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 OPTIONAL, -- Need R sl-TxPoolSelectedNormal-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolConfig-r16 OPTIONAL, -- Need R sl-TxPoolExceptional-r16 SL-ResourcePoolConfig-r16 OPTIONAL -- Need R } -- TAG-SL-BWP-POOLCONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
3,049 | 5.5.2 Connection Management | This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. The UE mentioned in this clause corresponds to the 5G-RG in the case of W-5GAN and to the W-AGF in the case of FN-RG. In the case of N5CW devices access 5GC via trusted WLAN access networks, the UE mentioned in this clause corresponds to TWIF. A UE that successfully establishes a Non-3GPP Access Connection to the 5GC over a Non-3GPP access transitions to CM-CONNECTED state for the Non-3GPP access. In the case of Untrusted Non-3GPP access to 5GC, the Non-3GPP Access Connection corresponds to an NWu connection. In the case of Trusted access to 5GC, the Non-3GPP Access Connection corresponds to an NWt connection. In the case of N5CW devices access 5GC via trusted WLAN access networks, the Non-3GPP Access Connection corresponds to an Yt' connection. In the case of Wireline access to 5GC, the Non-3GPP Access Connection corresponds to a Y4 connection and to Y5 connection. A UE does not establish multiple simultaneous Non-3GPP Access Connection to the 5GC. The Non-3GPP Access Connection is released either as a result of an Explicit Deregistration procedure or an AN Release procedure. In the case of Untrusted Non-3GPP access, Trusted Non-3GPP access and W-5GAN access to 5GC, the N3IWF, TNGF, TWIF and W-AGF may in addition explicitly release the NWu, NWt, Yt', Y4 and Y5 signalling connection due to NWu, NWt, Yt', Y4 and Y5 connection failure, respectively. In the case of NWu and NWt, the release may be determined by the "dead peer detection" mechanism in IKEv2 defined in RFC 7296 [60]. In the case of Y4 and Y5 the release may be detected for example by lost of synchronisation of physical link, lost of PPPoE session, etc. Further details on how NWu, NWt, Yt', Y4 and Y5 connection failure is detected is out of scope of 3GPP specifications. For W-5GCAN, the W-AGF explicitly releases the N2 connection due to Y4 or Y5 connection failure, as determined by the "dead peer detection" mechanism in DOCSIS MULPI [89]. The release of the Non-3GPP Access Connection between the UE and the N3IWF, TNGF, TWIF or W-AGF shall be interpreted as follows: - By the N3IWF, TNGF, TWIF and W-AGF as a criterion to release the N2 connection. - By the UE as a criterion for the UE to transition to CM-IDLE. A UE registered over non-3GPP access remains in RM-REGISTERED state, unless the Non-3GPP Access Connection release occurs as part of a Deregistration procedure over non-3GPP access in which case the UE enters the RM-DEREGISTERED state. When the UE in RM-REGISTERED transitions to CM-IDLE, the UE non-3GPP Deregistration timer starts running in the UE. The UE non-3GPP Deregistration timer stops when the UE moves to CM-CONNECTED state or to the RM-DEREGISTERED state. NOTE 1: When moved to CM-IDLE state over one access, the UE can attempt to re-activate UP connections for the PDU Sessions over other access, per UE policies and depending on the availability of these accesses. NOTE 2: The release of the NWu, NWt, Yt', Y4 or Y5 at the UE can occur as a result of explicit signalling from the N3IWF, TNGF, TWIF or W-AGF respectively, e.g. IKE INFORMATION EXCHANGE in the case of NWu or as a result of the UE detecting NWu, NWt, Yt', Y4 or Y5 connection failure, e.g. as determined by the "dead peer detection" mechanism in IKEv2 as defined in RFC 7296 [60] for NWu, NWt and Yt' or W-5GAN access specific mechanism for Y4 and Y5. Further details on how the UE detects NWu, NWt, Yt', Y4 or Y5 connection failure is out of scope of 3GPP specifications. In the case of Non-3GPP access, when the AMF releases the N2 interface, the N3IWF, TNGF, TWIF and W-AGF shall release all the resources associated with the UE including the Non-3GPP Access Connection with the UE and its corresponding N3 resources. A release of the N2 connection by the AMF shall set the CM state for the UE in the AMF to CM-IDLE. NOTE 3: It is assumed that a UE configured to receive services from a 5GC over non-3GPP access that is RM-DEREGISTERED or CM-IDLE over the non-3GPP access will attempt to establish Non-3GPP Access Connection and transition to CM-CONNECTED state whenever the UE successfully connects to a non-3GPP access unless prohibited by the network to make a N3GPP Access Connection (e.g. due to network congestion). An UE cannot be paged on Non-3GPP access network. When a UE registered simultaneously over a 3GPP access and a non-3GPP access moves all the PDU Sessions to one of the accesses, whether the UE initiates a Deregistration procedure in the access that has no PDU Sessions is up to the UE implementation. Release of PDU Sessions over the non-3GPP access does not imply the release of N2 connection. When the UE has PDU Sessions routed over the non-3GPP access and the UE state becomes CM-IDLE for the non-3GPP access, these PDU Sessions are not released to enable the UE to move the PDU Sessions over the 3GPP access based on UE policies. The core network maintains the PDU Sessions but deactivates the N3 user plane connection for such PDU Sessions. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.2 |
3,050 | 5.15.11 Network Slice Admission Control 5.15.11.0 General | The Network Slice Admission Control Function (NSACF) monitors and controls the number of registered UEs per network slice and/or the number of PDU Sessions per network slice for the network slices that are subject to Network Slice Admission Control (NSAC). The NSACF is configured with the maximum number of UEs and/or the maximum number of PDU Sessions allowed to be served per S-NSSAI subject to NSAC. The NSACF is also configured with information indicating applicable access type(s) for the S-NSSAI (i.e. 3GPP Access Type, Non-3GPP Access Type, or both). The NSACF also provides event-based Network Slice status notifications and reports to the consumer NFs (e.g. AF). A NSACF can be configured with the NSAC Service Area(s) it serves. The NSAC Service Area Identifier is a unique identifier in a PLMN or SNPN. The consumer NFs which use the NSAC services are configured with a single and network slice independent value of the NSAC Service Area Identifier so they can discover the correct NSACF (see clause 6.3.22). The NSACF may be responsible for one or more S-NSSAIs. For one S-NSSAI there may be one or multiple NSACFs deployed in a network (a PLMN or a SNPN) as follows: - If a PLMN or SNPN is configured with a single NSAC service area, there is a single NSACF configured with the maximum number of UEs per network slice and/or the maximum number of PDU Sessions per network slice, which are valid in the network. In this case there is no need to provision any NSAC Service Area Identifier value in the PLMN or SNPN. - If a PLMN or SNPN is configured with multiple NSAC service areas, an NSACF may be deployed on a NSAC service area basis, which can be one NSACF instance or one NSACF Set. There are three NSAC architecture options: - Option 1: non-Hierarchical NSAC architecture. In this architecture, independent NSACFs are deployed in every NSAC service area. There is no interaction between the NSACFs deployed in different NSAC service areas. Each NSACF is configured with the maximum number of UEs per network slice and/or the maximum number of PDU Sessions which are valid in the NSAC service area (see clauses 5.15.11.1.1 and 5.15.11.2.1 for more details). - Option 2: Centralized NSAC architecture. In this architecture, a single centralized NSACF is deployed in the network to handle admissions in all NSAC service areas. The centralized NSACF is configured with the total number of UEs per network slice and the maximum number of PDU Sessions for the entire PLMN. NSAC Requests from AMF or SMF to the single centralized NSCAF in this case includes the NSAC service area of the NF consumer if multiple NSAC service areas are deployed in PLMN. NOTE 1: It is possible to configure in the centralized architecture the maximum number of registered UEs and/or the maximum number of PDU sessions per NSAC service area if required by the operator. In this case, NSAC can be performed on a per NSAC service area. - Option 3: Hierarchical NSAC architecture is deployed in the network. There are two roles of NSACF and interaction between them may be required (see clauses 5.15.11.1.2 and 5.15.11.2.2 for more details): - Primary NSACF, controls and distributes of the maximum number of UEs and/or the maximum number of PDU Sessions for other NSACF(s) deployed in different NSAC service Area. The Primary NSACF handles overall NSAC for an S-NSSAI at the global level (i.e. it is ultimately responsible for the NSAC for an S-NSSAI). β NSACF is responsible for one or multiple NSAC service Area. And one NSAC service area is only associated with one NSACF instance or one NSACF Set. NOTE 2: When multiple NSACFs are deployed, how the maximum number of UEs per network slice and the maximum number of PDU Sessions per network slice is distributed (by OAM for Option 1 and by the primary NSACF for Option 3) among multiple NSACFs, i.e. the algorithm of the maximum number distribution, is implementation specific. NOTE 3: When multiple NSACFs are deployed based on option 1, the UE moves to new NSAC service area with a different NSACF, and if the number of UE or PDU Sessions in the target NSACF has reached the maximum number, whether the session continuity can be guaranteed is left to implementation. NOTE 4: When multiple NSACFs are deployed based on Hierarchical NSAC architecture, it is possible that the role of Primary NSACF and the role of NSACF are co-located at the same NSACF instance. Subject to operator policy and national/regional regulations, the AMF may exempt UEs and the SMF may exempt PDU sessions from NSAC when the UE and/or PDU Session is used for Emergency service or for Critical and Priority services (e.g. MCX, MPS). When the AMF receives a Registration Request for an Emergency Registration, or with a Registration Request with an Establishment Cause indicating a priority service (e.g. MCX, MPS) or when the AMF determines that there is a priority subscription (e.g. MPS, MCX) in the UDM, the AMF may accept the registration request without applying NSAC, i.e. the AMF triggers the NSAC procedure, but the response from the NSACF is ignored at the AMF. When the SMF receives a PDU Session Establishment Request for an emergency PDU Session or a PDU Session Establishment Request with a priority header, the SMF may accept the PDU Session Establishment Request without applying NSAC, i.e. the SMF triggers the NSAC procedure, but the response from the NSACF is ignored at the SMF. Alternatively, when NSAC is exempted for the UE and/or PDU Session, the AMF and the SMF skip the corresponding NSAC procedure, i.e. this UE (respectively PDU Session) is not counted towards the maximum number of UEs (respectively PDU Sessions). The support of NSAC for the S-NSSAI used for onboarding as described in clause 5.30.2.10 is optional and subject to Onboarding Network operator policies. However, NSAC for S-NSSAI used for onboarding is not applicable to UEs that registered in ON-SNPN with Registration Type "SNPN Onboarding". In the case of NSAC for maximum number of PDU Sessions, when the NSACF rejects the request from the SMF to increase the number of PDU Sessions, the SMF may provide to the UE a back-off timer associated with reject cause set to 'Maximum number of PDU Sessions per S-NSSAI reached' for an Access Type as described in clause 4.2.11.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the UE receives from the SMF a back-off timer associated with the reject cause set to 'Maximum number of PDU Sessions per S-NSSAI reached' for an Access Type, the UE shall not request the establishment of a PDU Session for this S-NSSAI on the indicated Access Type until the back-off timer expires. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11 |
3,051 | 4.13.2.2 Number of successful WLAN additions to the LWA WLAN mobility set | a) This measurement provides the number of successful WLAN additions to the LWA WLAN mobility set. b) CC c) On receipt of RRCConnectionReconfigurationComplete message by the eNB, corresponding to the transmitted RRCConnectionReconfiguration message which includes the wlan-ToAddList in the lwa-MobilityConfig of lwa-Configuration information element (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]). d) An integer value e) LWI.LwaWlanAddSucc f) WLANMobilitySet g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.13.2.2 |
3,052 | 5.4.5.2.2 UE-initiated NAS transport procedure initiation | In the connected mode, the UE initiates the NAS transport procedure by sending the UL NAS TRANSPORT message to the AMF, as shown in figure 5.4.5.2.2.1. In case a) in subclause 5.4.5.2.1, the UE shall: - include the PDU session information (PDU session ID, old PDU session ID, S-NSSAI, mapped S-NSSAI (if available in roaming scenarios), DNN, request type, alternative S-NSSAI, MA PDU session information), if available; - set the Payload container type IE to "N1 SM information"; and - set the Payload container IE to the 5GSM message. The UE shall set the PDU session ID IE to the PDU session ID. If an old PDU session ID is to be included, the UE shall set the Old PDU session ID IE to the old PDU session ID. If an alternative S-NSSAI is to be included, the UE shall set the Alternative S-NSSAI IE to the alternative S-NSSAI and shall set the S-NSSAI IE to the S-NSSAI to be replaced. If an S-NSSAI is to be included, the UE shall set the S-NSSAI IE to the S-NSSAI selected for the PDU session from the allowed NSSAI for the current PLMN or SNPN, associated with the mapped S-NSSAI (if available in roaming scenarios). If a DNN is to be included, the UE shall set the DNN IE to the DNN. 5GSM procedures specified in clause 6 describe conditions for inclusion of the S-NSSAI, mapped S-NSSAI (if available in roaming scenarios), and the DNN. If a request type is to be included, the UE shall set the Request type IE to the request type. The request type is not provided along 5GSM messages other than the PDU SESSION ESTABLISHMENT REQUEST message and the PDU SESSION MODIFICATION REQUEST message. If an MA PDU session information is to be included, the UE shall set the MA PDU session information IE to the MA PDU session information. The MA PDU session information is not provided along 5GSM messages other than the PDU SESSION ESTABLISHMENT REQUEST message and the PDU SESSION MODIFICATION REQUEST message as specified in 3GPP TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ] [13B]. If the UE supports the non-3GPP access path switching for the PDU session and the AMF has indicated its support for the non-3GPP access path switching, the UE shall include the Non-3GPP access path switching indication information element and set the NAPS bit to "non-3GPP access path switching supported". The non-3GPP access path switching indication is not provided along 5GSM messages other than the PDU SESSION ESTABLISHMENT REQUEST message. In case b) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "SMS"; and - set the Payload container IE to the SMS payload. Based on the UE preferences regarding access selection for mobile originated (MO) transmission of SMS over NAS as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]: - when SMS over NAS is preferred to be sent over 3GPP access: the UE attempts to deliver MO SMS over NAS via the 3GPP access if the UE is registered over both 3GPP access and non-3GPP access. If the delivery of SMS over NAS via the 3GPP access is not available, the UE attempts to deliver MO SMS over NAS via the non-3GPP access; and - when SMS over NAS is preferred to be sent over non-3GPP access: the UE attempts to deliver MO SMS over NAS via the non-3GPP access if the UE is registered over both 3GPP access and non-3GPP access. If the delivery of SMS over NAS via the non-3GPP access is not available, the UE attempts to deliver MO SMS over NAS via the 3GPP access. In case c) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "LTE Positioning Protocol (LPP) message container"; - set the Payload container IE to the LPP message payload; and - set the Additional information IE to the routing information provided by the upper layer location services application. In case c1) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "SLPP message container"; - set the Payload container IE to the SLPP message payload; and - set the Additional information IE to the routing information provided by the upper layer location services application. In case d) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "SOR transparent container"; and - set the Payload container IE to the UE acknowledgement due to successful reception of steering of roaming information, and; i) set the ME support of SOR-CMCI indicator to "SOR-CMCI supported by the ME" ; ii) set the ME support of SOR-SNPN-SI indicator to "SOR-SNPN-SI supported by the ME"; and iii) set the ME support of SOR-SNPN-SI-LS indicator to "SOR-SNPN-SI-LS supported by the ME", - in the Payload container IE carrying the acknowledgement (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]). In case e) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "UE policy container"; and - set the contents of the Payload container IE as specified in Annex D. In case f) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "UE parameters update transparent container"; and - set the contents of the Payload container IE to the UE acknowledgement due to successful reception of UE parameters update data (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]). In case g) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "Location services message container"; - set the Payload container IE to the Location services message payload; - set the Additional information IE to the routing information, if preconfigured or provided by AMF in a previous procedure or provided by the upper layer location services application; and - include the Payload container information IE with the PRU bit set to "Payload container related to PRU" if the location services message payload is related to PRU (see 3GPP TS 24.080[ Mobile radio interface layer 3 supplementary services specification; Formats and coding ] [13A]). NOTE: The AMF may configure the routing information to the UE during the PRU association procedure or the PRU disassociation procedure as specified in 3GPP TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [6B]. For case h), when the UE is located outside the LADN service area, the UE shall not perform the UE-initiated NAS transport procedure to send CIoT user data via the control plane for a PDU session for LADN. In case h) in subclause 5.4.5.2.1, the UE shall: - include the PDU session ID, and Release assistance indication (if available); - set the Payload container type IE to "CIoT user data container"; and - set the Payload container IE to the user data container. In case i) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "Service-level-AA container"; and - set the Payload container IE to the Service-level-AA container. In case j) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "UPP-CMI container"; and - set the Payload container IE to the UPP-CMI container. In case k) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "Multiple payloads"; and - set each payload container entry of the Payload container IE (see subclause 9.11.3.39), as follows: i) set the payload container type field of the payload container entry to a payload container type value set in the Payload container type IE as specified in cases a) to j) above; ii) set the payload container entry contents field of the payload container entry to the payload container contents set in the Payload container IE as specified in cases a) to j) above, and iii) set the optional IE fields, if any, to the optional associated payload routing information as specified in cases a) to j) above. Figure 5.4.5.2.2.1: UE-initiated NAS transport procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.5.2.2 |
3,053 | 10.5.5.32 Extended DRX parameters | The purpose of the Extended DRX parameters information element is to indicate that the MS wants to use eDRX and for the network to indicate the Paging Time Window length value and the extended DRX cycle value to be used for eDRX. The Extended DRX parameters is a type 4 information element with a minimum length of 3 octets and a maximum length of 4 octets. The Extended DRX parameters information element is coded as shown in figure 10.5.5.32/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5.32/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.5.32/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Extended DRX parameters information element Table 10.5.5.32/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Extended DRX parameters information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.32 |
3,054 | 5.2.6.8.2 Nnef_ChargeableParty_Create service operation | Service operation name: Nnef_ChargeableParty Create Description: The consumer requests to become the chargeable party for a data session for a UE. Inputs, Required: AF Identifier, UE address (i.e. IP address or MAC address), Flow description information as described in clause 6.1.3.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] or External Application Identifier, ASP Identifier, Sponsor Information, Sponsoring Status. Inputs, Optional: Time period, traffic volume, Background Data Transfer Reference ID, DNN if available, S-NSSAI if available. Outputs, Required: Transaction Reference ID, result. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.8.2 |
3,055 | 19.4.2.7 Target RNC-ID for U-TRAN | In the special case of a UTRAN target RNC a possible SGSN that can control that RNC can be identified by RNC-ID. This identifier can be used for SRNS relocation with a U-TRAN target RNC. A subdomain name for use by core network nodes based on RNC-ID shall be derived from the MNC and MCC by adding the label "rnc" to the beginning of the Home Network Realm/Domain (see clause 19.2). The RNC FQDN shall be constructed as: rnc<RNC>.rnc.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org <RNC> shall be Hex coded digits representing the RNC-ID code of the RNC. If there are less than 4 significant digits in <RNC>, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. NOTE: Above subdomain is for release 8 core network nodes to allow DNS records other than A/AAAA records. The subdomain name in Annex C.3 are still used for existing A/AAAA records for pre-Release 8 nodes and are still used for backward compatibility. However, RNC-ID in Annex C.3 was originally intended for the case where only one SGSN controlled an RNC-ID and gave the SGSN IP address. The usage for the above RNC FQDN is potentially broader and can target an SGSN pool. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.7 |
3,056 | 5.4.3.3 Paging Priority | Paging Priority is a feature that allows the AMF to include an indication in the Paging Message sent to NG-RAN that the UE be paged with priority. The decision by the AMF whether to include Paging Priority in the Paging Message is based on the ARP value in the message received from the SMF for an IP packet waiting to be delivered in the UPF. If the ARP value is associated with select priority services (e.g. MPS, MCS), the AMF includes Paging Priority in the Paging Message. When the NG-RAN receives a Paging Message with Paging Priority, it handles the page with priority. The AMF while waiting for the UE to respond to a page sent without priority receives another message from the SMF with an ARP associated with select priority services (e.g. MPS, MCS), the AMF sends another Paging message to the (R)AN including the Paging Priority. For subsequent messages, the AMF may determine whether to send the Paging message with higher Paging Priority based on local policy. For a UE in RRC_INACTIVE state, the NG-RAN determines Paging Priority based on the ARP associated with the QoS Flow as provisioned by the operator policy, and the Core Network Assisted RAN paging information from AMF as described in clause 5.4.6.3. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.3.3 |
3,057 | 6.3.5E.3 Aggregate power control tolerance | Aggregate power control tolerance is the ability of a UE to maintain its power in non-contiguous transmission in response to 0 dB TPC commands with respect to the first UE transmission, when the power control parameters specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] are constant. For category M1 and M2 TDD and FD-FDD UEs, the aggregate power control tolerance requirements specified in Table 6.3.5E.3.1-0 apply. For category M1 and M2 HD-FDD UEs and for continuous uplink transmissions of duration β€ 64 ms, the aggregate power control tolerance requirements specified in Table 6.3.5E.3.1-0 apply. For category M1 and M2 HD-FDD UEs and for continuous uplink transmissions of duration > 64 ms, the aggregate power control tolerance requirements specified in Table 6.3.5E.3.1-1 apply. | 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.5E.3 |
3,058 | 6.10.2.1 SN Addition or modification | When the MN is executing the Secondary Node Addition procedure (i.e. initial offload of one or more radio bearers to the SN), or the Secondary Node Modification procedure (as in clauses 10.2.2 and 10.3.2 in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [51]) which requires an update of the KSN, the MN shall derive an KSN as defined in clause 6.10.3.2. The MN shall maintain the SN Counter as defined in Clause 6.10.3.1. In the case of Conditional PSCell Change and conditional PSCell addition as specified in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [51], if there are more than one candidate SNs, for each SN, the MN shall derive a different KSN via using different SN counter as defined in clause 6.10.3.2. When executing the procedure for adding subsequent radio bearer(s) to the same SN, the MN shall, for each new radio bearer, assign a radio bearer identity that has not previously been used since the last KSN change. If the MN cannot allocate an unused radio bearer identity for a new radio bearer in the SN, due to radio bearer identity space exhaustion, the MN shall increment the SN Counter and compute a fresh KSN, and then shall perform a SN Modification procedure to update the KSN. The dual connectivity procedure with activation of encryption/decryption and integrity protection follows the steps outlined on the Figure 6.10.2.1-1. Figure 6.10.2.1-1. Security aspects in SN Addition/Modification procedures (MN initiated) 1. The UE and the MN establish the RRC connection. 2. The MN sends SN Addition/Modification Request to the SN over the Xn-C to negotiate the available resources, configuration, and algorithms at the SN. The MN computes and delivers the KSN to the SN if a new key is needed. The UE security capabilities (see subclause 6.10.4) and the UP security policy received from the SMF shall also be sent to SN. In case of PDU split, UP integrity protection and ciphering activation decision from MN may be also included as described in subclause 6.10.4 When the MN decides to configure CPA or CPC, if there are more than one candidate SNs, for each SN, the MN shall derive a different KSN and delivers the KSN to each SN seperately.. 3. The SN allocates the necessary resources and chooses the ciphering algorithm and integrity algorithm which has the highest priority from its configured list and is also present in the UE security capability. If a new KSN was delivered to the SN then the SN calculates the needed RRC. The UP keys may be derived at the same time when RRC key derived. The SN shall activate the UP security policy as described in subclause 6.10.4. 4. The SN sends SN Addition/Modification Acknowledge to the MN indicating availability of requested resources and the identifiers for the selected algorithm(s) for the requested DRBs and/or SRB for the UE. The UP integrity protection and encryption indications shall be send to the MN. 5. The MN sends the RRC Connection Reconfiguration Request to the UE instructing it to configure the new DRBs and/or SRB for the SN. The MN shall include the SN Counter parameter to indicate a new KSN is needed and the UE shall compute the KSN for the SN. The MN forwards the UE configuration parameters (which contains the algorithm identifier(s) received from the SN in step 4) , and UP integrity protection and encryption indications(received from the SN in step 4) to the UE (see subclause 6.10.3.3 for further details). If an SN sends more than one candidate PScell SCG configuration, the MN signals to the UE that all these configurations are associated with the same SN counter value. NOTE 3: Since the message is sent over the RRC connection between the MN and the UE, it is integrity protected using the KRRCint of the MN. Hence the SN Counter cannot be tampered with. 6. The UE accepts the RRC Connection Reconfiguration Request after validating its integrity. The UE shall compute the KSN for the SN if an SN Counter parameter was included. The UE shall also compute the needed RRC and UP keys and activate the RRC and UP protection as per the indications received for the associated SRB and/or DRBs respectively. The UE sends the RRC Reconfiguration Complete to the MN. The UE activates the chosen encryption/decryption and integrity protection keys with the SN at this point. 7. MN sends SN Reconfiguration Complete to the SN over the Xn-C to inform the SN of the configuration result. On receipt of this message, SN may activate the chosen encryption/decryption and integrity protection with UE. If SN does not activate encryption/decryption and integrity protection with the UE at this stage, SN shall activate encryption/decryption and integrity protection upon receiving the Random Access request from the UE. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.10.2.1 |
3,059 | 5.7.2.4 Failure to deliver ULInformationTransfer message | The UE shall: 1> if AS security is not started and radio link failure occurs before the successful delivery of ULInformationTransfer messages has been confirmed by lower layers; or 1> if PDCP re-establishment or release/addition (e.g due to key refresh upon PCell or PSCell change, or RRC connection re-establishment, or failure of resume procedure initiated for SDT) occurs on an SRB on which ULInformationTransfer messages were submitted for transmission but successful delivery of these messages was not confirmed by lower layers: 2> inform upper layers about the possible failure to deliver the information contained in the concerned ULInformationTransfer messages, unless the messages only include dedicatedInfoF1c. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.2.4 |
3,060 | 9.5.9.7 Extended protocol configuration options | This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the MS and the extended protocol configuration options IE is supported by both the MS and the network end-to-end for the PDN connection (see subclause 6.1.3.7). This IE is also included to indicate the selected Bearer Control Mode to be applied when the extended protocol configuration options IE is supported by both the MS and the network end-to-end for the PDN connection (see subclause 6.1.3.7). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.5.9.7 |
3,061 | 6.10.3 UE-specific reference signals associated with PDSCH | UE-specific reference signals associated with PDSCH - are transmitted on antenna port(s) , , , ,, , , or on the antenna ports indicated in Table 6.3.4.4-1, where is the number of layers used for transmission of the PDSCH; - are present and are a valid reference for PDSCH demodulation only if the PDSCH transmission is associated with the corresponding antenna port according to clause 7.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]; - are transmitted only on the physical resource blocks upon which the corresponding PDSCH is mapped. A UE-specific reference signal associated with PDSCH is not transmitted in resource elements in which one of the physical channels or physical signals other than the UE-specific reference signals defined in 6.1 are transmitted using resource elements with the same index pair regardless of their antenna port . A UE-specific reference signal associated with subslot-PDSCH or slot-PDSCH is only transmitted in physical resource blocks in frequency domain assigned for PDSCH transmission where - the assignment maps to both physical resource blocks of a given PRG (see clause 6.4.2); - in case of subslot-PDSCH, the associated SPDCCH is not mapped to resource elements of a given PRG assigned for PDSCH transmission (see clause 6.4.2).. For frame structure type 3, for PDSCH in a subframe with the same duration as the DwPTS duration of a special subframe configuration, the UE-specific reference signals are defined the same as that for the corresponding special subframe configuration. | 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.10.3 |
3,062 | 5.35.2 5G System enhancements to support IAB | In IAB operation, the IAB-UE interacts with the 5GC using procedures defined for UE. The IAB-node gNB-DU only interacts with the IAB-donor-CU and follows the CU/DU design defined in TS 38.401[ NG-RAN; Architecture description ] [42]. For the IAB-UE operation, the existing UE authentication methods as defined in TS 33.501[ Security architecture and procedures for 5G System ] [29] applies. Both USIM based methods and EAP based methods are allowed, and NAI based SUPIs can be used. The following aspects are enhanced to support the IAB operation in the Registration procedure as defined in clause 4.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]: - The IAB-node provides an IAB-indication to the IAB-donor-CU when the RRC connection is established as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. When the IAB-indication is received, the IAB-donor-CU selects an AMF that supports IAB and includes the IAB-indication in the N2 INITIAL UE MESSAGE as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] so that the AMF can perform IAB authorization; - the UE Subscription data as defined in clause 5.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] is enhanced to include the authorization information for the IAB operation; - Authorization procedure during the UE Registration procedure is enhanced to perform verification of IAB subscription information; - If the IAB operation is not authorized and IAB-UE is not allowed to be registered, the AMF rejects the IAB-UE's registration or de-register the IAB-UE. The AMF initiates UE Context setup/modification procedure by providing IAB authorized indication with the value set to "not authorized" to the NG-RAN, if the IAB-UE is still allowed to be registered; - If the IAB operation is authorized, UE Context setup/modification procedure is enhanced to provide IAB authorized indication with the value set to "authorized" to NG-RAN. After registered to the 5G system, the IAB-node remains in CM-CONNECTED state if the IAB operation is authorized. In the case of radio link failure, the IAB-UE uses existing UE procedure to restore the connection with the network. The IAB-UE uses Deregistration Procedure as defined in clause 4.2.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] to disconnect from the network. In the case of controlled IAB-node release as specified in clause 8.9.10 of TS 38.401[ NG-RAN; Architecture description ] [42] (including the case when authorization state of the IAB-node is changed from authorized to non-authorized), after UE Context Modification message to NG-RAN with authorization indication as not authorized and after a certain period (e.g. based on the expiration of a timer configured on the AMF), the AMF may trigger the IAB-UE Deregistration. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.35.2 |
3,063 | 5.2.5.4.4 Npcf_SMPolicyControl_Delete service operation | Service operation name: Npcf_SMPolicyControl_Delete Description: The NF Service Consumer can request the deletion of the SM Policy Association and of the associated resources. Inputs, Required: SM Policy Association ID. Inputs, Optional: 5G SRVCC indication. Outputs, Required: Success or Failure. Outputs, Optional: None. See clause 4.16.6 for the usage of this service operation. When the PDU session for IMS is released due to PS to CS handover for 5G SRVCC, SMF indicate the 5G SRVCC indication received from AMF to PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.4.4 |
3,064 | 14.4.1.2 Nnssaaf_NSSAA_Authenticate service operation | Service operation name: Nnssaaf_NSSAA_Authenticate Description: NF consumer requires the NSSAAF to relay Network Slice specific authentication messages towards the corresponding AAA-S handling the Network Slice specific authentication for the requested S-NSSAI (see clause 16). Input, Required: 1) In the initial NSSAA requests: EAP ID Response, GPSI, S-NSSAI 2) In subsequent NSSAA requests: EAP message, GPSI, S-NSSAI Input, Optional: None Output, Required: EAP message, GPSI, S-NSSAI Output, Optional: None | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 14.4.1.2 |
3,065 | 9.9.3 Reporting of Precoding Matrix Indicator (PMI) for 4Rx UE | The minimum performance requirements of PMI reporting are defined based on the precoding gain, expressed as the relative increase in throughput when the transmitter is configured according to the UE reports compared to the case when the transmitter is using random precoding, respectively. When the transmitter uses random precoding, for each PDSCH allocation a precoder is randomly generated and applied to the PDSCH. A fixed transport format (FRC) is configured for all requirements. The requirements for transmission mode 9 with 8 TX are specified in terms of the ratio In the definition of Ξ³, for PUSCH 3-1 single PMI is 70% of the maximum throughput obtained at using the precoders configured according to the UE reports, and is the throughput measured at with random precoding . | 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.3 |
3,066 | 6.50.2.3 Other aspects | Subject to HPLMN policy and network control, the 5G system shall be able to collect charging information related to traffic steering and/or switching of a DualSteer deviceβs user data across two 3GPP access networks. NOTE 1: Charging information should be collected for both 3GPP access networks; in case the two 3GPP access networks belong to different PLMNs, or a PLMN and NPN, a proper business/roaming agreement among network operators is assumed. Subject to home network operator policy and network control, the 5G system shall be able to support traffic steering and/or switching of a DualSteer deviceβs user data between a NPN and a PLMN, for one or more a DualSteer devices with a NPN subscription accessing NPN services, to meet specific QoS requirements for each device, assuming non-simultaneous transmission over the two 3GPP access networks. NOTE 2: The above assumes a NPN hosted by a PLMN or offered as a slice of a PLMN, data anchoring in the NPN, and a business/roaming agreement between the PLMN and the NPN operator (if different). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.50.2.3 |
3,067 | 16.3.4.4 PDU Session Setup Handling | When new PDU sessions need to be established, the 5GC requests the NG-RAN to allocate/ resources relative to the relevant PDU sessions by means of the PDU Session Resource Setup procedures over NG-C. One S-NSSAI is added per PDU session to be established, so NG-RAN is enabled to apply policies at PDU session level according to the SLA represented by the network slice, while still being able to apply (for example) differentiated QoS within the slice. NG-RAN confirms the establishment of the resources for a PDU session associated to a certain network slice by responding with the PDU Session Resource Setup Response message over the NG-C interface. Figure 16.3.4.4-1: Network Slice-aware PDU Session Resource Setup | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.3.4.4 |
3,068 | 6.1.2 Need codes and conditions for optional fields | The need for fields to be present in a message or an abstract type, i.e., the ASN.1 fields that are specified as OPTIONAL in the abstract notation (ASN.1), is specified by means of comment text tags attached to the OPTIONAL statement in the abstract syntax. All comment text tags are available for use in the downlink direction for RRC message and in the sidelink for PC5 RRC message. The meaning of each tag is specified in table 6.1.2-1. If conditions are used, a conditional presence table is provided for the message or information element specifying the need of the field for each condition case. The table also specifies whether UE maintains or releases the value in case the field is absent. The conditions clarify what the UE may expect regarding the setting of the message by the network for the RRC message or by the peer UE in the sidelink RRC message. Violation of conditions is regarded as invalid network behaviour when transmitting downlink RRC message or invalid UE behavior when transmitting PC5 RRC message, which the UE is not required to cope with. Hence the general error handling defined in 10.4 does not apply in case a field is absent although it is mandatory according to the CondC or CondM condition. For guidelines on the use of need codes and conditions, see Annex A.6 and A.7. Table 6.1.2-1: Meaning of abbreviations used to specify the need for fields to be present NOTE: In this version of the specification, the condition tags CondC and CondM are not used. Any field with Need M or Need N in system information shall be interpreted as Need R. The need code used within a CondX definition only applies for the case (part of the condition) where it is defined: A condition may have different need codes for different parts of the condition. In particular, the CondX definition may contain the following "otherwise the field is absent" parts: - "Otherwise, the field is absent": The field is not relevant or should not be configured when this part of the condition applies. In particular, the UE behaviour is not defined when the field is configured via another part of the condition and is reconfigured to this part of the condition. A need code is not provided when the transition from another part of the condition to this part of the condition is not supported, when the field clearly is a one-shot or there is no difference whether UE maintains or releases the value (e.g., in case the field is mandatory present according to the other part of the condition). - "Otherwise, the field is absent, Need R": The field is released if absent when this part of the condition applies. This handles UE behaviour in case the field is configured via another part of the condition and this part of the condition applies (which means that network when transmitting downlink RRC message or peer UE transmitting PC5 RRC message can assume UE releases the field if this part of the condition is valid). - "Otherwise, the field is absent, Need M": The UE retains the field if it was already configured when this part of the condition applies. This means the network when transmitting downlink RRC message or the peer UE when transmitting PC5 RRC message cannot release the field, but UE retains the previously configured value. Use of different Need codes in different parts of a condition should be avoided. For downlink RRC message and sidelink PC5 RRC messages, the need codes, conditions and ASN.1 defaults specified for a particular (child) field only apply in case the (parent) field including the particular field is present. Thus, if the parent is absent the UE shall not release the field unless the absence of the parent field implies that. For (parent) fields without need codes in downlink RRC messages or sidelink PC5 RRC message, if the parent field is absent, UE shall follow the need codes of the child fields. Thus, if parent field is absent, the need code of each child field is followed (i.e. Need R child fields are released, Need M child fields are not modified and the actions for Need S child fields depend on the specified conditions of each field). Examples of (parent) fields in downlink RRC messages and sidelink PC5 RRC message without need codes where this rule applies are: - nonCriticalExtension fields at the end of a message using empty SEQUENCE extension mechanism, - groups of non-critical extensions using double brackets (referred to as extension groups), and - non-critical extensions at the end of a message or at the end of a structure, contained in a BIT STRING or OCTET STRING (referred to as parent extension fields). The handling of need codes as specified in the previous is illustrated by means of an example, as shown in the following ASN.1. -- /example/ ASN1START RRCMessage-IEs ::= SEQUENCE { field1 InformationElement1 OPTIONAL, -- Need M field2 InformationElement2 OPTIONAL, -- Need R nonCriticalExtension RRCMessage-v1570-IEs OPTIONAL } RRCMessage-1570-IEs ::= SEQUENCE { field3 InformationElement3 OPTIONAL, -- Need M nonCriticalExtension RRCMessage-v1640-IEs OPTIONAL } RRCMessage-v1640-IEs ::= SEQUENCE { field4 InformationElement4 OPTIONAL, -- Need R nonCriticalExtension SEQUENCE {} OPTIONAL } InformationElement1 ::= SEQUENCE { field10 InformationElement10 OPTIONAL, -- Need N field11 InformationElement11 OPTIONAL, -- Need M field12 InformationElement12 OPTIONAL, -- Need R ..., [[ field13 InformationElement13 OPTIONAL, -- Need R field14 InformationElement14 OPTIONAL -- Need M ]] } InformationElement2 ::= SEQUENCE { field21 InformationElement11 OPTIONAL, -- Need M ... } -- ASN1STOP The handling of need codes as specified in the previous implies that: - if field1 in RRCMessage-IEs is absent, UE does not modify or take action on any child fields configured within field1 (regardless of their need codes); - if field2 in RRCMessage-IEs is absent, UE releases the field2 (and also its child field field21); - if field1 or field2 in RRCMessage-IEs is present, UE retains or releases their child fields according to the child field presence conditions; - if field1 in RRCMessage-IEs is present but the extension group containing field13 and field14 is absent, the UE releases field13 but does not modify field14; - if nonCriticalExtension defined by IE RRCMessage-v1570-IEs is absent, the UE does not modify field3 but releases field4; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.1.2 |
3,069 | .1 Modify Bearer Command | The Modify Bearer Command shall be sent on the S11 interface by the MME to the SGW and on the S5/S8 interface by the SGW to the PGW as part of the HSS Initiated Subscribed QoS Modification procedure, or when the SQCI flag or the PSCI flag is set to the Context Response message. It shall also be sent on the S4 interface by the SGSN to the SGW and on the S5/S8 interface by the SGW to the PGW as part of the HSS Initiated subscribed QoS modification procedure, or when the SQCI flag or the PSCI flag is set to the Context Response message. When deferred reporting of subscription change procedure is homogenously supported by MMEs and SGSNs in the serving network, the MME shall defer sending Modify Bearer Command if the related UE is not reachable by the MME, e.g. when the UE is suspended, when the UE has entered into power saving mode or when the PPF is cleared in the MME, until the UE becomes reachable again as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. NOTE: SGSNs do not defer the reporting of subscription change but need to support reporting the subscription change when receiving the PSCI flag in the Context Response message. It shall also be sent on the S2a/S2b interface by the TWAN/ePDG to the PGW as part of the HSS Initiated Subscribed QoS Modification procedure. Table .1-1: Information Elements in a Modify Bearer Command Table .1-2: Bearer Context within Modify Bearer Command Table 7.2.14-3: Overload Control Information within Modify Bearer Command | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | .1 |
3,070 | 13.6 Anonymous User Identity | The Anonymous User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). A SIP URI for an Anonymous User Identity shall take the form "sip:user@domain". The user part shall be the string "anonymous" and the domain part shall be the string "anonymous.invalid". The full SIP URI for Anonymous User Identity is thus: "sip:[email protected]" For more information on the Anonymous User Identity and when it is used, see 3GPP TS 29.163[ Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks ] [63]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.6 |
3,071 | 8.10.4.2.2 TDD | The parameters specified in Table 8.10.4.2.2-1 are valid for all TDD TM9 localized ePDCCH tests unless otherwise stated. Table 8.10.4.2.2-1: Test Parameters for Localized EPDCCH with TM9 and 4Rx For the parameters specified in Table 8.10.4.2.2-1 the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.10.4.2.2-2. EPDCCH subframe monitoring is configured and the subframe monitoring requirement in EPDCCH restricted subframes is statDTX of 99.9%. The downlink physical setup is in accordance with Annex C.3.2. Table 8.10.4.2.2-2: Minimum performance Localized EPDCCH with TM9 and 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.2.2 |
3,072 | 9.2.9 Timing Advance | In RRC_CONNECTED, the gNB is responsible for maintaining the timing advance to keep the L1 synchronised. Serving cells having UL to which the same timing advance applies and using the same timing reference cell are grouped in a TAG. Each TAG contains at least one serving cell with configured uplink, and the mapping of each serving cell to a TAG is configured by RRC. For the primary TAG the UE uses the PCell as timing reference, except with shared spectrum channel access where an SCell can also be used in certain cases (see clause 7.1, TS 38.133[ NR; Requirements for support of radio resource management ] [13]). In a secondary TAG, the UE may use any of the activated SCells of this TAG as a timing reference cell, but should not change it unless necessary. Timing advance updates are signalled by the gNB to the UE via MAC CE commands. Such commands restart a TAG-specific timer which indicates whether the L1 can be synchronised or not: when the timer is running, the L1 is considered synchronised, otherwise, the L1 is considered non-synchronised (in which case uplink transmission can only take place through MSG1/MSGA). When two TAG IDs are configured for the PCell, both TAGs are regarded as primary TAG. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.9 |
3,073 | 5.15.15.2 UE Configuration of network-controlled Slice Usage Policy | The UE during the Registration procedure may indicate in UE MM Core Network Capability that it supports UE configuration of network-controlled Slice Usage Policy. If so, the AMF determines Slice Usage Policy for one (or more) Network Slice(s) for the UE and configures the UE with this information together with Configured NSSAI to control the usage of this (or these) Network Slice(s). The AMF may be locally configured with network Slice Usage Policy, or receive the policy from the AM-PCF, or per the information received from UDM for AF managed timer values (see clause 5.15.15.3 for more details). The network-controlled Slice Usage Policy is provided to the UE in the Registration Accept or the UE Configuration Update Command and may include: - An indication, for one or more of S-NSSAI(s) of the HPLMN in the Configured NSSAI, whether the UE only registers with the Network Slice with the network when applications in the UE require data transmission in the Network Slice (i.e. the UE can only register the Network Slice only on demand and consider the Network Slice as on demand S-NSSAI). NOTE: All Other Network Slices in the Configured NSSAI are handled by the UE using UE specific policies (e.g. they may be registered irrespective of applications need). - For all on demand S-NSSAI(s) of the HPLMN in the Configured NSSAI, a deregistration inactivity timer that causes the UE to deregister the Network Slice after the last PDU Session associated with the S-NSSAI is released. This deregistration inactivity timer is started at the UE and AMF per access type when the last PDU Session associated with the S-NSSAI is released, or the Network Slice is included in the Allowed NSSAI and no PDU session is established. The deregistration inactivity timer is stopped and reset when the first PDU session is established or the S-NSSAI is removed from the Allowed NSSAI. The AMF and UE may locally remove the S-NSSAI from the Allowed NSSAI when the timer expires. The AMF may also send a UE Configuration Update Command to remove the slice from the Allowed NSSAI. If the UE and network state became misaligned, the UE may, for example, request connectivity in a Network Slice which is no longer allowed. In this case, the AMF shall provide the updated Allowed NSSAI in a UE Configuration Update Command after rejecting the PDU Session establishment. The UE may then re-register with the Network Slice if needed. The UE stores the received Slice Usage Policy with the Configured NSSAI for the serving PLMN and this is kept stored for as long as a Configured NSSAI remains stored for the PLMN. When the Configured NSSAI is updated, the AMF may also provide a new Slice Usage Policy to the UE. The AMF receives deregistration inactivity timer values as described in clause 5.15.15.3. If the slice deregistration inactivity timer value is updated, the AMF provides the updated value to the UE, if the UE supports UE configuration of network-controlled Slice Usage Policy, during the registration procedure (i.e. subsequent registration if there is no ongoing registration). The AMF and the UE, if the update been provided to the UE successfully, use the updated slice deregistration inactivity timer value next time the slice deregistration inactivity timer starts. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.15.2 |
3,074 | 5.1.2.5 UE - PDN GW user plane with 3G access via the S4 interface | NOTE: Please refer to TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2] for the corresponding stack for PMIP based S5/S8. Legend: - GPRS Tunnelling Protocol for the user plane (GTP-U): This protocol tunnels user data between UTRAN and the SGSN, between SGSN and S-GW as well as between the S-GW and the P-GW in the backbone network. GTP shall encapsulate all end user IP packets. - UDP/IP: These are the backbone network protocols used for routing user data and control signalling. - Protocols on the Uu and the Iu interfaces are described in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. - SGSN controls the user plane tunnel establishment and establishes a tunnel between SGSN and S-GW. If Direct Tunnel is established between UTRAN and S-GW, see Figure 5.1.2.4-1. Figure 5.1.2.5-1: User Plane for Iu mode | 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.1.2.5 |
3,075 | 10.2.6A.2 Mapping to resource elements | For an NB-IoT carrier which is configured for NPRS transmission, the reference signal sequence shall be mapped to complex-valued modulation symbols used as reference signal for antenna port in slot according to, for Type 1 NPRS: or for Type 2 NPRS: according to higher layer configuration, where - when the higher layer parameter operationModeInfoNPRS for the configured NB-IoT carrier is set to in-band where is signalled by higher layers nprs-SequenceInfo, and if the higher layer parameter nprs-SequenceInfo indicates is odd, and if the higher layer parameter nprs-SequenceInfo indicates is even. - when the higher layer parameter operationModeInfoNPRS for the configured NB-IoT carrier is set to standalone or guard-band and where . If is not configured by higher layers, . The number of PBCH antenna ports is signalled by higher layers. If higher layer parameter nprsBitmap is not configured, resource elements in OFDM symbols 5 and 6 in each slot shall not be used for transmission of NPRS. If the configured periodicity of Type 1 NPRS is equal to that of Type 2 NPRS, the UE is not expected to be configured with overlapped resource elements between Type 1 NPRS and Type 2 NPRS. Otherwise, a resource element configured for Type 1 NPRS shall not be used for Type 2 NPRS. Figure 10.2.6A.2-1: Mapping of NPRS (operationModeInfoNPRS is set to in-band, nprsBitmap configured) Figure 10.2.6A.2-2: Mapping of NPRS (operationModeInfoNPRS is set to standalone or guard-band, nprsBitmap configured) | 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.6A.2 |
3,076 | 4.11.0a.2a Interaction with PCC for URSP delivery via EPS 4.11.0a.2a.0 General | This clause captures the enhancement to the interaction with PCC to support URSP delivery via EPS. To Support URSP provisioning in EPS, the SMF+PGW-C receives the Indication of URSP Provisioning Support from the UE as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the SMF+PGW-C also supports URSP Provisioning Support in EPS and ePCO, it selects a PCF which also supports URSP Provisioning in EPS to establish the SM Policy Association based on the received Indication of URSP Provisioning Support in EPS PCO and local configuration. The SMF+PGW-C then provides the "Indication of URSP Provisioning Support in EPS" in the ePCO to the UE. When the SMF+PGW-C receives the UE Policy Container ePCO in Bearer Resource Command during UE requested bearer resource modification procedure, it forwards transparently the UE Policy Container to PCF for the PDU Session in the Npcf_SMPolicyControl_Update Request including indication that "UE Policy Container received" PCRT was met. When the PCF for Session Management receives UE Policy Container from PCF for the UE, it forwards the UE Policy Container to SMF+PGW-C in Npcf_SMPolicyControl_UpdateNotify Request. The PCF for the PDU Session retrieves the PCRTs for UE Policy from PCF for the UE and subscribe to the applicable PCRTs in EPC to SMF+PGW-C. When URSP Provisioning is supported in EPS, the PCF for the PDU Session may establish the UE Policy Association with PCF for the UE: - When the first UE Policy Container is received from the UE for an SM Policy association. - During 5GS to EPS mobility with N26 when the SMF+PGW-C notifies the PCF for the PDU Session about a RAT-Type change via Npcf_SMPolicyControl_Update. The PCF for the UE triggers the re-evaluation of applicable URSPs in the cases as described in clause 6.1.2.2.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and determines whether an update of URSP is needed for the UE. The PCF for the UE generates the URSP and sends it to the PCF for the PDU Session in the UE Policy Container via Npcf_UEPolicyControl_UpdateNotify Request. The procedures for the UE Policy association defined in clauses 4.16.11, 4.16.12 and 4.16.13 apply in EPS with the main differences below: - AMF is replaced by the PCF for the PDU Session. - Delivery of UE Policy Containers from the PCF for the UE to the PCF for the PDU Session is done via Npcf_UEPolicyControl service instead of via UE Configuration Update procedure. - Delivery of UE Policy Containers from the SMF+PGW-C to the UE is done via PDN GW initiated bearer modification without QoS update procedure as specified in clause 4.11.0a.2a.10. URSP delivery via EPS is also supported in roaming scenarios, both for a PDN connection established in Home Routed and for a PDN connection established in LBO. NOTE: If the PCF for the PDU Session is the same as the PCF for the UE, the interactions between them are internal to the PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.2a |
3,077 | A.6 Guidelines regarding use of need codes | The following rule provides guidance for determining need codes for optional downlink fields: - if the field needs to be stored by the UE (i.e. maintained) when absent: - use Need M (=Maintain); - else, if the field needs to be released by the UE when absent: - use Need R (=Release); - else, if UE shall take no action when the field is absent (i.e. UE does not even need to maintain any existing value of the field): - use Need N (=None); - else (UE behaviour upon absence does not fit any of the above conditions): - use Need S (=Specified); - specify the UE behaviour upon absence of the field in the procedural text or in the field description table. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.6 |
3,078 | β SIB3 | SIB3 contains neighbouring cell related information relevant only for intra-frequency cell re-selection. The IE includes cells with specific re-selection parameters as well as exclude-listed cells. SIB3 information element -- ASN1START -- TAG-SIB3-START SIB3 ::= SEQUENCE { intraFreqNeighCellList IntraFreqNeighCellList OPTIONAL, -- Need R intraFreqExcludedCellList IntraFreqExcludedCellList OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ intraFreqNeighCellList-v1610 IntraFreqNeighCellList-v1610 OPTIONAL, -- Need R intraFreqAllowedCellList-r16 IntraFreqAllowedCellList-r16 OPTIONAL, -- Cond SharedSpectrum2 intraFreqCAG-CellList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF IntraFreqCAG-CellListPerPLMN-r16 OPTIONAL -- Need R ]], [[ intraFreqNeighHSDN-CellList-r17 IntraFreqNeighHSDN-CellList-r17 OPTIONAL, -- Need R intraFreqNeighCellList-v1710 IntraFreqNeighCellList-v1710 OPTIONAL -- Need R ]], [[ channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]] } IntraFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo IntraFreqNeighCellList-v1610::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo-v1610 IntraFreqNeighCellList-v1710 ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo-v1710 IntraFreqNeighCellInfo ::= SEQUENCE { physCellId PhysCellId, q-OffsetCell Q-OffsetRange, q-RxLevMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R q-RxLevMinOffsetCellSUL INTEGER (1..8) OPTIONAL, -- Need R q-QualMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R ... } IntraFreqNeighCellInfo-v1610 ::= SEQUENCE { ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16 OPTIONAL -- Cond SharedSpectrum2 } IntraFreqNeighCellInfo-v1710 ::= SEQUENCE { ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17 OPTIONAL -- Cond SharedSpectrum2 } IntraFreqExcludedCellList ::= SEQUENCE (SIZE (1..maxCellExcluded)) OF PCI-Range IntraFreqAllowedCellList-r16 ::= SEQUENCE (SIZE (1..maxCellAllowed)) OF PCI-Range IntraFreqCAG-CellListPerPLMN-r16 ::= SEQUENCE { plmn-IdentityIndex-r16 INTEGER (1..maxPLMN), cag-CellList-r16 SEQUENCE (SIZE (1..maxCAG-Cell-r16)) OF PCI-Range } IntraFreqNeighHSDN-CellList-r17 ::= SEQUENCE (SIZE (1..maxCellIntra)) OF PCI-Range -- TAG-SIB3-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
3,079 | 10.5.1.1 Cell identity | The purpose of the Cell Identity information element is to identify a cell within a location area. The Cell Identity information element is coded as shown in figure 10.5.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Cell Identity is a type 3 information element with 3 octets length. Figure 10.5.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Cell Identity information element Table 10.5.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Cell Identity 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.1 |
3,080 | 5.13a Extended Idle mode Discontinuous Reception (DRX) | The extended idle mode DRX value range is described in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. A UE and the core network may negotiate the use of extended idle mode DRX as described in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. The MME includes the extended idle mode DRX cycle length in paging message to assist the eNodeB in paging the UE For extended idle mode DRX cycle length of 5.12s, the network should follow regular paging strategy as defined in clause 5.13 For extended idle mode DRX cycle length of 10.24s or longer, the following applies: If the UE decides to request for extended idle mode DRX, the UE includes an extended idle mode DRX parameters information element in the attach request and/or TAU request message. The UE may also include the UE specific DRX parameters for regular idle mode DRX according to clause 5.13. The extended idle mode DRX parameters information element includes the idle mode DRX length. The MME decides whether to accept or reject the UE request for enabling extended idle mode DRX as described in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. If the MME accepts the extended idle mode DRX, the MME based on operator policies and, if available, the extended idle mode DRX cycle length value in the subscription data from the HSS, may also provide different values of the extended idle mode DRX parameters than what was requested by the UE. The MME taking into account the RAT specific Subscribed Paging Time Window, the UEs current RAT -NB-IOT or WB-E-UTRAN) and local policy also assigns a Paging Time Window length to be used, and provides this value to the UE during Attach/TAU procedures together with the extended idle mode DRX cycle length in extended idle mode DRX parameter. If the MME accepts the use of extended idle mode DRX, the UE shall apply extended idle mode DRX based on the received extended idle mode DRX length, the UEs current RAT -NB-IOT or WB-E-UTRAN) and RAT specific Paging Time Window length. If the UE does not receive the extended idle mode DRX parameters information element in the relevant accept message because the SGSN/MME rejected its request or because the request was received by SGSN/MME not supporting extended idle mode DRX, the UE shall apply its regular discontinuous reception as defined in clause 5.13. NOTE: The extended idle mode DRX cycle length requested by UE takes into account requirements of applications running on the UE. Subscription based determination of eDRX cycle length can be used in those rare scenarios when applications on UE cannot be modified to request appropriate extended idle mode DRX cycle length. The network accepting extended DRX while providing an extended idle mode DRX cycle length value longer than the one requested by the UE, can adversely impact reachability requirements of applications running on the UE. When the UE has bearers for emergency bearer services, the UE and MME follow regular discontinuous reception as defined in clause 5.13 and shall not use the extended idle mode DRX. Extended idle mode DRX parameters may be negotiated while the UE has bearers for emergency bearer services. When the bearers for emergency bearer services are released, the UE and MME shall reuse the negotiated extended idle mode DRX parameters in the last TAU/Attach procedure. When the UE is attached for RLOS services, the UE and the MME follow regular discontinuous reception as defined in clause 5.13 and shall not use the extended idle mode DRX. The UE shall include the extended idle mode DRX parameters information element in each TAU message if it still wants to use extended idle mode DRX. At MME to MME, MME to SGSN and SGSN to MME mobility, the extended idle mode DRX parameters are not sent from the old CN node to the new CN node as part of the MM context information. If extended idle mode DRX is enabled, the MME handles paging as defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. If the MME is requested to monitor Reachability for Data and the UE is about to become reachable for paging, the MME sends a Monitoring Report message to the address that was indicated in the related Monitoring Request as described in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. | 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.13a |
3,081 | 6.7 Carrier Aggregation | In case of CA, the multi-carrier nature of the physical layer is only exposed to the MAC layer for which one HARQ entity is required per serving cell as depicted on Figures 6.7-1 and 6.7-2 below: - In both uplink and downlink, there is one independent hybrid-ARQ entity per serving cell and one transport block is generated per assignment/grant per serving cell in the absence of spatial multiplexing. Each transport block and its potential HARQ retransmissions are mapped to a single serving cell. Figure 6.7-1: Layer 2 Structure for DL with CA configured Figure 6.7-2: Layer 2 Structure for UL with CA configured | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.7 |
3,082 | 5.2.4 Call establishment for SRVCC or vSRVCC 5.2.4.1 General | Before call establishment for SRVCC or vSRVCC can be initiated in the mobile station, the MM connection must be established by the network. At PS to CS domain change from S1 mode or Iu mode due to SRVCC handover or vSRVCC handover (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [126]), the RR sublayer in the MS indicates to the MM layer if a voice only SRVCC handover or a voice and video SRVCC handover was completed successfully. At reception of this indication, the MS that supports SRVCC or vSRVCC shall establish an MM connection as specified in subclause 4.5.1.8 and either proceeds with subclause 5.2.4.2 if the indication is that voice only SRVCC was completed successfully or proceeds with subclause 5.2.4.2a if the indication is that voice and video SRVCC was completed successfully. At 5G-SRVCC handover from NG-RAN to UTRAN (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [126]), the RR sublayer in the MS indicates to the MM layer if 5G-SRVCC handover from NG-RAN to UTRAN was completed successfully. At reception of this indication, the MS that supports 5G-SRVCC handover from NG-RAN to UTRAN shall establish an MM connection as specified in subclause 4.5.1.8 and proceeds with subclause 5.2.4.2 if the indication is that 5G-SRVCC handover from NG-RAN to UTRAN was completed successfully. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.4 |
3,083 | M.1 Mapping of the parameters between 5GS and TSN UNI | Editor's note: The information provided here is a guidance for better understanding of the function. Content of this Annex will be updated to a functional level detail once stage 3 work is stable. The details of the parameters in the TSN UNI are specified in IEEE Std 802.1Q [98] and IEEE P802.1Qdj [146]. Stream identification is further specified in IEEE Std 802.1CB [83] and IEEE Std 802.1CBdb [178]. The SMF/CUC derives the End Station related information for the stream requirements towards the TN CNC for the QoS Flow as follows: a) For the Talker group: β StreamID: can be generated by the SMF/CUC based on the End Station MAC address acting as Talker and a UniqueID. SUPI, PDU Session ID and QFI may be used to derive the UniqueID. The MAC address is either pre-configured at the SMF/CUC or provided by the AN-TL or CN-TL to the SMF/CUC (e.g. as part of the EndStationInterfaces information). - StreamRank: set to zero for ARP priority values 1-8; set to one for other ARP values. β EndStationInterfaces: If the AN-TL and CN-TL are supported, the SMF/CUC receives the EndStationInterfaces (MacAddress, InterfaceName) from the AN-TL and CN-TL via TL-Container. If the AN-TL and CN-TL are not supported the SMF/CUC sets the information based on pre-configuration. - DataFrameSpecification (optional): When it is present it specifies how the TN can identify packets of the TN stream using Ethernet, IP and transport protocol header fields in order to apply the required TSN configuration. The SMF/CUC may derive the DataFrameSpecification based on: - N3 tunnel end point addresses that are used for the QoS Flow. The SMF/CUC may instruct the UPF and NG-RAN to assign a separate N3 tunnel end point address for each QoS Flow that may carry TSC streams so that the TN can distinguish the QoS Flows based on the N3 tunnel destination IP addresses. NOTE 1: IPv6 can be used in the N3 tunnel end point addresses to provide sufficient address space in case separate N3 tunnel end point addresses are used for each QoS flow that can carry time sensitive streams. - Mask-and-match stream identification parameters (IEEE 802.1CBdb [178] clause 9.1.6) (optional). The SMF/CUC may indicate mask-and-match configuration based on the TEID and QFI of the given QoS flow and the destination IP address to the TN CNC, when the deployment supports mask-and-match stream identification function as defined in clause 6.8 in IEEE Std 802.1CBdb [178]. This functionality can be used for example to check for the TEID and QFI in the GTP header and the destination IP address to distinguish the QoS Flows. This enables the TN CNC to configure the mask-and-match stream identification function in the transport network. This is an option that allows to use a single GTP-U tunnel as defined for non-TSN Transport networks. The DataFrameSpecification or mask-and-match stream identification parameters may be provided to the AN-TL and CN-TL to configure stream identification. In that case, the AN-TL and CN-TL can perform the stream identification without relying on additional information from the upper layers of the AN or CN node. When AN-TL and CN-TL are not supported the TN CNC configures the edge bridge to perform the stream transformation based on the provided the DataFrameSpecification or mask-and-match parameters when applicable. β TrafficSpecification elements: β Interval: derived from the Periodicity of the traffic as indicated in the TSCAI. β MaxFramesPerInterval: specifies the maximum number of frames that the Talker transmits in one Interval. β MaxFrameSize: derived from the MDBV of the QoS Flow. If the PCF determines interworking with a TSN network deployed in the transport network is supported based on the DNN/S-NSSAI of the PDU Session, the PCF generates MDBV based on the Burst Size as described in clause 5.27.3 and the PCF transfers the MDBV to the SMF/CUC. The SMF/CUC sets MaxFrameSize based on the following formula: MDBV of the QoS Flow - the framing bits which is not used for transferring in 5GS, (e.g. CRC + the GTP-U tunnel overhead). - TransmissionSelection: specifies the algorithm that the Talker uses to transmit the Stream's traffic class. If no algorithm is known, the value zero (strict priority) is used. β TSpecTimeAware group (optional, present only if the traffic in the QoS Flow is time-synchronized): β EarliestTransmitOffset: the earliest offset within the Interval. For uplink, EarliestTransmitOffset should be set based on the following formula: Packet arrival time at the Talker (UL) - M x Interval, where M is the largest integer for which the relation: Packet arrival time at the Talker (UL) > M x Interval duration. would be true. Packet arrival time at the Talker (UL) should be: TSCAC BAT in UL direction (presented in TAI time and corrected for clock drifting as specified in the present specification) + UE-DS-TT Residence Time. For downlink, EarliestTransmitOffset should be set based on the following formula: Packet arrival time at the Talker (DL) - M x Interval, where M is the largest integer for which the relation: Packet arrival time at the Talker (DL) > M x Interval duration. would be true. Packet arrival time at the Talker (DL) should be TSCAC BAT in DL direction (presented in TAI time and corrected for clock drifting as specified in the present specification). β LatestTransmitOffset: the last chance within an interval should leave enough time to transfer a packet with MaxFrameSize. Derived from the end of the interval, the time to transfer a packet with MaxFrameSize. The LatestTransmitOffset shall be set to the Buffer Capability when the value of LatestTransmitOffset subtracted by the packet arrival time at the Talker (either UL or DL respectively as described in EarliestTransmitOffset) exceeds the Buffer capability. The value of LatestTransmitOffset shall be larger or equal than EarliestTransmitOffset. β Jitter: derived in SMF/CUC based on local information on Jitter in AN-TL and CN-TL and respective stream and traffic interference. Annex U, clauses U.1.1, U.1.2, and U.1.3 of IEEE Std 802.1Q [98] provide some examples. β UserToNetworkRequirements: β NumSeamlessTrees: set to one (no redundancy) or other value (if redundancy is required). β MaxLatency: set to CN PDB subtracted by maximum possible buffer duration in Talker. Maximum possible buffer duration is set to LatestTransmitOffset subtracted by EarliestTransmitOffset. - InterfaceCapabilities (optional): If the AN-TL and CN-TL are supported, the SMF/CUC collects InterfaceCapabilities from AN-TL and CN-TL via TL-Container. If the AN-TL and CN-TL are not supported, the SMF/CUC leaves the InterfaceCapabilities empty. b) For the Listener group: - Stream ID and Stream Rank: that were generated for the Talker of the TN stream are also used by the SMF/CUC for the Listener. - EndStationInterfaces: derived as with the corresponding information for the Talker group. - UserToNetworkRequirements: β NumSeamlessTrees: set to one. β MaxLatency: derived as with the corresponding information for the Talker group. - InterfaceCapabilities: derived as with the corresponding information for the Talker group. c) For the Status group: The Status group contains the end station communication-configuration provided by TN CNC to the SMF/CUC: β Stream ID. β StatusInfo. β AccumulatedLatency: If the AccumulatedLatency is included from TN CNC to SMF/CUC for a stream in DL direction, the SMF/CUC may use the AccumulatedLatency to update the TSCAI BAT to the NG-RAN; the SMF sets the TSCAI Burst Arrival Time in downlink direction as the sum of the TSCAC BAT value in downlink direction and AccumulatedLatency and the buffer duration in Talker in CN-TL. The buffer duration in CN-TL is zero if TimeAwareOffset for the Talker group is not present, and TimeAwareOffset - EarliestTransmitOffset if the TimeAwareOffset is present for the Talker group. β InterfaceConfiguration (optional): β MAC Address (optional, present only if the respective InterfaceCapability contains a value for Active Destination MAC and VLAN Stream identification in CB-StreamIdenTypeList, and stream transformation is performed in AN-TL and CN-TL). β VLAN Tag (optional, present only if the respective InterfaceCapability contains that it is VlanTagCapable and a value for Active Destination MAC and VLAN Stream identification in CB-StreamIdenTypeList, and the stream transformation is performed in AN-TL and CN-TL). β IPv4/IPv6 Tuples (optional, but not supported in this release of the specification). β TimeAwareOffset (optional, present only if the traffic is time-synchronized, AN-TL and CN-TL is supported, and TSpecTimeAware elements were provided in the stream requirements). If the InterfaceConfiguration is included and if the AL-TL/CN-TL acting as Talker End Station support the Stream Transformation as described in IEEE Std 802.1Q [98], the SMF/CUC can instruct the UPF and NG-RAN to assign an individual TSN Transport address by providing the InterfaceConfiguration to the AN-TL/CN-TL via TL-Container. The Talker in AN-TL/CN-TL shall use the indicated InterfaceConfiguration, e.g. source MAC address, multicast destination MAC address, VLAN ID, as assigned by the TN CNC for the data stream in a QoS Flow. The TN can identify the streams based on the Stream Transformation that is applied in the AN-TL/CN-TL acting as Taker End Station. This allows to use a single GTP-U tunnel as defined for non-TSN Transport networks. If the TimeAwareOffset is included from TN CNC to SMF/CUC, the SMF/CUC should send the TimeAwareOffset to the AN-TL (for streams in UL direction) or the CN-TL port (for streams in the DL direction). The AL-TL/CN-TL derive Gate Control information (i.e. AdminBaseTime, AdminCycleTime, AdminControlListLength, and AdminControlList) based on the TimeAwareOffset as defined in IEEE Std 802.1Q [98] at the AN-TL (for streams in UL direction) and the CN-TL port (for streams in the DL direction). The AN-TL or CN-TL acting as Talker buffers the data burst until the time indicated in the TimeAwareOffset is reached. If the SMF/CUC receives a TimeAwareOffset from TN CNC for a downlink stream (i.e. for a Talker in the UPF/CN-TL), the SMF/CUC adds the received TimeAwareOffset value to the TSCAI BAT in the DL direction in the TSCAI and updates the NG-RAN for the new TSCAI. β FailedInterfaces (optional) provides a list of one or more physical ports of failed end stations or bridges to locate the interfaces in the physical topology that caused the failure. It is up to implementation how the SMF reacts when it receives FailedInterfaces. NOTE 2: It is assumed that the end station communication-configuration will contain at least the same information as defined for the status. NOTE 3: If Jitter value needs to be considered, EarliestTransmitOffset for UL and DL and LatestTransmitOffset shall be Jitter corrected. How Jitter correction is carried out is up to implementation. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | M.1 |
3,084 | 5.2.6.11.6 Nnef_ServiceParameter_Notify operation | Service operation name: Nnef_ServiceParameter_Notify Description: This service operation is used by the NEF to notify a Service Parameter Authorisation Update (e.g. to revoke an authorization) to AF, see clause clause 4.15.6.7a or to forward a notification for a subscribed event by the AF, see clause 4.15.6.7, e.g. the notification of outcome of UE Policies Delivery to AF. Inputs, Required: Transaction Reference ID, Target UE (i.e. GPSI) or External Group Id, Result. The Transaction Reference ID identifies the AF request for service specific parameter provisioning that the notification (i.e. notification of an authorization update or reporting a subscribed event) is related to. The GPSI is the identifier of the UE for which the notification is related to. Inputs, Optional: DNN, S-NSSAI, PLMN ID(s) of inbound roamers, Event Information (defined on a per Event ID basis, for UE Policies delivery outcome it may include the result of the UE Policies delivery procedure and for unsuccessful results, an identifier of the reason), authorization update information (e.g. authorization revocation cause). The Event ID may be the UE Policies delivery outcome defined in clause 4.15.6.7. The GPSI is the identifier of the UE for which the event report is related to. The NEF provides, in addition to the SUPI and if available GPSI(s), the External-Group-Id if provided as Target UE in the Nnef_ServiceParameter_Subscribe operation. Outputs, Required: None. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.11.6 |
3,085 | 4.4.8.2 Architecture to support IEEE Time Sensitive Networking | The 5G System is integrated with the external network as a TSN bridge. This "logical" TSN bridge (see Figure 4.4.8.2-1) includes TSN Translator functionality for interoperation between TSN Systems and 5G System both for user plane and control plane. 5GS TSN translator functionality consists of Device-side TSN translator (DS-TT) and Network-side TSN translator (NW-TT). The TSN AF is part of 5GC and provides the control plane translator functionality for the integration of the 5GS with a TSN network, e.g. the interactions with the CNC. 5G System specific procedures in 5GC and RAN, wireless communication links, etc. remain hidden from the TSN network. To achieve such transparency to the TSN network and the 5GS to appear as any other TSN Bridge, the 5GS provides TSN ingress and egress ports via DS-TT and NW-TT. DS-TT and NW-TT optionally support: - hold and forward functionality for the purpose of de-jittering; - per-stream filtering and policing as defined in clause 8.6.5.2.1 of IEEE Std 802.1Q [98]. DS-TT optionally supports link layer connectivity discovery and reporting as defined in IEEE Std 802.1AB [97] for discovery of Ethernet devices attached to DS-TT. NW-TT supports link layer connectivity discovery and reporting as defined in IEEE Std 802.1AB [97] for discovery of Ethernet devices attached to NW-TT. If a DS-TT does not support link layer connectivity discovery and reporting, then NW-TT performs link layer connectivity discovery and reporting as defined in IEEE Std 802.1AB [97] for discovery of Ethernet devices attached to DS-TT on behalf of DS-TT. NOTE 1: If NW-TT performs link layer connectivity discovery and reporting on behalf of DS-TT, it is assumed that LLDP frames are transmitted between NW-TT and UE on the QoS Flow with the default QoS rule as defined in the clause 5.7.1.1. Alternatively, SMF can establish a dedicated QoS Flow matching on the Ethertype defined for LLDP (IEEE Std 802.1AB [97]). There are three TSN configuration models defined in IEEE Std 802.1Q [98]. Amongst the three models: - fully centralized model is supported in this Release of the specification; - fully distributed model is not supported in this Release of the specification; - centralized network/distributed user model is not supported in this Release of the specification. NOTE 2: This Release supports interworking with TSN using clause 8.6.8.4 of IEEE Std 802.1Q [98] scheduled traffic and clause 8.6.5.2.1 of IEEE Std 802.1Q [98] per-stream filtering and policy. Figure 4.4.8.2-1: System architecture view with 5GS appearing as TSN bridge NOTE 3: Whether DS-TT and UE are combined or are separate is up to implementation. NOTE 4: TSN AF does not need to support N33 in this release of the specification. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.8.2 |
3,086 | 5.16 MME-initiated procedure on UE's CSG membership change | If the UE is in ECM-CONNECTED state and connected via a CSG cell and the MME detects that the UE's CSG membership to that cell has expired, the MME shall send an S1AP UE CONTEXT MODIFICATION REQUEST message to the eNodeB which includes an indication that the CSG membership of the UE has expired. The eNodeB receiving this indication may initiate a handover to another cell. If the UE is not handed over the eNodeB should initiate the S1 release procedure with an appropriate cause. The MME initiates S1 release after a configurable time if the UE is not handed over or released by the CSG cell. If the CSG membership expires for a UE with ongoing emergency bearer service, no indication that the CSG membership of the UE has expired is sent to the eNodeB and the MME shall deactivate all non-emergency PDN connections. If the UE is in ECM-CONNECTED state and connected via a hybrid cell and the MME detects that the UE's CSG membership to that cell has changed or expired, and the CSG Information Reporting Action indicates User CSG Information shall be reported to the P-GW then the MME shall modify the last known CSG membership and send a Change Notification message to the Serving GW with User CSG Information to indicate the CSG membership change. The Serving GW shall send the Change Notification message with the User CSG Information to the PDN GW. The MME shall also send the S1AP UE CONTEXT MODIFICATION REQUEST message to the eNodeB which includes an indication of whether the UE is a CSG member. Based on this information the eNodeB may perform differentiated treatment for CSG and non-CSG members. MME shall release the impacted LIPA PDN connection if the LIPA CSG authorization data for this CSG cell is no longer valid due to UE's CSG membership changed or expired. | 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.16 |
3,087 | 8.3.1.2A Enhanced Performance Requirement Type C - Dual-Layer Spatial Multiplexing | The requirements are specified in Table 8.3.1.2A-2, with the addition of the parameters in Table 8.3.1.2A-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of this test is to verify rank two performance for full RB allocation upon antenna ports 7 and 8. Table 8.3.1.2A-1: Test Parameters for Testing CDM-multiplexed DM RS (dual layer) with multiple CSI-RS configurations Table 8.3.1.2A-2: Enhanced Performance Requirement Type C for CDM-multiplexed DM RS (FRC) with multiple CSI-RS configurations | 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.3.1.2A |
3,088 | 7 Receiver characteristics 7.1 General | Unless otherwise stated the receiver characteristics are specified at the antenna connector(s) of the UE. For UE(s) with an integral antenna only, a reference antenna(s) with a gain of 0 dBi is assumed for each antenna port(s). UE with an integral antenna(s) may be taken into account by converting these power levels into field strength requirements, assuming a 0 dBi gain antenna. . For UEs with more than one receiver antenna connector, identical interfering signals shall be applied to each receiver antenna port if more than one of these is used (diversity). The levels of the test signal applied to each of the antenna connectors shall be as defined in the respective sections below. With the exception of subclause 7.3, the requirements shall be verified with the network signalling value NS_01 configured (Table 6.2.4-1). All the parameters in clause 7 are defined using the UL reference measurement channels specified in Annexes A.2.2 and A.2.3, the DL reference measurement channels specified in Annex A.3.2 and using the set-up specified in Annex C.3.1. For the additional requirements for intra-band non-contiguous carrier aggregation of two or more sub-blocks, an in-gap test refers to the case when the interfering signal is located at a negative offset with respect to the assigned lowest channel frequency of the highest sub-block and located at a positive offset with respect to the assigned highest channel frequency of the lowest sub-block. For the additional requirements for intra-band non-contiguous carrier aggregation of two or more sub-blocks, an out-of-gap test refers to the case when the interfering signal(s) is (are) located at a positive offset with respect to the assigned channel frequency of the highest carrier frequency, or located at a negative offset with respect to the assigned channel frequency of the lowest carrier frequency. For the additional requirements for intra-band non-contiguous carrier aggregation of two or more sub-blocks with channel bandwidth larger than or equal to 5 MHz, the existing adjacent channel selectivity requirements, in-band blocking requirements (for each case), and narrow band blocking requirements apply for in-gap tests only if the corresponding interferer frequency offsets with respect to the two measured carriers satisfy the following condition in relation to the sub-block gap size Wgap for at least one of these carriers j = 1,2, so that the interferer frequency position does not change the nature of the core requirement tested: Wgap β₯ 2β|FInterferer (offset),j| β BWChannel(j) where FInterferer (offset),j for a sub-block with a single component carrier is the interferer frequency offset with respect to carrier j as specified in subclause 7.5.1, subclause 7.6.1 and subclause 7.6.3 for the respective requirement and BWChannel(j) the channel bandwidth of carrier j. FInterferer (offset),j for a sub-block with two or more contiguous component carriers is the interference frequency offset with respect to the carrier adjacent to the gap is specified in subclause 7.5.1A, 7.6.1A and 7.6.3A. The interferer frequency offsets for adjacent channel selectivity, each in-band blocking case and narrow- band blocking shall be tested separately with a single in-gap interferer at a time. For a ProSe UE that supports both ProSe Direct Discovery and ProSe Direct Communication, the receiver characteristics specified in clause 7 for ProSe Direct Communication shall apply. For ProSe Direct Discovery and ProSe Direct Communication on E-UTRA ProSe operating bands that correspond to TDD E-UTRA operating bands as specified in subclause 5.5D, the only additional requirement for ProSe specified in subcaluse 7.4.1D is applicable. | 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 | 7 |
3,089 | 9.11.2.10 Service-level-AA container | The purpose of the Service-level-AA container information element is to transfer upper layer information for authentication and authorization between the UE and the network. The Service-level-AA container information element is coded as shown in figure 9.11.2.10.1, figure 9.11.2.10.2, figure 9.11.2.10.3, figure 9.11.2.10.4 and table 9.11.2.10.1. The Service-level-AA container information element is a type 6 information element with a minimum length of 6 octets and a maximum length of 65538 octets. Figure 9.11.2.10.1: Service-level-AA container information element Figure 9.11.2.10.2: Service-level-AA container contents Figure 9.11.2.10.3: Service-level-AA parameter (when the type of service-level-AA parameter field contains an IEI of a type 4 information element as specified in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]) Figure 9.11.2.10.4: Service-level-AA parameter (when the type of service-level-AA parameter field contains an IEI of a type 6 information element as specified in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]) Figure 9.11.2.10.5: Service-level-AA parameter (when Service-level-AA payload type and its associated Service-level-AA payload are included in the Service-level-AA container contents) Figure 9.11.2.10.6: Service-level-AA parameter (when the type of service-level-AA parameter field contains an IEI of a type 1 information element as specified in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]) Table 9.11.2.10.1: Service-level-AA container information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.2.10 |
3,090 | 6.4.3 Cipher key and integrity key lifetime | Authentication and key agreement, which generates cipher/integrity keys, is not mandatory at call set-up, and there is therefore the possibility of unlimited and malicious re-use of compromised keys. A mechanism is needed to ensure that a particular cipher/integrity key set is not used for an unlimited period of time, to avoid attacks using compromised keys. The UE shall therefore contain a mechanism to limit the amount of data that is protected by an access link key set. For this purpose, a value called THRESHOLD is set by the operator, stored in the USIM and read out by the ME upon power on. Each time an RRC connection is released the values STARTCS and STARTPS of the bearers that were protected in that RRC connection are compared with THRESHOLD. If STARTCS and/or STARTPS are greater than or equal to THRESHOLD, the ME sets the START value in the ME for the corresponding core network domain(s) to zero, deletes the cipher key and the integrity key stored on the USIM and the ME and sets the KSI to invalid (refer to section 6.4.4). Otherwise, the STARTCS and STARTPS are stored in the ME. The ME shall write back the values of STARTCS and/or STARTPS to the USIM only when the UE is about to power off in a controlled manner and there are valid UTRAN keys for that domain. When the UE has powered on and before attempting to connect to any network, the ME reads the START values from the USIM and stores them in the volatile memory of ME. If STARTCS and/or STARTPS read from the USIM are greater than or equal to THRESHOLD or the KSI on the USIM is invalid, the ME sets the START value in the ME for the corresponding core network domain(s) to zero. The ME then marks the START values in the USIM as invalid by setting STARTCS and STARTPS to THRESHOLD. In addition for the former case, the ME deletes the cipher key and the integrity key stored on the USIM and sets the KSI to invalid (refer to section 6.4.4). When an RRC connection is established the ME uses the START values from the volatile memory of the ME. The ME shall trigger the generation of a new access link key set (a cipher key and an integrity key) for a core network domain if either the START value for that domain in the ME is greater than or equal to THRESHOLD or if there are no valid keys in the ME nor in the USIM for that domain. In addition for the former case, the ME deletes the cipher key and the integrity key stored on the USIM, sets the KSI to invalid (refer to section 6.4.4) and sets the corresponding START value(s) in the ME to zero. This mechanism will ensure that a cipher/integrity key set cannot be reused beyond the limit set by the operator. When the user is attached to a UTRAN, a R99+ ME with a SIM inserted shall use a default value for maximum value of STARTCS or STARTPS as described in section 6.8.2.4. This maximum value of STARTCS or STARTPS corresponds to THRESHOLD as described in the present clause. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.3 |
3,091 | 5.2a Maintenance of UL Synchronization | If upper layer informs that the UL synchronization is lost according to the clause 5.3.18 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], the MAC entity shall: - flush all HARQ buffers; - not perform any uplink transmission. If upper layer informs that the UL synchronization is restored for the SpCell according to the clause 5.3.18 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], uplink transmissions can be performed. NOTE: The MAC entity suspends all UL operations (e.g. stop RACH, SR, and UL HARQ operation) after receiving the indication of an uplink synchronization loss and resumes the operation when receiving an indication of uplink synchronization. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.2a |
3,092 | 5.1.2.3 UE - PDN GW user plane with 2G access via the S4 interface | Legend: - GPRS Tunnelling Protocol for the user plane (GTP-U): This protocol tunnels user data between SGSN and the S-GW as well as between the S-GW and the P-GW in the backbone network. GTP shall encapsulate all end user IP packets. - UDP/IP: These are the backbone network protocols used for routing user data and control signalling. - Protocols on the Um and the Gb interfaces are described in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. Figure 5.1.2.3-1: User Plane for A/Gb mode | 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.1.2.3 |
3,093 | 5.8.10.2.5 Sidelink measurement object addition/modification | The UE shall: 1> for each sl-MeasObjectId included in the received sl-MeasObjectToAddModList: 2> if an entry with the matching sl-MeasObjectId exists in the sl-MeasObjectList within the VarMeasConfigSL, for this entry: 3> for each sl-MeasId associated with this sl-MeasObjectId included in the sl-MeasIdList within the VarMeasConfigSL, if any: 4> remove the measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included; 4> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId; 3> reconfigure the entry with the value received for this sl-MeasObject; 2> else: 3> add a new entry for the received sl-MeasObject to the sl-MeasObjectList within VarMeasConfigSL. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.2.5 |
3,094 | 17.3.1 Home network domain name | The home network domain name shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network domain name consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. The UE shall derive the home network domain name from the IMSI as described in the following steps: 1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27], 3GPP TS 51.011[ Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface ] [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; 2. use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" domain name; 3. add the label "gan." to the beginning of the domain name. An example of a home network domain name is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999, Which gives the home network domain name: gan.mnc015.mcc234.pub.3gppnetwork.org. NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 17.3.1 |
3,095 | 6.4.4.3 EPS bearer context deactivation accepted by the UE | Upon receipt of the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE shall delete the EPS bearer context identified by the EPS bearer identity. After deactivating the identified EPS bearer context, the UE shall respond to the MME with the DEACTIVATE EPS BEARER CONTEXT ACCEPT. If the EPS bearer identity indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST is that of the default bearer to a PDN, the UE shall delete all EPS bearer contexts associated to the PDN. After deactivating all EPS bearer contexts, the UE shall respond to the MME with the DEACTIVATE EPS BEARER CONTEXT ACCEPT. Upon sending the DEACTIVATE EPS BEARER CONTEXT ACCEPT message, the UE shall enter the state BEARER CONTEXT INACTIVE. If due to the EPS bearer context deactivation only the PDN connection for emergency bearer services remains established, the UE shall consider itself attached for emergency bearer services only. If the DEACTIVATE EPS BEARER CONTEXT REQUEST includes ESM cause #39 "reactivation requested" and the EPS bearer context is a default EPS bearer context, and the UE provided an APN for the establishment of the PDN connection, the UE shall stop timer T3396 if it is running for the APN provided by the UE. The UE should then re-initiate the UE requested PDN connectivity procedure for the same APN as the deactivated default EPS bearer context to reactivate the EPS bearer context. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop the timer T3396 associated with no APN if it is running, and should re-initiate the UE requested PDN connectivity procedure without including an APN. Additionally, the UE should re-initiate the request(s) for dedicated bearer resources that have been activated on request of the UE and released as a result of this EPS bearer context deactivation procedure. If the DEACTIVATE EPS BEARER CONTEXT REQUEST message was received for an emergency PDN connection, the UE shall not stop the timer T3396 associated with no APN if it is running. The UE should then re-initiate the UE requested PDN connectivity procedure for the emergency PDN connection. NOTE 1: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer context(s) automatically. NOTE 2: The UE behaviour is not specified for the case where the DEACTIVATE EPS BEARER CONTEXT REQUEST includes ESM cause #39 "reactivation requested" and the deactivated EPS bearer context was a dedicated EPS bearer context. If the DEACTIVATE EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]), the UE uses the PTI to identify the UE requested bearer resource modification procedure or UE requested PDN disconnect procedure to which the EPS bearer context deactivation is related (see clause 6.5.4). If the DEACTIVATE EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]), the UE shall release the traffic flow aggregate description associated to the PTI value provided. If the ESM cause value is #26 "insufficient resources", the network may include a value for timer T3396 in the DEACTIVATE EPS BEARER CONTEXT REQUEST message. The UE shall take different actions depending on the timer value received for timer T3396 (if the UE is configured for dual priority, exceptions are specified in clause 6.5.5; if the UE is a UE configured to use AC11 β 15 in selected PLMN, exceptions are specified in clause 6.3.5): i) if the timer value indicates neither zero nor deactivated, the UE shall stop timer T3396 associated with the corresponding APN, if it is running. The UE shall start timer T3396 with received value and not send another PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST with exception of those identified in clause 6.5.4.1, or BEARER RESOURCE ALLOCATION REQUEST message for the same APN until timer T3396 expires or the timer T3396 is stopped. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop timer T3396 associated with no APN, if it is running. The UE shall start timer T3396 with the received value and not send another PDN CONNECTIVITY REQUEST message without an APN and with request type different from "emergency" and from "handover of emergency bearer services", or another BEARER RESOURCE MODIFICATION REQUEST with exception of those identified in clause 6.5.4.1, or BEARER RESOURCE ALLOCATION REQUEST message for a non-emergency PDN connection established without an APN provided by the UE, until timer T3396 expires or timer T3396 is stopped. The UE shall not stop timer T3396 upon a PLMN change or inter-system change; ii) if the timer value indicates that this timer is deactivated, the UE shall not send another PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST with exception of those identified in clause 6.5.4.1, or BEARER RESOURCE ALLOCATION REQUEST message for the same APN until the UE is switched off or the USIM is removed, or the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST, ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST message for the same APN from the network or a DEACTIVATE EPS BEARER CONTEXT REQUEST message including ESM cause #39 "reactivation requested" for a default EPS bearer context for the same APN from the network. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall not send another PDN CONNECTIVITY REQUEST message without an APN and with request type different from "emergency" and from "handover of emergency bearer services", or another BEARER RESOURCE MODIFICATION REQUEST with exception of those identified in clause 6.5.4.1, or BEARER RESOURCE ALLOCATION REQUEST message for a non-emergency PDN connection established without APN provided by the UE , until the UE is switched off or the USIM is removed, or the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST, ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST message for a non-emergency PDN connection established without an APN provided by the UE, or a DEACTIVATE EPS BEARER CONTEXT REQUEST message including ESM cause #39 "reactivation requested" for a default EPS bearer context of a non-emergency PDN connection established without an APN provided by the UE. The timer T3396 remains deactivated upon a PLMN change or inter-system change; and iii) if the timer value indicates zero, the UE: - shall stop timer T3396 associated with the corresponding APN, if running, and may send another PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message for the same APN; and - if the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop timer T3396 associated with no APN, if running, and may send another PDN CONNECTIVITY REQUEST message without an APN, or another BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message for a non-emergency PDN connection established without an APN provided by the UE. If the timer T3396 is running when the UE enters state EMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE remains the same, then timer T3396 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3396 is running, the UE shall behave as follows when the UE is switched on and the USIM in the UE remains the same: - let t1 be the time remaining for T3396 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 β t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1; - if prior to switch off, timer T3396 was running for a specific APN, because a PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with timer T3396, and if timer T3396 is restarted at switch on, then the UE configured for dual priority shall handle session management requests as indicated in clause 6.5.5; and - if prior to switch off timer T3396 was running because a PDN CONNECTIVITY REQUEST without APN sent together with an ATTACH REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with timer T3396, and if timer T3396 is restarted at switch on, then the UE configured for dual priority shall handle session management requests as indicated in clause 6.5.5. If the T3396 IE is not included, the UE shall proceed with deactivation procedure and then send DEACTIVATE EPS BEARER CONTEXT ACCEPT message. Upon receipt of the DEACTIVATE EPS BEARER CONTEXT ACCEPT message, the MME shall enter the state BEARER CONTEXT INACTIVE and stop the timer T3495. | 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.3 |
3,096 | 8.75 User CSG Information (UCI) | User CSG Information (UCI) is coded as depicted in Figure 8.75-1. The CSG ID is defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. Figure 8.75-1: User CSG Information For two digits in the MNC, bits 5 to 8 of octet 6 are coded as "1111". The CSG ID consists of 4 octets. Bit 3 of Octet 8 is the most significant bit and bit 1 of Octet 11 is the least significant bit. The coding of the CSG ID is the responsibility of the operator that allocates the CSG ID by administrative means. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. Access mode values are specified in Table 8.75-1. Table 8.75-1: Access mode values and their meanings Leave CSG flag (LCSG) shall be set to "1" if UE leaves CSG cell/Hybrid cell, and in this case, the receiving node shall ignore the rest information in the IE. CSG Membership Indication (CMI) values are specified in Table 8.75-2. CMI shall be included in the User CSG Information if the Access mode is Hybrid Mode. For the other values of Access Mode, the CMI shall be set to 0 by the sender and ignored by the receiver. Table 8.75-2: CSG Membership indication (CMI) NOTE: Due to a specification oversight, the CMI values in the above table are reversed from the values of the CMI IE (see clause 8.79). Furthermore, the encoding is different between GTPv1 and GTPv2. | 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.75 |
3,097 | 5.2.2.3.3 ATTEMPTING-REGISTRATION | The UE in 3GPP access: a) shall initiate an initial registration procedure on the expiry of timers T3502, T3511 or T3346; b) may initiate an initial registration procedure for emergency services even if timers T3502, T3511 or T3346 are running; b1) may initiate an initial registration procedure even if timer T3502, T3346 or T3447 is running, if the UE is a UE configured for high priority access in selected PLMN; b2) may initiate an initial registration procedure even if timer T3502, T3346 is running, if the UE is a UE configured for high priority access in selected SNPN; c) shall initiate an initial registration procedure when entering a new PLMN or SNPN, except i) if timer T3346 is running and the new PLMN or SNPN is equivalent to the PLMN or SNPN where the UE started timer T3346; ii) if the PLMN identity of the new cell is in the forbidden PLMN lists; iii) if the SNPN is not an SNPN selected for localized services in SNPN (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), the SNPN identity of the new cell is in the "permanently forbidden SNPNs" list or the "temporarily forbidden SNPNs" list which are, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription; iv) if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), the SNPN identity of the new cell is in the "permanently forbidden SNPNs for access for localized services in SNPN" list or the "temporarily forbidden SNPNs for access for localized services in SNPN" list, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription; or v) if the current TAI is in one of the lists of 5GS forbidden tracking areas; d) shall initiate an initial registration procedure when the current TAI has changed, if timer T3346 is not running, the PLMN identity of the new cell is not in one of the forbidden PLMN lists or the SNPN identity of the new cell is in neither the "permanently forbidden SNPNs" list nor the "temporarily forbidden SNPNs" list which are, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, and the current TAI is not in one of the lists of 5GS forbidden tracking areas; e) shall initiate an initial registration procedure if the 5GS update status is set to 5U2 NOT UPDATED, and timers T3511, T3502 and T3346 are not running; f) may initiate an initial registration procedure for UE in NB-N1 mode upon receiving a request from upper layers to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]) or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]) if timer T3346 is not already running for "MO exception data" and even if timer T3502 or timer T3511 is running; and g) may initiate an initial registration procedure with 5GS registration type IE set to "initial registration" for initiating of an emergency PDU session, upon request of the upper layers to establish the emergency PDU session. The UE in non-3GPP access: a) shall initiate an initial registration procedure on the expiry of timers T3502, T3511 or T3346; b) may initiate an initial registration procedure for emergency services even if timers T3502, T3511 or T3346 are running; b1) may initiate an initial registration procedure even if timer T3502 or T3346 is running if the UE is a UE configured for high priority access in selected PLMN; c) shall initiate an initial registration procedure when entering a new PLMN or SNPN, except if timer T3346 is running and the new PLMN or SNPN is equivalent to the PLMN or SNPN where the UE started timer T3346; d) shall initiate an initial registration procedure if the 5GS update status is set to 5U2 NOT UPDATED, and timers T3511, T3502 and T3346 are not running; and e) may initiate an initial registration procedure with 5GS registration type IE set to "initial registration" for initiating of an emergency PDU session, upon request of the upper layers to establish the emergency PDU session. | 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.2.2.3.3 |
3,098 | 6.6.4 Mapping to resource elements | The block of complex-valued symbols for each antenna port shall - for an MBMS-dedicated cell, be transmitted during 4 consecutive radio frames fulfilling , starting in each radio frame fulfilling , and - otherwise, be transmitted during 4 consecutive radio frames, starting in each radio frame fulfilling . The block of complex-valued symbols shall be mapped in sequence starting with to resource elements constituting the core set of PBCH 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 in slot 1 in subframe 0 and finally the radio frame number. The resource-element indices are given by where resource elements reserved for reference signals shall be excluded. The mapping operation shall assume cell-specific reference signals for antenna ports 0-3 being present irrespective of the actual configuration. The UE shall assume that the resource elements assumed to be reserved for reference signals in the mapping operation above but not used for transmission of reference signal are not available for PDSCH or MPDCCH transmission. The UE shall not make any other assumptions about these resource elements. For an MBMS-dedicated cell configured with repetition, the physical broadcast channel shall be repeated as described in clause 6.6.4.1. If a cell is configured with repetition of the physical broadcast channel - symbols mapped to core resource element in slot 1 in subframe 0 within a radio frame according to the mapping operation above, and - cell-specific reference signals in OFDM symbols in slot 1 in subframe 0 within a radio frame with according to the mapping operation above shall additionally be mapped to resource elements in slot number within radio frame unless resource element is used by CSI reference signals. For frame structure type 1, , , and are given by Table 6.6.4-1. For frame structure type 2, - if , and are given by Table 6.6.4-2 and ; - if , and are given by Table 6.6.4-2 and , except that repetitions with and are not applied. For both frame structure type 1 and frame structure type 2, repetition of the physical broadcast channel is not applicable if . Resource elements already reserved or used for transmission of cell-specific reference signals in absence of repetition shall not be used for additional mapping of cell-specific reference signals. Table 6.6.4-1: Frame offset, slot and symbol number triplets for repetition of PBCH for frame structure type 1. Table 6.6.4-2: Slot and symbol number pairs for repetition of PBCH for frame structure type 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 | 6.6.4 |
3,099 | Annex L (normative): Support of GERAN/UTRAN access | This annex applies when the SMF+PGW-C is enhanced to support UE accessing the network via GERAN/UTRAN over Gn/Gp interface. For this scenario, the SMF+PGW-C uses N7 interface to interact with PCF and the N40 interface to interact with CHF. NOTE 1: For the interface with the serving node of the UE, the SMF+PGW-C is assumed to behave as the Control Plane of the PGW described in Annex D of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. SMF+PGW-C selection by SGSN is specified in Annex G of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The SMF+PGW-C interacting with PCF for GERAN/UTRAN access is specified in Annex G of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The functional description for SMF+PGW-C interacting with PCF to support GERAN/UTRAN access is specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE 2: Support for IP address preservation upon mobility between 5GS and GERAN/UTRAN for PDN sessions established in EPC is described in clause 5.17.2.4. IP address preservation is not supported for direct mobility between 5GS and GERAN/UTRAN, nor for indirect mobility cases when the PDN session is established in 5GS or in GERAN/UTRAN. The charging services on SMF+PGW-C interactions with CHF for GERAN/UTRAN access are specified in TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [68]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
3,100 | 8.10.1.2.10 Closed loop spatial multiplexing performance - Single-Layer Spatial Multiplexing 2 Tx Antenna Port with CRS assistance information (Cell-Specific Reference Symbols) | The requirements are specified in Table 8.10.1.2.10-2, with the addition of parameters in Table 8.10.1.2.10-1. In Table 8.10.1.2.10-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the closed loop single layer TM4 performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.10.1.2.10-1: Test Parameters Table 8.10.1.2.10-2: Minimum Performance for PDSCH | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.2.10 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.