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
⌀ |
|---|---|---|---|---|---|---|---|
5,601 | 19.4.2.6 Serving GPRS Support Node (SGSN) within SGSN pool | A specific SGSN within an operator's network is identified using the RAI FQDN (clause 19.4.2.5) and the Network Resource Identifier (NRI) (see 3GPP TS 23.236[ Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ] [23]). Such an identifier can be used by a target MME or SGSN node to connect to the source SGSN node. The SGSN FQDN shall be constructed as: nri-sgsn<NRI>.rac<RAC>.lac<LAC>.rac.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org <NRI> shall be Hex coded digits representing the NRI code of the SGSN. If there are less than 4 significant digits in < NRI>, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. Coding for other fields is the same as in Clause 19.4.2.5. When a target MME constructs the FQDN of the source SGSN in the case of SGSN pooling, it should derive the NRI from the 8-bit MME Code received in the GUTI from the UE. However, if the length of the NRI, e.g., X, which is configured in the MME is less than 8 bits, then the MME should use only the most significant X bits of the MME Code as the NRI within the SGSN FQDN. 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.2 are still used for existing A/AAAA records for pre-Release 8 nodes and are also still used for backward compatibility. . | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.6 |
5,602 | Annex E (informative): Guidelines for enhancements to MS network capability IE and UE network capability IE | The UE uses the information elements MS network capability and UE network capability to inform the core network about its network related capabilities. Both information elements can be signalled in any of the modes: A/Gb mode, Iu mode and S1 mode. The purpose of the present annex is to give some guidelines how to select the information element(s) to be enhanced if new capabilities need to be added. 1) If a capability is related to a feature that can be used in a network supporting A/Gb mode only or Iu mode only or both, the capability will be signalled in the MS network capability IE. 2) If a capability is related to a feature that can be used in network supporting S1 mode only, the capability will be signalled in the UE network capability IE. 3) If a capability is related to a feature that can be used only in a network supporting both S1 mode and at least one of the two modes A/Gb mode and Iu mode, the capability is added only to one of the two information elements: a) If the information is used by the MME only, the capability will be signalled in the UE network capability IE. b) If the information is used by the SGSN only or both by the SGSN and by the MME, the capability will be signalled in the MS network capability IE. NOTE: The reason for rules 1 and 2 is that a UE not supporting A/Gb mode and Iu mode will not provide the MS network capability IE to the network and a UE not supporting S1 mode will not provide the UE network capability IE. In some cases, due to rules 1 and 2 the capability indicator will be included in both information elements. EXAMPLE 1: The support indicator for UCS2 is included in both information elements. EXAMPLE 2: The "SRVCC to GERAN/UTRAN capability" is included in the MS network capability IE, as it is used both by the MME for SRVCC from E-UTRAN to GERAN/UTRAN and by the SGSN for SRVCC from UTRAN HSPA to GERAN/UTRAN. | 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 | Annex |
5,603 | 4.15.6.13.2 Procedures for Creating a Multi-member AF session with required QoS | Figure 4.15.6.13.2-1: Procedures for creating a Multi-member AF session with required QoS 1. The AF sends a request to reserve resources for the traffic flows for the communication between a set of UEs and an AF, using Nnef_AFsessionWithQoS_Create request message (a list of UE addresses, AF Identifier, Flow description information or External Application Identifier, QoS Reference or individual QoS parameters, Alternative Service Requirements (as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), QoS parameter(s) to be measured, Reporting frequency, Target of reporting, optional an indication of local event notification, DNN, S-NSSAI) to the NEF. The Flow description information, if provided, is common for the list of UEs identified by the list of UE addresses. - The AF may, instead of a QoS Reference, provide one or more of the following individual QoS parameters: Requested 5GS Delay (optional), Requested Priority (optional), Requested Guaranteed Bitrate, Requested Maximum Bitrate, Maximum Burst Size and Requested Packet Error Rate. The optional Alternative Service Requirements provided by the AF shall either contain QoS References or Requested Alternative QoS Parameter Set(s) in a prioritized order as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The AF may provide QoS parameter(s) to be measured as defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Reporting frequency, Target of reporting, optional an indication of local event notification as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The AF may also provide the Consolidated Data Rate threshold and optionally, a list of UE addresses subject to Consolidated Data Rate monitoring. If so, the AF shall also subscribe to QoS Monitoring of UL and/or DL data rate described in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] . NOTE 1: When the Consolidated Data Rate threshold is provided, it, by default, applies to the list of UE addresses associated with the Multi-member AF session with required QoS. However, if the specific list of UE addresses subject to Consolidated Data Rate monitoring is also provided together with the Consolidate Data Rate threshold, then such list has to be the subset of the list of UE addresses. 2. The NEF authorizes the AF request that contains a list of UE addresses and may apply policies to control the overall amount of QoS authorized for the AF. If the authorisation is not granted, all steps (except step 8) are skipped and the NEF replies to the AF with a Result value indicating that the authorisation failed. The NEF assigns a Transaction Reference ID to the Nnef_AFsessionWithQoS_Create request. The NEF activates Consolidated Data Rate monitoring only when both the Consolidated Data Rate threshold and a request to do QoS Monitoring of data rate are provided by the AF. 2a. If the NEF recognizes, based on configuration, that the IP address(es) received in the list of UE addresses are different from the IP address(es) assigned by 5GC (i.e. the UE(s) are behind a NAT in UPFs), the NEF performs steps 3 to 6 of the AF specific UE ID retrieval procedure defined in clause 4.15.10 for each UE IP address with port number in order to identify the corresponding IP address (and IP domain, if necessary) that has been assigned by the 5GC. The NEF then uses the respective corresponding IP address (and IP domain, if necessary) in the following steps instead of the UE IP address provided by the AF. 3-4. The NEF finds BSF serving the UE IP address(es) using NRF and then for each UE IP address, the NEF uses Nbsf_Management_Discovery service operation, providing the UE IP address, to discover the responsible PCF for each of the PDU Sessions. Steps 5-7 apply for each UE address in the list of UE addresses. 5. The NEF provides the UE address and the received parameters in step 1 to the PCF in the Npcf_PolicyAuthorization_Create request. If the request contains QoS monitoring information without an indication of direct event notification, the NEF shall include that indication in the request to ensure that QoS Monitoring reports shall be sent by the UPF directly to the NEF. 6. Step 4 in Figure 4.15.6.6-1 applies. The PCF generates authorized QoS Monitoring policy according to the QoS Monitoring information if received from the NEF in step 5 and provides PCC rules with the policy to the SMF as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The SMF configures the UPF to perform QoS Monitoring as described in clause 5.8.2.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 7. The PCF sends the Npcf_PolicyAuthorization_Create response message to the NEF. 8. The NEF aggregates the authorization responses from the PCFs and sends a Nnef_AFsessionWithQoS_Create response message (Transaction Reference ID, Result for list of UE addresses) with the aggregated authorization responses to the AF. Result for list of UE addresses includes whether the authorization was successful or has failed for every UE address in the list. The NEF stores the list of UE addresses for which the authorization was successful together with the Transaction Reference ID, the QoS and the QoS monitoring information. Steps 9-10 apply for each UE address in the list of UE addresses. 9. Step 6 in Figure 4.15.6.6-1 applies. 10. Step 7 in Figure 4.15.6.6-1 applies. 11. The NEF aggregates the notifications from the PCFs and sends a Nnef_AFsessionWithQoS_Notify message (Transaction Reference ID, Result for list of UE addresses) with the aggregated resource allocation status events to the AF. Result for list of UE addresses includes, for every UE address in the list, the information whether resources are allocated, resources are not allocated or resources are allocated while the currently fulfilled QoS matches an Alternative Service Requirement. The NEF updates the locally stored list of UE addresses by removing any UEs for which resources could not be allocated. NOTE 2: For those UE address(es) that did not get any resources, the AF may request resource reservation again, by adding them to the list of UE address(es) as described in clause 4.15.6.13.3. 12. As direct event notification is requested based on the parameters received in step 5, the QoS Monitoring events are reported by the UPF(s) to the NEF using Nupf_EventExposure service as described in clause 5.2.26.2. 13. When the NEF receives QoS Monitoring events, the NEF sends Nnef_AFsessionWithQoS_Notify message with the individual or aggregated QoS Monitoring events to the AF as described for the QoS Monitoring and the Consolidated Data Rate monitoring in clause 4.15.6.13.1. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.13.2 |
5,604 | 5.5.2.3.3 Execution phase | Figure 5.5.2.3.3-1: E-UTRAN to GERAN A/Gb mode Inter RAT HO, execution phase NOTE 1: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Step (B) shows PCRF interaction in the case of PMIP-based S5/S8. Steps 10 and 10a concern GTP based S5/S8 The source eNodeB continues to receive downlink and uplink user plane PDUs. 1. The Source MME completes the preparation phase towards Source eNodeB by sending the message Handover Command (Target to Source Transparent Container (PS Handover Command with RN part and EPC part), E-RABs to Release List, Bearers Subject to Data Forwarding List), S1AP Cause. The "Bearers Subject to Data forwarding list" may be included in the message and it shall be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in the preparation phase (Step 7 of the preparation phase for Direct Forwarding, else parameters received in Step 8a of the preparation phase). S1AP Cause indicates the RAN Cause as received from the target SGSN. Source eNodeB initiate data forwarding for the bearers specified in the "Bearers Subject to Data Forwarding List". The data forwarding may go directly i.e. to target SGSN or alternatively go via the Serving GW if so decided by source MME and/or target SGSN in the preparation phase. 2. The Source eNodeB will give a command to the UE to handover to the Target Access System via the message HO from E-UTRAN Command. This message includes a transparent container including radio aspect parameters that the Target BSS has set-up in the preparation phase (RN part). This message also includes the XID and IOV-UI parameters received from the Target SGSN (EPC part). Upon the reception of the HO from E-UTRAN Command message containing the Handover Command message, the UE shall associate its bearer IDs to the respective PFIs based on the relation with the NSAPI and shall suspend the uplink transmission of the user plane data. 3. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the eNodeB sends the RAN Usage data report message (Secondary RAT usage data) to the MME. Since the handover is an inter-RAT handover, the MME continues with the Secondary RAT usage data reporting procedure as in clause 5.7A.3. The reporting procedure in clause 5.7A.3 is only performed if PGW secondary RAT usage reporting is active. 4. The UE moves to the Target GERAN A/Gb (2G) system and performs executes the handover according to the parameters provided in the message delivered in step 2. The procedure is the same as in step 6 in clause 5.3.2.2 in TS 43.129[ None ] [8] with the additional function of association of the received PFI and existing Bearer Id related to the particular NSAPI. 5. After accessing the cell using access bursts and receiving timing advance information from the BSS in step 4, the UE processes the NAS container and then sends one XID response message to the target SGSN via target BSS. The UE sends this message immediately after receiving the Packet Physical Information message containing the timing advance or, in the synchronised network case, immediately if the PS Handover Access message is not required to be sent. Upon sending the XID Response message, the UE shall resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target cell. For NSAPIs using LLC ADM, for which radio resources were not allocated in the target cell, the UE may request for radio resources using the legacy procedures. If the Target SGSN indicated XID Reset (i.e. reset to default XID parameters) in the NAS container included in the HO from E-UTRAN Command message, and to avoid collision cases the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ADM, but wait for the SGSN to do so (see step 12). In any case the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ABM, but wait for the SGSN to do so (see step 12a). This step is the same as specified in clause 5.3.2.2 in TS 43.129[ None ] [8]. 6. Upon reception of the first correct RLC/MAC block (sent in normal burst format) from the UE to the Target BSS, the Target BSS informs the Target SGSN by sending the message PS Handover Complete (IMSI, and Local TLLI, Request for Inter RAT Handover Info). The target BSS that supports inter-RAT PS handover to UTRAN shall, when the INTER RAT HANDOVER INFO was not included in the Source BSS to Target BSS transparent container received in the PS HANDOVER REQUEST message as specified in TS 48.018[ None ] [42], request the INTER RAT HANDOVER INFO from the target SGSN by setting the 'Request for Inter RAT Handover Info' to '1'. 7. The Target BSS also relays the message XID Response to the Target SGSN. Note, the message in step 6 and 7 may arrive in any order in the Target SGSN. 8. Then the Target SGSN knows that the UE has arrived to the target side and Target SGSN informs the Source MME by sending the Forward Relocation Complete Notification (ISR Activated, Serving GW change) message. If ISR Activated is indicated, the source MME shall maintain the UE's contexts and activate ISR, which is only possible when the S-GW is not changed. The Source MME will also acknowledge that information. A timer in source MME is started to supervise when resources in Source eNodeB and Source Serving GW (for Serving GW relocation) shall be released. Upon receipt of the Forward Relocation Complete Acknowledge message the target SGSN starts a timer if the target SGSN allocated S-GW resources for indirect forwarding. For all bearers that were not included in the Forward Relocation Request message sent in step 3, the MME now releases them by sending a Delete Bearer Command to the SGW, or, the appropriate message to the SCEF. 9. The Target SGSN will now complete the Handover procedure by informing the Serving GW (for Serving GW relocation this will be the Target Serving GW) that the Target SGSN is now responsible for all the EPS Bearer Context(s) the UE has established. This is performed in the message Modify Bearer Request (SGSN Tunnel Endpoint Identifier for Control Plane, NSAPI(s), SGSN Address for Control Plane, SGSN Address(es) and TEID(s) for User Traffic for the accepted EPS bearers and RAT type, ISR Activated) per PDN connection. As it is a mobility from E-UTRAN, if the target SGSN supports location information change reporting, the target SGSN shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If the PDN GW requested User CSG information (determined from the UE context), the SGSN also includes the User CSG Information IE in this message. If the UE Time Zone has changed, the SGSN includes the UE Time Zone IE in this message. If Serving GW is not relocated but the Serving Network has changed or if the SGSN has not received any old Serving Network information from the old MME, the SGSN includes the new Serving Network IE in this message. In network sharing scenarios Serving Network denotes the serving core network. If indicated, ISR Activated indicates that ISR is activated, which is only possible when the S-GW was not changed. When the Modify Bearer Request does not indicate ISR Activated and S-GW is not changed, the S-GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the S-GW reserved. The SGSN releases the non-accepted EPS Bearer contexts by triggering the EPS Bearer context deactivation procedure. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the SGSN. 10. The Serving GW (for Serving GW relocation this will be the Target Serving GW) may inform the PDN GW the change of, for example, for Serving GW relocation or the RAT type, that e.g. can be used for charging, by sending the message Modify Bearer Request per PDN connection. The S-GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if they are present in step 9. Serving Network should be included if it is received in step 9 or in step 4 in clause 5.5.2.3.2. For Serving GW relocation, the Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers and may include the PDN Charging Pause Supported Indication. The PDN GW must acknowledge the request with the message Modify Bearer Response. In the case of Serving GW relocation, the PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function), etc.) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. If location information change reporting is required and supported in the target SGSN, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response. If PCC infrastructure is used, the PDN GW informs the PCRF about the change of, for example, the RAT type. If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path. The source Serving GW shall forward the "end marker" packets to the source eNodeB. 11. The Serving GW (for Serving GW relocation this will be the Target Serving GW) acknowledges the user plane switch to the Target SGSN via the message Modify Bearer Response (Cause, Serving GW Tunnel Endpoint Identifier for Control Plane, Serving GW Address for Control Plane, Protocol Configuration Options, MS Info Change Reporting Action). At this stage the user plane path is established for all EPS Bearer contexts between the UE, Target BSS, Target SGSN, Serving GW (for Serving GW relocation this will be the Target Serving GW) and PDN GW. If the Serving GW does not change, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path. 12. If the Target SGSN indicated XID Reset (i.e. reset to default XID parameters) in the NAS container included in the HO from E-UTRAN Command message, then on receipt of the PS Handover Complete the Target SGSN initiates an LLC/SNDCP XID negotiation for each LLC SAPI used in LLC ADM. In this case if the Target SGSN wants to use the default XID parameters, it shall send an empty XID Command. If the Target SGSN indicated 'Reset to the old XID parameters' in the NAS container, no further XID negotiation is required for LLC SAPIs used in LLC ADM only. 12a. The Target SGSN (re-)establishes LLC ABM for the EPS Bearer contexts which use acknowledged information transfer. During the exchange of SABM and UA the SGSN shall perform LLC/SNDCP XID negotiation. These steps (12 and 12a) are the same as specified in clause 5.3.2.2 in TS 43.129[ None ] [8]. 13. After the UE has finished the reconfiguration procedure the UE shall initiate the Routing Area Update procedure. NOTE 2: The RAU procedure is performed regardless if the UE has this routing area registered or not, as specified by TS 43.129[ None ] [8]. This is needed e.g. to update the START-PS value stored in the 2G-SGSN. The START_PS is delivered to SGSN in INTER RAT HANDOVER INFO parameter of RAU Complete message when requested by SGSN in RAU Accepted. The target SGSN knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target SGSN performs only a subset of the RAU procedure, specifically it excludes the context transfer procedures between source MME and target SGSN. For a UE supporting CIoT EPS Optimisations, the UE uses the bearer status information in the RAU Accept to identify any non-transferred bearers that it shall locally release. 13a. Upon reception of the PS Handover Complete message with the 'Request for Inter RAT Handover Info' set to '1', the SGSN should send then PS Handover Complete Acknowledge (TLLI, INTER RAT HANDOVER INFO) to the target BSS. NOTE 3: An SGSN that does not recognize the "Request for Inter RAT Handover Info" in the PS Handover Complete message will not send the PS Handover Complete Acknowledge message back to the BSS. The target BSS receiving the PS Handover Complete Acknowledge message shall set the 'Reliable INTER RAT HANDOVER' to '1' in the PS Handover Required message in any subsequent PS handover to GERAN A/Gb mode. The target BSS failing to receive the PS Handover Complete Acknowledge message shall set the 'Reliable INTER RAT HANDOVER' to '0' in the PS Handover Required message in any subsequent PS handover to GERAN A/Gb mode. The Target BSS shall, upon receipt of the INTER RAT HANDOVER INFO in the PS Handover Complete Acknowledge message, overwrite its current INTER RAT HANDOVER INFO with this new one. 14. When the timer started at step 8 expires, the source MME sends a Release Resources message to the source eNodeB. The Source eNodeB releases its resources related to the UE. When the timer started in step 8 expires and if the source MME received the Serving GW change indication in the Forward Relocation Response message, it deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication, Secondary RAT usage data) messages to the Source Serving GW. The operation Indication flag is not set, that indicates to the Source Serving GW that the Serving GW changes and the Source Serving GW shall not initiate a delete procedure towards the PDN GW. Secondary RAT usage data is included if it was received in step 3. The Source Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR has been activated before this procedure, the cause indicates to the Source S-GW that the Source S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. 15. If indirect forwarding was used then the expiry of the timer at source MME started at step 8 triggers the source MME to send a Delete Indirect Data Forwarding Tunnel Request message to the S-GW to release the temporary resources used for indirect forwarding. 16. If indirect forwarding was used and the Serving GW is relocated, then the expiry of the timer at target SGSN started at step 8 triggers the target SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the target S-GW to release temporary resources used for indirect forwarding. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.2.3.3 |
5,605 | 10.2.6.2 Mapping to resource elements | Narrowband reference signals are transmitted on one or two antenna ports . If the higher layer indicates UE may assume that is equal to , UE may assume - the number of antenna ports for the cell-specific reference signals as defined in clause 6.10.1 is the same as for the narrowband reference signals, - the antenna ports for cell-specific reference signals {0, 1} are equivalent to antenna ports for narrowband reference signals {2000, 2001}, respectively, and - the cell-specific reference signals are available in all subframes where the narrowband reference signals are available. If the higher layer does not indicate UE may assume that is equal to , UE may assume - the number of antenna port for the cell-specific reference signals as defined in clause 6.10.1 is obtained from the higher layer parameter eutra-NumCRS-Ports, - the cell-specific reference signals are available in all subframes where the narrowband reference signals are available, and the cell-specific frequency shift for cell-specific reference signals as defined in clause 6.10.1.2 is given by . The reference signal sequence shall be mapped to complex-valued modulation symbols used as reference symbols for antenna port in slot according to where When frame structure type 2 is used, the following values of apply for the generation of NRSs in special subframes - in each slot for special subframe configurations {3, 4, 8} - in the first slot for special subframe configurations {9, 10} - in the first slot for special subframe configurations {1, 2, 6, 7}. The variables and define the position in the frequency domain for the different reference signals where is given by The cell-specific frequency shift is given by . Resource elements used for transmission of narrowband reference signals on any of the antenna ports in a slot shall not be used for any transmission on any other antenna port in the same slot and set to zero. Narrowband reference signals shall not be transmitted in subframes containing NPSS or NSSS. For frame structure type 2, narrowband reference signals shall not be transmitted in special subframe for configurations 0 and 5. Figure 10.2.6.2-1 illustrates the resource elements used for reference signal transmission according to the above definition. The notation is used to denote a resource element used for reference signal transmission on antenna port. Figure 10.2.6.2-1. Mapping of downlink narrowband reference signals (normal cyclic prefix) | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.6.2 |
5,606 | 5.17.2.3.3 Mobility for UEs in dual-registration mode | To support mobility in dual-registration mode, the support of N26 interface between AMF in 5GC and MME in EPC is not required. A UE that supports dual registration mode may operate in this mode when it receives an indication from the network that interworking without N26 is supported. For UE operating in dual-registration mode the following principles apply for PDU Session transfer from 5GC to EPC: - UE operating in Dual Registration mode may register in EPC ahead of any PDU Session transfer using the Attach procedure indicating that the UE is moving from 5GC without establishing a PDN Connection in EPC if the EPC supports EPS Attach without PDN Connectivity as defined in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. Support for EPS Attach without PDN Connectivity is mandatory for UE supporting dual-registration procedures. NOTE 1: Before attempting early registration in EPC the UE needs to check whether EPC supports EPS Attach without PDN Connectivity by reading the related SIB in the target cell. - UE performs PDU Session transfer from 5GC to EPC using the UE initiated PDN connection establishment procedure with "handover" indication in the PDN Connection Request message (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 UE has not registered with EPC ahead of the PDU Session transfer, the UE can perform Attach in EPC with "handover" indication in the PDN Connection Request message (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]). - UE may selectively transfer certain PDU Sessions to EPC, while keeping other PDU Sessions in 5GC. - UE may maintain the registration up to date in both 5GC and EPC by re-registering periodically in both systems. If the registration in either 5GC or EPC times out (e.g. upon mobile reachable timer expiry), the corresponding network starts an implicit detach timer. NOTE 2: Whether UE transfers some or all PDU Sessions on the EPC side and whether it maintains the registration up to date in both EPC and 5GC can depend on UE capabilities that are implementation dependent. The information for determining which PDU Sessions are transferred on EPC side and the triggers can be pre-configured in the UE and are not specified in this Release of the specification. The UE does not know before-hand, i.e. before trying to move a given PDU session to EPC, whether that PDU session can be transferred to EPC. NOTE 3: The Start of Unavailability Period and/or Unavailability Period Duration that the UE determines for NR satellite access with discontinuous network coverage in 5GS (see clause 5.4.1.4) and determines for satellite access with discontinuous coverage in EPS (see clause 4.13.8.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]) can be different between 5GS and EPS. For UE operating in dual-registration mode the following principles apply for PDN connection transfer from EPC to 5GC: - UE operating in Dual Registration mode may register in 5GC ahead of any PDN connection transfer using the Registration procedure indicating that the UE is moving from EPC (clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). - UE performs PDN connection transfer from EPC to 5GC using the UE initiated PDU Session Establishment procedure with "Existing PDU Session" indication (clause 4.3.2.2.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). - UE may selectively transfer certain PDN connections to 5GC, while keeping other PDN Connections in EPC. - UE may maintain the registration up to date in both EPC and 5GC by re-registering periodically in both systems. If the registration in either EPC or 5GC times out (e.g. upon mobile reachable timer expiry), the corresponding network starts an implicit detach timer. NOTE 4: Whether UE transfers some or all PDN connections on the 5GC side and whether it maintains the registration up to date in both 5GC and EPC can depend on UE capabilities that are implementation dependent. The information for determining which PDN connections are transferred on 5GC side and the triggers can be pre-configured in the UE and are not specified in this Release of the specification. The UE does not know before-hand, i.e. before trying to move a given PDN connection to 5GC, whether that PDN connection can be transferred to 5GC. NOTE 5: If EPC does not support EPS Attach without PDN Connectivity the MME detaches the UE when the last PDN connection is released by the PGW as described in clause 5.4.4.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26] (in relation to transfer of the last PDN connection to non-3GPP access). When sending a control plane request for MT services (e.g. MT SMS) the network routes it via either the EPC or the 5GC. In absence of UE response, the network should attempt routing the control plane request via the other system. NOTE 6: The choice of the system through which the network attempts to deliver the control plane request first is left to network configuration. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.2.3.3 |
5,607 | 6.4.2.2 Dedicated EPS bearer context activation initiated by the network | In WB-S1 mode, the MME shall initiate the dedicated bearer context activation procedure by sending an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, start the timer T3485, and enter the state BEARER CONTEXT ACTIVE PENDING (see example in figure 6.4.2.2.1). The MME allocates the EPS bearer identity selecting a value as specified by clause 9.3.2, and includes it in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. The MME shall include the EPS bearer identity of the associated default bearer as the linked EPS bearer identity in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. If this procedure was initiated by a UE requested bearer resource allocation procedure or a UE requested bearer resource modification procedure, the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST shall contain the procedure transaction identity (PTI) value received by the MME in the BEARER RESOURCE ALLOCATION REQUEST or BEARER RESOURCE MODIFICATION REQUEST respectively. Figure 6.4.2.2.1: Dedicated EPS bearer context activation procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.2.2 |
5,608 | 13.2.4.5.2a Modifications by Roaming Hub | In case a roaming hub needs to originate an error message, then clause 13.2.4.5.2 shall also apply with the following addition: If an error message needs to be sent, the originating roaming hub shall insert an empty reformattedData IE as defined in TS 29.573[ 5G System; Public Land Mobile Network (PLMN) Interconnection; Stage 3 ] [73], Table 6.2.5.2.2-1 for the Request, and Table 6.2.5.2.3-1 for the response, and the patches shall be based on an empty reformattedData JSON element. Editor's Note: Whether it is an empty reformattedData JSON element or an empty DataToIntegrityProtectBlock that is inserted by the Roaming Hub and that the Roaming Hub bases its patches on is ffs. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4.5.2a |
5,609 | 5.2.2.3.3 Request for on demand system information | The UE shall, while SDT procedure is not ongoing: 1> if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL-MSG1-Repetition and criteria to select supplementary uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met and if criteria to apply MSG1 repetition as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1e for the concerned si-RequestConfigSUL-MSG1-Repetition is met: 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in si-RequestConfigSUL-MSG1-Repetition corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 1> else if the UE is a RedCap UE and if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing si-RequestConfigRedCap-MSG1-Repetition and criteria to select normal uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met and if criteria to apply MSG1 repetition as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1e for the concerned si-RequestConfigRedCap-MSG1-Repetition is met: 2> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in si-RequestConfigRedCap-MSG1-Repetition corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 1> else if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL and criteria to select supplementary uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met: 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfigSUL corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 1> else if the UE is an (e)RedCap UE and if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing si-RequestConfigRedCap and criteria to select normal uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met: 2> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfigRedcap corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 1> else: 2> if the UE is not a RedCap UE and if SIB1 includes si-SchedulingInfo containing si-RequestConfigMSG1-Repetition and criteria to select normal uplink and to apply MSG1 repetition as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1e for the concerned si-RequestConfigMSG1-Repetition are met; or 2> if the UE is a RedCap UE and if initialUplinkBWP-RedCap is not configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing si-RequestConfigMSG1-Repetition and criteria to select normal uplink and to apply MSG1 repetition as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1e for the concerned si-RequestConfigMSG1-Repetition are met: 3> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 3> if acknowledgement for SI request is received from lower layers: 4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 2> else if the UE is neither a RedCap nor an eRedCap UE and if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met; or 2> if the UE is an (e)RedCap UE and if initialUplinkBWP-RedCap is not configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met: 3> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfig corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 3> if acknowledgement for SI request is received from lower layers: 4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 2> else: 3> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1; 3> apply the default MAC Cell Group configuration as specified in 9.2.2; 3> apply the timeAlignmentTimerCommon included in SIB1; 3> apply the CCCH configuration as specified in 9.1.1.2; 3> initiate transmission of the RRCSystemInfoRequest message with rrcSystemInfoRequest in accordance with 5.2.2.3.4; 3> if acknowledgement for RRCSystemInfoRequest message with rrcSystemInfoRequest is received from lower layers: 4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers: 2> reset MAC; 2> if SI request is based on RRCSystemInfoRequest message with rrcSystemInfoRequest: 3> release RLC entity for SRB0. NOTE: After RACH failure for SI request it is up to UE implementation when to retry the SI request. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.3.3 |
5,610 | 6.6.3.3.27 Minimum requirement (network signalled value “NS_31”) | When "NS_31" is indicated in the cell, the power of any UE emission for E-UTRA channels assigned within 5150-5250 MHz, 5250-5350 MHz, 5470-5725 MHz and 5725-5850 MHz shall not exceed the levels specified in Table 6.6.3.3.27-1, Table 6.6.3.3.27-2, Table 6.6.3.3.27-3 and Table 6.6.3.3.27-4, respectively. These requirements also apply for the frequency ranges that are less than FOOB (MHz) in Table 6.6.3.1-1 from the edge of the channel bandwidth. Table 6.6.3.3.27-1: Additional requirements for E-UTRA channels assigned within 5150-5250 MHz Table 6.6.3.3.27-2: Additional requirements for E-UTRA channels assigned within 5250-5350 MHz Table 6.6.3.3.27-3: Additional requirements for E-UTRA channels assigned within 5470-5725 MHz Table 6.6.3.3.27-4: Additional requirements for E-UTRA channels assigned within 5725-5850 MHz | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.3.3.27 |
5,611 | 5.2.27.2.5 Ntsctsf_TimeSynchronization_ConfigUpdateNotify operation | Service operation name: Ntsctsf_TimeSynchronization_ConfigUpdateNotify Description: Forward the notification for the time synchronization configuration. When the TSCTSF detects a change corresponding to a time synchronization configuration, it invokes Ntsctsf_TimeSynchronization_ConfigUpdateNotify service operation to the NF consumer(s) which has subscribed for the event. The following table describes the parameters in the event. Table 5.2.27.2.5-1: Time Synchronization configuration event parameters NOTE: Leader and Follower terms in this specification are aligned with NOTE 2 in clause 5.27.1.2.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Inputs, Required: PTP instance reference, current state of the time synchronization configuration (i.e. whether the time synchronization configuration is active or not for the PTP ports of the PTP instance). Inputs, Optional: Time synchronization information as described in Table 5.2.27.2.5-1. Outputs, Required: Operation execution result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.2.5 |
5,612 | 14.4A Fast Re-authentication NAI | The Fast Re-authentication NAI in both EAP-SIM and EAP-AKA shall take the form of a NAI as specified in clause 2.1 of IETF RFC 4282 [53]. If the 3GPP AAA server does not return a complete NAI, the Fast Re-authentication NAI shall consist of the username part of the fast re-authentication identity as returned from the 3GPP AAA server and the same realm as used in the permanent user identity. If the 3GPP AAA server returns a complete NAI as the re-authentication identity, then this NAI shall be used. The username part of the fast re-authentication identity shall be decorated as described in 14.4 if the Selected PLMN is different from the HPLMN. NOTE: The permanent user identity is either the root or decorated NAI as defined in clauses 14.3 and 14.4. EXAMPLE 1: If the fast re-authentication identity returned by the 3GPP AAA Server is 458405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: [email protected] EXAMPLE 2: If the fast re-authentication identity returned by the 3GPP AAA Server is "[email protected]" and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: [email protected] EXAMPLE 3: If the fast re-authentication identity returned by the 3GPP AAA Server is 458405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, the Fast Re-authentication NAI takes the form: wlan.mnc015.mcc234.3gppnetwork.org [email protected] | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 14.4A |
5,613 | 5.4.7.1 Transmission using PUR | Transmission using PUR is initiated by the RRC layer. When transmission using PUR is initiated, RRC layer provides MAC with the following information: - PUR-RNTI; - Duration of PUR response window pur-ResponseWindowTimer; - UL grant information. If the MAC entity has a PUR-RNTI, the MAC entity shall for each TTI for which RRC layer has provided uplink grant for transmission using PUR: - deliver the uplink grant, and the associated HARQ information to the HARQ entity for this TTI. After transmission using PUR, the MAC entity shall monitor PDCCH identified by PUR-RNTI in the PUR response window using timer pur-ResponseWindowTimer: - if PUR was transmitted in a non-terrestrial network and UE supports delaying the start of the pur-ResponseWindowTimer: - the MAC entity shall start pur-ResponseWindowTimer at the subframe that contains the end of the corresponding PUSCH transmission plus 4 subframes plus UE-eNB RTT. - else: - the MAC entity shall start pur-ResponseWindowTimer at the subframe that contains the end of the corresponding PUSCH transmission plus 4 subframes. While pur-ResponseWindowTimer is running, the MAC entity shall: - if the PDCCH transmission is addressed to the PUR-RNTI and contains an UL grant for a retransmission: - if PUR was transmitted in a non-terrestrial network and UE supports delaying the start of the pur-ResponseWindowTimer: - restart pur-ResponseWindowTimer at the last subframe of a PUSCH transmission corresponding to the retransmission indicated by the UL grant plus 4 subframes plus UE-eNB RTT. - else: - restart pur-ResponseWindowTimer at the last subframe of a PUSCH transmission corresponding to the retransmission indicated by the UL grant plus 4 subframes. - if L1 ACK for transmission using PUR is received from lower layers; or - if PDCCH transmission is addressed to the PUR-RNTI and the MAC PDU is successfully decoded: - stop pur-ResponseWindowTimer; - if L1 ACK for transmission using PUR is received from lower layers or the MAC PDU contains only Timing Advance Command MAC control element: - indicate to upper layers the transmission using PUR was successful; - if repetition adjustment for transmission using PUR is received from lower layers: - indicate the value of the repetition adjustment to upper layers. - discard the PUR-RNTI. - else if fallback indication for PUR is received from lower layers: - stop pur-ResponseWindowTimer; - indicate to upper layers PUR fallback indication is received; - if repetition adjustment for transmission using PUR is received from lower layers: - indicate the value of the repetition adjustment to upper layers. - discard the PUR-RNTI. - if the pur-ResponseWindowTimer expires: - if PUR was transmitted in a non-terrestrial network: - if no notification of a reception of a PDCCH transmission addressed to the PUR-RNTI containing an UL grant for a retransmission was received after the start of pur-ResponseWindowTimer: - indicate to upper layers the transmission using PUR has failed; - discard the PUR-RNTI. - else: - indicate to upper layers the transmission using PUR has failed; - discard the PUR-RNTI. | 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.7.1 |
5,614 | 4.1.1.7 Handling of NAS level mobility management congestion control | The network may detect GMM or MM signalling congestion and perform NAS level mobility management congestion control. PS domain NAS level mobility management congestion control consists of general NAS level mobility management congestion control and subscribed APN based congestion control. CS domain NAS level mobility management congestion control consists of general NAS level mobility management congestion control. Under NAS level mobility management congestion control the network may reject mobility management signalling requests from MSs as specified in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]. The network should not reject requests for emergency bearer services. When subscribed APN based congestion control is active for a particular APN, the network may reject attach request from MSs with subscription to this APN. In mobility management the network may detect NAS signalling congestion. The network may start or stop performing the subscribed APN based congestion control based on mobility management level criteria such as: - rate of mobility management NAS messages from a group of MSs with a subscription to a particular APN exceeds or falls below certain thresholds; or - setting in network management. When the NAS level mobility management congestion control is active, the network may include a value for the mobility management back-off timer T3246 or T3346 in the reject messages. The MS starts the mobility management back-off timer with the value received in the mobility management reject messages. To avoid that large numbers of MSs simultaneously initiate deferred requests, the network should select the value for the mobility management back-off timer for the rejected MSs so that timeouts are not synchronised. For subscribed APN based congestion control the value of timer T3346 for a particular APN may be APN dependent. If the timer T3346 is running when the MS enters state GMM-DEREGISTERED, the MS remains switched on, and the SIM/USIM in the MS remains the same, then timer T3346 is kept running until it expires or it is stopped. If the MS is switched off when the timer T3246 or T3346 is running, the MS shall behave as follows for each running timer when the MS is switched on and the SIM/USIM in the MS remains the same: - let t1 be the time remaining until 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 MS is not capable of determining t, then the MS shall restart the timer with the value t1; and - if prior to switch off, timer T3346 was started due to a NAS request message (ATTACH REQUEST, ROUTING AREA UPDATE REQUEST or SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority", then if timer T3346 is restarted at switch on, the MS configured for low priority shall handle mobility management requests as indicated in subclauses 4.7.3.1.5, 4.7.5.1.5 and 4.7.13.5. If the MS enters a new PLMN while timer T3246 is running, and the new PLMN is not equivalent to the PLMN where the MS started timer T3246, the MS shall stop timer T3246 when initiating mobility management procedures in the new PLMN. If the MS enters a new PLMN while timer T3346 is running, and the new PLMN is not equivalent to the PLMN where the MS started timer T3346, the MS shall stop timer T3346 when initiating mobility management procedures in the new PLMN. At an inter-system change from S1 mode to A/Gb mode or from Iu mode to A/Gb mode within the same RA, if the timer T3346 is running and the TIN indicates "RAT-related TMSI", the MS shall set the GPRS update status to GU2 NOT UPDATED and enter state GMM-REGISTERED.ATTEMPTING-TO-UPDATE. After change in RAI, if the timer T3346 is running and GPRS update status is GU1 UPDATED then MS shall set the GPRS update status to GU2 NOT UPDATED and enter state GMM-REGISTERED.ATTEMPTING-TO-UPDATE. After change in LAI, if the timer T3246 is running and MM update status is U1 UPDATED then MS shall set the MM update status to U2 NOT UPDATED and enter state MM IDLE, ATTEMPTING TO UPDATE. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.1.7 |
5,615 | 5.3.5.3 Uplink timing control | The gNB (including IAB-DU and IAB-donor-DU) determines the desired Timing Advance setting and provides that to the UE (or IAB-MT). The UE/IAB-MT uses the provided TA to determine its uplink transmit timing relative to the UE's/IAB-MTs observed downlink receive timing. An IAB-node may support additional modes for uplink timing: - The IAB-MT uses the provided TA plus a provided additional offset to determine its uplink transmission timing, to facilitate parent node's IAB-MT Rx / IAB-DU Rx multiplexing; - The IAB-MT aligns its uplink transmission timing to that of the collocated IAB-DU downlink transmission timing, to facilitate IAB-MT Tx / IAB-DU Tx multiplexing of this IAB-node. The IAB-node uplink timing mode is indicated by the parent node via MAC-CE. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.3 |
5,616 | 5.6.1 Overview | The 5GC supports a PDU Connectivity Service i.e. a service that provides exchange of PDUs between a UE and a data network identified by a DNN. The PDU Connectivity Service is supported via PDU Sessions that are established upon request from the UE. The Subscription Information for each S-NSSAI may contain a Subscribed DNN list and one default DNN. When the UE does not provide a DNN in a NAS Message containing PDU Session Establishment Request for a given S-NSSAI, the serving AMF determines the DNN for the requested PDU Session by selecting the default DNN for this S-NSSAI if a default DNN is present in the UE's Subscription Information; otherwise the serving AMF selects a locally configured DNN for this S-NSSAI. The expectation is that the URSP in the UE is always up to date using the procedure defined in clause 4.16.12.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and therefore the UE requested DNN will be up to date. In order to cover cases that UE operates using local configuration, but also other cases where operator policies can be used in order to replace an "up to date" UE requested DNN with another DNN used only internally in the network, during UE Registration procedure the PCF may indicate, to the AMF, the operator policies to be used at PDU Session Establishment for DNN replacement of a UE requested DNN. PCF may indicate a policy for DNN replacement of UE requested DNNs not supported by the network, and/or indicate a list of UE requested DNNs per S-NSSAI valid for the serving network, that are subject for replacement (details are described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). If the DNN provided by the UE is not supported by the network and AMF cannot select an SMF by querying NRF, the AMF shall reject the NAS Message containing PDU Session Establishment Request from the UE with a cause indicating that the DNN is not supported unless the PCF provided the policy to perform a DNN replacement of unsupported DNNs. If the DNN requested by the UE is indicated for replacement or the DNN provided by the UE is not supported by the network and the PCF provided the policy to perform DNN replacement of UE requested DNNs not supported by the network, the AMF shall interact with the PCF to perform a DNN replacement. During PDU Session Establishment procedure and as a result of DNN replacement, the PCF provides the selected DNN that is applicable for the S-NSSAI requested by the UE at the PDU Session Establishment. The AMF uses the selected DNN in the query towards the NRF for the SMF selection, as specified in clause 6.3.2, and provides both requested and selected DNN to the selected SMF. For PDU Session with Home-routed Roaming whether to perform DNN replacement is based on operator agreements. NOTE 1: The selected DNN is determined based on operator preferences and can differ from subscribed DNNs. The matching of selected DNN to S-NSSAI is assumed to be based on network configuration. Each PDU Session supports a single PDU Session type i.e. supports the exchange of a single type of PDU requested by the UE at the establishment of the PDU Session. The following PDU Session types are defined: IPv4, IPv6, IPv4v6, Ethernet, Unstructured. PDU Sessions are established (upon UE request), modified (upon UE and 5GC request) and released (upon UE and 5GC request) using NAS SM signalling exchanged over N1 between the UE and the SMF. Upon request from an Application Server, the 5GC is able to trigger a specific application in the UE. When receiving that trigger message, the UE shall pass it to the identified application in the UE. The identified application in the UE may establish a PDU Session to a specific DNN, see clause 4.4.5. SMF may support PDU Sessions for LADN where the access to a DN is only available in a specific LADN service area. This is further defined in clause 5.6.5. SMF may support PDU Sessions for a 5G VN group which offers a virtual data network capable of supporting 5G LAN-type service over the 5G system. This is further defined in clause 5.8.2.13. The SMF is responsible of checking whether the UE requests are compliant with the user subscription. For this purpose, it retrieves and requests to receive update notifications on SMF level subscription data from the UDM. Such data may indicate per DNN and per S-NSSAI of the HPLMN: - The allowed PDU Session Types and the default PDU Session Type. - The allowed SSC modes and the default SSC mode. - QoS Information (refer to clause 5.7): the subscribed Session-AMBR, Default 5QI and Default ARP. - The IP Index information. - The static IP address/prefix. - The subscribed User Plane Security Policy. - the Charging Characteristics to be associated with the PDU Session. Whether this information is provided by the UDM to a SMF in another PLMN (for PDU Sessions in LBO mode) is defined by operator policies in the UDM/UDR. NOTE 2: The content of the Charging Characteristics as well as the usage of the Charging Characteristics by the SMF are defined in TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [68]. A PDU Session may support: (a) a single-access PDU Connectivity Service, in which case the PDU Session is associated with a single access type at a given time, i.e. either 3GPP access or non-3GPP access; or (b) a multi-access PDU Connectivity Service, in which case the PDU Session is simultaneously associated with both 3GPP access and non-3GPP access and simultaneously associated with two independent N3/N9 tunnels between the PSA and RAN/AN. A PDU Session supporting a single-access PDU Connectivity Service is also referred to as single-access PDU Session, while a PDU Session supporting a multi-access PDU Connectivity Service is referred to as Multi-Access PDU (MA PDU) Session and it is used to support the ATSSS feature (see clause 5.32 for details). A UE that is registered over multiple accesses chooses over which access to establish a PDU Session. As defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], the HPLMN may send policies to the UE to guide the UE selection of the access over which to establish a PDU Session. NOTE 3: In this Release of the specification, at any given time, a PDU Session is routed over only a single access network, unless it is an MA PDU Session in which case it can be routed over one 3GPP access network and one Non 3GPP access network concurrently. A UE may request to move a single-access PDU Session between 3GPP and Non 3GPP accesses. The decision to move single-access PDU Sessions between 3GPP access and Non 3GPP access is made on a per PDU Session basis, i.e. the UE may, at a given time, have some PDU Sessions using 3GPP access while other PDU Sessions are using Non 3GPP access. If the UE is attempting to move a single-access PDU session from 3GPP access to non-3GPP access and the PDU session is associated with control plane only indication, then the AMF shall reject the PDU Session Establishment request as related CIoT 5GS optimisation features are not supported over non-3GPP access as described in clause 5.4.5.2.5 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. If the UE is attempting to move a single-access PDU session from non-3GPP access to NB-N1 mode of 3GPP access, the PDU Session Establishment request would also be rejected by AMF when the UP resources for the UE exceed the maximum number of supported UP resources as described in clause 5.4.5.2.4 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. In a PDU Session Establishment Request message sent to the network, the UE shall provide a PDU Session ID. The PDU Session ID is unique per UE and is the identifier used to uniquely identify one of a UE's PDU Sessions. The PDU Session ID shall be stored in the UDM to support handover between 3GPP and non-3GPP access when different PLMNs are used for the two accesses. The UE also provides as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]: (a) PDU Session Type. (b) S-NSSAI of the HPLMN that matches the application (that is triggering the PDU Session Request) within the NSSP in the URSP rules or within the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE 4: If the UE cannot determine any S-NSSAI after performing the association of the application to a PDU Session, then it does not indicate any S-NSSAI in the PDU Session Establishment procedure as defined in clause 5.15.5.3. (c) S-NSSAI of the Serving PLMN from the Allowed NSSAI, corresponding to the S-NSSAI of the HPLMN (b). NOTE 5: In non-roaming scenario the mapping of the Allowed NSSAI to HPLMN S-NSSAIs is not provided to the UE (because the S-NSSAI of the Serving PLMN (c) has the same value of the S-NSSAI of the HPLMN (b)), therefore the UE provides in the PDU Session Request only the S-NSSAI of the Serving PLMN (c). NOTE 6: In roaming scenarios the UE provides in the PDU Session Request both the S-NSSAI of the HPLMN (b) and the S-NSSAI of the VPLMN from the Allowed NSSAI (c) that maps to the S-NSSAI of the HPLMN. (d) DNN (Data Network Name). (e) SSC mode (Service and Session Continuity mode defined in clause 5.6.9.2). Additionally, if the UE supports ATSSS and wants to activate a MA PDU Session, the UE shall provide Request Type as "MA PDU Request" and shall indicate the supported ATSSS capabilities (see clause 5.32 for details). Table 5.6.1-1: Attributes of a PDU Session Subscription Information may include a wildcard DNN per subscribed S-NSSAI: when a wildcard DNN is associated with a subscribed S-NSSAI, the subscription allows, for this S-NSSAI, the UE to establish a PDU Session using any DNN value. NOTE 7: The SMF is made aware whether the DNN of a PDU Session being established corresponds to an explicitly subscribed DNN or corresponds to a wildcard DNN. Thus, the SMF can reject a PDU Session establishment if the DNN of the PDU Session is not part of explicitly subscribed DNN(s) and local policies in the SMF require UE to have a subscription to this DNN. A UE may establish multiple PDU Sessions, to the same data network or to different data networks, via 3GPP and via and Non-3GPP access networks at the same time. A UE may establish multiple PDU Sessions to the same Data Network and served by different UPF terminating N6. A UE with multiple established PDU Sessions may be served by different SMF. The SMF shall be registered and deregistered on a per PDU Session granularity in the UDM. The user plane paths of different PDU Sessions (to the same or to different DNN) belonging to the same UE may be completely disjoint between the AN and the UPF interfacing with the DN. When the SMF cannot control the UPF terminating the N3 interface used by a PDU Session and SSC mode 2/3 procedures are not applied to the PDU Session, an I-SMF is inserted between the SMF and the AMF and handling of PDU Session(s) is described in clause 5.34. NOTE 8: User Plane resources for PDU Sessions of a UE, except for regulatory prioritized service like Emergency Services and MPS, can be deactivated by the SMF if the UE is only reachable for regulatory prioritized services. The SMF serving a PDU session (i.e. Anchor) can be changed during lifetime of the PDU session either within the same SMF set or, if the Context Transfer Procedures as specified in clause 4.26 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] are supported, between SMFs in different SMF sets. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.1 |
5,617 | 6.2.25 MFAF | The Messaging Framework Adaptor Function (MFAF) supports the following functionality: - Interfacing with a DCCF that controls how a messaging framework will process, format and send data to consumers or notification endpoints. - Receiving data from Data Sources via services offered by those Data Sources. - Sending data received from Data Sources to a messaging framework (outside the scope of 3GPP). - Receiving data from a messaging framework (outside the scope of 3GPP). - Processing, formatting and sending data to specified consumers or notification endpoints. NOTE: The internal logic of Messaging Framework is outside the scope of 3GPP, only MFAF and the interface between MFAF and other 3GPP defined NF is under 3GPP scope. The MFAF functionality is specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.25 |
5,618 | 6.5 MBS Session associations in NG-RAN Node | The following MBS Session associations are defined in the NG-RAN node to support NR MBS: NG-RAN MBS session resource context: Encompasses CP and UP, transport and radio resources to support an MBS Session. For multicast it also encompasses the MBS Session state (active, de-activated) and information about joined UEs. If an MBS session resource within a gNB serves multiple MBS service areas, as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [27] the same NG RAN MBS session resource context may be associated with multiple NG-U resources. For a multicast MBS session, NG-U resources are setup or released by the gNB upon UE mobility or UEs leaving or joining the multicast MBS session. MBS Session context in a gNB-DU: The definition of an MBS Session context in a gNB-DU applicable for broadcast and multicast. An MBS Session context in a gNB-DU - is a block of information associated to an MBS Session, which may consist of one or several MRB Contexts; - corresponds to either one or several F1-U tunnels. MRB Context in a gNB-DU: An MRB Context is a block of information in a gNB-DU associated to an MRB (MRB “instance”). The gNB-DU sets up resources for each MRB Context in a gNB-DU associated to an MBS Session context - based on information provided within MBS Session Context related information as received by the gNB-DU (e.g. MRB QoS, MBS service area information, etc.), and, - for multicast, based on the UE Contexts established for RRC_CONNECTED UEs within the gNB-DU containing joining information of the UE for the respective multicast session. - for broadcast, the gNB-DU determines whether F1-U tunnels are setup per gNB-DU or per MBS Area Session ID served by the gNB-DU. - for multicast, the gNB-DU determines whether F1-U tunnels are setup per gNB-DU or per cell served by the DU or per MBS Area Session ID served by the gNB-DU or for ptp restransmissions or for a ptp-only MRB leg. For multicast, for each MRB, the gNB-DU provides the MRB specific Uu configuration to the gNB-CU to configure the UE. Multicast F1-U Context: A Multicast F1-U Context is a block of information in a gNB-DU to control the F1-U tunnels associated to the MRB Contexts established for a multicast MBS session. A Multicast F1-U Context is either established per gNB-DU or per cell served by the gNB-DU or per MBS Area Session ID served by the gNB-DU or for ptp restransmissions or for ptp forwarding or for a ptp-only MRB leg. Several Multicast F1-U contexts may exist in parallel in a gNB-DU for the same multicast MBS session. Allocation and usage of MRB ID values on NG-RAN interfaces for multicast MBS sessions: - F1 interface: an MRB ID signalled on an F1 interface instance identifies uniquely an MRB among all MRB contexts in an gNB-DU, allocated for all active multicast MBS sessions served by that gNB-DU. The value of each MRB ID is the same value as communicated to UEs served by that gNB-DU. - E1 interface: an MRB ID signalled on an E1 interface instance identifies uniquely an MRB among all MRBs allocated for a multicast MBS session. - Xn interface, NG interface: MRB IDs are signalled on Xn/NG interfaces for providing MBS QoS flow to MRB mapping information and data forwarding information from the source gNB. The value of the MRB ID signalled on the Xn/NG interface is the same value as communicated to UEs at the source cell. Allocation and usage of MRB ID values on NG-RAN interfaces for broadcast MBS sessions: - An MRB ID signalled on NG-RAN interfaces identifies uniquely an MRB among all MRBs allocated for a broadcast MBS sesssion. MBS-associated logical F1/E1-connection: F1AP and E1AP provide means to exchange control plane messages associated with an MBS session over the respective F1/E1 interface. An MBS-associated logical connection is established during the first F1AP/E1AP message exchange between the F1/E1 peer nodes. The connection is maintained as long as MBS associated F1AP/E1AP messages need to be exchanged over the F1/E1 interface. The MBS-associated logical F1-connection uses the identities gNB-CU MBS F1AP ID and gNB-DU MBS F1AP ID. The MBS-associated logical E1-connection uses the identities gNB-CU-CP MBS E1AP ID and gNB-CU-UP MBS E1AP ID. When a node (DU or CU or CU-CP and CU-UP) receives an MBS associated F1AP/E1AP message the node retrieves the associated MBS session based on the F1AP/E1AP ID. MBS-associated signalling: MBS-associated signalling is an exchange of F1AP/E1AP messages associated with one MBS session over the MBS-associated logical F1/E1-connection. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 6.5 |
5,619 | 5.20b.3 Support QoS for a group | The procedure as defined in clause 4.15.6.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] is applicable for provisioning of default QoS for a DNN and S-NSSAI for a group of UEs with the following clarifications and enhancements: - The AF request contains the Default QoS for the group, and the UDM stores such QoS in the UDR and uses such QoS to set 5GS Subscribed QoS profile in Session Management Subscription data for each UE within the group. NOTE: When a UE belongs to multiple groups simultaneously, and AF(s) provision different Default QoS for the same DNN and S-NSSAI but different groups, UDM selects a QoS profile among the groups the UE belongs to for a DNN and S-NSSAI to set the 5GS subscribed QoS profile. How the UDM selects a QoS profile is based on implementation and configuration. The UDM can e.g. select a QoS profile with a higher 5QI Priority Level or higher ARP priority level. Mechanisms as defined in clause 5.7.2.7 are used to enforce the 5GS Subscribed QoS profile for a DNN and S-NSSAI for each UE within a group. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.20b.3 |
5,620 | 5.7.3b.4 Actions related to transmission of MCGFailureInformation message | The UE shall set the contents of the MCGFailureInformation message as follows: 1> include and set failureType in accordance with 5.7.3b.3; 1> for each MeasObjectNR configured by a measConfig associated with the MCG, and for which measurement results are available: 2> include an entry in measResultFreqList; 2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to ssb: 3> set ssbFrequency in measResultFreqList to the value indicated by ssbFrequency as included in the MeasObjectNR; 2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to csi-rs: 3> set refFreqCSI-RS in measResultFreqList to the value indicated by refFreqCSI-RS as included in the associated measurement object; 2> if a serving cell is associated with the MeasObjectNR: 3> set measResultServingCell in measResultFreqList to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> set the measResultNeighCellList in measResultFreqList to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows; 3> ordering the cells with sorting as follows: 4> based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS; 4> using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR; 3> for each neighbour cell included: 4> include the optional fields that are available. 1> for each EUTRA frequency the UE is configured to measure by measConfig for which measurement results are available: 2> set the measResultFreqListEUTRA to include the best measured cells, ordered such that the best cell is listed first using RSRP to order the cells if RSRP measurement results are available for cells on this frequency, otherwise using RSRQ to order the cells if RSRQ measurement results are available for cells on this frequency, otherwise using SINR to order the cells, based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available; 1> for each UTRA-FDD frequency the UE is configured to measure by measConfig for which measurement results are available: 2> set the measResultFreqListUTRA-FDD to include the best measured cells, ordered such that the best cell is listed first using RSCP to order the cells if RSCP measurement results are available for cells on this frequency, otherwise using EcN0 to order the cells, based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available; 1> if the UE is in NR-DC: 2> include and set measResultSCG in accordance with 5.7.3.4; 1> if the UE is in NE-DC: 2> include and set measResultSCG-EUTRA in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.6.13.5; NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. NOTE 2: Field measResultSCG-Failure is used to report available results for NR frequencies the UE is configured to measure by SCG RRC signalling. NOTE 3: Field measResultSCG-EUTRA is used to report available results for E-UTRAN frequencies the UE is configured to measure by E-UTRA RRC signalling. 1> if SRB1 is configured as split SRB and pdcp-Duplication is not configured: 2> if the primaryPath for the PDCP entity of SRB1 refers to the MCG: 3> set the primaryPath to refer to the SCG. The UE shall: 1> start timer T316; 1> if SRB1 is configured as split SRB: 2> submit the MCGFailureInformation message to lower layers for transmission via SRB1, upon which the procedure ends; 1> else (i.e. SRB3 configured): 2> submit the MCGFailureInformation message to lower layers for transmission embedded in NR RRC message ULInformationTransferMRDC via SRB3 as specified in 5.7.2a.3. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3b.4 |
5,621 | 8.3.2.4.6 Minimum requirements for QCL Type C and 2 Layers Spatial Multiplexing | The requirements are specified in Table 8.3.2.4.6-3, with the additional parameters in Table 8.3.2.4.6-1 and Table 8.3.2.4.6-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 with non-coherent joint transmission from two transmission points. The test verifies that the UE configured with quasi co-location type C performs correct tracking and compensation of the frequency and time difference between two transmission points, channel parameters estimation, channel estimation and rate matching behaviour according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ signalling defined in [6]. In Table 8.3.2.4.6-1, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals, PBCH and PDSCH, and transmission point 2 (TP 2) has different Cell ID and transmits PDSCH. In the test the PDSCH is transmitted from TP 1 and TP 2. The downlink physical channel setup for TP 1 is according to Annex C.3.2 and for TP 2 according to Annex C.3.2. Table 8.3.2.4.6-1: Test Parameters Table 8.3.2.4.6-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.3.2.4.6-3: Performance Requirements | 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.6 |
5,622 | 10.5.3.2.1 Authentication Response Parameter (extension) (UMTS authentication challenge only) | This IE is included if the authentication response parameter RES is longer than 4 octets (UMTS only) and therefore does not fit in the Authentication Response Parameter field (see 10.5.3.2). The Authentication Response parameter (extension) IE is coded as shown in figure 10.5.76.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.90.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Authentication Response parameter (extension) IE is a type 4 information element with a minimum length of 3 octets and a maximum length of 14 octets. Figure 10.5.76.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Authentication Response Parameter (extension) information element (UMTS authentication challenge only) Table 10.5.90.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Authentication Response Parameter (extension) information element (RES) | 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.2.1 |
5,623 | 13.11 Unknown User Identity | The Unknown User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). A SIP URI for an Unknown User Identity shall take the form "sip:user@domain". The user part shall be the string "unknown" and the domain part shall be the string "unknown.invalid". The full SIP URI for Unknown User Identity is thus: "sip:[email protected]" For more information on the Unknown 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], clauses 7.4.6 and 7.5.4. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.11 |
5,624 | 5.1.1 Physical channels | An uplink physical channel corresponds to a set of resource elements carrying information originating from higher layers and is the interface defined between TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] and the present document TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] . The following uplink physical channels are defined: - Physical Uplink Shared Channel, PUSCH - Physical Uplink Control Channel, PUCCH - Short Physical Uplink Control Channel, SPUCCH - Physical Random Access Channel, PRACH | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.1.1 |
5,625 | G.6 Additional cause codes for GMM | Cause value = 7 GPRS services not allowed This cause is sent to the MS when it is not allowed to operate GPRS services. Cause value = 8 GPRS services and non-GPRS services not allowed This cause is sent to the MS when it is not allowed to operate either GPRS or non-GPRS services. Cause value = 9 MS identity cannot be derived by the network This cause is sent to the MS when the network cannot derive the MS's identity from the P-TMSI/GUTI, e.g. because no matching identity/context can be found in the network. Cause value = 10 Implicitly detached This cause is sent to the MS either if the network has implicitly detached the MS, e.g. some while after the mobile reachable timer has expired, or if the GMM context data related to the subscription dose not exist in the SGSN e.g. because of a SGSN restart, or because of a periodic routing area update request routed to a new SGSN. Cause value = 14 GPRS services not allowed in this PLMN This cause is sent to the MS which requests GPRS service, or if the network initiates a detach request in a PLMN which does not offer roaming for GPRS services to that MS. Cause value = 16 MSC temporarily not reachable This cause is sent to the MS if it requests a combined GPRS attach or routing are updating in a PLMN where the MSC is temporarily not reachable via the GPRS part of the network. Cause value = 28 SMS provided via GPRS in this routing area This cause is sent to the MS if the SGSN decides not to establish a Gs association since the MS is supposed to send and receive short messages via GPRS. Cause value = 40 No PDP context activated This cause is sent to the MS if the MS requests an establishment of the radio access bearers for all active PDP contexts by sending a SERVICE REQUEST message indicating "data" to the network, but the SGSN does not have any active PDP context(s). | 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 | G.6 |
5,626 | 5.1.3 Potential service requirements | The 3GPP system shall enable a UAS to send the following UAV data to a UTM: unique identity (this may be unique 3GPP identity), UE capability of the UAV, make & model, serial number, take-off weight, position, owner identity, owner address, owner contact details, owner certification, take-off location and time, mission type, route data, operating status. The 3GPP system shall enable a UAS to send the following UAV controller data to a UTM: unique identity, UE capability of the UAV controller, position, owner identity, owner address, owner contact details, owner certification, the identity of the UAV operator who operate the UAV controller, UAV operator license and certification. The 3GPP system shall enable a UAS to send different UAS data to UTM based on the different authentication and authorizations level which are applied to the UAS. The 3GPP system shall support capability to extend UAS data being sent to UTM with the evolution of UTM and its support applications in future. The 3GPP system shall protect against spoofing attacks of the UAS identities. The 3GPP system shall protect the integrity of the message(s) sent from UAS to a UTM containing the UAS identities. The 3GPP system shall enable a UE in a UAS to send the following identifiers to a UTM: IMSI, IMEI, MSISDN. The 3GPP system shall protect the confidentiality of the message(s) sent between UAS to a UTM containing the UAS identities. The 3GPP system may enable an MNO to augment the data sent to a UTM with the following: network-based positioning information, preconfigured pairing data. A UAS may optimise subsequent messages sent to an UTM by omitting unchanged static or semi-static data (e.g. owner identity, owner address, owner contact details, owner certification). The UTM shall be able to associate the UAV and UAV controller, identify them as a UAS, and authorise a UAS to operate. The UTM shall be able to coordinate the route data provided in the authorisation to operate and change it if needed. The UTM shall be able to refuse authorisation for a UAS to operate. The UTM shall be able to inform an MNO of the outcome of an authorisation to operate. An MNO shall be able to enforce the authorisation for a UAS to operate (e.g. by enabling or disabling communication between the UAV and UAV controller). The 3GPP system shall enable an MNO to allow a UAS authorisation request only if appropriate subscription information is present. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.1.3 |
5,627 | 5.3.26 Support for unavailability period | If the UE and network support unavailability period and an event is triggered in the UE making the UE unavailable for a certain period of time, the UE may store its 5GMM and 5GSM context in USIM or non-volatile memory in the ME to be able to reuse it after the unavailability period. NOTE 1: How and where the UE stores its contexts depends upon the UE implementation. The UE can store some or all of its contexts in the ME or USIM using existing ME or USIM functionality. To activate the unavailability period, the UE provides unavailability information, including a type of unavailability, an unavailability period duration if known, and the start of the unavailability period if known, during the registration procedure or during the de-registration procedure (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]). The support for the unavailability period is negotiated in the registration procedure. If the UE is registered to a PLMN via a satellite NG-RAN cell, the AMF may provide the unavailability period duration of the UE during the registration procedure. The AMF may consider the unavailability period duration provided by the UE if available and determine the unavailability period duration of the UE as described in subclause 5.5.1.3.4. If the UE provided unavailability information in the last registration procedure or de-registration procedure, the AMF considers the UE unreachable until the UE re-register for a normal service without providing unavailability information. If the UE did not include a start of the unavailability period, the AMF shall consider the start of the unavailability period to be the time at which AMF received the REGISTRATION REQUEST message or the DEREGISTRATION REQUEST message from the UE. During the registration procedure, the AMF may determine the values of the negotiated extended DRX parameters, the timer T3324, and the periodic registration update timer (T3512) to be provided to the UE based on the unavailability period duration and the start of the unavailability period based on their availability. The AMF should set the value of the mobile reachable timer and implicit de-registration timer based on the unavailability period duration and the start of the unavailability period. The AMF releases the N1 signalling connection after the completion of the registration procedure in which the UE provided unavailability information without providing the start of the unavailability period. NOTE 2: If the UE supports MUSIM and the UE and the networks the UE is registered with support the unavailability period, then the UE can indicate a different unavailability period to each registered network. If for discontinuous coverage the UE has stored a discontinuous coverage maximum time offset as described in subclause 5.4.4.3, 5.5.1.2.4, and 5.5.1.3.4, the UE shall set the discontinuous coverage maximum time offset value to a random value up to and including the stored discontinuous coverage maximum time offset for this PLMN and satellite NG-RAN RAT Type, determine a time point equal to the time when the UE is about to lose satellite coverage minus the discontinuous coverage maximum time offset value, and send the REGISTRATION REQUEST message for mobility registration update to the AMF indicating out of coverage at the determined time point. If for discontinuous coverage the UE has stored a maximum time offset as described in subclause 5.4.4.3, 5.5.1.2.4, and 5.5.1.3.4, upon returning in coverage of a TA in the current registration after being out of coverage due to discontinuous coverage, and in the last REGISTRATION ACCEPT message the end of unavailability period report was set to "UE needs to report end of unavailability period", the UE shall start the discontinuous coverage maximum time offset timer with a random value up to and including the stored maximum time offset value, if available, for this PLMN and NR satellite access, and starts the discontinuous coverage maximum time offset timer. The UE shall enter 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE state and shall not initiate any NAS signalling on that NR satellite access and PLMN while the maximum time offset timer is running. The UE shall stop the maximum time offset timer and initiate NAS signalling if the UE receives paging message, has pending emergency services, is establishing an emergency PDU session or is performing emergency services fallback procedure or when the UE enters a TAI outside the registration area. At expiry of the discontinuous coverage maximum time offset timer the UE shall perform a registration procedure for mobility registration update. If the end of unavailability period report indicates "UE does not need to report end of unavailability period" then upon returning in coverage of a TAI in the current registration area the UE shall choose an appropriate substate of 5GMM-REGISTERED and does not need to perform a registration procedure for mobility registration update due to end of the unavailability period. If for discontinuous coverage the AMF sets the End of unavailability report bit in Unavailability configuration IE value to “UE does not need to report end of unavailability”, the UE is not required to trigger the registration procedure for mobility registration update when the unavailability period duration has ended. If the AMF does not provide the Unavailability configuration IE or the AMF sets the End of unavailability report bit in Unavailability configuration IE value to “UE needs to report end of unavailability”, the UE should trigger registration procedure for mobility registration update when the unavailability period duration has ended. When the unavailability period is activated, all NAS timers are stopped and associated procedures aborted except for timers T3512, T3346, T3447, T3448, T3396, T3584, T3585, any back-off timers, T3245, T3247, the timer T controlling the periodic search for HPLMN or EHPLMN or higher prioritized PLMNs, and the timer TSENSE controlling the periodic search for PLMNs satisfying the operator controlled signal level threshold (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]). When the UE activates the unavailability period using registration procedure without providing the start of the unavailability period, then after successful completion of the procedure the UE shall enter the state 5GMM-REGISTERED.NO-CELL-AVAILABLE and may deactivate AS layer. Otherwise, if the UE provided the start of unavailability period in the registration procedure, the UE shall enter the state 5GMM-REGISTERED.NO-CELL-AVAILABLE and may deactivate AS layer only after the UE activates the unavailability period. When the UE activates the unavailability period using the de-registration procedure, then after successful completion of the procedure the UE shall enter the state 5GMM-DEREGISTERED.NO-CELL-AVAILABLE and deactivate the AS layer. When the UE comes out of the unavailability period the UE shall activate the AS layer if deactivated and perform registration procedure as described in subclause 5.5.1.2.2 and 5.5.1.3.2. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.26 |
5,628 | 6.2.5.1.4.5 Deleting a derived QoS rule in the UE | Upon expiry of timer T3583 associated with a derived QoS rule, the UE shall remove the derived QoS rule. Upon release of the PDU session, the UE shall remove the derived QoS rule(s) associated with the PDU session. If the network accepts the request from the UE to revoke the usage of reflective QoS and sets the value of the RQ timer to "deactivated" or zero, the UE shall remove the derived QoS rule(s) associated with the PDU session. Upon inter-system mobility from WB-N1 mode to NB-N1 mode or from NR connected to 5GCN to NB-N1 mode, the UE shall remove the derived QoS rule(s) associated with the PDU session that is kept active. When a derived QoS rule is deleted, the timer T3583 associated with the derived QoS rule shall be stopped. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.5.1.4.5 |
5,629 | 6.2.32 TSN AF | The TSN AF supports control plane translator functionality for the integration of the 5GS with a TSN network, this involves e.g.: - 5GS Bridge management. - Port and bridge management information exchange with DS-TT or NW-TT. - Interactions with the CNC for 5GS Bridge configuration and reporting. - determining the TSC Assistance Container and TSN QoS information by mapping TSN Stream(s) based on IEEE standards. The traffic pattern parameter determination may be based on PSFP (IEEE Std 802.1Q [98]) as specified in Annex I, clause I.1. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.32 |
5,630 | 5.31 Support for Cellular IoT 5.31.1 General | This clause provides an overview about 5GS optimisations and functionality for support of Cellular Internet-of-Things (Cellular IoT, or CIoT) according to service requirements described in TS 22.261[ Service requirements for the 5G system ] [2]. Cellular IoT is in earlier 3GPP releases also referred to as Machine Type Communication (MTC) (see clause 4.3.17 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]). The specific functionality is described in the affected procedures and features of this specification, in TS 23.502[ Procedures for the 5G System (5GS) ] [3], TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and other specifications. In this Release Control Plane CIoT 5GS Optimisations (clause 5.31.4) and User Plane CIoT 5GS Optimisations (clause 5.31.18) are only supported over E-UTRA and these CIoT 5GS optimisations are not supported over Non-3GPP RAT type accesses. CIoT functionality is provided by the visited and home networks when the networks are configured to support CIoT. It applies to both the non-roaming case and the roaming case and some functionality may be dependent upon the existence of appropriate roaming agreements between the operators. Some of the CIoT functions are controlled by subscriber data. Other CIoT functions are based on indicators sent by the UE to the network. CIoT functionality is performed by UEs that are configured to support different options as described in clause 5.31.2 Though motivated by scenarios and use cases defined in TS 22.261[ Service requirements for the 5G system ] [2], the functions added to support CIoT have general applicability and are in no way constrained to any specific scenario, use case or UE types, except where explicitly stated. In the context of CIoT the term AF denotes an SCS/AS as defined TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [36]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31 |
5,631 | 5.10 Multiple-PDN support and PDN activation for UEs supporting "Attach without PDN connectivity" 5.10.1 General | The EPS shall support simultaneous exchange of traffic to multiple PDNs through the use of separate PDN GWs or a single PDN GW. The usage of multiple PDNs is controlled by network policies and defined in the user subscription EPS Optimisation. The EPS shall support UE-initiated connectivity establishment in order to allow multiple PDN connections to one or more PDNs. It shall be possible for a UE to initiate disconnection from any PDN. All simultaneously active PDN connections of a UE that are associated with the same APN shall be provided by the same PDN-GW. UE support for multiple PDN connections is optional. If the Control Plane CIoT EPS Optimisation is supported: - a PDN connection of Non-IP PDN Type may also be served by an SCEF (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]); multiple PDN connections of Non-IP PDN Type may be served by the same or multiple SCEFs; and - the MME decides, based on APN Configuration information, whether a PDN connection is served by an SCEF or a PDN GW. | 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.10 |
5,632 | 10.13.2 MR-DC with 5GC | The Notification Control Indication procedure may be initiated either by the MN or by the SN and is used to indicate that GFBR for one or several QoS flows cannot be fulfilled any more or can be fulfilled again by the reporting node. Figure 10.13.2-1: Notification Control Indication procedure Figure 10.13.2-1 shows an example signalling flow for the Notification Control Indication procedure. 1. The MN may, for an SN terminated bearer, indicate, that the GFBR requested from the MN cannot be fulfilled anymore. In case the SN terminated bearer is configured as a split bearer, the SN may decide to increase the share provided by the SN or it may decide to notify the MN that resources requested for the SN terminated bearer cannot fulfill the GFBR any more. 2. Continuing the example message flow from step 1, the SN informs the MN that the GFBR for an SN terminated bearer cannot be fulfilled any more. 3. The MN decides to inform the 5GC that NG-RAN cannot fulfill the GFBR for a GBR QoS flow any more. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.13.2 |
5,633 | 16.14.4.2 Assumptions | A feeder link switch over may result in transferring the established connection for the affected UEs between two gNBs. For soft feeder link switch over, an NTN payload is able to connect to more than one NTN Gateway during a given period, i.e. a temporary overlap can be ensured during the transition between the feeder links. For hard feeder link switch over, an NTN payload connects to only one NTN Gateway at any given time, i.e. a radio link interruption may occur during the transition between the feeder links. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.4.2 |
5,634 | 5.5.2.1A.4 Mapping to physical resources | The sequence shall be multiplied with the amplitude scaling factor and mapped in sequence starting with to the sub-carriers. The set of sub-carriers used in the mapping process shall be identical to the corresponding PUSCH transmissions using sub-PRB allocations for BL/CE UEs as defined in clause 5.3.4. The mapping to resource elements shall be in increasing order of first, then , and finally the slot number. The value of the symbol index in a slot is 3. For BL/CE UEs, if uplink resource reservation is enabled for the UE as specified in [9], and the Resource reservation field in the DCI is set to 1, then in case of PUSCH transmission with associated with C-RNTI or SPS C-RNTI using UE-specific MPDCCH search space including PUSCH transmission without a corresponding MPDCCH, - In a subframe that is fully reserved as defined in clause 8.0 in [4], the demodulation reference signal transmission is postponed until the next BL/CE uplink subframe that is not fully reserved. - In a subframe that is partially reserved, the demodulation reference signal transmission in a SC-FDMA symbol that is reserved is dropped. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.2.1A.4 |
5,635 | 6.3.3.6 Abnormal cases in the UE | The following abnormal cases can be identified: a) PDU session inactive for the received PDU session ID. If the PDU session ID in the PDU SESSION RELEASE COMMAND message belongs to any PDU session in state PDU SESSION INACTIVE in the UE, the UE shall include the 5GSM cause #43 "Invalid PDU session identity" in the 5GSM STATUS message, and set the PDU session ID to the received PDU session ID in the UL NAS TRANSPORT message as specified in subclause 5.4.5. b) User-plane resources of the MA PDU session on the access indicated in the Access type IE not established. If the PDU session is an MA PDU session and has user-plane resources established on a single access different from the access indicated in the Access type IE, the UE shall not diagnose an error, further process the release command and consider the user-plane resources of the MA PDU session on the access indicated in the Access type IE as successfully released. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.3.6 |
5,636 | 6.5.3 Data integrity protection method | Figure 16 illustrates the use of the integrity algorithm f9 to authenticate the data integrity of a signalling message. Figure 16: Derivation of MAC-I (or XMAC-I) on a signalling message The input parameters to the algorithm are the Integrity Key (IK), the integrity sequence number (COUNT-I), a random value generated by the network side (FRESH), the direction bit DIRECTION and the signalling data MESSAGE. Based on these input parameters the user computes message authentication code for data integrity MAC-I using the integrity algorithm f9. The MAC-I is then appended to the message when sent over the radio access link. The receiver computes XMAC-I on the message received in the same way as the sender computed MAC-I on the message sent and verifies the data integrity of the message by comparing it to the received MAC-I. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.5.3 |
5,637 | 9.9.4.22 Header compression configuration | The purpose of the Header compression configuration information element is to negotiate ROHC channel setup parameters specified in IETF RFC 5795 [37] and, optionally, provide additional header compression context setup parameters. The Header compression configuration information element is coded as shown in figure 9.9.4.22.1 and table 9.9.4.22.1. The Header compression configuration is a type 4 information element with a minimum length of 5 octets and a maximum length of 257 octets. The optional Additional header compression parameters container field conveys the additional header compression context setup parameters as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] in a generic container. This field corresponds to the profile-specific information in the header of the ROHC IR packet type in IETF RFC 5795 [37]. Figure 9.9.4.22.1: Header compression configuration information element Table 9.9.4.22.1: Header compression configuration information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.4.22 |
5,638 | 4.1.1.1 Attempted RRC connection establishments | a) This measurement provides the number of RRC connection establishment attempts for each establishment cause. b) CC c) Receipt of an RRCConnectionRequest message by the eNodeB/RN from the UE. Each RRCConnectionRequest message received is added to the relevant per establishment cause measurement. The possible causes are included in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. The sum of all supported per cause measurements shall equal the total number of RRCConnectionRequest. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. e) The measurement name has the form RRC.ConnEstabAtt.Cause where Cause identifies the establishment cause. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.1.1.1 |
5,639 | 7.2.3 Create Bearer Request | The direction of this message shall be from PGW to SGW and from SGW to MME/S4-SGSN, and from PGW to TWAN/ePDG (see Table 6.1-1). The Create Bearer Request message shall be sent on the S5/S8 interface by the PGW to the SGW and on the S11 interface by the SGW to the MME as part of the Dedicated Bearer Activation procedure. The message shall also be sent on the S5/S8 interface by the PGW to the SGW and on the S4 interface by the SGW to the SGSN as part of the Secondary PDP Context Activation procedure or the Network Requested Secondary PDP Context Activation procedure. The message shall also be sent on the S2a interface by the PGW to the TWAN as part of the Dedicated bearer activation in WLAN on GTP S2a, and on the S2b interface by the PGW to the ePDG as part of the Dedicated S2b bearer activation with GTP on S2b. The message shall also be sent on the S5/S8 or S2a/S2b interface by the PGW to the SGW or to the TWAN/ePDG and on the S11/S4 interface by the SGW to the MME/S4-SGSN as part of the Network-initiated IP flow mobility procedure or the UE-initiated IP flow mobility procedure, as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71]. Table -1: Information Elements in a Create Bearer Request NOTE: In the case that the procedure was initiated by a UE Requested Bearer Resource Modification Procedure or a UE Requested Bearer Resource Allocation Procedure or Secondary PDP Context Activation Procedure, then there will be only one instance of the Bearer Contexts IE in the Create Bearer Request. Table -2: Bearer Context within Create Bearer Request Table 7.2.3-3: Load Control Information within Create Bearer Request Table 7.2.3-4: Overload Control Information within Create Bearer Request Table 7.2.3-5: PGW Change Info within Create Bearer Request | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.2.3 |
5,640 | 13.2.4.3.1.2 metadata | The JSON object containing information added by the sending SEPP. It shall contain: a) N32-f message ID: Unique identifier (64-bit integer) representing a HTTP Request/Response transaction between two SEPPs. The N32-f message ID is generated by the sending SEPP and included in the HTTP Request sent over the N32 interface. The receiving SEPP uses the same N32-f message ID when it responds back with a HTTP Response. The N32-f message ID is included in the metadata portion of the JSON structure. b) authorizedIPX ID: String identifying the first hop IPX (cIPX or pIPX) that is authorized to update the message. This field shall always be present. When there is no IPX that is authorized to update, the value of this field is set to null. The sending SEPP selects one of the IPX providers from the list exchanged with the other SEPP during parameter exchange over N32-c and includes its identifier value in this field. c) N32-f context ID: Unique identifier representing the N32-f context information used for protecting the message. This is exchanged during parameter exchange over N32-c (clause 13.2.2.4.1). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4.3.1.2 |
5,641 | 4.2.15 Architecture to support WLAN connection using 5G credentials without 5GS registration | The reference architecture shown with reference point representation in Figure 4.2.15-1 and with Service Based Interface (SBI)-representation in Figure 4.2.15-2, enables a UE to connect to a WLAN access network using its 5GS credentials without registration to 5GS. This architecture is based on the Non-Seamless WLAN Offload Function (NSWOF), which interfaces to the WLAN access network using the SWa' reference point and interfaces to the AUSF using the Nausf SBI. The SWa' reference point corresponds to SWa reference point as defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43] with the difference that SWa' the EAP procedure ensures that the permanent user ID is not visible over the access as defined in TS 33.501[ Security architecture and procedures for 5G System ] [29] and that SWa' connects the Untrusted non-3GPP IP Access, possibly via 3GPP AAA Proxy, to the NSWOF and that the EAP user ID is a SUCI and not an IMSI. The functionality of the NSWOF and the procedures applied for supporting a WLAN connection using 5GS credentials for Non-seamless WLAN offload are further defined in TS 33.501[ Security architecture and procedures for 5G System ] [29] Annex S. The roaming architectures are shown with reference point representation in Figure 4.2.15-3 and with SBI representation in Figure 4.2.15-4. The architecture in Figure 4.2.15-1 and Figure 4.2.15-2 applies to UEs with PLMN or SNPN credentials. NOTE 1: For a UE with SNPN credentials it is assumed that the realm part of UE identifier in SUCI format is defined in a way that enables routing of SWa requests from the WLAN AN to the NSWOF in the SNPN's 5GC. The architectures in Figure 4.2.15-3a and Figure 4.2.15-4a apply to UEs with PLMN or SNPN credentials from a CH using UDM. The architecture in Figure 4.2.15-3b applies to UEs with SNPN credentials from a CH using AAA Server. In this architecture the UE procedures for access selection for 5G NSWO defined in clause 6.3.12b apply. Except the UE, all NFs in Figure 4.2.15-3b are out of scope of 3GPP. The architectures in Figure 4.2.15-3c and Figure 4.2.15-4b apply to UEs with SNPN credentials from a CH using AAA Server via 5GC (NSWOF/AUSF/UDM/NSSAAF). In this architecture the UE procedures for access selection for 5G NSWO defined in clause 6.3.12b apply. NOTE 2: How to protect the user identity over the WLAN interface in architecture defined in Figure 4.2.15-3b and Figure 4.2.15-3c is defined in TS 33.501[ Security architecture and procedures for 5G System ] [29]. The UE can also connect to a WLAN access network using 5GS credentials by performing the 5GS registration via Trusted non-3GPP access procedure defined in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. With this procedure, the UE connects to a WLAN access network using 5GS credentials and simultaneously registers in 5GS. However, the architecture defined in Figure 4.2.15-1, Figure 4.2.15-2, Figure 4.2.15-3 and in Figure 4.2.15-4, enables a UE to connect to a WLAN access network using 5GS credentials but without registration in 5GS. If the WLAN is configured as Untrusted Non-3GPP access, in the case that the WLAN supports IEEE 802.1x, the UE may first use the 5G NSWO procedure to obtain a connection with and the local IP address from the WLAN, and any time after that, the UE may initiate the Untrusted Non-3GPP Access to obtain the access to 5GC. Figure 4.2.15-1: Reference architecture to support authentication for Non-seamless WLAN offload in 5GS Figure 4.2.15-2: Service based reference architecture to support authentication for Non-seamless WLAN offload in 5GS Figure 4.2.15-3: Roaming reference architectures to support authentication for Non-seamless WLAN offload in 5GS Figure 4.2.15-3a: Reference architectures to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using UDM Figure 4.2.15-3b: Reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server Figure 4.2.15-3c: Reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server via 5GC NOTE 2: Configuration 2) in Figure 4.2.15-3 and Figure 4.2.15-3a is a deployment variant of configuration 1) Figure 4.2.15-4: Service based Roaming reference architecture to support authentication for Non-seamless WLAN offload in 5GS The SWd' reference point corresponds to the SWd reference point as defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43] with the difference that SWd' connects the 3GPP AAA Proxy, possibly via intermediate 3GPP AAA Proxy, to the NSWOF and that the EAP user ID is a SUCI and not an IMSI. In both roaming and non-roaming scenarios, the NSWOF acts towards the WLAN Access as a 3GPP AAA server, with the difference that the EAP user ID is a SUCI and not an IMSI. Figure 4.2.15-4a: Service based reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using UDM Figure 4.2.15-4b: Service based reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server via 5GC | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.15 |
5,642 | 5.2.3.2.2 ATTEMPTING-TO-UPDATE | The UE: - shall not send any user data; - shall initiate tracking area updating on the expiry of timers T3411, T3402 or T3346; - shall initiate tracking area updating when entering a new PLMN, if timer T3346 is running and the new PLMN is not equivalent to the PLMN where the UE started timer T3346, the PLMN identity of the new cell is not in one of the forbidden PLMN lists, and the tracking area is not in one of the lists of forbidden tracking areas; - shall initiate tracking area updating when the tracking area of the serving cell has changed, if timer T3346 is not running, the PLMN identity of the new cell is not in one of the forbidden PLMN lists and the tracking area is not in one of the lists of forbidden tracking areas; - may initiate a tracking area updating procedure upon request of the upper layers to establish a PDN connection for emergency bearer services; - shall initiate tracking area updating procedure upon request of the upper layers to establish a PDN connection without the NAS signalling low priority indication as specified in clause 5.5.3.2.6, item l), if timer T3346 is running due to a NAS request message (TRACKING AREA UPDATE REQUEST, CONTROL PLANE SERVICE REQUEST or EXTENDED SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority" and timer T3402 and timer T3411 are not running; - may detach locally and initiate an attach for emergency bearer services even if timer T3346 is running; - shall use requests for non-EPS services from CM layers to trigger a combined tracking area updating procedure, if timer T3346 is not running (see clause 5.5.3.3), or to attempt to select GERAN, UTRAN or cdma2000® 1xRTT radio access technology and proceed with the appropriate MM and CC specific procedures; - may use requests for an MMTEL voice call or MMTEL video call from the upper layers to initiate tracking area updating, if timer T3346 is not running; - shall initiate tracking area updating when the UE performs inter-system change from N1 mode to S1 mode, even if timer T3402 is running; - shall initiate tracking area updating in response to paging with S-TMSI or paging with IMSI and domain indicator set to ″CS″; NOTE: As an implementation option, the MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. - shall initiate tracking area updating if the EPS update status is set to EU2 NOT UPDATED, and timers T3411, T3402 and T3346 are not running; - if configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], shall perform the eCall inactivity procedure at expiry of timer T3444 or T3445 (see clause 5.5.4); - may initiate tracking area updating 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) ] [15A]) if timer T3346 is not already running for "MO exception data" and even if timer T3402 or timer T3411 is running; - may initiate tracking area updating if the UE is a UE configured to use AC11 – 15 in the selected PLMN, even if timer T3402, T3346 or timer T3447 is running; and - shall not initiate the detach signalling procedure unless the current TAI is part of the TAI list. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.3.2.2 |
5,643 | 4.7.9.1 Paging for GPRS services | In A/Gb mode, paging is used by the network to identify the cell the MS has currently selected, or to prompt the mobile to re-attach if necessary as a result of network failure. If the MS is not GPRS attached when it receives a paging for GPRS services, the MS shall ignore the paging. In Iu mode, paging is used by the network to request the establishment of PS signalling connection or to prompt the mobile to re-attach if necessary as a result of network failure. If the MS is not GPRS attached when it receives a paging for GPRS services, the MS shall ignore the paging. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.9.1 |
5,644 | 8.3.3.1.2 TDD Pcell (TDD single carrier) | The parameters specified in Table 8.3.3.1.2-1 are valid for TDD CC and LAA SCell(s) unless otherwise stated. And the additional parameters specified in Table 8.3.3.1.2-2 are valid for LAA SCell(s). Table 8.3.3.1.2-1: Common Test Parameters Table 8.3.3.1.2-2: Addtional Test Parameters for LAA SCell(s) For CA with LAA SCell(s), the requirements for dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C are specified in Table 8.3.3.1.2-7, with the addition of the parameters in Table 8.3.3.1.2-3, Table 8.3.3.1.2-4 and Table 8.3.3.1.2-5, The downlink physical channel setup is set according to Annex C.3.2. The purpose of these tests is to verify the rank-2 performance for full RB allocation for CA with LAA SCell(s). Table 8.3.3.1.2-3: Test Parameters for Large Delay CDD (FRC) for PCell Table 8.3.3.1.2-4: Test Parameters for CDM-multiplexed DM RS (dual layer) for LAA SCell(s) Table 8.3.3.1.2-5: Single carrier performance Large Delay CDD (FRC) for PCell for multiple CA configurations Table 8.3.3.1.2-6: Single carrier performance for CDM-multiplexed DM RS (dual layer) for LAA SCell(s) for multiple CA configurations Table 8.3.3.1.2-7: Minimum performance (FRC) based on single carrier performance for CA with one LAA SCell Table 8.3.3.1.2-8: Minimum performance (FRC) based on single carrier performance for CA with two LAA SCells Table 8.3.3.1.2-9: Minimum performance (FRC) based on single carrier performance for CA with three LAA SCells Table 8.3.3.1.2-10: Minimum performance (FRC) based on single carrier performance for CA with four LAA SCells Table 8.3.3.1.2-11: Minimum performance (FRC) based on single carrier performance for CA with five LAA SCells Table 8.3.3.1.2-12: Minimum performance (FRC) based on single carrier performance for CA with six LAA SCells | 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.3.1.2 |
5,645 | 5.2.3.2.1 NORMAL-SERVICE | The UE: a) shall initiate the mobility or the periodic registration update procedure (according to conditions given in subclause 5.5.1.3.2), except that the periodic registration update procedure shall not be initiated over non-3GPP access; b) shall initiate the service request procedure (according to conditions given in subclause 5.6.1); c) shall respond to paging; NOTE 1: Paging is not supported over non-3GPP access. NOTE 2: As an implementation option, the MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. d) if configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22], shall perform the eCall inactivity procedure at expiry of timer T3444 or timer T3445 (see subclause 5.5.3); and e) shall initiate a registration procedure for mobility and periodic registration update on the expiry of timer T3511; and f) if acting as a 5G ProSe UE-to-network relay UE as specified in 3GPP 24.554 [19E], shall initiate the authentication and key agreement procedure (according to the conditions given in subclause 5.5.4). | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.3.2.1 |
5,646 | 9.2.3.4.4 Data Forwarding | If late data forwarding is applied, the source NG-RAN node initiates data forwarding once it knows which target NG-RAN node the UE has successfully accessed. In that case the behavior of the Conditional Handover data forwarding follows the same behavior as defined in 9.2.3.2.3 for the intra-system handover data forwarding, except the behavior for DRBs configured with DAPS handover. If early data forwarding is applied instead, the source NG-RAN node initiates data forwarding before the UE executes the handover, to a candidate target node of interest. The behavior of early data forwarding for the Conditional Handover follows the same principles for DRBs configured with DAPS handover in the intra-system handover as defined in 9.2.3.2.3. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.3.4.4 |
5,647 | 10.5.4.25 User-user | The purpose of the user-user information element is to convey information between the mobile station and the remote ISDN user. The user-user information element is coded as shown in figure 10.5.114/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.131/ 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . There are no restrictions on the content of the user-user information field. The user-user is a type 4 information element with a minimum length of 3 octets and a maximum length of either 35 or 131 octets. In the SETUP message the user-user information element has a maximum size of 35 octets in a GSM PLMN. In the USER INFORMATION, ALERTING, CONNECT, DISCONNECT, PROGRESS, RELEASE and RELEASE COMPLETE messages the user-user information element has a maximum size of 131 octets in a GSM PLMN. In other networks than GSM PLMNs the maximum size of the user-user information element is 35 or 131 octets in the messages mentioned above. The evolution to a single maximum value is the long term objective; the exact maximum value is the subject of further study. NOTE: The user-user information element is transported transparently through a GSM PLMN. Figure 10.5.114/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] User-user information element Table 10.5.131/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : User-user 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.4.25 |
5,648 | D.3.1 Example of possible implementation | This clause provides an example of a possible implementation of the "Loss" algorithm, amongst other possible methods. It is possible to make use of a statistical loss function (e.g., random selection of messages to throttle based on the indicated percentage) to decide if the given message can be sent or need to be throttled. For example, the source node generates a random number between (0, 100) for each message which is a potential candidate for throttling. To realize 10% throttling, messages with a random number 10 or less are throttled and hence this achieves approximately a 10% reduction in the overall traffic. The actual traffic reduction might vary slightly from the requested percentage, albeit by an insignificant amount. The algorithm can select certain messages to throttle in priority. For example, implementations can distinguish between higher-priority and lower-priority messages, and drop the lower-priority messages in favour of dropping the higher priority messages, as long as the total reduction in traffic conforms to the requested reduction in effect at the time. For example, in the 50-50 distribution of high priority and low priority messages, 20% reduction to low priority messages and 0% reduction to high priority messages need to be applied in order to achieve the effective reduction in traffic by 10% towards the overloaded node. | 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 | D.3.1 |
5,649 | 5.4.2.2 Authentication initiation by the network | When a NAS signalling connection exists, the network can initiate an authentication procedure at any time. For restrictions applicable after handover or inter-system handover to S1 mode see clause 5.5.3.2.3. The network initiates the authentication procedure by sending an AUTHENTICATION REQUEST message to the UE and starting the timer T3460 (see example in figure 5.4.2.2.1). The AUTHENTICATION REQUEST message contains the parameters necessary to calculate the authentication response (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). If an eKSI is contained in an initial NAS message during an EMM procedure, the network shall include a different eKSI value in the AUTHENTICATION REQUEST message when it initiates an authentication procedure. Figure 5.4.2.2.1: Authentication procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.2.2 |
5,650 | 5.6C Channel bandwidth for Dual Connectivity | For E-UTRA DC bands specified in 5.5C, the corresponding E-UTRA CA configurations in 5.6A.1, i.e., dual uplink inter-band carrier aggregation with uplink assigned to two E-UTRA bands, are applicable to Dual Connectivity. NOTE 1: Requirements for the dual connectivity configurations are defined in the section corresponding E-UTRA uplink CA configurations, unless otherwise specified. NOTE 2: For TDD inter-band dual connectivity configurations, requirements are applicable only for synchronous operation. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.6C |
5,651 | 4.2.2.8 Service State, RECEIVING GROUP CALL (LIMITED SERVICE) | Only applicable for mobile stations supporting VGCS listening or VBS listening: When in state MM IDLE and service state RECEIVING GROUP CALL (LIMITED SERVICE), the mobile station shall: - not perform periodic updating; - not perform IMSI detach; - reject any requests from CM entities for MM connections except for emergency calls; - perform normal location updating when a cell is entered which may provide normal service (e.g. location area not in one of the forbidden LAI lists.); - it may respond to paging (with IMSI); - indicate notifications to the GCC or BCC sublayer for which a channel description has been received in the notification by the RR sublayer; - reject requests of the GCC or BCC sublayer to respond to notifications for which no channel description has been received in the notification by the RR sublayer; - request the RR sublayer to receive a voice group or broadcast call if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for which a channel description has been received in the notification by the RR sublayer and then go to the service state RECEIVING GROUP CALL (LIMITED SERVICE). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.2.8 |
5,652 | 9.3.2.2.2 TDD | For the parameters specified in Table 9.3.2.2.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.2.2.2-2 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. Table 9.3.2.2.2-1 Fading test for TDD Table 9.3.2.2.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.2.2.2 |
5,653 | 5.15.2.1.2 Sidelink process | For each subframe where a transmission takes place for the Sidelink process, one TB and the associated HARQ information is received from the Sidelink HARQ Entity. The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is updated modulo 4. The Sidelink process shall: - if this subframe corresponds to a new transmission opportunity: - set CURRENT_IRV to 0; - else, if this subframe corresponds to a retransmission opportunity: - increment CURRENT_IRV by 1. - if a TB was allocated to the Sidelink process: - if this is a new transmission: - optionally store the received data in the soft buffer and attempt to decode the received data according to the CURRENT_IRV. - else if this is a retransmission: - if the data for this TB has not yet been successfully decoded: - optionally combine the received data with the data currently in the soft buffer for this TB and attempt to decode the combined data according to the CURRENT_IRV. - if the data which the MAC entity attempted to decode was successfully decoded for this TB: - if this is the first successful decoding of the data for this TB: - deliver the decoded MAC PDU to upper layers. | 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.15.2.1.2 |
5,654 | – SL-BWP-PoolConfig | The IE SL-BWP-PoolConfig is used to configure NR sidelink communication resource pool. SL-BWP-PoolConfig information element -- ASN1START -- TAG-SL-BWP-POOLCONFIG-START SL-BWP-PoolConfig-r16 ::= SEQUENCE { sl-RxPool-r16 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 OPTIONAL, -- Cond HO sl-TxPoolSelectedNormal-r16 SL-TxPoolDedicated-r16 OPTIONAL, -- Need M sl-TxPoolScheduling-r16 SL-TxPoolDedicated-r16 OPTIONAL, -- Need N sl-TxPoolExceptional-r16 SL-ResourcePoolConfig-r16 OPTIONAL -- Need M } SL-TxPoolDedicated-r16 ::= SEQUENCE { sl-PoolToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolID-r16 OPTIONAL, -- Need N sl-PoolToAddModList-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolConfig-r16 OPTIONAL -- Need N } SL-ResourcePoolConfig-r16 ::= SEQUENCE { sl-ResourcePoolID-r16 SL-ResourcePoolID-r16, sl-ResourcePool-r16 SL-ResourcePool-r16 OPTIONAL -- Need M } SL-ResourcePoolID-r16 ::= INTEGER (1..maxNrofPoolID-r16) -- TAG-SL-BWP-POOLCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,655 | 4.7.4.1.2 MS initiated GPRS detach procedure completion for GPRS services only | When the DETACH REQUEST message is received by the network, the network shall send a DETACH ACCEPT message to the MS, if the detach type IE value indicates that the detach request has not been sent due to switching off. If switching off was indicated, the procedure is completed when the network receives the DETACH REQUEST message. The network and the MS shall deactivate the PDP contexts, the MBMS contexts and deactivate the logical link(s), if any. The MS is marked as inactive in the network for GPRS services; state GMM-DEREGISTERED is entered in the MS and the network. In Iu mode, if the detach has been sent due to switching off, then the network shall release the resources in the lower layers for this MS (see 3GPP TS 25.331[ None ] [23c]). NOTE: When the DETACH REQUEST message is received by the network, and if the detach type IE value indicates that the detach is not due to power off, the authentication and ciphering procedure as well as the identification procedure may be performed. If the MS supports S1 mode and operates in MS operation mode A or B , the MS shall disable the E-UTRA capability (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.4.1.2 |
5,656 | 5.9.3.3 Broadcast MRB establishment | Upon a broadcast MRB establishment, the UE shall: 1> establish a PDCP entity and an RLC entity in accordance with MRB-InfoBroadcast for this broadcast MRB included in the MBSBroadcastConfiguration message and the configuration specified in 9.1.1.7; 1> configure the MAC layer in accordance with the mtch-SchedulingInfo (if included); 1> configure the physical layer in accordance with the mbs-SessionInfoList, searchSpaceMTCH, and pdsch-ConfigMTCH, applicable for the broadcast MRB; 1> if an SDAP entity with the received mbs-SessionId does not exist: 2> establish an SDAP entity as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24] clause 5.1.1; 2> indicate the establishment of the user plane resources for the mbs-SessionId to upper layers; 1> receive DL-SCH on the cell where the MBSBroadcastConfiguration message was received for the established broadcast MRB using g-RNTI and mtch-SchedulingInfo (if included) in this message for this MBS broadcast service. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.3.3 |
5,657 | 9.11.3.31B Mapped NSSAI | The purpose of the Mapped NSSAI information element is to transfer S-NSSAI(s) applicable in the HPLMN to the visited PLMN. The Mapped NSSAI information element is coded as shown in figure 9.11.3.31B.1, figure 9.11.3.31B.2 and table 9.11.3.31B.1. The Mapped NSSAI is a type 4 information element with a minimum length of 4 octets and a maximum length of 42 octets. NOTE 1: The total number of S-NSSAI values in a requested mapped NSSAI cannot exceed eight. Figure 9.11.3.31B.1: Mapped NSSAI information element Figure 9.11.3.31B.2: Mapped S-NSSAI content Table 9.11.3.31B.1: Mapped NSSAI information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.31B |
5,658 | 4.13.3.2 Deregistration procedures for SMS over NAS | If UE indicates to AMF that it no longer wants to send and receive SMS over NAS (e.g. not including "SMS supported" indication in subsequent Registration Request message) or AMF considers that UE is deregistered on specific Access Type(s) or AMF receives Deregistration Notification from UDM for specific Access Type(s) indicating UE Initial Registration, Subscription Withdrawn or 5GS to EPS Mobility as specified in clause 5.2.3.2.2, then: - AMF may, if the UE is not registered at other Access Type at the AMF any more, unsubscribe from SMS Subscription data changes notification with the UDM by means of the Nudm_SDM_Unsubscribe service operation. - AMF invokes Nsmsf_SMService_Deactivate service operation to trigger the release of UE Context for SMS on SMSF for the impacted Access Type(s) based on local configurations. - AMF may, if the UE is not registered at other Access Type at the AMF anymore, delete or deactivate the stored SMSF address in its UE Context. - The SMSF unsubscribes from SMS Management Subscription data changes notification with the UDM by means of the Nudm_SDM_Unsubscribe service operation if the UE is not registered at other Access Type for SMS over NAS service at the SMSF anymore. - The SMSF shall invoke Nudm_UECM_Deregistration (SUPI, NF ID, Access Type) service operation from UDM to trigger UDM to delete SMSF address of the UE for the impacted Access Type(s). The SMSF also removes the UE Context for SMS for the impacted Access Type(s), including AMF address. - The UDM may update UE context in SMSF in UDR by Nudr_DM_Update (SUPI, Subscription Data, SMS Subscription data, SMSF address). The UDM may remove the corresponding subscription of data change notification in UDR by Nudr_DM_Unsubscribe service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.3.2 |
5,659 | 4.17.6.2 SMF provisioning of UPF instances using NRF | This procedure applies when a SMF wants to get informed about UPFs available in the network and supporting a list of parameters. Figure 4.17.6.2-1: SMF provisioning of UPF instances using NRF procedure The following takes place when an SMF expects to be informed of UPFs available in the network: 1 The SMF issues a Nnrf_NFManagement_NFStatusSubscribe Service Operation providing the target UPF Provisioning Information it is interested in. 2 The NRF issues Nnrf_NFManagement_NFStatusNotify with the list of all UPFs that currently meet the SMF subscription. This notification indicates the subset of the target UPF Provisioning Information that is supported by each UPF. The following takes place when a new UPF instance is deployed: 3 At any time a new UPF instance is deployed. 4 The UPF instance is configured with the NRF identity to contact for registration and with its UPF Provisioning Information. An UPF is not required to understand the UPF Provisioning Information beyond usage of this information to register in step 5. 5 The UPF instance issues an Nnrf_NFManagement_NFRegister Request operation providing its NF type, the FQDN or IP address of its N4 interface and the UPF Provisioning Information configured in step 4. 6. Alternatively (to steps 4 and 5) OAM registers the UPF on the NRF indicating the same UPF Provisioning Information as provided in step 5. This configuration mechanism is out of scope of this specification. 7. Based on the subscription in step 1, the NRF issues Nnrf_NFManagement_NFStatusNotify to all SMFs with a subscription matching the UPF Provisioning Information of the new UPF | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.6.2 |
5,660 | 5.7.2.4.1b Notification control with Alternative QoS Profiles | If, for a given GBR QoS Flow, Notification control is enabled and the NG-RAN has received a list of Alternative QoS Profile(s) for this QoS Flow and supports the Alternative QoS Profile handling, the following shall apply: 1) If the NG-RAN determines that the GFBR, the PDB or the PER of the QoS profile cannot be fulfilled, NG-RAN shall send a notification towards SMF that the "GFBR can no longer be guaranteed". Before sending a notification that the "GFBR can no longer be guaranteed" towards the SMF, the NG-RAN shall check whether the GFBR, the PDB and the PER that the NG-RAN currently fulfils match any of the Alternative QoS Profile(s) in the indicated priority order. If there is a match, the NG-RAN shall indicate the reference to the matching Alternative QoS Profile with the highest priority together with the notification to the SMF. If there is no match, the NG-RAN shall send a notification that the "GFBR can no longer be guaranteed" towards the SMF indicating that the lowest Alternative QoS Profile cannot be fulfilled (unless specific conditions at the NG-RAN require the release of the NG-RAN resources for this GBR QoS Flow, e.g. due to Radio link failure or RAN internal congestion). 2) If a notification that the "GFBR can no longer be guaranteed" has been sent to the SMF and the NG-RAN determines that the currently fulfilled GFBR, PDB or PER are different (better or worse) from the situation indicated in the last notification, the NG-RAN shall send a notification (i.e. "GFBR can no longer be guaranteed" or "GFBR can be guaranteed again") to the SMF and indicate the current situation (unless specific conditions at the NG-RAN require the release of the NG-RAN resources for this GBR QoS Flow, e.g. due to Radio link failure or RAN internal congestion). NOTE 1: The current situation is either that the QoS Profile can be fulfilled (which is implicitly indicated by the "GFBR can be guaranteed again" notification itself), that a different Alternative QoS Profile can be fulfilled, or that the lowest priority Alternative QoS Profile cannot be fulfilled. 3)- The NG-RAN should always try to fulfil the QoS profile and, if this is not possible, any Alternative QoS Profile that has higher priority. NOTE 2: In order to avoid a too frequent signalling to the SMF, it is assumed that NG-RAN implementation can apply hysteresis (e.g. via a configurable time interval) before notifying the SMF that the currently fulfilled values match the QoS Profile or a different Alternative QoS Profile of higher priority. It is also assumed that the PCF has ensured that the QoS values within the different Alternative QoS Profile(s) are not too close to each other. 4) Upon receiving a notification from the NG-RAN, the SMF may inform the PCF. If it does so, the SMF shall indicate the currently fulfilled situation to the PCF. See TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. 5) If the PCF has not indicated differently, the SMF uses NAS signalling (that is sent transparently through the RAN) to inform the UE about changes in the QoS parameters (i.e. 5QI, GFBR, MFBR) that the NG-RAN is currently fulfilling for the QoS Flow after Notification control has occurred. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.2.4.1b |
5,661 | 9.11.4.28 Ethernet header compression configuration | The purpose of the Ethernet header compression configuration information element is to negotiate the use of EHC and the length of the CID field in the EHC packet (see 3GPP TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [29]). The Ethernet header compression configuration information element is coded as shown in figure 9.11.4.28.1 and table 9.11.4.28.1. The Ethernet header compression configuration is a type 4 information element with the length of 3 octets. Figure 9.11.4.28.1: Ethernet header compression configuration information element Table 9.11.4.28.1: Ethernet header compression configuration information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.28 |
5,662 | 8.7.5.2 Minimum Requirement TDD PCell | For UE not supporting 256QAM, the requirements for TDD FDD CA with TDD PCell are specified in Table 8.7.5.2-1 with the additional parameters specified in Table 8.7.5-1, and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.5.2-2. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.2-3 with the additional parameters specified in Table 8.7.5-1, and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category or UE DL category, and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.5.2-4. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements in Table 8.7.5.2-1 is not applicable. The applicability of ther requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.7.5.2-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM) Table 8.7.5.2-2: Test points for sustained data rate (FRC 64QAM) Table 8.7.5.2-3: Minimum requirement (TDD FDD CA 256QAM) Table 8.7.5.2-4: Test points for sustained data rate (FRC 256QAM) | 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.5.2 |
5,663 | – FeatureSetEUTRA-DownlinkId | The IE FeatureSetEUTRA-DownlinkId identifies a downlink feature set in E-UTRA list (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. The first element in that list is referred to by FeatureSetEUTRA-DownlinkId = 1. The FeatureSetEUTRA-DownlinkId=0 is used when the UE does not support a carrier in this band of a band combination. FeatureSetEUTRA-DownlinkId information element -- ASN1START -- TAG-FEATURESETEUTRADOWNLINKID-START FeatureSetEUTRA-DownlinkId ::= INTEGER (0..maxEUTRA-DL-FeatureSets) -- TAG-FEATURESETEUTRADOWNLINKID-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,664 | 5.3.17 Service Gap Control | Service gap control (SGC) only applies to 3GPP access. The network may control the frequency with which UEs can transition from 5GMM-IDLE mode to 5GMM-CONNECTED mode via the SGC as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. If the network supports SGC and the service gap time value i.e. T3447 value is available in the 5GMM context of the UE, the AMF shall consider SGC as active for the UE. The UE and the network negotiate usage of SGC during the registration procedure for initial registration and registration procedure for mobility and periodic registration update: - the UE supporting SGC indicates its support in the REGISTRATION REQUEST message. If the UE supports SGC and the SGC is active for the UE, the AMF includes T3447 value IE in the REGISTRATION ACCEPT message (see subclause 5.5.1.2 and subclause 5.5.1.3). The UE stores the T3447 value; and - for UEs that do not support SGC when the network rejects mobility management signalling requests because SGC is active in the network, the mechanism for general NAS level mobility management congestion control as specified in subclause 5.3.9 applies. The network can provide a new T3447 value to the UE to be used next time it is started or stop timer T3447 in the UE if running with the Generic UE configuration update procedure as specified in subclause 5.4.4. The UE shall start timer T3447 when the N1 NAS signalling connection is released and if: - the UE supports SGC, and the T3447 value is available in the UE and does not indicate zero; and - the N1 NAS signalling connection released was not established for: - paging; - registration procedure for initial registration with Follow-on request indicator set to "No follow-on request pending"; - registration procedure for mobility and periodic registration update with Follow-on request indicator set to "No follow-on request pending" and without Uplink data status IE included; - requests for emergency services; or - requests for exception data reporting. If the SGC is active in the network, after the UE transitions from 5GMM-CONNECTED mode to 5GMM-IDLE mode except when the UE was in 5GMM-CONNECTED mode due to: - paging; - registration procedure for initial registration with Follow-on request indicator set to "No follow-on request pending"; - registration procedure for mobility and periodic registration update with Follow-on request indicator set to "No follow-on request pending" and without Uplink data status IE included, - requests for emergency services; or - requests for exception data reporting, the network shall start timer T3447 if not already running: - with the T3447 value available in the 5GMM context minus 4 minutes, if the UE supports SGC and the T3447 value has been sent to the UE with a non-zero value; or - with the T3447 value available in the 5GMM context if the UE does not support SGC. When timer T3447 is running, the network allows: - requests for emergency service; - requests for emergency services fallback; - requests for high priority access; - requests for exception data reporting; - registration procedure for initial registration with Follow-on request indicator set to "No follow-on request pending"; - registration procedure for mobility and periodic registration update without Uplink data status IE included and with Follow-on request indicator set to "No follow-on request pending"; or - service request procedure or registration procedure for mobility and periodic registration update triggered by paging and subsequent MO signalling or MO data, if any, until the UE enters 5GMM-IDLE mode. The UE or the network with a running T3447 timer keeps the timer running when the UE transits from 5GMM-IDLE mode to 5GMM-CONNECTED mode. NOTE: If the UE transitions from 5GMM-IDLE mode to 5GMM-CONNECTED mode due to registration procedure for initial registration with Follow-on request indicator set to "No follow-on request pending" or mobility and periodic registration update request without Uplink data status IE and with Follow-on request indicator set to "No follow-on request pending", the UE initiates no further MO signalling except for mobility and periodic registration update requests without Uplink data status and with Follow-on request indicator set to "No follow-on request pending" until the UE receives mobile terminated signalling (e.g. DL NAS TRANSPORT message for MT SMS) or MT data over user plane, or after the UE has moved to 5GMM-IDLE state and the service gap timer is not running. If timer T3447 is running when the UE changes PLMN or enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE remains the same, then timer T3447 is kept running until it expires. If the AMF determines that the UE operating in single-registration mode has performed an inter-system change from N1 mode to S1 mode and the timer T3447 is running in the AMF, the AMF stops the T3447. Upon inter-system change from S1 mode to N1 mode, if the UE supports service gap control, T3447 is running in the UE, and the T3447 value IE is included in the REGISTRATION ACCEPT message received from the AMF (see subclause 5.5.1.2 and subclause 5.5.1.3), the UE shall keep T3447 running. Additionally, the UE shall store and replace the currently stored service gap time value with the received T3447 value. Upon expiry of the running T3447 timer, the UE shall use the new value when starting T3447 again. If the UE is switched off when the timer T3447 is running, the UE shall behave as follows when the UE is switched on and the USIM in the UE remains the same: - let t1 be the time remaining for timer T3447 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. | 3GPP TS 24.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.17 |
5,665 | 5.6.1.2.2 UE is using EPS services with control plane CIoT EPS optimization | The UE shall send a CONTROL PLANE SERVICE REQUEST message, start T3417 and enter the state EMM-SERVICE-REQUEST-INITIATED. For case a in clause 5.6.1.1, the Control plane service type of the CONTROL PLANE SERVICE REQUEST message shall indicate "mobile terminating request". The UE may include the ESM DATA TRANSPORT message. The UE shall not include any ESM message other than ESM DATA TRANSPORT message. For case b in clause 5.6.1.1, - if the UE has pending IP, non-IP or Ethernet user data that is to be sent via the control plane radio bearers, the Control plane service type of the CONTROL PLANE SERVICE REQUEST message shall indicate "mobile originating request". The UE shall include an ESM DATA TRANSPORT message in the ESM message container IE. If the UE supports the CP-EDT (see 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [20]), the UE shall provide the CONTROL PLANE SERVICE REQUEST message in the NAS request to the lower layer to establish a RRC connection as specified in clause 5.3.1.1. For cases b and m in clause 5.6.1.1, - if the UE has pending IP, non-IP or Ethernet user data that is to be sent via the user plane radio bearers, the UE shall set the Control plane service type of the CONTROL PLANE SERVICE REQUEST message to "mobile originating request" and the "active" flag in the Control plane service type IE to 1. The UE shall not include any ESM message container or NAS message container IE in the CONTROL PLANE SERVICE REQUEST message. For case c in clause 5.6.1.1, the UE shall set the Control plane service type of the CONTROL PLANE SERVICE REQUEST message to "mobile originating request". If the CONTROL PLANE SERVICE REQUEST message is: - for sending SMS, the UE shall include the SMS message in the NAS message container IE and shall not include any ESM message container IE in the CONTROL PLANE SERVICE REQUEST message; and - for sending signalling different from SMS, the UE shall not include any ESM message container or NAS message container IE in the CONTROL PLANE SERVICE REQUEST message. For cases p and q in clause 5.6.1.1, the UE shall send the CONTROL PLANE SERVICE REQUEST message, - for case p in clause 5.6.1.1 set Request type to "NAS signalling connection release" in the UE request type IE and Control plane service type IE to "mobile originating request"; or - for case q in clause 5.6.1.1 set Request type to "Rejection of paging" in the UE request type IE and Control plane service type IE to "mobile terminating request"; and start T3417 and enter the state EMM-SERVICE-REQUEST-INITIATED. Further, the UE may include its paging restriction preference in the Paging restriction IE in the CONTROL PLANE SERVICE REQUEST message and shall not include any ESM message container or NAS message container IE in the CONTROL PLANE SERVICE REQUEST message. For case o in clause 5.6.1.1, the Control plane service type of the CONTROL PLANE SERVICE REQUEST message shall indicate "mobile originating request". The UE shall not include the Paging restriction IE in the CONTROL PLANE SERVICE REQUEST message. The UE may include the UE request type IE and set Request type to "NAS signalling connection release" to remove the paging restriction and request the release of the NAS signalling connection at the same time. If the UE requests the release of the NAS signalling connection, the UE shall not include any ESM message container or NAS message container IE in the CONTROL PLANE SERVICE REQUEST message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.1.2.2 |
5,666 | 6.2.3F UE maximum output power for modulation / channel bandwidth for category NB1 and NB2 | For UE category NB1 and NB2 power class 3 and 5 the allowed Maximum Power Reduction (MPR) for the maximum output power given in Table 6.2.2F-1 is specified in Table 6.2.3F-1. Table 6.2.3F-1: Maximum Power Reduction (MPR) for UE category NB1 and NB2 Power Class 3 and 5 For UE category NB1 and NB2 power class 6 the allowed Maximum Power Reduction (MPR) for the maximum output power given in Table 6.2.2F-1 is specified in Table 6.2.3F-2. Table 6.2.3F-2: Maximum Power Reduction (MPR) for UE category NB1 and NB2 Power Class 6 For the UE maximum output power modified by MPR, the power limits specified in sub-clause 6.2.5F 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.2.3F |
5,667 | 4.13.3 Network/Access selection for satellite access | Network/Access selection principles specified in clause 4.3.2.2 also apply for satellite access for Cellular IoT. In the case of satellite access for Cellular IoT, a UE with location capability (i.e. GNSS capability) should use its awareness of its location to select a PLMN that is allowed to operate the UE location as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. In order to ensure that regulatory requirements are met, the network may be configured to enforce this UE choice by verifying the UE location as specified in clause 4.13.4. | 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.3 |
5,668 | 10.5.7.6 MBMS context status | The purpose of the MBMS context status information element is to indicate the state of each MBMS context which can be identified by an NSAPI. The MBMS context status information element is a type 4 information element with a minimum length of 2 octets and a maximum length of 18 octets. The MBMS context status information element is coded as shown in figure 10.5.149/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.165/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.149/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] MBMS context status information element Table 10.5.165/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MBMS context status information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.7.6 |
5,669 | 12.2.6 Discovery of the support of the feature by the peer node | A GTP-C entity shall determine whether to use the load control feature (i.e. provide or handle load control information) - within the PLMN, based on the operator's policy (local PLMN-wide configuration); - across the PLMN boundaries, based on the operator's policy (local configuration per PLMN). NOTE: The feature may be activated when all or some of the nodes in the PLMN support the feature. The GTP-C entity assumes that all of the peer nodes support this feature when the feature is activated, i.e. it does not need to determine which peers support the feature. The above operator policy/local configuration may allow the use of load control at node level, load control at node level and APN level, or none. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.2.6 |
5,670 | 6.3.6.3.3 Combined N3IWF/ePDG Selection | If the UE is attached to 5GC via an N3IWF that is located in the same country as the country in which the UE is currently located and the AMF has previously indicated support for emergency services over non-3GPP access as defined in clause 5.16.4.1, the UE reuses the existing N3IWF connection for emergency services. Otherwise, the UE terminates any existing N3IWF connection and performs PLMN and N3IWF or ePDG selection for emergency services. If the UE is attached to EPC via an ePDG that has indicated support for the emergency services and is located in the same country as the country in which the UE is currently located, the UE reuses the existing ePDG connection for emergency services. Otherwise, the UE terminates the existing ePDG connection, if any, and performs PLMN and N3IWF or ePDG selection for emergency services. PLMN and N3IWF or ePDG selection for emergency services is performed as follows: If the UE is equipped with a UICC: - The UE determines whether it is located in the home country or a visited country; - If the UE is located in the home country the UE selects the Home PLMN for emergency services and selects an N3IWF or ePDG as follows: - If the Non-3GPP Access Node Selection Information for the HPLMN is available the UE selects first an N3IWF or ePDG based on the Non-3GPP Access Node type preference in the Non-3GPP Access Node Selection Information for the HPLMN. To select an N3IWF the UE uses the N3IWF identifier configuration (if available). If the N3IWF identifier configuration is not available, the UE constructs the FQDN format as indicated by the FQDN format in the Non-3GPP Access Node Selection Information for the HPLMN. To select an ePDG the UE selects the ePDG identified by the configured Emergency ePDG FQDN (if available). If the configured Emergency ePDG FQDN is not available, the UE constructs either the Tracking/Location Area Identity based Emergency ePDG FQDN or the Operator Identifier based Emergency ePDG FQDN as indicated by the FQDN format in the Non-3GPP Access Node Selection Information for the HPLMN. - If the Non-3GPP Access Node Selection Information is not available, the UE shall first attempt to select an N3IWF following the procedure defined in clause 6.3.6.2 before attempting to select an ePDG. To select an ePDG the UE selects the ePDG identified by the configured Emergency ePDG FQDN (if available). If the configured Emergency ePDG FQDN is not available, the UE constructs the Operator Identifier based Emergency ePDG FQDN. - If the UE is located in a visited country, the UE performs a DNS query using the Visited Country Emergency FQDN for N3IWF and using the Visited Country Emergency FQDN for ePDG, as specified in TS 23.003[ Numbering, addressing and identification ] [19] to determine which PLMNs in the visited country support emergency services in non-3GPP access. - If the DNS responses contain one or more records, the UE selects a PLMN that supports emergency services in non-3GPP access for the UE. Each record in the DNS responses shall contain the identity of a PLMN in the visited country supporting emergency services in non-3GPP access via ePDG or N3IWF. - The UE shall consider these PLMNs based on their priorities in the Non-3GPP Access Node Selection Information. If the UE cannot select a PLMN in the Non-3GPP Access Node Selection Information or if non-3GPP Access Node Selection Information is not available, the UE shall attempt to select any PLMN in the list of PLMNs returned in the DNS response. - Once the UE has selected a PLMN the UE shall select an N3IWF or ePDG for the selected PLMN as follows: - If the Non-3GPP Access Node Selection Information for the PLMN is available the UE selects first an N3IWF or ePDG based on the Non-3GPP Access Node type preference in the Non-3GPP Access Node Selection Information for the PLMN. To select an N3IWF the UE constructs the FQDN format as indicated by the FQDN format in the Non-3GPP Access Node Selection Information for the PLMN. To select an ePDG the UE constructs either the Tracking/Location Area Identity based Emergency ePDG FQDN or the Operator Identifier based Emergency ePDG FQDN as indicated by the FQDN format in the Non-3GPP Access Node Selection Information for the PLMN. - If the Non-3GPP Access Node Selection Information is not available, the UE shall first attempt to select an N3IWF following the procedure defined in clause 6.3.6.2 before attempting to select an ePDG. To select an ePDG the UE constructs the Operator Identifier based Emergency ePDG FQDN. - If the DNS response does not contain any record, or if the DNS response contains one or more records but the UE fails to select a PLMN that supports emergency services in non-3GPP access, or if the Emergency Registration procedure has failed for all PLMNs supporting emergency services in non-3GPP access, the UE notifies the user that emergency session cannot be established. If the UE is not equipped with a UICC, the UE shall perform the emergency ePDG/N3IWF selection procedure above as if always in a visited country and without using the Non-3GPP Access Node Selection Information, i.e. the UE may construct the Operator Identifier FQDN for N3IWF or ePDG based on a PLMN ID obtained via implementation specific means. When a N3IWF has been selected, the UE initiates an Emergency Registration. If the Emergency Registration fails, the UE shall attempt to select an ePDG before selecting another PLMN supporting emergency services in non-3GPP access. When an ePDG has been selected, the UE initiates an Emergency Registration. If the Emergency Registration fails, the UE shall attempt to select a N3IWF before selecting another PLMN supporting emergency services in non-3GPP access. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.6.3.3 |
5,671 | 12.3.4 APN level overload control 12.3.4.1 General | APN level overload control refers to advertising of the overload information at APN level granularity and hence applying the mitigation policies based on this information to the signalling traffic related to this APN only. Only a PGW may advertise APN level overload information when it detects overload for certain APNs, e.g. based on shortage of internal or external resources for an APN (e.g. IP address pool). NOTE: When all the internal and external resources, applicable to the APNs, are available for all the APNs served by a PGW, the node level overload information is exactly the same as APN level overload information of that PGW, for each of its APNs, and hence, performing node overload control can be sufficient. | 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 |
5,672 | 5.2.27.4.2 Ntsctsf_ASTI_Create operation | Service operation name: Ntsctsf_ASTI_Create Description: Authorize the request, activate the 5G access stratum time distribution. Inputs, Required: Target for 5G access stratum time distribution (one UE identified by a SUPI or a GPSI, a group of UEs identified by an Internal Group Identifier or an External Group Identifier), AF identifier, mandatory service parameters as described in Table 4.15.9.4-1. Inputs, Optional: Optional service parameters as described in Table 4.15.9.4-1, subscription for 5G access stratum time distribution status, Notification Target Addess. Outputs, Required: Operation execution result indication, in successful operation the time synchronization configuration id. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.4.2 |
5,673 | 4.4.5 Ciphering of NAS signalling messages | The use of ciphering in a network is an operator option subject to MME configuration. When operation of the network without ciphering is configured, the MME shall indicate the use of "null ciphering algorithm" EEA0 (see clause 9.9.3.23) in the current security context for all UEs. For setting the security header type in outbound NAS messages, the UE and the MME shall apply the same rules irrespective of whether the "null ciphering algorithm" or any other ciphering algorithm is indicated in the security context. When the UE establishes a new NAS signalling connection, it shall send the initial NAS message - partially ciphered, if it is a CONTROL PLANE SERVICE REQUEST message including an ESM message container information element or a NAS message container information element; and - unciphered, if it is any other initial NAS message. The UE shall partially cipher the CONTROL PLANE SERVICE REQUEST message by ciphering the value part of the ESM message container IE or the value part of the NAS message container, using the ciphering algorithm of the current EPS security context. The UE shall send the ATTACH REQUEST message always unciphered. The UE shall send the TRACKING AREA UPDATE REQUEST message always unciphered. Except for the CONTROL PLANE SERVICE REQUEST message including an ESM message container information element or a NAS message container information element, the UE shall start the ciphering and deciphering of NAS messages when the secure exchange of NAS messages has been established for a NAS signalling connection. From this time onward, unless explicitly defined, the UE shall send all NAS messages ciphered until the NAS signalling connection is released, or the UE performs intersystem handover to A/Gb mode or Iu mode. The MME shall start ciphering and deciphering of NAS messages as described in clause 4.4.2.3. From this time onward, except for the SECURITY MODE COMMAND message, the MME shall send all NAS messages ciphered until the NAS signalling connection is released, or the UE performs intersystem handover to A/Gb mode or Iu mode. Once the encryption of NAS messages has been started between the MME and the UE, the receiver shall discard the unciphered NAS messages which shall have been ciphered according to the rules described in this specification. The MME shall discard any CONTROL PLANE SERVICE REQUEST message including an ESM message container information element or a NAS message container information element which has not been partially ciphered according to the rules described above. If the "null ciphering algorithm" EEA0 has been selected as a ciphering algorithm, the NAS messages with the security header indicating ciphering are regarded as ciphered. Details of ciphering and deciphering of NAS signalling messages are specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.5 |
5,674 | 5.2.2.3.2 Acquisition of an SI message | For SI message acquisition PDCCH monitoring occasion(s) are determined according to searchSpaceOtherSystemInformation. If searchSpaceOtherSystemInformation is set to zero, PDCCH monitoring occasions for SI message reception in SI-window are same as PDCCH monitoring occasions for SIB1 where the mapping between PDCCH monitoring occasions and SSBs is specified in TS 38.213[ NR; Physical layer procedures for control ] [13]. If searchSpaceOtherSystemInformation is not set to zero, PDCCH monitoring occasions for SI message are determined based on search space indicated by searchSpaceOtherSystemInformation. PDCCH monitoring occasions for SI message which are not overlapping with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are sequentially numbered from one in the SI window. The [x×N+K]th PDCCH monitoring occasion (s) for SI message in SI-window corresponds to the Kth transmitted SSB, where x = 0, 1, ...X-1, K = 1, 2, …N, N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 and X is equal to CEIL(number of PDCCH monitoring occasions in SI-window/N). The actual transmitted SSBs are sequentially numbered from one in ascending order of their SSB indexes. The UE assumes that, in the SI window, PDCCH for an SI message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB and thus the selection of SSB for the reception SI messages is up to UE implementation. When acquiring an SI message, the UE shall: 1> determine the start of the SI-window for the concerned SI message as follows: 2> if the concerned SI message is configured in the schedulingInfoList: 3> for the concerned SI message, determine the number n which corresponds to the order of entry in the list of SI messages configured by schedulingInfoList in si-SchedulingInfo in SIB1; 3> determine the integer value x = (n – 1) × w, where w is the si-WindowLength; 3> the SI-window starts at the slot #a, where a = x mod N, in the radio frame for which SFN mod T = FLOOR(x/N), where T is the si-Periodicity of the concerned SI message and N is the number of slots in a radio frame as specified in TS 38.213[ NR; Physical layer procedures for control ] [13]; 2> else if the concerned SI message is configured in the schedulingInfoList2; 3> determine the integer value x = (si-WindowPosition -1) × w, where w is the si-WindowLength; 3> the SI-window starts at the slot #a, where a = x mod N, in the radio frame for which SFN mod T = FLOOR(x/N), where T is the si-Periodicity of the concerned SI message and N is the number of slots in a radio frame as specified in TS 38.213[ NR; Physical layer procedures for control ] [13]; 2> else if the concerned SI message is configured in the posSchedulingInfoList and offsetToSI-Used is not configured: 3> create a concatenated list of SI messages by appending the posSchedulingInfoList in posSI-SchedulingInfo in SIB1 to schedulingInfoList in si-SchedulingInfo in SIB1; 3> for the concerned SI message, determine the number n which corresponds to the order of entry in the concatenated list; 3> determine the integer value x = (n – 1) × w, where w is the si-WindowLength; 3> the SI-window starts at the slot #a, where a = x mod N, in the radio frame for which SFN mod T = FLOOR(x/N), where T is the posSI-Periodicity of the concerned SI message and N is the number of slots in a radio frame as specified in TS 38.213[ NR; Physical layer procedures for control ] [13]; 2> else if the concerned SI message is configured by the posSchedulingInfoList and offsetToSI-Used is configured: 3> determine the number m which corresponds to the number of SI messages with an associated si-Periodicity of 8 radio frames (80 ms), configured by schedulingInfoList in SIB1; 3> for the concerned SI message, determine the number n which corresponds to the order of entry in the list of SI messages configured by posSchedulingInfoList in SIB1; 3> determine the integer value x = m × w + (n – 1) × w, where w is the si-WindowLength; 3> the SI-window starts at the slot #a, where a = x mod N, in the radio frame for which SFN mod T = FLOOR(x/N) +8, where T is the posSI-Periodicity of the concerned SI message and N is the number of slots in a radio frame as specified in TS 38.213[ NR; Physical layer procedures for control ] [13]; 1> receive the PDCCH containing the scheduling RNTI, i.e. SI-RNTI in the PDCCH monitoring occasion(s) for SI message acquisition, from the start of the SI-window and continue until the end of the SI-window whose absolute length in time is given by si-WindowLength, or until the SI message was received; 1> if the SI message was not received by the end of the SI-window, repeat reception at the next SI-window occasion for the concerned SI message in the current modification period; 1> if all the SIB(s) and/or posSIB(s) requested in DedicatedSIBRequest message have been acquired: 2> stop timer T350, if running; NOTE 1: The UE is only required to acquire broadcasted SI message if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located. NOTE 2: The UE is not required to monitor PDCCH monitoring occasion(s) corresponding to each transmitted SSB in SI-window. NOTE 3: If the concerned SI message was not received in the current modification period, handling of SI message acquisition is left to UE implementation. NOTE 4: A UE in RRC_CONNECTED may stop the PDCCH monitoring during the SI window for the concerned SI message when the requested SIB(s) are acquired. NOTE 5: A UE capable of NR sidelink communication/discovery and configured by upper layers to perform NR sidelink communication/discovery on a frequency, may acquire SIB12 or SystemInformationBlockType28 from a cell other than current serving cell (for RRC_INACTIVE or RRC_IDLE) or current PCell (for RRC_CONNECTED), if SIB12 of current serving cell (for RRC_INACTIVE or RRC_IDLE) or current PCell (for RRC_CONNECTED) does not provide configuration for NR sidelink communication/discovery for the frequency, and if the other cell providing configuration for NR sidelink communication/discovery for the frequency meets the S-criteria as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20] or TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [27]. 1> perform the actions for the acquired SI message as specified in clause 5.2.2.4. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.3.2 |
5,675 | 5.2.6.25.5 Nnef_TimeSynchronization_ConfigUpdateNotify operation | Service operation name: Nnef_TimeSynchronization_ConfigUpdateNotify Description: Forward the notification for the time synchronization configuration or (g)PTP time distribution status change. When the NEF receives a notification of a change corresponding to a time synchronization configuration or (g)PTP time distribution status from the TSCTSF, it forwards the notification by invoking a Nnef_TimeSynchronization_ConfigUpdateNotify service operation to the NF consumer(s) that has subscribed for the event. The event parameters are described in Table 5.2.27.2.5-1. Known NF Service Consumers: AF. Inputs, Required: As specified in clause 5.2.27.2.5. Inputs, Optional: As specified in clause 5.2.27.2.5. Outputs, Required: Operation execution result indication. 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.25.5 |
5,676 | 5.2.2.2.7A Namf_Communication_N1N2TransferFailureNotification service operation | Service operation name: Namf_Communication_N1N2TransferFailureNotification. Description: The AMF uses this notification to inform the NF service consumer that initiated an earlier Namf_Communication_N1N2MessageTransfer, that the AMF failed to deliver the N1 message to the UE as the UE failed to respond to paging, or the UE responded with a Reject Paging Indication. Input, Required: Cause, N1N2MessageTransfer Notification Target Address. Input, Optional: Estimated Maximum wait time. Output, Required: None. Output, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.7A |
5,677 | 10.5.4.29 Network Call Control Capabilities | The purpose of the Network Call Control Capabilities information element is to identify the call control capabilities of the network. The contents might affect the manner in which the mobile station handles the call. The Network Call Control Capabilities information element is coded as shown in figure 10.5.118/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.135/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Network Call Control Capabilities is a type 4 information element with a length of 3 octets. Figure 10.5.118/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Network Call Control Capabilities information element Table 10.5.135/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network Call Control Capabilities | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.29 |
5,678 | 4.11.1.5 Impacts to EPS Procedures 4.11.1.5.1 General | This clause captures changes to procedures in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] due to interworking with 5GS based on N26. The handover procedures between EPS and 5GS captured in clause 4.11.1.2 capture impacts to clause 5.5.1.2.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] (S1-based handover, normal). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.5 |
5,679 | 6.3.1A.4 Abnormal cases on the network side | The following abnormal cases can be identified: a) Expiry of timer T3594. On the first expiry of the timer T3594, the SMF shall resend the SERVICE-LEVEL AUTHENTICATION COMMAND message and shall reset and restart timer T3594. This retransmission is repeated four times, i.e., on the fifth expiry of timer T3594, the SMF shall abort the procedure and send PDU SESSION ESTABLISHMENT REJECT message with the 5GSM cause #29 "user authentication or authorization failed" as specified in subclause 6.4.1.4.1. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1A.4 |
5,680 | 4.5.1.6 Call re-establishment | The re-establishment procedure allows a MS to resume a connection in progress after a radio link failure, possibly in a new cell and possibly in a new location area. The conditions in which to attempt call re-establishment or not depend on the call control state, see subclause 5.5.4 and, whether or not a cell allowing call re-establishment has been found (as described in 3GPP TS 45.008[ None ] [34]). MM connections are identified by their protocol discriminators and transaction identifiers: these shall not be changed during call re-establishment. The re-establishment takes place when a lower layer failure occurs and at least one MM connection is active (i.e. the mobile station's MM sublayer is either in state 6 "MM CONNECTION ACTIVE" or state 20 "WAIT FOR ADDITIONAL OUTGOING MM CONNECTION"). NOTE: During a re-establishment attempt the mobile station does not return to the MM IDLE state; thus no location updating is performed even if the mobile is not updated in the location area of the selected cell. No call re-establishment shall be performed for voice group and broadcast calls. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.1.6 |
5,681 | 8.10.1.1.6 Dual-Layer Spatial Multiplexing (User-Specific Reference Symbols) | For dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.10.1.1.6-2, with the addition of the parameters in Table 8.10.1.1.6-1 where Cell 1 is the serving cell and Cell 2 is the interfering cell. The downlink physical channel setup is set according to Annex C.3.2. The purpose of these tests is to verify the rank-2 performance for full RB allocation, to verify rate matching with multiple CSI reference symbol configurations with non-zero and zero transmission power, and to verify that the UE correctly estimate SNR. Table 8.10.1.1.6-1: Test Parameters for Testing CDM-multiplexed DM RS (dual layer) with multiple CSI-RS configurations with 4 RX Antenna Ports Table 8.10.1.1.6-2: Minimum performance for CDM-multiplexed DM RS (FRC) with multiple CSI-RS configurations and 4 RX 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.1.1.6 |
5,682 | 5.3.5.3 Reception of an RRCReconfiguration by the UE | The UE shall perform the following actions upon reception of the RRCReconfiguration, upon execution of the conditional reconfiguration (CHO, CPA or CPC), or upon execution of an LTM cell switch: 1> if the RRCReconfiguration is applied due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3: 2> remove all the entries within the MCG and the SCG VarConditionalReconfig, if any; 1> if the RRCReconfiguration includes the daps-SourceRelease: 2> reset the source MAC and release the source MAC configuration; 2> for each DAPS bearer: 3> release the RLC entity or entities as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4], clause 5.1.3, and the associated logical channel for the source SpCell; 3> reconfigure the PDCP entity to release DAPS as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 2> for each SRB: 3> release the PDCP entity for the source SpCell; 3> release the RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4], clause 5.1.3, and the associated logical channel for the source SpCell; 2> release the physical channel configuration for the source SpCell; 2> discard the keys used in the source SpCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key), if any; 1> if the RRCReconfiguration is received via other RAT (i.e., inter-RAT handover to NR): 2> if the RRCReconfiguration does not include the fullConfig and the UE is connected to 5GC (i.e., delta signalling during intra 5GC handover): 3> re-use the source RAT SDAP and PDCP configurations if available (i.e., current SDAP/PDCP configurations for all RBs from source E-UTRA RAT prior to the reception of the inter-RAT HO RRCReconfiguration message); 1> else: 2> if the RRCReconfiguration includes the fullConfig: 3> perform the full configuration procedure as specified in 5.3.5.11; 1> if the RRCReconfiguration includes the masterCellGroup: 2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5; 1> if the RRCReconfiguration includes the masterKeyUpdate: 2> perform AS security key update procedure as specified in 5.3.5.7; 1> if the RRCReconfiguration includes the sk-Counter: 2> perform security key update procedure as specified in 5.3.5.7; 1> if the RRCReconfiguration includes the secondaryCellGroup: 2> perform the cell group configuration for the SCG according to 5.3.5.5; 1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig: 2> if the mrdc-SecondaryCellGroupConfig is set to setup: 3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd: 4> perform MR-DC release as specified in clause 5.3.5.10; 3> if the received mrdc-SecondaryCellGroup is set to nr-SCG: 4> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG; 3> if the received mrdc-SecondaryCellGroup is set to eutra-SCG: 4> perform the RRC connection reconfiguration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.5.3 for the RRCConnectionReconfiguration message included in eutra-SCG; 2> else (mrdc-SecondaryCellGroupConfig is set to release): 3> perform MR-DC release as specified in clause 5.3.5.10; 1> if the RRCReconfiguration message includes the radioBearerConfig: 2> perform the radio bearer configuration according to 5.3.5.6; 1> if the RRCReconfiguration message includes the radioBearerConfig2: 2> perform the radio bearer configuration according to 5.3.5.6; 1> if the RRCReconfiguration message includes the measConfig: 2> perform the measurement configuration procedure as specified in 5.5.2; 1> if the RRCReconfiguration message includes the dedicatedNAS-MessageList: 2> forward each element of the dedicatedNAS-MessageList to upper layers in the same order as listed; 1> if the RRCReconfiguration message includes the dedicatedSIB1-Delivery: 2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2; NOTE 0: If this RRCReconfiguration is associated to the MCG and includes reconfigurationWithSync in spCellConfig and dedicatedSIB1-Delivery, the UE initiates (if needed) the request to acquire required SIBs, according to clause 5.2.2.3.5, only after the random access procedure or the LTM cell switch execution towards the target SpCell is completed. 1> if the RRCReconfiguration message includes the dedicatedSystemInformationDelivery: 2> perform the action upon reception of System Information as specified in 5.2.2.4; 2> if all the SIB(s) and/or posSIB(s) requested in DedicatedSIBRequest message have been acquired: 3> stop timer T350, if running; 1> if the RRCReconfiguration message includes the dedicatedPosSysInfoDelivery: 2> perform the action upon reception of the contained posSIB(s), as specified in clause 5.2.2.4.16; 2> if all the SIB(s) and/or posSIB(s) requested in DedicatedSIBRequest message have been acquired: 3> stop timer T350, if running; 1> if the RRCReconfiguration message includes the otherConfig: 2> perform the other configuration procedure as specified in 5.3.5.9; 1> if the RRCReconfiguration message includes the bap-Config: 2> perform the BAP configuration procedure as specified in 5.3.5.12; 1> if the RRCReconfiguration message includes the iab-IP-AddressConfigurationList: 2> if iab-IP-AddressToReleaseList is included: 3> perform release of IP address as specified in 5.3.5.12a.1.1; 2> if iab-IP-AddressToAddModList is included: 3> perform IAB IP address addition/update as specified in 5.3.5.12a.1.2; 1> if the RRCReconfiguration message includes the conditionalReconfiguration: 2> perform conditional reconfiguration as specified in 5.3.5.13; 1> if the RRCReconfiguration message includes the needForGapsConfigNR: 2> if needForGapsConfigNR is set to setup: 3> consider itself to be configured to provide the measurement gap requirement information of NR target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap requirement information of NR target bands; 1> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR: 2> if needForGapNCSG-ConfigNR is set to setup: 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of NR target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of NR target bands; 1> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA: 2> if needForGapNCSG-ConfigEUTRA is set to setup: 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; 1> if the RRCReconfiguration message includes the onDemandSIB-Request: 2> if onDemandSIB-Request is set to setup: 3> consider itself to be configured to request SIB(s) or posSIB(s) in RRC_CONNECTED in accordance with clause 5.2.2.3.5; 2> else: 3> consider itself not to be configured to request SIB(s) or posSIB(s) in RRC_CONNECTED in accordance with clause 5.2.2.3.5; 3> stop timer T350, if running; 1> if the RRCReconfiguration message includes the sl-ConfigDedicatedNR: 2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14; NOTE 0a: If the sl-ConfigDedicatedNR was received embedded within an E-UTRA RRCConnectionReconfiguration message, the UE does not build an NR RRCReconfigurationComplete message for the received sl-ConfigDedicatedNR. 1> if the RRCReconfiguration message includes the sl-L2RelayUE-Config: 2> perform the L2 U2N or U2U Relay UE configuration procedure as specified in 5.3.5.15; 1> if the RRCReconfiguration message includes the sl-L2RemoteUE-Config: 2> perform the L2 U2N or U2U Remote UE configuration procedure as specified in 5.3.5.16; 1> if the RRCReconfiguration message includes the dedicatedPagingDelivery: 2> perform the Paging message reception procedure as specified in 5.3.2.3; 1> if the RRCReconfiguration message includes the sl-ConfigDedicatedEUTRA-Info: 2> perform related procedures for V2X sidelink communication in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.10 and clause 5.5.2; 1> if the RRCReconfiguration message includes the ul-GapFR2-Config: 2> perform the FR2 UL gap configuration procedure as specified in 5.3.5.13c; 1> if the RRCReconfiguration message includes the musim-GapConfig: 2> perform the MUSIM gap configuration procedure as specified in 5.3.5.9a; 1> if idleInactiveReportAllowed is not included in the RRCReconfiguration message: 2> for each application layer measurement configuration with configforRRC-IdleInactive set to true: 3> forward the measConfigAppLayerId and inform upper layers about the release of the application layer measurement configuration; 3> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; 3> if stored, release the application layer measurement configuration in UE variables VarAppLayerIdleConfig and VarAppLayerPLMN-ListConfig; 3> consider itself not to be configured to send application layer measurement report for the measConfigAppLayerId; 1> if the RRCReconfiguration message includes the appLayerMeasConfig: 2> perform the application layer measurement configuration procedure as specified in 5.3.5.13d; 1> if the RRCReconfiguration message includes the ue-TxTEG-RequestUL-TDOA-Config: 2> if ue-TxTEG-RequestUL-TDOA-Config is set to setup: 3> perform the UE positioning assistance information procedure as specified in 5.7.14; 2> else: 3> release the configuration of UE positioning assistance information; 1> if the RRCReconfiguration message includes the uav-Config: 2> (re)configure the UAV parameters in accordance with the included uav-Config; 1> if the RRCReconfiguration message includes the sl-IndirectPathAddChange: 2> perform the SL indirect path specific configuration procedure as specified in 5.3.5.17.2.2; 1> if the RRCReconfiguration message includes the n3c-IndirectPathAddChange: 2> perform configuration procedure for the remote UE part of N3C indirect path as specified in 5.3.5.17.3.2; 1> if the RRCReconfiguration message includes the n3c-IndirectPathConfigRelay: 2> perform the configuration procedure for the relay UE part of N3C indirect path as specified in 5.3.5.17.3.3; 1> if the RRCReconfiguration message includes the ltm-Config: 2> if the ltm-Config is set to setup: 3> perform the LTM configuration procedure as specified in 5.3.5.18.1; 2> else: 3> perform the LTM configuration release procedure as specified in clause 5.3.5.18.7; 1> set the content of the RRCReconfigurationComplete message as follows: 2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrent: 3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL; 3> include uplinkDirectCurrentBWP-SUL for each MCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList; 2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier: 3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG; 2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentMoreCarrier: 3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG; 2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrent: 3> include the uplinkTxDirectCurrentList for each SCG serving cell with UL; 3> include uplinkDirectCurrentBWP-SUL for each SCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList; 2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier: 3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG; 2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrentMoreCarrier: 3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG; NOTE 0b: The UE does not expect that the reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier is received in both masterCellGroup and in secondaryCellGroup. Network only configures at most one of reportUplinkTxDirectCurrent, reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier in one RRC message. 2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to eutra-SCG: 3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.3.5.3; 2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG: 3> include in the nr-SCG-Response the SCG RRCReconfigurationComplete message; 3> if the RRCReconfiguration message is applied due to conditional reconfiguration execution and the RRCReconfiguration message does not include the reconfigurationWithSync in the masterCellGroup: 4> include in the selectedCondRRCReconfig the condReconfigId for the selected cell of conditional reconfiguration execution; 4> if a new sk-Counter value has been selected due to the conditional reconfiguration execution for subsequent CPAC: 5> include selectedSK-Counter and set its value to the selected sk-Counter value; 3> if the RRCReconfiguration message is applied due to conditional reconfiguration execution and condExecutionCondPSCell is configured for the selected PSCell: 4> include in the selectedPSCellForCHO-WithSCG and set it to the information of the selected PSCell; 2> if the RRCReconfiguration includes the reconfigurationWithSync in spCellConfig of an MCG: 3> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; or 3> if the UE has logged measurements available for NR and if the current registered SNPN is included in snpn-ConfigIDList stored in the VarLogMeasReport: 4> include the logMeasAvailable in the RRCReconfigurationComplete message; 4> if Bluetooth measurement results are included in the logged measurements the UE has available for NR: 5> include the logMeasAvailableBT in the RRCReconfigurationComplete message; 4> if WLAN measurement results are included in the logged measurements the UE has available for NR: 5> include the logMeasAvailableWLAN in the RRCReconfigurationComplete message; 3> if the sigLoggedMeasType in VarLogMeasReport is included; or 3> if the UE is capable of reporting availability of signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the sigLoggedMeasType in VarLogMeasReport of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] is included: 4> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE): 5> set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message; 4> else: 5> if the UE has logged measurements: 6> set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message; 3> if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList; or 3> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the registered SNPN identity is equal to snpn-identity stored in VarConnEstFailReport or any entry of VarConnEstFailReportList: 4> include connEstFailInfoAvailable in the RRCReconfigurationComplete message; 3> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report; or 3> if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; or 3> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the current registered SNPN is included in snpn-IdentityList stored in VarRLF-Report: 4> include rlf-InfoAvailable in the RRCReconfigurationComplete message; 3> if the UE was configured with successHO-Config when connected to the source PCell; and 3> if the applied RRCReconfiguration is not due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3: 4> perform the actions for the successful handover report determination as specified in clause 5.7.10.6, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the MCG; 3> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report; or 3> if the UE has successful handover information available in VarSuccessHO-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessHO-Report: 4> include successHO-InfoAvailable in the RRCReconfigurationComplete message; 3> if the UE supports logging the successful PSCell change or addition information, release successPSCell-Config configured by the source PCell, if available; 3> if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessPSCell-Report; or 3> if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessPSCell-Report: 4> include successPSCell-InfoAvailable in the RRCReconfigurationComplete message; 2> if the RRCReconfiguration message was received via SRB1, but not within mrdc-SecondaryCellGroup or E-UTRA RRCConnectionReconfiguration or E-UTRA RRCConnectionResume: 3> if the UE is configured to provide the measurement gap requirement information of NR target bands: 4> if the RRCReconfiguration message includes the needForGapsConfigNR; or 4> if the NeedForGapsInfoNR information is changed compared to last time the UE reported this information; or 4> if the RRCReconfiguration message includes the needForInterruptionConfigNR and set it to enabled; or 4> if the needForInterruptionConfigNR is enabled and the NeedForInterruptionInfoNR information is changed compared to last time the UE reported this information: 5> include the NeedForGapsInfoNR and set the contents as follows: 6> include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell; 6> if requestedTargetBandFilterNR is configured: 7> for each supported NR band that is also included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band; 6> else: 7> include an entry in interFreq-needForGap and set the corresponding gap requirement information for each supported NR band; 5> if the needForInterruptionConfigNR is enabled: 6> include the needForInterruptionInfoNR and set the contents as follows: 7> include intraFreq-needForInterruption with the same number of entries, and listed in the same order, as in intraFreq-needForGap; 7> for each entry in intraFreq-needForInterruption, include interruptionIndication and set the interruption requirement information if the corresponding entry in intraFreq-needForGap is set to no-gap; 7> include interFreq-needForInterruption with the same number of entries, and listed in the same order, as in interFreq-needForGap; 7> for each entry in interFreq-needForInterruption, include interruptionIndication and set the interruption requirement information if the corresponding entry in interFreq-needForGap is set to no-gap; 3> if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands: 4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR; or 4> if the needForGapNCSG-InfoNR information is changed compared to last time the UE reported this information: 5> include the NeedForGapNCSG-InfoNR and set the contents as follows: 6> include intraFreq-needForNCSG and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell; 6> if requestedTargetBandFilterNCSG-NR is configured: 7> for each supported NR band included in requestedTargetBandFilterNCSG-NR, include an entry in interFreq-needForNCSG and set the NCSG requirement information for that band; 6> else: 7> include an entry for each supported NR band in interFreq-needForNCSG and set the corresponding NCSG requirement information; 3> if the UE is configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands: 4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA; or 4> if the needForGapNCSG-InfoEUTRA information is changed compared to last time the UE reported this information: 5> include the NeedForGapNCSG-InfoEUTRA and set the contents as follows: 6> if requestedTargetBandFilterNCSG-EUTRA is configured, for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA, include an entry in needForNCSG-EUTRA and set the NCSG requirement information for that band; otherwise, include an entry for each supported E-UTRA band in needForNCSG-EUTRA and set the corresponding NCSG requirement information; 2> if the UE has flight path information available: 3> if the UE had not previously provided a flight path information since last entering RRC_CONNECTED state; or 3> if at least one waypoint was not previously provided; or 3> if at least one upcoming waypoint that was previously provided is being removed; or 3> if flightPathUpdateDistanceThr is configured and for at least one waypoint, the 3D distance between the previously provided location and the new location is more than or equal to the distance threshold configured by flightPathUpdateDistanceThr; or 3> if flightPathUpdateTimeThr is configured and for at least one waypoint, the timestamp was not previously provided but is now available, or the time between the previously provided timestamp and the new timestamp, if available, is more than or equal to the time threshold configured by flightPathUpdateTimeThr: 4> include flightPathInfoAvailable; NOTE 0c: If neither flightPathUpdateDistanceThr nor flightPathUpdateTimeThr is configured, it is up to UE implementation whether to include flightPathInfoAvailable when updated flight path information is available. 1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (UE in (NG)EN-DC): 2> if the RRCReconfiguration message was received via E-UTRA SRB1 as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; or 2> if the RRCReconfiguration message was received via E-UTRA RRC message RRCConnectionReconfiguration within MobilityFromNRCommand (handover from NR standalone to (NG)EN-DC); 3> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr-SecondaryCellGroupConfig specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]: 4> submit the RRCReconfigurationComplete message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.6.2a. 3> else if the RRCReconfiguration message was included in E-UTRA RRCConnectionResume message: 4> submit the RRCReconfigurationComplete message via E-UTRA embedded in E-UTRA RRC message RRCConnectionResumeComplete as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.3.4a; 3> else: 4> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.5.3/5.3.5.4/5.4.2.3; 3> if the scg-State is not included in the E-UTRA message (RRCConnectionReconfiguration or RRCConnectionResume) containing the RRCReconfiguration message: 4> perform SCG activation as specified in 5.3.5.13a; 4> if reconfigurationWithSync was included in spCellConfig of an SCG: 5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 4> else if the SCG was deactivated before the reception of the E-UTRA RRC message containing the RRCReconfiguration message: 5> if bfd-and-RLM was not configured to true before the reception of the E-UTRA RRCConnectionReconfiguration or RRCConnectionResume message containing the RRCReconfiguration message or if lower layers indicate that a Random Access procedure is needed for SCG activation: 6> initiate the Random Access procedure on the SpCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 5> else the procedure ends; 4> else the procedure ends; 3> else: 4> perform SCG deactivation as specified in 5.3.5.13b; 4> the procedure ends; 2> if the RRCReconfiguration message was received within nr-SecondaryCellGroupConfig in RRCConnectionReconfiguration message received via SRB3 within DLInformationTransferMRDC: 3> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.5.3/5.3.5.4; 3> if the scg-State is not included in the RRCConnectionReconfiguration: 4> if reconfigurationWithSync was included in spCellConfig of an SCG: 5> initiate the Random Access procedure on the SpCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 4> else the procedure ends; 3> else: 4> perform SCG deactivation as specified in 5.3.5.13b; 4> the procedure ends; NOTE 1: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation. 2> else (RRCReconfiguration was received via SRB3) but not within DLInformationTransferMRDC: 3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration; NOTE 2: In (NG)EN-DC and NR-DC, in the case RRCReconfiguration is received via SRB1 or within DLInformationTransferMRDC via SRB3, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3 but not within DLInformationTransferMRDC, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete. 1> else if the RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration or RRCResume via SRB1): 2> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr-SCG within mrdc-SecondaryCellGroup; or 2> if the RRCReconfiguration is applied due to an LTM cell switch execution: 3> submit the RRCReconfigurationComplete message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3. 2> if the scg-State is not included in the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message: 3> perform SCG activation as specified in 5.3.5.13a; 3> if reconfigurationWithSync was included in spCellConfig in nr-SCG: 4> if the RRCReconfiguration message is not applied due to an LTM cell switch execution for which lower layer indicate to skip the Random Access procedure: 5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 4> if the UE was configured with successPSCell-Config when connected to the source PSCell (for PSCell change) or to the PCell (for PSCell addition or change): 5> perform the actions for the successful PSCell change or addition report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the SCG; 3> else if the SCG was deactivated before the reception of the NR RRC message containing the RRCReconfiguration message: 4> if bfd-and-RLM was not configured to true before the reception of the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message; or 4> if lower layers indicate that a Random Access procedure is needed for SCG activation: 5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 4> else the procedure ends; 3> else the procedure ends; 2> else 3> perform SCG deactivation as specified in 5.3.5.13b; 3> the procedure ends; NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation. 1> else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC): 2> if the RRCReconfiguration message was received within DLInformationTransferMRDC: 3> if the RRCReconfiguration message was received within the nr-SCG within mrdc-SecondaryCellGroup (NR SCG RRC Reconfiguration): 4> if the scg-State is not included in the RRCReconfiguration message containing the RRCReconfiguration message: 5> if reconfigurationWithSync was included in spCellConfig in nr-SCG: 6> initiate the Random Access procedure on the PSCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 6> if the UE was configured with successPSCell-Config by the PCell or by the source PSCell: 7> perform the actions for the successful PSCell change report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the SCG; 5> else: 6> the procedure ends; 4> else: 5> perform SCG deactivation as specified in 5.3.5.13b; 5> the procedure ends; 3> else: 4> if the RRCReconfiguration does not include the mrdc-SecondaryCellGroupConfig: 5> if the RRCReconfiguration includes the scg-State: 6> perform SCG deactivation as specified in 5.3.5.13b; 4> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration; 2> else: 3> if the RRCReconfiguration includes the reconfigurationWithSync in spCellConfig for the SCG; and 3> if the UE was configured with successPSCell-Config: 4> perform the actions for the successful PSCell change report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the SCG; 3> if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessPSCell-Report; or 3> if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessPSCell-Report: 4> include successPSCell-InfoAvailable in the RRCReconfigurationComplete message; 3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration; 1> else (RRCReconfiguration was received via SRB1): 2> if the UE is in NR-DC and; 2> if the RRCReconfiguration does not include the mrdc-SecondaryCellGroupConfig: 3> if the RRCReconfiguration includes the scg-State: 4> perform SCG deactivation as specified in 5.3.5.13b; 3> else: 4> perform SCG activation without SN message as specified in 5.3.5.13b1; 2> if the reconfigurationWithSync was included in spCellConfig of an MCG: 3> if ta-Report or ta-ReportATG is configured with value enabled and the UE supports TA reporting: 4> indicate TA report initiation to lower layers; 2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration; 2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment procedure: 3> resume SRB2, SRB4, DRBs, multicast MRB, and BH RLC channels for IAB-MT, and Uu Relay RLC channels for L2 U2N Relay UE, that are suspended; 1> if sl-IndirectPathAddChange was included in RRCReconfiguration message and if SRB1 is configured as split SRB and pdcp-Duplication is configured: 2> when successfully sending RRCReconfigurationComplete message via SL indirect path (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE): 3> stop timer T421; 1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and when MAC of an NR cell group successfully completes a Random Access procedure triggered above; or, 1> if sl-PathSwitchConfig was included in reconfigurationWithSync included in spCellConfig of an MCG, and when successfully sending RRCReconfigurationComplete message (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE); or, 1> if rach-LessHO was included in reconfigurationWithSync included in spCellConfig of an MCG, and upon indication from lower layers that the RACH-less handover has been successfully completed; or, 1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and the RRCReconfiguration message is applied due to an LTM cell switch execution and upon an indication from lower layer that the LTM cell switch execution has been successfully completed: 2> stop timer T304 for that cell group if running; 2> if sl-PathSwitchConfig was included in reconfigurationWithSync: 3> stop timer T420; 3> release all radio resources, including release of the RLC entities and the MAC configuration at the source side; 3> reset MAC used in the source cell; 2> if rach-LessHO was included in reconfigurationWithSync and cg-NTN-RACH-Less-Configuration was configured: 3> release the uplink grant configured for RACH-less handover in cg-NTN-RACH-Less-Configuration; NOTE 2b: PDCP and SDAP configured by the source prior to the path switch that are reconfigured and re-used by target when delta signalling is used, are not released as part of this procedure. 2> stop timer T310 for source SpCell if running; 2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any; 2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell; 2> for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 2> if the reconfigurationWithSync was included in spCellConfig of an MCG: 3> if T390 is running: 4> stop timer T390 for all access categories; 4> perform the actions as specified in 5.3.14.4. 3> if T350 is running: 4> stop timer T350; 3> if RRCReconfiguration does not include dedicatedSIB1-Delivery and 3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIB1: 4> acquire the SIB1, which is scheduled as specified in TS 38.213[ NR; Physical layer procedures for control ] [13], of the target SpCell of the MCG; 4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2; 2> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution and the subsequentCondReconfig is included in the entry in VarConditionalReconfig containing the RRCReconfiguration message: 3> for each condReconfigId included in condExecutionCondToAddModList within subsequentCondReconfig: 4> replace within VarConditionalReconfig the entry in condExecutionCond or condExecutionCondSCG with the matching condReconfigId value; 2> if the reconfigurationWithSync was included in spCellConfig of an MCG; or 2> if the reconfigurationWithSync was included in spCellConfig of an SCG and the CPA, CPC, or subsequent CPAC was configured: 3> remove all the entries in the condReconfigList within the MCG and the SCG VarConditionalReconfig except for the entries in which subsequentCondReconfig is present, if any; 3> remove all the entries within VarConditionalReconfiguration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.5.9.6, if any; 3> for each measId of the MCG measConfig, if configured, and for each measId of the SCG measConfig, if configured, if the associated reportConfig has a reportType set to condTriggerConfig: 4> if the reportConfigId is not associated with any measId indicated by the condExecutionCond or the condExecutionCondSCG in an entry of condReconfigList in VarConditionalReconfig in which subsequentCondReconfig is included: 5> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig; 4> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig; and 4> if the measObjectId is not associated with any measId indicated by the condExecutionCond or the condExecutionCondSCG in an entry of condReconfigList in VarConditionalReconfig in which subsequentCondReconfig is included: 5> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig; 4> remove the entry with the matching measId from the measIdList within the VarMeasConfig; 2> if reconfigurationWithSync was included in masterCellGroup or secondaryCellGroup: 3> if the UE initiated transmission of a UEAssistanceInformation message for the corresponding cell group during the last 1 second, and the UE is still configured to provide the concerned UE assistance information for the corresponding cell group; or 3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution or an LTM cell switch procedure, and the UE is configured to provide UE assistance information for the corresponding cell group, and the UE has initiated transmission of a UEAssistanceInformation message for the corresponding cell group since it was configured to do so in accordance with 5.7.4.2: 4> initiate transmission of a UEAssistanceInformation message for the corresponding cell group in accordance with clause 5.7.4.3 to provide the concerned UE assistance information; 4> start or restart the prohibit timer (if exists) or the leave without response timer for the MUSIM associated with the concerned UE assistance information with the timer value set to the value in corresponding configuration; 3> if SIB12 is provided by the target PCell, and the UE initiated transmission of a SidelinkUEInformationNR message indicating a change of NR sidelink communication/discovery related parameters relevant in target PCell (i.e. change of sl-RxInterestedFreqList or sl-TxResourceReqList) during the last 1 second preceding reception of the RRCReconfiguration message including reconfigurationWithSync in spCellConfig of an MCG; or 3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution and the UE is capable of NR sidelink communication/discovery and SIB12 is provided by the target PCell, and the UE has initiated transmission of a SidelinkUEInformationNR message since it was configured to do so in accordance with 5.8.3.2: 4> initiate transmission of the SidelinkUEInformationNR message in accordance with 5.8.3.3; 2> if reconfigurationWithSync was included in masterCellGroup: 3> if configured with application layer measurements and if application layer measurement report container has been received from upper layers for which the successful transmission of the message or at least one segment of the message has not been confirmed by lower layers: 4> re-submit the MeasurementReportAppLayer message or all segments of the MeasurementReportAppLayer message to lower layers for transmission via SRB4; 2> if reconfigurationWithSync was included in masterCellGroup and the target cell provides SIB21: 3> if the UE initiated transmission of an MBSInterestIndication message during the last 1 second preceding reception of this RRCReconfiguration message; or 3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution, and the UE has initiated transmission of an MBSInterestIndication message after having received this RRCReconfiguration message: 4> initiate transmission of an MBSInterestIndication message in accordance with clause 5.9.4; 2> the procedure ends. NOTE 3: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located. NOTE 4: The UE sets the content of UEAssistanceInformation according to latest configuration (i.e. the configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may include more than the concerned UE assistance information within the UEAssistanceInformation according to 5.7.4.2. Therefore, the content of UEAssistanceInformation message might not be the same as the content of the previous UEAssistanceInformation message. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.3 |
5,683 | 5.27.2.5.3 Reactive RAN feedback for Burst Arrival Time adaptation | If the RAN receives the capability for BAT adaptation without a Burst Arrival Time in the TSCAI and notification control is enabled for this QoS Flow, the 5GS will perform the following actions: - If NG-RAN determines that the PDB of the QoS flow cannot be fulfilled in DL and UL direction, then if supported, NG-RAN shall determine a BAT offset value which reduces the time between the arrival of the traffic bursts and the time of the next possible transmission over the air interface for DL and UL, respectively. NG-RAN shall not provide a BAT offset with the same value until the PDB of the QoS Flow can be fulfilled again. NOTE: NG-RAN determines BAT offset value in reference to the current arrival time of the bursts experienced by RAN in DL and by UE in UL. Further details on BAT offset determination for DL and UL will be defined by RAN WG2. - The BAT offset is provided from NG-RAN to the SMF when sending the notification towards the SMF that the "GFBR can no longer be guaranteed" described in clause 5.7.2.4. The SMF provides the BAT offset to the PCF and the PCF provides the BAT offset to the AF as part of notifying the AF as described in clause 6.1.3.23a of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.2.5.3 |
5,684 | 4.11.1.3.2 5GS to EPS Idle mode mobility using N26 interface | In the case of network sharing the UE selects the target PLMN ID according to clause 5.18.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Clause 4.11.1.3.2 covers the case of idle mode mobility from 5GC to EPC. UE performs Tracking Area Update procedure in E-UTRA/EPS when it moves from NG-RAN/5GS to E-UTRA/EPS coverage area. The procedure involves a Tracking Area Update to EPC and setup of default EPS bearer and dedicated bearers in EPC in steps 1-11 and re-activation, if required. Figure 4.11.1.3.2-1: 5GS to EPS Idle mode mobility using N26 interface The TAU procedure in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] is used with the following 5GS interaction: 1. Step 1 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 2. Step 2 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the modification captured in clause 4.11.1.5.3. 3-4. Steps 3-4 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 5a. The AMF verifies the integrity of the TAU request message: The AMF determines for a PDU Session whether to retrieve context including mapped UE EPS connection from V-SMF (in the case of HR roaming) or from the SMF+PGW-C (in the case of non roaming or LBO roaming) as follows: - If the AMF determines that one or more of the EBI(s) can be transferred, the AMF sends Nsmf_PDUSession_ContextRequest to the V-SMF or SMF+PGW-C and includes in the message EBI value(s) if any that cannot be transferred. - The EBI values(s) that cannot be transferred is determined by the AMF if the target MME does not support 15 EPS bearers, i.e. the AMF determines the EBI values in range 1-4 as not to be transferred to EPS and if there are still more than 8 EBI values associated with PDU Sessions, the AMF then determines EBI value(s) not to be transferred to EPS based on S-NSSAI and ARP as specified in clause 5.17.2.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - The AMF does not retrieve the context for a PDU Session that cannot be transferred to EPS due to no EBI allocated, or allocated EBIs not transferrable, or combination of the two. In non-roaming or LBO roaming, the AMF retrieves context that includes the mapped EPS Bearer Contexts. - The AMF provides in Nsmf_PDUSession_ContextRequest the target MME capability to the PGW C+SMF in the request to allow the SMF+PGW-C to determine whether to include EPS Bearer context for Ethernet PDN type or non-IP PDN Type or not. - If the AMF includes in Nsmf_PDUSession_ContextRequest EBI list not to be transferred and if the EBI value of the QoS Flow associated with the default QoS Rule is included in that list, the SMF+PGW-C shall not return the PDN Connection context (which implies the whole PDU Session is not transferred to EPS), otherwise if the EBI value of the QoS Flow associated with the default QoS Rule is not included in the EBI list not to be transferred, the V-SMF or SMF+PGW-C shall not provide the EPS bearer context(s) mapped from QoS Flow(s) associated with that list. - When the AMF sends Nsmf_PDUSession_ContextRequest to the V-SMF or the SMF+PGW-C, the AMF indicates whether the target MME supports User Plane Integrity Protection with EPS. The above steps are performed with all the SMF+PGW-Cs corresponding to PDU Sessions of the UE which are associated with 3GPP access and have EBI(s) allocated to them. In Home Routed roaming, the AMF requests the V-SMF to provide SMF Context by using Nsmf_PDUSession_ContextRequest. NOTE 1: The AMF knows the MME capability to support 15 EPS bearers, support User Plane Integrity Protection with EPS, Ethernet PDN Type and/or non-IP PDN type or not through local configuration. 5b. For Non-roaming or roaming with local breakout scenario, if the CN Tunnel Info for EPS bearer(s) have not been allocated before, the SMF sends N4 Session Modification Request to PGW-U+UPF to establish the tunnel for each EPS bearers and PGW-U+UPF provides the PGW-U Tunnel Info for each EPS bearers to SMF+PGW-C. NOTE 2: In home routed roaming case, the CN Tunnel Info for each EPS bearer has been prepared by the SMF+PGW-C and provided to the V-SMF as specified in clause 4.11.1.4.1. 5c. For PDU Sessions that are anchored a UPF, in non-roaming or roaming with local breakout, the SMF+PGW-C returns mapped EPS bearer contexts, which includes PGW-C control plane tunnel information of the PDN connection corresponding to the PDU session, EBI for each EPS bearer, PGW-U tunnel information for each EPS bearer and EPS QoS parameters for each EPS bearer. For PDU Sessions with PDU Session Type Ethernet, if the UE and target MME supports Ethernet PDN type, the SMF+PGW-C provides SM Context for Ethernet PDN Type, otherwise if the UE or target MME does not support Ethernet Type but support non-IP Type, the SMF+PGW-C provides SM Context for non-IP PDN Type. For PDU Sessions with PDU Session Type Unstructured, the SMF provides SM Context for non-IP PDN Type. In home routed roaming, V-SMF provides the SM Context. If the UP integrity protection policy for the EPS bearer context is set to "Required", the V-SMF or the PGW C+SMF shall not provide the EPS bearer context unless the MME supports User Plane Integrity Protection with EPS and the UE supports User Plane Integrity Protection with EPS. For PDU Sessions that are anchored at an NEF, the SMF returns an SCEF+NEF ID and an EBI for each PDN connection corresponding to a PDU Session. If the SMF+PGW-C has marked that the status of one or more QoS Flows are deleted in the 5GC but not synchronized with the UE yet according to clause 4.3.3.2, the SMF+PGW-C does not return to the AMF the EPS context(s) if all its associated QoS Flows are marked as deleted, that is, the SMF+PGW-C returns to the AMF the EPS bearer contexts mapped from QoS Flows where at least one of the QoS Flow for the EPS bearer is not marked as deleted. 6. The AMF responds with a Context Response message as in step 5 in clause 5.3.3.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] carrying mapped MM context (including mapped security context), Return preferred and SM EPS UE Context (default and dedicated GBR bearers) to the MME. If the verification of the integrity protection fails, the AMF returns an appropriate error cause. Return preferred is an optional indication by the AMF of a preferred return of the UE to the 5GS PLMN at a later access change to a 5GS shared network. The AMF may start an implementation specific (guard) timer for the UE context. From the received context and the Tracking Area indicated by the RAN, the MME can determine whether the UE is performing Inter-RAT mobility to or from NB-IoT. 7 - 14. Steps 6-12 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] are performed with following addition and modification: In the step 10, if the PDU Session (PDN connection) has QoS Flows that do not have EPS bearer ID(s) assigned, the SMF+PGW-C deletes the PCC rule(s) associated with those QoS Flows and informs the PCF about the removed PCC rule(s). If there are QoS Flow(s) with PCC rule(s) that do not have allocated TFT packet filters (due to number exceeding limit), the SMF+PGW-C deletes those PCC rule(s) and informs the PCF about the removed PCC rule(s). In the step 10, if the MME does not indicate support of User Plane integrity protection, or the new eNB does not support User Plane integrity protection, or the UE does not support User Plane Integrity Protection with EPS and the UP integrity protection policy is set to "Required" then the SMF+PGW-C releases the bearers associated with the PDN CONNECTION. In the step 11, the SMF+PGW-C requests the PGW-U+UPF to establish the tunnel for each EPS bearer by providing SGW-U Tunnel Info. In step 10, the SMF+PGW-C may need to report some subscribed event to the PCF by performing an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5. If the mapped EPS bearers are not included in Modify Bearer Request, the SMF+PGW-C deletes the PCC rule(s) associated with the QoS Flows corresponding to those mapped EPS bearers. Step 9a from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the modification captured in clause 4.11.1.5.3 If the SCEF connection is to be established, the steps 9-13 are replaced with the steps 2-3 from clause 5.13.1.2 of TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [23]. The SCEF+NEF ID and the EBI received from the AMF are included in the Create SCEF Connection Request. 15-15c. The HSS+UDM invokes Nudm_UECM_DeregistrationNotification to notify the AMF associated with 3GPP access with reason as 5GS to EPS Mobility. If the timer started in step 6 is not running, the old AMF removes the UE context. Otherwise, the AMF may remove UE context when the timer expires. The AMF requests the release of the PDU Session(s) which is associated with 3GPP access and not expected to be transferred to EPC, i.e. AMF requests the release of: - PDU Session(s) whose corresponding SMF+PGW-C(s) are not contacted by AMF for SM context because the AMF determines that none of EBI(s) for the PDU Session can be transferred to EPS at step 5a; and - PDU Session(s) for which the SM context retrieval failed at step 5c. The AMF requests the release of the SM context in the V-SMF only and the V-SMF releases resource in the V-UPF, for Home Routed PDU Session with EBIs allocated. The 5GC may also keep UE context to allow the use of native security parameters when UE moves back from EPS to 5GS later. If PCC is enabled, the AMF initiates AM Policy Association Termination procedure as defined in clause 4.16.3.2 and UE Policy Association Termination procedure as defined in clause 4.16.13.1. Registration associated with the non-3GPP access in the AMF is not removed (i.e. an AMF that was serving the UE over both 3GPP and non-3GPP accesses does not consider the UE as deregistered over non 3GPP access and will remain registered and subscribed to subscription data updates in UDM). When the UE decides to deregister over non-3GPP access or the old AMF decides not to maintain a UE registration for non-3GPP access anymore, the old AMF then deregisters from UDM by sending a Nudm_UECM_Deregistration service operation, unsubscribes from Subscription Data updates by sending an Nudm_SDM_Unsubscribe service operation to UDM and releases all the AMF and AN resources related to the UE. 16 - 18. Steps 17-21 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the following modification: - The MME may provide the eNodeB with a PLMN list in the Handover Restriction List taking into account the last used 5GS PLMN ID and the Return preferred indication. The Handover Restriction List contains a list of PLMN IDs as specified by clause 5.2a of TS 23.251[ Network sharing; Architecture and functional description ] [35] for eNodeB functions. - The MME may not release the signalling connection with the UE based on the indication received in the step 1 that the UE is moving from 5GC. 19. [conditional] Step 19 from clause 4.11.1.2.1 applies. If some of the QoS Flow(s) for an EPS bearer were marked as deleted, the SMF+PGW-C may initiate bearer modification as specified 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 ] [13] to remove the TFT filter(s) corresponding to the Packet Filter Set(s) in the QoS rules. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.3.2 |
5,685 | 5.8.2.8.3 Redirection | The uplink application's traffic redirection may be enforced either in the SMF (as specified in 5.8.2.5 Control of user plane forwarding) or directly in the UPF. The redirect destination may be provided in the dynamic PCC rule or be preconfigured, either in the SMF or in the UPF. When receiving redirect information (redirection enabled/disabled and redirect destination) within a dynamic PCC rule or being activated/deactivated by the PCF for the predefined redirection policies, SMF shall decide whether to provide and what information to be provided to the UPF based on where the redirection is enforced and where the redirect destination is acquired/preconfigured. When redirection is enforced in the UPF and the redirect destination is acquired from the dynamic PCC rule or is configured in the SMF, SMF shall provide the redirect destination to the UPF. When redirection is enforced in the SMF, SMF shall instruct the UPF to forward applicable user plane traffic to the SMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.8.3 |
5,686 | A.36 Monitor of E-RAB release | E-RAB is the key and limited resource for E-UTRAN to deliver services. The release of the E-RAB needs to be monitored as: - an abnormal release of the E-RAB will cause the call(/session) drop, which directly impacts the QoS delivered by the networks, and the satisfaction degree of the end user; - a successfully released E-RAB can be used to setup other requested calls(/sessions). The E-RAB failed to be released will still occupy the limited resource and hence it can not be used to admit other requested calls(/sessions). From a retainability measurement aspect, E-RABs do not need to be released because they are inactive, they can be kept to give fast access when new data arrives. To define (from an E-RAB release measurement point of view) if an E-RAB is considered active or not, the E-RABs can be divided into two groups: a) Continuous flow, E-RABs that are always considered active, i.e. independent of if there is ongoing traffic or not at the moment. Examples: VoIP sessions, Real-time sessions, Live streaming sessions. b) Bursty flow, E-RABs that are only considered active when there is data in UL/DL buffer. Example: Web sessions. How to decide for a particular QCI if the E-RAB is of type bursty flow or continuous flow is outside the scope of this document. The specific reason causing the abnormal and failed release of the E-RAB is required in order to find out the problem and ascertain the solutions. And due to different priority and tolerance for different service type with different OoS level in the networks, the monitor needs to be opened on each service type with OoS level. The E-RAB can be released by E-RAB Release procedure (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) , UE Context Release procedure (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9] and 3GPP TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) procedure, Reset procedure(See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) either initiated by eNodeB or MM, Path Switch procedure (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) and Intra-eNB HO procedure (See 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8])E. So performance measurements related to E-RAB Release (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) and UE Context Release (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) procedure for each service type with QoS level are necessary to support the monitor of E-RAB release. From quality point of view the E-RAB or UE Context drop ratio of the same values in two different cells may be perceived differently by the end user especially for VoIP services, depending on the duration of the dropped call in comparison to intended call duration when call would not be dropped. For example, having the E-RAB drop ratio of 90% in two cells may be perceived differently by the end user, where in the first cell there was a dropped call which lasted for 99% of intended call duration and in the other cell it lasted only 40%. In the first case, the end user with high probability may not follow up with an additional call request, while in the second it may be the opposite as the main goal of the conversation has not been achieved yet. Therefore, as an extended monitoring especially for VoIP sessions observation of the "Distribution of Normally Released Call (QCI1 E-RAB) Duration" and "Distribution of Abnormally Released Call (QCI1 E-RAB) Duration" is recommended. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.36 |
5,687 | – RLC-BearerConfig | The IE RLC-BearerConfig is used to configure an RLC entity, a corresponding logical channel in MAC and the linking to a PDCP entity (served radio bearer). RLC-BearerConfig information element -- ASN1START -- TAG-RLC-BEARERCONFIG-START RLC-BearerConfig ::= SEQUENCE { logicalChannelIdentity LogicalChannelIdentity, servedRadioBearer CHOICE { srb-Identity SRB-Identity, drb-Identity DRB-Identity } OPTIONAL, -- Cond LCH-SetupOnly reestablishRLC ENUMERATED {true} OPTIONAL, -- Need N rlc-Config RLC-Config OPTIONAL, -- Cond LCH-Setup mac-LogicalChannelConfig LogicalChannelConfig OPTIONAL, -- Cond LCH-Setup ..., [[ rlc-Config-v1610 RLC-Config-v1610 OPTIONAL -- Need R ]], [[ rlc-Config-v1700 RLC-Config-v1700 OPTIONAL, -- Need R logicalChannelIdentityExt-r17 LogicalChannelIdentityExt-r17 OPTIONAL, -- Cond LCH-SetupModMRB multicastRLC-BearerConfig-r17 MulticastRLC-BearerConfig-r17 OPTIONAL, -- Cond LCH-SetupOnlyMRB servedRadioBearerSRB4-r17 SRB-Identity-v1700 OPTIONAL -- Need N ]] } MulticastRLC-BearerConfig-r17 ::= SEQUENCE { servedMBS-RadioBearer-r17 MRB-Identity-r17, isPTM-Entity-r17 ENUMERATED {true} OPTIONAL -- Need S } LogicalChannelIdentityExt-r17 ::= INTEGER (320..65855) -- TAG-RLC-BEARERCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,688 | 5.31.7 Power Saving Enhancements 5.31.7.1 General | To enable UE power saving and to enhance MT reachability while using MICO mode, e.g. for CIoT, the following features are specified in the following clauses: - Extended Discontinuous Reception (DRX) for CM-IDLE and CM-CONNECTED with RRC_INACTIVE; - MICO mode with Extended Connected Time; - MICO mode with Active Time; - MICO mode and Periodic Registration Timer Control. If a UE requests via NAS to enable both MICO mode with Active Time and extended idle mode DRX, e.g. based on local configuration, Expected UE Behaviour, if available, UE requested Active Time value, UE subscription information and network policies etc, the AMF may decide to enable MICO mode with or without Active Time, extended idle mode DRX or both. The functions and procedures to enable a UE using power saving functions to receive MBS service are defined in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [129]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.7 |
5,689 | 13.1 Interference avoidance for in-device coexistence | IDC solution as described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] is extended to address EN-DC/NR-DC operation. For the FDM solution, the list of NR carriers or NR frequency ranges suffering from IDC problems is signalled in IDC report. For the TDM solution, a periodic pattern can be signalled per-CG in IDC report. In EN-DC, the MN can configure the UE to report FDM assistance information with affected carriers. In NR-DC, the MN can configure the UE to report FDM assistance information with affected frequency ranges and/or TDM assistance information. For both EN-DC and NR-DC, the SN can configure the UE to report FDM assistance information with affected frequency ranges and/or TDM assistance information to the SN via SRB1 or SRB3, if SRB3 is configured and the SCG is activated. The network can also configure autonomous denial per-CG for the UE to solve IDC problems. The requirement on RRM/RLM/CSI measurements in different phases of IDC interference defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2] is applicable except that for NR serving cell, the requirements in TS 38.133[ NR; Requirements for support of radio resource management ] [8] and TS 38.101[ None ] -1 [12], TS 38.101[ None ] -2 [13], TS 38.101[ None ] -3 [14] apply. | 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.1 |
5,690 | 5.2.4 Synchronization signal and PBCH block | The Synchronization Signal and PBCH block (SSB) consists of primary and secondary synchronization signals (PSS, SSS), each occupying 1 symbol and 127 subcarriers, and PBCH spanning across 3 OFDM symbols and 240 subcarriers, but on one symbol leaving an unused part in the middle for SSS as show in Figure 5.2.4-1. For the 3 MHz channel bandwidth, the PBCH is further equally punctured from both edges to span 144 subcarriers. The possible time locations of SSBs within a half-frame are determined by sub-carrier spacing and the periodicity of the half-frames where SSBs are transmitted is configured by the network. During a half-frame, different SSBs may be transmitted in different spatial directions (i.e. using different beams, spanning the coverage area of a cell). Within the frequency span of a carrier, multiple SSBs can be transmitted. The PCIs of SSBs transmitted in different frequency locations do not have to be unique, i.e. different SSBs in the frequency domain can have different PCIs. However, when an SSB is associated with an RMSI, the SSB is referred to as a Cell-Defining SSB (CD-SSB). A PCell is always associated to a CD-SSB located on the synchronization raster. When an SSB is not associated with an RMSI, the SSB is referred to as a non-Cell Defining SSB (NCD-SSB), which can be used to perform RLM, BFD, and RRM measurements and measurements for RA resource selection inside the active DL BWP when the active BWP does not contain the CD-SSB. A UE may be configured with multiple SSBs provided that each BWP is configured with at most one SSB (CD-SSB or NCD-SSB). Figure 5.2.4-1: Time-frequency structure of SSB Polar coding is used for PBCH. The UE may assume a band-specific sub-carrier spacing for the SSB unless a network has configured the UE to assume a different sub-carrier spacing. PBCH symbols carry its own frequency-multiplexed DMRS. QPSK modulation is used for PBCH. The PBCH physical layer model is described in TS 38.202[ NR; Services provided by the physical layer ] [20]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.4 |
5,691 | I.2.4 Requirements for handling control plane data | An RNC in an exposed location has to provide confidentiality and integrity protection for control plane packets on the Iu and Iur reference points. 1. Control plane data ciphering/deciphering and integrity handling shall take place inside the secure environment where the related keys are stored. 2. The transport of control plane data over Iu and Iur shall be integrity-, confidentiality- and replay-protected from unauthorized parties. If this is to be accomplished by cryptographic means, Annex I.3 shall be applied. NOTE: Protection for signalling data that is sent from or to the UE extends between the UE and the serving RNC, cf. the NOTE in Annex I.2.3. This protection does not, however, cover the signalling data exchanged between RNCs over Iur; hence a separate requirement is needed for Iur. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | I.2.4 |
5,692 | 9.4.15 Routing area update accept | This message is sent by the network to the MS to provide the MS with GPRS mobility management related data in response to a routing area update request message. See table 9.4.15/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: routing area update accept Significance: dual Direction: network to MS Table 9.4.15/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : ROUTING AREA UPDATE ACCEPT message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.4.15 |
5,693 | 6.15.2.1 Procedure for UE Parameters Update | The UDM may decide to perform UE parameters update anytime after the UE has been successfully authenticated and registered to the 5G system. The security procedure for the UE parameters update is described below in figure 6.15.2.1-1: Figure 6.15.2.1-1: Procedure for UE Parameters Update 1) The UDM decides to perform the UE Parameters Update (UPU) using the control plane procedure while the UE is registered to the 5G system. If the final consumer of any of the UE parameters to be updated (e.g., the updated Routing ID Data) is the USIM, the UDM shall protect these parameters using a secured packet mechanism (see 3GPP TS 31.115[ Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications ] [65]) to update the parameters stored on the USIM. The UDM shall then prepare the UE Parameters Update Data (UPU Data) by including the parameters protected by the secured packet, if any, as well as any UE parameters for which final consumer is the ME (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]). 2-3) The UDM shall invoke Nausf_UPUProtection service operation message by including the UPU Data to the AUSF to get UPU-MAC-IAUSF and CounterUPU as specified in sub-clause 14.1.4 of this document. The UDM shall select the AUSF that holds the latest KAUSF of the UE. If the UDM decided that the UE is to acknowledge the successful security check of the received UE Parameters Update Data, then the UDM shall include the ACK Indication in the Nausf_UPUProtection service operation message to signal that it also needs the expected UPU-XMAC-IUE, as specified in sub-clause 14.1.4 of this document. The details of the CounterUPU is specified in sub-clause 6.15.2.2 of this document. The inclusion of UE Parameters Update Data in the calculation of UPU-MAC-IAUSF allows the UE to verify that it has not been tampered by any intermediary. The expected UPU-XMAC-IUE allows the UDM to verify that the UE received the UE Parameters Update Data correctly. 4) The UDM shall invoke Nudm_SDM_Notification service operation, which includes the UPU transparent container if the AMF supports UPU transparent container, or includes individual IEs comprising the UE Parameters Update Data, UPU-MAC-IAUSF, CounterUPU within the Access and Mobility Subscription data. If the UDM requests an acknowledgement, it shall temporarily store the expected UPU-XMAC-IUE. 5) Upon receiving the Nudm_SDM_Notification message, the AMF shall send a DL NAS Transport message to the served UE. The AMF shall include in the DL NAS Transport message the transparent container if received from the UDM in step 4. Otherwise, if the UDM provided individual IEs in step 4, then the AMF shall construct a UPU transparent container. 6) On receiving the DL NAS Transport message, the UE shall calculate the UPU-MAC-IAUSF in the same way as the AUSF (as specified in Annex A.19) on the received UE Parameters Update Data and the CounterUPU and verify whether it matches the UPU-MAC-IAUSF value received within the UPU transparent container in the DL NAS Transport message. If the verification of UPU-MAC-IAUSF is successful and the UPU Data contains any parameters that is protected by secured packet (see 3GPP TS 31.115[ Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications ] [65]), the ME shall forward the secured packet to the USIM using procedures in 3GPP TS 31.111[ Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) ] [66]. If the verification of UPU-MAC-IAUSF is successful and the UPU Data contains any parameters that is not protected by secure packet, the ME shall update its stored parameters with the received parameters in UDM Updata Data. 7) If the UDM has requested an acknowledgement from the UE and the UE has successfully verified and updated the UE Parameters Update Data provided by the UDM, then the UE shall send the UL NAS Transport message to the serving AMF. The UE shall generate the UPU-MAC-IUE as specified in Annex A.20 and include the generated UPU-MAC-IUE in a transparent container in the UL NAS Transport message. 8) If a transparent container with the UPU-MAC-IUE was received in the UL NAS Transport message, the AMF shall send a Nudm_SDM_Info request message with the transparent container to the UDM. 9) If the UDM indicated that the UE is to acknowledge the successful security check of the received UE Parameters Update Data, then the UDM shall compare the received UPU-MAC-IUE with the expected UPU-XMAC-IUE that the UDM stored temporarily in step 4. If the UDM supports Home triggered authentication (see clause 6.1.5), the UDM based on its local policy may decide to trigger a primary authentication to refresh the UPU counter based on the value of counter received in step 3. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.15.2.1 |
5,694 | 5.31.11 Inter-RAT idle mode mobility to and from NB-IoT | Tracking Areas are configured so that they do not contain both NB-IoT and other RATs' cells, so when the UE is changing RAT type to or from NB-IoT while remaining registered with 5GC, the UE will perform the Mobility Registration Update procedure, see clause 5.3.2.3. When the UE is changing RAT type to or from NB-IoT and moving between 5GC and EPC, during the Registration, Attach or TAU procedure the RAT type change is determined. The specification in this clause does not apply to RAT type corresponding to Non-3GPP Access type. PDU session handling is controlled by "PDU Session continuity at inter RAT mobility" in the UE's subscription data, which indicates per DNN/S-NSSAI whether to; - maintain the PDU session, - disconnect the PDU session with a reactivation request, - disconnect the PDU session without reactivation request, or - leave it up to local VPLMN policy when the UE moves between a "broadband" RAT (e.g. NR or WB-E-UTRA) and a "narrowband" RAT (NB-IoT). During PDU session establishment the SMF retrieves the "PDU Session continuity at inter RAT mobility" subscription information (if available) from the UDM. Local SMF configuration is used if "PDU Session continuity at inter RAT mobility" is not available for a PDU Session. The AMF informs the SMF at an inter-RAT idle mobility event, e.g. to or from NB-IoT connected to 5GC about the RAT type change in the Nsmf_PDUSession_UpdateSMContext message during the Registration procedure. Based on this (H-)SMF handles the PDU session according to "PDU session continuity at inter RAT mobility information" subscription data or based on local policy. NOTE: The "PDU Session continuity at inter RAT mobility" and "PDN continuity at inter-RAT mobility" subscription should be the same so that the PDU sessions/PDN connections are handled the same by both CN types. During inter-RAT idle mode mobility to NB-IoT, if a PDU session has more than one QoS rule, the SMF shall initiate a PDU session modification procedure as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3] to remove any non-default QoS rule, and maintain only the default QoS rule. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.11 |
5,695 | 5.3.1.3 Suspend and resume of the NAS signalling connection | Suspend of the NAS signalling connection can be initiated by the network in EMM-CONNECTED mode when user plane CIoT EPS optimization is used. Resume of the suspended NAS signalling connection is initiated by the UE. In the UE, when user plane CIoT EPS optimization is used: - Upon indication from the lower layers that the RRC connection has been suspended, the UE shall enter EMM-IDLE mode with suspend indication, shall not consider the NAS signalling connection released and shall not consider the secure exchange of NAS messages terminated (see clause 4.4.2.3 and 4.4.5). Based on further indications provided by the lower layers, the UE shall update the status of the suspend indication for the EMM-IDLE mode; - Upon trigger of a procedure using an initial NAS message when in EMM-IDLE mode with suspend indication, the UE shall: i) if the initial NAS message is a TRACKING AREA UPDATE REQUEST message which includes a UE radio capability information update needed IE, enter EMM-IDLE mode without suspend indication and proceed with the tracking area updating procedure; and ii) otherwise, request the lower layer to resume the RRC connection. In this request to the lower layer the NAS shall provide to the lower layer the RRC establishment cause and the call type according to annex D of this document; NOTE 1: In NB-S1 mode, in the request to the lower layer the data volume information of the initial NAS message is provided to the lower layers. Interactions between the NAS and the lower layers in order to obtain the data volume information of the initial NAS message (see 3GPP TS 36.321[ Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification ] [49], 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]) is left to implementations. - Upon indication from the lower layers that the RRC connection has been resumed when in EMM-IDLE mode with suspend indication, the UE shall enter EMM-CONNECTED mode. If the pending NAS message is: i) a SERVICE REQUEST message; ii) a CONTROL PLANE SERVICE REQUEST message, and the UE did not include any ESM message container, NAS message container, EPS bearer context status information element, or UE request type information element; or iii) an EXTENDED SERVICE REQUEST message, and the Service type information element indicates "packet services via S1" and the UE did not include any EPS bearer context status information element, or UE request type information element; the message shall not be sent. Otherwise the UE shall cipher the message as specified in clause 4.4.5 and send the pending initial NAS message upon entering EMM-CONNECTED mode; NOTE 2: If a NAS message is discarded and not sent to the network, the uplink NAS COUNT value corresponding to that message is reused for the next uplink NAS message to be sent. - Upon fallback indication from the lower layers at RRC connection resume when in EMM-IDLE mode with suspend indication, the UE shall enter EMM-IDLE mode without suspend indication, send any pending initial NAS message and proceed as if RRC connection establishment had been requested; - Upon indication from the lower layers that the RRC connection resume has failed and indication from the lower layers that the RRC connection is suspended, the UE shall enter EMM-IDLE mode with suspend indication and restart the ongoing NAS procedure if required; and - Upon indication from the lower layers that the RRC connection resume has failed and indication from the lower layers that the RRC connection is not suspended, the UE shall enter EMM-IDLE mode without suspend indication and restart the ongoing NAS procedure if required. In the network, when user plane CIoT EPS optimization is used: - Upon indication from the lower layers that the RRC connection has been suspended, the network shall enter EMM-IDLE mode with suspend indication, shall not consider the NAS signalling connection released and shall not consider the secure exchange of NAS messages terminated; and - Upon indication from the lower layers that the RRC connection has been resumed when in EMM-IDLE mode with suspend indication, the network shall enter EMM-CONNECTED mode. For the case that not all suspended bearers are resumed, see clause 6.4.4.6. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.1.3 |
5,696 | 8.49 Fully Qualified Cause (F-Cause) | Fully Qualified Cause (F- Cause) is coded as depicted in Figure 8.49-1. Figure 8.49-1: Full Qualified Cause (F-Cause) The value of Instance field of the F-Cause IE in a GTPv2 message shall indicate whether the F-Cause field contains RANAP Cause, BSSGP Cause or S1-AP Cause. All spare bits shall be set to zeros by the sender and ignored by the receiver. F-Cause field is coded as follows: - For RANAP Cause, the F-Cause field shall contain a non-transparent copy of the cause value of the corresponding IE (see clause 8.2.2), "Cause", as defined in clause 9.2..4 in 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33]. Cause Type field shall be ignored by the receiver. The value of F-Cause field (which has a range of 1..512) is transferred over the Iu interface and encoded into two octet as binary integer. - For BSSGP Cause, the F-Cause field shall contain a non-transparent copy of the cause value of the corresponding IE (see clause 8.2.2), "Cause", as defined in clause 11.3.8 in 3GPP TS 48.018[ None ] [34]. Cause Type field shall be ignored by the receiver. The value of F-Cause field (which has a range of 0..255) is transferred over the Gb interface and encoded into one octet as binary integer. - For S1-AP Cause, the F-Cause field shall contain a non-transparent copy of the cause value of the corresponding IE (see clause 8.2.2), "Cause", as defined in clause 9.2.1.3 in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. Cause Type field shall contain the RAN Cause subcategory as specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] and it shall be encoded as in Table 8.49-1. The value of F-Cause field (and the associated RAN cause subcategory) is transferred over the S1-AP interface and encoded into one octet as binary integer. Table 8.49-1: Cause Type values and their meanings | 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.49 |
5,697 | 4.7.3 GPRS attach procedure | The GPRS attach procedure is used for the following purposes: - normal GPRS attach, performed by the MS to IMSI attach for GPRS services only. The normal GPRS attach procedure shall be used: - by GPRS MSs in MS operation mode C, independent of the network operation mode; - by GPRS MSs in MS operation modes A or B if the network operates in network operation mode II; and - by GPRS MSs in MS operation mode A, independent of the network operation mode, if a circuit-switched transaction is ongoing; - combined GPRS attach procedure, used by GPRS MSs in MS operation modes A or B to attach the IMSI for GPRS and non-GPRS services provided that the network operates in network operation mode I. - GPRS attach for emergency bearer services, performed by the MS to IMSI or IMEI attach to emergency bearer services. The lower layers indicate to NAS that the network does not support emergency bearer services for the MS in limited service state (see 3GPP TS 25.331[ None ] [23c]). This information is taken into account when deciding whether to initiate attach for emergency bearer services. With a successful GPRS attach procedure a GMM context is established. When the timer T3346 is running, MS is allowed to initiate an attach procedure if: - the MS is an MS configured to use AC11 – 15 in selected PLMN; - the MS is attaching for emergency bearer services; or - the MS has timer T3346 running because a request from an MS with the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected, and the MS needs to attach without the low priority indicator, or with the low priority indicator set to "MS is not configured for NAS signalling low priority". An eCall only mobile station that is not capable of eCall over IMS shall not perform a normal or combined GPRS attach procedure. An eCall only mobile station that is capable of eCall over IMS may perform a normal or combined GPRS attach procedure only upon failure of a routing area updating procedure following intersystem change from S1 mode to A/Gb or Iu mode. When the MS moves from NG-RAN coverage to GERAN coverage, or from NG-RAN coverage to UTRAN coverage, the MS shall perform a normal or combined GPRS attach procedure, if the following applies: - the MS initiated a registration procedure while in N1 mode; and - since then the MS did not perform a successful EPS attach or tracking area updating procedure in S1 mode or GPRS attach or routing area updating procedure in A/Gb mode or Iu mode. Subclause 4.7.3.1 describes the GPRS attach procedure to attach the IMSI only for GPRS services. The combined GPRS attach procedure used to attach the IMSI for both GPRS and non-GPRS services is described in subclause 4.7.3.2. GPRS attach for emergency bearer services is described as part of subclause 4.7.3.1. If an IMSI attach for non-GPRS services is requested and a GMM context exists, the routing area updating procedure shall be used as described in subclause 4.7.5.2. To limit the number of consecutive rejected attach attempts, a GPRS attach attempt counter is introduced. The GPRS attach attempt counter shall be incremented as specified in subclause 4.7.3.1.5. Depending on the value of the GPRS attach attempt counter, specific actions shall be performed. The GPRS attach attempt counter shall be reset when: - the MS is powered on; - a SIM/USIM is inserted; - a GPRS attach or combined GPRS attach procedure is successfully completed; - an attach or combined attach procedure is successfully completed in S1 mode; - a combined GPRS attach procedure is completed for GPRS services only with cause #2, #16, #17, #22 or #28; - a GPRS attach or combined GPRS attach procedure is rejected with cause #11, #12, #13, #14 ,#15 or #25; - a network initiated detach procedure is completed with cause #11, #12, #13, #14, #15 or #25; or - a new PLMN is selected; and additionally when the MS is in substate ATTEMPTING-TO-ATTACH: - expiry of timer T3302; - a new routing area is entered; - an attach is triggered by CM sublayer requests; - timer T3346 is started. The mobile equipment shall contain a list of "forbidden location areas for roaming", as well as a list of "forbidden location areas for regional provision of service". The handling of these lists is described in subclause 4.4.1; the same lists are used by GMM and MM procedures. In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. The MS shall construct the Routing Area Identification of the cell from this chosen PLMN identity, and the LAC and the RAC received on the BCCH. For: - a shared GERAN, in A/Gb mode, the chosen PLMN identity is indicated to the GERAN in the first RLC data block of an upper layer PDU (see 3GPP TS 44.060[ None ] [76]) when a foreign TLLI or a random TLLI is used by the network sharing supporting MS for the transmission. - a shared UTRAN, the chosen PLMN identity shall be indicated to the UTRAN in the RRC INITIAL DIRECT TRANSFER message (see 3GPP TS 25.331[ None ] [23c]). For GERAN Iu mode, network sharing is not supported. Whenever an ATTACH REJECT message with the cause "PLMN not allowed" is received by the MS, the chosen PLMN indentity shall be stored in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. Whenever an ATTACH REJECT message is received by the MS with the cause "Roaming not allowed in this location area", "Location Area not allowed", or "No suitable cells in Location Area", the LAI that is part of the constructed RAI shall be stored in the suitable list. The network informs the MS about the support of specific features, such as LCS-MOLR, MBMS, IMS voice over PS session, emergency bearer services in Iu mode in the Network feature supporti nformation element. The information is either explicitly given by sending the Network feature support IE or implicitly by not sending it. The handling in the network is described in subclause 9.4.2.9. The network can also use the Additional network feature support IE in order to inform the MS about the support of specific features such as the delivery of SMS via GPRS (GPRS-SMS) or implicitly by not sending it. The MS may use the support indications for LCS-MOLR, MBMS and GPRS-SMS to inform the user about the availability of the appropriate services. The MS shall not request the LCS-MOLR or MBMS services, if the service has not been indicated as available. The indication for MBMS is defined in subclause "MBMS feature support indication" in 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [106]. In an MS with IMS voice over PS capability, the IMS voice over PS session indicator and the emergency bearer services indicator shall be provided to the upper layers. The upper layers take the IMS voice over PS session indicator into account as specified in 3GPP TS 23.221[ Architectural requirements ] [131], subclause 7.2a and subclause 7.2b, when selecting the access domain for voice sessions or calls in Iu mode. When initiating an emergency call in Iu mode, the upper layers also take the emergency bearer services indicator into account for the access domain selection. The MS may use the GPRS-SMS indication in order to obtain SMS. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3 |
5,698 | 13.4.1.3.2 Authorization for indirect communication with delegated discovery procedure | This clause covers the scenario where the NF Service Consumer use the SCP to discover and select the NF Service Producer instance that can process the service request. Figure 13.4.1.3.2-1: Authorization and service invocation procedure, for indirect communication with delegated discovery 1. The NF Service Consumer sends a service request to the SCP. The service request may include the NF Service Consumer's CCA as defined in clause 13.3.8.The NF Service Consumer may include an access token in the service request if it has received an access token in a previous service response. If a previously received access token has expired, the NF Service Consumer may include discovery parameters as specified in TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [74] clause 5.2.3.2.7 in the service request. If the CCA is included, the NF type of the expected audience in CCA shall contain NF type of "NRF" and the NF type of the NF Service Producer . 2. The SCP may perform a service discovery with the NRF. If NF Service Consumer has included an access token in step 1, or if the SCP has a cached granted access token, then SCP may reuse the access token and proceeds to step 6. 3. The SCP sends an access token request (Nnrf_AccessToken_Get Request) to the NRF. The access token request includes parameters as defined in clause 13.4.1.1. The access token request may include the NF Service Consumer's CCA if received in Step 1. 4. The NRF authenticates the NF Service Consumer using one of the methods described in clause 13.3.1.2. If NF Service Consumer authentication is successful and the NF Service Consumer is authorized based on the NRF policy, the NRF issues an access token as described in clause 13.4.1.1. The NRF uses the NF Service Consumer instance ID as the subject of the access token. 5. The NRF sends the access token to the SCP in an access token response (Nnrf_AccessToken_Get Response). 6. The SCP sends the service request to the NF Service Producer. The service request includes an access token (i.e., received in Step 1, received in Step 5, or previously cached), and may include the NF Service Consumer's CCA if received in Step 1. 7. The NF Service Producer authenticates the NF Service Consumer by one of the methods described in clause 13.3.2.2 and if successful, it validates the access token as described in clause 13.4.1.1. 8. If the validation of the access token is successful, the NF Service Producer sends the service response to the SCP. 9. The SCP forwards the service response to the NF Service Consumer. The SCP may include the access token in the service response to NF Service Consumer for possible re-use in subsequent service requests. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.4.1.3.2 |
5,699 | 9.3.3 Call proceeding | This message is sent by the network to the calling mobile station to indicate that the requested call establishment information has been received, and no more call establishment information will be accepted. See table 9.57/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: CALL PROCEEDING Significance: local Direction: network to mobile station Table 9.57/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CALL PROCEEDING message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.3 |
5,700 | 6.1 General 6.1.3 General rules | In the ASN.1 of this specification, the first bit of a bit string refers to the leftmost bit, unless stated otherwise. Upon reception of a list not using ToAddModList and ToReleaseList structure, the UE shall delete all entries of the list currently in the UE configuration before applying the received list and shall consider each entry as newly created. This applies also to lists whose size is extended (i.e. with a second list structure in the ASN.1 comprising additional entries), unless otherwise specified. This implies that Need M should not be used for fields in the entries of these lists; if used, UE will handle such fields equivalent to a Need R. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.