Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
3,101 | 4.16.9 Update of the subscription information in the PCF | Figure-4.16.9-1: Procedure for update of the subscription information in the PCF NOTE: The V-PCF is not used for session management related policy decisions in this procedure. 0. The PCF performs the subscription to notification to the profile modified in the UDR by invoking Nudr_DM_Subscribe (Policy Data, SUPI, Notification Target Address (+ Notification Correlation Id), Event Reporting Information (continuous reporting), one or several of the following: "PDU Session Policy Control data", "Remaining allowed Usage data" or "UE context Policy Control data") service. 1. The UDR detects that the related subscription profile has been changed. 2. If subscribed by the PCF, the UDR notifies the PCF on the changed profile by invoking Nudr_DM_Notify (Notification Correlation Id, Policy Data, SUPI, updated data and one or several of the following data subtypes "PDU Session Policy Control Data" or "Remaining allowed Usage data" or "UE Context Policy Control data") service. 3. The PCF stores the updated profile. 4. If the updated subscriber profile requires the status of new policy counters available at the CHF then an Initial/Intermediate Spending Limit Report Retrieval is initiated by the PCF as defined in clauses 4.16.8,2 and 4.16.8.3. If the updated subscriber profile implies that no policy counter status is needed an Intermediate Spending Limit Report Request Retrieval is initiated by the PCF to unsubscribe or, if this is the last policy counter status, a Final Spending Limit Report Retrieval is initiated by the PCF as specified in clause 4.16.8.4. 5. PCF makes an authorization and policy decision. 6. The PCF provides new session management related policy decisions to the SMF, using the Policy related interaction in PDU Session Modification procedure in clause 4.16.6, new access and mobility related policy information to the AMF using the AM Policy Association Modification procedure in clause 4.16.2 or new UE policy information to the AMF using the UE Policy Association Modification procedure in clause 4.16.12. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.9 |
3,102 | 5.3.1.2 Release of the NAS signalling connection 5.3.1.2.1 General | The signalling procedure for the release of the NAS signalling connection is initiated by the network. In S1 mode, when the RRC connection has been released, the UE shall enter EMM-IDLE mode and consider the NAS signalling connection released. If the UE is configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17] then: - if the NAS signalling connection that was released had been established for eCall over IMS, the UE shall start timer T3444; and - if the NAS signalling connection that was released had been established for a call to an HPLMN designated non-emergency MSISDN or URI for test or terminal reconfiguration service, the UE shall start timer T3445. The UE shall start the SGC timer T3447 with the service gap time value available in the UE when the NAS signalling connection is released if: - the UE supports SGC feature, and the service gap timer value is available in the UE and does not indicate zero; and - the NAS signalling connection that was released had been established for mobile originated request for transfer of uplink data. If the UE receives the "Extended wait time" from the lower layers when no attach, tracking area updating or service request procedure is ongoing, the UE shall ignore the "Extended wait time". To allow the network to release the NAS signalling connection, the UE: a) shall start the timer T3440 if the UE receives any of the EMM cause values #11, #12, #13, #14 (not applicable to the service request procedure), #15, #25, #31, #35, 42 or #78; a1) may start timer T3440 if the UE receives a SERVICE REJECT message, case e) in clause 5.6.1.6 is applicable and the procedure was started from EMM-IDLE mode; b) shall start the timer T3440 if: - the UE receives a TRACKING AREA UPDATE ACCEPT message which does not include a UE radio capability ID deletion indication IE; - the UE has not set the "active" flag in the TRACKING AREA UPDATE REQUEST message; - the UE has not set the "signalling active" flag in the TRACKING AREA UPDATE REQUEST message; - the tracking area updating or combined tracking area updating procedure has been initiated in EMM-IDLE mode, or the UE has set Request type to "NAS signalling connection release" in the UE request type IE in the TRACKING AREA UPDATE REQUEST message and the NAS signalling connection release bit is set to "NAS signalling connection release supported" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message; and - the user plane radio bearers have not been set up; c) shall start the timer T3440 if the UE receives a DETACH ACCEPT message and the UE has set the detach type to "IMSI detach" in the DETACH REQUEST message and user plane radio bearers have not been set up; d) shall start the timer T3440 if the UE receives a TRACKING AREA UPDATE REJECT message indicating: - any of the EMM cause values #9 or #10 and the UE has no CS fallback emergency call, CS fallback call, 1xCS fallback emergency call, or 1xCS fallback call pending; or - the EMM cause values #40, the TRACKING AREA UPDATE message was not triggered due to receiving a paging for CS fallback or a paging for 1xCS fallback, and the UE has no CS fallback emergency call, CS fallback call, 1xCS fallback emergency call, or 1xCS fallback call pending; e) shall start the timer T3440 if the UE receives a SERVICE REJECT message indicating any of the EMM cause values #9, #10 or #40 as a response to a SERVICE REQUEST message CONTROL PLANE SERVICE REQUEST message, or an EXTENDED SERVICE REQUEST message with service type set to "packet services via S1"; f) may start the timer T3440 if the UE receives any of the EMM cause values #3, #6, #7 or #8 or if it receives an AUTHENTICATION REJECT message; g) shall start the timer T3440 if the UE receives a SERVICE REJECT message indicating the EMM cause value #39 and the UE has initiated EXTENDED SERVICE REQUEST in EMM-IDLE and the user plane radio bearers have not been set up; h) shall start the timer T3440 if the UE receives a SERVICE REJECT, SERVICE ACCEPT, ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message with control plane data back-off timer; i) shall start the timer T3440 if the UE receives the EMM cause value #22 along with a T3346 value, and the value indicates that the timer T3346 is neither zero nor deactivated; j) shall start the timer T3440 if the UE receives a SERVICE ACCEPT message and the UE has set Request type to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE in the EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message; k) shall start the timer T3440 if the UE receives a SERVICE ACCEPT message, the UE has set the Control plane service type of the CONTROL PLANE SERVICE REQUEST message to "mobile terminating request" and the "active" flag in the Control plane service type IE to 0, the user plane radio bearers have not been set up, and the CONTROL PLANE SERVICE REQUEST message was sent from EMM-IDLE mode; l) shall start the timer T3440 if the UE receives a DETACH ACCEPT message and the UE has set the detach type to "EPS detach" or "combined EPS/IMSI detach" in the DETACH REQUEST message; or m) shall start the timer T3440 after the completion of the DETACH procedure, if the UE receives a DETACH REQUEST message and the detach type indicates "re-attach required". Upon expiry of T3440, - in cases a, a1, b, c, f, h, i, j and l, the UE shall locally release the established NAS signalling connection; - in cases d and e, the UE shall locally release the established NAS signalling connection and the UE shall initiate the attach procedure as described in clause 5.5.3.2.5, 5.5.3.3.5 or 5.6.1.5; or - in case m), the UE shall locally release the established NAS signalling connection and initiate the attach procedure as described in clause 5.5.3.2.5, 5.5.3.3.5 or 5.6.1.5. In cases b, c and g, - upon an indication from the lower layers that the user plane radio bearers are set up, the UE shall stop timer T3440 and may send uplink signalling via the existing NAS signalling connection or user data via the user plane bearers. If the uplink signalling is for CS fallback for emergency call, or for establishing a PDN connection for emergency bearer services, the UE shall send the uplink signalling via the existing NAS signalling connection; or In cases b, c, g and j, - upon receipt of a DETACH REQUEST message, the UE shall stop timer T3440 and respond to the network initiated detach as specified in clause 5.5.2.3. In case b, j and k, - upon receiving a request from upper layers to send NAS signalling not associated with establishing either a CS emergency call or a PDN connection for emergency bearer services, the UE shall wait for the local release of the established NAS signalling connection upon expiry of timer T3440 or T3440 being stopped before proceeding; - upon receiving a request from upper layers to establish either a CS emergency call or a PDN connection for emergency bearer services, the UE shall stop timer T3440 and shall locally release the NAS signalling connection, before proceeding as specified in clause 5.6.1; - upon receipt of ESM DATA TRANSPORT message, as an implementation option, the UE may reset and restart timer T3440; - upon receipt of a DOWNLINK NAS TRANSPORT or DOWNLINK GENERIC NAS TRANSPORT message, the UE which is in EMM-REGISTERED without PDN connections shall stop timer T3440 and may send uplink signalling via the existing NAS signalling connection; - upon receipt of an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST, MODIFY EPS BEARER CONTEXT REQUEST, DEACTIVATE EPS BEARER CONTEXT REQUEST, DOWNLINK NAS TRANSPORT or DOWNLINK GENERIC NAS TRANSPORT message, if the UE is using control plane CIoT EPS optimization, the UE shall stop timer T3440 and may send uplink signalling via the existing NAS signalling connection; or - upon initiation of tracking area updating procedure or combined tracking area updating procedure due to detecting the current TAI is not in the TAI list as specified in clause 5.5.3.2.6 for cases e, i, j, clause 5.5.3.2.2 for case a or clause 5.5.3.3.2 for case a, the UE shall stop timer T3440. In case c, - upon receiving a request from upper layers to send NAS signalling not associated with establishing a PDN connection for emergency bearer services, the UE shall wait for the local release of the established NAS signalling connection upon expiry of timer T3440 or T3440 being stopped before proceeding; or - upon receiving a request from upper layers to establish a PDN connection for emergency bearer services, the UE shall stop timer T3440 and shall locally release the NAS signalling connection, before proceeding as specified in clause 5.6.1. In cases d and e, - upon an indication from the lower layers that the RRC connection has been released, the UE shall stop timer T3440 and perform a new attach procedure as specified in clause 5.5.3.2.5, 5.5.3.3.5 or 5.6.1.5; or - upon receiving a request from upper layers to establish a PDN connection for emergency bearer services, the UE shall stop timer T3440 and shall locally release the NAS signalling connection, before proceeding as specified in clause 5.5.1. In cases a and f, - upon receiving a request from upper layers to establish a PDN connection for emergency bearer services, the UE shall stop timer T3440 and shall locally release the NAS signalling connection, before proceeding as specified in clause 5.5.1. In case g, - upon receiving a request from upper layers to send NAS signalling not associated with establishing either a CS emergency call or a PDN connection for emergency bearer services, the UE shall wait for the local release of the established NAS signalling connection upon expiry of timer T3440 or T3440 being stopped before proceeding; or - upon receiving a request from upper layers to establish either a CS emergency call or a PDN connection for emergency bearer services, the UE shall stop timer T3440 and shall locally release the NAS signalling connection, before proceeding as specified in clause 5.6.1. In case h, - upon an indication from the lower layers that the user plane radio bearers are set up or upon receiving a request from upper layers to send NAS signalling not associated with ESM DATA TRANSPORT, the UE shall stop timer T3440; or - the UE shall not send ESM DATA TRANSPORT message until expiry of timer T3440 or times T3440 being stopped. In EMM-CONNECTED mode, if the UE moves to EMM-SERVICE-REQUEST-INITIATED state upon receipt of a CS SERVICE NOTIFICATION message, the UE shall stop timer T3440. In S101 mode, when the cdma2000® HRPD radio access connection has been released, the UE shall enter EMM-IDLE mode and consider the S101 mode NAS signalling connection released. If the timer T3440 is not running when the UE enters state EMM-DEREGISTERED.PLMN-SEARCH or EMM-REGISTERED.PLMN-SEARCH, the UE may locally release the NAS signalling connection. | 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.2 |
3,103 | 5.17.1.2 User Plane management to support interworking with EPS | In order to support the interworking with EPC, the SMF+PGW-C provides information over N4 to the UPF+PGW-U related to the handling of traffic over S5-U. Functionality defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] for traffic steering control on SGi-LAN/N6 can be activated in UPF+PGW-U under consideration of whether the UE is connected to EPC or 5GC. When the UE is connected to EPC and establishes/releases PDN connections, the following differences apply to N4 compared to when the UE is connected to 5GC: - The CN Tunnel Info is allocated for each EPS Bearer. - In addition to the Service Data Flow related information, the SMF+PGW-C shall be able to provide the GBR and MBR values for each GBR bearer of the PDN connection to the UPF+PGW-U. If the UE does not have preconfigured rules for associating an application to a PDN connection (i.e. the UE does not have rules in UE local configuration and is not provisioned with ANDSF rules), the UE should use a matching URSP rule as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], if available, to derive the parameters, e.g. APN, for the PDN connection establishment and associating an application to the PDN connection. NOTE: The mapping between the parameters in the URSP rules and the parameters used for PDN connection establishment is defined in TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [110]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.1.2 |
3,104 | 6.41.2.2 Configuration of Localized Services in Hosting Network | NOTE: The term “Service provider of localized services” includes also 3rd party service provider. The 5G system shall support suitable mechanisms to allow automatically establishing localized service agreements for a specific occasion (time and location) and building temporary relationship among hosting network operator and other service providers including network operators or 3rd party application providers. The 5G system shall support means for the service provider to request the hosting network via standard mechanisms to provide access to 3rd party services at a specific period of time and location. This period of time shall be flexible, so that a change in service provision can be decided at any time (e.g., to cancel or prolong local services in the locality of service delivery) based on localized services agreements. Based on localized services agreements, the 5G system shall provide suitable means to allow the service provider to request and provision various localized service requirements, including QoS, expected/maximum number of users, event information for discovery, network slicing, required IP connectivity etc, and routing policies for the application of the localized services via the hosting network. The 5G system shall support means for a hosting network to create policies and configure resources for the requested time and location for the 3rd party services based on the received request. The 5G system shall support means for a hosting network to notify the service provider of the accepted service parameters and routing policies. Subject to regulatory requirements and localized service agreements, the 5G system shall allow a home network operator to automatically negotiate policies with the hosting network for allowing the home network’s subscribers to connect at a specific occasion, e.g., time and location, for their home network services. Subject to the automatic localized services agreements between the hosting network operator and home network operator, for UE with only home network subscription and with authorization to access hosting networks the 5G system shall support: - access to the hosting network and use home network services or selected localized services via the hosting network, - seamless service continuity for home network services or selected localized services when moving between two hosting networks or a host network and the home network. The 5G system shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of their spatial extent (in terms of a particular topology, for example a single cell), as specified by a service provider of localized services. The 5G system shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of the resources or capacity available, to correspond to requirements that apply only to the locality of service delivery, as specified by a service provider of localized services. The 5G system shall support means for a hosting network to provide a 3rd party service provider with information for automatic discovery of the hosting network by the UEs to allow access to specific 3rd party services. The 5G system shall support secure mechanisms to allow a home network to coordinate with a hosting network for a subscriber to temporarily access the hosting network (e.g., based on temporary credentials) at a given time (start time and duration) and location. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.41.2.2 |
3,105 | 5.3.10.5 RLF report content determination | The UE shall determine the content in the VarRLF-Report as follows: 1> clear the information included in VarRLF-Report, if any; 1> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN); 1> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., registered SNPN); 1> set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure; 1> if measRSSI-ReportConfig is configured for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF), set the measResultLastServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment the UE detected the failure; 1> if the SS/PBCH block-based measurement quantities are available: 2> set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE detected failure; 1> if the CSI-RS based measurement quantities are available: 2> set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure; 1> for each of the configured measObjectNR in which measurements are available: 2> if the SS/PBCH block-based measurement quantities are available: 3> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the cell with highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the cell with highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE detected failure; 4> for each neighbour cell included, include the optional fields that are available; NOTE 0a: For the neighboring cells included in measResultListNR in measResultNeighCells ordered based on the SS/PBCH block measurement quantities, UE also includes the CSI-RS based measurement quantities, if available. 2> if the CSI-RS based measurement quantities are available: 3> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected radio link failure; 4> for each neighbour cell included, include the optional fields that are available; NOTE 0b: For ordering the neighboring cells based on the CSI-RS measurement quantities, UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS/PBCH block-based ordered measurements. 2> for each neighbour cell, if any, included in measResultListNR in measResultNeighCells: 3> if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in the MCG VarConditionalReconfig at the moment of the detected failure: 4> set choConfig in MeasResult2NR to the execution condition for each measId within condTriggerConfig associated to the neighbour cell within the MCG VarConditionalReconfig; 4> if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure; or 4> if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure: 5> set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time; 5> set timeBetweenEvents to the elapsed time between the point in time of fullfilling the condition in choConfig that was fulfilled first in time, and the point in time of fullfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fullfilled; 1> for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency: 2> set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequencies other than the frequency of the source PCell (in case HO failure) or of the PCell (in case RLF), up to the moment the UE detected failure; 1> for each of the configured EUTRA frequencies in which measurements are available; 2> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, and based on measurements collected up to the moment the UE detected failure; 3> for each neighbour cell included, include the optional fields that are available; 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. 1> set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF); 1> if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in VarRLF-report as follows: 2> set the connectionFailureType to hof; 2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running: 3> set lastHO-Type to daps; 3> if radio link failure was detected in the source PCell, according to clause 5.3.10.3: 4> set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running; 4> set the rlf-Cause to the trigger for detecting the source radio link failure in accordance with clause 5.3.10.4; 2> if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of the handover failure: 3> if the UE executed a conditional handover toward target PCell according to the condRRCReconfig of the target PCell: 4> set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed conditional handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig of the target PCell of the failed conditional handover; 3> else: 4> set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig; 3> set choCandidateCellList to include the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of each of the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResultNeighCells; 2> if the UE supports RLF-Report for conditional handover and if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover: 3> set lastHO-Type to cho; 2> set the nrFailedPCellId in failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover; 2> include nrPreviousCell in previousPCellId and set it to the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message including reconfigurationWithSync was received; 2> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync; 1> else if the failure is detected due to Mobility from NR failure as described in 5.4.3.5, set the fields in VarRLF-report as follows: 2> set the connectionFailureType to hof; 2> if last MobilityFromNRCommand concerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA): 3> set the eutraFailedPCellId in failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover; 2> include nrPreviousCell in previousPCellId and set it to the global cell identity and tracking area code of the PCell where the last MobilityFromNRCommand message was received; 2> set the timeConnFailure to the elapsed time since the initialization of the handover associated to the last MobilityFromNRCommand message; 2> if voiceFallbackIndication is included in the last MobilityFromNRCommand: 3> include the voiceFallbackHO; 1> else if the failure is detected due to radio link failure as described in 5.3.10.3, set the fields in VarRLF-report as follows: 2> set the connectionFailureType to rlf; 2> set the rlf-Cause to the trigger for detecting radio link failure in accordance with clause 5.3.10.4; 2> set the nrFailedPCellId in failedPCellId to the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected; 2> if an RRCReconfiguration message including the reconfigurationWithSync was received before the connection failure: 3> if the last successfully executed RRCReconfiguration message including the reconfigurationWithSync concerned an intra NR handover and it was received while connected to the previous PCell to which the UE was connected before connecting to the PCell where radio link failure is detected; and 3> if T311 was not running before entering the PCell in which the radio link failure was detected: 4> include the nrPreviousCell in previousPCellId and set it to the global cell identity and the tracking area code of the PCell where the last executed RRCReconfiguration message including reconfigurationWithSync was received; 4> if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a DAPS handover: 5> set lastHO-Type to daps; 4> else if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover: 5> set lastHO-Type to cho; 4> set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync; 3> else if the last RRCReconfiguration message including the reconfigurationWithSync concerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA: 4> include the eutraPreviousCell in previousPCellId and set it to the global cell identity and the tracking area code of the E-UTRA PCell where the last RRCReconfiguration message including reconfigurationWithSync was received embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.4.3.3; 4> set the timeConnFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.4.3.3; 2> if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of declaring the radio link failure: 3> set timeSinceCHO-Reconfig to the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the last conditionalReconfiguration including the condRRCReconfig message; 3> set choCandidateCellList to include the global cell identity if available, and otherwise to the physical cell identity and carrier frequency of each of all the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of radio link failure, excluding the candidate target cells included in measResultNeighCells; 1> if connectionFailureType is rlf and the rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure; or 1> if connectionFailureType is rlf and the rlf-Cause is set to lbtFailure and the radio link failure is detected during the random access procedure; or 1> if connectionFailureType is hof and if the failed handover is an intra-RAT handover: 2> set the ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5; 1> if connectionFailureType is rlf and the rlf-Cause is set to lbtFailure, and the radio link failure is not detected during the random access procedure: 2> set the locationAndBandwidth and subcarrierSpacing in bwp-Info associated to the UL BWP in which the consistent uplink LBT failure was detected; 1> if the rlf-Cause is set to t310-Expiry or t312-Expiry: 2> set the ssbRLMConfigBitmap and/or csi-rsRLMConfigBitmap in measResultLastServCell to include the radio link monitoring configuration of the last serving cell, if available; 1> if the UE supports RLF-Report for fast MCG recovery procedure: 2> if the fast MCG recovery procedure fails due to expiry of timer T316: 3> set the mcgRecoveryFailureCause to t316-expiry; 2> else if the SCG was deactivated before initiation of the fast MCG recovery procedure: 3> set the mcgRecoveryFailureCause to scgDeactivated; Editor´s note: The use of scgDeactivated cause. 2> else if the UE detected SCG failure while the timer T316 was running or before initiation of the fast MCG recovery procedure: 3> set the pSCellId to the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell; 3> set the scgFailureCause value according to 5.7.3.5; 3> set the elapsedTimeSCGFailure to the time elapsed between SCG failure and the MCG failure; 1> if available, set the locationInfo as in 5.3.3.7. The UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure/handover failure is detected. NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.10.5 |
3,106 | 5.41 NR RedCap UEs differentiation | This functionality is used by the network to identify traffic to/from UEs accessing over NR RedCap, e.g. for charging differentiation. An NR RedCap UE using NR shall provide an NR RedCap indication to the NG-RAN during RRC Connection Establishment procedure as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. When the UE has provided an NR RedCap indication to the NG-RAN during RRC Connection Establishment, the NG-RAN shall provide an NR RedCap Indication to the AMF in the Initial UE Message (see clause 4.2.2.2.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]). When the AMF receives an NR RedCap Indication from NG-RAN in an Initial UE Message, the AMF shall store the NR RedCap Indication in the UE context, consider that the RAT type is NR RedCap and signal it accordingly to the SMSF during registration procedure for SMS over NAS, to the SMF during PDU Session Establishment or PDU Session Modification procedure. The PCF will also receive the NR RedCap RAT type indication when applicable, from the SMF during SM Policy Association Establishment or SM Policy Association Modification procedure. During handover from E-UTRA to NR, the target NG-RAN (i.e. gNB) provides the NR RedCap indication to AMF in NGAP Path Switch Request message during Xn handover, or NGAP Handover Request Acknowledge message during N2 handover (including intra 5GS N2 handover and EPS to 5GS handover) based on the UE capability information provided by the source RAN to the target RAN as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. The NFs interacting with CHF shall include the NR RedCap as RAT type. Upon AMF change, the source AMF shall provide the "NR RedCap Indication" to the target AMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.41 |
3,107 | F.1 5GS Bridge information reporting | Figure F.1-1: 5GS Bridge information reporting Identities of 5GS Bridge and UPF/NW-TT ports are pre-configured on the UPF based on deployment. The SMF requests the UPF/NW-TT to measure and report the clock drift between the TSN GM time and 5GS GM time for one or more TSN time domains. 1. PDU Session Establishment as defined clause 4.3.2.2.1-1 is used to establish a PDU Session serving for TSC. During this procedure, the SMF selects a UPF, which supports functions as defined in clause 5.28.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], for the PDU Session. During this procedure, the SMF receives the UE-DS-TT residence time, DS-TT MAC address for this PDU Session and port management capabilities from the DS-TT/UE in PDU Session Establishment request and receives the allocated port number for DS-TT Ethernet port and user-plane Node ID in N4 Session Establishment Response message. The UPF allocates the port number for DS-TT, user-plane Node ID after receiving N4 Session Establishment Request message. 2. The SMF sends the information received in step 1 to the TSN AF via PCF to establish/modify the 5GS Bridge. The Npcf_PolicyAuthorization_Notify message in step 2b is delivered via the pre-configured AF session as described in clause 4.16.5.1. The TSN AF stores the binding relationship between 5GS user-plane Node ID, MAC address of the DS-TT Ethernet port and also updates 5GS bridge delay as defined in clause 5.27.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] for future configuration. The TSN AF requests creation of a new AF session associated with the MAC address of the DS-TT Ethernet port using the Npcf_PolicyAuthorization_Create operation (step 2c) and subscribes for TSN events over the newly created AF session using the Npcf_PolicyAuthorization_Subscribe operation (step 2d). In the case of TSN AF support for direct notification from UPF for PMIC and UMIC, the subscription in step 2d has following additional information: "Notification Target Address for PMIC/UMIC UPF event" and "Correlation ID for PMIC/UMIC UPF event". Using the 5GS user-plane Node ID received in step 2b the TSN AF subscribes with the NW-TT for receiving user plane node management information changes for the 5GS bridge indicated by the 5GS user-plane Node ID as described in clause 5.28.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. After receiving a User plane node Management Information Container (UMIC) containing the NW-TT port numbers, the TSN AF subscribes with the NW-TT for receiving NW-TT port management information changes for the NW-TT port indicated by each of the NW-TT port numbers as described in clause 5.28.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TSN AF can use any PDU Session to subscribe with the NW-TT for bridge or port management information notifications. Similarly, the UPF can use any PDU Session to send bridge or port management information notifications. 3. If DS-TT has indicated support for the TSN Time domain number in the port management capabilities, TSN AF provides the TSN Time domain number to DS-TT. Optionally, TSN AF provides the TSN Time domain number to NW-TT. 4. If supported according to the port management capabilities received from DS-TT, TSN AF retrieves txPropagationDelay and Traffic Class table from DS-TT. TSN AF also retrieves txPropagationDelay and Traffic Class table from NW-TT. NOTE: It is assumed that distribution of TSN GM time towards NW-TT and DS-TT for the TSN time domain is activated before TSN AF retrieves txPropagationDelay so that DS-TT and NW-TT can convert txPropagationDelay from 5GS time to TSN time before reporting txPropagationDelay to TSN AF. 5. If DS-TT supports neighbor discovery according to the port management capabilities received from DS-TT, then TSN AF: - provides DS-TT port neighbor discovery configuration to DS-TT to configure and activate the LLDP agent in DS-TT; - subscribes to receive Neighbor discovery information for each discovered neighbor of DS-TT (see Table K.1-1 in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If DS-TT does not support neighbor discovery, then TSN AF: - provides DS-TT port neighbor discovery configuration to NW-TT to configure and activate the LLDP agent in NW-TT to perform neighbor discovery on behalf of DS-TT; - subscribes to receive Neighbor discovery information for each discovered neighbor of DS-TT from NW-TT (see Table K.1-1 in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. TSN AF: - writes NW-TT port neighbor discovery configuration to NW-TT to configure and activate the LLDP agent in NW-TT; - subscribes to receive Neighbor discovery information for each discovered neighbor of NW-TT (see Table K.1-1 in TS 23.501[ System architecture for the 5G System (5GS) ] [2]). 6. TSN AF receives notifications from DS-TT (If DS-TT supports neighbour discovery) and NW-TT on discovered neighbors of DS-TT and NW-TT. 7. The TSN AF constructs the above received information as 5GS Bridge information and sends them to the CNC to register a new TSN Bridge or update an existing TSN Bridge. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | F.1 |
3,108 | 16.20.2 Mechanisms and Principles | Support of AI/ML in NG-RAN requires inputs from neighbour NG-RAN nodes (e.g. predicted information, feedback information, measurements) and/or UEs (e.g. measurement results). Signalling procedures used for the exchange of information to support AI/ML in NG-RAN, are use case and data type agnostic, which means that the intended usage of the data exchanged via these procedures (e.g., input, output, feedback) is not indicated. AI/ML algorithms and models are out of 3GPP scope, and the details of model performance feedback are also out of 3GPP scope. Support of AI/ML in NG-RAN does not apply to ng-eNB. For the deployment of AI/ML in NG-RAN, the following scenarios may be supported: - AI/ML Model Training is located in the OAM and AI/ML Model Inference is located in the NG-RAN node; - AI/ML Model Training and AI/ML Model Inference are both located in the NG-RAN node. The following information can be configured to be reported by an NG-RAN node: - Predicted resource status information; - UE performance feedback; - Measured UE trajectory; - Energy Cost (EC). The collection and reporting are configured through the Data Collection Reporting Initiation procedure, while the actual reporting is performed through the Data Collection Reporting procedure. The collection of measured UE trajectory and UE performance feedback is triggered at successful Handover execution. Cell-based UE trajectory prediction, which can be used e.g. for the Mobility Optimization use case, is transferred to the target NG-RAN node via the Handover Preparation procedure to provide information for e.g. subsequent mobility decisions. Cell-based UE trajectory prediction is limited to the first-hop target NG-RAN node. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.20.2 |
3,109 | – NonCellDefiningSSB | The IE NonCellDefiningSSB is used to configure a NCD-SSB to be used while the UE operates in an (e)RedCap-specific initial BWP or a dedicated BWP that does not contain the CD-SSB. NonCellDefiningSSB information element -- ASN1START -- TAG-NONCELLDEFININGSSB-START NonCellDefiningSSB-r17 ::= SEQUENCE { absoluteFrequencySSB-r17 ARFCN-ValueNR, ssb-Periodicity-r17 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 } OPTIONAL, -- Need S ssb-TimeOffset-r17 ENUMERATED { ms5, ms10, ms15, ms20, ms40, ms80, spare2, spare1 } OPTIONAL, -- Need S ... } -- TAG-NONCELLDEFININGSSB-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,110 | 5.8.5 Parameters for N4 session management 5.8.5.1 General | These parameters are used by SMF to control the functionality of the UPF as well as to inform SMF about events occurring at the UPF. The N4 session management procedures defined in clause 4.4.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] will use the relevant parameters in the same way for all N4 reference points: the N4 Session Establishment procedure as well as the N4 Session Modification procedure provide the control parameters to the UPF, the N4 Session Release procedure removes all control parameters related to an N4 session, and the N4 Session Level Reporting procedure informs the SMF about events related to the PDU Session that are detected by the UPF. The parameters over N4 reference point provided from SMF to UPF comprises an N4 Session ID and may also contain: - Packet Detection Rules (PDR) that contain information to classify traffic (PDU(s)) arriving at the UPF; - Forwarding Action Rules (FAR) that contain information on whether forwarding, dropping or buffering is to be applied to a traffic identified by PDR(s); - Multi-Access Rules (MAR) that contain information on how to handle traffic steering, switching and splitting for a MA PDU Session; - Usage Reporting Rules (URR) contains information that defines how traffic identified by PDR(s) shall be accounted as well as how a certain measurement shall be reported; - QoS Enforcement Rules (QER), that contain information related to QoS enforcement of traffic identified by PDR(s); - Session Reporting Rules (SRR) that contain information to request the UP function to detect and report events for a PDU session that are not related to specific PDRs of the PDU session or that are not related to traffic usage measurement. - Trace Requirements; - Port Management Information Container in 5GS; - Bridge/Router Information. The N4 Session ID is assigned by the SMF and uniquely identifies an N4 session. If the UPF indicated support of Trace, the SMF may activate a trace session during a N4 Session Establishment or a N4 Session Modification procedure. In that case it provides Trace Requirements to the UPF. The SMF may deactivate an on-going trace session using a N4 Session Modification procedure. There shall be at most one trace session activated per N4 Session at a time. For the MA PDU Session, the SMF may add an additional access tunnel information during an N4 Session Modification procedure by updating MAR with addition of an FAR ID which refers to an FAR containing the additional access tunnel information for the MA PDU session for traffic steering in the UPF. For the MA PDU Session, the SMF may request Access Availability report per N4 Session, during N4 Session Establishment procedure or N4 Session Modification procedure. A N4 Session may be used to control both UPF and NW-TT behaviour in the UPF. A N4 session support and enable exchange of bridge/router configuration between the SMF and the UPF: - Information that the SMF needs for bridge/router management (clause 5.8.5.9); - Information that 5GS transparently relays between the TSN AF or TSCTSF and the NW-TT: transparent Port Management Information Container along with the associated NW-TT port number. - Information that 5GS transparently relays between the TSN AF or TSCTSF and the NW-TT: transparent user plane node Management Information Container (clause 5.8.5.14). When a N4 Session related with bridge/router management is established, the UPF allocates a dedicated port number for the PDU Session. The UPF then provides to the SMF following configuration parameters for the N4 Session: - port number. - user-plane node ID. To support TSN, the user-plane node ID is Bridge ID. To support integration with IETF DetNet, the user-plane node ID can be Router ID. The User Plane Node ID may be pre-configured in the UPF based on deployment. After the N4 session has been established, the SMF and UPF may at any time exchange transparent user plane node and Port Management Information Container over a N4 session. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.5 |
3,111 | 5.1.2.6 UE - P-GW user plane with Control Plane CIoT EPS Optimisations | Legend: - GTP-u (GPRS Tunnelling Protocol User plane): This protocol tunnels user data between MME and the S-GW as well as between the S-GW and the P-GW in the backbone network. GTP shall encapsulate all end user packets. End user Ethernet packets are only used with a combined PDN GW+SMF (as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [83]). - UDP/IP: These are the backbone network protocols used for routing user data and control signalling. - NAS: this is the Non-Access Stratum Layer used to carry Data between UE and MME and may include Header compression and security functions of user plane IP data. Whether a convergence protocol sublayer may be required for this purpose is a stage 3 matter. Figure 5.1.2.6-1: User Plane with Control Plane CIoT EPS Optimisations | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.1.2.6 |
3,112 | A-MPR for CA_NS_05 for CA_38C | If the UE is configured to CA_ and it receives IE CA_NS_05 the allowed maximum output power reduction applied to transmission on the PCC and the SCC for contiguously aggregated signals is specified in Table . Table 6..5-1: Contigous Allocation A-MPR for CA_NS_05 If the UE is configured to CA_38C and it receives IE CA_NS_05 the allowed maximum output power reduction applied to transmissions on the PCell and the SCell with non-contiguous resource allocation is defined as follows A-MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = -14.17 A + 16.50 ; 0 ≤ A < 0.60 -2.50 A + 9.50 ; 0.60 ≤ A ≤ 1 Where A = NRB_alloc / NRB_agg. | 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 | A-MPR |
3,113 | 19.2 Call flows in roaming scenarios | The procedures described in clause 17 of the present specification: Session Start procedure (clause 17.5.2), Session Stop procedure (clause 17.5.3), Registration procedure (clause 17.5.4), De-registration procedure (GGSN initiated) (clause 17.5.5), De-registration procedure (BM-SC initiated) (clause 17.5.6), Trace Session Activation procedure (clause 17.5.8), Trace Session Deactivation procedure (clause 17.5.9), MBMS UE Context Modification procedure (clause 17.5.10), and Session Update procedure (clause 17.5.11) work exactly the same in roaming scenarios, i.e when the GGSN is in a visited PLMN and the BM-SC is in the home PLMN, and they are Gmb procedures only and are not needed over Mz interface. Service activation procedures and Service deactivation procedures are the only procedures over Mz interface, and are described in detail in the following subclauses. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 19.2 |
3,114 | 4.2.4.2 UE Configuration Update procedure for access and mobility management related parameters | This procedure is initiated by the AMF when the AMF wants to update access and mobility management related parameters in the UE configuration. This procedure is also used to trigger UE to perform, based on network indication, either Mobility Registration Update procedure while the UE is in CM-CONNECTED state to modify NAS parameters that require negotiation (e.g. MICO mode) or to steer the UE towards EPC as specified in clause 5.31.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], or Mobility Registration Update procedure after the UE enters CM-IDLE state (e.g. for changes to Allowed NSSAI that require re-registration) or to update the UE with the Alternative S-NSSAI. If a Registration procedure is needed, the AMF provides an indication to the UE to initiate a Registration procedure. UE Configuration Update shall be sent over the Access Type (i.e. 3GPP access or non-3GPP access) the UE Configuration Update is applied to, when applicable. If the AMF wants to update NAS parameters in the UE which require UE acknowledgement, then the AMF provides an indication to the UE of whether the UE shall acknowledge the command or not. The AMF should not request acknowledgement of the NITZ command. The AMF shall request acknowledgement for NSSAI information (e.g. Allowed NSSAI, Partially Allowed NSSAI, S-NSSAI rejected partially in the RA), 5G-GUTI, TAI List, [TAI List for S-NSSAIs in Partially Allowed NSSAI], [TAI List for S-NSSAI(s) rejected partially in RA] and Mobility Restrictions, LADN Information, MICO, Operator-defined access category definitions, PLMN-assigned UE Radio Capability ID, S-NSSAI location availability information and SMS subscription. Figure 4.2.4.2-1: UE Configuration Update procedure for access and mobility management related parameters 0. AMF determines the necessity of UE configuration change due to various reasons (e.g. UE mobility change, NW policy, reception of Subscriber Data Update Notification from UDM, change of Network Slice configuration (including due to change of the NSSRG information in subscription information as specified in clause 5.15.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], or due to change of NSAG Information as specified in clause 5.15.14 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), or to remove S-NSSAI from the Allowed NSSAI due to expiry of slice deregistration inactivity timer or to provide the UE with updated Slice Usage Policy as specified in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], need to assign PLMN-assigned UE Radio Capability ID, change of Enhanced Coverage Restriction information in the UE context, informing MBSR (IAB-UE) authorization state changes as specified in clause 5.35A.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] based on operator configuration, a change related to discontinuous coverage (e.g. out-of-coverage period change), need to notify the UE to reconnect to the network due to NG-RAN timing synchronization status change as specified in clause 4.15.9.4) or that the UE needs to perform a Registration Procedure. If a UE is in CM-IDLE, the AMF can wait until the UE is in CM-CONNECTED state or triggers Network Triggered Service Request (in clause 4.2.3.3). NOTE 1: It is up to the network implementation whether the AMF can wait until the UE is in CM-CONNECTED state or trigger the Network Triggered Service Request. NOTE 2: The AMF can check whether Network Slice configuration needs to be updated by using the Nnssf_NSSelection_Get service operation and in such case the AMF compares the stored information with the output from the NSSF to decide whether an update of the UE is required. The AMF may include Mobility Restriction List in N2 message that delivers UE Configuration Update Command to the UE if the service area restriction for the UE is updated. 1. The AMF sends UE Configuration Update Command containing one or more UE parameters (Configuration Update Indication, 5G-GUTI, TAI List, Allowed NSSAI, Mapping Of Allowed NSSAI, [Partially Allowed NSSAI], [Mapping Of Partially Allowed NSSAI], [TAI List for S-NSSAIs in Partially Allowed NSSAI], Configured NSSAI for the Serving PLMN, Mapping Of Configured NSSAI, [NSSRG Information], rejected S-NSSAIs, [TAI List for S-NSSAI(s) rejected partially in RA], NITZ, Mobility Restrictions, LADN Information, MICO, Operator-defined access category definitions, SMS Subscribed Indication, [PLMN-assigned UE Radio Capability ID], [PLMN-assigned UE Radio Capability ID deletion indication], ["List of PLMN(s) to be used in Disaster Condition"], [Disaster Roaming wait range information], [Disaster Return wait range information], [MPS priority], [MCX priority], [UAS services Indication], MBSR authorization information, [S-NSSAI location availability information], [Mapping Of Alternative NSSAI], UE reconnection indication, [Slice Usage Policy], [Maximum Time Offset]) to the UE. Optionally, the AMF may update the rejected S-NSSAIs in the UE Configuration Update command. The AMF includes one or more of 5G-GUTI, TAI List, Allowed NSSAI, Mapping Of Allowed NSSAI, Partially Allowed NSSAI, Mapping Of Partially Allowed NSSAI, [TAI List for S-NSSAIs in Partially Allowed NSSAI], Configured NSSAI for the Serving PLMN, Mapping Of Configured NSSAI, rejected S-NSSAIs, [TAI List for S-NSSAI(s) rejected partially in RA], NITZ (Network Identity and Time Zone), Mobility Restrictions parameters, LADN Information, Operator-defined access category definitions, PLMN-assigned UE Radio Capability ID, or SMS Subscribed Indication if the AMF wants to update these NAS parameters without triggering a UE Registration procedure. The AMF may include in the UE Configuration Update Command also Configuration Update Indication parameters indicating whether: - Network Slicing Subscription Change has occurred; - the UE shall acknowledge the command; and - whether a Registration procedure is requested. If the AMF indicates Network Slicing Subscription Change, then the UE shall locally erase all the network slicing configuration for all PLMNs and if applicable, update the configuration for the current PLMN based on any received information. If the AMF indicates Network Slicing Subscription Change, the UE shall also be requested to acknowledge in step 2. If the AMF also includes in the UE Configuration Update Command message a new Configured NSSAI for the Serving PLMN, then the AMF should also include a new Allowed NSSAI with, if available, the associated Mapping Of Allowed NSSAI, unless the AMF cannot determine the new Allowed NSSAI after the Subscribed S-NSSAI(s) are updated, in which case the AMF does not include in the UE Configuration Update Command message any Allowed NSSAI. If the UE has indicated its support of the subscription-based restrictions to simultaneous registration of network slices feature in the UE 5GMM Core Network Capability, the AMF includes, if available, the NSSRG Information, defined in clause 5.15.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE has not indicated its support of the subscription-based restrictions to simultaneous registration of network slices feature and the subscription information for the UE includes NSSRG information and the AMF is providing the Configured NSSAI to the UE, the Configured NSSAI shall include the S-NSSAIs according to clause 5.15.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For a non-roaming UE, if the UE has indicated its support of Slice Usage Policy in the UE 5GMM Core Network Capability, the AMF may include Slice Usage Policies for slices in the Configured NSSAI as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In the Slice Usage Policy, the AMF indicates an S-NSSAI is on demand slice and slice deregistration inactivity timer value. If the AMF includes slice deregistration timer value, the UE starts any slice deregistration inactivity timer for the on demand S-NSSAIs as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE has indicated its support of NSAG feature in 5GMM Core Network Capability, the AMF includes, if available, the NSAG Information, defined in clause 5.15.14 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] when providing a new Configured NSSAI which includes S-NSSAIs with associated NSAG Value(s) or when the NSAG Information changes for some S-NSSAI in the Configured NSSAI. When NSAG Information is provided to the UE, the AMF requests the UE to acknowledge the UE Configuration Command message. When the UE and the AMF supports RACS as defined in clause 5.4.4.1a of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the AMF needs to configure the UE with a UE Radio Capability ID and the AMF already has the UE radio capabilities other than NB-IoT radio capabilities for the UE and the AMF may provide the UE with the UE Radio Capability ID for the UE radio capabilities the UCMF returns to the AMF in a Nucmf_assign service operation for this UE. If the UE is needed to be redirected to the dedicated frequency band(s) for S-NSSAI(s), the AMF may determine a Target NSSAI, as described in clause 5.3.4.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], itself or by interacting with the NSSF using Nnssf_NSSelection_Get which includes e.g. the Rejected S-NSSAI(s) for RA and Allowed NSSAI. The AMF may determine RFSP index associated to the Target NSSAI by interacting with the PCF using Npcf_AMPolicyControl_Update which includes the Target NSSAI to retrieve a corresponding RFSP index or based on local configuration in case PCF is not deployed. The Target NSSAI and the RFSP index associated with the Target NSSAI are provided to the NG-RAN within the N2 message carrying the UE Configuration Update Command message. If the UE and AMF supports Disaster Roaming service, the AMF may include the "list of PLMN(s) to be used in Disaster Condition", Disaster Roaming wait range information and Disaster Return wait range information as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the disaster condition is no longer applicable, the serving AMF that provides Disaster Roaming service may notify the UE as specified in clause 5.40.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the AMF receives a Subscriber Data Update Notification from the UDM that includes MPS priority or MCX priority, the AMF includes MPS priority or MCX priority in the UE Configuration Update Command, respectively, as specified in clause 5.22.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If UAS service becomes enabled or disabled (e.g. because the aerial subscription is part of the UE subscription data retrieved from UDM changes), the AMF may include an Indication of UAS services being enabled or disabled in the UE Configuration Update Command. If the UE indicates its support of LADN per DNN and S-NSSAI in the UE MM Core Network Capability during the Registration procedure as specified in clause 4.2.2.2.2, the AMF may include LADN Information per DNN and S-NSSAI. For MBSR (IAB-UE) registered in AMF, the AMF may update the MBSR authorization information as specified in clause 5.35A.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE indicated a support for the Network Slice Replacement feature in the 5GMM Core Network Capability and the AMF determines that an S-NSSAI from an Allowed NSSAI is to be replaced with an Alternative S-NSSAI (as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the AMF includes the Mapping Of Alternative NSSAI within the UE Configuration Update Command to the UE and also adds the Alternative S-NSSAI to the Allowed NSSAI and/or Configured NSSAI, if not already included. If both the UE and the network support unavailability due to discontinuous coverage, the AMF determines this Maximum Time Offset as described in clause 5.4.13.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF includes the Maximum Time Offset within the UE Configuration Update Command to the UE. 2a. If the UE Configuration Update Indication requires acknowledgement of the UE Configuration Update Command, then the UE shall send a UE Configuration Update complete message to the AMF. The AMF should request acknowledgement for all UE Configuration Updates, except when only NITZ is provided. If Registration procedure is not required, steps 3a, 3b, 3c and step 4 are skipped. If the Configuration Update Indication is included in the UE Configuration Update Command message and it requires a Registration procedure, depending on the other NAS parameters included in the UE Configuration Update command, the UE shall execute steps 3a or 3b or 3c+4 as applicable. If the PLMN-assigned UE Radio Capability ID is included in step1, the AMF stores the UE Radio Capability ID in UE context if receiving UE Configuration Update complete message. If the UE receives PLMN-assigned UE Radio Capability ID deletion indication in step 1, the UE shall delete the PLMN-assigned UE Radio Capability ID(s) for this PLMN. If UE Configuration Update is only for this purpose, the following steps are skipped. 2b. [Conditional] The AMF also uses the Nudm_SDM_Info service operation to provide an acknowledgment to UDM that the UE received CAG information as part of the Mobility Restrictions (if the CAG information was updated), or the Network Slicing Subscription Change Indication (if this was indicated in step 1) and acted upon it. 2c. [Conditional] If the AMF has reconfigured the 5G-GUTI over 3GPP access, the AMF informs the NG-RAN of the new UE Identity Index Value (derived from the new 5G-GUTI) when the AMF receives the acknowledgement from the UE in step 2a. [Conditional] If the UE is registered to the same PLMN via both 3GPP and non-3GPP access and if the AMF has reconfigured the 5G-GUTI over non-3GPP access and the UE is in CM-CONNECTED state over 3GPP access, then the AMF informs the NG-RAN of the new UE Identity Index Value (derived from the new 5G-GUTI) when the AMF receives the acknowledgement from the UE in step 2a. [Conditional] If the AMF has configured the UE with a PLMN-assigned UE Radio Capability ID, the AMF informs NG-RAN of the UE Radio Capability ID, when it receives the acknowledgement from the UE in step 2a. [Conditional] If the Mobility Restrictions for the UE were updated and the Mobility Restrictions were not provided in the N2 message that delivers the UE Configuration Update Command, the AMF provides the NG-RAN with updated Mobility Restrictions unless the AMF releases the UE in this step (see below). If the AMF initiated the UE Configuration Update procedure due to receiving Nudm_SDM_Notification and the CAG information has changed such that a CAG Identifier has been removed from the Allowed CAG list or the UE is only allowed to access CAG cells, the AMF shall release the NAS signalling connection by triggering the AN Release procedure for UEs that are not receiving Emergency Services as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the AMF need to update Allowed CAG list to the NG-RAN due to change of validity condition as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], the AMF may either update NG-RAN and keep the NAS signalling connection or release the NAS signalling connection by triggering the AN Release procedure, without updating Allowed CAG list to the NG-RAN, for the UEs that are not receiving Emergency Services as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 3: If validity condition needs to be applied immediately before the NG-RAN enforces Allowed CAG list, the AMF can trigger AN Release without sending updated Allowed CAG list to the NG-RAN. NOTE 4: When the UE is accessing the network for emergency service the conditions in clause 5.16.4.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] apply. 2d [Conditional] If the UE is configured with a new 5G-GUTI in step 2a via non-3GPP access and the UE is registered to the same PLMN via both 3GPP and non-3GPP access, then the UE passes the new 5G-GUTI to its 3GPP access' lower layers. If the UE is configured with a new 5G-GUTI in step 2a over the 3GPP access, the UE passes the new 5G-GUTI to its 3GPP access' lower layers. NOTE 5: Steps 2c and 2d are needed because the NG-RAN may use the RRC_INACTIVE state and a part of the 5G-GUTI is used to calculate the Paging Frame (see TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [44] and TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [43]). It is assumed that the UE Configuration Update Complete is reliably delivered to the AMF after the 5G-AN has acknowledged its receipt to the UE. 3a. [Conditional] If only NAS parameters that can be updated without transition from CM-IDLE are included (e.g. MICO mode, Enhanced Coverage Restricted information) the UE shall initiate a Registration procedure immediately after the acknowledgement to re-negotiate the updated NAS parameter(s) with the network. Steps 3b, 3c and step 4 are skipped. 3b. [Conditional] If a new Allowed NSSAI and/or a new Mapping Of Allowed NSSAI and/or Partially Allowed NSSAI and/or Mapping Of Partially Allowed NSSAI and/or a new Configured NSSAI provided by the AMF to the UE in step 1 does not affect the existing connectivity to AMF, the AMF needs not release the NAS signalling connection for the UE after receiving the acknowledgement in step 2 and immediate registration is not required. The UE can start immediately using the new Allowed NSSAI and/or the new Mapping Of Allowed NSSAI and/or Partially Allowed NSSAI and/or Mapping Of Partially Allowed NSSAI. If one or more PDU Sessions use a S-NSSAI that is not part of the new Allowed NSSAI or Partially Allowed NSSAI, the AMF indicates to the SMF(s) the corresponding PDU Session ID(s) and each SMF releases the PDU Session(s) according to clause 4.3.4.2. The UE cannot connect to an S-NSSAI included in the new Configured NSSAI for the Serving PLMN but not included in the new Allowed NSSAI or Partially Allowed NSSAI until the UE performs a Registration procedure and includes a Requested NSSAI based on the new Configured NSSAI, following the requirements described in clause 5.15.5.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Steps 3c and 4 are skipped. The AMF may, based on its policy, provide anyway an indication that a Registration procedure is required even though the UE Configuration Update Command in step 1 does not affect the existing connectivity to Network Slices: in such a case only step 3c is skipped. 3c. [Conditional] If a new Allowed NSSAI and/or a new Mapping Of Allowed NSSAI and/or Partially Allowed NSSAI and/or Mapping Of Partially Allowed NSSAI and/or a new Configured NSSAI provided by the AMF to the UE in step 1 affects ongoing existing connectivity to AMF, then the AMF shall provide an indication that the UE shall initiate a Registration procedure. 4. [Conditional] After receiving the acknowledgement in step 2, the AMF shall release the NAS signalling connection for the UE by triggering the AN Release procedure, unless there is one established PDU Sessions associated with regulatory prioritized services. If there is one established PDU Session associated with regulatory prioritized services, the AMF informs SMFs to release the PDU Session(s) associated with non regulatory prioritized services for this UE (see clause 4.3.4). The AMF shall reject any NAS Message from the UE carrying PDU Session Establishment Request for a non-emergency PDU Session before the required Registration procedure has been successfully completed by the UE. The UE initiates a Registration procedure (see clauses 4.2.2.2.2 and 4.13.3.1) with registration type Mobility Registration Update after the UE enters CM-IDLE state and shall not include the 5G-S-TMSI or GUAMI in Access Stratum signalling and shall include, subject to the conditions set out in clause 5.15.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], a Requested NSSAI in access stratum signalling. If there is an established PDU Session associated with emergency service and the UE has received an indication to perform the Registration procedure, the UE shall initiate the Registration procedure only after the PDU Session associated with emergency service is released. NOTE 6: Receiving UE Configuration Update command without an indication requesting to perform re-registration, can still trigger Registration procedure by the UE for other reasons. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.4.2 |
3,115 | 8.7.5.1 Minimum Requirement FDD PCell | For UE not supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1-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.1-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.1-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 the maximum aggregated bandwidth as specified in Table 8.7.5.1-4. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.5.1-1 is not applicable. The applicability of the 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.1-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM) Table 8.7.5.1-2: Test points for sustained data rate (FRC 64QAM) Table 8.7.5.1-3: Minimum requirement (TDD FDD CA 256QAM) Table 8.7.5.1-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.1 |
3,116 | 4.3.6 Radio Resource Management functions | Radio resource management functions are concerned with the allocation and maintenance of radio communication paths, and are performed by the radio access network. RRM includes both idle mode and connected mode. The RRM strategy in E-UTRAN may be based on user specific information. To support radio resource management in E-UTRAN the MME provides the parameter 'Index to RAT/Frequency Selection Priority' (RFSP Index) to an eNodeB across S1. The RFSP Index is mapped by the eNodeB to locally defined configuration in order to apply specific RRM strategies. The RFSP Index is UE specific and applies to all the Radio Bearers. Examples of how this parameter may be used by the E-UTRAN: - to derive UE specific cell reselection priorities to control idle mode camping. - to decide on redirecting active mode UEs to different frequency layers or RATs. To provide additional support to radio resource management in E-UTRAN, the MME may provide the parameter 'Additional RRM Policy Index' (ARPI) to an eNodeB across S1. The ARPI is mapped by the eNodeB to locally defined configuration in order to apply specific RRM strategies. An example of how this parameter may be used by the E-UTRAN is: - to prioritise the allocation of RAN resources to the set of UEs with the same ARPI. The Serving PLMN can use the ARPI to carry information that is independent to the Reference SPID values documented in Informative Annex I of TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. The MME receives the subscribed RFSP Index and subscribed ARPI from the HSS (e.g., during the Attach procedure). For non-roaming subscribers the MME chooses the RFSP Index and ARPI in use according to one of the following procedures, depending on operator's configuration: - the RFSP Index in use is identical to the subscribed RFSP Index, or - the MME chooses the RFSP Index in use based on the subscribed RFSP Index, the locally configured operator's policies and the UE related context information available at the MME, including UE's usage setting and voice domain preference for E-UTRAN, if received during Attach and Tracking Area Update procedures (see clause 4.3.5.9). NOTE: One example of how the MME can use the "UE voice capabilities and settings" is to select an RFSP value that enforces idle mode camping on 2G/3G for a UE acting in a "Voice centric" way and provisioned with "CS Voice preferred, IMS Voice as secondary", in order to minimize the occurrancy of RAT changes. Another example is the selection of an RFSP value that prevents idle mode camping on 2G for a UE provisioned with "IMS PS voice preferred, CS Voice as secondary" if other RATs supporting IMS Voice are available, as the UE would in such case always select the CS domain for its voice calls. - the ARPI In Use is identical to the subscribed ARPI, or - the MME chooses the ARPI in use based on the subscribed ARPI, the locally configured operator's policies and the UE related context information available at the MME. For roaming subscribers the MME may alternatively choose the RFSP Index and ARPI in use based on the visited network policy, but can take input from the HPLMN into account (e.g., an RFSP Index value/ARPI value pre-configured per HPLMN, or a single RFSP Index value/single ARPI value to be used for all roamers independent of the HPLMN). The MME forwards the RFSP Index and ARPI in use to the eNodeB across S1. The RFSP Index and ARPI in use is also forwarded from source eNodeB to target eNodeB when X2 is used for intra-E-UTRAN handover, UE context retrieval, or, Dual Connectivity with a secondary RAN node. The MME stores the subscribed RFSP Index and ARPI values received from the HSS and the RFSP Index and ARPI values in use. During the Tracking Area Update procedure, the MME may update the RFSP Index/ARPI value in use (e.g. the MME may need to update the RFSP Index/ARPI value in use if the UE related context information in the MME has changed). When the RFSP Index/ARPI value in use is changed, the MME immediately provides the updated RFSP Index/ARPI value in use to eNodeB by modifying an existing UE context or by establishing an new UE context in the eNodeB or by being configured to include the updated RFSP Index/ARPI value in use in the DOWNLINK NAS TRANSPORT message if the user plane establishment is not needed. During inter-MME mobility procedures, the source MME forwards both RFSP Index values and both ARPI values to the target MME. The target MME may replace the received RFSP Index and ARPI values in use with a new RFSP Index value in use or new ARPI value in use that is based on the operator's policies and the UE related context information available at the target MME. The S1 messages that transfer the RFSP Index and ARPI to the eNodeB are specified in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. Refer to TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] for further information on E-UTRAN. To support a RAN with a mixture of RAN nodes that support and do not support the ARPI, the MME sends the ARPI In Use in the S1 interface PATCH SWITCH ACKNOWLEDGEMENT and HANDOVER REQUEST messages. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.6 |
3,117 | 6.1.5 Overall Architecture of NR MBS | The overall architecture specified in clause 6.1.1 and 6.1.2 applies for NR MBS. Upon establishment of a MBS Session resource by the 5GC, the gNB-CU triggers the establishment of MRBs, involving the gNB-DU. If E1 is deployed, the gNB-CU-CP triggers establishment of respective MBS UP resources in the gNB-CU-UP. The gNB-DU assigns the G-RNTI. A shared F1-U tunnel is used between the gNB-CU and the gNB-DU forMRB with PTM transmission. UE dedicated F1-U tunnels are used between the gNB-CU and the gNB-DU for data transmission of PTP retransmission and PTP forwarding of an MRB. For an MRB configured with PTP only transmission either a shared F1-U or a UE dedicated F1-U tunnel is used, dependent on the lower layer configuration. The gNB-DU assigns the DL GTP-U TEID and provides it to the gNB-CU. If E1 is deployed the gNB-CU-CP forwards it to the gNB-CU-UP. For both broadcast and multicast, DL flow control maybe used for the shared F1-U tunnel established for the MRB, as specified in TS 38.425[ NG-RAN; NR user plane protocol ] [24]. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 6.1.5 |
3,118 | – NTN-Parameters | The IE NTN-Parameters is used to convey the subset of UE Radio Access Capability Parameters that apply to NTN access when there is a difference compared to TN access. NTN-Parameters information element -- ASN1START -- TAG-NTN-PARAMETERS-START NTN-Parameters-r17 ::= SEQUENCE { inactiveStateNTN-r17 ENUMERATED {supported} OPTIONAL, ra-SDT-NTN-r17 ENUMERATED {supported} OPTIONAL, srb-SDT-NTN-r17 ENUMERATED {supported} OPTIONAL, measAndMobParametersNTN-r17 MeasAndMobParameters OPTIONAL, mac-ParametersNTN-r17 MAC-Parameters OPTIONAL, phy-ParametersNTN-r17 Phy-Parameters OPTIONAL, fdd-Add-UE-NR-CapabilitiesNTN-r17 UE-NR-CapabilityAddXDD-Mode OPTIONAL, fr1-Add-UE-NR-CapabilitiesNTN-r17 UE-NR-CapabilityAddFRX-Mode OPTIONAL, ue-BasedPerfMeas-ParametersNTN-r17 UE-BasedPerfMeas-Parameters-r16 OPTIONAL, son-ParametersNTN-r17 SON-Parameters-r16 OPTIONAL } -- TAG-NTN-PARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,119 | 4.26.5.3 SMF Context Transfer procedure, LBO or no Roaming, no I-SMF | In the case of dynamic IP address assignment (IPv4 address and/or IPv6 prefix), the procedure in figure 4.26.4.1.1-1 assumes that, if the UE IP address is received from Old SMF, the control of the IP address(es) assigned by Old SMF is moved to New SMF by O&M procedures. New SMF is in full control of the concerned IP address(es) when the transfer is complete. NOTE 1: If UPF has the IP point of presence from the DNN, the same UPF is used. Figure 4.26.4.1.1-1: Context transfer of a PDU session 1. SM context transfer is triggered, e.g. by OAM to Old SMF including SUPI, PDU session ID and New SMF ID or SMF set ID. The SMF selection by using SMF set ID not applicable when the IP range is managed by SMF. 2. [Conditional - depending on current subscription] Old SMF subscribes to events when UE status becomes CM-IDLE or CM-CONNECTED with RRC_INACTIVE state (Namf_EventExposure_Subscribe). 3. [Conditional - depending on the event] The AMF detects the monitored event occurs and sends the event report by means of Namf_EventExposure_Notify message, to Old SMF. 4. From Old SMF to AMF Nsmf_PDUSession_SMContextStatusNotify (SMF transfer indication, Old SMF ID, New SMF ID or SMF set ID from Step 1, PDU Session ID, SUPI, SM Context ID). 5. AMF, or SCP if delegated discovery is used, uses New SMF ID or SMF set ID to select New SMF and sends Nsmf_PDUSession_CreateSMContext request (PDU Session ID, Old SMF ID, SM Context ID in Old SMF, UE location info, Access Type, RAT Type, Operation Type, SMF transfer indication). The same PDU Session ID as received in step 4 is used. If the AMF receives the service request from the UE for the PDU session(s) affected by this procedure the AMF delays the transaction with the SMF until the step 13 completes. If the AMF receives the UE context transfer request from the other AMF due to the UE mobility, the AMF defers the response until the step 13 completes. Also, to avoid infinite waiting time, the AMF starts a locally configured guard timer upon sending the request to the SMF and the AMF decides the procedure has failed at expiry of the guard timer. NOTE 2: Either delay or failure of the SM Context transfer may incur timeout or failure in UE procedure(s). 6. From New SMF to Old SMF SMF Nsmf_PDUSession_ContextRequest request (SM Context type, SM Context ID, SMF transfer indication). If New SMF is not capable to transfer this SM Context (e.g. it is not responsible for the IP range), steps 9 to 12 are skipped. 7. Old SMF releases the N4 session with the UPF by sending a flag notifying the UPF about the expected re-establishment of the N4 session for the same PDU session. Based on this, if supported, the UPF should delay the release of the N4 session up to step 10.2 to allow for uninterrupted packet handling until the N4 session is re-established by New SMF. 8. From Old SMF to New SMF Nsmf_PDUSession_ContextRequest response (SM Context or endpoint address where New SMF can retrieve SM Context). The SM Context includes the IP address(es) if the PDU session is of type IPv4, IPv6 or IPv4v6, or the Ethernet MAC address(es) if the PDU session if of type Ethernet as well as the UPF to be selected by New SMF. Old SMF starts a timer to monitor the SMF context transferring process. 9. [Conditional] If dynamic PCC is used for the PDU Session, New SMF sets up a new policy association towards PCF. 10.1. UPF receives a N4 session establishment request for the same PDU session from step 7. The parameters from step 8 and if applies, step 9 are used. 10.2. New SMF performs a full re-establishment of the N4 session, establishing a new N4 session. All information related to the N4 session of Old SMF that is not used by the N4 session of New SMF is removed from UPF if not already done. 11. New SMF registers to UDM. The information stored at the UDM includes SUPI, SMF identity and the associated DNN and PDU Session ID. 12. New SMF subscribes to subscription changes for the UE. 13. From New SMF to AMF: Nsmf_PDUSession_CreateSMContext response. If this response indicates a redirect (e.g. another SMF in the set), the procedure moves to step 5 with the indicated endpoint address as target. 14. UDM notifies Old SMF that it is deregistered for the PDU Session by sending Nudm_UECM_DeregistrationNotification, optionally including New SMF ID 15. [Conditional] If 14 was not received and the timer from step 8 expires, Old SMF re-establishes the N4 session. The UPF may for the purpose use the information stored in step 7. In this case, the procedure ends here. 16. [Conditional] If Nudm_UECM_DeregistrationNotification in step 14 was received, Old SMF removes its policy association with PCF. Any changes to the QoS rules need to be sent to the UE when it becomes active. 17. Old SMF releases any internal resources corresponding to the indicated PDU session. Subscribers to SMContextStatusNotify for the transferred SM context are notified of the context transfer and optionally of the new location of the transferred SM context. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.26.5.3 |
3,120 | 6.2.3 UE maximum output power for modulation / channel bandwidth | For UE Power Class 1, 2 and 3, the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2.2-1due to higher order modulation and transmit bandwidth configuration (resource blocks) is specified in Table 6.2.3-1. Table 6.2.3-1: Maximum Power Reduction (MPR) for Power Class 1, 2 and 3 For PRACH, PUCCH and SRS transmissions, the allowed MPR is according to that specified for PUSCH QPSK modulation for the corresponding transmission bandwidth. For each TTI pattern, the MPR shall be evaluated per Teval period as specified in table 6.2.3-2 and given by the maximum value taken over the transmission(s) within that period; the maximum MPR over TREF is then applied for TREF. Table 6.2.3-2: MPR evaluation period For UE Power Class 1 and 3 transmissions with non-contiguous resource allocation in single component carrier, the allowed Maximum Power Reduction (MPR) for the maximum output power in table 6.2.2-1, is specified as follows MPR = CEIL {MA, 0.5} Where MA is defined as follows for QPSK, 16 QAM and 64 QAM MA = 8.00-10.12A ; 0.00< A ≤ 0.33 5.67 - 3.07A ; 0.33< A ≤0.77 3.31 ; 0.77< A ≤1.00 Where MA is defined as follows for 256 QAM MA = 8.00-10.12A ; 0.00< A ≤ 0.25 5.50 ; 0.25< A < 1.00 Where A = NRB_alloc / NRB. CEIL{MA, 0.5} means rounding upwards to closest 0.5dB, i.e. MPR [3.0, 3.5 4.0 4.5 5.0 5.5 6.0 6.5 7.0 7.5 8.0] The allowed MPR for transmission on an Scell in Band 46 or Band 49 within a component carrier of a nominal channel bandwidth of 10 MHz or 20 MHz is in accordance with 6.2.3-1 for RIV = ‘11111’ (10 MHz) and L = 10 (20 MHz) with L defined in Clause 8.1.4 of [6]. For all other possible values of the RIV defined in Clause 8.1.4 of [6] the allowed MPR is 2.5 dB for QPSK modulation, 3 dB for 16QAM modulation and 4 dB for 64QAM modulation (256QAM is FFS). For a power class 2 capable UE operating on Band 41, when an IE P-max as defined in [7] of 23 dBm or lower is indicated in the cell or if the uplink/downlink configuration is 0 or 6, the requirements for power class 2 are not applicable, and the corresponding requirements for a power class 3 UE shall apply. For each supported frequency band other than Band 14 and Band 41, the UE shall: - if the UE supports a different power class than the default UE power class for the band and the supported power class enables the higher maximum output power than that of the default power class: - if the band is a TDD band whose frame configuration is 0 or 6; or - if the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is not provided; or - if the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is provided and set to the maximum output power of the default power class or lower; - meet all requirements for the default power class of the operating band in which the UE is operating and set its configured transmitted power as specified in sub-clause 6.2.5; - else (i.e the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is provided and set to the higher value than the maximum output power of the default power class): - meet all requirements for the supported power class and set its configured transmitted power class as specified in sub-clause 6.2.5. For UE Power Class 2 transmissions with non-contiguous resource allocation in single component carrier, the allowed Maximum Power Reduction (MPR) for the maximum output power is not specified in this version of the specification. For the UE maximum output power modified by MPR, the power limits specified in subclause 6.2.5 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.3 |
3,121 | A.2 Guidance for planning | From these uses, the following planning rule can be derived: If there exist places where MSs can receive signals from two cells, whether in the same PLMN or in different PLMNs, which use the same BCCH frequency, it is highly preferable that these two cells have different BSICs. Where the coverage areas of two PLMNs overlap, the rule above is respected if: 1) The PLMNs use different sets of BCCH frequencies (In particular, this is the case if no frequency is common to the two PLMNs. This usually holds for PLMNs in the same country), or 2) The PLMNS use different sets of NCCs, or 3) BSIC and BCCH frequency planning is co-ordinated. Recognizing that method 3) is more cumbersome than method 2), and that method 1) is too constraining, it is suggested that overlapping PLMNs which use a common part of the spectrum agree on different NCCs to be used in any overlapping areas. As an example, a preliminary NCC allocation for countries in the European region can be found in clause A.3 of this annex. This example can be used as a basis for bilateral agreements. However, the use of the NCCs allocated in clause A.3 is not compulsory. PLMN operators can agree on different BSIC allocation rules in border areas. The use of BSICs is not constrained in non-overlapping areas, or if ambiguities are resolved by using different sets of BCCH frequencies. If the PLMNs share one or more cells with other PLMNs, the planning rule above should be applied also when the BCCH frequency is different. The rule should be respected by using different sets of NCCs. In addition to that, the PLMN sharing one or more cells with other PLMNs should use different NCCs for shared and non-shared neighbouring cells. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | A.2 |
3,122 | 5.3.5.13.3 Conditional reconfiguration addition/modification | For each condReconfigId received in the condReconfigToAddModList IE the UE shall: 1> if an entry with the matching condReconfigId exists in the condReconfigToAddModList within the VarConditionalReconfig: 2> if the entry in condReconfigToAddModList includes an condExecutionCond, condExecutionCondSCG, or condExecutionCondPSCell; 3> replace condExecutionCond, condExecutionCondSCG, or condExecutionCondPSCell within the VarConditionalReconfig with the value received for this condReconfigId; 2> if the entry in condReconfigToAddModList includes subsequentCondReconfig containing condExecutionCondToAddModList: 3> for each condReconfigId received in condExecutionCondToAddModList: 4> if an entry with the matching condReconfigId exists in the condExecutionCondToAddModList within VarConditionalReconfig; 5> replace the entry in condExecutionCondToAddModList within VarConditionalReconfig with the value received for this condReconfigId; 4> else: 5> add a new entry in condExecutionCondToAddModList within VarConditionalReconfig with the value received for this condReconfigId; 2> if the entry in condReconfigToAddModList includes subsequentCondReconfig containing condExecutionCondToReleaseList: 3> for each condReconfigId received in condExecutionCondToReleaseList that is part of current stored condExecutionCondToAddModList within VarConditionalReconfig: 4> remove the entry in condExecutionCondToAddModList within VarConditionalReconfig with the value received for this condReconfigId; 2> if the entry in condReconfigToAddModList includes an securityCellSetId; 3> replace securityCellSetId within the VarConditionalReconfig with the value received for this condReconfigId; NOTE: The UE should release the entry within VarServingSecurityCellSetID in case all the subsequent CPAC configurations are released. 2> if the entry in condReconfigToAddModList includes an condRRCReconfig; 3> replace condRRCReconfig within the VarConditionalReconfig with the value received for this condReconfigId; 1> else: 2> add a new entry for this condReconfigId within the VarConditionalReconfig; 1> perform conditional reconfiguration evaluation as specified in 5.3.5.13.4; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.13.3 |
3,123 | 5.3.2.3 Reception of the Paging message by the UE or PagingRecord by the L2 U2N Remote UE | Upon receiving the Paging message by the UE or receiving PagingRecord from its connected L2 U2N Relay UE by a L2 U2N Remote UE, the UE shall: 1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message, or 1> if in RRC_IDLE, for the PagingRecord, if any, included in the UuMessageTransferSidelink message received from the connected L2 U2N Relay UE: 2> if the ue-Identity included in the PagingRecord matches the UE identity allocated by upper layers: 3> if upper layers indicate the support of paging cause: 4> forward the ue-Identity, accessType (if present) and paging cause (if determined) to the upper layers; 3> else: 4> forward the ue-Identity and accessType (if present) to the upper layers; NOTE 1: If the L2 U2N Relay UE supports the MUSIM feature, it can forward the paging cause to the connected L2 U2N Remote UE. 1> if in RRC_INACTIVE, for each of the PagingRecord, if any, included in the Paging message, or 1> if in RRC_INACTIVE, for the PagingRecord, if any, included in the UuMessageTransferSidelink message received from the connected L2 U2N Relay UE: 2> if the ue-Identity included in the PagingRecord matches the UE's stored fullI-RNTI: 3> if the UE is configured by upper layers with Access Identity 1: 4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mps-PriorityAccess; 3> else if the UE is configured by upper layers with Access Identity 2: 4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mcs-PriorityAccess; 3> else if the UE is configured by upper layers with one or more Access Identities equal to 11-15: 4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to highPriorityAccess; 3> else if mt-SDT indication was included in the paging message and if the conditions for initiating SDT for a resume procedure initiated in response to RAN paging according to 5.3.13.1b are fulfilled: 4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mt-SDT: 3> else: 4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mt-Access; NOTE 2: If both conditions for initiating MT-SDT and MO-SDT according to 5.3.13.1b are fulfilled, UE may initiate RRC connection resumption procedure for MT-SDT or MO-SDT based on implementation. NOTE 3: A MUSIM UE may not initiate the RRC connection resumption procedure, e.g. when it decides not to respond to the Paging message due to UE implementation constraints as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]. 2> else if the ue-Identity included in the PagingRecord matches the UE identity allocated by upper layers: 3> if upper layers indicate the support of paging cause: 4> forward the ue-Identity, accessType (if present) and paging cause (if determined) to the upper layers; 3> else: 4> forward the ue-Identity and accessType (if present) to the upper layers; 3> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause 'other'; 1> if in RRC_IDLE, for each TMGI included in pagingGroupList, if any, included in the Paging message: 2> if the UE has joined an MBS session indicated by the TMGI included in the pagingGroupList: 3> forward the TMGI to the upper layers; 1> if in RRC_INACTIVE and the UE has joined one or more MBS session(s) indicated by the TMGI(s) included in the pagingGroupList: 2> if the UE is not configured to receive multicast in RRC_INACTIVE or if inactiveReceptionAllowed is not included for at least one of the MBS session (s) indicated by the TMGI(s) that the UE has joined: 3> if PagingRecordList is not included in the Paging message; or 3> if none of the ue-Identity included in any of the PagingRecord matches the UE identity allocated by upper layers or the UE's stored fullI-RNTI: 4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set as below: 5> if the UE is configured by upper layers with Access Identity 1: 6> set resumeCause to mps-PriorityAccess; 5> else if the UE is configured by upper layers with Access Identity 2: 6> set resumeCause to mcs-PriorityAccess; 5> else if the UE is configured by upper layers with one or more Access Identities equal to 11-15: 6> set resumeCause to highPriorityAccess; 5> else: 6> set resumeCause to mt-Access; 3> else if the ue-Identity included in any of the PagingRecord matches the UE identity allocated by upper layers: 4> forward the TMGI(s) to the upper layers; 2> else: 3> start monitoring the G-RNTI(s) corresponding to the TMGI(s), if configured; 3> if the UE was notified to stop monitoring the G-RNTI(s) for all the joined multicast sessions that are configured for reception in RRC_INACTIVE: 4> start monitoring the Multicast MCCH-RNTI; 4> acquire the MBSMulticastConfiguration message on multicast MCCH, if present; 3> else if the UE was notified to stop monitoring the G-RNTI for at least one multicast session for which the PTM configuration was not included in RRCRelease message: 4> acquire the MBSMulticastConfiguration message on multicast MCCH; 1> if the UE is acting as a L2 U2N Relay UE, for each of the PagingRecord, if any, included in the Paging message: 2> if the ue-Identity included in the PagingRecord in the Paging message matches the UE identity in sl-PagingIdentityRemoteUE included in sl-PagingInfo-RemoteUE received in RemoteUEInformationSidelink message from a L2 U2N Remote UE: 3> inititate the Uu Message transfer in sidelink to that UE as specified in 5.8.9.9; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.2.3 |
3,124 | G.4 Causes related to nature of request | Cause value = 32 Service option not supported This cause is sent when the MS requests a service/facility in the CM SERVICE REQUEST message which is not supported by the PLMN. Cause value = 33 Requested service option not subscribed This cause is sent when the MS requests a service option for which it has no subscription. Cause value = 34 Service option temporarily out of order This cause is sent when the MSC cannot service the request because of temporary outage of one or more functions required for supporting the service. Cause value = 38 Call cannot be identified This cause is sent when the network cannot identify the call associated with a call re-establishment request. | 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.4 |
3,125 | 5.2.6.11.3 Nnef_ServiceParameter_Update operation | Service operation name: Nnef_ServiceParameter_Update Description: The consumer updates service specific parameters in the UDR via the NEF. Inputs, Required: Service Descriptor (e.g. the combination of DNN and S-NSSAI, an AF-Service-Identifier or an External Application Identifier), Transaction Reference ID. Inputs, Optional: Service Parameters and Target UE identifiers (e.g. the address (IP or Ethernet) of the UE if available, GPSI if available, External Group Identifier if available), or "PLMN ID(s) of inbound roamers". 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.11.3 |
3,126 | 4.23.9.1 Addition of PDU Session Anchor and Branching Point or UL CL controlled by I-SMF | This clause describes a procedure to add a PDU Session Anchor and Branching Point or UL CL controlled by I-SMF. Figure 4.23.9.1-1: Addition of PDU Session Anchor and Branching Point or UL CL controlled by I-SMF 1. UE has an established PDU Session with a UPF including the PDU Session Anchor 1, which is controlled by SMF.The I-SMF and an I-UPF controlled by I-SMF have already been inserted for the PDU Session. Events described in item 1 and 2 of clause 4.23.9.0 have taken place. 2. At some point, using the list of DNAI(s) of interest for this PDU Session received from the SMF, the I-SMF decides to establish a new PDU Session Anchor e.g. due to UE mobility. The I-SMF selects a UPF and using N4 establishes the new PDU Session Anchor 2 (PSA2) of the PDU Session. During this step: - (if needed) the PSA2 CN Tunnel Info of the local N9 termination on the PSA2 may be determined, - In the case of IPv6 multi-homing applies to the PDU Session, a new IPv6 prefix corresponding to PSA2 is allocated by the I-SMF or by the UPF supporting the PSA2. 3. The I-SMF may select a UPF that will be acting as UL CL or Branching Point and replace the current I-UPF. If a new UPF that will act as UL CL/Branching Point is selected (i.e. the existing I-UPF is replaced), the I-SMF uses N4 establishment to provide the 5G AN Tunnel Info, the PSA1 and (where applicable) PSA2 CN Tunnel Info to the new UPF. NOTE 1: If the Branching Point or UL CL and the PSA2 are co-located in a single UPF then steps 2 and 3 can be merged. 4. The I-SMF invokes Nsmf_PDUSession_Update Request (Indication of UL CL or Branching Point insertion, IPv6 prefix @PSA2, DNAI(s) supported by PSA2, DL Tunnel Info of the new UL CL/Branching Point, if any) to SMF. Whether the UL CL/Branching Point and PSA2 are supported by the same UPF is transparent to the SMF. Multiple local PSAs (i.e. PSA2) may be inserted at one time, each corresponds to a DNAI and/or an IPv6 prefix in the case of multi-homing. The I-SMF informs the SMF that a UL CL or Branching Point is inserted, the I-SMF provides DNAI(s) supported by PSA2 to the SMF. The DL Tunnel Info of UL CL/Branching Point is provided to SMF if a new UPF is selected to replace I-UPF in step 3. In the case of IPv6 multi-homing PDU Session, the IPv6 prefix @PSA2 is also provided to SMF. The SMF performs the Session Management Policy Modification procedure as defined in clause 4.16.5 to provide the new allocated IPv6 prefix to the PCF. The SMF may also send a notification to the AF, as described in clause 4.3.6.3. The DNAI(s) supported by PSA2 may be used by the SMF to determine which PCC rules are to be applied at UPF(s) controlled by the I-SMF. The SMF acknowledges the Nsmf_PDUSession_Update from the I-SMF 5. If a new DL Tunnel Info of UL CL/ Branching Point has been provided in step 4, the SMF updates the PSA1 via N4 with the CN Tunnel Info for the downlink traffic. Now the downlink packets from PSA1 are sent to UE via the new UPF which will act as Branching Point/UL CL. The SMF may also update the forwarding rules in PSA1 if some traffic is to be moved to UPFs controlled by I-SMF. 6. The SMF provides I-SMF with N4 information for the PSA and for the UL CL with a SMF initiated Nsmf_PDUSession_Update Request (set of (N4 information, involved DNAI), Indication of no DNAI change, Indication of no local PSA change)). The SMF generates N4 information for local traffic handling based on PCC rules and CHF requests that will be enforced by UPFs controlled by I-SMF. The N4 information for local traffic handling corresponds to N4 rules (PDR, FAR, URR, QER, etc.) related with the support of a DNAI. This is described in clause 5.34.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. N4 information for local traffic handling may indicate information (as the 5G AN Tunnel Info) that the SMF does not know and that the I-SMF needs to determine itself to build actual rules sent to the UPF(s). If the rule is applied to the local PSA, the N4 information includes the associated DNAI. If the "Indication of application relocation possibility" or "UE IP address preservation indication" attributes are included in the PCC rule, the SMF includes the corresponding Indication of no DNAI change and Indication no local PSA change respectively. If the CN Tunnel Info at the PSA1 has changed, the SMF may also provide its new value. The I-SMF uses N4 information for local traffic handling received from the SMF as well as 5G AN Tunnel Info received from the 5G AN via the AMF and local configuration to determine N4 rules to send to the UPF(s) it is controlling. 7. The I-SMF updates the PSA2 via N4 providing N4 rules determined in step 6. It also provides the Branching Point or UL CL CN Tunnel Info for down-link traffic if the PSA2 and the UL CL/Branching Point are supported by different UPF(s). 8. The I-SMF updates the Branching Point or UL CL via N4 providing N4 rules determined in step 6. NOTE 2: If the Branching Point or UL CL and the PSA2 are co-located in a single UPF then step 7 and step 8 can be merged. 9. The I-SMF Issues a Nsmf_PDUSession_Update Response to SMF that may include N4 information received from the local UPF(s). 10. Steps 6-8 of clause 4.3.5.4 are performed. In the case of IPv6 multi-homing PDU Session, the SMF notifies the UE of the IPv6 prefix @PSA2 and updates the UE with IPv6 multi-homed routing rule via a PSA controlled by the SMF. NOTE 3: Step 6 of clause 4.3.5.4 is skipped if the current I-UPF is selected to act as Branching Point or UL CL. 11. If a new UPF is selected to replace I-UPF in step 3, the I-SMF uses N4 Release to remove the I-UPF of the PDU Session. The I-UPF releases resources for the PDU Session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.9.1 |
3,127 | 5.5.4.18 Event X2 (Serving L2 U2N Relay UE becomes worse than threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition X2-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition X2-2, as specified below, is fulfilled; Inequality X2-1 (Entering condition) Mr + Hys < Thresh Inequality X2-2 (Leaving condition) Mr – Hys > Thresh The variables in the formula are defined as follows: Mr is the measurement result of the serving L2 U2N Relay UE, not taking into account any offsets. Hys is the hysteresis parameter for this event. Thresh is the threshold parameter for this event (i.e. x2-Threshold-Relay as defined within reportConfigNR for this event). Mr is expressed in dBm. Hys are expressed in dB. Thresh is expressed in the same unit as Mr. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.18 |
3,128 | 9.11.4.29 Remote UE context list | The purpose of the Remote UE context list information element is to provide identity and optionally IP address of a 5G ProSe remote UE connected to, or disconnected from, a UE acting as a 5G ProSe layer-3 UE-to-network relay. The Remote UE context list information element is coded as shown in figure 9.11.4.29.1, figure 9.11.4.29.2, table 9.11.4.29.1 and table 9.11.4.29.2. The Remote UE context list is a type 6 information element with a minimum length of 16 octets and a maximum length of 65538 octets. Figure 9.11.4.29.1: Remote UE context list Table 9.11.4.29.1: Remote UE context list Figure 9.11.4.29.2: Remote UE context Table 9.11.4.29.2: Remote UE context | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.29 |
3,129 | 6.3.6 Reporting authentication failures from the SGSN/VLR to the HLR | The purpose of this procedure is to provide a mechanism for reporting authentication failures from the serving environment back to the home environment. The procedure is shown in Figure 13. Figure 13: Reporting authentication failure from VLR/SGSN to HLR The procedure is invoked by the serving network VLR/SGSN when the authentication procedure fails. The authentication failure report shall contain: 1. Subscriber identity; 2. Failure cause code. The possible failure causes are either that the network signature was wrong or that the user response was wrong; 3. Access type. This indicates the type of access that initiated the authentication procedure; 4. Authentication re-attempt. This indicates whether the failure was produced in a normal authentication attempt or it was due to an authentication reattempt (there was a previous unsuccessful authentication). Details are provided in subclause 6.3.6.1; 5. VLR/SGSN address; 6. . This number uniquely identifies the specific AV that failed authentication. The HE may decide to cancel the location of the user after receiving an authentication failure report and may store the received data so that further processing to detect possible fraud situations could be performed. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3.6 |
3,130 | 6.3.19 DCCF discovery and selection | Multiple instances of DCCF may be deployed in a network. The NF consumers shall utilize the NRF to discover DCCF instance(s) unless DCCF information is available by other means, e.g. locally configured on NF consumers. The DCCF selection function in NF consumers selects a DCCF instance based on the available DCCF instances. The following factors may be considered by the NF consumer for DCCF selection: - DCCF Serving Area information, i.e. list of TAIs for which the DCCF coordinates Data Sources. - S-NSSAI. - NF type of the data source. - NF Set ID of the data source. NOTE: NF Set ID can be used when the NF consumer is a DCCF when the DCCF determines that it needs to discover another DCCF which is responsible for co-ordinating the collection of required data. The DCCF discovers a target DCCF via NRF using NF Set ID of the data source. - DCCF relocation capability: Support for relocating the data collection subscription among DCCFs. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.19 |
3,131 | 18.3 Interconnecting the Presence Network Agent and the GGSN | The Presence Network Agent may be directly attached to the GGSN or via a Radius Proxy. If the GGSN needs to connect both to an AAA server and a Presence Network Agent for the same APN, but supports only a single RADIUS interface, the GGSN can be directly attached to the AAA server. The Presence Network Agent can in turn be attached to the AAA server, which acts as a RADIUS proxy. If the AAA server is configured as a RADIUS Proxy between the Presence Network Agent and the GGSN, the Radius Profile for the Pk Reference Point shall be applicable on the interface between the Presence Network Agent and the AAA server. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 18.3 |
3,132 | 9.11.3.69 UE radio capability ID deletion indication | The purpose of the UE radio capability ID deletion indication information element is to indicate to the UE that deletion of UE radio capability IDs is requested. The UE radio capability ID deletion indication is a type 1 information element. The UE radio capability ID deletion indication information element is coded as shown in figure 9.11.3.69.1 and table 9.11.3.69.1. Figure 9.11.3.69.1: UE radio capability ID deletion indication information element Table 9.11.3.69.1: UE radio capability ID deletion indication 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.69 |
3,133 | 6.4.3 EPS bearer context modification procedure 6.4.3.1 General | The purpose of the EPS bearer context modification procedure is to modify an EPS bearer context with a specific QoS and TFT, or re-negotiate header compression configuration associated to an EPS bearer context. The EPS bearer context modification procedure is initiated by the network, but it may also be initiated as part of the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure. The network may also initiate the EPS bearer context modification procedure to update the APN-AMBR of the UE, for instance after an inter-system handover. See 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] annex E. The MME may also initiate the EPS bearer context modification procedure to update the WLAN offload indication to the UE, for instance after the MME received an updated WLAN offload indication of a PDN Connection from HSS. See 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] clause 4.3.23. The MME may also initiate the EPS bearer context modification procedure to update information required for inter-system change from S1 mode to N1 mode (e.g. session-AMBR, QoS rule(s)). See 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]. The network may initiate the EPS bearer context modification procedure together with the completion of the service request procedure. The network may initiate the EPS bearer context modification procedure to initiate the procedure for the UUAA-SM for the UAS services. The network may initiate the EPS bearer context modification procedure to enable transport of a UE policy container with the length of two octets from the network to the UE and a related UE policy container with the length of two octets from the UE to the network. The UE policy containers with the length of two octets enable transfer of messages of the network-requested UE policy management procedure as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.3 |
3,134 | 5.3.8 Handling of timer T3502 | The value of timer T3502 can be sent by the network to the UE in the REGISTRATION ACCEPT message. The UE shall apply this value in all tracking areas of the registration area assigned to the UE, until a new value is received. The value of timer T3502 can be sent by the network to the UE in the REGISTRATION REJECT message during the initial registration. If a REGISTRATION REJECT message including timer T3502 value was received integrity protected, the UE shall apply this value until a new value is received with integrity protection or a new PLMN or SNPN is selected. Otherwise, the default value of this timer is used. The default value of this timer is also used by the UE in the following cases: a) REGISTRATION ACCEPT message is received without a value specified, and the 5GS registration type IE in the REGISTRATION REQUEST message is not set to "periodic registration updating”; b) the UE does not have a stored value for this timer; c) a new PLMN which is not in the list of equivalent PLMNs or a new SNPN has been entered, the initial registration procedure fails, the registration attempt counter is equal to 5 and no REGISTRATION REJECT message was received from the new PLMN or SNPN; d) the network indicates that the timer is "deactivated"; or e) a new PLMN which is not in the list of equivalent PLMNs or a new SNPN has been entered, the registration procedure for mobility and periodic registration update fails and the registration attempt counter is equal to 5. | 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.8 |
3,135 | 6.4.5 Handling of NAS COUNTs | The NAS security context created at the registration time of the first access type contains the NAS integrity and encryption keys, selected algorithm common for all NAS connections. In addition, each NAS connection shall have a unique NAS connection identifier, a distinct pair of NAS COUNTs, one NAS COUNT for uplink and one NAS COUNT for downlink, associated with it. In the NAS security context, the NAS connection identifier shall be the differentiator for the connection-specific parameters. It is essential that the NAS COUNTs for a particular KAMF are not reset to the start values (that is the NAS COUNTs only have their start value when a new KAMF is generated). This prevents the security issue of using the same NAS COUNTs with the same NAS keys, e.g. key stream re-use, in the case a UE moves back and forth between two AMFs and the same NAS keys are re-derived. In the AMF, all the distinct pairs of NAS COUNTs part of the same 5G NAS security context, shall only be set to the start value in the following cases: - for a partial native 5GC NAS security context created by a successful primary authentication run on one of the NAS connections established between the same AMF and the UE, or, - for a mapped 5G security context generated when a UE moves from an MME to the AMF during both idle and connected mode mobility, or, - for a new KAMF taken into use in a target AMF during mobility registration update or handover. The start value of NAS COUNT shall be zero (0). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.5 |
3,136 | 8.13.3.6.1 Minimum Requirement for FDD PCell | The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD CA with FDD PCell and 2DL CCs, the requirements are specified in Table 8.13.3.6.1-4 based on single carrier requirement specified in Table 8.13.3.6.1-2 and Table 8.13.3.6.1-3, with the addition of the parameters in Table 8.13.3.6.1-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.3.6.1-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.3.6.1-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD PCell and SCell (FRC) Table 8.13.3.6.1-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD SCell (FRC) Table 8.13.3.6.1-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.3.6.1 |
3,137 | 6.4.2.3 Dedicated EPS bearer context activation accepted by the UE | Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, if the UE provided an APN for the establishment of the PDN connection, the UE shall stop timer T3396, if it is running for the APN provided by the UE. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop the timer T3396 associated with no APN if it is running. If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message was received for an emergency PDN connection, the UE shall not stop the timer T3396 associated with no APN if it is running. For any case, the UE shall then check the received TFT before taking it into use, send an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message and enter the state BEARER CONTEXT ACTIVE. The ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message shall include the EPS bearer identity. The linked EPS bearer identity included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message indicates to the UE to which default bearer, IP address and PDN the dedicated bearer is linked. If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]), the UE uses the PTI to identify the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure to which the dedicated bearer context activation is related. If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]) and the PTI is associated to a UE requested bearer resource allocation procedure or a UE requested bearer resource modification procedure, the UE shall release the traffic flow aggregate description associated to the PTI value provided. The UE shall use the received TFT to apply mapping of uplink traffic flows to the radio bearer. The UE shall treat any packet filter without explicit direction as being bi-directional. If the UE receives an APN rate control parameters container in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall store the APN rate control parameters value and use the stored APN rate control parameters value as the maximum allowed limit of uplink user data related to the corresponding APN in accordance with 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the UE has a previously stored APN rate control parameters value for this APN, the UE shall replace the stored APN rate control parameters value for this APN with the received APN rate control parameters value. If the UE receives an additional APN rate control parameters for exception data container in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall store the additional APN rate control parameters for exception data value and use the stored additional APN rate control parameters for exception data value as the maximum allowed limit of uplink exception data related to the corresponding APN in accordance with 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the UE has a previously stored additional APN rate control parameters for exception data value for this APN, the UE shall replace the stored additional APN rate control parameters for exception data value for this APN with the received additional APN rate control parameters for exception data value. If the UE receives a small data rate control parameters container in the Protocol configuration options IE or the Extended protocol configuration options IE in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall store the small data rate control parameters value and use the stored small data rate control parameters value as the maximum allowed limit of uplink user data for the corresponding PDU session that becomes transferred after inter-system change from S1 mode to N1 mode in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58]. If the UE has a previously stored small data rate control parameters value for this PDU session, the UE shall replace the stored small data rate control parameters value for this PDU Session with the received small data rate control parameters value. If the UE receives an additional small data rate control parameters for exception data container in the protocol configuration options IE or the extended protocol configuration options IE in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall store the additional small data rate control parameters for exception data value and use the stored additional small data rate control parameters for exception data value as the maximum allowed limit of uplink exception data for the corresponding PDU session that becomes transferred after inter-system change from S1 mode to N1 mode in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58]. If the UE has a previously stored additional small data rate control parameters for exception data value for this PDU session, the UE shall replace the stored additional small data rate control parameters for exception data value for this PDU session with the received additional small data rate control parameters for exception data value. If the UE receives QoS rule(s) of the 5GS QoS flow(s), which corresponds to the dedicated EPS bearer being activated, in the Protocol configuration options IE or the Extended protocol configuration options IE of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE stores the QoS rule(s) for use during inter-system change from S1 mode to N1 mode. Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, if the UE indicated the URSP provisioning in EPS support indicator as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] in the UE requested PDN connectivity procedure establishing the PDN connection, and the UE policy container with the length of two octets as defined in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] is included in the Extended protocol configuration options IE of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message: a) the UE shall forward the UE policy container with the length of two octets to the UE policy delivery service (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D); and b) upon receipt of a UE policy container with the length of two octets from the UE policy delivery service, the UE shall include the UE policy container with the length of two octets from the UE policy delivery service in the Extended protocol configuration options IE of the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. Editor's note: (WI: eUEPO, CR: 3936) URSP provisioning in EPS in a PDN connection interworked from a PDU session, is FFS. Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message, the MME shall stop the timerT3485 and enter the state BEARER CONTEXT ACTIVE. | 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.3 |
3,138 | 5.4.2.5 NAS security mode command not accepted by the UE | If the security mode command cannot be accepted, the UE shall send a SECURITY MODE REJECT message. The SECURITY MODE REJECT message contains a 5GMM cause that typically indicates one of the following cause values: #23 UE security capabilities mismatch. #24 security mode rejected, unspecified. If the UE detects that the received Replayed UE security capabilities IE has been altered compared to the latest values that the UE sent to the network, the UE shall set the cause value to #23 "UE security capabilities mismatch". Upon receipt of the SECURITY MODE REJECT message, the AMF shall stop timer T3560. The AMF shall also abort the ongoing procedure that triggered the initiation of the NAS security mode control procedure. Both the UE and the AMF shall apply the 5G NAS security context in use before the initiation of the security mode control procedure, if any, to protect the SECURITY MODE REJECT message and any other subsequent messages according to the rules in subclause 4.4.4 and 4.4.5. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.2.5 |
3,139 | 7.5.2 Create Forwarding Tunnel Response | A Create Forwarding Tunnel Response message shall be sent by a Serving GW to a MME as a response to a Create Forwarding Tunnel Request message. Table 7.5.2-1 specifies the presence requirements and the conditions of the IEs in the message. The Cause value indicates if Data Forwarding Resources has been created in the Serving GW or not. Data Forwarding Resources have not been created in the Serving GW if the Cause differs from "Request accepted". Possible Cause values are specified in Table 8.4-1. Only the Cause IE shall be included in the response if the Cause IE contains another value than "Request accepted". Table 7.5.2-1: Information Elements in a Create Forwarding Tunnel Response | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.5.2 |
3,140 | 5.2.3.3.2 Nudm_SDM_Get service operation | Service Operation name: Nudm_SDM_Get Description: Consumer NF gets the subscription data indicated by the subscription data type input from UDM. The UDM shall check the requested consumer is authorized to get the specific subscription data requested. In the case of NF consumer is SMF, the subscriber data may contain e.g. Allowed PDU Session Type(s), Allowed SSC mode(s), default 5QI/ARP, Subscribed S-NSSAI(s). Inputs, Required: NF ID, Subscription data type(s), Key for each Subscription data type(s). Inputs, Optional: Data Sub Key(s), SoR Update Indicator, AF Identifier (for AF authorisation by the UDM), Disaster Roaming Indicator indicating that Disaster Roaming service is applied, Serving PLMN ID. NOTE: Some subscription data subsets can be specific to the Serving PLMN where the UE is registered (e.g. access and mobility subscription data) as defined in clause 5.2.12.2.1. If the corresponding NF consumer does not include the Serving PLMN ID, the UDM provides the subscription data for the SUPI associated to the HPLMN. If the AMF already has subscription data for the UE but the SoR Update Indicator in the UE context requires the AMF to retrieve SoR information depending on the NAS Registration Type ("Initial Registration" or "Emergency Registration"), the AMF shall include SoR update indicator in the Nudm_SDM_Get depending on the NAS Registration type. Outputs, Required: The consumer NF gets the requested subscription data. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.3.2 |
3,141 | 5.1.3 Requirements for UE in MR-DC | In this specification, the UE considers itself to be in: - EN-DC, if and only if it is configured with nr-SecondaryCellGroupConfig according to TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], and it is connected to EPC, - NGEN-DC, if and only if it is configured with nr-SecondaryCellGroupConfig according to TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], and it is connected to 5GC, - NE-DC, if and only if it is configured with mrdc-SecondaryCellGroup set to eutra-SCG, - NR-DC, if and only if it is configured with mrdc-SecondaryCellGroup set to nr-SCG, - MR-DC, if and only if it is in (NG)EN-DC, NE-DC or NR-DC. NOTE: This use of these terms deviates from the definition in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [41] and other specifications. In TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] , these terms include also the case where the UE is configured with E-UTRA or NR MCG only (i.e. no NR or E-UTRA SCG) but with one or more bearers terminated in a secondary node (i.e. using NR PDCP). The UE in (NG)EN-DC only executes a subclause of clause 5 in this specification when the subclause: - is referred to from a subclause under execution, either in this specification or in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; or - applies to a message received on SRB3 (if SRB3 is established); or - applies to field(s), IE(s), UE variable(s) or timer(s) in this specification that the UE is configured with. When executing a subclause of clause 5 in this specification, the UE follows the requirements in clause 5.1.2 and in all subclauses of this specification applicable to the messages (including processing time requirements), fields, IEs, timers and UE variables indicated in the subclause under execution. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.1.3 |
3,142 | 11.2.1.5 IP Fragmentation Across Gi/Sgi | 3GPP and non-3GPP accesses provide IP services for a MS/UE. The GGSN/P-GW endpoint is a GTPv1-U tunnel (controlled by GTP Gn/Gp or S5/S8/S2a/S2b) or IP tunnel (controlled by S5/S8/S2a/S2b PMIPv6 or employed by a UE with MIPv4 or DSMIPv6). The MTU of the IP tunnel on the MS/UE side of the IP link may be different than the MTU of the IP link connecting the GGSN/P-GW to the PDN. As a result IP packets crossing the Gi/Sgi interface may need to be fragmented. Unnecessary fragmentation should be avoided when possible due to the following; - Fragmentation is bandwidth inefficient, since the complete IP header is duplicated in each fragment. - Fragmentation is CPU intensive since more fragments require more processing at IP endpoints and IP routers. It also requires additional memory at the receiver. - If one fragment is lost, the complete IP packet has to be discarded. The reason is there is no selective retransmission of IP fragments provided in IPv4 or IPv6. To avoid unnecessary fragmenting of IP packets the MS/UE, or a server in an external IP network, may find out the end-to-end MTU by path MTU discovery and hence fragment correctly at the source. IP Fragmentation on Gi/Sgi shall be handled according to IETF RFC 791 [16] and IETF RFC 2460 [49]. The GGSN/P-GW shall enforce the MTU of IP packets to/from the MS/UE based on IETF RFC 791 [16] and IETF RFC 2460 [49]. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.2.1.5 |
3,143 | 6.1.3.9.2 Abnormal cases | The following abnormal cases can be identified: a) Expiry of timers: On the first expiry of the timer T3395, the network shall resend the message DEACTIVATE PDP CONTEXT REQUEST and shall reset and restart the timer T3395. This retransmission is repeated, i.e. on the fifth expiry of the timer T3395, the network shall erase the MBMS context related data for that MS. Figure 6.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MBMS context deactivation procedure | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.9.2 |
3,144 | 4.7.2.5 RA Update procedure for Signalling Connection Re-establishment (Iu mode only) | When the MS receives an indication from the lower layers that the RRC connection has been released with cause "Directed signalling connection re-establishment", see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111], then the MS shall enter PMM-IDLE mode and initiate immediately a normal routing area update procedure (the use of normal or combined procedure depends on the network operation mode in the current serving cell) regardless whether the routing area has been changed since the last update or not. This routing area update procedure shall also be performed or continued if the MS has performed an inter-system change towards GSM, irrespective whether the READY timer is running or the MS is in PMM-IDLE or PMM-CONNECTED mode. | 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.2.5 |
3,145 | 5.2.3.6.3 Nudm_ParameterProvision_Create service operation | Service operation name: Nudm_ParameterProvision_Create Description: The consumer creates a Network Configuration with one or more parameters, a 5G VN group related information (e.g. 5G VN group data, 5G VN membership management), or Multicast MBS related information. Inputs, Required: AF Identifier, Transaction Reference ID(s). Inputs, Optional: GPSI, External Group ID, DNN, S-NSSAI, one or multiple Network Configuration parameters, one or multiple Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or one or multiple Application-Specific Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or ECS Address Configuration Information, or for 5G VN group creation, External Group ID and 5G VN group related information, MTC Provider Information, for Multicast MBS related information, or DNN and S-NSSAI specific Group Parameters. Outputs, Required: Transaction Reference ID(s), Operation execution result indication. Outputs, Optional: Transaction specific parameters, if available; Internal Group ID if the inputs include a new 5G VN configuration. For Multicast MBS related information, refer to TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.6.3 |
3,146 | 5.5.3.2.7 Abnormal cases on the network side | The following abnormal cases can be identified: a) If a lower layer failure occurs before the message TRACKING AREA UPDATE COMPLETE has been received from the UE and a GUTI has been assigned, the network shall abort the procedure, enter EMM-IDLE mode and shall consider both, the old and new GUTI as valid until the old GUTI can be considered as invalid by the network (see clause 5.4.1.4). During this period the network may use the identification procedure followed by a GUTI reallocation procedure if the old GUTI is used by the UE in a subsequent message. The network may page with IMSI if paging with old and new S-TMSI fails. Paging with IMSI causes the UE to re-attach as described in clause 5.6.2.2.2. Additionally, if the TRACKING AREA UPDATE ACCEPT message includes: 1) a different negotiated IMSI offset value assigned to a UE that previously had another negotiated IMSI offset value assigned; 2) no negotiated IMSI offset value assigned to a UE that previously had negotiated IMSI offset value assigned; or 3) a negotiated IMSI offset value assigned to a UE that previously had no negotiated IMSI offset value assigned; for case 1) the network shall use two alternative IMSI values and for case 2) and 3) the network shall use one alternative IMSI value and the IMSI value for paging the UE until one of the two (alternative) IMSI values can be considered as invalid by the network. NOTE 1: As the network assigns a new GUTI when the alternative IMSI value is changed or deleted (see clause 5.5.3.2.4), the network can consider the alternative IMSI value associated with the old GUTI as invalid if the UE responds to the paging with the new GUTI. If the UE supports WUS assistance, the MME supports and accepts the use of WUS assistance and if the TRACKING AREA UPDATE ACCEPT message includes: 1) a different negotiated UE paging probability information for the UE assigned to a UE that previously had another negotiated UE paging probability information for the UE assigned; 2) no negotiated UE paging probability information for the UE assigned to a UE that previously had negotiated UE paging probability information for the UE assigned; or 3) a negotiated UE paging probability information for the UE assigned to a UE that previously had no negotiated UE paging probability information for the UE assigned; for case 1) the network shall use two UE paging probability information for the UE values and for case 2) and 3) the network shall use one UE paging probability information for the UE value for paging the UE until one of the two UE paging probability information for the UE values can be considered as invalid by the network. NOTE 2: As the network assigns a new GUTI when the UE paging probability information for the UE value is changed or deleted (see clause 5.5.3.2.4), the network can consider the UE paging probability information for the UE value associated with the old GUTI as invalid if the UE responds to the paging with the new GUTI. b) Protocol error If the TRACKING AREA UPDATE REQUEST message has been received with a protocol error, the network shall return a TRACKING AREA UPDATE REJECT message with one of the following EMM cause values: #96: invalid mandatory information element error; #99: information element non-existent or not implemented; #100: conditional IE error; or #111: protocol error, unspecified. c) T3450 time-out On the first expiry of the timer, the network shall retransmit the TRACKING AREA UPDATE ACCEPT message and shall reset and restart timer T3450. The retransmission is performed four times, i.e. on the fifth expiry of timer T3450, the tracking area updating procedure is aborted. Both, the old and the new GUTI shall be considered as valid until the old GUTI can be considered as invalid by the network (see clause 5.4.1.4). During this period the network acts as described for case a above. d) TRACKING AREA UPDATE REQUEST received after the TRACKING AREA UPDATE ACCEPT message has been sent and before the TRACKING AREA UPDATE COMPLETE message is received If one or more of the information elements in the TRACKING AREA UPDATE REQUEST message differ from the ones received within the previous TRACKING AREA UPDATE REQUEST message, the previously initiated tracking area updating procedure shall be aborted if the TRACKING AREA UPDATE COMPLETE message has not been received and the new tracking area updating procedure shall be progressed; or If the information elements do not differ for cases other than inter-system change from N1 mode to S1 mode in EMM-IDLE mode with the UE operating in the single-registration mode, then the TRACKING AREA UPDATE ACCEPT message shall be resent and the timer T3450 shall be restarted if a TRACKING AREA UPDATE COMPLETE message is expected. If the information elements do not differ for the case of inter-system change from N1 mode to S1 mode in EMM-IDLE mode with the UE operating in the single-registration mode, the MME should forward the new TRACKING AREA UPDATE REQUEST message which contains the same information elements as the previous TRACKING AREA UPDATE REQUEST message to the source AMF to run the integrity check, obtain the latest mapped EPS security context (to be used to protect any future NAS message sent to the UE) and continue with the new tracking area updating procedure. In these cases, the retransmission counter related to T3450 is not incremented. NOTE 3: Instead of forwarding the new TRACKING AREA UPDATE REQUEST message which contains the same information elements to the source AMF, the MME can decide to initiate an authentication procedure followed by a security mode control procedure to take the new partial native EPS security context into use if the new partial native EPS security context is taken into use successfully, then resend the same TRACKING AREA UPDATE ACCEPT message protected using this new EPS security context. e) More than one TRACKING AREA UPDATE REQUEST received and no TRACKING AREA UPDATE ACCEPT or TRACKING AREA UPDATE REJECT message has been sent If one or more of the information elements in the TRACKING AREA UPDATE REQUEST message differs from the ones received within the previous TRACKING AREA UPDATE REQUEST message, the previously initiated tracking area updating procedure shall be aborted and the new tracking area updating procedure shall be progressed; if the information elements do not differ for cases other than inter-system change from N1 mode to S1 mode in EMM-IDLE mode with the UE operating in the single-registration mode, then the network shall continue with the previous tracking area updating procedure and shall not treat any further this TRACKING AREA UPDATE REQUEST message. If the information elements do not differ for the case of inter-system change from N1 mode to S1 mode in EMM-IDLE mode with the UE operating in the single-registration mode, the MME should forward the new TRACKING AREA UPDATE REQUEST message which contains the same information elements as the previous TRACKING AREA UPDATE REQUEST message to the source AMF to run the integrity check, obtain the latest mapped EPS security context (to be used to protect any future NAS message sent to the UE) and continue with the previous tracking area updating procedure. NOTE 4: Instead of forwarding the new TRACKING AREA UPDATE REQUEST message which contains the same information elements to the source AMF, the MME can decide to initiate an authentication procedure followed by a security mode control procedure to take the new partial native EPS security context into use and, if the new partial native EPS security context is taken into use successfully, use this new EPS security context to protect any future NAS message sent to the UE. f) Lower layers indication of non-delivered NAS PDU due to handover If the TRACKING AREA UPDATE ACCEPT message or TRACKING AREA UPDATE REJECT message could not be delivered due to an intra MME handover and the TAI of the target cell and the TAI of the source cell are the same, then upon successful completion of the intra MME handover the MME shall retransmit the TRACKING AREA UPDATE ACCEPT message or TRACKING AREA UPDATE REJECT message. If a failure of the handover procedure is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the TRACKING AREA UPDATE ACCEPT message or TRACKING AREA UPDATE REJECT message. g) DETACH REQUEST message received before the TRACKING AREA UPDATE ACCEPT message is sent or before the TRACKING AREA UPDATE COMPLETE message (in case of GUTI and/or TMSI was allocated) is received. Detach containing cause "switch off": The network shall abort the signalling for the tracking area updating procedure towards the UE and shall progress the detach procedure as described in clause 5.5.2.2. NOTE 5: Internally in the network, before processing the detach request, the MME can perform the necessary signalling procedures for the tracking area updating procedure before progressing the detach procedure. Detach containing other causes than "switch off": The network shall proceed with the tracking area updating procedure and shall progress the detach procedure after successful completion of the tracking area updating procedure. h) If the TRACKING AREA UPDATE REQUEST message with EPS update type IE indicating "periodic updating" is received by the new MME which does not have the EMM context data related to the subscription, the new MME may send the TRACKING AREA UPDATE REJECT message with EMM cause value #10 "Implicitly detached" | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.3.2.7 |
3,147 | 4.3.16 Local IP Access (LIPA) function | The LIPA function enables a UE connected via a HeNB to access other entities in the same residential/enterprise network without the user plane traversing the mobile operator's network except HeNB subsystem. The Local IP Access is achieved using a Local GW (L-GW) collocated with the HeNB. LIPA is established by the UE requesting a new PDN connection to an APN for which LIPA is permitted, and the network selecting the Local GW associated with the HeNB and enabling a direct user plane path between the Local GW and the HeNB. The HeNB supporting the LIPA function includes the Local GW address to the MME in every INITIAL UE MESSAGE and every UPLINK NAS TRANSPORT control message as specified in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. NOTE 1: The protocol option (i.e. GTP or PMIP) supported on the S5 interface between Local GW and S-GW is configured on the MME. For this release of the specification no interface between the L-GW and the PCRF is specified and there is no support for Dedicated bearers on the PDN connection used for Local IP Access. The Local GW (L-GW) shall reject any UE requested bearer resource modification. The direct user plane path between the HeNB and the collocated L-GW is enabled with a Correlation ID parameter that is associated with the default EPS bearer on a PDN connection used for Local IP Access. Upon establishment of the default EPS bearer the MME sets the Correlation ID equal to the PDN GW TEID (GTP-based S5) or the PDN GW GRE key (PMIP-based S5). The Correlation ID is then signalled by the MME to the HeNB as part of E-RAB establishment and is stored in the E-RAB context in the HeNB. The Correlation ID is used in the HeNB for matching the radio bearers with the direct user plane path connections from the collocated L-GW. If the UE is roaming and if the HSS indicates LIPA roaming allowed for this UE in this VPLMN, then the VPLMN (i.e. MME) may provide LIPA for this UE. Furthermore, in the absence of any LIPA information for the requested APN from the HSS, the VPLMN (i.e MME) shall not provide LIPA. The VPLMN address allowed flag is not considered when establishing a LIPA PDN connection. LIPA is supported for APNs that are valid only when the UE is connected to a specific CSG. LIPA is also supported for "conditional" APNs that can be authorized to LIPA service when the UE is using specific CSG. APNs marked as "LIPA prohibited" or without a LIPA permission indication cannot be used for LIPA. MME shall release a LIPA PDN connection to an APN if it detects that the UE's LIPA CSG authorization data for this APN has changed and the LIPA PDN connection is no longer allowed in the current cell. As mobility of the LIPA PDN connection is not supported in this release of the specification, the LIPA PDN connection shall be released when the UE moves away from H(e)NB. Before starting the handover procedure towards the target RAN, the H(e)NB shall request using an intra-node signalling the collocated L-GW to release the LIPA PDN connection. The H(e)NB determines that the UE has a LIPA PDN connection from the presence of the Correlation ID in the UE (E-)RAB context. The L-GW shall then initiate and complete the release of the LIPA PDN connection using the PDN GW initiated bearer deactivation procedure as per clause 5.4.4.1 or GGSN initiated PDP context deactivation procedure as specified in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. The H(e)NB shall not proceed with the handover preparation procedure towards the target RAN until the UE's (E-)RAB context is clear for the Correlation ID. At the handover, the source MME checks whether the LIPA PDN connection has been released. If it has not been released: - and the handover is the S1-based handover or the Inter-RAT handover, the source MME shall reject the handover. - and the handover is X2-based handover, the MME shall send a Path Switch Request Failure message (see more detail in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) to the target HeNB. The MME performs explicit detach of the UE as described in the MME initiated detach procedure of clause 5.3.8.3. NOTE 2: The direct signalling (implementation dependent) from the H(e)NB to the L-GW is only possible since mobility of the LIPA PDN connection is not supported in this release. During idle state mobility events, the MME/SGSN shall deactivate the LIPA PDN connection when it detects that the UE has moved away from the HeNB. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.16 |
3,148 | 5.2.3.2 CC-Establishment present | In the "CC establishment present" state, the mobile station, upon receipt of the CC-ESTABLISHMENT message, shall stop timer T332. The CC-ESTABLISHMENT message contains information which the mobile station shall use for the subsequent SETUP message (if any) related to this CC-ESTABLISHMENT. The CC-ESTABLISHMENT message shall contain the Setup Container IE. If no CC-ESTABLISHMENT message is received by the call control entity of the mobile station before the expiry of timer T332, then the mobile station shall initiate clearing procedures towards the network using a RELEASE COMPLETE message with cause #102 "recovery on timer expiry" and proceed in accordance with subclause 5.4.2. Upon receipt of a CC-ESTABLISHMENT message the mobile station shall perform checks on the Setup Container IE in order to align the contained information with the mobile's present capabilities and configuration. The "recall alignment procedure" is defined later on in this subclause. If the recall alignment procedure has succeeded, the call control entity of the Mobile Station shall: - form and store the SETUP message for sending later in the "Recall present" state, - acknowledge the CC-ESTABLISHMENT message with a CC-ESTABLISHMENT CONFIRMED message, - start timer T335, and - enter the "CC-establishment confirmed" state. Exception: A busy mobile station which has successfully performed the recall alignment procedure shall respond with a CC-ESTABLISHMENT CONFIRMED message with cause #17 "user busy", and proceed as stated above. For speech calls the mobile station shall indicate all codecs that it supports for UTRAN in the Supported Codec List information element of the CC-ESTABLISHMENT CONFIRMED message. Codecs for GERAN shall be indicated in the Bearer Capability information element. Additionally, if the mobile station supports codecs for GERAN and UTRAN, it shall indicate the codecs for GERAN also in the Supported Codec List information element. A mobile station, for which the recall alignment procedure failed, shall respond with a RELEASE COMPLETE message in accordance with subclause 5.4.2 with the appropriate cause code as indicated in the description of the recall alignment procedure. The SETUP message is constructed from the Setup Container IE received in the CC ESTABLISHMENT MESSAGE. The mobile station shall assume that the Setup Container IE contains an entire SETUP message with the exception of the Protocol Discriminator, Transaction ID and Message Type elements. The mobile station may assume that the contents of the Setup Container IE are the same as were sent from the subscriber in a previous SETUP message of the mobile originating call establishment attempt. The mobile station shall copy the Setup Container to the SETUP message and not modify the contents except as defined in the recall alignment procedure and as defined in exceptions below. The mobile station shall not add other Information Elements to the end of the SETUP message. Exceptions: Bearer Capability IE(s), HLC IE(s) and LLC IE(s) (including Repeat Indicator(s), if there are 2 bearer capabilities), and the Supported Codec List IE require handling as described in the recall alignment procedure below. If the CC Capabilities in the Setup Container IE is different to that supported by the mobile station, the mobile station shall modify the CC Capabilities in the SETUP message to indicate the true capabilities of the mobile station. Facility IE(s) and SS Version IE(s) require handling as described in the recall alignment procedure. Stream Identifier IE requires handling as described in the recall alignment procedure. If no response to the CC-ESTABLISHMENT message is received by the call control entity of the network before the expiry of timer T333, then the network shall initiate clearing procedures towards the called mobile station using a RELEASE COMPLETE message with cause #102 "recovery on timer expiry" and inform all appropriate entities within the network, proceeding in accordance with subclause 5.4.2. Figure 5.7a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Call initiation and possible subsequent responses. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.3.2 |
3,149 | 6.2.1 AMF | The Access and Mobility Management function (AMF) includes the following functionality. Some or all of the AMF functionalities may be supported in a single instance of an AMF: - Termination of RAN CP interface (N2). - Termination of NAS (N1), NAS ciphering and integrity protection. - Registration management. - Connection management. - Reachability management. - Mobility Management. - Lawful intercept (for AMF events and interface to LI System). - Provide transport for SM messages between UE and SMF. - Transparent proxy for routing SM messages. - Access Authentication. - Access Authorization. - Provide transport for SMS messages between UE and SMSF. - Security Anchor Functionality (SEAF) as specified in TS 33.501[ Security architecture and procedures for 5G System ] [29]. - Location Services management for regulatory services. - Provide transport for Location Services messages between UE and LMF as well as between RAN and LMF. - EPS Bearer ID allocation for interworking with EPS. - UE mobility event notification. - S-NSSAIs per TA mapping notification. - Support for Control Plane CIoT 5GS Optimisation. - Support for User Plane CIoT 5GS Optimisation. - Support for restriction of use of Enhanced Coverage. - Provisioning of external parameters (Expected UE Behaviour parameters or Network Configuration parameters). - Support for Network Slice-Specific Authentication and Authorization. - Support for charging. - Controlling the 5G access stratum-based time distribution based on UE's subscription data. - Controlling the gNB's time synchronization status reporting and subscription. NOTE 1: Regardless of the number of Network functions, there is only one NAS interface instance per access network between the UE and the CN, terminated at one of the Network functions that implements at least NAS security and Mobility Management. In addition to the functionalities of the AMF described above, the AMF may include the following functionality to support non-3GPP access networks: - Support of N2 interface with N3IWF/TNGF. Over this interface, some information (e.g. 3GPP Cell Identification) and procedures (e.g. Handover related) defined over 3GPP access may not apply, and non-3GPP access specific information may be applied that do not apply to 3GPP accesses. - Support of NAS signalling with a UE over N3IWF/TNGF. Some procedures supported by NAS signalling over 3GPP access may be not applicable to untrusted non-3GPP (e.g. Paging) access. - Support of authentication of UEs connected over N3IWF/TNGF. - Management of mobility, authentication, and separate security context state(s) of a UE connected via a non-3GPP access or connected via a 3GPP access and a non-3GPP access simultaneously. - Support as described in clause 5.3.2.3 a co-ordinated RM management context valid over a 3GPP access and a Non 3GPP access. - Support as described in clause 5.3.3.4 dedicated CM management contexts for the UE for connectivity over non-3GPP access. - Determine whether the serving N3IWF/TNGF is appropriate based on the slices supported by the N3IWFs/TNGFs as specified in clause 6.3.6 and clause 6.3.12 respectively. NOTE 2: Not all of the functionalities are required to be supported in an instance of a Network Slice. In addition to the functionalities of the AMF described above, the AMF may include policy related functionalities as described in clause 6.2.8 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The AMF uses the N14 interface for AMF re-allocation and AMF to AMF information transfer. This interface may be either intra-PLMN or inter-PLMN (e.g. in the case of inter-PLMN mobility). In addition to the functionality of the AMF described above, the AMF may include the following functionality to support monitoring in roaming scenarios: - Normalization of reports according to roaming agreements between VPLMN and HPLMN (e.g. change the location granularity in a report from cell level to a level that is appropriate for the HPLMN); and - Generation of charging/accounting information for Monitoring Event Reports that are sent to the HPLMN. In addition to the functionality of the AMF described above, the AMF may provide support for Network Slice restriction and Network Slice instance restriction based on NWDAF analytics. In addition to the functionalities of the AMF described above, the AMF may provide support for the Disaster Roaming as described in clause 5.40. In addition to the functionalities of the AMF described above, the AMF may also include following functionalities to support Network Slice Admission Control: - Support of NSAC for maximum number of UEs as defined in clauses 5.15.11.1 and 5.15.11.3. In addition to the functionality of the AMF described above, the AMF may include the following functionality to support SNPNs: - Support for Onboarding of UEs for SNPNs. In addition to the functionalities of the AMF described above, the AMF may also include following functionalities to support satellite backhaul: - Support for reporting satellite backhaul category and its modification based on AMF local configuration to SMF as defined in clause 5.43.4. In addition to the functionalities of the AMF described above, the AMF may provide support for Network Slice instance change for PDU sessions as defined in clause 5.15.5.3. In addition to the functionalities of the AMF described above, the AMF may also support functionalities for Partial Network Slice support in a Registration Area as described in clause 5.15.17. In addition to the functionalities of the AMF described above, the AMF may also include functionalities to support NS-AoS not matching deployed Tracking Areas as described in clause 5.15.18. In addition to the functionalities of the AMF described above, the AMF may also include functionalities to support Network Slice Replacement as described in clause 5.15.19. In addition to the functionalities of the AMF described above, the AMF may also include functionalities to enforce the LADN Service Area per LADN DNN and S-NSSAI for a UE as described in clause 5.6.5a, as well as to enforce the LADN Service Area per LADN DNN for a UE in clause 5.6.5. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.1 |
3,150 | 7.6.2.1 Minimum requirements | The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Tables 7.6.2.1-1 and 7.6.2.1-2. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements only apply for carriers assigned in the paired part. For Table 7.6.2.1-2 in frequency range 1, 2 and 3, up to exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size, where is the number of resource blocks in the downlink transmission bandwidth configuration (see Figure 5.6-1). For these exceptions the requirements of subclause 7.7 Spurious response are applicable. For Table 7.6.2.1-2 in frequency range 4, up to exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size, where is the number of resource blocks in the downlink transmission bandwidth configurations (see Figure 5.6-1) and is the number of resource blocks allocated in the uplink. For these exceptions the requirements of clause 7.7 spurious response are applicable. Table 7.6.2.1-1: Out-of-band blocking parameters Table 7.6.2.1-2: Out of band blocking | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.6.2.1 |
3,151 | 5.3.4B.5 eNodeB Control Plane Relocation Indication procedure | For intra-NB-IoT mobility for UE and MME using Control Plane CIoT EPS Optimisation the eNodeB CP Relocation Indication procedures may be used. The purpose of the eNodeB CP Relocation Indication procedure is to request the MME to authenticate the UE's re-establishment request as described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41], and initiate the establishment of the UE's S1 connection and, if necessary, the S11-U connection after the UE has initiated a RRC Re-establishment procedure in a new eNodeB. More details are defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.4B.5 |
3,152 | 10.1.6.2 Baseband signal generation | The time-continuous random-access signal for symbol group is defined by where , is an amplitude scaling factor in order to conform to the transmit power specified in clause 16.3.1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], , accounts for the difference in subcarrier spacing between the random access preamble and uplink data transmission, and the location in the frequency domain controlled by the parameter is derived from clause 10.1.6.1. The variable is given by Table 10.1.6.2-1. Table 10.1.6.2-1: Random access baseband parameters | 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.1.6.2 |
3,153 | 5.9.6 Data Network Name (DNN) | A DNN is equivalent to an APN as defined in TS 23.003[ Numbering, addressing and identification ] [19]. Both identifiers have an equivalent meaning and carry the same information. The DNN may be used e.g. to: - Select a SMF and UPF(s) for a PDU Session. - Select N6 interface(s) for a PDU Session. - Determine policies to apply to this PDU Session. The wildcard DNN is a value that can be used for the DNN field of Subscribed DNN list of Session Management Subscription data defined in clause 5.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The wildcard DNN can be used with an S-NSSAI for operator to allow the subscriber to access any Data Network supported within the Network Slice associated with the S-NSSAI. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.9.6 |
3,154 | 8.3.1.2 Dual-Layer Spatial Multiplexing | 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.3.1.2-2, with the addition of the parameters in Table 8.3.1.2-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.3.1.2-1: Test Parameters for Testing CDM-multiplexed DM RS (dual layer) with multiple CSI-RS configurations Table 8.3.1.2-2: Minimum performance for CDM-multiplexed DM RS (FRC) with multiple CSI-RS configurations | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.1.2 |
3,155 | 6.4.9.1 Security procedures applied | The security mode procedure shall be applied as part of emergency call establishment, or PS connection establishment for an emergency session, as defined in TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [35]. Thus, integrity protection (and optionally ciphering) shall be applied as for a non-emergency call or non-emergency related PS connection. If authentication of the (U)SIM fails for any reason, the emergency call or PS connection establishment for emergency session shall proceed as in 6.4.9.2 d) below. Once the call, or PS connection, is in progress with integrity protection (and optionally ciphering) applied, failure of integrity checking or ciphering is an unusual circumstance and must be treated in the same manner as other equipment failures, that is, the call, or emergency related PS connection, will terminate. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.9.1 |
3,156 | 5.8.2 Conditions for NR sidelink communication/discovery/positioning operation | The UE shall perform NR sidelink communication/positioning operation only if the conditions defined in this clause are met: 1> if the UE's serving cell is suitable (RRC_IDLE or RRC_INACTIVE or RRC_CONNECTED); and if either the selected cell on the frequency used for NR sidelink communication/discovery/positioning operation belongs to the registered or equivalent PLMN as specified in TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [57] or TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [72] or the UE is out of coverage on the frequency used for NR sidelink communication/discovery/positioning operation as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20] and TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [27]; or 1> if the UE's serving cell (RRC_IDLE or RRC_CONNECTED) fulfils the conditions to support NR sidelink communication/discovery/positioning in limited service state as specified in TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [55]; and if either the serving cell is on the frequency used for NR sidelink communication/discovery/positioning operation or the UE is out of coverage on the frequency used for NR sidelink communication/discovery/positioning operation as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20] and TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [27]; or 1> if the UE has no serving cell (RRC_IDLE). | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.2 |
3,157 | 5.34 Support of deployments topologies with specific SMF Service Areas 5.34.1 General | When the UE is outside of the SMF Service Area, or current SMF cannot serve the target DNAI for the traffic routing for local access to the DN, an I-SMF is inserted between the SMF and the AMF. The I-SMF has a N11 interface with the AMF and a N16a interface with the SMF and is responsible of controlling the UPF(s) that the SMF cannot directly control. The exchange of the SM context and forwarding of tunnel information if needed are done between two SMFs directly without involvement of AMF. Depending on scenario, a PDU Session in non-roaming case or local breakout is either served by a single SMF or served by an SMF and an I-SMF. When a PDU Session is served by both an SMF and an I-SMF, the SMF is the NF instance that has the interfaces towards the PCF and CHF. In this Release of the specification, deployments topologies with specific SMF Service Areas apply only for 3GPP access. The SMF shall release or reject the PDU Session if the DNN of the PDU Session corresponds to a LADN and the I-SMF is inserted to the PDU Session. NOTE 1: This implies that operators need to plan the LADN deployment in such a way that the LADN Service area needs to be within the SMF Service Area, but not across SMFs' Service Areas. NOTE 2: This is to cover the case where the UE is not in or moves out of SMF Service Area and an I-SMF is inserted to the PDU Session e.g. during PDU Session Establishment, Service Request. If the PDU Session is maintained with I-SMF, the SMF is not be able to enforce the LADN Service control, e.g. SMF is not notified in the case of Service Request. Independent of whether deployments topologies with specific SMF Service Areas apply, the SMF may trigger the PDU Session re-establishment to the same DN, if the PDU Session is associated with the SSC mode 2 or SSC mode 3. NOTE 3: SSC mode 2 or SSC mode 3 can be used to optimize SMF location for a PDU Session and/or, depending on deployment, ensure that the UE is always within the service area of the SMF controlling the PDU Session. In this case (when PDU Session continuity over the PLMN is not required) procedures described in this clause are not needed. In this Release, how TSC (as defined in clauses 5.27 and 5.28) is supported for PDU Sessions involving an I-SMF is not specified. In this Release, Redundant User Plane Paths as defined in clause 5.33.2.2 is not supported for PDU Sessions involving an I-SMF. Redundant PDU sessions support as defined in clause 5.33.2.1 is supported for PDU Sessions involving an I-SMF, when different S-NSSAIs are used for the redundant PDU sessions. Redundant User Plane Paths as defined in clause 5.33.2.3 is supported for PDU Sessions involving an I-SMF only if this PDU session is established for a S-NSSAI referring to network instances requiring redundant transmission at transport layer. QoS monitoring (as defined in clause 5.33.3) is supported as long as SMF and not I-SMF initiates the QoS monitoring function. Dynamic CN PDB provisioning (as defined in clause 5.7.3.4) is supported for PDU Sessions involving an I-SMF. In this Release, no dedicated functionality is specified for I-SMF and N16a in order to support NPN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.34 |
3,158 | 5.7.2.2 Initiation | A UE in RRC_CONNECTED or a UE in RRC_INACTIVE during SDT initiates the UL information transfer procedure whenever there is a need to transfer NAS dedicated information. The UE initiates the UL information transfer procedure by sending the ULInformationTransfer message. In addition, an IAB-MT in RRC_CONNECTED initiates the UL information transfer procedure whenever there is a need to transfer F1-C related information. When F1-C related information has to be transferred, the IAB-MT shall initiate the procedure only if SRB2 or split SRB2 is established. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.2.2 |
3,159 | 8.10.1.1.6A Enhanced Performance Requirement Type C - Dual-Layer Spatial Multiplexing | The requirements are specified in 8.10.1.1.6A-2, with the addition of the parameters in 8.10.1.1.6A-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of this test is to verify rank-two performance for full RB allocation upon antenna ports 7 and 8. 8.10.1.1.6A-1: Test Parameters for Testing CDM-multiplexed DM RS (dual layer) with multiple CSI-RS configurations 8.10.1.1.6A-2: Enhanced Performance Requirement Type C for CDM-multiplexed DM RS (FRC) with multiple CSI-RS configurations | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.1.6A |
3,160 | 4.17.5a NF/NF service discovery between SNPN and Credentials Holder hosting AUSF/UDM or between SNPN and DCS hosting AUSF/UDM | Figure 4.17.5a-1: NF/NF service discovery across SNPN and Credentials Holder In the case of a UE accessing SNPN using credentials from a Credentials Holder hosting AUSF/UDM, similar procedure can be used for service discovery across PLMNs as specified in clause 4.17.5 with the difference as below: - The Serving PLMN is replaced by SNPN and Home PLMN is replaced by CH; - In step 1: - the Home PLMN ID in Nnrf_NFDiscovery_Request is replaced by identification for the Credentials Holder, i.e.: - the realm in the case of Network Specific Identifier based SUCI/SUPI; or - the MCC and MNC in the case of an IMSI based SUCI/SUPI; NOTE: When IMSI based SUPI is used for a UE of a CH, the IMSI is assumed to be globally unique and assigned by the owner of a PLMN ID containing MCC and MNC of the IMSI as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - the Serving PLMN ID is replaced by SNPN ID (i.e. PLMN ID and NID); - In step 2, the NRF in SNPN identifies NRF in CH based on the identification for the Credentials Holder. In the case of a UE accessing ON-SNPN using Default UE credentials from a DCS hosting AUSF/UDM, a similar procedure can be used than for service discovery across PLMNs as specified in clause 4.17.5, with the difference as below: - The Serving PLMN is replaced by SNPN and Home PLMN is replaced by DCS; - In step 1: - the Home PLMN ID in Nnrf_NFDiscovery_Request is replaced by identification for the DCS, i.e.: - the realm in the case of Network Specific Identifier based SUCI/SUPI; - the Serving PLMN ID is replaced by SNPN ID (i.e. PLMN ID and NID); - In step 2, the NRF in SNPN identifies NRF in DCS based on the identification for the DCS. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.5a |
3,161 | 5.5.1.3.6 Abnormal cases in the UE | The UE shall proceed as follows: 1) if the UE requested the combined attach for EPS services and "SMS only" and the ATTACH ACCEPT message indicates a combined attach successful for EPS and non-EPS services, the UE shall behave as if the combined attach was successful for EPS services and "SMS only"; NOTE 1: In this case the UE can ignore the CS SERVICE NOTIFICATION message or the Paging with CN domain indicator set to "CS", as specified in clause 5.6.2.3.2. 2) if the combined attach was successful for EPS services only and the ATTACH ACCEPT message contained an EMM cause value not treated in clause 5.5.1.3.4.3 or the EMM cause IE is not included in the message, the UE shall proceed as follows: a) The UE shall stop timer T3410 if still running, and shall enter state MM IDLE. The tracking area updating attempt counter shall be incremented, unless it was already set to 5; b) If the tracking area updating attempt counter is less than 5: - the UE shall start timer T3411, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. When timer T3411 expires the combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered; c) If the tracking area updating attempt counter is equal to 5: - a UE operating in CS/PS mode 2 of operation and a UE operating in CS/PS mode 1 of operation with "IMS voice available" shall start timer T3402 if the value of the timer as indicated by the network is not zero, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. - If the value of T3402 as indicated by the network is zero, the UE shall perform the actions defined for the expiry of the timer T3402. - When timer T3402 expires the combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered; and - a UE operating in CS/PS mode 1 of operation with "IMS voice not available" shall attempt to select GERAN, UTRAN or NG-RAN radio access technology and proceed with appropriate MM, GMM or 5GMM specific procedures. If the UE selects GERAN or UTRAN radio access technology, the UE may disable the E-UTRA capability (see clause 4.5). If No E-UTRA Disabling In 5GS is enabled at the UE (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [50] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) and the UE selects NG-RAN radio access technology, it shall not disable the E-UTRA capability; otherwise, the UE may disable the E-UTRA capability as specified in clause 4.5; and NOTE 2: Whether the UE requests RRC to treat the active E-UTRA cell as barred (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]) is left to the UE implementation. d) If there is a CS fallback emergency call pending or CS fallback call pending, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures; otherwise the EMM sublayer shall indicate the abort of the EMM procedure to the MM sublayer; and 3) otherwise, the abnormal cases specified in clause 5.5.1.2.6 apply with the following modification. If the attach attempt counter is incremented according to clause 5.5.1.2.6 the next actions depend on the value of the attach attempt counter: - if the attach attempt counter is less than 5, the UE shall set the update status to U2 NOT UPDATED but shall not delete any LAI, TMSI, ciphering key sequence number and list of equivalent PLMNs; or - if the attach attempt counter is equal to 5, then the UE shall delete any LAI, TMSI, ciphering key sequence number and list of equivalent PLMNs and set the update status to U2 NOT UPDATED. - The UE shall attempt to select GERAN, UTRAN or NG-RAN radio access technology and proceed with appropriate MM, GMM or 5GMM specific procedures. Additionally, if the UE selects GERAN or UTRAN radio access technology, the UE may disable the E-UTRA capability as specified in clause 4.5. If No E-UTRA Disabling In 5GS is enabled at the UE (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [50] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) and the UE selects NG-RAN radio access technology, it shall not disable the E-UTRA capability; otherwise, the UE may disable the E-UTRA capability as specified in clause 4.5. NOTE 3: Whether the UE requests RRC to treat the active E-UTRA cell as barred (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]) is left to the UE implementation. If there is a CS fallback emergency call pending or CS fallback call pending, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures; otherwise the EMM sublayer shall indicate the abort of the EMM procedure to the MM sublayer. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.3.6 |
3,162 | – UplinkCancellation | The IE UplinkCancellation is used to configure the UE to monitor PDCCH for the CI-RNTI. UplinkCancellation information element -- ASN1START -- TAG-UPLINKCANCELLATION-START UplinkCancellation-r16 ::= SEQUENCE { ci-RNTI-r16 RNTI-Value, dci-PayloadSizeForCI-r16 INTEGER (0..maxCI-DCI-PayloadSize-r16), ci-ConfigurationPerServingCell-r16 SEQUENCE (SIZE (1..maxNrofServingCells)) OF CI-ConfigurationPerServingCell-r16, ... } CI-ConfigurationPerServingCell-r16 ::= SEQUENCE { servingCellId ServCellIndex, positionInDCI-r16 INTEGER (0..maxCI-DCI-PayloadSize-1-r16), positionInDCI-ForSUL-r16 INTEGER (0..maxCI-DCI-PayloadSize-1-r16) OPTIONAL, -- Cond SUL-Only ci-PayloadSize-r16 ENUMERATED {n1, n2, n4, n5, n7, n8, n10, n14, n16, n20, n28, n32, n35, n42, n56, n112}, timeFrequencyRegion-r16 SEQUENCE { timeDurationForCI-r16 ENUMERATED {n2, n4, n7, n14} OPTIONAL, -- Cond SymbolPeriodicity timeGranularityForCI-r16 ENUMERATED {n1, n2, n4, n7, n14, n28}, frequencyRegionForCI-r16 INTEGER (0..37949), deltaOffset-r16 INTEGER (0..2), ... }, uplinkCancellationPriority-v1610 ENUMERATED {enabled} OPTIONAL -- Need S } -- TAG-UPLINKCANCELLATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,163 | 4.4.8.2 Time Period the Requested latency of GBR services Cannot be Achieved in the Cell | a) This measurement provides time period the requested latency cannot be achieved in the cell. The measurement is split into sub-counters per QoS class level (QCI). Concerning operator specific QCIs their definition is vendor specific. b) CC c) This measurement is obtained by summing up the pre-defined sampling intervals during which the requested latency cannot be achieved in the cell and reporting accumulated value at the end of measurement period. The latency defined in TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] is used to evaluate time period during which the QoS is not satisfied by comparing the latency with the packet delay budget of the GBR services. The measurement period and number of samples during one measurement period are provided by the operator. d) Each measurement is an integer value (Unit: ms). e) The measurement name has the form Cell.ReqLatencyNotAchieved.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic. h) EPS. i) In case the duration interval provided with this measurement is followed with the on restricting the UEs for network access to the cell policy executed via ACB as mentioned in A.5 then this measurement provides “Time period in Active ACB triggered via requested QoS cannot be achieved”. The measurement can be executed with grouping of couple of QCIs to a common monitoring to distinguish between voice and data services. The latency measurements is used as a reference on how to evaluate the quality of provided services to end user in observed cell. They shall be obtained directly in the eNB as internal measurements during each sampling period. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.8.2 |
3,164 | K.2.2 PTP Instance configuration K.2.2.1 General | Based on input received from external applications (CNC in case of TSN AF or any AF in case of TSCTSF), TSN AF or TSCTSF may configure PTP instances (identified by PTP Instance ID) in a DS-TT or NW-TT by sending port management information (PMIC, see Table K.1-1) and user plane node management information (UMIC, see Table K.1-2) to DS-TT or NW-TT as described below: - use PMIC "PTP instance specification" for configuring DS-TT(s) for PTP instance data sets common for all PTP ports (i.e. defaultDS and TimePropertiesDS), and PTP instance data sets specific for each PTP port (i.e. portDS data set); - use UMIC "PTP instance specification" for configuring NW-TT for PTP instance data sets common for all PTP ports; - use PMIC "PTP instance specification" for configuring NW-TT for PTP instance data sets specific for each PTP port; - use UMIC "Time synchronization information for DS-TT ports" for configuring NW-TT for PTP instance data sets specific for each PTP port for the PTP ports in DS-TT(s). TSN AF or TSCTSF may also configure PTP instances for DS-TT ports in NW-TT by sending UMIC (see Table K.1-2) to NW-TT to enable NW-TT to operate as a grandmaster on behalf of DS-TT (see clause K.2.2.4 for more details). For each PTP instance the TSN AF or TSCTSF may provide individual PTP configuration parameters or may provide a PTP profile ID to DS-TT or NW-TT. The DS-TT and NW-TT use the default values as defined in the corresponding PTP Profile, if individual PTP configuration parameters that are covered by the PTP profile are not provided. NOTE 1: Even if PTP profiles are used to configure DS-TT or NW-TT, individual PTP parameters can still be configured in addition, e.g. domain numbers, transport to use, etc. To configure DS-TT and NW-TT to operate as a PTP relay instance, TSN AF or TSCTSF shall set the PTP profile (see Table K.1-1) to IEEE Std 802.1AS [104]. DS-TT may operate as a PTP relay instance with the gPTP GM connected on N6 until the first PTP instance is configured in the DS-TT by TSN AF or TSCTSF. To initialize a PTP instance in 5GS, TSN AF or TSCTSF creates a new PTP instance in NW-TT by assigning a new PTP Instance ID and indicating it to the NW-TT in "PTP instance specification" in UMIC and PMIC(s) for each NW-TT port that is part of the PTP instance. TSN AF or TSCTSF then retrieves the "defaultDS.clockIdentity" of the PTP instance in NW-TT via UMIC. NW-TT ensures that the clockIdentity in defaultDS in UMIC matches with the clockIdentity in the portDS.portIdentity in PMIC(s) for a particular PTP Instance ID. To add a DS-TT port into an existent PTP instance in 5GS, the TSN AF or TSCTSF indicates the PTP Instance ID (to which the DS-TT port is being added) to the DS-TT in "PTP instance specification" in PMIC, and indicating the PTP Instance ID to the NW-TT in "Time synchronization information for DS-TT ports" in UMIC for the corresponding DS-TT port. For a particular PTP instance in NW-TT, the same PTP Instance ID shall be used in "PTP instance specification" in PMIC, in "PTP instance specification" in UMIC, and in "Time synchronization information for DS-TT ports" in UMIC. NOTE 2: The TSN AF or TSCTSF creates a PTP Instance in the NW-TT or DS-TT by using the "Set parameter" operation code as described in TS 24.539[ 5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3 ] [139]. The NW-TT or DS-TT determines that this "Set parameter" operation creates a new PTP Instance based on the PTP Instance ID that does not correspond to any of the configured PTP Instances in the "PTP instance specification" and "Time synchronization information for DS-TT ports" (for NW-TT) or in the "PTP instance specification" (for DS-TT). The TSN AF or TSCTSF then initializes the PTP instance in the DS-TT by setting the applicable PTP instance data sets common for all PTP ports (i.e. defaultDS and TimePropertiesDS), (including"defaultDS.clockIdentity") via "PTP instance specification" in PMIC to the same value as retrieved from the NW-TT via "PTP instance specification" in UMIC. The TSN AF or TSCTSF also enables the PTP instance by setting the defaultDS.instanceEnable = TRUE to DS-TT via PMIC and to NW-TT via UMIC (if applicable). The TSN AF or TSCTSF can initialize any number of PTP instances: a) among the DS-TT(s) and NW-TT that are part of the same set of PTP instances in 5GS; up to the maximum number of supported PTP instances by the NW-TT or DS-TT that supports the lowest number of supported PTP instances; and b) in the NW-TT; up to the maximum number of supported PTP instances by the NW-TT. NOTE 3: How the TSN AF or TSCTSF assign NW-TT port(s) of one NW-TT to different PTP instances is up to implementation. To remove a DS-TT port from a PTP instance in 5GS, the TSN AF or TSCTSF deletes the PTP instance in DS-TT using PMIC and in NW-TT using UMIC as specified in TS 24.539[ 5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3 ] [139]. To remove a NW-TT port from a PTP instance in 5GS, the TSN AF or TSCTSF deletes the PTP instance in NW-TT using PMIC as specified in TS 24.539[ 5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3 ] [139]. If a PTP instance in 5GS is no more needed the TSN AF or TSCTSF may delete the PTP instance in NW-TT using UMIC as specified in TS 24.539[ 5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3 ] [139]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | K.2.2 |
3,165 | 8.1 Description | IoT introduces new UEs with different life cycles, including IoT devices with no user interface (e.g. embedded sensors), long life spans during which an IoT device can change ownership several times (e.g. consumer goods), and which cannot be pre-provisioned (e.g. consumer goods). These drive a need for secure mechanisms to dynamically establish or refresh credentials and subscriptions. New access technologies, including licensed and unlicensed, 3GPP and non-3GPP, drive a need for access-independent security that is seamlessly available while the IoT device is active. High-end smartphones, UAVs, and factory automation drive a need for protection against theft and fraud. A high level of 5G security is essential for critical communication, e.g. in industrial automation, industrial IoT, and the Smart Grid. Expansion into enterprise, vehicular, medical, and public safety markets drive a need for increased end user privacy protection. 5G security addresses all of these new needs while continuing to provide security consistent with prior 3GPP systems. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 8.1 |
3,166 | 9.9.1.4.2 TDD | The following requirements apply to UE Category ≥5. For the parameters specified in table 9.9.1.4.2-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 – Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 – 1 and median CQI1 – 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.9.1.4.2-1: PUCCH 1-1 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.9.1.4.2 |
3,167 | 4.18.3.2 Management of PFDs in the SMF | This procedure enables the provisioning, modification or removal of PFDs associated with an application identifier in the SMF. Either the complete list of all PFDs of all application identifiers, the complete list of all PFDs of one or more application identifiers or a subset of PFDs for individual application identifiers may be managed. Each PFD of an application identifier is associated with a PFD id if a subset of the PFD(s) associated with an application identifier can be provisioned, updated or removed. If always the full set of PFD(s) for an application identifier is managed in each transaction, PFD ids do not need to be provided. Figure 4.18.3.2-1 Management of PFDs in the SMF 1. As pre-requisite condition to receiving push notifications, the SMF subscribes to PFD notifications from the NEF (PFDF) by sending Nnef_PFDManagement_Subscribe message. 2. The NEF (PFDF) invokes Nnef_PFD_Management_Notify (Application Identifier, PFDs, PFDs operation) to the SMF(s) to which the PFD(s) shall be provided. The NEF (PFDF) may decide to delay the distribution of PFDs to the SMF(s) for some time to optimize the signalling load. If the NEF (PFDF) received an Allowed Delay for a PFD, the NEF (PFDF) shall distribute this PFD within the indicated time interval. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.18.3.2 |
3,168 | 6.6.5 Cipher key selection | There is one CK for CS connections (CKCS), established between the CS service domain and the user and one CK for PS connections (CKPS) established between the PS service domain and the user. The radio bearers for CS user data are ciphered with CKCS. The radio bearers for PS user data are ciphered with CKPS. The signalling radio bearers are used for transfer of signalling data for services delivered by both CS and PS service domains. These signalling radio bearers are ciphered by the CK of the service domain for which the most recent security mode negotiation took place. This may require that the cipher key of an (already ciphered) ongoing signalling connection has to be changed, when a new connection is established with another service domain, or when a security mode negotiation follows a re-authentication during an ongoing connection. This change should be completed by the RNC within five seconds after receiving the security mode command from the VLR/SGSN. NOTE: For the behaviour of the terminal regarding key changes see section 6.4.5. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.6.5 |
3,169 | – BandCombinationList | The IE BandCombinationList contains a list of NR CA, NR non-CA and/or MR-DC band combinations (also including DL only or UL only band). BandCombinationList information element -- ASN1START -- TAG-BANDCOMBINATIONLIST-START BandCombinationList ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination BandCombinationList-v1540 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1540 BandCombinationList-v1550 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1550 BandCombinationList-v1560 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1560 BandCombinationList-v1570 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1570 BandCombinationList-v1580 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1580 BandCombinationList-v1590 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1590 BandCombinationList-v15g0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v15g0 BandCombinationList-v15n0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v15n0 BandCombinationList-v1610 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1610 BandCombinationList-v1630 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1630 BandCombinationList-v1640 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1640 BandCombinationList-v1650 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1650 BandCombinationList-v1680 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1680 BandCombinationList-v1690 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1690 BandCombinationList-v16a0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v16a0 BandCombinationList-v1700 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1700 BandCombinationList-v1720 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1720 BandCombinationList-v1730 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1730 BandCombinationList-v1740 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1740 BandCombinationList-v1760 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1760 BandCombinationList-v1770 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1770 BandCombinationList-v1800 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1800 BandCombinationList-UplinkTxSwitch-r16 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-r16 BandCombinationList-UplinkTxSwitch-v1630 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1630 BandCombinationList-UplinkTxSwitch-v1640 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1640 BandCombinationList-UplinkTxSwitch-v1650 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1650 BandCombinationList-UplinkTxSwitch-v1670 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1670 BandCombinationList-UplinkTxSwitch-v1690 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1690 BandCombinationList-UplinkTxSwitch-v16a0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v16a0 BandCombinationList-UplinkTxSwitch-v16e0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v16e0 BandCombinationList-UplinkTxSwitch-v1700 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1700 BandCombinationList-UplinkTxSwitch-v1720 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1720 BandCombinationList-UplinkTxSwitch-v1730 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1730 BandCombinationList-UplinkTxSwitch-v1740 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1740 BandCombinationList-UplinkTxSwitch-v1760 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1760 BandCombinationList-UplinkTxSwitch-v1770 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1770 BandCombinationList-UplinkTxSwitch-v1800 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1800 BandCombination ::= SEQUENCE { bandList SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters, featureSetCombination FeatureSetCombinationId, ca-ParametersEUTRA CA-ParametersEUTRA OPTIONAL, ca-ParametersNR CA-ParametersNR OPTIONAL, mrdc-Parameters MRDC-Parameters OPTIONAL, supportedBandwidthCombinationSet BIT STRING (SIZE (1..32)) OPTIONAL, powerClass-v1530 ENUMERATED {pc2} OPTIONAL } BandCombination-v1540::= SEQUENCE { bandList-v1540 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1540, ca-ParametersNR-v1540 CA-ParametersNR-v1540 OPTIONAL } BandCombination-v1550 ::= SEQUENCE { ca-ParametersNR-v1550 CA-ParametersNR-v1550 } BandCombination-v1560::= SEQUENCE { ne-DC-BC ENUMERATED {supported} OPTIONAL, ca-ParametersNRDC CA-ParametersNRDC OPTIONAL, ca-ParametersEUTRA-v1560 CA-ParametersEUTRA-v1560 OPTIONAL, ca-ParametersNR-v1560 CA-ParametersNR-v1560 OPTIONAL } BandCombination-v1570 ::= SEQUENCE { ca-ParametersEUTRA-v1570 CA-ParametersEUTRA-v1570 } BandCombination-v1580 ::= SEQUENCE { mrdc-Parameters-v1580 MRDC-Parameters-v1580 } BandCombination-v1590::= SEQUENCE { supportedBandwidthCombinationSetIntraENDC BIT STRING (SIZE (1..32)) OPTIONAL, mrdc-Parameters-v1590 MRDC-Parameters-v1590 } BandCombination-v15g0::= SEQUENCE { ca-ParametersNR-v15g0 CA-ParametersNR-v15g0 OPTIONAL, ca-ParametersNRDC-v15g0 CA-ParametersNRDC-v15g0 OPTIONAL, mrdc-Parameters-v15g0 MRDC-Parameters-v15g0 OPTIONAL } BandCombination-v15n0::= SEQUENCE { mrdc-Parameters-v15n0 MRDC-Parameters-v15n0 } BandCombination-v1610 ::= SEQUENCE { bandList-v1610 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1610 OPTIONAL, ca-ParametersNR-v1610 CA-ParametersNR-v1610 OPTIONAL, ca-ParametersNRDC-v1610 CA-ParametersNRDC-v1610 OPTIONAL, powerClass-v1610 ENUMERATED {pc1dot5} OPTIONAL, powerClassNRPart-r16 ENUMERATED {pc1, pc2, pc3, pc5} OPTIONAL, featureSetCombinationDAPS-r16 FeatureSetCombinationId OPTIONAL, mrdc-Parameters-v1620 MRDC-Parameters-v1620 OPTIONAL } BandCombination-v1630 ::= SEQUENCE { ca-ParametersNR-v1630 CA-ParametersNR-v1630 OPTIONAL, ca-ParametersNRDC-v1630 CA-ParametersNRDC-v1630 OPTIONAL, mrdc-Parameters-v1630 MRDC-Parameters-v1630 OPTIONAL, supportedTxBandCombListPerBC-Sidelink-r16 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL, supportedRxBandCombListPerBC-Sidelink-r16 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL, scalingFactorTxSidelink-r16 SEQUENCE (SIZE (1..maxBandComb)) OF ScalingFactorSidelink-r16 OPTIONAL, scalingFactorRxSidelink-r16 SEQUENCE (SIZE (1..maxBandComb)) OF ScalingFactorSidelink-r16 OPTIONAL } BandCombination-v1640 ::= SEQUENCE { ca-ParametersNR-v1640 CA-ParametersNR-v1640 OPTIONAL, ca-ParametersNRDC-v1640 CA-ParametersNRDC-v1640 OPTIONAL } BandCombination-v1650 ::= SEQUENCE { ca-ParametersNRDC-v1650 CA-ParametersNRDC-v1650 OPTIONAL } BandCombination-v1680 ::= SEQUENCE { intrabandConcurrentOperationPowerClass-r16 SEQUENCE (SIZE (1..maxBandComb)) OF IntraBandPowerClass-r16 OPTIONAL } BandCombination-v1690 ::= SEQUENCE { ca-ParametersNR-v1690 CA-ParametersNR-v1690 OPTIONAL } BandCombination-v16a0 ::= SEQUENCE { ca-ParametersNR-v16a0 CA-ParametersNR-v16a0 OPTIONAL, ca-ParametersNRDC-v16a0 CA-ParametersNRDC-v16a0 OPTIONAL } BandCombination-v1700 ::= SEQUENCE { ca-ParametersNR-v1700 CA-ParametersNR-v1700 OPTIONAL, ca-ParametersNRDC-v1700 CA-ParametersNRDC-v1700 OPTIONAL, mrdc-Parameters-v1700 MRDC-Parameters-v1700 OPTIONAL, bandList-v1710 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1710 OPTIONAL, supportedBandCombListPerBC-SL-RelayDiscovery-r17 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL, supportedBandCombListPerBC-SL-NonRelayDiscovery-r17 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL } BandCombination-v1720 ::= SEQUENCE { ca-ParametersNR-v1720 CA-ParametersNR-v1720 OPTIONAL, ca-ParametersNRDC-v1720 CA-ParametersNRDC-v1720 OPTIONAL } BandCombination-v1730 ::= SEQUENCE { ca-ParametersNR-v1730 CA-ParametersNR-v1730 OPTIONAL, ca-ParametersNRDC-v1730 CA-ParametersNRDC-v1730 OPTIONAL, bandList-v1730 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1730 OPTIONAL } BandCombination-v1740 ::= SEQUENCE { ca-ParametersNR-v1740 CA-ParametersNR-v1740 OPTIONAL } BandCombination-v1760 ::= SEQUENCE { ca-ParametersNR-v1760 CA-ParametersNR-v1760, ca-ParametersNRDC-v1760 CA-ParametersNRDC-v1760 } BandCombination-v1770::= SEQUENCE { bandList-v1770 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1770, mrdc-Parameters-v1770 MRDC-Parameters-v1770 OPTIONAL, ca-ParametersNR-v1770 CA-ParametersNR-v1770 OPTIONAL } BandCombination-v1800 ::= SEQUENCE { ca-ParametersNR-v1800 CA-ParametersNR-v1800 OPTIONAL, ca-ParametersNRDC-v1800 CA-ParametersNRDC-v1800 OPTIONAL, supportedBandCombListPerBC-SL-U2U-RelayDiscovery-r18 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL } BandCombination-UplinkTxSwitch-r16 ::= SEQUENCE { bandCombination-r16 BandCombination, bandCombination-v1540 BandCombination-v1540 OPTIONAL, bandCombination-v1560 BandCombination-v1560 OPTIONAL, bandCombination-v1570 BandCombination-v1570 OPTIONAL, bandCombination-v1580 BandCombination-v1580 OPTIONAL, bandCombination-v1590 BandCombination-v1590 OPTIONAL, bandCombination-v1610 BandCombination-v1610 OPTIONAL, supportedBandPairListNR-r16 SEQUENCE (SIZE (1..maxULTxSwitchingBandPairs)) OF ULTxSwitchingBandPair-r16, uplinkTxSwitching-OptionSupport-r16 ENUMERATED {switchedUL, dualUL, both} OPTIONAL, uplinkTxSwitching-PowerBoosting-r16 ENUMERATED {supported} OPTIONAL, ..., [[ -- R4 16-5 UL-MIMO coherence capability for dynamic Tx switching between 3CC 1Tx-2Tx switching uplinkTxSwitching-PUSCH-TransCoherence-r16 ENUMERATED {nonCoherent, fullCoherent} OPTIONAL ]] } BandCombination-UplinkTxSwitch-v1630 ::= SEQUENCE { bandCombination-v1630 BandCombination-v1630 OPTIONAL } BandCombination-UplinkTxSwitch-v1640 ::= SEQUENCE { bandCombination-v1640 BandCombination-v1640 OPTIONAL } BandCombination-UplinkTxSwitch-v1650 ::= SEQUENCE { bandCombination-v1650 BandCombination-v1650 OPTIONAL } BandCombination-UplinkTxSwitch-v1670 ::= SEQUENCE { bandCombination-v15g0 BandCombination-v15g0 OPTIONAL } BandCombination-UplinkTxSwitch-v1690 ::= SEQUENCE { bandCombination-v1690 BandCombination-v1690 OPTIONAL } BandCombination-UplinkTxSwitch-v16a0 ::= SEQUENCE { bandCombination-v16a0 BandCombination-v16a0 OPTIONAL } BandCombination-UplinkTxSwitch-v16e0 ::= SEQUENCE { bandCombination-v15n0 BandCombination-v15n0 OPTIONAL } BandCombination-UplinkTxSwitch-v1700 ::= SEQUENCE { bandCombination-v1700 BandCombination-v1700 OPTIONAL, -- R4 16-1/16-2/16-3 Dynamic Tx switching between 2CC/3CC 2Tx-2Tx/1Tx-2Tx switching supportedBandPairListNR-v1700 SEQUENCE (SIZE (1..maxULTxSwitchingBandPairs)) OF ULTxSwitchingBandPair-v1700 OPTIONAL, -- R4 16-6: UL-MIMO coherence capability for dynamic Tx switching between 2Tx-2Tx switching uplinkTxSwitchingBandParametersList-v1700 SEQUENCE (SIZE (1.. maxSimultaneousBands)) OF UplinkTxSwitchingBandParameters-v1700 OPTIONAL } BandCombination-UplinkTxSwitch-v1720 ::= SEQUENCE { bandCombination-v1720 BandCombination-v1720 OPTIONAL, uplinkTxSwitching-OptionSupport2T2T-r17 ENUMERATED {switchedUL, dualUL, both} OPTIONAL } BandCombination-UplinkTxSwitch-v1730 ::= SEQUENCE { bandCombination-v1730 BandCombination-v1730 OPTIONAL } BandCombination-UplinkTxSwitch-v1740 ::= SEQUENCE { bandCombination-v1740 BandCombination-v1740 OPTIONAL } BandCombination-UplinkTxSwitch-v1760 ::= SEQUENCE { bandCombination-v1760 BandCombination-v1760 OPTIONAL } BandCombination-UplinkTxSwitch-v1770 ::= SEQUENCE { bandCombination-v1770 BandCombination-v1770 OPTIONAL } BandCombination-UplinkTxSwitch-v1800 ::= SEQUENCE { supportedBandPairListNR-r18 SEQUENCE (SIZE (1..maxULTxSwitchingBandPairs)) OF ULTxSwitchingBandPair-r18 OPTIONAL, -- R1 49-Y: Minimum separation time for two uplink switching on more than 2 bands within any two consecutive reference slots uplinkTxSwitchingMinimumSeparationTime-r18 ENUMERATED {n0us, n500us} OPTIONAL, uplinkTxSwitchingAdditionalPeriodDualUL-List-r18 SEQUENCE (SIZE (1..maxULTxSwitchingBetweenBandPairs-r18)) OF UplinkTxSwitchingAdditionalPeriodDualUL-r18 OPTIONAL } ULTxSwitchingBandPair-r16 ::= SEQUENCE { bandIndexUL1-r16 INTEGER(1..maxSimultaneousBands), bandIndexUL2-r16 INTEGER(1..maxSimultaneousBands), uplinkTxSwitchingPeriod-r16 ENUMERATED {n35us, n140us, n210us}, uplinkTxSwitching-DL-Interruption-r16 BIT STRING (SIZE(1..maxSimultaneousBands)) OPTIONAL } ULTxSwitchingBandPair-v1700 ::= SEQUENCE { uplinkTxSwitchingPeriod2T2T-r17 ENUMERATED {n35us, n140us, n210us} OPTIONAL } ULTxSwitchingBandPair-r18 ::= SEQUENCE { bandCombination-v1800 BandCombination-v1800 OPTIONAL, bandIndexUL1-r18 INTEGER(1..maxSimultaneousBands), bandIndexUL2-r18 INTEGER(1..maxSimultaneousBands), uplinkTxSwitchingOptionForBandPair-r18 ENUMERATED {switchedUL, dualUL, both}, -- R1 49-X: Supported switching option for each band pair in the band combination for UL Tx switching across more than 2 bands uplinkTxSwitchingPeriodForBandPair-r18 SEQUENCE { switchingPeriodFor2T-r18 ENUMERATED {n35us, n140us, n210us} OPTIONAL, switchingPeriodFor1T-r18 ENUMERATED {n35us, n140us, n210us} }, uplinkTxSwitching-DL-Interruption-r18 BIT STRING (SIZE(1..maxSimultaneousBands)) OPTIONAL, uplinkTxSwitchingPeriodUnaffectedBandDualUL-List-r18 SEQUENCE (SIZE (1..maxSimultaneousBands-2-r18)) OF SwitchingPeriodUnaffectedBandDualUL-r18 OPTIONAL } UplinkTxSwitchingBandParameters-v1700 ::= SEQUENCE { bandIndex-r17 INTEGER(1..maxSimultaneousBands), uplinkTxSwitching2T2T-PUSCH-TransCoherence-r17 ENUMERATED {nonCoherent, fullCoherent} OPTIONAL } UplinkTxSwitchingAdditionalPeriodDualUL-r18::= SEQUENCE { uplinkTxSwitchingBetweenBandPairs-r18 SEQUENCE { bandPairIndex1-r18 INTEGER(1.. maxULTxSwitchingBandPairs), anotherBandPairOrBand-r18 CHOICE { bandPairIndex2-r18 INTEGER(1.. maxULTxSwitchingBandPairs), bandIndex-r18 INTEGER(1..maxSimultaneousBands) } }, switchingAdditionalPeriodDualUL-r18 ENUMERATED {n35us, n140us, n210us} } SwitchingPeriodUnaffectedBandDualUL-r18::= SEQUENCE { bandIndexUnaffected-r18 INTEGER(1..maxSimultaneousBands), periodUnaffectedBandDualUL-r18 CHOICE { maintainedUL-Trans-r18 NULL, periodOnULBands-r18 ENUMERATED {n35us, n140us, n210us} } } CombinationCarrierType-r18 ::= SEQUENCE { schedulingCellCarrierType-r18 ENUMERATED {licensed-fdd-fr1, licensed-tdd-fr1, unlicensed-tdd-fr1, fr2-1, fr2-2}, scheduledCellCarrierType-r18 ENUMERATED {licensed-fdd-fr1, licensed-tdd-fr1, unlicensed-tdd-fr1, fr2-1, fr2-2} } BandParameters ::= CHOICE { eutra SEQUENCE { bandEUTRA FreqBandIndicatorEUTRA, ca-BandwidthClassDL-EUTRA CA-BandwidthClassEUTRA OPTIONAL, ca-BandwidthClassUL-EUTRA CA-BandwidthClassEUTRA OPTIONAL }, nr SEQUENCE { bandNR FreqBandIndicatorNR, ca-BandwidthClassDL-NR CA-BandwidthClassNR OPTIONAL, ca-BandwidthClassUL-NR CA-BandwidthClassNR OPTIONAL } } BandParameters-v1540 ::= SEQUENCE { srs-CarrierSwitch CHOICE { nr SEQUENCE { srs-SwitchingTimesListNR SEQUENCE (SIZE (1..maxSimultaneousBands)) OF SRS-SwitchingTimeNR }, eutra SEQUENCE { srs-SwitchingTimesListEUTRA SEQUENCE (SIZE (1..maxSimultaneousBands)) OF SRS-SwitchingTimeEUTRA } } OPTIONAL, srs-TxSwitch SEQUENCE { supportedSRS-TxPortSwitch ENUMERATED {t1r2, t1r4, t2r4, t1r4-t2r4, t1r1, t2r2, t4r4, notSupported}, txSwitchImpactToRx INTEGER (1..32) OPTIONAL, txSwitchWithAnotherBand INTEGER (1..32) OPTIONAL } OPTIONAL } BandParameters-v1610 ::= SEQUENCE { srs-TxSwitch-v1610 SEQUENCE { supportedSRS-TxPortSwitch-v1610 ENUMERATED {t1r1-t1r2, t1r1-t1r2-t1r4, t1r1-t1r2-t2r2-t2r4, t1r1-t1r2-t2r2-t1r4-t2r4, t1r1-t2r2, t1r1-t2r2-t4r4} } OPTIONAL } BandParameters-v1710 ::= SEQUENCE { -- R1 23-8-3 SRS Antenna switching for >4Rx srs-AntennaSwitchingBeyond4RX-r17 SEQUENCE { -- 1. Support of SRS antenna switching xTyR with y>4 supportedSRS-TxPortSwitchBeyond4Rx-r17 BIT STRING (SIZE (11)), -- 2. Report the entry number of the first-listed band with UL in the band combination that affects this DL entryNumberAffectBeyond4Rx-r17 INTEGER (1..32) OPTIONAL, -- 3. Report the entry number of the first-listed band with UL in the band combination that switches together with this UL entryNumberSwitchBeyond4Rx-r17 INTEGER (1..32) OPTIONAL } OPTIONAL } BandParameters-v1730 ::= SEQUENCE { -- R1 39-3-2 Affected bands for inter-band CA during SRS carrier switching srs-SwitchingAffectedBandsListNR-r17 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF SRS-SwitchingAffectedBandsNR-r17 } BandParameters-v1770 ::= SEQUENCE { ca-BandwidthClassDL-NR-r17 CA-BandwidthClassNR-r17 OPTIONAL, ca-BandwidthClassUL-NR-r17 CA-BandwidthClassNR-r17 OPTIONAL } ScalingFactorSidelink-r16 ::= ENUMERATED {f0p4, f0p75, f0p8, f1} IntraBandPowerClass-r16 ::= ENUMERATED {pc2, pc3, spare6, spare5, spare4, spare3, spare2, spare1} SRS-SwitchingAffectedBandsNR-r17 ::= BIT STRING (SIZE (1..maxSimultaneousBands)) -- TAG-BANDCOMBINATIONLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,170 | 10.16 Support of inter-system handover involving EN-DC or MR-DC with 5GC 10.16.1 General | Inter-system handover is specified in TS 23.501[ System architecture for the 5G System (5GS) ] [11] and TS 23.502[ Procedures for the 5G System (5GS) ] [20]. Data forwarding for inter-system handover is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] and clause 8.4. Inter-system Inter-Master node handover with/without SN change is not supported in this version of the protocol (e.g. no transition from EN-DC to NGEN-DC or NR-DC). Inter-system HO from NR to E-UTRA with EN-DC configuration is supported in this version of the specification. N26 based inter-system HO will be executed between source RAN and gNB. Inter-system HO from E-UTRA connected to 5GC to E-UTRA with EN-DC configuration is not supported. Inter-system HO from E-UTRA with EPC to MR-DC with 5GC is not supported. Inter-system handover with source gNB and the target en-gNB or the source en-gNB and the target gNB being realised within the same network entity is supported in this version of the specification as described in clause 10.16.2 and clause 10.16.3. | 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.16 |
3,171 | Annex M (normative): Additional Requirements for backward compatibility with PCS 1900 for NA revision 0 ME | This annex provides additional requirements to support network mechanisms for backward compatibility with PCS 1900 for NA revision 0 mobile equipments (applicable until July 1, 1998). PCS 1900 for NA revision 0 mobile equipments are defined to understand Mobile Network Codes made of up to 2 digits. However federal regulation mandates that a 3-digit MNC shall be allocated by each administration to network operators. Therefore each network operator is identified by a 3-digit Mobile Country Code and a 3-digit Mobile Network Code. An operator whose network code complies to the allocation principle specified for PCS 1900 for NA and wants to achieve for a transition period of time the backward compatibility with PCS 1900 for NA revision 0 mobile equipments shall apply the following: - The network shall send over the air interface the 3-digit Mobile Country Code and only the two most significant digits of the Mobile Network Code (the value of the "digit" sent instead of the 3rd digit is specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] , subclause 10.5.1.3) (see note). When a PCS 1900 for NA (revision greater than 0) mobile equipment recognizes over the air the Mobile Country Code and the two most significant digits of the Mobile Network Code as being the HPLMN codes of the current IMSI, the mobile equipment shall take into account the value of the sixth IMSI digit read from the SIM/USIM. If this value matches to a value contained in the limited set of values for the least significant MNC digit assigned by the number administration bodies for PCS 1900 for NA then the following applies for the mobile equipment: - The value sent over the air instead of the 3rd MNC digit in the Location Area Identification (for coding see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] , subclause 10.5.1.3) shall be interpreted as the value of the sixth IMSI digit read from the SIM/USIM. NOTE: It is still a network operator option to apply this requirement after July 1, 1998. However, in this case the following shall be considered: 1. Network selection considerations for overlapping networks: - Networks overlapping to the HPLMN, identified over the radio interface by an identical combination MCC1 MCC2 MCC3 MNC1 MNC2 (possible after July 1, 1998) may be selectable by PCS 1900 for NA mobile equipments revision 0 with the same priority as the HPLMN or presented to the user as the HPLMN. 2 Roaming considerations: - Roamers (SIM/USIM) from networks identified by an identical combination MCC1 MCC2 MCC3 MNC1 MNC2 (possible after July 1, 1998) when roaming into the operator network with PCS 1900 for NA mobile equipments revision 0, may cause these equipments to exhibit an unpredictable behaviour (e.g. looping in the HPLMN selection and registration procedures). - Home subscribers (SIM/USIM) roaming with PCS 1900 for NA mobile equipments revision 0 into networks identified by an identical combination MCC1 MCC2 MCC3 MNC1 MNC2 (possible after July 1, 1998), may consider being attached to the HPLMN. | 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 | Annex |
3,172 | 4.2.6 AN Release | This procedure is used to release the logical NG-AP signalling connection for the UE between the (R)AN and the AMF and the associated N3 User Plane connections and (R)AN signalling connection between the UE and the (R)AN and the associated (R)AN resources. When the NG-AP signalling connection is lost due to (R)AN or AMF failure, the AN release is performed locally by the AMF or the (R)AN as described in the procedure flow below without using or relying on any of the signalling shown between (R)AN and AMF. The AN release causes all UP connections of the UE to be deactivated. The initiation of AN release may be due to: - (R)AN-initiated with cause e.g. O&M Intervention, Unspecified Failure, (R)AN (e.g. Radio) Link Failure, User Inactivity, Inter-System Redirection, request for establishment of QoS Flow for IMS voice, Release due to UE generated signalling connection release, mobility restriction, Release Assistance Information (RAI) from the UE, UE using satellite access moved out of PLMN serving area, etc.; or - AMF-initiated with cause e.g. Unspecified Failure, etc. Both (R)AN-initiated and AMF-initiated AN Release procedures are shown in Figure 4.2.6-1. If Service Gap Control shall be applied for the UE (see clause 5.31.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and the Service Gap timer is not already running, the Service Gap timer shall be started in AMF and UE when entering CM-IDLE, unless the connection was initiated after a paging of an MT event, or after a Registration procedure without Uplink data status or after a Registration procedure for regulatory prioritized services like Emergency services or exception reporting. For this procedure, the impacted SMF and UPF are all under control of the PLMN serving the UE, e.g. in Home Routed roaming case the SMF and UPF in HPLMN are not involved. Figure 4.2.6-1: AN Release procedure 1. If there is some confirmed (R)AN conditions (e.g. Radio Link Failure) or for other (R)AN internal reason, the (R)AN may decide to initiate the UE context release in the (R)AN. In this case, the (R)AN sends an N2 UE Context Release Request (Cause, List of PDU Session ID(s) with active N3 user plane) message to the AMF. Cause indicates the reason for the release (e.g. AN Link Failure, O&M intervention, unspecified failure, etc.). The List of PDU Session ID(s) indicates the PDU Sessions served by (R)AN of the UE. If the (R)AN is NG-RAN, this step is described in clause 8.3.2 of TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. If the (R)AN is an N3IWF this step is described in clause 4.12.4.2. If the reason for the release is the NG-RAN received an AS Release Assistance Indicator as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16], NG-RAN should not immediately release the RRC connection but instead send an N2 UE Context Release Request message to the AMF. If the AS RAI indicates only a single downlink transmission is expected then NG-RAN should only send the N2 UE Context Release Request after a single downlink NAS PDU or N3 data PDU has been transferred. If N2 Context Release Request cause indicates the release is requested due to user inactivity or AS RAI then the AMF continues with the AN Release procedure unless the AMF is aware of pending MT traffic or signalling. If N2 Context Release Request cause indicates the release is requested due to a UE using satellite access moved out of PLMN serving area, the AMF may deregister the UE as described in clause 4.2.2.3.3 before continuing with the AN Release procedure. 2. AMF to (R)AN: If the AMF receives the N2 UE Context Release Request message or due to an internal AMF event, including the reception of Service Request or Registration Request to establish another NAS signalling connection still via (R)AN, the AMF sends an N2 UE Context Release Command (Cause) to the (R)AN. The Cause indicates either the Cause from (R)AN in step 1 or the Cause due to an AMF event. If the (R)AN is a NG-RAN this step is described in detail in clause 8.3.3 of TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. If the (R)AN is an N3IWF/TNGF/W-AGF this step is described in clauses 4.12.4.2 / 4.12a and in clause 7.2.5 of TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [53] for W-5GAN access. If the AMF receives Service Request or Registration Request to establish another NAS signalling connection still via (R)AN, after successfully authenticating the UE, the AMF releases the old NAS signalling connection and then continues the Service Request or Registration Request procedure. 3. [Conditional] If the (R)AN connection (e.g. RRC connection or NWu connection) with the UE is not already released (step 1), either: a) the (R)AN requests the UE to release the (R)AN connection. Upon receiving (R)AN connection release confirmation from the UE, the (R)AN deletes the UE's context, or b) if the Cause in the N2 UE Context Release Command indicates that the UE has already locally released the RRC connection, the (R)AN locally releases the RRC connection. 4. The (R)AN confirms the N2 Release by returning an N2 UE Context Release Complete (List of PDU Session ID(s) with active N3 user plane, User Location Information, Age of Location Information) message to the AMF. The List of PDU Session ID(s) indicates the PDU Sessions served by (R)AN of the UE. The AMF stores always the latest UE Radio Capability information or NB-IoT specific UE Radio Access Capability Information received from the NG-RAN node received as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. The N2 signalling connection between the AMF and the (R)AN for that UE is released. If the UE is served by an NG-eNB that supports WUS, then the NG-eNB should include the Information On Recommended Cells And RAN nodes For Paging; otherwise the (R)AN may provide the list of recommended cells / TAs / NG-RAN node identifiers for paging to the AMF. If the PLMN has configured secondary RAT usage reporting, the NG-RAN node may provide RAN usage data Report. This step shall be performed promptly after step 2, i.e. it shall not be delayed, for example, in situations where the UE does not acknowledge the RRC Connection Release. The NG-RAN includes Paging Assistance Data for CE capable UE, if available, in the N2 UE Context Release Complete message. The AMF stores the received Paging Assistance Data for CE capable UE in the UE context for subsequent Paging procedure. 5. [Conditional] AMF to SMF: For each of the PDU Sessions in the N2 UE Context Release Complete, the AMF invokes Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, PDU Session Deactivation, Cause, Operation Type, User Location Information, Age of Location Information, N2 SM Information (Secondary RAT usage data)). The Cause in step 5 is the same Cause in step 2. If List of PDU Session ID(s) with active N3 user plane is included in step 1b, the step 5 to 7 are performed before step 2. The Operation Type is set to "UP deactivate" to indicate deactivation of user plane resources for the PDU Session. For PDU Sessions using Control Plane CIoT 5GS Optimisation and if the UE has negotiated the use of extended Idle mode DRX, the AMF informs the SMF immediately that the UE is not reachable for downlink data. For PDU Sessions using Control Plane CIoT 5GS Optimisation and if the UE has negotiated the use of MICO mode with Active Time, the AMF informs the SMF that the UE is not reachable for downlink data once the Active Time has expired. 6a [Conditional] SMF to UPF: N4 Session Modification Request (AN or N3 UPF Tunnel Info to be removed, Buffering on/off). For PDU Sessions not using Control Plane CIoT 5GS Optimisation, the SMF initiates an N4 Session Modification procedure indicating the need to remove Tunnel Info of AN or UPF terminating N3. Buffering on/off indicates whether the UPF shall buffer incoming DL PDU or not. If the SMF has received an indication from the AMF that the UE is not reachable for downlink data for PDU Sessions using Control Plane CIoT 5GS Optimisation, the SMF may initiate an N4 Session Modification procedure to activate buffering in the UPF. If multiple UPFs are used in the PDU Session and the SMF determines to release the UPF terminating N3, step 6a is performed towards the UPF (e.g. PSA) terminating N9 towards the current N3 UPF. The SMF then releases the N4 session towards the N3 UPF (the N4 release is not shown on the call flow). See clause 4.4 for more details. If the cause of AN Release is because of User Inactivity, or UE Redirection, the SMF shall preserve the GBR QoS Flows. If the AN Release is due to the reception of Service Request or Registration Request to establish another NAS signalling connection via (R)AN as described in step 2, the SMF also preserves the GBR QoS Flows. In any other case, the SMF shall trigger the PDU Session Modification procedure (see clause 4.3.3) for the GBR QoS Flows of the UE after the AN Release procedure is completed. If the redundant I-UPFs are used for URLLC, the N4 Session Modification Request procedure is done for each I-UPF. In this case, SMF selects both the redundant I-UPFs to buffer the DL packets for this PDU Session or drop the DL packets for this PDU session or forward the DL packets for this PDU session to the SMF, based on buffering instruction provided by the SMF as described in clause 5.8.3.2 or 5.8.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the redundant N3 tunnels are used for URLLC, the N4 Session Modification Request procedure to the UPF of N3 terminating point is to remove the dual AN Tunnel Info for N3 tunnel of the corresponding PDU Session. 6b. [Conditional] UPF to SMF: N4 Session Modification Response acknowledging the SMF request. See clause 4.4 for more details. 7. [Conditional] SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response for step 5. Upon completion of the procedure, the AMF considers the N2 and N3 as released and enters CM-IDLE state. After completion of the procedure, the AMF reports towards the NF consumers are triggered for cases in clause 4.15.4. After completion of the procedure, if steps 5 to 7 were performed before step 2 and the AMF received N2 SM information from NG-RAN in step 4 (e.g. Secondary RAT usage data report), the AMF initiates a Nsmf_PDUSession_UpdateSMContext towards SMF to deliver the N2 SM information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.6 |
3,173 | 6.3.3.2 Layer mapping for spatial multiplexing | For spatial multiplexing, the layer mapping shall be done according to Table 6.3.3.2-1. The number of layers is less than or equal to the number of antenna ports used for transmission of the physical channel. The case of a single codeword mapped to multiple layers is only applicable when the number of cell-specific reference signals is four or when the number of UE-specific reference signals is two or larger. For subslot/slot-PDSCH, the number of codewords is always one. Table 6.3.3.2-1: Codeword-to-layer mapping for spatial multiplexing | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.3.2 |
3,174 | 9.2.2.3 RAN-Based Notification Area | A UE in the RRC_INACTIVE state can be configured by the last serving NG-RAN node with an RNA, where: - the RNA can cover a single or multiple cells, and shall be contained within the CN registration area; in this release Xn connectivity should be available within the RNA; - a RAN-based notification area update (RNAU) is periodically sent by the UE and is also sent when the cell reselection procedure of the UE selects a cell that does not belong to the configured RNA. There are several different alternatives on how the RNA can be configured: - List of cells: - A UE is provided an explicit list of cells (one or more) that constitute the RNA. - List of RAN areas: - A UE is provided (at least one) RAN area ID, where a RAN area is a subset of a CN Tracking Area or equal to a CN Tracking Area. A RAN area is specified by one RAN area ID, which consists of a TAC and optionally a RAN area Code; - A cell broadcasts one or, in case of network sharing with multiple cell ID broadcast, more RAN area IDs in the system information. NG-RAN may provide different RNA definitions to different UEs but not mix different definitions to the same UE at the same time. UE shall support all RNA configuration options listed above. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.2.3 |
3,175 | 5.2.1 Downlink transmission scheme | Demodulation Reference Signal (DMRS) based spatial multiplexing is supported for Physical Downlink Shared Channel (PDSCH). Up to 8, 12, 16 and 24 orthogonal DL DMRS ports are supported for type 1, type 2, enhanced type 1, and enhanced type 2 DMRS respectively. Up to 8 orthogonal DL DMRS ports per UE are supported for SU-MIMO and up to 4 orthogonal DL DMRS ports per UE are supported for MU-MIMO. The number of SU-MIMO code words is one for 1-4 layer transmissions and two for 5-8 layer transmissions. The DMRS and corresponding PDSCH are transmitted using the same precoding matrix and the UE does not need to know the precoding matrix to demodulate the transmission. The transmitter may use different precoder matrix for different parts of the transmission bandwidth, resulting in frequency selective precoding. The UE may also assume that the same precoding matrix is used across a set of Physical Resource Blocks (PRBs) denoted Precoding Resource Block Group (PRG). Transmission durations from 2 to 14 symbols in a slot is supported. Aggregation of multiple slots with Transport Block (TB) repetition is supported. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.1 |
3,176 | 10.5.4.22 Repeat indicator | The purpose of the repeat indicator information element is to indicate how the associated repeated information elements shall be interpreted, when included in a message. The repeat indicator information element is included immediately before the first occurrence of the associated information element which will be repeated in a message. "Mode 1" refers to the first occurrence of that information element, "mode 2" refers to the second occurrence of that information element in the same message. The repeat indicator information element is coded as shown in figure 10.5.109/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.129/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The repeat indicator is a type 1 information element. Figure 10.5.109/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Repeat indicator information element Table 10.5.129/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Repeat indicator 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.22 |
3,177 | 6.8.5.1 UMTS security context | A UMTS security context in GSM BSS is only established for UMTS subscribers with a ME that is capable of UMTS AKA under GSM BSS controlled by a R99+ VLR/SGSN. At the network side, two cases are distinguished: a) In case of a handover to a UTRAN controlled by the same MSC/VLR, the UMTS cipher/integrity keys CK and IK from the key set used before the intersystem handover are sent to the target RNC. b) In case of a handover to a UTRAN controlled by another MSC/VLR, the initial MSC/VLR sends the UMTS cipher/integrity keys CK and IK from the key set used before the intersystem handover to the new RNC via the new MSC/VLR that controls the target RNC. The initial MSC/VLR remains the anchor point for throughout the service. The anchor MSC/VLR also derives and sends to the non-anchor MSC/VLR the 64-bit GSM cipher key Kc, if any 64-bit ciphering algorithm is permitted, and/or the 128-bit ciphering key Kc128 if a 128-bit ciphering algorithm is also permitted. The non-anchor MSC/VLR stores all keys. This is done to allow subsequent handovers in a non-anchor R99+ MSC/VLR. At the user side, in either case, the ME applies the UMTS cipher/integrity keys CK and IK from the key set which was used before the intersystem handover. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.5.1 |
3,178 | 6.2.7 Handling of DNN based congestion control | The network may detect and start performing DNN based congestion control when one or more DNN congestion criteria as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] are met. If the UE does not provide a DNN for a non-emergency PDU session, then the network uses the selected DNN. In the UE, 5GS session management timers T3396 for DNN based congestion control are started and stopped on a per DNN basis except for an LADN DNN in case of PLMN. For an LADN DNN, 5GS session management timers T3396 for DNN based congestion control is applied to the registered PLMN and its equivalent PLMNs. In case of SNPN, if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs, in the UE, 5GS session management timers T3396 for DNN based congestion control are started and stopped on a per DNN and SNPN basis. If the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, in the UE 5GS session management timers T3396 for DNN based congestion control are started and stopped on a per DNN, SNPN and selected entry of the "list of subscriber data" or selected PLMN subscription basis. Upon receipt of a 5GMM message or 5GSM message from the network for which the UE needs to stop the running timers T3396 associated with an LADN DNN as specified in subclause 6.3.2.3, 6.3.3.3, 6.4.1.4.2 and 6.4.2.4.2, only the running timer T3396 which is associated with the PLMN and equivalent PLMNs where the timer was started is stopped. In an SNPN, if the UE supports equivalent SNPNs, the UE applies the timer T3396 for all the equivalent SNPNs, otherwise the UE applies the timer T3396 for the registered SNPN. The DNN associated with T3396 is the DNN provided by the UE during the PDU session establishment. If no DNN is provided by the UE along the PDU SESSION ESTABLISHMENT REQUEST, then T3396 is associated with no DNN. For this purpose, the UE shall memorize the DNN provided to the network during the PDU session establishment. The timer T3396 associated with no DNN will never be started due to any 5GSM procedure related to an emergency PDU session. If the timer T3396 associated with no DNN is running, it does not affect the ability of the UE to request an emergency PDU session. In a PLMN, if T3396 is running or is deactivated, then the UE is not allowed to initiate the: a) PDU session establishment procedure; b) PDU session modification procedure; or c) NAS transport procedure for sending CIoT user data; for the respective DNN or without a DNN unless the UE is a UE configured for high priority access in selected PLMN or to report a change of 3GPP PS data off UE status. In an SNPN, if T3396 is running or is deactivated for the registered SNPN, is associated with a DNN or with no DNN, with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, with the selected entry of the "list of subscriber data" or the selected PLMN subscription, then the UE is not allowed to initiate the a) PDU session establishment procedure; or b) PDU session modification procedure; for the respective DNN or without a DNN unless the UE is a UE configured for high priority access in the RSNPN or to report a change of 3GPP PS data off UE status. In an SNPN, if the UE supports equivalent SNPNs, the timer T3396 is running or is deactivated for all the equivalent SNPNs, is associated with a DNN or no DNN, with the RSNPN or an equivalent SNPN, and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, then the UE is not allowed to initiate the: a) PDU session establishment procedure; or b) PDU session modification procedure; for the respective DNN or without a DNN unless the UE is a UE configured for high priority access in selected SNPN or to report a change of 3GPP PS data off UE status. | 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.7 |
3,179 | 5.8.2.12 Reporting of the UE MAC addresses used in a PDU Session | For Ethernet PDU Session type, the SMF may control the UPF to report the different MAC (Ethernet) addresses used as source address of frames sent UL by the UE in a PDU Session. These MAC addresses are called UE MAC addresses. This control and the corresponding reporting takes place over N4. NOTE: This is e.g. used to support reporting of all UE MAC addresses in a PDU Session to the PCF as described in clause 5.6.10.2. The UPF reports the removal of a UE MAC address based on the detection of absence of traffic during an inactivity time. The inactivity time value is provided by the SMF to the UPF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.12 |
3,180 | 28.3.2.2.8 Prefixed Operator Identifier based N3IWF FQDN | The Prefixed Operator Identifier based N3IWF FQDN, used by a UE that is configured with Slice-specific N3IWF prefix configuration, shall be constructed as specified for the Operator Identifier based N3IWF FQDN in clause 28.3.2.2.2, with the addition of <Prefix> before the labels "n3iwf.5gc". The <Prefix> is provided in the Slice-specific N3IWF prefix configuration for the selected PLMN that contains S-NSSAIs that match all (or most, in case there is no full match) of the S-NSSAIs that the UE is going to include in the Requested NSSAI in the subsequent Registration procedure, and is specified in 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [144]. The Prefixed Operator Identifier based N3IWF FQDN shall be constructed as follows: "<Prefix>.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" As an example, the Prefixed Operator Identifier based N3IWF FQDN for MNC 123, MCC 345 with an example <Prefix> value "ssn3iwfprefix-Y" is coded in the DNS as: "ssn3iwfprefix-Y.n3iwf.5gc.mnc123.mcc345.pub.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.2.8 |
3,181 | D.8.7.2 Conditional IE errors | When upon receipt of a UPDS message the UE diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error, or when it receives a UPDS message containing at least one syntactically incorrect conditional IE, the UE shall ignore the message. When the network receives a message and diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a message containing at least one syntactically incorrect conditional IE, the network shall either: a) try to treat the message (the exact further actions are implementation dependent); or b) ignore the message. | 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 | D.8.7.2 |
3,182 | 5.5.4.15a CondEvent D2 (Distance between UE and a moving referenceLocation1 is above threshold1 and distance between UE and a moving referenceLocation2 is below threshold2) | The UE shall: 1> consider the entering condition for this event to be satisfied when both condition D2-1 and condition D2-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition D2-3 or condition D2-4, i.e. at least one of the two, as specified below, are fulfilled; Inequality D2-1 (Entering condition 1) Inequality D2-2 (Entering condition 2) Inequality D2-3 (Leaving condition 1) Inequality D2-4 (Leaving condition 2) The variables in the formula are defined as follows: Ml1 is the distance between UE and a moving reference location for this event, not taking into account any offsets. The moving reference location is determined based on referenceLocation1 as defined within reportConfigNR for this event and the corresponding epoch time and satellite ephemeris. Ml2 is the distance between UE and a moving reference location for this event, not taking into account any offsets. The moving reference location is determined based on referenceLocation2 as defined within reportConfigNR for this event and the corresponding epoch time and satellite ephemeris Hys is the hysteresis parameter for this event (i.e. hysteresisLocation as defined within reportConfigNR for this event). Thresh1 is the threshold for this event defined as a distance, configured with parameter distanceThreshFromReference1, from a moving reference location configured with parameter referenceLocation1 within reportConfigNR for this event. Thresh2 is the threshold for this event defined as a distance, configured with parameter distanceThreshFromReference2, from a moving reference location configured with parameter referenceLocation2 within reportConfigNR for this event. Ml1 is expressed in meters. Ml2 is expressed in the same unit as Ml1. Hys is expressed in the same unit as Ml1. Thresh1 is expressed in the same unit as Ml1. Thresh2 is expressed in the same unit as Ml1. Editor's Note: FFS whether location-based conditional handover (condEventD2) applies only to moving cells or a combination of moving and quasi-Earth fixed cells for the choice of source and target cells. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.15a |
3,183 | 5.16.4.9 Handling of PDU Sessions for Emergency Services | The QoS Flows of a PDU Session associated with the emergency DNN shall be dedicated for IMS emergency sessions and shall not allow any other type of traffic. The emergency contexts shall not be changed to non-emergency contexts and vice versa. The UPF shall block any traffic that is not from or to addresses of network functions (e.g. P-CSCF) providing Emergency Services. If there is already an emergency PDU Session over a given Access Type (3GPP access or non-3GPP access), the UE shall not request another emergency PDU Session over any Access Type except for handing over the existing emergency PDU Session to the other Access Type. If the SMF receives a new emergency PDU session establishment request and an emergency PDU Session exists for the same UE over any Access Type, the SMF shall remove the existing SM context locally and clear the associated resources in the network and proceed with the new request. NOTE: If the UE releases emergency PDU session locally and requests for establishment of a new one before the SMF has released the emergency PDU session due to PDU session inactivity as specified in clause 4.3.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], the above duplicate emergency PDU session handling in the network removes the old emergency PDU session as part of establishing a new one. This releases all emergency call back resources related with the old emergency PDU Session. The ARP reserved for emergency service shall only be assigned to QoS Flows associated with an emergency PDU Session. If the UE is Emergency Registered over a given access, it shall not request a PDU Session to any other DNN over this access. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.4.9 |
3,184 | 5.2.27.3.2 Ntsctsf_QoSandTSCAssistance_Create operation | Service operation name: Ntsctsf_QoSandTSCAssistance_Create Description: The consumer requests the network to provide a specific QoS for an AF session or a UE or a group of UEs. Inputs, Required: AF Identifier, Target UE identifier (UE address, or GPSI or External Group Identifier), Flow description(s) or External Application Identifier, QoS Reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Inputs, Optional: sponsored data connectivity information if applicable, Alternative Service Requirements (containing one or more QoS Reference parameters or Requested Alternative QoS Parameter Set(s) in a prioritized order), 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 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], DNN if available, flow direction, Burst Arrival Time at UE (uplink) or UPF (downlink), Periodicity, Time domain, Survival Time, BAT Window or Capability for BAT adaptation, Periodicity Range. Outputs, Required: Transaction Reference ID, result. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.3.2 |
3,185 | 4.16.1.8 Number of Path Update Successful at Secondary Node Additions | a) This measurement provides the number of path update successful at Secondary Node Additions. b) CC c) On receipt of an E-RAB modification confirmation message by the MN from MME (after MN sends SgNB reconfiguration complete message) when path switch is needed. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ENDC.PathUpdateSucctAtSNAddition. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.16.1.8 |
3,186 | 4.23.16.1 Handover of a PDU Session procedure from untrusted non-3GPP to 3GPP access (non-roaming and roaming with local breakout) | The following impacts are applicable to clause 4.9.2.1 when a PDU Session is handover from untrusted non-3GPP to 3GPP access (non-roaming and roaming with local breakout): - Step2: The UE performs a PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified clause 4.23.5.1 and an I-SMF and an I-UPF may be selected and inserted for this PDU. If I-SMF is selected, in the Nsmf_PDUSession_Create Response the SMF shall include all QoS information for the QoS Flow(s) applicable to the PDU Session for the target access so that when sending the PDU Session Establishment Accept, within the N1 SM container and in the N2 SM information, the I-SMF can include all QoS information (e.g. QoS Rule(s) in N1 SM container, QFI(s) and QoS Profile(s) in N2 SM information) for the QoS Flow(s). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.16.1 |
3,187 | A.2 Procedural specification A.2.1 General principles | The procedural specification provides an overall high level description regarding the UE behaviour in a particular scenario. It should be noted that most of the UE behaviour associated with the reception of a particular field is covered by the applicable parts of the PDU specification. The procedural specification may also include specific details of the UE behaviour upon reception of a field, but typically this should be done only for cases that are not easy to capture in the PDU clause e.g. general actions, more complicated actions depending on the value of multiple fields. Likewise, the procedural specification need not specify the UE requirements regarding the setting of fields within the messages that are sent to the network i.e. this may also be covered by the PDU specification. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.2 |
3,188 | 7.7.2 Conditional IE errors | When upon receipt of a 5GMM or 5GSM message the UE diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error, or when it receives a 5GMM or 5GSM message containing at least one syntactically incorrect conditional IE, the UE shall ignore the message and shall return a status message (5GMM STATUS or 5GSM STATUS depending on the EPD) with cause #100 "conditional IE error". When the network receives a message and diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a message containing at least one syntactically incorrect conditional IE, the network shall either: a) try to treat the message (the exact further actions are implementation dependent); or b) ignore the message except that it should return a status message (5GMM STATUS or 5GSM STATUS depending on the EPD) with cause #100 "conditional IE error". | 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 | 7.7.2 |
3,189 | – UL-CCCH-Message | The UL-CCCH-Message class is the set of 48-bits RRC messages that may be sent from the UE to the Network on the uplink CCCH logical channel. -- ASN1START -- TAG-UL-CCCH-MESSAGE-START UL-CCCH-Message ::= SEQUENCE { message UL-CCCH-MessageType } UL-CCCH-MessageType ::= CHOICE { c1 CHOICE { rrcSetupRequest RRCSetupRequest, rrcResumeRequest RRCResumeRequest, rrcReestablishmentRequest RRCReestablishmentRequest, rrcSystemInfoRequest RRCSystemInfoRequest }, messageClassExtension SEQUENCE {} } -- TAG-UL-CCCH-MESSAGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,190 | 5.2.8.3.3 Nsmf_EventExposure_Subscribe service operation | Service operation name: Nsmf_EventExposure_Subscribe. Description: This service operation is used by an NF to subscribe or modify a subscription for event notifications on a specified PDU Session or for all PDU Sessions of one UE, group of UE(s) or any UE. Input, Required: NF ID, Target of Event Reporting as defined in clause 5.2.8.3.1, (set of) Event ID(s) defined in clause 5.2.8.3.1, Notification Target Address (+ Notification Correlation ID), Event Reporting Information defined in Table 4.15.1-1. Input, Optional: Event Filter(s) associated with each Event ID; Event Filter(s) are defined in clause 5.2.8.3.1, Subscription Correlation ID (in the case of modification of the event subscription), Expiry time, DNN, S-NSSAI, DNAI, UPFId, UPF event exposure information (Type of measurement, granularity of measurement, reporting suggestion information, etc. associated with the UPF Event IDs as described in clause 4.15.4.5). NOTE: The SMF is generally meant to determine the UPF to contact for a subscription related to UPF event exposure. UPF ID is only provided to indicate a UP Path as defined in Table 6.4.1-1 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50], i.e. when the NWDAF has received the target UPF as part of statistics of observed service experience on an UP path involving that UPF. Output, Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Expiry time (required if the subscription can be expired based on the operator's policy). Output, Optional: First corresponding event report is included, if available (see clause 4.15.1). Notification Target Address (+ Notification Correlation ID) is used to correlate Notifications sent by SMF or UPF with this subscription. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.3.3 |
3,191 | 5.15.18.2 S-NSSAI location availability information | S-NSSAI location availability information defines additional restrictions to the usage of an S-NSSAI in TAs where the Network Slice availability does not match the TA boundaries. The AMF is configured per S-NSSAI whether to send the S-NSSAI location availability information to supporting UEs. The S-NSSAI location availability information sent to the UE includes, for each applicable S-NSSAI of the Configured NSSAI, Location information indicating the cells of TAs in the RA where the related S-NSSAI is available if the S-NSSAI is not available in all the cells of the TA. If the UE has indicated that the UE supports S-NSSAI location availability information in the 5GMM Core Network Capability (see clause 5.4.4a), the AMF may, based on OAM configuration, configure the UE with S-NSSAI location availability information for one or more S-NSSAIs when the AMF allocates an RA where the Network Slice availability does not match whole TAs, by including the S-NSSAI location availability information in the Registration Accept message or the UE Configuration Command message. A UE that receives S-NSSAI location availability information applies the information as follows. 1. If the S-NSSAI is rejected in the RA or rejected partially in the RA or rejected with a cause code that allows attempting to register the S-NSSAI again, the UE can request the S-NSSAI only if the S-NSSAI location availability information indicates that the S-NSSAI is available at the cell where the UE is camping. 2. If the S-NSSAI is in the Partially Allowed NSSAI or in the Allowed NSSAI and the UE is in a cell within the RA but outside the NS-AoS of the S-NSSAI, the following applies: a. The UE shall not activate User Plane resources for any already established PDU Session with that S-NSSAI. b. The UE shall not send user data as payload of a NAS message (see clause 5.31.4.1) in uplink direction. c. For an already established PDU Session, the UE and the SMF may initiate signalling for PDU Session release procedure or PDU Session modification procedure (i.e. for PS data off status change reporting). 3. If the S-NSSAI is in the Partially Allowed NSSAI or in the Allowed NSSAI, and the UE in CM-CONNECTED state moves from a cell inside the NS-AoS to a cell outside the NS-AoS and the User Plane resources are active for a PDU Session on that S-NSSAI, the NG-RAN deactivates the User Plane resources as described in the AN initiated modification of a PDU Session in clause 4.3.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 1: By Radio Resource Management and existing mechanisms in NG-RAN, handover can be used to keep the UE in the NS-AoS or steer the UE to enter the NS-AoS as long as radio conditions allow it. NOTE 2: Since the S-NSSAI location availability information is not a used as a trigger for the UE to perform MRU due to mobility, i.e. the UE performs MRU due to mobility upon changing to a new TA outside the UE's Registration Area, the S-NSSAI remains registered and is included in the Allowed NSSAI when the UE exits the NS-AoS. If the S-NSSAI is subject for NSAC, the S-NSSAI is counted towards NSAC as described in clause 5.15.11 also when the UE is outside the NS-AoS. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.18.2 |
3,192 | 4.2.9.2 Network Slice-Specific Authentication and Authorization | Figure 4.2.9.2-1: Network Slice-Specific Authentication and Authorization procedure 1. For S-NSSAIs that are requiring Network Slice-Specific Authentication and Authorization, based on change of subscription information, or triggered by the AAA-S, the AMF may trigger the start of the Network Slice Specific Authentication and Authorization procedure. If Network Slice Specific Authentication and Authorization is triggered as a result of Registration procedure, the AMF may determine, based on UE Context in the AMF, that for some or all S-NSSAI(s) subject to Network Slice Specific Authentication and Authorization, the UE has already been authenticated following a Registration procedure on a first access. Depending on Network Slice Specific Authentication and Authorization result (e.g. success/failure) from the previous Registration, the AMF may decide, based on Network policies, to skip Network Slice Specific Authentication and Authorization for these S-NSSAIs during the Registration on a second access. If the Network Slice Specific Authentication and Authorization procedure corresponds to a re-authentication and re-authorization procedure triggered as a result of AAA Server-triggered UE re-authentication and re-authorization for one or more S-NSSAIs, as described in 4.2.9.2, or triggered by the AMF based on operator policy or a subscription change and if S-NSSAIs that are requiring Network Slice-Specific Authentication and Authorization are included in the Allowed NSSAI for each Access Type, the AMF selects an Access Type to be used to perform the Network Slice Specific Authentication and Authorization procedure based on network policies. 2. The AMF may send an EAP Identity Request for the S-NSSAI in a NAS MM Transport message including the S-NSSAI. This is the S-NSSAI of the H-PLMN, not the locally mapped S-NSSAI value. 3. The UE provides the EAP Identity Response for the S-NSSAI alongside the S-NSSAI in an NAS MM Transport message towards the AMF. 4. The AMF sends the EAP Identity Response to the NSSAAF in a Nnssaaf_NSSAA_Authenticate Request (EAP Identity Response, GPSI, S-NSSAI). NOTE: If the UE subscription includes multiple GPSIs, the AMF uses any GPSI in the list provided by the UDM for NSSAA procedures. 5. If the AAA-P is present (e.g. because the AAA-S belongs to a third party and the operator deploys a proxy towards third parties), the NSSAAF forwards the EAP ID Response message to the AAA-P, otherwise the NSSAAF forwards the message directly to the AAA-S. The NSSAAF is responsible to send the NSSAA requests to the appropriate AAA-S based on local configuration of AAA-S address per S-NSSAI. The NSSAAF uses towards the AAA-P or the AAA-S an AAA protocol message of the same protocol supported by the AAA-S. 6. The AAA-P forwards the EAP Identity message to the AAA-S addressable by the AAA-S address together with S-NSSAI and GPSI. The AAA-S stores the GPSI to create an association with the EAP Identity in the EAP ID response message, so the AAA-S can later use it to revoke authorization or to trigger reauthentication. 7-14. EAP-messages are exchanged with the UE. One or more than one iteration of these steps may occur. 15. EAP authentication completes. The AAA-S stores the S-NSSAI for which the authorisation has been granted, so it may decide to trigger reauthentication and reauthorization based on its local policies. An EAP-Success/Failure message is delivered to the AAA-P (or if the AAA-P is not present, directly to the NSSAAF) with GPSI and S-NSSAI. 16. If the AAA-P is used, the AAA-P sends an AAA Protocol message including (EAP-Success/Failure, S-NSSAI, GPSI) to the NSSAAF. 17. The NSSAAF sends the Nnssaaf_NSSAA_Authenticate Response (EAP-Success/Failure, S-NSSAI, GPSI) to the AMF. 18. The AMF transmits a NAS MM Transport message (EAP-Success/Failure) to the UE. The AMF shall store the EAP result for each S-NSSAI for which the NSSAA procedure in steps 1-17 was executed. 19a. [Conditional] If a new Allowed NSSAI (i.e. including any new S-NSSAIs in a Requested NSSAI for which the NSSAA procedure succeeded and/or excluding any S-NSSAI(s) in the existing Allowed NSSAI for the UE for which the procedure has failed, or including default S-NSSAI(s) if all S-NSSAIs in a Requested NSSAI or in the existing Allowed NSSAI are subject to NSSAA and due to failure of the NSSAA procedures, they cannot be in the Allowed NSSAI)) and/or new Rejected S-NSSAIs (i.e. including any S-NSSAI(s) in the existing Allowed NSSAI for the UE for which the procedure has failed, or any new requested S-NSSAI(s) for which the NSSAA procedure failed) need to be delivered to the UE, or if the AMF re-allocation is required, the AMF initiates the UE Configuration Update procedure, for each Access Type, as described in clause 4.2.4.2. If the Network Slice-Specific Re-Authentication and Re-Authorization fails and there are PDU session(s) established that are associated with the S-NSSAI for which the NSSAA procedure failed, the AMF shall initiate the PDU Session Release procedure as specified in clause 4.3.4 to release the PDU sessions with the appropriate cause value. 19b. [Conditional] If the Network Slice-Specific Authentication and Authorization fails for all S-NSSAIs (if any) in the existing Allowed NSSAI for the UE and (if any) for all S-NSSAIs in the Requested NSSAI and no default S-NSSAI could be added in the Allowed NSSAI, the AMF shall execute the Network-initiated Deregistration procedure described in clause 4.2.2.3.3 and it shall include in the explicit De-Registration Request the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.9.2 |
3,193 | O.3 Information element identifier | The information element identifier and its use are defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. For the information elements defined in subclause O.4, the coding of the information element identifier bits is defined in table O.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . For a method to determine from the information element identifier whether an unknown information element is of type 1 or 2 (i.e. it is an information element of one octet length) or type 4 (i.e. the next octet is the length indicator indicating the length of the remaining of the information element) see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20], subclause 11.2.4. Table O.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Information element identifier coding for user-user protocol information elements | 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 | O.3 |
3,194 | 8.5.2 TAU Procedure | NOTE: This procedure is based on clause 4.11.1.3.2 in TS 23.502[ Procedures for the 5G System (5GS) ] [8] and only includes steps and descriptions that are relevant to security. Figure 8.5.2-1: Idle mode mobility from 5G to 4G 1. The UE initiates the TAU procedure by sending a TAU Request to the MME with a mapped EPS GUTI derived from the 5G GUTI and its EPS security capabilities. The mapped EPS GUTI contains the information of the AMF that has the latest UE context in the 5G network. The UE integrity protects the TAU Request message using the current 5G NAS security context identified by the 5G GUTI used to derive the mapped EPS GUTI. More precisely, the UE shall compute the NAS MAC for the TAU request as it is done for a 5G NAS message over a 3GPP access. The NAS Uplink COUNT for integrity protection of the TAU request shall use the same value as the 5G NAS Uplink COUNT. Consequently, this results in an increase of the stored NAS Uplink COUNT value in the NAS COUNT pair associated with the 3GPP access. The corresponding ngKSI value of the 5G Security context is included in the eKSI parameter of the TAU Request message. 2. Upon receipt of the TAU Request, the MME obtains the AMF address from the mapped EPS GUTI value. 3. The MME forwards the complete TAU Request message including the eKSI, NAS-MAC and mapped EPS GUTI in the Context Request message. 4. The AMF shall use the eKSI value field to identify the 5G NAS security context and use it to verify the TAU Request message as if it was a 5G NAS message received over 3GPP access. 5. If the verification is successful, the AMF shall derive a mapped EPS NAS security context as described in clause 8.6.1. The AMF shall set the EPS NAS algorithms to the ones indicated earlier to the UE in a NAS SMC as described in clause 6.7.2. The AMF shall include the mapped EPS NAS security context in the Context Response message it sends to the MME. The AMF shall never transfer 5G security parameters to an entity outside the 5G system. 6. The UE shall derive a mapped EPS NAS security context as described in clause 8.6.1. The UE shall select the EPS algorithms using the ones received in an earlier NAS SMC from the AMF as described in clause 6.7.2. The UE shall immediately activate the mapped EPS security context and be ready to use it for the processing of the TAU Accept message in step 7. 7. The MME compares the UE security algorithms to its configured list after it receives the Context Response message. If an algorithm change is required, the MME shall select the NAS algorithm which has the highest priority from its configured list and is also present in the UE 5G security capabilities and initiate an NAS SMC to the UE. Otherwise, step 8~10 shall be skipped. 8 - 10. The MME and the UE performs an NAS SMC to derive new NAS keys with the new algorithms as described in Clause 7.2.8.1.2 of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. 11. The MME completes the procedure with a TAU Accept message. After successful completion of the TAU procedure, the UE shall delete any mapped 5G security context. After deleting the mapped 5G security context, if the UE has a full non-current native 5G NAS security context then the UE shall make the non-current native 5G NAS security context the current one. 8.5.3 Initial Attach Procedure NOTE: This procedure is based on clause 4.11.1.5.2 in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The Initial Attach procedure shall use the security mechanism for the TAU procedure in clause 8.5.2. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 8.5.2 |
3,195 | 9.2.1.4 TDD (CSI measurements in case two CSI subframe sets are configured) | The following requirements apply to UE Category ≥1. For the parameters specified in Table 9.2.1.4-1, and using the downlink physical channels specified in tables C.3.2-1 for Cell 1, C3.3-1 for Cell 2 and C.3.2-2, the reported CQI value according to RC.2 TDD / RC.6 TDD in Table A.4-1 in subframes overlapping with aggressor cell ABS and non-ABS subframes shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER in non-ABS subframes using the transport format indicated by median CQI obtained by reports in CSI subframe sets CCSI,1 is less than or equal to 0.1, the BLER in non-ABS subframes using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER in non-ABS subframes using the transport format indicated by the median CQI is greater than 0.1, the BLER in non-ABS subframes using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. The value of the median CQI obtained by reports in CSI subframe sets CCSI,0 minus the median CQI obtained by reports in CSI subframe sets CCSI,1 shall be larger than or equal to 2 and less than or equal to 5 in Test 1 and shall be larger than or equal to 0 and less than or equal to 1 in Test 2. Table 9.2.1.4-1: PUCCH 1-0 static test (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.2.1.4 |
3,196 | 8.1.2.3D Applicability and test rules for different CA with LAA SCell(s) configurations and bandwidth combination sets | The performance requirement for CA with LAA SCell(s) UE demodulation tests in Clause 8 are defined independent of CA configurations and bandwidth combination sets specified in Clause 5.6A.1. For UEs supporting different CA with LAA SCell(s) configurations and bandwidth combination sets, the applicability and test rules are defined for the tests for 2 DL CA with LAA SCell(s) in Table 8.1.2.3D-1 and in Table 8.1.2.3D-2 for 3 or more DL CA with LAA SCell(s). For simplicity, CA configuration below refers to combination of CA with LAA SCell(s) configuration and bandwidth combination set. Table 8.1.2.3D-1: Applicability and test rules for CA UE demodulation tests for CA with LAA SCell(s) with 2 DL CCs Table 8.1.2.3D-2: Applicability and test rules for CA UE demodulation tests for CA with LAA SCell(s) with 3 or more DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.1.2.3D |
3,197 | 5.2.6.34.2 Nnef_DNAIMapping_Subscribe service operation | Service operation name: Nnef_DNAIMapping_Subscribe Description: This service operation is used by the consumer to subscribe for DNAI information by providing specific information of AF and NWDAF. Inputs, Required: EAS address information i.e. IP address/IP address range or FQDN. Inputs, Optional: DNN, S-NSSAI, AF identifier, Event Reporting Information defined in Table 4.15.1-1. NOTE: If consumer wants, one-time reporting can be done by setting the Event Reporting Information as follows: event reporting mode to maximum number of reports, maximum number of reports=1 and Immediate reporting flag set. Outputs, Required: When the subscription is accepted and not one-time reporting: Subscription Correlation ID, Expiry time (required if the subscription can be expired based on the operator's policy). Outputs, Optional: DNAI, if available. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.34.2 |
3,198 | 9.3 Security header type | Bits 1 to 4 of the second octet of every 5GMM message contain the Security header type IE. This IE includes control information related to the security protection of a 5GMM message. The total size of the Security header type IE is 4 bits. The Security header type IE can take the values shown in table 9.3.1. Table 9.3.1: Security header type A 5GMM message received with the security header type encoded as 0000 shall be treated as not security protected, plain 5GS NAS message. A protocol entity sending a not security protected 5GMM message shall send the message as plain 5GS NAS message and encode the security header type as 0000. | 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.3 |
3,199 | – DRX-ConfigSecondaryGroup | The IE DRX-ConfigSecondaryGroup is used to configure DRX related parameters for the second DRX group as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]. DRX-ConfigSecondaryGroup information element -- ASN1START -- TAG-DRX-CONFIGSECONDARYGROUP-START DRX-ConfigSecondaryGroup-r16 ::= SEQUENCE { drx-onDurationTimer-r16 CHOICE { subMilliSeconds INTEGER (1..31), milliSeconds ENUMERATED { ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } }, drx-InactivityTimer-r16 ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} } -- TAG-DRX-CONFIGSECONDARYGROUP-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,200 | 5.2.8.2.11 Nsmf_PDUSession_ContextPush service operation | Service operation name: Nsmf_PDUSession_ContextPushRequest Description: This service operation is used by the SMF as Service Consumer to push one SM Context to a another SMF as NF Service Producer. It may be triggered by OAM. Input, Required: One of the following: - SM Context of identified PDU session. - Endpoint where SM Context of identified PDU session can be retrieved. The SM context includes SM context in I-SMF(or V-SMF) and SM context in SMF (or H-SMF) separately. See Table 5.2.8.2.10-1 for single SM Context stored in I-SMF or V-SMF that may be transferred to another SMF instance. Editor's note: The SM context stored in SMF(or H-SMF) is to be defined. Output, Required: Result Indication. Output, Optional: Cause. See clause 4.26.2 for an example usage of this service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.2.11 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.