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,301 | 5.6.9 Session and Service Continuity 5.6.9.1 General | The support for session and service continuity in 5G System architecture enables to address the various continuity requirements of different applications/services for the UE. The 5G System supports different session and service continuity (SSC) modes defined in this clause. The SSC mode associated with a PDU Session does not change during the lifetime of a PDU Session. The following three modes are specified with further details provided in the next clause: - With SSC mode 1, the network preserves the connectivity service provided to the UE. For the case of PDU Session of IPv4 or IPv6 or IPv4v6 type, the IP address is preserved. - With SSC mode 2, the network may release the connectivity service delivered to the UE and release the corresponding PDU Session(s). For the case of IPv4 or IPv6 or IPv4v6 type, the release of the PDU Session induces the release of IP address(es) that had been allocated to the UE. - With SSC mode 3, changes to the user plane can be visible to the UE, while the network ensures that the UE suffers no loss of connectivity. A connection through new PDU Session Anchor point is established before the previous connection is terminated in order to allow for better service continuity. For the case of IPv4 or IPv6 or IPv4v6 type, the IP address is not preserved in this mode when the PDU Session Anchor changes. NOTE: In this Release of the specification, the addition/removal procedure of additional PDU Session Anchor in a PDU Session for local access to a DN is independent from the SSC mode of the PDU Session. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.9 |
3,302 | 5.2.6.35.2 Nnef_TrafficInfluenceData_Subscribe operation | Service operation name: Nnef_TrafficInfluenceData_Subscribe Description: The NF consumer subscribes for the notifications of AF traffic influence request information. Inputs, Required: Data Set Identifier (i.e. Application data), Data Subset Identifier (i.e. AF traffic influence request information), Data Key(s), Notification Target Address, Event Reporting Information defined in Table 4.15.1-1. Inputs, Optional: None. Outputs, Required: When the subscription is accepted: Subscription Correlation ID. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.35.2 |
3,303 | 4.3.8 Change of Network Slice instance for PDU Sessions | When a Network Slice instance for the existing PDU Session is required to be changed as described in clause 5.15.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the AMF deletes the old NSI ID corresponding to the Network Slice instance that is congested or no longer available and informs the SMF of the PDU Session(s) which is selected by using such old NSI ID to release this PDU session with appropriate cause value as described in clause 4.3.4.2. If so, the SMF triggers the impacted UE(s) to establish new PDU session(s) associated with the same S-NSSAI by using the procedures for PDU Session(s) of SSC mode 2 or SSC mode 3 as defined in clause 4.3.5. When UE initiates PDU Session Establishment procedure, the AMF may select a new Network Slice instance for the given S-NSSAI during PDU Session Establishment by querying the NSSF as described in the clause 4.3.2.2.3. If there is no Network Slice instance available, the network may change the related network slice(s) for the UE as described in clause 5.15.5.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.8 |
3,304 | 4.3.28 Restriction of use of Enhanced Coverage | Support of UEs in Enhanced Coverage is specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. The usage of Enhanced Coverage may require use of extensive resources (e.g. radio and signalling resources) from the network. This feature enables the operator to prevent specific subscribers from using Enhanced Coverage. The UE indicates its capability of support for restriction of use of Enhanced Coverage in Attach and TAU procedure for the RAT it is camping on to the MME. MME receives Enhanced Coverage Restricted parameter from the HSS. This parameter is kept as part of subscription data in the HSS and specifies per PLMN whether the enhanced coverage functionality is restricted or not for the UE. For roaming UEs, if HSS doesn't provide any Enhanced Coverage Restricted parameter or the provided Enhanced Coverage Restricted parameter is in conflict with the roaming agreement, the MME uses default Enhanced Coverage Restricted parameter locally configured in the VPLMN based on the roaming agreement with the subscriber's HPLMN. The UE shall assume that restriction for use of Enhanced Coverage is same in the equivalent PLMNs. If the UE includes the support for restriction of use of Enhanced Coverage, MME sends Enhanced Coverage Restricted parameter to the UE in the Attach/TAU Accept message. The UE shall use the value of Enhanced Coverage Restricted parameter to determine if enhanced coverage feature is restricted or not. NOTE: How this parameter is used by UE at AS layer is defined in the RAN specification. The UE assumes Enhanced Coverage is allowed unless explicitly restricted by the network for a PLMN. NB-IoT cells also broadcast the support of restriction of use of Enhanced Coverage as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]). If the MME has sent the Enhanced Coverage Restricted parameter to the UE, the MME provides an Enhanced Coverage Restricted parameter to the eNodeB via S1 signalling during paging, and whenever the UE context is established in RAN, e.g. during service request procedure, attach procedure, and TAU procedure. | 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.28 |
3,305 | 5.7.10.4 Actions for the Random Access report determination | Upon successfully performing random-access procedure initialized with 4-step or 2-step RA type, or upon failed or successfully completed on-demand system information acquisition procedure in RRC_IDLE or RRC_INACTIVE state, or upon failed or successfully completed RA-SDT operation as specified in clause 5.3.13.5, the UE shall: 1> if the RPLMN or the PLMN selected by upper layers (see TS24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]) from the PLMN(s) included in the plmn-IdentityList in SIB1 is not included in plmn-IdentityList stored in a non-empty VarRA-Report; or 1> if the registered SNPN or the SNPN selected by upper layers (see TS24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]) from the list of SNPN(s) included in the NPN-IdentityInfoList in SIB1is not included in plmn-IdentityList stored in a non-empty VarRA-Report: 2> clear the information included in VarRA-Report; 1> if the UE is not in SNPN access mode and if the number of RA-Report entries stored in the ra-ReportList in VarRA-Report is less than maxRAReport: 2> if the number of PLMN entries in plmn-IdentityList stored in VarRA-Report is less than maxPLMN; or 2> if the number of PLMN entries in plmn-IdentityList stored in VarRA-Report is equal to maxPLMN and the list of EPLMNs is subset of or equal to the plmn-IdentityList stored in VarRA-Report: 3> append the following contents associated to the successfully completed random-access procedure or the failed or successfully completed on-demand system information acquisition procedure as a new entry in the VarRA-Report: 4> if the list of EPLMNs has been stored by the UE: 5> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN) without exceeding the limit of maxPLMN; 4> else: 5> set the plmn-Identity, in plmn-IdentityList, to the PLMN selected by upper layers (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]) from the PLMN(s) included in the plmn-IdentityInfoList in SIB1; 4> set the cellId to the global cell identity and the tracking area code, if available, otherwise to the physical cell identity and carrier frequency of the cell in which the corresponding random-access preamble was transmitted; 4> if the UE supports spCell ID indication: 5> if the corresponding random-access procedure was performed on an SCell of MCG: 6> set the spCellId to the global cell identity of the PCell; 5> if the corresponding random-access procedure was performed on an SCell of SCG: 6> set the spCellId to the global cell identity of the PSCell, if available, otherwise, set the spCellId to the global cell identity of the PCell; 5> if the corresponding random-access procedure was performed on PSCell: 6> if the cellId is not set to the global cell identity of the PSCell, set the spCellId to the global cell identity of the PCell; 4> set the raPurpose to include the purpose of triggering the random-access procedure; 4> set the ra-InformationCommon as specified in clause 5.7.10.5. 1> if the UE is in SNPN access mode and if the number of RA-Report entries stored in the ra-ReportList in VarRA-Report is less than maxRAReport: 2> if the number of SNPN identity entries in snpn-IdentityList stored in VarRA-Report is less than maxNPN; or 2> if the number of SNPN identity entries in snpn-IdentityList stored in VarRA-Report is equal to maxNPN and the list of equivalent SNPN(s) is subset of or equal to the snpn-IdentityList stored in VarRA-Report: 3> append the following contents associated to the successfully completed random-access procedure or the failed or successfully completed on-demand system information acquisition procedure as a new entry in the VarRA-Report: 4> if the list of equivalent SNPN(s) has been stored by the UE: 5> set the snpn-IdentityList to include the list of equivalent SNPN(s) stored by the UE (i.e. includes the registered SNPN) without exceeding the limit of maxNPN; 4> else: 5> set the snpn-Identity, in snpn-IdentityList, to the SNPN identity selected by upper layers (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]) from the SNPN identities included in the NPN-IdentityInfoList in SIB1; 4> set the cellId to the global cell identity and the tracking area code, if available, otherwise to the physical cell identity and carrier frequency of the cell in which the corresponding random-access preamble was transmitted; 4> if the UE supports spCell ID indication: 5> if the corresponding random-access procedure was performed on an SCell of MCG: 6> set the spCellId to the global cell identity of the PCell; 5> if the corresponding random-access procedure was performed on an SCell of SCG: 6> set the spCellId to the global cell identity of the PSCell, if available, otherwise, set the spCellId to the global cell identity of the PCell; 5> if the corresponding random-access procedure was performed on PSCell: 6> if the cellId is not set to the global cell identity of the PSCell, set the spCellId to the global cell identity of the PCell; 4> set the raPurpose to include the purpose of triggering the random-access procedure; 4> set the ra-InformationCommon as specified in clause 5.7.10.5. The UE may discard the random access report information, i.e. release the UE variable VarRA-Report, 48 hours after the last successful random access procedure or the failed or successfully completed on-demand system information acquisition procedure or the failed or successfully completed RA-SDT procedure related information is added to the VarRA-Report. NOTE 1: Void. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.10.4 |
3,306 | 5.2.12 UDR Services 5.2.12.1 General | The following Data Set Identifiers shall be considered in this release: Subscription Data, Policy Data, Application data and Data for Exposure. The corresponding Data Subset Identifiers and Data (Sub)Key(s) are defined in Table 5.2.12.2.1-1. The set of Data Set Identifiers shall be extensible to cater for new identifiers as well as for operator specific identifiers and related data to be consumed. The following table illustrates the UDR Services. Table 5.2.12.1-1: NF services provided by UDR The following table shows the Exposure data that may be stored in the UDR along with a time stamp using Data Management (DM) Service: NOTE: When the data in Table 5.2.12.1-2 need to be monitored in real time, they should be monitored directly at the originating NF (e.g. registration state changes may be monitored via the Namf_EventExposure service) and not use the stored information from UDR if it is not the latest. It is expected that such dynamically changing information (e.g. UE reachability status) is used for statistical purpose and analytics. Table 5.2.12.1-2: Exposure data stored in the UDR | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.12 |
3,307 | 7A.2.4 Authentication for devices that do not support 5GC NAS over WLAN access | A N5CW device is capable to register to 5GC with 3GPP credentials and to establish 5GC connectivity via a trusted WLAN access network. The reference architecture is captured in clause 4.2.8.5.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The 3GPP credentials are stored as defined in clause 6.1.1.1. The Trusted WLAN Interworking Function (TWIF) provides interworking functionality that enables connectivity with 5GC and implements the NAS protocol stack and exchanges NAS messages with the AMF on behalf of the N5CW device. A single EAP-AKA’ authentication procedure is executed for connecting the N5CW device both to the trusted WLAN access network and to the 5G core network. Figure 7A.2.4-1: Authentication Procedure for N5CW 0. The N5CW device selects a PLMN and a trusted WLAN that supports "5G connectivity-without-NAS" to this PLMN by using the procedure specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2] clause 6.3.12a, "Access Network selection for devices that do not support 5GC NAS over WLAN". Steps 1-10: Initial registration to 5GC. 1. The N5CW device associates with the trusted WLAN network and the EAP-AKA’ authentication procedure is initiated. 2. The N5CW device shall provide its Network Access Identity (NAI) The Trusted WLAN Access Point (TWAP) selects a Trusted WLAN Interworking Function (TWIF), e.g. based on the received realm, and sends an AAA request to the selected TWIF. If the N5CW device registers to 5GC over 3GPP access for the first time when the above procedure is initiated, then the NAI shall include the SUCI. The SUCI shall be constructed as specified in clause 6.12.2. If the N5CW device has registered to 5GC over 3GPP access when the above procedure is initiated, then the NAI includes the 5G-GUTI assigned to the N5CW device over 3GPP access. This enables the TWIF in step 4a below to select the same AMF as the one serving the N5CW device over 3GPP access. 3. The TWIF shall create a 5GC Registration Request message on behalf of the N5CW device. The TWIF shall use default values to populate the parameters in the Registration Request message, which are the same for all N5CW device that do not support 5G NAS. The Registration type indicates "Initial Registration". 4. The TWIF shall select an AMF (e.g. by using the 5G-GUTI in the NAI, if provided by the N5CW device) and shall send an N2 message to the AMF including the Registration Request, the User Location and an AN Type. 5. In case the AMF triggers an authentication procedure, it sends a request to AUSF by sending Nausf_UEAuthentication_Authenticate Request message. The Nausf_UEAuthentication_Authenticate Request message contains SUCI or SUPI (in case of a valid 5G-GUTI is received by the AMF). The request message contains also an indication that the request is from a N5CW device. Even if the AMF already has a security context identified by 5G-GUTI, the AMF shall initiate the primary authentication. NOTE 1: To avoid key stream reuse when deriving KTWIF from KAMF, the KAMF always needs to be refreshed by a renewed primary authentication. 6. The AUSF shall send Nudm_UEAuthentication_Get Request to the UDM including SUCI or SUPI and the N5CW indication. 7. Upon reception of the Nudm_UEAuthentication_Get Request, the UDM shall invoke SIDF if a SUCI is received. SIDF shall de-conceal SUCI to gain SUPI before UDM can process the request. The UDM may select an authentication method based on the "realm" part of the SUPI, the N5CW device indicator, a combination of the "realm" part and the N5CW device indicator, or the UDM local policy. 8. The EAP-AKA’ procedure will be trigged to perform mutual authentication between the N5CW device and the home network as specified in clause 6.1.3.1. EAP-AKA' takes place between the N5CW device and AUSF. Over the N2 interface, the EAP messages are encapsulated within NAS Authentication messages. The EAP-AKA’ messages exchanged between the N5CW Device and the TWIF shall be encapsulated into the layer-2 packets, e.g. into IEEE 802.3/802.1x packets, into IEEE 802.11/802.1x packets, into PPP packets, etc. 9. The NAS security context is not be required in this scenario. The AMF shall derive an KTWIF key from the received KAMF key as specified in Annex A.9. NAS security between AMF and TWIF is established similar to unauthenticated emergency calls, i.e. with NULL encryption and NULL integrity protection. NOTE 2: N5CW devices does not support NAS; therefore, using the NAS counter is not possible in N5CW devices. 10a. The AMF shall send NAS Security Mode Command to the TWIF. The NAS Security Mode Command shall contain the EAP-Success message and the NULL security algorithms. 10b. The TWIF shall not forward the EAP-Success to the N5CW directly, instead, it shall store the EAP-Success message and wait for KTWIF. 10c. The TWIF shall send the NAS Security Mode Complete message to the AMF. 11. The AMF sends an N2 Initial Context Setup Request and provides the KTWIF key to TWIF. 12. The TWIF shall derive a TNAP key, KTNAP, from the KTNGF key as specified in Appendix A.22 and send the TNAP key and the EAP-Success message to the Trusted WLAN Access Point, which forwards the EAP-Success to the N5CW device. The TNAP key corresponds to the PMK (Pairwise Master Key) which is used to secure the WLAN air-interface communication according to IEEE 802.11 [80]. A layer-2 or layer-3 connection is established between the Trusted WLAN Access Point and the TWIF for transporting all user-plane traffic of the N5CW device to TWIF. This connection is later bound to an N3 connection that is created for this N5CW device. 13. The TWIF shall send N2 Initial Context Setup Response message to the AMF. 14. The following steps are captured in clause 4.12b.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [8]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7A.2.4 |
3,308 | 4.5.6 Cell Unavailable Time | This measurement provides the length of time the cell has been unavailable for each cause. DER (n=1) This measurement is obtained by accumulating the time periods when the cell is unavailable per cause. The possible cause could be “manual intervention”, “fault” and “energy saving”. The sum of all supported per cause measurements shall equal the total time periods of cell unavailability. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value (in seconds). The number of measurements is equal to the number of supported causes plus a possible sum value identified by the .sum suffix. The measurement name has the form RRU.CellUnavailableTime.cause. Where cause identifies the cause resuling in cell unavailable. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS This measurement is to support KPI “E-UTRAN Cell Availability” defined in [13]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.5.6 |
3,309 | 6.3.4.7 Symbol / Slot boundary time mask for slot TTI | The slot boundary time mask defines the observation period between the previous/subsequent slot and the (reference) slot. A transient period at a symbol boundary within a slot is only allowed in the case of Intra slot frequency hopping. For the cases when the slot contains SRS the time masks in subclause 6.3.4.8 shall apply. There are no additional requirements on UE transmit power beyond that which is required in subclause 6.2.2 and subclause 6.6.2.3 For slot boundary, the time maks specified in subclause 6.3.4.4 shall apply with a transient time of 10µs intead of 20µs. For frequency hopping within the slot, the time masks specified in subclause 6.3.4.5 shall apply. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.4.7 |
3,310 | – UEInformationResponse | The UEInformationResponse message is used by the UE to transfer information requested by the network. Signalling radio bearer: SRB1 or SRB2 (when logged measurement information is included) RLC-SAP: AM Logical channel: DCCH Direction: UE to network UEInformationResponse message -- ASN1START -- TAG-UEINFORMATIONRESPONSE-START UEInformationResponse-r16 ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { ueInformationResponse-r16 UEInformationResponse-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } UEInformationResponse-r16-IEs ::= SEQUENCE { measResultIdleEUTRA-r16 MeasResultIdleEUTRA-r16 OPTIONAL, measResultIdleNR-r16 MeasResultIdleNR-r16 OPTIONAL, logMeasReport-r16 LogMeasReport-r16 OPTIONAL, connEstFailReport-r16 ConnEstFailReport-r16 OPTIONAL, ra-ReportList-r16 RA-ReportList-r16 OPTIONAL, rlf-Report-r16 RLF-Report-r16 OPTIONAL, mobilityHistoryReport-r16 MobilityHistoryReport-r16 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UEInformationResponse-v1700-IEs OPTIONAL } UEInformationResponse-v1700-IEs ::= SEQUENCE { successHO-Report-r17 SuccessHO-Report-r17 OPTIONAL, connEstFailReportList-r17 ConnEstFailReportList-r17 OPTIONAL, coarseLocationInfo-r17 OCTET STRING OPTIONAL, nonCriticalExtension UEInformationResponse-v1800-IEs OPTIONAL } UEInformationResponse-v1800-IEs ::= SEQUENCE { flightPathInfoReport-r18 FlightPathInfoReport-r18 OPTIONAL, successPSCell-Report-r18 SuccessPSCell-Report-r18 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FlightPathInfoReport-r18 ::= SEQUENCE (SIZE (0..maxWayPoint-r18)) OF WayPoint-r18 WayPoint-r18 ::= SEQUENCE { wayPointLocation-r18 OCTET STRING, timeStamp-r18 AbsoluteTimeInfo-r16 OPTIONAL } LogMeasReport-r16 ::= SEQUENCE { absoluteTimeStamp-r16 AbsoluteTimeInfo-r16, traceReference-r16 TraceReference-r16, traceRecordingSessionRef-r16 OCTET STRING (SIZE (2)), tce-Id-r16 OCTET STRING (SIZE (1)), logMeasInfoList-r16 LogMeasInfoList-r16, logMeasAvailable-r16 ENUMERATED {true} OPTIONAL, logMeasAvailableBT-r16 ENUMERATED {true} OPTIONAL, logMeasAvailableWLAN-r16 ENUMERATED {true} OPTIONAL, ... } LogMeasInfoList-r16 ::= SEQUENCE (SIZE (1..maxLogMeasReport-r16)) OF LogMeasInfo-r16 LogMeasInfo-r16 ::= SEQUENCE { locationInfo-r16 LocationInfo-r16 OPTIONAL, relativeTimeStamp-r16 INTEGER (0..7200), servCellIdentity-r16 CGI-Info-Logging-r16 OPTIONAL, measResultServingCell-r16 MeasResultServingCell-r16 OPTIONAL, measResultNeighCells-r16 SEQUENCE { measResultNeighCellListNR MeasResultListLogging2NR-r16 OPTIONAL, measResultNeighCellListEUTRA MeasResultList2EUTRA-r16 OPTIONAL }, anyCellSelectionDetected-r16 ENUMERATED {true} OPTIONAL, ..., [[ inDeviceCoexDetected-r17 ENUMERATED {true} OPTIONAL ]] } ConnEstFailReport-r16 ::= SEQUENCE { measResultFailedCell-r16 MeasResultFailedCell-r16, locationInfo-r16 LocationInfo-r16 OPTIONAL, measResultNeighCells-r16 SEQUENCE { measResultNeighCellListNR MeasResultList2NR-r16 OPTIONAL, measResultNeighCellListEUTRA MeasResultList2EUTRA-r16 OPTIONAL }, numberOfConnFail-r16 INTEGER (1..8), perRAInfoList-r16 PerRAInfoList-r16, timeSinceFailure-r16 TimeSinceFailure-r16, ... } ConnEstFailReportList-r17 ::= SEQUENCE (SIZE (1..maxCEFReport-r17)) OF ConnEstFailReport-r16 MeasResultServingCell-r16 ::= SEQUENCE { resultsSSB-Cell MeasQuantityResults, resultsSSB SEQUENCE{ best-ssb-Index SSB-Index, best-ssb-Results MeasQuantityResults, numberOfGoodSSB INTEGER (1..maxNrofSSBs-r16) } OPTIONAL } MeasResultFailedCell-r16 ::= SEQUENCE { cgi-Info CGI-Info-Logging-r16, measResult-r16 SEQUENCE { cellResults-r16 SEQUENCE{ resultsSSB-Cell-r16 MeasQuantityResults }, rsIndexResults-r16 SEQUENCE{ resultsSSB-Indexes-r16 ResultsPerSSB-IndexList } } } RA-ReportList-r16 ::= SEQUENCE (SIZE (1..maxRAReport-r16)) OF RA-Report-r16 RA-Report-r16 ::= SEQUENCE { cellId-r16 CHOICE { cellGlobalId-r16 CGI-Info-Logging-r16, pci-arfcn-r16 PCI-ARFCN-NR-r16 }, ra-InformationCommon-r16 RA-InformationCommon-r16 OPTIONAL, raPurpose-r16 ENUMERATED {accessRelated, beamFailureRecovery, reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure, noPUCCHResourceAvailable, requestForOtherSI, msg3RequestForOtherSI-r17, lbtFailure-r18, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, ..., [[ spCellID-r17 CGI-Info-Logging-r16 OPTIONAL ]] } RA-InformationCommon-r16 ::= SEQUENCE { absoluteFrequencyPointA-r16 ARFCN-ValueNR, locationAndBandwidth-r16 INTEGER (0..37949), subcarrierSpacing-r16 SubcarrierSpacing, msg1-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-FrequencyStartCFRA-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, msg1-SubcarrierSpacingCFRA-r16 SubcarrierSpacing OPTIONAL, msg1-FDM-r16 ENUMERATED {one, two, four, eight} OPTIONAL, msg1-FDMCFRA-r16 ENUMERATED {one, two, four, eight} OPTIONAL, perRAInfoList-r16 PerRAInfoList-r16, ..., [[ perRAInfoList-v1660 PerRAInfoList-v1660 OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16 ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16 ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msgA-RO-FrequencyStartCFRA-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msgA-SubcarrierSpacing-r17 SubcarrierSpacing OPTIONAL, msgA-RO-FDM-r17 ENUMERATED {one, two, four, eight} OPTIONAL, msgA-RO-FDMCFRA-r17 ENUMERATED {one, two, four, eight} OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17 ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL, msgA-TransMax-r17 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, msgA-MCS-r17 INTEGER (0..15) OPTIONAL, nrofPRBs-PerMsgA-PO-r17 INTEGER (1..32) OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17 INTEGER (1..maxNrofUL-Allocations) OPTIONAL, frequencyStartMsgA-PUSCH-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, nrofMsgA-PO-FDM-r17 ENUMERATED {one, two, four, eight} OPTIONAL, dlPathlossRSRP-r17 RSRP-Range OPTIONAL, intendedSIBs-r17 SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17 OPTIONAL, ssbsForSI-Acquisition-r17 SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-Index OPTIONAL, msgA-PUSCH-PayloadSize-r17 BIT STRING (SIZE (5)) OPTIONAL, onDemandSISuccess-r17 ENUMERATED {true} OPTIONAL ]], [[ usedFeatureCombination-r18 ReportedFeatureCombination-r18 OPTIONAL, triggeredFeatureCombination-r18 ReportedFeatureCombination-r18 OPTIONAL, attemptedBWP-InfoList-r18 SEQUENCE (SIZE (1..maxNrofBWPs)) OF AttemptedBWP-Info-r18 OPTIONAL, numberOfLBTFailures-r18 INTEGER (1..128) OPTIONAL, perRAInfoList-v1800 PerRAInfoList-v1800 OPTIONAL, sdt-Failed-r18 ENUMERATED {true} OPTIONAL ]] } AttemptedBWP-Info-r18 ::= SEQUENCE { locationAndBandwidth-r18 INTEGER (0..37949), subcarrierSpacing-r18 SubcarrierSpacing } ReportedFeatureCombination-r18 ::= SEQUENCE { redCap-r18 ENUMERATED {true} OPTIONAL, smallData-r18 ENUMERATED {true} OPTIONAL, nsag-r18 NSAG-List-r17 OPTIONAL, msg3-Repetitions-r18 ENUMERATED {true} OPTIONAL, triggered-S-NSSAI-List-r18 SEQUENCE (SIZE (1..maxNrofS-NSSAI)) OF S-NSSAI OPTIONAL } PerRAInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-r16 PerRAInfoList-v1660 ::= SEQUENCE (SIZE (1..200)) OF PerRACSI-RSInfo-v1660 PerRAInfo-r16 ::= CHOICE { perRASSBInfoList-r16 PerRASSBInfo-r16, perRACSI-RSInfoList-r16 PerRACSI-RSInfo-r16 } PerRAInfoList-v1800 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-v1800 PerRAInfo-v1800 ::= CHOICE { perRASSBInfoList-v1800 PerRASSBInfo-v1800, perRACSI-RSInfoList-v1800 PerRACSI-RSInfo-v1800 } PerRASSBInfo-r16 ::= SEQUENCE { ssb-Index-r16 SSB-Index, numberOfPreamblesSentOnSSB-r16 INTEGER (1..200), perRAAttemptInfoList-r16 PerRAAttemptInfoList-r16 } PerRASSBInfo-v1800 ::= SEQUENCE { allPreamblesBlocked ENUMERATED {true} OPTIONAL, lbt-Detected-r18 ENUMERATED {true} OPTIONAL, ... } PerRACSI-RSInfo-r16 ::= SEQUENCE { csi-RS-Index-r16 CSI-RS-Index, numberOfPreamblesSentOnCSI-RS-r16 INTEGER (1..200) } PerRACSI-RSInfo-v1660 ::= SEQUENCE { csi-RS-Index-v1660 INTEGER (1..96) OPTIONAL } PerRACSI-RSInfo-v1800 ::= SEQUENCE { allPreamblesBlocked ENUMERATED {true} OPTIONAL, lbt-Detected-r18 ENUMERATED {true} OPTIONAL, ... } PerRAAttemptInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAAttemptInfo-r16 PerRAAttemptInfo-r16 ::= SEQUENCE { contentionDetected-r16 BOOLEAN OPTIONAL, dlRSRPAboveThreshold-r16 BOOLEAN OPTIONAL, ..., [[ fallbackToFourStepRA-r17 ENUMERATED {true} OPTIONAL ]] } SIB-Type-r17 ::= ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType9, sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14-v1610, spare6, spare5, spare4, spare3, spare2, spare1} RLF-Report-r16 ::= CHOICE { nr-RLF-Report-r16 SEQUENCE { measResultLastServCell-r16 MeasResultRLFNR-r16, measResultNeighCells-r16 SEQUENCE { measResultListNR-r16 MeasResultList2NR-r16 OPTIONAL, measResultListEUTRA-r16 MeasResultList2EUTRA-r16 OPTIONAL } OPTIONAL, c-RNTI-r16 RNTI-Value, previousPCellId-r16 CHOICE { nrPreviousCell-r16 CGI-Info-Logging-r16, eutraPreviousCell-r16 CGI-InfoEUTRALogging } OPTIONAL, failedPCellId-r16 CHOICE { nrFailedPCellId-r16 CHOICE { cellGlobalId-r16 CGI-Info-Logging-r16, pci-arfcn-r16 PCI-ARFCN-NR-r16 }, eutraFailedPCellId-r16 CHOICE { cellGlobalId-r16 CGI-InfoEUTRALogging, pci-arfcn-r16 PCI-ARFCN-EUTRA-r16 } }, reconnectCellId-r16 CHOICE { nrReconnectCellId-r16 CGI-Info-Logging-r16, eutraReconnectCellId-r16 CGI-InfoEUTRALogging } OPTIONAL, timeUntilReconnection-r16 TimeUntilReconnection-r16 OPTIONAL, reestablishmentCellId-r16 CGI-Info-Logging-r16 OPTIONAL, timeConnFailure-r16 INTEGER (0..1023) OPTIONAL, timeSinceFailure-r16 TimeSinceFailure-r16, connectionFailureType-r16 ENUMERATED {rlf, hof}, rlf-Cause-r16 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, beamFailureRecoveryFailure, lbtFailure-r16, bh-rlfRecoveryFailure, t312-expiry-r17, spare1}, locationInfo-r16 LocationInfo-r16 OPTIONAL, noSuitableCellFound-r16 ENUMERATED {true} OPTIONAL, ra-InformationCommon-r16 RA-InformationCommon-r16 OPTIONAL, ..., [[ csi-rsRLMConfigBitmap-v1650 BIT STRING (SIZE (96)) OPTIONAL ]], [[ lastHO-Type-r17 ENUMERATED {cho, daps, spare2, spare1} OPTIONAL, timeConnSourceDAPS-Failure-r17 TimeConnSourceDAPS-Failure-r17 OPTIONAL, timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17 OPTIONAL, choCellId-r17 CHOICE { cellGlobalId-r17 CGI-Info-Logging-r16, pci-arfcn-r17 PCI-ARFCN-NR-r16 } OPTIONAL, choCandidateCellList-r17 ChoCandidateCellList-r17 OPTIONAL ]], [[ pSCellId-r18 CHOICE { cellGlobalId-r18 CGI-Info-Logging-r16, pci-arfcn-r18 PCI-ARFCN-NR-r16 } OPTIONAL, mcgRecoveryFailureCause-r18 ENUMERATED {t316-Expiry, scgDeactivated, spare2, spare1} OPTIONAL, scgFailureCause-r18 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, synchReconfigFailureSCG, scg-ReconfigFailure, srb3-IntegrityFailure, scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, t312-Expiry-r16, bh-RLF-r16, beamFailure-r17, spare3, spare2, spare1 } OPTIONAL, elapsedTimeSCGFailure-r18 ElapsedTimeSCGFailure-r18 OPTIONAL, voiceFallbackHO-r18 ENUMERATED {true} OPTIONAL, measResultLastServCell-RSSI-r18 RSSI-Range-r16 OPTIONAL, measResultNeighFreqList-RSSI-r18 MeasResultNeighFreqList-RSSI-r18 OPTIONAL, bwp-Info-r18 AttemptedBWP-Info-r18 OPTIONAL, elapsedTimeT316-r18 ElapsedTimeT316-r18 OPTIONAL ]] }, eutra-RLF-Report-r16 SEQUENCE { failedPCellId-EUTRA CGI-InfoEUTRALogging, measResult-RLF-Report-EUTRA-r16 OCTET STRING, ..., [[ measResult-RLF-Report-EUTRA-v1690 OCTET STRING OPTIONAL ]] } } SuccessHO-Report-r17 ::= SEQUENCE { sourceCellInfo-r17 SEQUENCE { sourcePCellId-r17 CGI-Info-Logging-r16, sourceCellMeas-r17 MeasResultSuccessHONR-r17 OPTIONAL, rlf-InSourceDAPS-r17 ENUMERATED {true} OPTIONAL }, targetCellInfo-r17 SEQUENCE { targetPCellId-r17 CGI-Info-Logging-r16, targetCellMeas-r17 MeasResultSuccessHONR-r17 OPTIONAL }, measResultNeighCells-r17 SEQUENCE { measResultListNR-r17 MeasResultList2NR-r16 OPTIONAL, measResultListEUTRA-r17 MeasResultList2EUTRA-r16 OPTIONAL } OPTIONAL, locationInfo-r17 LocationInfo-r16 OPTIONAL, timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17 OPTIONAL, shr-Cause-r17 SHR-Cause-r17 OPTIONAL, ra-InformationCommon-r17 RA-InformationCommon-r16 OPTIONAL, upInterruptionTimeAtHO-r17 UPInterruptionTimeAtHO-r17 OPTIONAL, c-RNTI-r17 RNTI-Value OPTIONAL, ..., [[ eutraTargetCellInfo-r18 SEQUENCE { targetPCellId-r18 CGI-InfoEUTRALogging, targetCellMeas-r18 MeasQuantityResultsEUTRA OPTIONAL } OPTIONAL, measResultServCell-RSSI-r18 RSSI-Range-r16 OPTIONAL, measResultNeighFreqList-RSSI-r18 MeasResultNeighFreqList-RSSI-r18 OPTIONAL, eutra-C-RNTI-r18 EUTRA-C-RNTI OPTIONAL, timeSinceSHR-r18 TimeSinceSHR-r18 OPTIONAL ]] } SuccessPSCell-Report-r18 ::= SEQUENCE { pCellId-r18 CGI-Info-Logging-r16, sourcePSCellInfo-r18 SEQUENCE { sourcePSCellId-r18 CGI-Info-Logging-r16, sourcePSCellMeas-r18 MeasResultSuccessHONR-r17 OPTIONAL } OPTIONAL, targetPSCellInfo-r18 SEQUENCE { targetPSCellId-r18 CHOICE { cellGlobalId-r18 CGI-Info-Logging-r16, pci-arfcn-r18 PCI-ARFCN-NR-r16 }, targetPSCellMeas-r18 MeasResultSuccessHONR-r17 OPTIONAL }, measResultNeighCells-r18 SEQUENCE { measResultListNR-r18 MeasResultList2NR-r16 OPTIONAL, measResultListEUTRA-r18 MeasResultList2EUTRA-r16 OPTIONAL } OPTIONAL, spr-Cause-r18 SPR-Cause-r18 OPTIONAL, timeSinceCPAC-Reconfig-r18 TimeSinceCPAC-Reconfig-r18 OPTIONAL, locationInfo-r18 LocationInfo-r16 OPTIONAL, ra-InformationCommon-r18 RA-InformationCommon-r16 OPTIONAL, sn-InitiatedPSCellChange-r18 ENUMERATED {true} OPTIONAL, ... } MeasResultNeighFreqList-RSSI-r18 ::= SEQUENCE(SIZE (1..maxFreq)) OF MeasResultNeighFreq-RSSI-r18 MeasResultNeighFreq-RSSI-r18 ::= SEQUENCE { ssbFrequency-r18 ARFCN-ValueNR OPTIONAL, refFreqCSI-RS-r18 ARFCN-ValueNR OPTIONAL, measResult-RSSI-r18 RSSI-Range-r16 OPTIONAL } MeasResultList2NR-r16 ::= SEQUENCE(SIZE (1..maxFreq)) OF MeasResult2NR-r16 MeasResultList2EUTRA-r16 ::= SEQUENCE(SIZE (1..maxFreq)) OF MeasResult2EUTRA-r16 MeasResult2NR-r16 ::= SEQUENCE { ssbFrequency-r16 ARFCN-ValueNR OPTIONAL, refFreqCSI-RS-r16 ARFCN-ValueNR OPTIONAL, measResultList-r16 MeasResultListNR } MeasResultListLogging2NR-r16 ::= SEQUENCE(SIZE (1..maxFreq)) OF MeasResultLogging2NR-r16 MeasResultLogging2NR-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueNR, measResultListLoggingNR-r16 MeasResultListLoggingNR-r16 } MeasResultListLoggingNR-r16 ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultLoggingNR-r16 MeasResultLoggingNR-r16 ::= SEQUENCE { physCellId-r16 PhysCellId, resultsSSB-Cell-r16 MeasQuantityResults, numberOfGoodSSB-r16 INTEGER (1..maxNrofSSBs-r16) OPTIONAL } MeasResult2EUTRA-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueEUTRA, measResultList-r16 MeasResultListEUTRA } MeasResultRLFNR-r16 ::= SEQUENCE { measResult-r16 SEQUENCE { cellResults-r16 SEQUENCE{ resultsSSB-Cell-r16 MeasQuantityResults OPTIONAL, resultsCSI-RS-Cell-r16 MeasQuantityResults OPTIONAL }, rsIndexResults-r16 SEQUENCE{ resultsSSB-Indexes-r16 ResultsPerSSB-IndexList OPTIONAL, ssbRLMConfigBitmap-r16 BIT STRING (SIZE (64)) OPTIONAL, resultsCSI-RS-Indexes-r16 ResultsPerCSI-RS-IndexList OPTIONAL, csi-rsRLMConfigBitmap-r16 BIT STRING (SIZE (96)) OPTIONAL } OPTIONAL } } MeasResultSuccessHONR-r17::= SEQUENCE { measResult-r17 SEQUENCE { cellResults-r17 SEQUENCE{ resultsSSB-Cell-r17 MeasQuantityResults OPTIONAL, resultsCSI-RS-Cell-r17 MeasQuantityResults OPTIONAL }, rsIndexResults-r17 SEQUENCE{ resultsSSB-Indexes-r17 ResultsPerSSB-IndexList OPTIONAL, resultsCSI-RS-Indexes-r17 ResultsPerCSI-RS-IndexList OPTIONAL } } } ChoCandidateCellList-r17 ::= SEQUENCE(SIZE (1..maxNrofCondCells-r16)) OF ChoCandidateCell-r17 ChoCandidateCell-r17 ::= CHOICE { cellGlobalId-r17 CGI-Info-Logging-r16, pci-arfcn-r17 PCI-ARFCN-NR-r16 } SHR-Cause-r17 ::= SEQUENCE { t304-cause-r17 ENUMERATED {true} OPTIONAL, t310-cause-r17 ENUMERATED {true} OPTIONAL, t312-cause-r17 ENUMERATED {true} OPTIONAL, sourceDAPS-Failure-r17 ENUMERATED {true} OPTIONAL, ... } SPR-Cause-r18 ::= SEQUENCE { t304-cause-r18 ENUMERATED {true} OPTIONAL, t310-cause-r18 ENUMERATED {true} OPTIONAL, t312-cause-r18 ENUMERATED {true} OPTIONAL, ... } TimeSinceFailure-r16 ::= INTEGER (0..172800) MobilityHistoryReport-r16 ::= VisitedCellInfoList-r16 TimeUntilReconnection-r16 ::= INTEGER (0..172800) TimeSinceCHO-Reconfig-r17 ::= INTEGER (0..1023) TimeSinceCPAC-Reconfig-r18 ::= INTEGER (0.. 1023) TimeConnSourceDAPS-Failure-r17 ::= INTEGER (0..1023) UPInterruptionTimeAtHO-r17 ::= INTEGER (0..1023) ElapsedTimeT316-r18 ::= INTEGER (0..2000) ElapsedTimeSCGFailure-r18 ::= INTEGER (0..1023) TimeSinceSHR-r18 ::= INTEGER (0..172800) -- TAG-UEINFORMATIONRESPONSE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,311 | 5.29.2 5G VN group management | 5G System supports management of 5G VN Group identification and membership (i.e. definition of 5G VN group identifiers and membership) and 5G VN Group data (i.e. definition of 5G VN group data). The 5G VN Group management can be configured by a network administrator or can be managed dynamically by AF. A 5G VN group is characterized by the following: - 5G VN group identities: External Group ID and Internal Group ID are used to identify the 5G VN group. - 5G VN group membership: The 5G VN group members are uniquely identified by GPSI. The group as described in clause 5.2.3.3.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] is applicable to 5G LAN-type services. - 5G VN group data. The 5G VN group data may include the following parameters: PDU session type, DNN, S-NSSAI and Application descriptor, the indication that the 5G VN group is associated with 5G VN group communication, Information related with secondary authentication / authorization (e.g. to enable IP address assignment by the DN-AAA, Maximum Group Data Rate). The Information related with secondary authentication / authorization corresponds to the procedures described in clause 5.6.6; it allows e.g. the AF to provide DN-AAA server addressing information and possibly to request the SMF to get the UE IP address from the DN-AAA server. In order to support dynamic management of 5G VN Group identification and membership, the NEF exposes a set of services to manage (e.g. add/delete/modify) 5G VN groups and 5G VN members. The NEF also exposes services to dynamically manage 5G VN group data. An AF can request provisioning of traffic characteristics, QoS parameters and monitoring of QoS parameters for a 5G VN group as described in clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. A 5G VN group is identified by the AF using External Group ID. The NEF provides the External Group ID to UDM. The UDM maps the External Group ID to Internal Group ID. For a newly created 5G VN Group, an Internal Group ID is determined by the UDM based on implementation specific means. NOTE 1: The Internal Group ID determined by UDM has to comply with the format defined in TS 23.003[ Numbering, addressing and identification ] [19]. The NEF can retrieve the Internal Group ID from UDM via Nudm_SDM_Get service operation (External Group ID, Group Identifier translation). An External Group ID for a 5G VN group corresponds to a unique set of 5G VN group data parameters. The 5G VN group configuration is either provided by OA&M or provided by an AF to the NEF. When configuration is provided by an AF, the procedures described in clause 4.15.6.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] apply for storing the 5G VN group identifiers, group membership information and group data in the UDR, as follows: - The NEF provides the External Group ID, 5G VN group membership information and 5G VN group data to the UDM. - The UDM updates the Internal Group ID-list of the corresponding UE's subscription data in UDR, if needed. - The UDM updates the Group Identifier translation in the Group Subscription data with the Internal Group ID, External Group ID and list of group members, if needed. - The UDM stores/updates the 5G VN group data (PDU session type, DNN and S-NSSAI, Application descriptor, the indication that the 5G VN group is associated with 5G VN group communication, Information related with secondary authentication / authorization, Maximum Group Data Rate) in UDR. NOTE 2: It is assumed that all members of a 5G VN group belong to the same UDM Group ID. The NEF can select a UDM instance supporting the UDM Group ID of any of the member GPSIs of the 5G VN group. NOTE 3: Shared data mechanisms as defined in TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [122] can be used to support large 5G VN groups. An AF may also configure and update the service area, QoS for the 5G VN group as described in clause 5.20b as well as other parameters (e.g. Expected UE Behaviour parameters, Network Configuration parameters, ECS Address Configuration Information, etc.) for a 5G VN group as described in clause 4.15.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If a UE is member of a 5G VN Group, UDM retrieves UE subscription data and corresponding 5G VN group data from UDR, and provides the AMF and SMF with UE subscription data with 5G VN group data included. If the 5G VN group data contains the indication that the 5G VN group is associated with 5G VN group communication, the SMF may apply the 5G VN group communication as defined in clauses 5.29.3 and 5.29.4 for the PDU Sessions accessing to the 5G VN group. The PCF generates URSP rules based on 5G VN group data. The PCF retrieves 5G VN group data from UDR. The PCF(s) that have subscribed to modifications of 5G VN group data receive(s) a Nudr_DM_Notify notification of 5G VN group data change from the UDR as defined in TS 29.505[ 5G System; Usage of the Unified Data Repository services for Subscription Data; Stage 3 ] [145]. The PCF receives from the AMF at the UE Policy association establishment the Internal Group ID(s) corresponding to a UE, so that PCF identifies the 5G VN group data that needs to be used to generate URSP rules to the UE. If the PCF is made aware of a change of UE Internal Group Identifier(s) as defined in TS 29.525[ 5G System; UE Policy Control Service; Stage 3 ] [144] or change of 5G VN group membership as defined in TS 29.505[ 5G System; Usage of the Unified Data Repository services for Subscription Data; Stage 3 ] [145], or both, the PCF then may update the URSP rules for the impacted 5G VN group members. NOTE 4: The proper way to obtain the 5G VN group membership changes of a specific UE, e.g. if the UE is added to a new 5G VN group, is via the notification of change of UE Internal Group Identifier(s) from the AMF as specified in TS 29.525[ 5G System; UE Policy Control Service; Stage 3 ] [144]. The subscription in the UDR is for being notified about changes in the 5G VN group data and in the 5G VN group membership of a specific 5G VN group. If the PCF receives the Maximum Group Data Rate as part of the 5G VN group data, it performs the group related policy control as described in clauses 6.1.5 and 6.2.1.11 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. An AF may update the UE Identities of the 5G VN group at any time after the initial provisioning. An AF may subscribe to notification of the group status changes for the 5G VN group as described in clause 5.20. The DNN, S-NSSAI provided within 5G VN group data cannot be modified after the initial provisioning. In this Release of the specification, the home network of the 5G VN group members is same. In this Release of the specification, only a 1:1 mapping between (DNN, S-NSSAI) combination and 5G VN group is supported. The PCF delivers 5G VN group configuration information (DNN, S-NSSAI, PDU session type) to the UE for each GPSI that belongs to a 5G VN group. The 5G VN group configuration information is delivered in the URSP from the PCF to the UE using the UE Configuration Update procedure for transparent UE Policy delivery as described in clause 4.2.4.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and clause 6.1.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.29.2 |
3,312 | 5.2.13.2.6 Nbsf_Management_Subscribe service operation | Service Operation name: Nbsf_Management_Subscribe Description: NEF, AF, TSCTSF or PCF for a UE can subscribe to be notified of newly registered or deregistered PCF for a PDU Session. In addition, NEF or AF can subscribe to be notified of newly registered or deregistered PCF for a UE. NOTE 1: If BSF has already the requested information at the time of the subscription, it will accept the subscription request and will immediately provide the results in the Outputs parameters. Inputs, Required: SUPI, DNN(s) [Required, if PCF subscription is for a PDU Session], S-NSSAI(s) [Required, if PCF subscription is for a PDU Session], callback URI. Inputs, Optional: GPSI, indication of registration/deregistration per (DNN, S-NSSAI). Indication of registration/deregistration per (DNN, S-NSSAI) indicates to the BSF to report when the first SM policy association is established and when the last SM policy association is terminated to the same (DNN, S-NSSAI) combination. NOTE 2: It is up to stage3 to ensure an unambiguous error proof way for the BSF to differentiate between PCF for a PDU Session and PCF for a UE. This may or may not require providing the BSF additional input parameter(s). Outputs, Required: When the subscription is accepted: Subscription Correlation ID. Outputs, Conditional: One or more instance per (DNN, S-NSSAI) of (UE address(es) [If available], PCF address(es) [If available], PCF instance ID [If available], PCF Set ID [If available], level of Binding [If available] (see clause 6.3.1.0 of TS 23.501[ System architecture for the 5G System (5GS) ] [2])) or notification of registration/deregistration per (DNN, S-NSSAI). NOTE 3: The parameter UE address(es) is not applicable in the case of PCF for a UE. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.13.2.6 |
3,313 | 5.3.2A.2 Layer mapping for spatial multiplexing | For spatial multiplexing, the layer mapping shall be done according to Table 5.3.2A.2-1. The number of layers is less than or equal to the number of antenna ports used for transmission of the physical uplink shared channel. The case of a single codeword mapped to multiple layers is only applicable when the number of antenna ports used for PUSCH is four, except for slot-PUSCH and subslot-PUSCH transmission where a single codeword is used irrespective of the number of layers. Table 5.3.2A.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 | 5.3.2A.2 |
3,314 | – SlotFormatIndicator | The IE SlotFormatIndicator is used to configure monitoring a Group-Common-PDCCH for Slot-Format-Indicators (SFI). SlotFormatIndicator information element -- ASN1START -- TAG-SLOTFORMATINDICATOR-START SlotFormatIndicator ::= SEQUENCE { sfi-RNTI RNTI-Value, dci-PayloadSize INTEGER (1..maxSFI-DCI-PayloadSize), slotFormatCombToAddModList SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF SlotFormatCombinationsPerCell OPTIONAL, -- Need N slotFormatCombToReleaseList SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL, -- Need N ..., [[ availableRB-SetsToAddModList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF AvailableRB-SetsPerCell-r16 OPTIONAL, -- Need N availableRB-SetsToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL, -- Need N switchTriggerToAddModList-r16 SEQUENCE (SIZE(1..4)) OF SearchSpaceSwitchTrigger-r16 OPTIONAL, -- Need N switchTriggerToReleaseList-r16 SEQUENCE (SIZE(1..4)) OF ServCellIndex OPTIONAL, -- Need N co-DurationsPerCellToAddModList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF CO-DurationsPerCell-r16 OPTIONAL, -- Need N co-DurationsPerCellToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL -- Need N ]], [[ switchTriggerToAddModListSizeExt-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroupMinus4-r16)) OF SearchSpaceSwitchTrigger-r16 OPTIONAL, -- Need N switchTriggerToReleaseListSizeExt-r16 SEQUENCE (SIZE(1.. maxNrofAggregatedCellsPerCellGroupMinus4-r16)) OF ServCellIndex OPTIONAL -- Need N ]], [[ co-DurationsPerCellToAddModList-r17 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF CO-DurationsPerCell-r17 OPTIONAL -- Need N ]] } CO-DurationsPerCell-r16 ::= SEQUENCE { servingCellId-r16 ServCellIndex, positionInDCI-r16 INTEGER(0..maxSFI-DCI-PayloadSize-1), subcarrierSpacing-r16 SubcarrierSpacing, co-DurationList-r16 SEQUENCE (SIZE(1..64)) OF CO-Duration-r16 } CO-DurationsPerCell-r17 ::= SEQUENCE { servingCellId-r17 ServCellIndex, positionInDCI-r17 INTEGER(0..maxSFI-DCI-PayloadSize-1), subcarrierSpacing-r17 SubcarrierSpacing, co-DurationList-r17 SEQUENCE (SIZE(1..64)) OF CO-Duration-r17 } CO-Duration-r16 ::= INTEGER (0..1120) CO-Duration-r17 ::= INTEGER (0..4480) AvailableRB-SetsPerCell-r16 ::= SEQUENCE { servingCellId-r16 ServCellIndex, positionInDCI-r16 INTEGER(0..maxSFI-DCI-PayloadSize-1) } SearchSpaceSwitchTrigger-r16 ::= SEQUENCE { servingCellId-r16 ServCellIndex, positionInDCI-r16 INTEGER(0..maxSFI-DCI-PayloadSize-1) } -- TAG-SLOTFORMATINDICATOR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,315 | 12.2.1 Virtual dial-up- and direct Access to PDNs, or ISPs through Packet Domain | The access to PDNs, or ISPs may involve specific functions such as: user authentication, user’s authorization, end to end encryption between MS and PDN/ISP, allocation of a dynamic address belonging to the PLMN/PDN/ISP addressing space, etc. For this purpose the PLMN may offer, based on configuration data: - direct access to an IP based Intranet/ISP using a protocol configuration as depicted in figure 14. Here DHCP and/or RADIUS are used between the GGSN and Intranet/ISP for performing the specific functions mentioned above. The Packet Domain may also offer access to networks based on any protocol supported by PPP through one of its Network Control Protocols (NCPs); Figure 14: Protocol stack for direct access to IP-based Intranets/ISPs - virtual dial-up access to a PDN with PPP frame tunnelling as depicted in figure 15. Figure 15: Protocol stack for virtual dial-up access with PPP frame tunnelling | 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 | 12.2.1 |
3,316 | 6.3.1.4 Distribution of subscriber identities and security data between 5G and EPS serving network domains | NOTE 1: No direct interworking between 5G networks and network of generations prior to EPS are foreseen. Therefore, only the interaction between 5G and EPS serving network domains is addressed here. The transmission of the SUPI in the clear is permitted between 5G and EPS core network entities if it has the form of an IMSI. The transmission of any unmodified 5G security contexts to a EPS core network entity is not permitted. Details of security context transfer between EPS and 5G core network entities can be found in clause 8. The transmission of a 5G authentication vector to an EPS core network entity is not permitted. The transmission of any unused EPS authentication vectors to a 5G core network entity is not permitted. If SEAF receives any unused authentication vectors (e.g. in mobility scenarios from legacy MME) they shall be dropped without any processing. NOTE 2: The rules above differ from the corresponding rules in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] , clause 6.1.6: The latter allows forwarding of UMTS authentication vectors from an SGSN to an MME and back to the same SGSN under certain conditions. But this feature goes against a strict security separation of EPS and 5G domains. As its performance advantage is questionable it was not copied into 5G. NOTE 3: Security context mapping between EPS and 5G serving networks is allowed, according to clause 8. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3.1.4 |
3,317 | – SL-ConfiguredGrantConfigDedicated-SL-PRS-RP | The IE SL-ConfiguredGrantConfig-Dedicated-SL-PRS-RP specifies the configured grant configuration information for NR sidelink positioning in a dedicated SL-PRS resource pool.. SL-ConfiguredGrantConfigDedicated-SL-PRS-RP information element -- ASN1START -- TAG-SL-CONFIGUREDGRANTCONFIGDEDICATEDSL-PRS-RP-START SL-ConfiguredGrantConfigDedicatedSL-PRS-RP-r18 ::= SEQUENCE { sl-ConfigIndexCG-r18 SL-ConfigIndexCG-r16, sl-PeriodCG-r18 SL-PeriodCG-r16 OPTIONAL, -- Need M sl-TimeOffsetCG-Type1-r18 INTEGER (0..7999) OPTIONAL, -- Need R sl-TimeReferenceSFN-Type1-r18 ENUMERATED {sfn512} OPTIONAL, -- Need S sl-ResourcePoolID-r18 SL-ResourcePoolID-r16 OPTIONAL, -- Need M sl-TimeResourceCG-Type1-r18 INTEGER (0..496) OPTIONAL, -- Need M sl-PRS-ResourceIndicationFirstType1-r18 INTEGER(0..11) OPTIONAL, -- Need M sl-PRS-ResourceIndicationFutureType1-r18 INTEGER(0..143) OPTIONAL -- Need M } -- TAG-SL-CONFIGUREDGRANTCONFIGDEDICATEDSL-PRS-RP-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,318 | 4.2.11.2a Hierarchical NSACF-based number of UEs per network slice availability check and update procedure | Figure 4.2.11.2a-1: Hierarchical NSACF-based number of UEs per network slice availability check and update procedure For an S-NSSAIs subject to counting of the number of registered UEs, if hierarchical NSACF architecture is deployed in the network the enforcement of maximum number of UEs registered for an S-NSSAI is performed as follows: 1. Same as the step 1 defined in clause 4.2.11.2. 2. In addition to the information included in the Nnsacf_NSAC_NumOfUEsUpdate_Request as described in the step 2 of clause 4.2.11.2, the AMF may provide UE already registered indication to the NSACF if the UE has been registered with the S-NSSAI in another NSAC service area before. The AMF determines the indication based on the received Allowed NSSAI information from the source AMF (in case of inter AMF handover) or from SMF+PGW-C (in case of mobility from EPS to 5GS). 3. The NSACF performs NSAC for the indicated S-NSSAI. If the update flag parameter from the AMF indicates increase, the following applies: - For NSACF which support UE admission quota based control: - If the local maximum number of UEs is not reached yet, the NSACF executes the same action as specified in the step 3 in clause 4.2.11.2. The steps 4-8 are skipped. - If the local maximum number of UEs is reached, the NSACF sends a delegation request to the Primary NSACF. Steps 4-9 are executed. - For NSACF which supports UE admission threshold-based control, as defined in clause 5.15.11.1.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]: - If the UE admission is below the threshold level, the NSACF executes the same action as the step 3 defined in clause 4.2.11.2. Steps 4-8 are skipped. - If the UE admission is at or above the threshold level and the local maximum number of UEs has not been reached, the NSACF checks whether the UE already registered indication is present. - If the UE already registered indication is not present then the NSACF immediately rejects the NSAC request. Steps 4-8 are skipped. - If the UE already registered indication is present the NSACF executes the same action as the step 3 defined in clause 4.2.11.2 in order to allow for service continuity. Steps 4-8 are skipped. - If the local maximum number has been reached and the UE already registered indication is present then the NSACF sends a delegation request of NSAC to the Primary NSACF in order to allow for service continuity. Steps 4-9 are executed. If the update flag parameter from the AMF indicates decrease, the following applies: - If the UE entry to be deleted is stored at the NSACF, the NSACF executes the same action as the step 3 defined in clause 4.2.11.2. Steps 4-8 are skipped. - If the UE entry to be deleted is not stored at the NSACF, the NSACF sends a delegation request of NSAC to the Primary NSACF. Steps 4-9 are executed. 4. If the Primary NSACF has not been discovered before, the NSACF discovers and selects the Primary NSACF which manages the entire PLMN NSAC service area according to clause 6.3.22 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 5. The NSACF invokes Nnsacf_NSAC_NumOfUEsUpdate_Request service operation to the Primary NSACF. The request includes the NSAC request information received from AMF, which may include the UE already Registered indication only if it is received from AMF and the UE admission type is quota-based. 6. The Primary NSACF performs NSAC for the indicated S-NSSAI. If the update flag parameter from the NSACF indicates increase, the following applies: - If the Primary NSACF decided to delegate the NSAC update request to the NSACF, per the applied UE admission type of the network, the Primary NSACF adjusts the local maximum number for UE quota-based admission or the UE admission threshold for UE admission-threshold in its response to the NSACF. The Primary NSACF does not create a new entry associated with the UE ID in the received NSAC request. NOTE 1: When NSACF sends a delegation request to the Primary NSACF, the Primary NSACF either increases local maximum number at NSACF or rejects the NSAC request. - For quota-based admission type and if the Primary NSACF decided not to delegate the request to the NSACF and the UE already Registered indication is not included, the Primary NSACF rejects the NSAC request. If the UE already Registered indication is included and if the Primary NSACF decided to store the UE entry, it creates a new entry associated with the UE ID within the received NSAC. If the Primary NSACF is not able to store the UE entry, the Primary NSACF rejects the request. The Primary NSACF respond accordingly the NSACF as in step 7. - For threshold-based admission and if the Primary NSACF decided not to delegate the request to the NSACF, the same action as for step 3 in clause 4.2.11.2 is executed with the replacement of NSACF with Primary NSACF. NOTE 2: To support the session continuity across different NSAC service area, the Primary NSACF always reserves part of the global maximum number for its own use, i.e. the whole global maximum number is not distributed to all contacted NSACF(s). If the update flag parameter from the NSACF indicates decrease and the UE entry is managed by the Primary NSACF, the same action as step 3 in clause 4.2.11.2 is executed with the replacement of NSACF with Primary NSAC. This applies to both admission types. 7. The Primary NSACF returns the Nnsacf_NSAC_NumOfUEsUpdate_Response message to the NSACF. The response may include the Result indication as described in step 4 in clause 4.2.11.2. If the Primary NSACF determines to adjust the configured value stored at the NSACF, the updated local maximum number of UEs or UE admission threshold is also included in the response respectively. 8. The NSACF checks the response from Primary NSACF. If the response includes the updated configured value, - The NSACF, which supports UE admission quota based control, replaces the existing local maximum number of UEs with the received updated value. The same action is executed as for step 3 in clause 4.2.11.2 based on the updated configured value. - The NSACF, which supports UE admission threshold based control, replaces the existing UE admission threshold with the received updated value. The same action is executed as for step 3 in clause 4.2.11.2 based on the updated configured value. If the response does not include the updated configured value, the NSACF returns the response to AMF based on the received NSAC response from Primary NSACF. 9. Same as for step 4 defined in clause 4.2.11.2. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.11.2a |
3,319 | 8.44 UE Time Zone | UE Time Zone is used to indicate the offset between universal time and local time in steps of 15 minutes of where the UE currently resides. The "Time Zone" field uses the same format as the "Time Zone" IE in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5]. UE Time Zone is coded as this is depicted in Figure 8.44-1. The value of the Time Zone field represents the time zone adjusted for daylight saving time. The value of the Daylight Saving Time field specifies the adjustment that has been made. The spare bits indicate unused bits, which shall be set to 0 by the sending side and which shall not be evaluated by the receiving side. Figure 8.44-1: UE Time Zone Table 8.44-2 Possible values for the "Daylight Saving Time" field and their meanings. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.44 |
3,320 | 4.3.2.12.1 PDN connection with integrity protection | At PS to CS domain change from Iu mode to A/Gb mode due to SRVCC handover of a PDN connection for which integrity protection has been activated, ciphering may be started (see 3GPP TS 44.018[ None ] [84]) without any new authentication procedure. Deduction of the appropriate security key for ciphering in A/Gb mode, depends on the current GSM or UMTS security context for the PS domain stored in the MS and the network. The ME shall handle the GSM ciphering key according to table 4.3.2.12.1. Table 4.3.2.12.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : SRVCC handover from Iu mode to A/Gb mode The network shall replace an already established GSM or UMTS security context for the CS domain, if any, when the SRVCC handover from Iu mode to A/Gb mode has been completed successfully. If the SRVCC handover from Iu mode to A/Gb mode has not been completed successfully, the MS and the network shall delete the new derived GSM or UMTS security context for the CS domain. Additionally, the network shall delete the already established GSM or UMTS security context for the CS domain, if the CKSN of the already established GSM or UMTS security context is equal to the CKSN of the new derived GSM or UMTS security context for the CS domain. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2.12.1 |
3,321 | 5.2.5.4.3 Npcf_SMPolicyControl_UpdateNotify service operation | Service operation name: Npcf_SMPolicyControl_UpdateNotify Description: Provides to the NF Service Consumer, e.g. SMF, updated Policy information for the PDU Session. Inputs, Required: SM Policy Association ID. Inputs, Optional: Policy information for the PDU Session as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and Policy Control Request Trigger(s) of SM Policy Association as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Outputs, Required: Success or Failure. Outputs, Optional: None. See clause 4.16.5.2 for the 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.5.4.3 |
3,322 | 4.2 Applicability of minimum requirements | a) In this specification the Minimum Requirements are specified as general requirements and additional requirements. Where the Requirement is specified as a general requirement, the requirement is mandated to be met in all scenarios b) For specific scenarios for which an additional requirement is specified, in addition to meeting the general requirement, the UE is mandated to meet the additional requirements. c) The reference sensitivity power levels defined in subclause 7.3 are valid for the specified reference measurement channels. d) NOTE: Receiver sensitivity degradation may occur when: 1) The UE simultaneously transmits and receives with bandwidth allocations less than the transmission bandwidth configuration (see Figure 5.6-1), and 2) Any part of the downlink transmission bandwidth is within an uplink transmission bandwidth from the downlink center subcarrier. e) The spurious emissions power requirements are for the long term average of the power. For the purpose of reducing measurement uncertainty it is acceptable to average the measured power over a period of time sufficient to reduce the uncertainty due to the statistical nature of the signal. f) The requirements in this specification for TDD operating bands apply for downlink and uplink operations using Frame Structure Type 2 [4] except for Band 46 operating with Frame Structure Type 3. g) The requirements related to subslot TTI and/or slot TTI shall apply only if UE supports multiple TTI patterns. And these requirements only apply to subslot and/or slot TTI 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 | 4.2 |
3,323 | 5.7.5.2 UE Derived QoS Rule | The UE derived QoS rule contains following parameters: - One UL Packet Filter (in the Packet Filter Set as defined in clause 5.7.6); - QFI; - Precedence value (see clause 5.7.1.9). Upon receiving DL packet, one UL Packet Filter derived from the received DL packet as described in this clause is used to identify a UE derived QoS rule within a PDU Session. For PDU Session of IP type, the UL Packet Filter is derived based on the received DL packet as follows: - When Protocol ID / Next Header is set to TCP or UDP, by using the source and destination IP addresses, source and destination port numbers, and the Protocol ID / Next Header field itself. - When Protocol ID / Next Header is set to UDP, if the received DL packet is UDP-encapsulated IPSec protected packet, by using the source and destination IP addresses, source and destination port numbers, the Security Parameter Index, and the Protocol ID / Next Header field itself. In this case, if an uplink IPSec SA corresponding to a downlink IPSec SA of the SPI in the DL packet exists and the SPI of the uplink IPSec SA is known to the NAS layer, then the UL Packet Filter contains an SPI of the uplink IPSec SA. - When Protocol ID / Next Header is set to ESP, by using the source and destination IP addresses, the Security Parameter Index, and the Protocol ID / Next Header field itself. If the received DL packet is an IPSec protected packet, and an uplink IPSec SA corresponding to a downlink IPSec SA of the SPI in the DL packet exists and the SPI of the uplink IPSec SA is known to the NAS layer, then the UL Packet Filter contains an SPI of the uplink IPSec SA. NOTE 1: In this Release of the specification for PDU Sessions of IP type the use of Reflective QoS is restricted to service data flows for which Protocol ID / Next Header is set to TCP, UDP or ESP. NOTE 2: The UE does not verify whether the downlink packets with RQI indication match the restrictions on Reflective QoS. NOTE 3: How to determine the received DL packet is UDP-encapsulated IPSec protected packet is defined in RFC 3948 [138]. UDP encapsulation for ESP is used when a NAT is detected, and there can be different Security Parameter Indexes within the same IP-tuples. NOTE 4: Despite the indication of support for Reflective QoS, the UE might not be able to derive QoS Rules for ESP IPSec packets and UDP-encapsulated IPSec packets, if uplink IPSec SA corresponding to a downlink IPSec SA of the SPI in the DL packet exists and the SPI of the uplink IPSec SA is not known to the NAS layer. For PDU Session of Ethernet type the UL Packet Filter is derived based on the received DL packet by using the source and destination MAC addresses, the Ethertype on received DL packet is used as Ethertype for UL packet. In the case of presence of IEEE Std 802.1Q [98], the VID and PCP in IEEE Std 802.1Q [98] header(s) of the received DL packet is also used as the VID and PCP field for the UL Packet Filter. When double IEEE Std 802.1Q [98] tagging is used, only the outer (S-TAG) is taken into account for the UL Packet Filter derivation. NOTE 5: In this Release of the specification for PDU Sessions of Ethernet type the use of Reflective QoS is restricted to service data flows for which 802.1Q [98] tagging is used. The QFI of the UE derived QoS rule is set to the value received in the DL packet. When Reflective QoS is activated the precedence value for all UE derived QoS rules is set to a standardised value. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.5.2 |
3,324 | 10.5.5.8a P-TMSI signature 2 | The purpose of the P-TMSI signature 2 information element is to identify a GMM context of an MS. The P-TMSI signature 2 is a type 4 information element with 5 octets length. The P-TMSI signature 2 information element is coded as shown in figure 10.5.124a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.141a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.124a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : P-TMSI signature 2 information element Table 10.5.141a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : P-TMSI signature 2 information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.8a |
3,325 | 5.6 Network Assisted Cell Change | Network Assisted Cell Change (NACC) is a means that enables better performance for packet data services upon inter-cell change for those networks that do not support PS Handover. It reduces the service interruption time for UEs in active mode upon cell change by providing in the source cell, prior to the cell change, system information of a target cell allowing packet access. Within the scope of this specification, NACC is applicable for inter-RAT cell changes from a source E-UTRAN cell towards a target GERAN cell. When the UE changes from a source E-UTRAN cell towards a target GERAN cell, the UE locally deactivates ISR by setting its TIN from "RAT-related TMSI" to "GUTI", if any EPS bearer context activated after the ISR was activated in the UE exists. When the UE changes from a source E-UTRAN cell in connected mode towards a target GERAN cell from the same RA via Cell Change Order that is not for CS fallback and the ISR is active, the UE locally deactivates ISR by setting its TIN from "RAT-related TMSI" to "GUTI". | 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.6 |
3,326 | 6.2.5B Configured transmitted power for UL-MIMO | For UE supporting UL-MIMO, the transmitted power is configured per each UE. The definitions of configured maximum output power PCMAX,c, the lower bound PCMAX_L,c, and the higher bound PCMAX_H,c specified in subclause shall apply to UE supporting UL-MIMO, where - PPowerClass, ΔPPowerClass and TC,c are specified in subclause 6.2.2B; - MPR,c is specified in subclause 6.2.3B; - A-MPR,c is specified in subclause 6.2.4B. The measured configured maximum output power PUMAX,c for serving cell c shall be within the following bounds: PCMAX_L,c – MAX{TL, T LOW(PCMAX_L,c)} ≤ PUMAX,c ≤ PCMAX_H,c + T HIGH(PCMAX_H,c) where TLOW(PCMAX_L,c) and THIGH(PCMAX_H,c) are defined as the tolerance and applies to PCMAX_L,c and PCMAX_H,c separately, while TL is the absolute value of the lower tolerance in Table 6.2.2B-1 for the applicable operating band. For UE with two transmit antenna connectors in closed-loop spatial amultiplexing scheme, the tolerance is specified in Table 6.2.5B-1. The requirements shall be met with UL-MIMO configurations specified in Table 6.2.2B-2. Table B-1: PCMAX,c tolerance in closed-loop spatial multiplexing scheme If UE is configured for transmission on single-antenna port, the requirements 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.5B |
3,327 | 6.1.2.1.7 MBMS-ACTIVE | This state indicates that the MBMS context is active. Figure 6.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Session management states for PDP context handling in the MS (overview) It shall be noted, that Figure 6.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] applies to both the PDP context activation procedure and the secondary PDP context activation procedure, though the distinction in messages regarding the activation of PDP contexts is not shown here for simplicity. Figure 6.1a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Session management states for MBMS context handling in the MS (overview) | 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.2.1.7 |
3,328 | 4.4.4 SMF Pause of Charging procedure | The SMF Pause of Charging procedure aims for the SMF charging and usage monitoring data to more accurately reflect the downlink traffic actually sent to the AN. The following are example triggers for the SMF to enable the pause of charging - Operator specified criteria/threshold (e.g. number/fraction of packets/bytes dropped at UPF in downlink since last time the N3 tunnel towards the AN was released). The SMF requests the UPF to notify the SMF whenever the criteria/threshold is met. - Indication of "Radio Link Failure" (see clause 4.2.6). Based on operator policies, if the trigger for the SMF to enable the pause of charging is met, the SMF shall pause the charging. When the SMF pauses charging the following applies: - Towards the UPF(s) where the Usage Reporting is configured, the SMF shall modify the Usage Reporting Rules for the PDU Session so that the usage collection for charging is stopped. - The SMF may request the UPF to limit the rate of downlink traffic sent to the downstream UPF or the AN. NOTE 1: A consequence of using this procedure is that SMF charging data does not correspond to the volume that traversed the UPF and it is therefore not possible to count the downlink packets dropped between the PDU Session Anchor (PSA) UPF and the downstream UPF. NOTE 2: In this release of the specification, pause of charging procedure does not address the issue of packets dropped by the NG-RAN. In home routed roaming scenarios, based on operator's policy, the H-SMF may indicate to the V-SMF if the feature is to be enabled on a per PDU Session basis. This is indicated to the V-SMF by a "PDU Session Charging Pause Enabled" Indication in the Nsmf_PDUSession_Create Response during the PDU Session Establishment procedure. This is an indication to the V-SMF that when the criteria for pause of SMF charging are met at the VPLMN (as described further down in this clause) charging at the H-SMF can be paused. The H-SMF shall stop any charging and usage monitoring actions for the PDU Session upon receiving a "Start Pause of Charging" Indication in a Nsmf_PDUSession_Update request from the V-SMF. When the H-SMF receives a Nsmf_PDUSession_Update request for a PDU Session with a "Stop Pause of Charging" Indication, then the H-SMF shall resume charging for the PDU Session. Regardless of operator policy/configuration, the downlink user plane packets received at the (V-)UPF shall trigger Data Notifications as described in clause 4.2.3.3. When the (V-)SMF receives a Nsmf_PDUSession_UpdateSMContext request or a Namf_EventExposure_Notify about UE reachability, the (V-)SMF shall consider the PDU Session charging as being unpaused if it had been paused previously. Figure 4.4.4-1: SMF Pause of charging procedure 1. The UPF receives downlink data packets for a PDU Session that does not have an N3 tunnel and the UPF sends data notification to the SMF. The packets are buffered or discarded in the UPF based on operator policy. 2. Based on operator policy/configuration the SMF triggers the procedure to pause PDU Session charging. Triggering criteria are based on SMF operator policy/configuration. 3. SMF sends a N4 Session Modification Request message to the UPF where the Usage Reporting is configured, modifying the Usage Reporting Rules for the PDU Session so that the usage collection for charging is stopped. In home routed roaming scenarios, the V-SMF sends a Nsmf_PDUSession_Update request to the H-SMF with a "Start Pause of Charging" Indication. The H-SMF then requests the H-UPF to stop usage collection as mentioned before. 4. UPF confirms with a N4 Session Modification Response message. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.4 |
3,329 | 9.8.2 Security mechanisms for the F1 interface | The F1 interface connects the gNB-CU to the gNB-DU. It consists of the F1-C for control plane and the F1-U for the user plane. The security mechanisms for the F1 interface connecting the IAB-node to the IAB-donor-CU are detailed in clause M.3.3 of this document. In order to protect the traffic on the F1-U interface, IPsec ESP and IKEv2 certificates-based authentication shall be supported as specified in sub-clause 9.1.2 of the present document with confidentiality, integrity and replay protection. In order to protect the traffic on the F1-C interface, IPsec ESP and IKEv2 certificates-based authentication shall be supported as specified in sub-clause 9.1.2 of the present document with confidentiality, integrity and replay protection. IPsec is mandatory to implement on the gNB-DU and on the gNB-CU. On the gNB-CU side, a SEG may be used to terminate the IPsec tunnel. In addition to IPsec, for the F1-C interface, DTLS shall be supported as specified in RFC 6083 [58] to provide mutual authentication, integrity protection, replay protection and confidentiality protection. Security profiles for DTLS implementation and usage shall follow the TLS profile given in clause 6.2 of TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] and the certificate profile given in clause 6.1.3a of TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. The identities in the end entity certificates shall be used for authentication and policy checks.. Mutual authentication shall be supported over the F1-C interface between the gNB-CU and the gNB-DU using DTLS and/or IKEv2. NOTE 1: The use of transport layer security, via DTLS, does not rule out the use of network layer protection according to NDS/IP as specified in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3]. In fact, IPsec has the advantage of providing topology hiding. NOTE 2: The use of cryptographic solutions to protect F1 is an operator's decision. In case the gNB or the IAB-node has been placed in a physically secured environment then the 'secure environment' includes other nodes and links beside the gNB or the IAB-node. NOTE 3: The security considerations for DTLS over SCTP are documented in RFC 6083 [58]. NOTE 4: The support of DTLS (with mutual authentication) for F1-C, between the IAB-node (gNB-DU) and the IAB-donor-CU, is optional for the IAB-node and the IAB-donor-CU. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 9.8.2 |
3,330 | 16.12.3 Relay Discovery | Model A and Model B discovery models as defined in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48] are supported for U2N/U2U Relay discovery. The protocol stack used for discovery is illustrated in Figure 16.12.3-1. Figure 16.12.3-1: Protocol Stack of Discovery Message for UE-to-Network/UE-to-UE Relay The U2N Remote UE can perform Relay discovery message (i.e., as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]) transmission and may monitor the sidelink for Relay discovery message while in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED. The network may broadcast or configure via dedicated RRC signalling a Uu RSRP threshold, which is used by the U2N Remote UE to determine if it can transmit Relay discovery messages to U2N Relay UE(s). The U2N Relay UE can perform Relay discovery message (i.e., as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]) transmission and may monitor the sidelink for Relay discovery message while in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED. The network may broadcast or configure via dedicated RRC signalling a maximum Uu RSRP threshold, a minimum Uu RSRP threshold, or both, which are used by the U2N Relay UE to determine if it can transmit Relay discovery messages to U2N Remote UE(s). The U2U Remote UE and U2U Relay UE can perform Relay discovery message transmission or DCR message with integrated discovery transmission and may monitor for Relay discovery message or DCR message with integrated discovery while in coverage (i.e. RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED) or out-of-coverage. The network may provide the Relay discovery configuration using broadcast or dedicated signalling. In addition, the U2N/U2U Remote UE and L3 U2N/U2U Relay UE may use pre-configuration for Relay discovery. The resource pool(s) used for NR sidelink communication can be used for Relay discovery or the network may configure resource pool(s) dedicated for Relay discovery. Resource pool(s) dedicated for Relay discovery can be configured simultaneously with resource pool(s) for NR sidelink communication in system information, dedicated signalling and/or pre-configuration. Whether dedicated resource pool(s) for Relay discovery are configured is based on network implementation. If resource pool(s) dedicated for Relay discovery are configured, only those resource pool(s) dedicated for Relay discovery shall be used for Relay discovery. If only resource pool(s) for NR sidelink communication are configured, all the configured resource pool(s) can be used for Relay discovery and NR sidelink communication. Only communication resource pool is used for the DCR/DCA message with integrated discovery. For U2N Remote UE (including both in-coverage and out of coverage cases) that has been connected to the network via a U2N Relay UE, only resource allocation mode 2 is used for Relay discovery message transmission. For in-coverage U2N Relay UE, and for both in-coverage and out of coverage U2N Remote UEs, NR sidelink resource allocation principles are applied for Relay discovery message transmission. For U2U Remote UE and U2U Relay UE, NR sidelink resource allocation principles, both mode 1 and mode 2, can be applied for Relay discovery message transmission. The sidelink power control for the transmission of Relay discovery messages is same as for NR sidelink communication. No ciphering or integrity protection in PDCP layer is applied for the Relay discovery messages. The U2N/U2U Remote UE and U2N/U2U Relay UE can determine from SIB12 whether the gNB supports Relay discovery, or Non-Relay discovery, or both. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.3 |
3,331 | 5.3.5.9 Other configuration | The UE shall: 1> if the received otherConfig includes the delayBudgetReportingConfig: 2> if delayBudgetReportingConfig is set to setup: 3> consider itself to be configured to send delay budget reports in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to send delay budget reports and stop timer T342, if running. 1> if the received otherConfig includes the overheatingAssistanceConfig: 2> if overheatingAssistanceConfig is set to setup: 3> consider itself to be configured to provide overheating assistance information in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide overheating assistance information and stop timer T345, if running; 1> if the received otherConfig includes the idc-AssistanceConfig: 2> if idc-AssistanceConfig is set to setup: 3> consider itself to be configured to provide IDC assistance information in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide IDC assistance information; 1> if the received otherConfig includes the drx-PreferenceConfig: 2> if drx-PreferenceConfig is set to setup: 3> consider itself to be configured to provide its preference on DRX parameters for power saving for the cell group in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide its preference on DRX parameters for power saving for the cell group and stop timer T346a associated with the cell group, if running; 1> if the received otherConfig includes the maxBW-PreferenceConfig: 2> if maxBW-PreferenceConfig is set to setup: 3> consider itself to be configured to provide its preference on the maximum aggregated bandwidth for power saving for the cell group in accordance with 5.7.4; 3> if otherConfig includes maxBW-PreferenceConfigFR2-2: 4> consider itself to be configured to provide its preference on the maximum aggregated bandwidth for FR2-2 for power saving for the cell group in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide its preference on the maximum aggregated bandwidth for power saving for the cell group and stop timer T346b associated with the cell group, if running; 1> if the received otherConfig includes the maxCC-PreferenceConfig: 2> if maxCC-PreferenceConfig is set to setup: 3> consider itself to be configured to provide its preference on the maximum number of secondary component carriers for power saving for the cell group in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide its preference on the maximum number of secondary component carriers for power saving for the cell group and stop timer T346c associated with the cell group, if running; 1> if the received otherConfig includes the maxMIMO-LayerPreferenceConfig: 2> if maxMIMO-LayerPreferenceConfig is set to setup: 3> consider itself to be configured to provide its preference on the maximum number of MIMO layers for power saving for the cell group in accordance with 5.7.4; 3> if otherConfig includes maxMIMO-LayerPreferenceConfigFR2-2: 4> consider itself to be configured to provide its preference on the maximum number of MIMO layers for FR2-2 for power saving for the cell group in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide its preference on the maximum number of MIMO layers for power saving for the cell group and stop timer T346d associated with the cell group, if running; 1> if the received otherConfig includes the minSchedulingOffsetPreferenceConfig: 2> if minSchedulingOffsetPreferenceConfig is set to setup: 3> consider itself to be configured to provide its preference on the minimum scheduling offset for cross-slot scheduling for power saving for the cell group in accordance with 5.7.4; 3> if otherConfig includes minSchedulingOffsetPreferenceConfigExt: 4> consider itself to be configured to provide its preference on the minimum scheduling offset for 480 kHz SCS and/or 960 kHz SCS for cross-slot scheduling for power saving for the cell group in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide its preference on the minimum scheduling offset for cross-slot scheduling for power saving for the cell group and stop timer T346e associated with the cell group, if running; 1> if the received otherConfig includes the releasePreferenceConfig: 2> if releasePreferenceConfig is set to setup: 3> consider itself to be configured to provide assistance information to transition out of RRC_CONNECTED in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide assistance information to transition out of RRC_CONNECTED and stop timer T346f, if running. 1> if the received otherConfig includes the obtainCommonLocation: 2> include available detailed location information for any subsequent measurement report or any subsequent RLF report, SCGFailureInformation and successful handover report; NOTE 1: The UE is requested to attempt to have valid detailed location information available whenever sending a measurement report for which it is configured to include available detailed location information. The UE may not succeed e.g. because the user manually disabled the GPS hardware, due to no/poor satellite coverage. Further details, e.g. regarding when to activate GNSS, are up to UE implementation. 1> if the received otherConfig includes the btNameList: 2> if btNameList is set to setup, include available Bluetooth measurement results for any subsequent measurement report or any subsequent RLF report and SCGFailureInformation; 1> if the received otherConfig includes the wlanNameList: 2> if wlanNameList is set to setup, include available WLAN measurement results for any subsequent measurement report or any subsequent RLF report and SCGFailureInformation; 1> if the received otherConfig includes the sensorNameList: 2> if sensorNameList is set to setup, include available Sensor measurement results for any subsequent measurement report or any subsequent RLF report and SCGFailureInformation; NOTE 2: The UE is requested to attempt to have valid Bluetooth measurements, WLAN measurements and Sensor measurements whenever sending a measurement report for which it is configured to include these measurements. The UE may not succeed e.g. because the user manually disabled the WLAN or Bluetooth or Sensor hardware. Further details, e.g. regarding when to activate WLAN or Bluetooth or Sensor, are up to UE implementation. 1> if the received otherConfig includes the sl-AssistanceConfigNR: 2> consider itself to be configured to provide configured grant assistance information for NR sidelink communication in accordance with 5.7.4; 1> if the received otherConfig includes the referenceTimePreferenceReporting: 2> consider itself to be configured to provide UE reference time assistance information in accordance with 5.7.4; 1> else: 2> consider itself not to be configured to provide UE reference time assistance information; 1> if the received otherConfig includes the successHO-Config: 2> consider itself to be configured to provide the successful handover information in accordance with 5.7.10.6; 1> else: 2> consider itself not to be configured to provide the successful handover information. 1> if the received otherConfig includes the successPSCell-Config: 2> if thresholdPercentageT304-SCG is included: 3> consider itself to be configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7; 2> else if sn-InitiatedPSCellChange is included: 3> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7; 2> else: 3> consider itself to be configured by the PCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7; 1> else: 2> consider itself not to be configured to provide the successful PSCell change or addition information. 1> if the received otherConfig includes the ul-GapFR2-PreferenceConfig: 2> consider itself to be configured to provide its preference on FR2 UL gap in accordance with 5.7.4; 1> else: 2> consider itself not to be configured to provide its preference on FR2 UL gap; 1> if the received otherConfig includes the musim-GapAssistanceConfig: 2> if musim-GapAssistanceConfig is set to setup: 3> consider itself to be configured to provide MUSIM assistance information for gap preference in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide MUSIM assistance information for gap preference and stop timer T346h, if running; 1> if the received otherConfig includes the musim-LeaveAssistanceConfig: 2> if musim-LeaveAssistanceConfig is set to setup: 3> consider itself to be configured to provide MUSIM assistance information for leaving RRC_CONNECTED in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide MUSIM assistance information for leaving RRC_CONNECTED and stop timer T346g, if running. 1> if the received otherConfig includes the musim-GapPriorityAssistanceConfig: 2> consider itself to be configured to provide MUSIM assistance information for gap(s) priority in accordance with 5.7.4; 1> else: 2> consider itself not to be configured to provide MUSIM assistance information for gap(s) priority; 1> if the received otherConfig includes the musim-CapabilityRestrictionConfig: 2> if musim-CapabilityRestrictionConfig is set to setup: 3> consider itself to be configured to provide MUSIM assistance information for capability restriction in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide MUSIM assistance information for capability restriction and stop timer T348 and T346n, if running; 1> if the received otherConfig includes the rlm-RelaxationReportingConfig: 2> if rlm-RelaxationReportingConfig is set to setup: 3> consider itself to be configured to report the relaxation state of RLM measurements in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to report the relaxation state of RLM measurements and stop timer T346j associated with the cell group, if running; 1> if the received otherConfig includes the bfd-RelaxationReportingConfig: 2> if bfd-RelaxationReportingConfig is set to setup: 3> consider itself to be configured to report the relaxation state of BFD measurements in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to report the relaxation state of BFD measurements and stop timer T346k associated with the cell group, if running; 1> if the received otherConfig includes the scg-DeactivationPreferenceConfig: 2> if the scg-DeactivationPreferenceConfig is set to setup: 3> consider itself to be configured to provide its SCG deactivation preference in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide its SCG deactivation preference and stop timer T346i, if running. 1> if the received otherConfig includes the propDelayDiffReportConfig: 2> if the propDelayDiffReportConfig is set to setup: 3> consider itself to be configured to provide service link propagation delay difference between serving cell and neighbour cell(s) in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide service link propagation delay difference between serving cell and neighbour cell(s). 1> if the received otherConfig includes the rrm-MeasRelaxationReportingConfig: 2> if the rrm-MeasRelaxationReportingConfig is set to setup: 3> consider itself to be configured to report the fulfilment of the criterion for relaxing RRM measurements in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to report the fulfilment of the criterion for relaxing RRM measurements. 1> if the received otherConfig includes the multiRx-PreferenceReportingConfigFR2: 2> if the multiRx-PreferenceReportingConfigFR2 is set to setup: 3> consider itself to be configured to provide its preference on multi-Rx operation for FR2 in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide its preference on multi-Rx operation for FR2 and stop timer T346m, if running. 1> if the received otherConfig includes the uav-FlightPathAvailabilityConfig: 2> consider itself to be configured to indicate the availability of flight path information in accordance with 5.7.4; 1> if the received otherConfig includes the ul-TrafficInfoReportingConfig: 2> if ul-TrafficInfoReportingConfig is set to setup: 3> consider itself to be configured to provide UL traffic information in accordance with 5.7.4; 2> else: 3> consider itself not to be configured to provide UL traffic information and stop all instances of timer T346x, if running. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.9 |
3,332 | 6.2.18 Network Data Analytics Function (NWDAF) | The Network Data Analytics Function (NWDAF) includes one or more of the following functionalities: - Support data collection from NFs and AFs; - Support data collection from OAM; - Support retrieval of information from data repositories (e.g. UDR via UDM for subscriber-related information or via NEF(PFDF) for PFD information); - Support data collection of location information from LCS system; - NWDAF service registration and metadata exposure to NFs and AFs; - Support analytics information provisioning to NFs and AFs; - Support Machine Learning (ML) model training and provisioning to NWDAFs (containing Analytics logical function); - Support bulked data related to Analytics ID(s) provisioning for NFs; - Support accuracy information about Analytics IDs provisioning for NFs; - Support accuracy information or accuracy degradation about ML model provisioning for NFs; - Support roaming exchange capability to exchange data and analytics between PLMNs; - Support Federated Learning (FL) to train an ML model among multiple NWDAFs (containing MTLF). The details of the NWDAF functionality are defined in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. NOTE 1: Some or all of the NWDAF functionalities can be supported in a single instance of an NWDAF. NOTE 2: NWDAF functionality beyond its support for Nnwdaf is out of scope of 3GPP. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.18 |
3,333 | 4.13.6.2 Inter RAT Fallback in 5GC for IMS voice | Figure 4.13.6.2-1 describes the RAT fallback procedure in 5GC for IMS voice. When the UE is served by the 5GC, the UE has one or more ongoing PDU Sessions each including one or more QoS Flows. The serving PLMN AMF has sent an indication towards the UE during the Registration procedure that IMS voice over PS session is supported, see clause 5.16.3.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the UE has registered in the IMS. Figure 4.13.6.2-1: RAT Fallback for IMS voice 1. UE camps on source NG-RAN in the 5GS and an MO or MT IMS voice session establishment has been initiated. 2. Network initiated PDU Session modification to setup QoS flow for IMS voice reaches the source NG-RAN (see N2 PDU Session Request in clause 4.3.3). 3. If source NG-RAN is configured to support RAT fallback for IMS voice, source NG-RAN decides to trigger RAT fallback, taking into account on UE capabilities, network configuration and radio conditions. Source NG-RAN may initiate measurement report solicitation from the UE including target NG-RAN. 4. Source NG-RAN responds indicating rejection of the PDU Session modification to setup QoS flow for IMS voice received in step 2 by PDU Session Response message towards the SMF (or V-SMF, in the case of roaming scenario) via AMF with an indication that mobility due to fallback for IMS voice is ongoing. The SMF maintains the PCC rule(s) associated with the QoS Flow(s). 5. Source NG-RAN initiates Xn based Inter NG-RAN handover (see clause 4.9.1.2) or N2 based inter NG-RAN handover (see clause 4.9.1.3), or redirection to E-UTRA connected to 5GC (see clause 4.2.6). The SMF reports change of the RAT type if subscribed by PCF. 6. After completion of the Inter NG-RAN (inter-RAT) handover or redirection to E-UTRA connected to 5GC, the SMF re-initiates the PDU Session modification to setup QoS flow for IMS voice. The SMF reports about Successful Resource Allocation and Access Network Information if subscribed by PCF. The IMS signalling related to IMS voice call establishment continues after step 1 as specified in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [55]. At least for the duration of the IMS voice call the target NG-RAN is configured to not trigger inter NG-RAN handover back to source NG-RAN. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.6.2 |
3,334 | 12.3.9.3.2 Based on procedures | Message prioritization may be performed based on the relative priority of the procedure for which the message is being sent. Procedures are grouped into various categories and each of these categories is assigned a priority. Additionally, within a given category of procedures, messages may be further prioritized based on session parameters such as: APN, QCI, ARP and/or LAPI (as described in clause 12.3.9.3.3). Subsequently, messages with a high priority shall be given lower preference to throttle and messages with low priority shall be given higher preference to throttle. The grouping of the procedures is not performed based on an individual GTP-C entity but whilst considering all the procedures in general. A GTP-C entity should consider the procedures applicable to it and apply prioritized message throttling based on the category of the procedure, as described below. The categories are listed in decreasing order of priority with category 1 having the highest priority. For each category a non-exhaustive list of messages is provided. Any existing or newly defined message in future should be considered based on the category (as specified below) of the procedure for which the message is sent. 1. UE session mobility within and across 3GPP or non-3GPP access: Procedures involving active or idle mode UE mobility, such that GTP-C signalling is involved, shall be classified under this category. Some examples are X2/S1 based handover with/without an SGW change, TAU/RAU with a change of MME/SGSN with/without an SGW change, 3GPP access to trusted non-3GPP access handover, etc. Throttling of these messages, during the procedures related to UE session mobility, would result in the failure of the corresponding procedures. This could result potentially in the loss of the PDN connection and/or the interruption of the services. Hence, the messages, as identified below, when sent during the procedures belonging to this category, shall be considered with the highest priority and hence, shall be given the lowest preference to throttle. - Create Session Request, - Create Session Request with "handover" indication bit set, - Modify Bearer Request, - Modify Bearer Request with "handover" indication bit set, - Modify Access Bearer Request. 2. Release of PDN connection or bearer resources: Procedures resulting in the deactivation of an existing PDN connection, the deactivation of bearer(s) or of data forwarding tunnel of an UE leads to freeing up of the resources at the overloaded node and hence, can potentially ease the overload situation, since the freed up resources can be used for serving the remaining of the UEs. Thus, the messages belonging to this category resulting in the deactivation of PDN connection or bearer(s) or data forwarding tunnel(s), as identified below, shall be treated with the next lower level of priority and hence shall be given the corresponding preference whilst throttling: - Delete Session Request, - Delete Bearer Request, - Delete Bearer Command, - Delete Indirect Data Forwarding Tunnel Request. 3. Miscellaneous session management procedures: This category shall consist of the session management procedures, except PDN connection creation and bearer creation/modification procedures. Some examples are location reporting, when it is not combined with other mobility procedures, Service request and S1 release procedure. These procedures do not severely impact the on-going service of the UE. Hence, the messages, as identified below, when sent during the procedures identified under this category, shall be treated with the next lower level of priority and hence, shall be given the corresponding preference whilst throttling: - Release Access Bearer Request, - Modify Bearer Request, - Change Notification, - Suspend Notification, - Resume Notification. 4. Request for new PDN Connection or bearer resources: Procedures requesting the creation of PDN connection, creation or modification of bearer(s) or creation of data forwarding tunnel shall be classified in this category. Throttling of the messages belonging to this category would result in denial of new services while continuing with the existing services. However, this is the natural outcome of an overload condition, i.e. the overloaded node, due to lack of resources, is not able to provision new services while the trying to maintain the existing services and hence, the messages, as identified below, when sent during the procedures belonging to this category, shall be considered with the lowest level of priority and hence shall be given highest preference to throttle: - Create Session Request during PDN connection request, - Create Bearer Request, - Update Bearer Request, - Bearer Resource Command, - Modify Bearer Command, - Create Indirect Data Forwarding Tunnel Request. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.3.9.3.2 |
3,335 | 5.4.1.2.4.5 Abnormal cases in the UE | The following abnormal cases can be identified: a) Authentication failure (5GMM cause #71 "ngKSI already in use"). The UE shall send an AUTHENTICATION FAILURE message, with 5GMM cause #71 "ngKSI already in use", to the network and start the timer T3520 (see example in figure 5.4.1.3.7.1). Furthermore, the UE shall stop any of the retransmission timers that are running (e.g. T3510, T3517 or T3521). Upon the first receipt of an AUTHENTICATION FAILURE message from the UE with 5GMM cause #71 "ngKSI already in use", the network performs necessary actions to select a new ngKSI and send the same EAP-request message to the UE. NOTE 1: Upon receipt of an AUTHENTICATION FAILURE message from the UE with 5GMM cause #71 "ngKSI already in use", the network can also re-initiate the EAP based primary authentication and key agreement procedure (see subclause 5.4.1.2.2.2). Upon receiving a new AUTHENTICATION REQUEST message with the EAP message IE containing an EAP-request message from the network, the UE shall stop timer T3520, if running, process the EAP-request message as normal. If the network is validated successfully (an AUTHENTICATION REQUEST message that contains a valid ngKSI and EAP-request message is received), the UE shall send the AUTHENTICATION RESPONSE message to the network and shall start any retransmission timers (e.g. T3510, T3517 or T3521) if they were running and stopped when the UE received the first failed AUTHENTICATION REQUEST message. b) Transmission failure of AUTHENTICATION RESPONSE message or AUTHENTICATION FAILURE message indication from lower layers (if the EAP based primary authentication and key agreement procedure is triggered by a registration procedure). The UE shall stop the timer T3520, if running, and re-initiate the registration procedure. c) Transmission failure of AUTHENTICATION RESPONSE message or AUTHENTICATION FAILURE message indication with change in the current TAI (if the EAP based primary authentication and key agreement procedure is triggered by a service request procedure). The UE shall stop the timer T3520, if running. If the current TAI is not in the TAI list, the EAP based primary authentication and key agreement procedure shall be aborted and a registration procedure for mobility and periodic registration update shall be initiated. If the current TAI is still part of the TAI list, it is up to the UE implementation how to re-run the ongoing procedure that triggered the EAP based primary authentication and key agreement procedure. d) Transmission failure of AUTHENTICATION RESPONSE message or AUTHENTICATION FAILURE message indication without change in the current TAI (if the authentication procedure is triggered by a service request procedure). The UE shall stop the timer T3520, if running. It is up to the UE implementation how to re-run the ongoing procedure that triggered the EAP based primary authentication and key agreement procedure. e) Network failing the authentication check. If the UE deems that the network has failed the authentication check, then it shall request RRC to locally release the RRC connection and treat the active cell as barred (see 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]). The UE shall start any retransmission timers (e.g. T3510, T3517 or T3521), if they were running and stopped when the UE received the first AUTHENTICATION REQUEST message containing an ngKSI that was already in use. f) Change in the current TAI. If that the current TAI is not in the TAI list before the AUTHENTICATION RESPONSE message is sent, the UE may discard sending the AUTHENTICATION RESPONSE message to the network and continue with the initiation of the registration procedure for mobility and periodic registration update as described in subclause 5.5.1.3.2. For item e, if no emergency service is started or is ongoing: The UE shall stop timer T3520, if the timer is running and the UE enters 5GMM-IDLE mode, e.g. upon detection of a lower layer failure, release of the N1 NAS signalling connection, or as the result of an inter-system change in 5GMM-CONNECTED mode from N1 mode to S1 mode. The UE shall deem that the network has failed the authentication check or assume that the authentication is not genuine and proceed as described in item e above if any of the following occurs: - the timer T3520 expires; - the UE detects any combination of the EAP-based authentication failures: transmission of AUTHENTICATION FAILURE message with 5GMM cause #71 "ngKSI already in use", transmission of AUTHENTICATION RESPONSE message with an EAP-response message after detecting an error as described in subclause 5.4.1.2.2.4, with an EAP-response message after not accepting of the server certificate as described in subclause 5.4.1.2.3.1 or with an EAP-response message after failing to authenticate the network as described in subclause 5.4.1.2.3A.1, during three consecutive authentication challenges. The EAP-request/AKA'-challenge challenges shall be considered as consecutive only, if the EAP-request/AKA'-challenge challenges causing the second and third EAP-based authentication failure are received by the UE, while the timer T3520 started after the previous EAP-based authentication failure is running. Not accepting of the server certificate shall be considered as consecutive only, if the EAP-request messages causing the second and third not accepting of the server certificate are received by the UE, while the timer T3520 started after the previous EAP request message causing the previous not accepting of the server certificate is running. NOTE 2: Reception of an EAP-failure message is not considered when determining the three consecutive authentication challenges or three consecutive not accepting of the server certificate. For item e if there is an emergency service started or is ongoin: The UE shall stop timer T3520, if the timer is running and the UE enters 5GMM-IDLE mode, e.g. upon detection of a lower layer failure, release of the N1 NAS signalling connection, or as the result of an inter-system change in 5GMM-CONNECTED mode from N1 mode to S1 mode. If a UE has an emergency PDU session established or is establishing an emergency PDU session, and sends an AUTHENTICATION FAILURE message to the AMF with the 5GMM cause appropriate for this cases (i.e. #71) or an AUTHENTICATION RESPONSE message containing an EAP-response message as described in subclause 5.4.1.2.2.4, containing an EAP-response message after not accepting of the server certificate as described in subclause 5.4.1.2.3.1 or containing an EAP-response message after failing to authenticate the network as described in subclause 5.4.1.2.3A.1, and receives the SECURITY MODE COMMAND message before the timeout of timer T3520, the UE shall deem that the network has passed the authentication check successfully, stop timer T3520, respectively, and execute the security mode control procedure. If a UE has an emergency PDU session established or is establishing an emergency PDU session when timer T3520 expires, the UE shall not deem that the network has failed the authentication check and not behave as described in item e. Instead the UE shall continue using the current security context, if any, release all non-emergency PDU sessions, if any, by initiating UE-requested PDU session release procedure. If there is an ongoing PDU session establishment procedure, the UE shall release all non-emergency PDU sessions upon completion of the PDU session establishment procedure. The UE shall start any retransmission timers (e.g. T3510, T3517 or T3521) if: - they were running and stopped when the UE received the AUTHENTICATION REQUEST message and detected an authentication failure; and - the procedures associated with these timers have not yet been completed. The UE shall consider itself to be registered for emergency services. | 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.1.2.4.5 |
3,336 | 12.2 CN Domain Identifier | A CN Domain Edge Node is identified within the UTRAN by its CN Domain Identifier. The CN Domain identifier is used over UTRAN interfaces to identify a particular CN Domain Edge Node for relocation purposes. The CN Domain identifier for Circuit Switching (CS) consists of the PLMN-Id and the LAC, whereas for Packet Switching (PS) it consists of the PLMN-Id, the LAC, and the RAC of the first accessed cell in the target RNS. The two following CN Domain Identifiers are defined: - CN CS Domain-Id = PLMN-Id || LAC - CN PS Domain-Id = PLMN-Id || LAC || RAC The LAC and RAC are defined by the operator, and set in the RNC via O&M. For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [17]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 12.2 |
3,337 | – ULInformationTransferMRDC | The ULInformationTransferMRDC message is used for the uplink transfer of MR-DC dedicated information (e.g. for transferring the NR or E-UTRA RRC MeasurementReport message, the FailureInformation message, the UEAssistanceInformation message, the RRCReconfigurationComplete message, the IABOtherInformation message or the NR or E-UTRA RRC MCGFailureInformation message). Signalling radio bearer: SRB1, SRB3 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network ULInformationTransferMRDC message -- ASN1START -- TAG-ULINFORMATIONTRANSFERMRDC-START ULInformationTransferMRDC ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { ulInformationTransferMRDC ULInformationTransferMRDC-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } ULInformationTransferMRDC-IEs::= SEQUENCE { ul-DCCH-MessageNR OCTET STRING OPTIONAL, ul-DCCH-MessageEUTRA OCTET STRING OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-ULINFORMATIONTRANSFERMRDC-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,338 | 4.18 5GS session management in NB-N1 mode | A UE in NB-N1 mode (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]) shall calculate the value of the applicable NAS timer indicated in table 10.3.1 plus 180s. The timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not re-calculate the use of the NAS timer value until the NAS procedure is completed, restarted or aborted. When an SMF that supports NB-N1 mode performs NAS signalling with a UE, which is using NB-N1 mode, the SMF shall calculate the value of the applicable NAS timer indicated in table 10.3.2 plus 180s. The timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not re-calculate the use of the NAS timer value until the NAS procedure is completed, restarted or aborted. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.18 |
3,339 | 9.11.3.29 LADN indication | The purpose of the LADN indication information element is to request the network for LADN information for specific LADN DNN(s) or to indicate a request for LADN information. The LADN indication information element is coded as shown in figure 9.11.3.29.1 and table 9.11.3.29.1. The LADN indication is a type 6 information element with a minimum length of 3 octets and a maximum length of 811 octets. The LADN indication information element can contain a minimum of 0 and a maximum of 8 different LADN DNN values. Figure 9.11.3.29.1: LADN indication information element Table 9.11.3.29.1: LADN 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.29 |
3,340 | V.3 User consent check | Any NF that is deemed an enforcement point for user consent shall support to retrieve the user consent parameters from the UDM. Any NF that is deemed an enforcement point for user consent shall not accept any services or requests for data processing unless user consent is granted. Any NF that is deemed an enforcement point for user consent shall determine the purpose of data processing prior to the data processing. If the purpose of data processing is not implicitly known from the service request, the user consent enforcement point shall request it or otherwise deny the service. NFs obtaining or checking the user consent parameters shall consider the user consent parameters as effective until revoked. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | V.3 |
3,341 | 5.32.6.2.1 MPTCP Functionality | As mentioned in clause 5.32.6.1, the MPTCP functionality in the UE applies the MPTCP protocol (IETF RFC 8684 [81]) and the provisioned ATSSS rules for performing access traffic steering, switching and splitting. The MPTCP functionality in the UE may communicate with the MPTCP Proxy functionality in the UPF using the user plane of the 3GPP access, or the non-3GPP access, or both. The MPTCP functionality may be enabled in the UE when the UE provides an "MPTCP capability" during PDU Session Establishment procedure. The network shall not enable the MPTCP functionality when the type of the MA PDU Session is Ethernet. If the UE indicates it is capable of supporting the MPTCP functionality, as described in clause 5.32.2, and the network agrees to enable the MPTCP functionality for the MA PDU Session then: i) An associated MPTCP Proxy functionality is enabled in the UPF for the MA PDU Session by MPTCP functionality indication received in the Multi-Access Rules (MAR). ii) The network allocates to UE one IP address/prefix for the MA PDU Session and two additional IP addresses/prefixes, called "MPTCP link-specific multipath" addresses/prefixes; one associated with 3GPP access and another associated with the non-3GPP access. In the UE, these two IP addresses/prefixes are used only by the MPTCP functionality. Each "MPTCP link-specific multipath" address/prefix assigned to UE may not be routable via N6. The MPTCP functionality in the UE and the MPTCP Proxy functionality in the UPF shall use the "MPTCP link-specific multipath" addresses/prefixes for subflows over non-3GPP access and over 3GPP access and MPTCP Proxy functionality shall use the IP address/prefix of the MA PDU session for the communication with the final destination. In Figure 5.32.6.1-1, the IP@3 corresponds to the IP address of the MA PDU Session and the IP@1 and IP@2 correspond to the "MPTCP link-specific multipath" IP addresses. The following UE IP address management applies: - The MA PDU IP address/prefix shall be provided to the UE via mechanisms defined in clause 5.8.2.2. - The "MPTCP link-specific multipath" IP addresses/prefixes shall be allocated by the UPF and shall be provided to the UE via SM NAS signalling. NOTE 1: After the MA PDU Session is released, the same UE IP addresses/prefixes are not allocated to another UE for MA PDU Session in a short time. NOTE 2: The act of the UPF performing translation on traffic associated with the "MPTCP link-specific multipath" addresses to/from the MA PDU session IP address can lead to TCP port collision and exhaustion. The port collision can potentially occur because the UE also uses the MA PDU session IP address for non-MPTCP traffic, and this causes the port namespace of such address to be owned simultaneously by the UE and UPF. In addition, the port exhaustion can potentially occur when the UE creates a large number of flows, because multiple IP addresses used by the UE are mapped to a single MA PDU session IP address on the UPF. The UPF needs to consider these problems based on the UPF implementation, and avoid them by, for example, using additional N6-routable IP addresses for traffic associated to the link-specific multipath addresses/prefixes. How this is done is left to the implementation. iii) The network shall send MPTCP proxy information to UE, i.e. the IP address, a port number and the type of the MPTCP proxy. The following type of MPTCP proxy shall be supported in this release: - Type 1: Transport Converter, as defined in IETF RFC 8803 [82]. The MPTCP proxy information is retrieved by the SMF from the UPF during N4 session establishment. The UE shall support the client extensions specified in IETF RFC 8803 [82]. iv) The network may indicate to UE the list of applications for which the MPTCP functionality should be applied. This is achieved by using the Steering Functionality component of an ATSSS rule (see clause 5.32.8). NOTE 3: To protect the MPTCP proxy function (e.g. to block DDOS to the MPTCP proxy function), the IP addresses of the MPTCP Proxy Function are only accessible from the two "MPTCP link-specific multipath" IP addresses of the UE via the N3/N9 interface. v) When the UE indicates it is capable of supporting the MPTCP functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1) and these functionalities are enabled for the MA PDU Session, then the UE shall route via the MA PDU Session the TCP traffic of applications for which the MPTCP functionality should be applied (i.e. the MPTCP traffic), as defined in bullet iv. The UE may route all other traffic (i.e. the non-MPTCP traffic) via the MA PDU Session, but this type of traffic shall be routed on one of 3GPP access or non-3GPP access, based on the received ATSSS rule for non-MPTCP traffic (see clause 5.32.2). The UPF shall route all other traffic (i.e. non-MPTCP traffic) based on the N4 rules provided by the SMF. This may include N4 rules for ATSSS-LL, using any steering mode as instructed by the N4 rules. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.6.2.1 |
3,342 | 9.3.8.3.2 TDD | For the parameters specified in Table 9.3.8.3.2-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in Table 9.3.8.3.2-2 and by the following a) the ratio of the throughput obtained obtained for the Type B receiver with NAICS assistance information when transmitting the transport format indicated by each reported wideband CQI index subject to interference sources with specified and that obtained for the Type B receiver without NAICS assistance information when transmitting the transport format indicated by each reported wideband CQI index subject to interference sources with the same specified shall be ≥ ; Table 9.3.8.3.2-1 Fading test for single antenna (TDD) Table 9.3.8.3.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.8.3.2 |
3,343 | 11 Identification of Localised Service Area | Cells may be grouped into specific localised service areas. Each localised service area is identified by a localised service area identity (LSA ID). No restrictions are placed on what cells may be grouped into a given localised service area. The LSA ID can either be a PLMN significant number or a universal identity. This shall be known both in the networks and in the SIM. The LSA ID consists of 24 bits, numbered from 0 to 23, with bit 0 being the LSB. Bit 0 indicates whether the LSA is a PLMN significant number or a universal LSA. If the bit is set to 0 the LSA is a PLMN significant number; if it is set to 1 it is a universal LSA. The LSA ID shall be composed as shown in figure 19: Figure 19: Structure of LSA ID | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 11 |
3,344 | 4.11.3a.1 Handover from EPS to 5GC-TNGF | The handover procedure from EPS to 5GC-TNGF is supported as specified in clause 4.11.3.1 for handover procedure from EPS to 5GC-N3IWF with the following differences: - The untrusted non-3GPP access is substituted by trusted non-3GPP access point (TNAP). - The N3IWF is substituted by TNGF. - The registration procedure via trusted non-3GPP access as specified in clause 4.12a.2 shall be performed in step 1. - The UE requested PDU Session Establishment with Existing PDU Session indication in 5GC via trusted non-3GPP access is performed in step 2 as specified clause 4.12a.5. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.3a.1 |
3,345 | 5.3.11 UE actions upon going to RRC_IDLE | The UE shall: 1> reset MAC; 1> if the UE is NCR-MT: 2> indicate to NCR-Fwd to cease forwarding; 1> set the variable pendingRNA-Update to false, if that is set to true; 1> if going to RRC_IDLE was triggered by reception of the RRCRelease message including a waitTime: 2> if T302 is running: 3> stop timer T302; 2> start timer T302 with the value set to the waitTime; 2> inform upper layers that access barring is applicable for all access categories except categories '0' and '2'. 1> else: 2> if T302 is running: 3> stop timer T302; 3> perform the actions as specified in 5.3.14.4; 1> if T390 is running: 2> stop timer T390 for all access categories; 2> perform the actions as specified in 5.3.14.4; 1> if the UE is leaving RRC_INACTIVE: 2> if going to RRC_IDLE was not triggered by reception of the RRCRelease message: 3> if stored, discard the cell reselection priority information provided by the cellReselectionPriorities; 3> stop the timer T320, if running; 2> if T319a is running: 3> stop timer T319a; 3> consider SDT procedure is not ongoing; 1> stop all timers that are running except T302, T320, T325, T330, T331, T400 and T430; 1> discard the UE Inactive AS context, if any; 1> release the suspendConfig, if configured; 1> release the uav-Config, if configured; 1> perform LTM configuration release procedure for the MCG and SCG as specified in clause 5.3.5.18.7; 1> remove all the entries within the MCG and the SCG VarConditionalReconfig, if any; 1> remove the servingSecurityCellSetId within the VarServingSecurityCellSetID, if any; 1> for each measId, if the associated reportConfig has a reportType set to condTriggerConfig: 2> for the associated reportConfigId: 3> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig; 2> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig: 3> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig; 2> remove the entry with the matching measId from the measIdList within the VarMeasConfig; 1> discard the KgNB key, the S-KgNB key, the S-KeNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key, if any; 1> release all radio resources, including release of the RLC entity, the BAP entity, the MAC configuration and the associated PDCP entity and SDAP for all established RBs (except for broadcast MRBs), BH RLC channels, Uu Relay RLC channels, PC5 Relay RLC channels and SRAP entity; NOTE 0: A L2 U2N Relay UE may re-establish the SL-RLC0, SL-RLC1 and SRAP entity after release. 1> indicate the release of the RRC connection to upper layers together with the release cause; 1> for each application layer measurement configuration for which configForRRC-IdleInactive is not set to true: 2> inform upper layers about the release of all application layer measurement configurations; 2> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; 1> for each application layer measurement configuration for which configForRRC-IdleInactive is set to true: 2> initiate the procedure in 5.5b.1.2; 1> discard any segments of segmented RRC messages stored according to 5.7.6.3; 1> except if going to RRC_IDLE was triggered by inter-RAT cell reselection while the UE is in RRC_INACTIVE or RRC_IDLE or when selecting an inter-RAT cell while T311 was running or when selecting an E-UTRA cell for EPS fallback for IMS voice as specified in 5.4.3.5: 2> if the UE is capable of L2 U2N Remote UE: 3> enter RRC_IDLE, and perform either cell selection as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20], or relay selection as specified in clause 5.8.15.3, or both; 2> else: 3> enter RRC_IDLE and perform cell selection as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; NOTE 1: Whether to release the PC5 unicast link is left to L2 U2N Remote UE's implementation. NOTE 2: It is left to UE implementation whether to stop T430, if running, when going to RRC_IDLE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.11 |
3,346 | 6.18.1 Description | Given the multitude of use cases for new verticals and services, each operator, based on its business model, can deploy a network serving only a subset of the vertical industries and services. However, this should not prevent an end-user from accessing all new services and capabilities that will be accessible via 5G systems. To provide a better user experience for their subscribers with UEs capable of simultaneous network access, network operators could contemplate a variety of sharing business models and partnership with other network and service providers to enable its subscribers to access all services via multiple networks simultaneously, and with minimum interruption when moving. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.18.1 |
3,347 | 5.14.1.1 SL Grant reception and SCI transmission | In order to transmit on the SL-SCH the MAC entity must have at least one sidelink grant. Sidelink grants are selected as follows for sidelink communication: - if the MAC entity is configured to receive a single sidelink grant dynamically on the PDCCH and more data is available in STCH than can be transmitted in the current SC period, the MAC entity shall: - using the received sidelink grant determine the set of subframes in which transmission of SCI and transmission of first transport block occur according to clause 14.2.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - consider the received sidelink grant to be a configured sidelink grant occurring in those subframes starting at the beginning of the first available SC Period which starts at least 4 subframes after the subframe in which the sidelink grant was received, overwriting a previously configured sidelink grant occurring in the same SC period, if available; - clear the configured sidelink grant at the end of the corresponding SC Period; - else, if the MAC entity is configured by upper layers to receive multiple sidelink grants dynamically on the PDCCH and more data is available in STCH than can be transmitted in the current SC period, the MAC entity shall for each received sidelink grant: - using the received sidelink grant determine the set of subframes in which transmission of SCI and transmission of first transport block occur according to clause 14.2.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - consider the received sidelink grant to be a configured sidelink grant occurring in those subframes starting at the beginning of the first available SC Period which starts at least 4 subframes after the subframe in which the sidelink grant was received, overwriting a previously configured sidelink grant received in the same subframe number but in a different radio frame as this configured sidelink grant occurring in the same SC period, if available; - clear the configured sidelink grant at the end of the corresponding SC Period; - else, if the MAC entity is configured by upper layers to transmit using one or multiple pool(s) of resources as indicated in clause 5.10.4 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] and more data is available in STCH than can be transmitted in the current SC period, the MAC entity shall for each sidelink grant to be selected: - if configured by upper layers to use a single pool of resources: - select that pool of resources for use; - else, if configured by upper layers to use multiple pools of resources: - select a pool of resources for use from the pools of resources configured by upper layers whose associated priority list includes the priority of the highest priority of the sidelink logical channel in the MAC PDU to be transmitted; NOTE 1: If more than one pool of resources has an associated priority list which includes the priority of the sidelink logical channel with the highest priority in the MAC PDU to be transmitted, it is left for UE implementation which one of those pools of resources to select. - randomly select the time and frequency resources for SL-SCH and SCI of a sidelink grant from the selected resource pool. The random function shall be such that each of the allowed selections (see TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]) can be chosen with equal probability; - use the selected sidelink grant to determine the set of subframes in which transmission of SCI and transmission of first transport block occur according to clause 14.2.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - consider the selected sidelink grant to be a configured sidelink grant occurring in those subframes starting at the beginning of the first available SC Period which starts at least 4 subframes after the subframe in which the sidelink grant was selected; - clear the configured sidelink grant at the end of the corresponding SC Period; NOTE 2: Retransmissions on SL-SCH cannot occur after the configured sidelink grant has been cleared. NOTE 3: If the MAC entity is configured by upper layers to transmit using one or multiple pool(s) of resources as indicated in clause 5.10.4 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], it is left for UE implementation how many sidelink grants to select within one SC period taking the number of sidelink processes into account. Sidelink grants are selected as follows for V2X sidelink communication: - if the MAC entity is configured to receive a sidelink grant dynamically on the PDCCH and data is available in STCH, the MAC entity shall for each carrier configured in sl-V2X-ConfigDedicated for which a sidelink grant has been dynamically received on the PDCCH for this TTI: - use the received sidelink grant to determine the number of HARQ retransmissions and the set of subframes in which transmission of SCI and SL-SCH occur according to clauses 14.2.1 and 14.1.1.4A of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - consider the received sidelink grant to be a configured sidelink grant for the carrier; - if the MAC entity is configured by upper layers to receive a sidelink grant on the PDCCH addressed to SL Semi-Persistent Scheduling V-RNTI, the MAC entity shall for each SL SPS configuration and for each carrier configured in sl-V2X-ConfigDedicated for which a sidelink grant has been received on the PDCCH addressed to SL Semi-Persistent Scheduling V-RNTI either for this TTI or for this PDCCH occasion according to clause 3.1 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [24]: - if PDCCH contents indicate SPS activation: - use the received sidelink grant to determine the number of HARQ retransmissions and the set of subframes in which transmission of SCI and SL-SCH occur according to clauses 14.2.1 and 14.1.1.4A of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - consider the received sidelink grant to be a configured sidelink grant for the carrier. - if PDCCH contents indicate SPS release: - clear the corresponding configured sidelink grant for the carrier. - if the MAC entity is configured by upper layers to transmit using pool(s) of resources in one or multiple carriers as indicated in either clause 5.10.13.1 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] or TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [25] based on sensing, or partial sensing, or random selection only if upper layers indicates that transmissions of multiple MAC PDUs are allowed according to either clause 5.10.13.1a of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] or TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [25], and the MAC entity selects to create a configured sidelink grant corresponding to transmissions of multiple MAC PDUs, and data is available in STCH associated with one or multiple carriers, the MAC entity shall for each Sidelink process configured for multiple transmissions: - if there is no configured sidelink grant associated with the Sidelink process on any carrier allowed for the STCH as indicated by upper layers, as specified in TS 24.386[ User Equipment (UE) to V2X control function; protocol aspects; Stage 3 ] [15]: - trigger the TX carrier (re-)selection procedure as specified in clause 5.14.1.5; - else if there is a configured sidelink grant associated with the Sidelink process: - if SL_RESOURCE_RESELECTION_COUNTER = 0 and when SL_RESOURCE_RESELECTION_COUNTER was equal to 1 the MAC entity randomly selected, with equal probability, a value in the interval [0, 1] which is above the probability configured by upper layers in probResourceKeep; or - if neither transmission nor retransmission has been performed by the MAC entity on any resource indicated in the configured sidelink grant during the last second; or - if sl-ReselectAfter is configured and the number of consecutive unused transmission opportunities on resources indicated in the configured sidelink grant is equal to sl-ReselectAfter; or - if none of the configured sidelink grant(s) on the carrier(s) allowed for the STCH have radio resources available in this TTI to accommodate a RLC SDU according to clause 5.14.1.3.1 by using the maximum allowed MCS configured by upper layers in maxMCS-PSSCH and the MAC entity selects not to segment the RLC SDU; or NOTE 4: If none of the configured sidelink grant(s) on the carrier(s) allowed for the STCH have radio resources available in this TTI to accommodate the RLC SDU according to clause 5.14.1.3.1, it is left for UE implementation whether to perform segmentation or sidelink resource reselection. - if none of the configured sidelink grant(s) on the carrier(s) allowed for the STCH have radio resources available in this TTI, according to clause 5.14.1.3.1 to fulfil the latency requirement of the data in a sidelink logical channel according to the associated PPPP, and the MAC entity selects not to perform transmission(s) corresponding to a single MAC PDU; or NOTE 5: If the latency requirement is not met, it is left for UE implementation whether to perform transmission(s) corresponding to single MAC PDU or sidelink resource reselection. - if the pool of resources where the sidelink grant is configured for the Sidelink process, is reconfigured by upper layers: - trigger the TX carrier (re-)selection procedure as specified in clause 5.14.1.5; - clear the configured sidelink grant associated to the Sidelink process; - flush the HARQ buffer associated to the Sidelink process; - else if SL_RESOURCE_RESELECTION_COUNTER = 0 and when SL_RESOURCE_RESELECTION_COUNTER was equal to 1 the MAC entity randomly selected, with equal probability, a value in the interval [0, 1] which is less than or equal to the probability configured by upper layers in probResourceKeep: - clear the configured sidelink grant, if available; - randomly select, with equal probability, an integer value in the interval [5, 15] for the resource reservation interval higher than or equal to 100ms, in the interval [10, 30] for the resource reservation interval equal to 50ms or in the interval [25, 75] for the resource reservation interval equal to 20ms, and set SL_RESOURCE_RESELECTION_COUNTER to the selected value; - use the previously selected sidelink grant for the number of transmissions of the MAC PDUs determined in clause 14.1.1.4B of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] with the resource reservation interval to determine the set of subframes in which transmissions of SCI and SL-SCH occur according to clauses 14.2.1 and 14.1.1.4B of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - consider the selected sidelink grant to be a configured sidelink grant; - if the TX carrier (re-)selection procedure was triggered in above and one or more carriers have been (re-)selected in the Tx carrier (re-)selection according to clause 5.14.1.5: - determine the order of the (re-)selected carriers, according to the decreasing order based on the highest priority of logical channels which are allowed on each (re-)selected carrier, and perform the following for each Sidelink process on each (re-)selected carrier according to the order: - select one of the allowed values configured by upper layers in restrictResourceReservationPeriod and set the resource reservation interval by multiplying 100 with the selected value; NOTE 6: How the UE selects this value is up to UE implementation. - randomly select, with equal probability, an integer value in the interval [5, 15] for the resource reservation interval higher than or equal to 100ms, in the interval [10, 30] for the resource reservation interval equal to 50ms or in the interval [25, 75] for the resource reservation interval equal to 20ms, and set SL_RESOURCE_RESELECTION_COUNTER to the selected value; - select the number of HARQ retransmissions from the allowed numbers that are configured by upper layers in allowedRetxNumberPSSCH included in pssch-TxConfigList and, if configured by upper layers, overlapped in allowedRetxNumberPSSCH indicated in cbr-pssch-TxConfigList for the highest priority of the sidelink logical channel(s) allowed on the selected carrier and the CBR measured by lower layers according to TS 36.214[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements ] [6] if CBR measurement results are available or the corresponding defaultTxConfigIndex configured by upper layers if CBR measurement results are not available; - select an amount of frequency resources within the range that is configured by upper layers between minSubchannel-NumberPSSCH and maxSubchannel-NumberPSSCH included in pssch-TxConfigList and, if configured by upper layers, overlapped between minSubchannel-NumberPSSCH and maxSubchannel-NumberPSSCH indicated in cbr-pssch-TxConfigList for the highest priority of the sidelink logical channel(s) allowed on the selected carrier and the CBR measured by lower layers according to TS 36.214[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements ] [6] if CBR measurement results are available or the corresponding defaultTxConfigIndex configured by upper layers if CBR measurement results are not available; - randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer according to clause 14.1.1.6 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], according to the amount of selected frequency resources. The selected time and frequency resources shall fulfil the physical layer requirements as specified in TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [10], and the random function shall be such that each of the allowed selections can be chosen with equal probability; - use the randomly selected resource to select a set of periodic resources spaced by the resource reservation interval for transmission opportunities of SCI and SL-SCH corresponding to the number of transmission opportunities of MAC PDUs determined in clause 14.1.1.4B of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - if the number of HARQ retransmissions is equal to 1: - if there are available resources left in the resources indicated by the physical layer according to clause 14.1.1.6 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] that meet the conditions in clause 14.1.1.7 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] for more transmission opportunities: - randomly select the time and frequency resources for one transmission opportunity from the available resources, according to the amount of selected frequency resources. The selected time and frequency resources shall fulfil the physical layer requirements as specified in TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [10], and the random function shall be such that each of the allowed selections can be chosen with equal probability; - use the randomly selected resource to select a set of periodic resources spaced by the resource reservation interval for the other transmission opportunities of SCI and SL-SCH corresponding to the number of retransmission opportunities of the MAC PDUs determined in clause 14.1.1.4B of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - consider the first set of transmission opportunities as the new transmission opportunities and the other set of transmission opportunities as the retransmission opportunities; - consider the set of new transmission opportunities and retransmission opportunities as the selected sidelink grant. - else: - consider the set as the selected sidelink grant; - use the selected sidelink grant to determine the set of subframes in which transmissions of SCI and SL-SCH occur according to clause 14.2.1 and 14.1.1.4B of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - consider the selected sidelink grant to be a configured sidelink grant; - else, if the MAC entity is configured by upper layers to transmit using pool(s) of resources in one or multiple carriers as indicated in either clause 5.10.13.1 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] or TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [25], the MAC entity selects to create a configured sidelink grant corresponding to transmission(s) of a single MAC PDU, and data is available in STCH associated with one or multiple carriers, the MAC entity shall for a Sidelink process: - trigger the TX carrier (re-)selection procedure as specified in clause 5.14.1.5; - if one or more carriers have been (re-)selected in the Tx carrier (re-)selection according to clause 5.14.1.5: - determine the order of the (re-)selected carriers, according to the decreasing order based on the highest priority of logical channels which are allowed on each (re-)selected carrier, and perform the following for each Sidelink process on each (re-)selected carrier according to the order: - select the number of HARQ retransmissions from the allowed numbers that are configured by upper layers in allowedRetxNumberPSSCH included in pssch-TxConfigList and, if configured by upper layers, overlapped in allowedRetxNumberPSSCH indicated in cbr-pssch-TxConfigList for the highest priority of the sidelink logical channel(s) allowed on the selected carrier and the CBR measured by lower layers according to TS 36.214[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements ] [6] if CBR measurement results are available or the corresponding defaultTxConfigIndex configured by upper layers if CBR measurement results are not available; - select an amount of frequency resources within the range that is configured by upper layers between minSubchannel-NumberPSSCH and maxSubchannel-NumberPSSCH included in pssch-TxConfigList and, if configured by upper layers, overlapped between minSubchannel-NumberPSSCH and maxSubchannel-NumberPSSCH indicated in cbr-pssch-TxConfigList for the highest priority of the sidelink logical channel(s) allowed on the selected carrier and the CBR measured by lower layers according to TS 36.214[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements ] [6] if CBR measurement results are available or the corresponding defaultTxConfigIndex configured by upper layers if CBR measurement results are not available; - randomly select the time and frequency resources for one transmission opportunity of SCI and SL-SCH from the resources indicated by the physical layer according to clause 14.1.1.6 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] , according to the amount of selected frequency resources. The selected time and frequency resources shall fulfil the physical layer requirement as specified in TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [10], and the random function shall be such that each of the allowed selections can be chosen with equal probability; - if the number of HARQ retransmissions is equal to 1: - if there are available resources left in the resources indicated by the physical layer according to clause 14.1.1.6 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] that meet the conditions in subcause 14.1.1.7 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] for one more transmission opportunity: - randomly select the time and frequency resources for the other transmission opportunity of SCI and SL-SCH corresponding to additional transmission of the MAC PDU from the available resources, according to the amount of selected frequency resources. The selected time and frequency resources shall fulfil the physical layer requirements as specified in TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [10], and the random function shall be such that each of the allowed selections can be chosen with equal probability; - consider a transmission opportunity which comes first in time as the new transmission opportunity and a transmission opportunity which comes later in time as the retransmission opportunity; - consider both of the transmission opportunities as the selected sidelink grant; - else: - consider the transmission opportunity as the selected sidelink grant; - use the selected sidelink grant to determine the subframes in which transmission(s) of SCI and SL-SCH occur according to clause 14.2.1 and 14.1.1.4B of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - consider the selected sidelink grant to be a configured sidelink grant. NOTE 7: For V2X sidelink communication, the UE should ensure the randomly selected time and frequency resources fulfill the latency requirement. NOTE 8: For V2X sidelink communication, when there is no overlapping between the chosen configuration(s) in pssch-TxConfigList and chosen configuration(s) indicated in cbr-pssch-TxConfigList, it is up to UE implementation whether the UE transmits and which transmitting parameters the UE uses between allowed configuration(s) indicated in pssch-TxConfigList and allowed configuration(s) indicated in cbr-pssch-TxConfigList. The MAC entity shall for each subframe: - for each configured sidelink grant occurring in this subframe: - if SL_RESOURCE_RESELECTION_COUNTER = 1 for the Sidelink process associated with the configured sidelink grant and the MAC entity randomly selected, with equal probability, a value in the interval [0, 1] which is above the probability configured by upper layers in probResourceKeep: - set the resource reservation interval for the configured sidelink grant equal to 0; - if the configured sidelink grant corresponds to transmission of SCI: - for V2X sidelink communication in UE autonomous resource selection: - consider the selected transmission format to be SL-V2X-TxProfile for the highest priority of the sidelink logical channel(s) in the MAC PDU (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]); - select a MCS which is, if configured, within the range that is configured by upper layers between minMCS-PSSCH and maxMCS-PSSCH included in pssch-TxConfigList associated with the selected transmission format and, if configured by upper layers, overlapped between minMCS-PSSCH and maxMCS-PSSCH indicated in cbr-pssch-TxConfigList associated with the selected transmission format for the highest priority of the sidelink logical channel(s) in the MAC PDU and the CBR measured by lower layers according to TS 36.214[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements ] [6] if CBR measurement results are available or the corresponding defaultTxConfigIndex configured by upper layers if CBR measurement results are not available; NOTE 9: MCS selection is up to UE implementation if the MCS or the corresponding range is not configured by upper layers. NOTE 10: For V2X sidelink communication, when there is no overlapping between the chosen configuration(s) included in pssch-TxConfigList and chosen configuration(s) indicated in cbr-pssch-TxConfigList, it is up to UE implementation whether the UE transmits and which transmitting parameters the UE uses between allowed configuration(s) indicated in pssch-TxConfigList and allowed configuration(s) indicated in cbr-pssch-TxConfigList. - for V2X sidelink communication in scheduled resource allocation: - consider the selected transmission format to be SL-V2X-TxProfile for the highest priority of the sidelink logical channel(s) in the MAC PDU (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]); - select a MCS which is associated with the selected transmission format unless it is configured by upper layer; - instruct the physical layer to transmit SCI corresponding to the configured sidelink grant; - for V2X sidelink communication, deliver the configured sidelink grant, the associated HARQ information and the value of the highest priority of the sidelink logical channel(s) in the MAC PDU to the Sidelink HARQ Entity for this subframe; - else if the configured sidelink grant corresponds to transmission of first transport block for sidelink communication: - deliver the configured sidelink grant and the associated HARQ information to the Sidelink HARQ Entity for this subframe. NOTE 11: If the MAC entity has multiple configured sidelink grants occurring in one subframe and if not all of them can be processed due to the single-cluster SC-FDM restriction, it is left for UE implementation which one of these to process according to the procedure above. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.14.1.1 |
3,348 | 4.2.6 Service-based interfaces | The 5G System Architecture contains the following service-based interfaces: Namf: Service-based interface exhibited by AMF. Nsmf: Service-based interface exhibited by SMF. Nnef: Service-based interface exhibited by NEF. Npcf: Service-based interface exhibited by PCF. Nudm: Service-based interface exhibited by UDM. Naf: Service-based interface exhibited by AF. Nnrf: Service-based interface exhibited by NRF. Nnsacf: Service-based interface exhibited by NSACF. Nnssaaf: Service-based interface exhibited by NSSAAF. Nnssf: Service-based interface exhibited by NSSF. Nausf: Service-based interface exhibited by AUSF. Nudr: Service-based interface exhibited by UDR. Nudsf: Service-based interface exhibited by UDSF. N5g-eir: Service-based interface exhibited by 5G-EIR. Nnwdaf: Service-based interface exhibited by NWDAF. Nchf: Service-based interface exhibited by CHF. Nucmf: Service-based interface exhibited by UCMF. Ndccf: Service based interface exhibited by DCCF. Nmfaf: Service based interface exhibited by MFAF. Nadrf: Service based interface exhibited by ADRF. Naanf: Service-based interface exhibited by AANF. NOTE 1: The Service-based interface exhibited by AANF is defined in TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [124]. N5g-ddnmf: Service-based interface exhibited by 5G DDNMF. Nmbsmf: Service-based interface exhibited by MB-SMF. Nmbsf: Service-based interface exhibited by MBSF. NOTE 2: The Service-based interfaces exhibited by MB-SMF and MBSF are defined in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [129]. Ntsctsf: Service-based interface exhibited by TSCTSF. Nbsp: Service-based interface exhibited by an SBI capable Boostrapping Server Function in GBA. NOTE 2: The Service-based interfaces exhibited by an SBI capable Boostrapping Server Function are defined in TS 33.220[ Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) ] [140] and TS 33.223[ Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function ] [141]. Neasdf: Service-based interface exhibited by EASDF. NOTE 3: The Service-based interfaces exhibited by EADSF is defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. Nupf: Service-based interface exhibited by UPF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.6 |
3,349 | 4.23.16.3.1 The target AMF is in the PLMN of the N3IWF | The following impacts are applicable to clause 4.9.2.3.1 when a PDU Session is handover from untrusted non-3GPP to 3GPP access (home routed roaming) and target AMF is in the PLMN of the N3IWF: - 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. A different V-SMF and a different V-UPF may be selected for the PDU Session. If a new V-SMF is selected, in the Nsmf_PDUSession_Create Response the H-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 V-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) acceptable according to VPLMN policies. - (additional) Step 4: If a new V-SMF and a new V-UPF are selected for the PDU Session, the step 3a and 14 in clause 4.3.4.3 are performed to release the resource in the old V-SMF and old V-UPF. The steps 2 to 4 shall be repeated for all PDU Sessions to be moved from to untrusted non-3GPP access to 3GPP access. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.16.3.1 |
3,350 | 4.13.4 Emergency Services 4.13.4.1 General | If the 5GS supports Emergency Services, the support is indicated to UE via the Registration Accept message on per-TA-list and per-RAT basis, as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the 5GS supports Emergency Services Fallback, the support is indicated to UE via the Registration Accept message on per-TA-list and per-RAT basis, as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE shall follow the domain selection rules for emergency session attempts as described in TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [28]. If the 5GC has indicated Emergency Services Fallback support for the TA and RAT where the UE is currently camping and if the UE supports emergency services fallback, the UE shall initiate the Emergency Services Fallback procedure described in clause 4.13.4.2. At QoS Flow establishment request for Emergency Services, the procedure described in clause 4.13.6.2 Inter RAT Fallback in 5GC for IMS voice or the procedure described in clause 4.13.6.1 EPS fallback for IMS voice may be triggered by the network, when configured. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.4 |
3,351 | 8.2.2.3.1 Minimum Requirement 2 Tx Antenna Port | For single carrier, the requirements are specified in Table 8.2.2.3.1-2, with the addition of the parameters in Table 8.2.2.3.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 2 DL CCs, the requirements are specified in Table 8.2.2.3.1-4, with the addition of the parameters in Table 8.2.2.3.1-3 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For CA with 3 DL CCs, the requirements are specified in Table 8.2.2.3.1-7, based on single carrier requirement specified in Table 8.2.2.3.1-5, with the addition of the parameters in Table 8.2.2.3.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 4 DL CCs, the requirements are specified in Table 8.2.2.3.1-8, based on single carrier requirement specified in Table 8.2.2.3.1-5, with the addition of the parameters in Table 8.2.2.3.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, the requirements are specified in Table 8.2.2.3.1-9, based on single carrier requirement specified in Table 8.2.2.3.1-5, with the addition of the parameters in Table 8.2.2.3.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 6 DL CCs, the requirements are specified in Table 8.2.2.3.1-10, based on single carrier requirement specified in Table 8.2.2.3.1-5, with the addition of the parameters in Table 8.2.2.3.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 7 DL CCs, the requirements are specified in Table 8.2.2.3.1-11, based on single carrier requirement specified in Table 8.2.2.3.1-5, with the addition of the parameters in Table 8.2.2.3.1-3 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.2.3.1-1: Test Parameters for Large Delay CDD (FRC) Table 8.2.2.3.1-2: Minimum performance Large Delay CDD (FRC) Table 8.2.2.3.1-3: Test Parameters for Large Delay CDD (FRC) for CA Table 8.2.2.3.1-4: Minimum performance Large Delay CDD (FRC) for CA with 2DL CCs Table 8.2.2.3.1-5: Single carrier performance for multiple CA configurations Table 8.2.2.3.1-6: Void Table 8.2.2.3.1-7: Minimum performance (FRC) based on single carrier performance for CA with 3 DL CCs Table 8.2.2.3.1-8: Minimum performance (FRC) based on single carrier performance for CA with 4 DL CCs Table 8.2.2.3.1-9: Minimum performance (FRC) based on single carrier performance for CA with 5 DL CCs Table 8.2.2.3.1-10: Minimum performance (FRC) based on single carrier performance for CA with 6 DL CCs Table 8.2.2.3.1-11: Minimum performance (FRC) based on single carrier performance for CA with 7 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.3.1 |
3,352 | 7.3.1G Minimum requirements (QPSK) for V2X | When UE is configured for E-UTRA V2X reception non-concurrent with E-UTRA uplink transmissions for E-UTRA V2X operating bands specified in Table 5.5G-1, the throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.8.2 with parameters specified in Table 7.3.1G-1. Table 7.3.1G-1: Reference sensitivity of E-UTRA V2X Bands (PC5) Table 7.3.1.G-1a: Sidelink TX configuration for reference sensitivity of E-UTRA V2X Bands (PC5) When UE is configured for E-UTRA V2X reception on V2X carrier con-current with E-UTRA uplink and downlink for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2 with one or multiple contiguous carriers in V2X sidelink, E-UTRA V2X sidelink throughput for each component carrier shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.8.2 with parameters specified in Table 7.3.1G-2. Also the E-UTRAdownlink throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.3.3.2. For the UE which supports V2X in an operating band as specified in Table 5.5G-2, and the UE also supports a E-UTRA downlink inter-band con-current configuration in Table 7.3.1G-2A, the minimum requirement for reference sensitivity in Table 7.3.1G-1 and Table 7.3.1G-2 shall be increased by the amount given in ΔRIB,c in Table 7.3.1G-2A for the corresponding E-UTRA V2X band. Table 7.3.1G-2: Reference sensitivity for V2X Communication QPSK PREFSENS Table 7.3.1G-2A: ΔRIB,c (two bands) The reference sensitivity is defined to be met with E-UTRA uplink assigned to one band (that differs from the V2X operating band) and all E-UTRA downlink carriers active. The E-UTRA uplink resource blocks shall be located as close as possible to E-UTRA V2X operating band but confined within the transmission bandwidth configuration for the channel bandwidth (Table 5.6-1). The uplink configuration for the E-UTRA operating band is specified in Table 7.3.1G-3 and 7.3.1G-4. The REFSENS of Uu downlink and PC5 sidelink will be tested at the same time. Table 7.3.1G-3: Uplink configuration for REFSENS of E-UTRA V2X Bands Table 7.3.1G-4: Sidelink TX configuration for REFSENS of E-UTRA V2X Bands For intra-band contiguous multi-carrier operation, the reference sensitivity requirement specified in Table 7.3.1G-1 shall apply for each component carrier with all carriers active. The requirement is applied for multi-carrier intra-band con-current receptions when 2 carrier transmissions are activated at the same time. Table 7.3.1G-5: Sidelink TX configuration for REFSENS of E-UTRA V2X Bands for intra-band multi-carrier operation | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.3.1G |
3,353 | 7.6.2.1D Minimum requirements for ProSe | The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.6.2 with parameters specified in Tables 7.6.2.1D-1, 7.6.2.1D-2 and 7.6.2.1D-3. For Table 7.6.2.1D-3 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. Table 7.6.2.1D-1: Out-of-band blocking parameters for ProSe Direct Discovery Table 7.6.2.1D-2: Out-of-band blocking parameters for ProSe Direct Communication Table 7.6.2.1D-3: Out of band blocking for ProSe | 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.1D |
3,354 | I.3 Security mechanisms for interfaces with RNCs in exposed locations | In order to protect the Iu and Iur interfaces as required by Annexes X.2.3 and X.2.4, it is required to implement IPsec ESP as specified and profiled by TS 33.210[ Network Domain Security (NDS); IP network layer security ] [39], with confidentiality, integrity and replay protection. NOTE 1: In certain deployments IPsec security mechanisms may not be usable on the interfaces of the RNC in exposed locations. In such cases it is an operator decision to either ensure the interface security by other means, or to change the interface transport mechanisms to allow the application of IPsec security mechanisms. IKEv2 with certificates based authentication shall be implemented. The certificates shall be implemented according to the profile described by TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [40]. IKEv2 shall be implemented conforming to the IKEv2 profile described in TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [40]. For Iu and Iur, tunnel mode IPsec is mandatory to implement. On the core network side a SEG may be used to terminate the IPsec tunnel. Transport mode IPsec is optional for implementation on Iu and Iur. NOTE 2: Transport mode can be used for reducing the protocol overhead added by IPsec. NOTE 3: The IPsec security associations may also apply to IP packets carrying management information. If the sender of IPsec traffic uses DiffServ Code Points (DSCPs) to distinguish different QoS classes, either by copying DSCP from the inner IP header or directly setting the encapsulating IP header’s DSCP, the resulting traffic may be reordered to the point where the receiving node’s anti-replay check discards the packet. If different DSCPs are used on the encapsulating IP header, then to avoid packet discard under one IKE SA and with the same set of traffic selectors, distinct child-SAs should be established for each of the traffic classes (using the DSCPs as classifiers) as is specified in RFC 4301 [41]. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | I.3 |
3,355 | 6.1.3.2.2a Unsuccessful secondary PDP context activation requested by the network | Upon receipt of the REQUEST SECONDARY PDP CONTEXT ACTIVATION message, the MS may reject the network requested secondary PDP context activation by sending the REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message to the network. The message contains the same TI as included in the REQUEST SECONDARY PDP CONTEXT ACTIVATION and an additional cause code that typically indicates one of the following causes: # 26: insufficient resources; # 31: activation rejected, unspecified; # 40: feature not supported; # 41: semantic error in the TFT operation; # 42: syntactical error in the TFT operation; # 43: unknown PDP context; # 44: semantic errors in packet filter(s); # 45: syntactical errors in packet filter(s); # 46: PDP context without TFT already activated; # 48: request rejected, Bearer Control Mode violation; or # 95 - 111: protocol errors. The MS should reply with the REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message with cause #48 "request rejected, Bearer Control Mode violation" if the previously negotiated Bearer Control Mode is 'MS-only'. If a PDP context for the TI given in the Linked TI IE exists, then the TFT in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message is checked by the MS for different types of TFT IE errors as specified in subclause 6.1.3.2.3. Upon receipt of a REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message, the network shall stop timer T3385 and enter state PDP-INACTIVE. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.2.2a |
3,356 | 16.3.4.3 UE Context Handling | Following the initial access, the establishment of the RRC connection and the selection of the correct AMF, the AMF establishes the complete UE context by sending the Initial Context Setup Request message to the NG-RAN over NG-C. The message contains the Allowed NSSAI and additionally contains the S-NSSAI(s) as part of the PDU session(s) resource description when present in the message and may contain Partially Allowed NSSAI. Upon successful establishment of the UE context and allocation of PDU session resources to the relevant network slice(s) when present, the NG-RAN responds with the Initial Context Setup Response message. Figure 16.3.4.3-1: Network Slice-aware Initial Context Setup | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.3.4.3 |
3,357 | 5.16.4.11 Emergency Services Fallback | In order to support various deployment scenarios for obtaining Emergency Services, the UE and 5GC may support the mechanism to direct or redirect the UE either towards E-UTRA connected to 5GC (RAT fallback) when only NR does not support Emergency Services or towards EPS (E-UTRAN connected to EPC System fallback) when the 5GC does not support Emergency Services. Emergency Services fallback may be used when the 5GS does not indicate support for Emergency Services (see clause 5.16.4.1) and indicates support for Emergency Services fallback. Following principles apply for Emergency Services Fallback: - If the AMF indicates support for Emergency Services fallback in the Registration Accept message, then in order to initiate Emergency Service, normally registered UE supporting Emergency Services fallback shall initiate a Service Request with Service Type set to Emergency Services fallback as defined in clause 4.13.4.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - AMF uses the Service Type Indication within the Service Request to redirect the UE towards the appropriate RAT/System. The 5GS may, for Emergency Services, trigger one of the following procedures: - Handover or redirection to EPS. - Handover or redirection to E-UTRA connected to 5GC. - After receiving the Service Request for Emergency Fallback, the AMF triggers N2 procedure resulting in either CONNECTED state mobility (Handover procedure) or IDLE state mobility (redirection) to either E-UTRA/5GC or to E-UTRAN/EPC depending on factors such as N26 availability, network configuration and radio conditions. In the N2 procedure, the AMF based on support for Emergency Services in 5GC or EPC may indicate the target CN for the RAN node to know whether inter-RAT fallback or inter-system fallback is to be performed. The target CN indicated in the N2 procedure is also conveyed to the UE in order to be able to perform the appropriate NAS procedures (S1 or N1 Mode). - When the AS re-keying procedure and the Emergency Fallback procedure collides, the AMF gives up the AS re-keying procedure and only initiates the Emergency Fallback procedure. NOTE 1: Emergency Services Fallback to EPS can be followed by an onward movement to GERAN or UTRAN via CSFB procedures if the PLMN does not support IMS emergency services. NOTE 2: If the UE has signalled that S1 mode is disabled for a network that only supports IMS voice via EPS Fallback, the AMF will not indicate that Emergency Services Fallback is supported over 3GPP access. Emergency Services fallback is supported only in case of PLMN. Emergency Services Fallback is not supported for SNPN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.4.11 |
3,358 | 16.21.3.2 Path Failure Report | The L2 MP Remote UE in RRC_CONNECTED performs Uu RLM (as described in clause 9.2.7). When the L2 MP Remote UE detects Uu Radio Link Failure (RLF) on the direct path, the L2 MP Remote UE triggers path failure reporting through the indirect path via a RRC message if split SRB1 is configured and the indirect path is not suspended. Otherwise, RRC connection re-establishment is initiated. When the L2 MP Remote UE using PC5 indirect path detects PC5 Radio Link Failure (RLF) and/or Uu link failure on the indirect path, the L2 MP Remote UE triggers path failure reporting through the direct path via a RRC message, if the direct path is not suspended. When the L2 MP Remote UE using N3C indirect path detects N3C link failure and/or Uu link failure on the indirect path, the L2 MP Remote UE triggers path failure reporting through the direct path via a RRC message, if the direct path is not suspended. 16.21.3.3 System Information The L2 MP Remote UE can acquire any necessary SIB(s) over Uu interface or indirect path. If common search space for system information is configured with the active BWP on PCell, the L2 MP Remote UE can perform direct system information acquisition on PCell. The L2 MP Remote UE can also receive system information at lease PBCH/MIB on the direct path and directly acquires SFN from MIB on the direct path. Besides, the L2 MP Remote UE can receive the system information via dedicated RRC signalling via SRB1. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.21.3.2 |
3,359 | 5.28a.2 Transfer of TL-Container between SMF/CUC and AN-TL and CN-TL | If NG-RAN and UPF support AN-TL and CN-TL, the SMF/CUC may use the TL-Container to send a: 1) get-request. 2) set-request: submits the following information elements to the AN-TL or CN-TL: - InterfaceConfiguration as described in Annex M, clause M.1 (one InterfaceConfiguration is associated with each QFI in the N3 tunnel) - Interface ID Group. - TN Stream Identification Information for DataFrameSpecification. - TN Stream Identification Information for mask-and-match. - Interval (only provided together with TimeAwareOffset). - MaxFrameSize (only provided together with TimeAwareOffset). The AN-TL or CN-TL may use the TL-Container to send a: 1) get-response: indicates the following elements of the Talker or Listener group from the AN-TL or CN-TL: - EndStationInterfaces: list of InterfaceIDs. - InterfaceCapabilities. - Buffer capability: maximum possible buffer duration for a packet of a stream with the maximum size of an Ethernet packet (1522 Bytes) that is supported by the AN-TL / CN-TL when acting as a Talker. 2) set-response: reports the processing results for the corresponding set-request to the SMF/CUC. Details on the TL-Container information are provided in Table M.2-1 of clause M.2. The SMF/CUC may request the NG-RAN/UPF to report AN-TL or CN-TL information by including a TL-Container with a get-request to the AN-TL or CN-TL, respectively. The get-request is sent to AN-TL in the N2 SM information and to CN-TL in the N4 Session Establishment as described in clause 4.3.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the NG-RAN/UPF supports AN-TL/CN-TL, the NG-RAN/AN-TL and UPF/CN-TL responds with a TL-Container including the elements defined for the get-response. The SMF/CUC may submit TL-Container including a set-request the elements defined for the set-request to NG-RAN/AN-TL and UPF/CN-TL. The set-request is sent to AN-TL in the N2 SM information and to CN-TL in the N4 Session Modification request as described in clause 4.3.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The SMF/CUC shall initiate to the CN-TL/AN-TL the deletion of TN stream configurations as described in 4.3.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The InterfaceConfiguration is associated with the corresponding QFI in the N3 tunnel in the NG-RAN or UPF, respectively. The AN-TL/CN-TL uses the provided configuration for the traffic in the QoS Flow of the given QFI as described in Annex M. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.28a.2 |
3,360 | – QuantityConfig | The IE QuantityConfig specifies the measurement quantities and layer 3 filtering coefficients for NR and inter-RAT measurements. QuantityConfig information element -- ASN1START -- TAG-QUANTITYCONFIG-START QuantityConfig ::= SEQUENCE { quantityConfigNR-List SEQUENCE (SIZE (1..maxNrofQuantityConfig)) OF QuantityConfigNR OPTIONAL, -- Need M ..., [[ quantityConfigEUTRA FilterConfig OPTIONAL -- Need M ]], [[ quantityConfigUTRA-FDD-r16 QuantityConfigUTRA-FDD-r16 OPTIONAL, -- Need M quantityConfigCLI-r16 FilterConfigCLI-r16 OPTIONAL -- Need M ]] } QuantityConfigNR::= SEQUENCE { quantityConfigCell QuantityConfigRS, quantityConfigRS-Index QuantityConfigRS OPTIONAL -- Need M } QuantityConfigRS ::= SEQUENCE { ssb-FilterConfig FilterConfig, csi-RS-FilterConfig FilterConfig } FilterConfig ::= SEQUENCE { filterCoefficientRSRP FilterCoefficient DEFAULT fc4, filterCoefficientRSRQ FilterCoefficient DEFAULT fc4, filterCoefficientRS-SINR FilterCoefficient DEFAULT fc4 } FilterConfigCLI-r16 ::= SEQUENCE { filterCoefficientSRS-RSRP-r16 FilterCoefficient DEFAULT fc4, filterCoefficientCLI-RSSI-r16 FilterCoefficient DEFAULT fc4 } QuantityConfigUTRA-FDD-r16 ::= SEQUENCE { filterCoefficientRSCP-r16 FilterCoefficient DEFAULT fc4, filterCoefficientEcNO-r16 FilterCoefficient DEFAULT fc4 } -- TAG-QUANTITYCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,361 | K.2.2.6 Configuration for transport protocols | The procedure described in this clause is applicable when the PTP Profile that is used for the PTP instance in 5GS defines multiple permitted transport protocols. TSN AF or TSCTSF may use the element "Supported transport types" in port management information container (per DS-TT) to determine the supported transport types in the DS-TT. TSN AF or TSCTSF may use the element "Supported transport types" in UMIC (per NW-TT) to determine the supported transport types in the NW-TT. The TSN AF or TSCTSF may use the element "Transport type" (per PTP instance) in PMIC to configure the transport protocol in use for the PTP instance in DS-TT. The TSN AF or TSCTSF may use the element "Transport type" (per PTP instance) in UMIC to configure the transport protocol in use for the PTP instance in NW-TT. The PTP instance shall be configured to use one of the following transport protocols: 1) Ethernet as described in Annex E of IEEE Std 1588 [126]. The Ethertype as defined for PTP shall be used. The related Ethernet frames carry the PTP multicast Ethernet destination MAC address. 2) UDP over IPv4 as described in Annex C of IEEE Std 1588 [126], 3) UDP over IPv6 as described in Annex D of IEEE Std 1588 [126]. Option 1 applies to Ethernet PDU Session type. Options 2 and 3 apply to IP PDU Session type or Ethernet PDU Session type with IP payload. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | K.2.2.6 |
3,362 | 8.2.1.2.6 Enhanced Performance Requirement Type B - 2 Tx Antenna Ports with TM9 interference model | The requirements are specified in Table 8.2.1.2.6-2, with the addition of parameters in Table 8.2.1.2.6-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of two interfering cells applying transmission mode 9 interference model defined in clause B.6.4. In Table 8.2.1.2.6-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.2.1.2.6-1: Test Parameters for Transmit Diversity Performance (FRC) with TM9 interference model Table 8.2.1.2.6-2: Minimum Performance for Enhanced Performance Requirement Type B, Transmit Diversity (FRC) with TM9 interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.2.6 |
3,363 | 14.7.1 Format of W-APN Network Identifier | The W-APN Network Identifier follows the format defined for APNs in clause 9.1.1. In addition to what has been defined in clause 9.1.1 the W-APN Network Identifier shall not contain "w-apn." and not end in ".3gppnetwork.org". A W-APN Network Identifier may be used to access a service associated with a PDG. This may be achieved by defining: - a W-APN which corresponds to a FQDN of a PDG, and which is locally interpreted by the PDG as a request for a specific service, or - a W-APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or a W-APN Network Identifier consisting of a Reserved Service Label alone, which indicates a PDG by the nature of the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed between operators who have WLAN roaming agreements. The W-APN Network Identifier for the support of IMS Emergency calls shall take the form of a common, reserved Network Identifier of the form "sos". As an example, the W-APN for MCC 345 and MNC 12 is coded in the DNS as: "sos.w-apn.mnc012.mcc345.pub.3gppnetwork.org". where "sos" is the W-APN Network Identifier and " mnc012.mcc345.pub.3gppnetwork.org " is the W-APN Operator Identifier. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 14.7.1 |
3,364 | 5.19.6 SMF Overload Control | The SMF shall contain mechanisms for avoiding and handling overload situations. This can include the following measures: - SMF overload control that could result in rejections of NAS requests. The SMF overload control may be activated by SMF due to congestion situation at SMF e.g. configuration, by a restart or recovery condition of a UPF, or by a partial failure or recovery of a UPF for a particular UPF(s). Under unusual circumstances, if the SMF has reached overload situation, the SMF activates NAS level congestion control as specified in clause 5.19.7. The SMF may restrict the load that the AMF(s) are generating, if the AMF is configured to enable the overload restriction. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.19.6 |
3,365 | 11.2.1.1 Transparent access to the Internet | Figure 9: Example of the PDN Interworking Model, transparent case In figure 9, an example PDN interworking model for transparent access to the Internet is provided for a GGSN and its Gi reference point. In transparent access to the Internet case: - the MS is given an IPv4 address and/or an IPv6 prefix belonging to the operator addressing space. The IPv4 address and/or IPv6 prefix is assigned either at subscription in which case it is a static address or at IP-CAN session establishment in which case it is a dynamic address. This IPv4 address and/or IPv6 prefix if applicable is used for packet forwarding between the Internet and the GGSN/P-GW and within the packet domain. With IPv6, Stateless Address Autoconfiguration shall be used to assign an IPv6 address to the MS. These procedures are as described in the IPv6 non-transparent access case except that the addresses belong to the operator addressing space. - the MS need not send any authentication request at IP-CAN session establishment procedure and the GGSN/P-GW need not take any part in the user authentication/authorization process. The transparent case provides at least a basic ISP service. As a consequence of this it may therefore provide a bearer service for a tunnel to a private Intranet. Note that the remainder of this subclause deals with this specific use-case as depicted in figure 10. - The user level configuration may be carried out between the TE and the intranet, the Packet Domain network is transparent to this procedure. The used protocol stack is depicted in figure 10. Figure 10: Transparent access to an Intranet In figure 10, an example for transparent access to an Intranet is provided for a GGSN and its Gi reference point, but the same principle is applicable to EPC. The communication between the PLMN and the Intranet may be performed over any network, even an insecure network e.g. the Internet. There is no specific security protocol between the GGSN and the Intranet because security is ensured on an end to end basis between the MS and the intranet by the "Intranet Protocol". User authentication and encryption of user data are done within the "Intranet Protocol" if either of them is needed. This "Intranet Protocol" may also carry private (IP) addresses belonging to the address space of the Intranet. An example of an "Intranet Protocol" is Ipsec (see RFC 1825 [61]). If Ipsec is used for this purpose then Ipsec authentication header or security header may be used for user (data) authentication and for the confidentiality of user data (see RFC 1826 [62] and RFC 1827 [63]). In this case private IP tunnelling within public IP takes place. | 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.1 |
3,366 | D.4.1.1 Service area and connection density | Service coverage is only required along the medium-voltage line. In Europe, the line often forms a loop (see figure D.4.1.0-1), while deployments in other countries, e.g. the USA, tend to extend linearly over distances up to ~ 100 km. The vertical dimension of the poles in a medium voltages line is typically less than 40 m. Especially in urban areas, the number of ring main units can be rather large (> 10 km-2), and the number of connections to each ring main unit is expected to increase swiftly once economical, suitable wireless connectivity becomes available. We predict connection densities of up to 1.000 km-2. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | D.4.1.1 |
3,367 | 9.9.4.25 Release assistance indication | The purpose of the Release assistance indication IE is to inform the network whether - no further uplink and no further downlink data transmission is expected; or - only a single downlink data transmission (e.g. acknowledgement or response to uplink data) and no further uplink data transmission subsequent to the uplink data transmission is expected. The Release assistance indication information element is coded as shown in figure 9.9.4.25.1 and table 9.9.4.25.1. The Release assistance indication is a type 1 information element. Figure 9.9.4.25.1: Release assistance indication information element Table 9.9.4.25.1: Release assistance indication information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.4.25 |
3,368 | 6.4.1.5 Abnormal cases in the UE | The following abnormal cases can be identified: a) Default EPS bearer context activation request for an already activated default EPS bearer context: If the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with an EPS bearer identity identical to the EPS bearer identity of an already activated default EPS bearer context, the UE shall locally deactivate the existing default EPS bearer context and all the associated dedicated EPS bearer contexts, if any, and proceed with the requested default EPS bearer context activation. b) Default EPS bearer context activation request for an already activated dedicated EPS bearer context: If the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with an EPS bearer identity identical to the EPS bearer identity of an already activated dedicated EPS bearer context, the UE shall locally deactivate the existing dedicated EPS bearer context and proceed with the requested default EPS bearer context activation. | 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.1.5 |
3,369 | 5.1.5 Coordination between EMM and MM | UEs that operate in CS/PS mode 1 or CS/PS mode 2 of operation shall use the combined EPS/IMSI attach procedure in order to attach to both EPS and non-EPS services. UEs that operate in CS/PS mode 1 or CS/PS mode 2 of operation and are already attached to both EPS and non-EPS services shall use the combined tracking area updating and periodic tracking area updating procedures. UEs that operate in CS/PS mode 1 or CS/PS mode 2 of operation and are already attached to both EPS and non-EPS services shall perform a combined detach procedure in order to detach for non-EPS services. UEs that operate in CS/PS mode 1 or CS/PS mode 2 of operation should not use any MM timers related to MM specific procedures (e.g. T3210, T3211, T3212, T3213) while camped on E-UTRAN, unless the re-activation of these timers is explicitly described. If the MM timers are already running, the UE should not react on the expiration of the timers. 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] and moves from GERAN/UTRAN to E-UTRAN, the UE shall: - if timer T3242 is running, start timer T3444 with the time left on T3242 and stop timer T3242; - if timer T3243 is running, start timer T3445 with the time left on T3243 and stop timer T3243; - if the UE is attached for both EPS services and non-EPS services and timer T3242 or timer T3243 is running, perform a combined tracking area updating procedure; and NOTE 1: A UE configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17] being attached for both EPS services and non-EPS services upon moving from GERAN/UTRAN to E-UTRAN is only possible in the case when the UE has performed a combined attach in E-UTRAN, subsequently moved to GERAN/UTRAN and returned to E-UTRAN before timer T3242 or timer T3243 expires. - if the UE is attached for non-EPS services only and timer T3242 or timer T3243 is running, perform a combined attach procedure. NOTE 2: Timers T3242 and T3243 are specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]. | 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.1.5 |
3,370 | 2.8.2.2.3 Mapping in the new MME | In order to retrieve the UE's information, e.g. the IMSI, from the old SGSN, the new MME extracts only the RAI and P-TMSI from the GUTI via the reverse mapping procedure to that specified in clause 2.8.2.2.2. This is done in order to be able to include the mapped RAI and P-TMSI, along with the P-TMSI Signature received by the MME from the UE, in the corresponding message sent to the old SGSN (see 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [6] and 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [88] for specifics of the messaging). The old SGSN compares the received RAI, P-TMSI and P-TMSI Signature with the stored values for identifying the UE. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.8.2.2.3 |
3,371 | 8.8.5.1 TDD | For the parameters specified in Table 8.8.5.1-1 the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.8.5.1-2. The purpose of this test is to verify the distributed EPDCCH performance when the EPDCCH transmission in the serving cell is interfered by two interfering cells and applying TM9 interference model. In Table 8.8.5.1-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical setup is in accordance with Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.8.5.1-1: Test Parameters for EPDCCH Table 8.8.5.1-2: Minimum performance for EPDCCH for enhanced downlink control channel performance requirements Type A | 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.8.5.1 |
3,372 | 4.11.2 Successful PUCCH allocations for SCell scheduling in Carrier Aggregation | a) This measurement provides the number of successful PUCCH allocations in the PCell for SCell scheduling in Carrier Aggregation. This measurement is split into subcounters for the PUCCH format 3 and PUCCH format 1bwcs. b) CC c) On the success of a Scell scheduling in Carrier Aggregation. d) Each measurement is an integer value. e) DRB.PucchAllocNbrSucc.PUCCHFormat where PUCCHFormat identifies the PUCCH format, which is either “format3” or “format1bwcs”. 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.11.2 |
3,373 | 5.2.5.8 Npcf_AMPolicyAuthorization Service 5.2.5.8.1 General | Service description: This service is to authorise an AF request and potentially create or change access and mobility management policies of a UE based on the request of the authorized AF or TSCTSF. This service allows the NF consumer to subscribe/unsubscribe the notification of events for related to a user (i.e. a SUPI) that has an AM or UE Policy Association established, or both, the list of events are defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The description of the Throughput requirements, service coverage requirements and policy duration are defined in clause 6.1.2.6.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.8 |
3,374 | 10.5.6.12 Traffic Flow Template | The purpose of the traffic flow template information element is to specify the TFT parameters and operations for a PDP context. In addition, this information element may be used to transfer extra parameters to the network (e.g. the Authorization Token; see 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [95]). The TFT may contain packet filters for the downlink direction, the uplink direction or packet filters that are applicable to both directions. The packet filters determine the traffic mapping to PDP contexts. The downlink packet filters shall be used by the network and the uplink packet filters shall be used by the MS. A packet filter that is applicable to both directions shall be used by the network as a downlink packet filter and by the MS as an uplink packet filter. The traffic flow template is a type 4 information element with a minimum length of 3 octets. The maximum length for the IE is 257 octets. NOTE 1: The IE length restriction is due to the maximum length that can be encoded in a single length octet. NOTE 2: A maximum size IPv4 packet filter can be 36 bytes. Therefore, 7 maximum size IPv4 type packet filters can fit into one TFT IE, i.e. if needed not all packet filter components can be defined into one message. A maximum size IPv6 packet filter can be 54 bytes. Therefore, only 4 maximum size IPv6 packet filters, plus the last packet filter which can contain max 38 octets can fit into one TFT IE. However, using "Add packet filters to existing TFT", it's possible to create a TFT data structure including 16 maximum size IPv4 or IPv6 filters. The traffic flow template information element is coded as shown in figure 10.5.144/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.162/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . NOTE 3: The 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] reuses the traffic flow template information element for the purpose of the traffic flow aggregate description, where the use of individual TFT parameters, e.g. the packet filter identifier in the parameter list, can differ from this specification. Figure 10.5.144/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Traffic flow template information element Figure 10.5.144a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Packet filter list when the TFT operation is "delete packet filters from existing TFT" (z=N+3) Figure 10.5.144b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Packet filter list when the TFT operation is "create new TFT", or "add packet filters to existing TFT" or "replace packet filters in existing TFT" Figure 10.5.144c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Parameters list Table 10.5.162/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Traffic flow template 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.6.12 |
3,375 | 7.2.1 Create Session Request | The direction of this message shall be from MME/S4-SGSN to SGW and from SGW to PGW, and from ePDG/TWAN to the PGW (see Table 6.1-1). The Create Session Request message shall be sent on the S11 interface by the MME to the SGW, and on the S5/S8 interface by the SGW to the PGW as part of the procedures: - E-UTRAN Initial Attach when a PDN connection needs to be established through the SGW and PGW - Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN with GTP on S5/S8 interface (see clauses 8.2, 8.6 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) - UE requested PDN connectivity when a PDN connection needs to be established through the SGW and PGW - Addition of a 3GPP access of NBIFOM procedure as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71] - Restoration of PDN connections after an PGW-C/SMF change as specified in 3GPP TS 23.007[ Restoration procedures ] [17] The message shall also be sent on S4 interface by the SGSN to the SGW, and on the S5/S8 interface by the SGW to the PGW as part of the procedures: - PDP Context Activation - Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN with GTP on S5/S8 interface (see clauses 8.2, 8.6 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) - Addition of a 3GPP access of the NBIFOM procedure as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71] The message shall also be sent on the S11 interface by the MME to the SGW as part of the procedures: - Tracking Area Update procedure with Serving GW change - S1/X2-based handover with SGW change - UTRAN Iu mode to E-UTRAN Inter RAT handover with SGW change - GERAN A/Gb mode to E-UTRAN Inter RAT handover with SGW change - 3G Gn/Gp SGSN to MME combined hard handover and SRNS relocation procedure - Gn/Gp SGSN to MME Tracking Area Update procedure - Restoration of PDN connections after an SGW failure if the MME and PGW support these procedures as specified in 3GPP TS 23.007[ Restoration procedures ] [17] - MME triggered Serving GW relocation - Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN with PMIP on S5/S8 interface (see clauses 8.2 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) and on the S4 interface by the SGSN to the SGW as part of the procedures: - Routing Area Update with MME interaction and with SGW change - Gn/Gp SGSN to S4 SGSN Routing Area Update - Inter SGSN Routeing Area Update Procedure and Combined Inter SGSN RA / LA Update using S4 with SGW change - Iu mode RA Update Procedure using S4 with SGW change - E-UTRAN to UTRAN Iu mode Inter RAT handover with SGW change - E-UTRAN to GERAN A/Gb mode Inter RAT handover with SGW change - Serving RNS relocation using S4 with SGW change - Combined hard handover and SRNS relocation using S4 with SGW change - Combined Cell / URA update and SRNS relocation using S4 with SGW change - Enhanced serving RNS relocation with SGW relocation - Restoration of PDN connections after an SGW failure if the SGSN and PGW support these procedures as specified in 3GPP TS 23.007[ Restoration procedures ] [17] - S4-SGSN triggered Serving GW relocation - Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN with PMIP on S5/S8 interface (see clauses 8.2 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) and on the S2b interface by the ePDG to the PGW as part of the procedures: - Initial Attach with GTP on S2b - UE initiated Connectivity to Additional PDN with GTP on S2b - Handover to Untrusted Non-3GPP IP Access with GTP on S2b (See clause 8.6 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) - Initial Attach for emergency session (GTP on S2b) - Addition of an access using S2b of NBIFOM procedure as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71] and on the S2a interface by the TWAN to the PGW as part of the procedure: - Initial Attach in WLAN on GTP S2a - Initial Attach in WLAN for Emergency Service on GTP S2a - UE initiated Connectivity to Additional PDN with GTP on S2a - Handover to TWAN with GTP on S2a (See clause 16.10 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) - Addition of an access using S2a of NBIFOM procedure as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71]. If the new Create Session Request received by the SGW collides with an existing active PDN connection context (the existing PDN connection context is identified with the tuple [IMSI, EPS Bearer ID], where IMSI shall be replaced by TAC and SNR part of ME Identity for emergency or RLOS attached UE without UICC or authenticated IMSI), this Create Session Request shall be treated as a request for a new session. Before creating the new session, the SGW should delete: - the existing PDN connection context locally, if the Create Session Request is received with the TEID set to zero in the header, or if it is received with a TEID not set to zero in the header and it collides with the default bearer of an existing PDN connection context; - the existing dedicated bearer context locally, if the Create Session Request collides with an existing dedicated bearer context and the message is received with a TEID not set to zero in the header. In the former case, if the PGW S5/S8 IP address for control plane received in the new Create Session Request is different from the PGW S5/S8 IP address for control plane of the existing PDN connection, the SGW should also delete the existing PDN connection in the corresponding PGW by sending a Delete Session Request message. NOTE 1: The SGW can send the Create Session Request and Delete Session Request over S5/S8 asynchronously, e.g. the SGW can send the Delete Session Request and then the Create Session Request without having to wait for the Delete Session Response. It does not matter if the PGW happens to receive the Delete Session Request after the Create Session Request since the PGW assigns a different S5/S8 F-TEID for control plane to the new PDN connection. In some network deployment, e.g. when 5G Network Slice is deployed and the combined PGW-C/SMFs are connected to the UDM, the PGW may select another PGW supporting the network slice for which the UE has subscription and then forward the Create Session Request to that PGW. When forwarding the Create Session Request message, the PGW shall forward the Create Session Request message as received from the SGW but with the following modifications: - the destination IP address of the message shall be set to the selected PGW IP address; - the CSRMFI flag shall be set to "1"; - the source IP address and UDP port of the message shall be set to the IP address and port of the forwarding PGW. NOTE 2: The Create Session Response message is sent back to the forwarding PGW that forwards it to the SGW. It is assumed that GTPv2/UDP/IP connectivity between the source PGW/SMF and the target PGW/SMF which are in different slices is allowed in such network deployment; otherwise, if there is no GTPv2/UDP/IP connectivity between the source PGW/SMF and the target PGW/SMF, or if the source PGW/SMF does not support forwarding the request to the target PGW/SMF, the source PGW/SMF can proceed as specified in clause 7.2.2. If the new Create Session Request received by the PGW collides with an existing PDN connection context (the existing PDN connection context is identified with the triplet [IMSI, EPS Bearer ID, Interface type], where applicable Interface type here is S2a TWAN GTP-C interface or S2b ePDG GTP-C interface or S5/S8 SGW GTP-C interface, and where IMSI shall be replaced by TAC and SNR part of ME Identity for emergency or RLOS attached UE without UICC or authenticated IMSI), this Create Session Request shall be treated as a request for a new session. Before creating the new session, the PGW should delete: - the existing PDN connection context, if the Create Session Request collides with the default bearer of an existing PDN connection context; - the existing dedicated bearer context, if the Create Session Request collides with a dedicated bearer of an existing PDN connection context. The PGW shall allocate a new PGW S5/S8 F-TEID for control plane to the new PDN connection, i.e. not the same F-TEID value as the one which was assigned to the existing PDN connection. NOTE 3: With GTP based S2a and S2b, the EPS Bearer IDs assigned for specific UE over S2a between the TWAN and PGW and over S2b between an ePDG and PGW are independent of the EPS Bearer IDs assigned for the same UE over S5/S8 and may overlap in value (see 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45] clause 4.6.2). NOTE 4: Only the TAC and SNR part of the ME Identity is used to identify an emergency or RLOS attached UE without UICC or authenticated IMSI. Table -1: Information Elements in a Create Session Request Table -2: Bearer Context to be created within Create Session Request Table -3: Bearer Context to be removed within Create Session Request Table -4: Overload Control Information within Create Session Request Table 7.2.1-5: Remote UE Context Connected within Create Session Request | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.2.1 |
3,376 | 4.3.7.2 Load balancing between MMEs | The MME Load Balancing functionality permits UEs that are entering into an MME Pool Area to be directed to an appropriate MME in a manner that achieves load balancing between MMEs. This is achieved by setting a Weight Factor for each MME, such that the probability of the eNodeB selecting an MME is proportional to its Weight Factor. The Weight Factor is typically set according to the capacity of an MME node relative to other MME nodes. The Weight Factor is sent from the MME to the eNodeB via S1-AP messages (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]). If a HeNB GW is deployed, the Weight Factor is sent from the MME to the HeNB GW. NOTE 1: An operator may decide to change the Weight Factor after the establishment of S1-MME connectivity as a result of changes in the MME capacities. E.g., a newly installed MME may be given a very much higher Weight Factor for an initial period of time making it faster to increase its load. NOTE 2: It is intended that the Weight Factor is NOT changed frequently. e.g. in a mature network, changes on a monthly basis could be anticipated, e.g. due to the addition of RAN or CN nodes. In some networks, the eNodeB may be configured to select specific MME for UEs configured for low access priority with a different load balance to that used for MME selection for other UEs. NOTE 3: The eNodeB can determine whether or not the "UE is configured for low access priority" from information received in the RRC establishment or RRC resume signalling. When DCNs are used, load balancing by eNodeB is only performed between MMEs that belong to the same DCN within the same MME pool area, i.e. MMEs with the same PLMN and MMEGI value. When an MME serves multiple DCNs and one DCN is supported by multiple MMEs, in order to achieve load balancing across the MMEs of the same MME pool area supporting the same DCN, each DCN supported by this MME may have its own Weight Factor (Weight Factor per DCN). The Weight Factor per DCN is set according to the capacity of an MME node for a specific DCN relative to other MME nodes' capacity for that DCN within the same MME pool area. The eNodeB is provided with per DCN Weight Factors, if any, by the connected MMEs at the set-up of the S1 connection. The DCN Load Balancing functionality permits UEs that are entering into a pool area or being re-directed to an appropriate DCN to be distributed in a manner that achieves load balancing between the CN nodes of the same DCN. The eNodeB may be configured to select MME(s) from a specific CN for UEs configured for low access priority only for the case that no other information and configuration is available for selecting an MME from a specific DCN. | 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.7.2 |
3,377 | 5.3.3.3 Routing Area Update with MME interaction and without S-GW change | The Routing Area Update without S-GW change procedure takes place when a UE that is registered with an MME selects a UTRAN or GERAN cell and the S-GW is not changed by the procedure. In this case, the UE changes to a Routing Area that the UE has not yet registered with the network. This procedure is initiated by an ECM-IDLE state UE and may also be initiated if the UE is in ECM-CONNECTED state. The RA update case is illustrated in Figure 5.3.3.3-1. NOTE 1: This procedure covers the MME to 2G or 3G SGSN RAU. Figure 5.3.3.3-1: Routing Area Update with MME interaction and without S-GW change NOTE 2: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 8 and 10 concern GTP based S5/S8. 1. The UE selects a UTRAN or GERAN cell. This cell is in a Routing Area that the UE not yet registered with the network, or the UE reselects a UTRAN or GERAN cell and the TIN indicates "GUTI". The UE in ECM-CONNECTED state may change to the GERAN cell through Network Assisted Cell Change (NACC). 2a. The UE sends a Routing Area Update Request (old P-TMSI, P-TMSI Type, old RAI, UE Core Network Capability, MS Network Capability, P-TMSI Signature, additional P-TMSI/RAI, KSI, Voice domain preference and UE's usage setting) message to the new SGSN. The UE shall set the P-TMSI Type to indicate whether the P-TMSI is a native P-TMSI or is mapped from a GUTI. If the UE's internal TIN indicates "GUTI" and the UE holds a valid GUTI then the UE indicates the GUTI as the old P-TMSI and old RAI. If the UE's TIN indicates "P-TMSI" or "RAT-related TMSI" and the UE holds a valid P-TMSI and related RAI then these two elements are indicated as old P-TMSI and old RAI. Mapping a GUTI to a P-TMSI and an RAI is specified in TS 23.003[ Numbering, addressing and identification ] [9]. If the UE holds a valid P-TMSI and related RAI and the old P-TMSI and old RAI indicate a P-TMSI/RAI mapped from a GUTI, then the UE indicates these parameters as additional P-TMSI/RAI. The old P-TMSI is indicated in the RAU Request message for Iu-mode only. For Gb mode the TLLI is derived from the value that is determined as the old P-TMSI according to the rules above. The routing parameter that is signalled in the RRC signalling to the RNC for routing to the SGSN is derived from the identifier that is signalled as the old P-TMSI according to the rules above. For a combined MME/SGSN the RAN is configured to route the NRI(s) of this combined node to the same combined node. The RAN is also configured to route NRI(s) of P-TMSIs that are generated by the UE's mapping of the GUTIs allocated by the combined node. Such a RAN configuration may also be used for separate nodes to avoid changing nodes in the pool caused by inter RAT mobility. If the UE has a follow-on request, i.e. if there is pending uplink traffic (signalling or data), the 3G SGSN may use, as an implementation option, the follow-on request indication to release or keep the Iu connection after the completion of the RA update procedure. KSI is mapped from an eKSI identifying a KASME if the UE indicates a P-TMSI mapped from GUTI in the information element "old P-TMSI". KSI identifies a (CK, IK) pair if the UE indicates a P-TMSI in the information element "old P-TMSI". The UE sets the voice domain preference and UE's usage setting according to its configuration, as described in clause 4.3.5.9. 2b. The RNC shall add the Routing Area Identity, CSG access mode, CSG ID before forwarding the message to the SGSN. This RA identity corresponds to the RAI in the MM system information sent by the RNC to the UE. The BSS shall add the Cell Global Identity (CGI) of the cell where the UE is located before passing the message to the new SGSN. CSG ID is provided by RAN if the UE sends the RAU Request message via a CSG cell or a hybrid cell. CSG access mode is provided if the UE sends the RAU Request message via a hybrid cell. If the CSG access mode is not provided but the CSG ID is provided, the SGSN shall consider the cell as a CSG cell. For SIPTO at the Local Network the with stand-alone GW architecture the RNC includes the Local Home Network ID in the Initial UE Message and in Direct Transfer message if the target cell is in a Local Home Network. 3. The new S4 SGSN determines the type of the old node, i.e. MME or SGSN, as specified in clause 4.3.19, uses the old RAI received from the UE to derive the old MME address, and sends a Context Request (P-TMSI, old RAI, New SGSN Address, P-TMSI Signature) message to the old MME to get the context for the UE. To validate the Context Request the old MME uses a NAS token mapped from the P-TMSI Signature. If the UE is not known in the old MME, the old MME responds with an appropriate error cause. If integrity check fails in the old MME, the old MME responds with an appropriate error cause which shall initiate the security functions in the new S4 SGSN. If the security functions authenticate the UE correctly, the new S4 SGSN shall send a Context Request (IMSI, old RAI, New SGSN Address, UE Validated) message to the old MME.UE Validated indicates that the new S4 SGSN has authenticated the UE. If the new S4 SGSN indicates that it has authenticated the UE or if the old MME authenticates the UE, the old MME starts a timer. If the UE with emergency bearers is not authenticated in the old MME (in a network supporting unauthenticated UEs) the old MME continues the procedure with sending a Context Response and starting the timer also when it cannot validate the Context Request. 4. The old MME responds with one Context Response (IMSI, ME Identity (if available), KSI, CK, IK, unused Authentication Quintets, EPS Bearer Contexts, Serving GW signalling Address and TEID(s), ISR Supported, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, UE Core Network Capability, UE Specific DRX Parameters, Change to Report (if present)) message. The PDN GW Address and TEID(s) (for GTP-based S5/S8) or GRE Keys (PMIP-based S5/S8) for uplink traffic and control plane, and the TI(s) is part of the EPS Bearer context(s). The unused Authentication Quintets in the MM Context may be sent if stored by the MME and the MME received the unused Authentication Quintets from the same SGSN previously. ISR Supported is indicated if the old MME and associated Serving GW are capable to activate ISR for the UE. If the UE receives emergency bearer services from the old MME and the UE is UICCless, IMSI can not be included in the Context Response. For emergency attached UEs, if the IMSI cannot be authenticated, then the IMSI shall be marked as unauthenticated. Also, in this case, security parameters are included only if available. The new S4 SGSN shall ignore the UE Core Network Capability contained in the Context Response only when it has previously received an UE Core Network Capability in the Routing Area Update Request. If UE is not known in the old MME, the old MME responds with an appropriate error cause. Change to Report flag is included by the old MME if reporting of change of UE Time Zone, or Serving Network, or both towards Serving GW / PDN GW was deferred by the old MME. The new SGSN maps the EPS bearers to PDP contexts 1-to-1 and maps the EPS Bearer QoS parameter values of an EPS bearer to the Release 99 QoS parameter values of a PDP context as defined in Annex E. The PDP context(s) are established in the indicated order. The SGSN deactivates the PDP contexts which cannot be established. If SIPTO at the Local Network is active for a PDN connection in the architecture with stand-alone GW, the old MME shall include the Local Home Network ID of the old cell in the EPS Bearer context corresponding to the SIPTO at the Local Network PDN connection. For UE using CIoT EPS Optimisation without any activated PDN connection, there is no EPS Bearer Context(s) included in the Context Response message. The old MME only transfers the EPS Bearer Context(s) that the new SGSN supports. If not supported, EPS Bearer Context(s) of non-IP PDN connection are not transferred to the new SGSN. EPS Bearer Context(s) of Ethernet PDN connection type are not transferred to the new SGSN. If the EPS Bearer Context(s) of a PDN connection has not been transferred, the old MME shall consider all bearers of that PDN connection as failed and release that PDN connection by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3. 5. Security functions may be executed. Procedures are defined in clause 5.3.10 on "Security Function". If the new SGSN is configured to allow emergency bearer services for unauthenticated UE the new SGSN behave as follows: - where a UE has only emergency bearer services, the SGSN either skip the authentication and security procedure or accepts that the authentication may fail and continues the Routing Area Update procedure; or - where a UE has both emergency and non-emergency bearer services and authentication fails, the SGSN continues the Routing Area Update procedure and deactivates all the non-emergency PDP contexts as specified in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. 6. The new S4 SGSN sends a Context Acknowledge (ISR Activated) message to the old MME. Unless ISR is indicated by the new S4 SGSN, the old MME marks in its context that the information in the GWs is invalid. This ensures that the old MME updates the GW if the UE initiates a TAU procedure back to the old MME before completing the ongoing RAU procedure. NOTE 3: Updating the GWs refers to modification of session(s) on the Serving GW. This will result in successful re-establishment of the S11/S4 tunnel between the MME/SGSN and the Serving GW. ISR Activated indicates to the old MME that it shall maintain the UE's contexts and the MME stops the timer started in step 3. In this case, if the Implicit Detach timer is running, the old MME shall re-start it with a slightly larger value than the UE's E-UTRAN Deactivate ISR timer. When ISR Activated is not indicated and this timer expires the old MME deletes all bearer resources of that UE. As the Context Acknowledge from the new S4 SGSN does not include any S-GW change the old MME does not send any Delete Session Request message to the S-GW. The SGSN shall not activate ISR if the associated Serving GW does not support ISR. If the security functions do not authenticate the UE correctly, then the RAU is rejected, and the new S4 SGSN sends a reject indication to the old MME. The old MME shall continue as if the Identification and Context Request was never received. For UE using CIoT EPS Optimisation without any activated PDN connection, the steps 7, 8, 9, 10, and 11 are skipped. If the new SGSN identifies that the RAT type has changed, the SGSN checks the subscription information to identify for each APN whether to maintain the PDN connection, disconnect the PDN connection with a reactivation request or disconnect PDN connection without reactivation request. If the SGSN decides to deactive a PDN connection it performs SGSN-initiated PDN Connection Deactivation procedure after tracking area procedure is completed. Existing SM cause values as specified in TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [47] (e.g. #39, "reactivation requested"; #66 "Requested APN not supported in current RAT and PLMN combination"; and for a dedicated bearer, possibly #37 "QoS not accepted") are used to cause predictable UE behaviour. 7. In this procedure flow the Serving GW is not relocated. The SGSN sends a Modify Bearer Request (new SGSN Address and TEID, RAT type, ISR Activated) message per PDN connection to the Serving GW. If indicated, the information ISR Activated indicates that ISR is activated. As it is a mobility from E-UTRAN, if the target SGSN supports location information change reporting, the target SGSN shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If the PDN GW requested User CSG information, the SGSN also includes the User CSG information IE in this message. If either the UE Time Zone has changed, or Context Response message from old MME indicated pending UE Time Zone change reporting (via Change to Report flag), the SGSN includes the UE Time Zone IE in this message. If either the Serving Network has changed, or Context Response message from old MME indicated pending Serving Network change reporting (via Change to Report flag) the SGSN includes the new Serving Network IE in this message. In network sharing scenarios Serving Network denotes the serving core network. When the Modify Bearer Request does not indicate ISR Activated the S-GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the S-GW reserved. RAT type indicates a change in radio access. If ISR Activated is indicated or SGSN and SGW are configured to release S4 U-Plane when EPS Bearer Contexts associated with the released RABs are to be preserved, the SGSN does not send SGSN address and TEID for U-Plane in Modify Bearer Request. NOTE 4: The User CSG Information IE is not sent in step 7 if the "follow-on request indication" indicates releasing the Iu connection after the completion of the RA update procedure. 8. If the RAT type has changed or the Serving GW has received the User Location Information IE and/or the UE Time Zone IE and/or User CSG information IE and/or the Serving Network IE from the MME in step 7 the Serving GW informs the PDN GW(s) about the change of this information that e.g. can be used for charging, by sending the message Modify Bearer Request (RAT type) per PDN connection to the PDN GW(s) concerned. User Location Information IE and/or UE Time Zone IE and/or User CSG information IE and/or Serving Network IE are also included if they are present in step 7. 9. If dynamic PCC is deployed, and RAT type information or UE location information needs to be conveyed from the PDN GW to the PCRF, then the PDN GW shall send this information to the PCRF by means of an IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6]. NOTE 5: The PDN GW does not need to wait for the PCRF response, but continues in the next step. If the PCRF response leads to an EPS bearer modification the PDN GW should initiate a bearer update procedure. 10. The PDN GW updates its context field and returns a Modify Bearer Response (MSISDN) message to the Serving GW. MSISDN is included if the PDN GW has it stored in its UE context. If location information change reporting is required and supported in the target SGSN, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response. 11. The Serving GW updates its context fields. If ISR Activated is indicated in step 7 and RAT Type received in step 7 indicates UTRAN or GERAN, then the Serving GW only updates the SGSN Control Plane Address and keeps the MME related information unchanged. Otherwise the Serving GW shall update all of the information stored locally for this UE with the related information received from the SGSN. Then the Serving GW returns a Modify Bearer Response (Serving GW address and TEID for uplink traffic, MS Info Change Reporting Action) message. When the SGSN receives the Modify Bearer Response message, the SGSN checks if there is a "Availability after DDN Failure" monitoring event or a "UE Reachability" monitoring event configured for the UE in the SGSN and in such a case sends an event notification (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] for further information). 12. The new SGSN verifies whether it holds subscription data for the UE identified by the P-TMSI, the additional PTMSI/RAI or by the IMSI received with the context data from the old CN node. The additional P-TMSI/RAI allows the new SGSN to find any already existing UE context stored in the new SGSN. If there are no subscription data in the new SGSN for this UE, or for some network sharing scenario (e.g. GWCN) if the PLMN-ID of the RAI supplied by the RNC is different from that of the RAI in the UE's context, then the new SGSN informs the HSS of the change of the SGSN by sending an Update Location (SGSN Number, SGSN Address, IMSI, Homogenous Support of IMS Voice over PS Sessions, UE SRVCC capability, equivalent PLMN list) message to the HSS. For "Homogenous Support of IMS Voice over PS Sessions", see clause 5.3.8A of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. The inclusion of the equivalent PLMN list indicates that the SGSN supports the inter-PLMN handover to a CSG cell in an equivalent PLMN using the subscription information of the target PLMN. If the UE initiates the RAU procedure in a VPLMN supporting Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN (via Service Level Agreement) and the SGSN needs to retrieve the CSG subscription information of the UE from the CSS, the SGSN initiates the Update CSG Location Procedure with CSS as described in clause 5.3.12. 13. The HSS sends a Cancel Location (IMSI, Cancellation Type) message to the old SGSN with the Cancellation Type set to Update Procedure. When receiving the Cancel Location message the old SGSN removes all the UE contexts. The old SGSN acknowledges with a Cancel Location Ack (IMSI) message. 14. When receiving the Context Acknowledge message from the new SGSN and if the old MME has an S1-MME association for the UE, the source MME sends a S1-U Release Command to the source eNodeB after the timer started in step 3 has expired. The RRC connection is released by the source eNodeB. The source eNodeB confirms the release of the RRC connection and of the S1-U connection by sending a S1-U Release Complete message to the source MME. 15. The HSS acknowledges the Update Location message by sending an Update Location Ack (IMSI, Subscription Data) to the new SGSN. The Subscription Data may contain the CSG subscription data for the registered PLMN and for the equivalent PLMN list requested by SGSN in step 12. If the UE initiates the RAU procedure at a CSG cell, the new S4 SGSN shall check whether the CSG ID and associated PLMN is contained in the CSG subscription and is not expired. If the CSG ID and associated PLMN is not present or expired, the S4 SGSN shall send a RAU reject message to the UE with an appropriate cause value. The UE shall remove the CSG ID and associated PLMN from its Allowed CSG list if present. If the Update Location is rejected by the HSS, the new SGSN rejects the RAU Request from the UE with an appropriate cause sent in the RAU Reject message to the UE. In such cases, the new SGSN releases any local SGSN EPS Bearer contexts for this particular UE. 16. Void. 17. Void. 18. If due to regional subscription restrictions or access restrictions (e.g. CSG restrictions) the UE is not allowed to access the RA: - For UEs with ongoing emergency bearer services, the new SGSN accept the Routing Area Update Request and deactivates the non-emergency PDP contexts as specified in clause 9.2.4.2 in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. If the Routing Area Update procedure is initiated in PMM-IDLE/STANDBY state, all non-emergency PDP Contexts are deactivated by the Routing Area without PDP Context deactivation signalling between the UE and the SGSN - For all other cases, the new SGSN rejects Routing Area Update Request with an appropriate cause to the UE and notifies the HSS of rejection (details of this notification is covered in stage 3). The new SGSN responds to the UE with a Routing Area Update Accept (P-TMSI, P-TMSI signature, ISR Activated, Emergency Service Support indicator, PDP context status) message to the UE. P-TMSI is included if the SGSN allocates a new P-TMSI. The Emergency Service Support indicator informs the UE that Emergency bearer services are supported over UTRAN. If ISR Activated is indicated to the UE, its GUTI and list of TAs shall remain registered with the network and shall remain valid in the UE. When receiving the RAU Accept message and there is no ISR Activated indication the UE shall set its TIN to "P-TMSI". When ISR Activated is indicated and the UE's TIN indicates "P-TMSI" the TIN shall not be changed. When ISR Activated is indicated and the UE's TIN indicates "GUTI" or "RAT-related TMSI" the UE shall set its TIN to "RAT-related TMSI". If an SGSN change ISR is not activated by the new SGSN to avoid context transfer procedures with two old CN nodes. If the RAU procedure is initiated by manual CSG selection and occurs via a CSG cell, the UE upon receiving the RAU Accept shall add the CSG ID and associated PLMN to its Allowed CSG list if it is not already present. Manual CSG selection is not supported if the UE has emergency bearers established. In Iu mode, if after step 7 the new SGSN receives a Downlink Data Notification message or any other downlink signalling message while the UE is still connected, the new SGSN may prolong the PS signalling connection with the UE. If there is DL data buffered for a UE using power saving functions (i.e. the DL Data Buffer Expiration Time in the MM context for the UE in the SGSN has not expired), the user plane setup is performed in conjunction with the RAU Accept message. With the PDP context status information, the UE shall deactivate all those bearers contexts locally which are active in the UE, but are indicated by the SGSN as being inactive. If the user plane setup is performed in conjunction with the RAU Accept message and the RAU is performed via a hybrid cell, then the SGSN shall send an indication whether the UE is a CSG member to the RAN along with the RANAP message. Based on this information, the RAN may perform differentiated treatment for CSG and non-CSG members. NOTE 6: If the UE receives a RAU Accept message via a hybrid cell, the UE does not add the corresponding CSG ID and associated PLMN to its Allowed CSG list. Adding a CSG ID and associated PLMN to the UE's local Allowed CSG list for a hybrid cell is performed only by OTA or OMA DM procedures. 19. If P-TMSI was included in the Routing Area Update Accept message, the UE acknowledges the new P-TMSI by returning a Routing Area Update Complete message to the SGSN. 20. For Iu-mode, if the UE has uplink data or signalling pending it shall send a Service Request (P-TMSI, CKSN, Service Type) message to the new SGSN. If a P-TMSI was allocated in step 18, that P-TMSI is the one included in this message. Service Type specifies the requested service. Service Type shall indicate one of the following: Data or Signalling. 21. If the UE has sent the Service Request, the new 3G SGSN requests the RNC to establish a radio access bearer by sending a RAB Assignment Request (RAB ID(s), QoS Profile(s), GTP SNDs, GTP SNUs, PDCP SNUs) message to the RNC. If Direct Tunnel is established the SGSN provides to the RNC the Serving GW's Address for User Plane and TEID for uplink data. 22. If the SGSN established Direct Tunnel in step 21) it shall send Modify Bearer Request per PDN connection to the Serving GW and include the RNC's Address for User Plane and downlink TEID for data. The Serving GW updates the Address for User Plane and TEID for downlink data and return a Modify Bearer Response. NOTE 7: EPS does not support any CAMEL procedures. NOTE 8: The new SGSN may initiate RAB establishment after execution of the security functions (step 5), or wait until completion of the RA update procedure. For the MS, RAB establishment may occur any time after the RA update request is sent (step 2). In the case of a rejected routing area update operation, due to regional subscription, roaming restrictions or access restrictions (see TS 23.221[ Architectural requirements ] [27] and TS 23.008[ Organization of subscriber data ] [28]) the new SGSN should not construct an MM context. In the case of receiving the subscriber data from HSS, the new SGSN may construct an MM context and store the subscriber data for the UE to optimise signalling between the SGSN and the HSS. A reject shall be returned to the UE with an appropriate cause and the PS signalling connection shall be released. Upon return to idle, the UE shall act according to TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. If the network supports the MOCN configuration for network sharing, the SGSN may, if the UE is not a 'Network Sharing Supporting MS', in this case decide to initiate redirection by sending a Reroute Command to the RNS, as described in TS 23.251[ Network sharing; Architecture and functional description ] [24] instead of rejecting the routing area update. If the new SGSN is unable to update the bearer context in one or more P-GWs, the new SGSN shall deactivate the corresponding bearer contexts as described in clause "SGSN-initiated PDP Context Deactivation Procedure" of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. This shall not cause the SGSN to reject the routing area update. The new SGSN shall determine the Maximum APN restriction based on the received APN Restriction of each bearer context in the Context Response message and then store the new Maximum APN restriction value. The PDP contexts shall be prioritized by the new SGSN. If the new SGSN is unable to support the same number of active PDP contexts as received from the old MME, the prioritisation is used to decide which PDP contexts to maintain active and which ones to delete. In any case, the new SGSN shall first update all PDP contexts in one or more P-GWs and then deactivate the PDP context(s) that it cannot maintain as described in clause "SGSN-initiated PDP Context Deactivation Procedure" of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. This shall not cause the SGSN to reject the routing area update. NOTE 9: If the UE was in PMM-CONNECTED state the bearer contexts are sent already in the Forward Relocation Request message as described in clause "Serving RNS relocation procedures" of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. If the routing area update procedure fails a maximum allowable number of times, or if the SGSN returns a Routing Area Update Reject (Cause) message, the UE shall enter PMM DETACHED state. | 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.3.3 |
3,378 | 4.15.4.5.4 Information flow for subscription via SMF to UPF event exposure service related with AOI | Figure 4.15.4.5.4-1: Subscription to UPF event exposure service for AOI via SMF If the subscription is related to AOI, the UPF event consumer (e.g. NWDAF) firstly get the UE list which includes the UE(s) located in the AOI from the AMF(s), then subscribe to UPF via SMF as described in clause 4.15.4.5.2. If the UPF event consumer (e.g. NWDAF) further needs to filter certain UE(s) out from the UE list get from the AMF(s), the UPF event consumer (e.g. NWDAF) locally decides the final UE list. 1. The UPF event consumer (e.g. NWDAF) determines the AMF(s) based on the AOI, i.e. TAIs and possibly on the target S-NSSAI and obtains the UE list which includes the UE(s) located in the AoI from AMF(s) by invoking Namf_EventExposure_Subscribe service operation to get the presence of UE(s) and moving in or out status in Area of Interest as described in clause 5.2.2.3 and in clause 5.3.4.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The target of Namf_EventExposure_Subscribe depends on whether the UPF event consumer (e.g. NWDAF) targets one UE a group of UE or Any UE. 2. The UPF event consumer (e.g. NWDAF) locally computes the final UE list by comparing the UE list from AMF(s) and its own target UE list if it exists. 3. For each UE in the final UE list, the UPF event consumer (e.g. NWDAF) issues a subscription to UPF event exposure service via the SMF serving the UE (Nsmf_EventExposure Subscription) to get UPF data as described in clause 4.15.4.5.2. When an AMF reports a change of the list of UE(s) in the AoI (Namf_EventExposure_Notify), the UPF event consumer (e.g. NWDAF) may need to cancel the Nsmf_EventExposure Subscription or to issue a new Nsmf_EventExposure Subscription. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.4.5.4 |
3,379 | 4.3.2.1.3 Number of outgoing unnecessary handovers related with inter-RAT MRO | This measurement provides the number of outgoing unnecessary handovers to another RAT from E-UTRAN related with inter-RAT MRO. CC The measurement is obtained by accumulating the number of outgoing unnecessary handovers to anther RAT from E-UTRAN according to the definitions in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [12] and TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. A single integer value. HO.IratOutUnnecessaryFromEutran GSMRelation UTRANRelation CDMA2000Relation Valid for packet switched traffic EPS This measurement is to support the PM for inter-RAT MRO defined in TS 32.522[ Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) ] [15]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.2.1.3 |
3,380 | 10.2.1 Authenticated IMS Emergency Sessions 10.2.1.1 General | Authenticated emergency services are provided to UEs in the following scenarios: a) A UE in RM-DEREGISTERED state requests IMS Emergency services In this scenario, the UE has a valid subscription and is authenticated when it registers with the network. b) A UE in RM-REGISTERED state initiates a PDU Session request to setup an IMS Emergency Session In this scenario, the UE is already registered with the network and share a security context with the AMF. The UE initiates a session management message to setup a new bearer for emergency services. The request for emergency services is sent protected by the current security context. The AMF may decide to re-authenticate the UE. If there is a redirection of the UE to EUTRAN for IMS Emergency services, the redirect command from the gNB to the UE shall be protected by the UE’s AS security context. The AMF shall send the ‘NG AP UE Initial Context setup’ message to enable the AS security context set up. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 10.2.1 |
3,381 | 16.12.5.3 RRC Connection Re-establishment | The L2 U2N Remote UE may perform the following actions during the RRC connection re-establishment procedure: - If only suitable cell(s) are available, the L2 U2N Remote UE initiates RRC re-establishment procedure towards a suitable cell; - If only suitable L2 U2N Relay UE(s) are available, the L2 U2N Remote UE initiates RRC re-establishment procedure towards a suitable relay UE's serving cell via selected suitable L2 U2N Relay; - If both a suitable cell and a suitable relay are available, the L2 U2N Remote UE can select either one to initiate RRC re-establishment procedure based on implementation. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.5.3 |
3,382 | 5.6.13 Always-on PDU session | An always-on PDU Session is a PDU Session for which User Plane resources have to be activated during every transition from CM-IDLE mode to CM-CONNECTED state. Based on an indication from upper layers, a UE may request to establish a PDU Session as an always-on PDU Session. The SMF decides whether the PDU Session can be established as an always-on PDU Session. In Home Routed roaming case, based on local policies, the V-SMF shall be involved to determine whether the PDU Session can be established as an always-on PDU Session. If the UE requests the 5GC to modify a PDU Session, which was established in EPS, to an always-on PDU Session after the first inter-system change from EPS to 5GS, the SMF decides whether the PDU Session can be established as an always-on PDU Session based on the procedure described above. The UE shall request activation of User Plane resources for always-on PDU Sessions even if there are no pending uplink data for this PDU Session or when the Service Request is triggered for signalling only or when the Service Request is triggered for paging response only. If the UE has one or more established PDU Sessions which are not accepted by the network as always-on PDU Sessions and the UE has no uplink user data pending to be sent for those PDU Sessions, the UE shall not request for activating User Plane resources for those PDU sessions. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.13 |
3,383 | 5.28.2 5GS Bridge configuration for TSN | The configuration information of 5GS Bridge as defined in clause 8.6.8.4 of IEEE Std 802.1Q [98], includes the following: - Bridge ID of 5GS Bridge. - Configuration information of scheduled traffic on ports of DS-TT and NW-TT: - Egress ports of 5GS Bridge, e.g. ports on DS-TT and NW-TT; - Traffic classes and their priorities. NOTE 1: In this Release of the specification, scheduled traffic (clause 8.6.8.4 in IEEE Std 802.1Q [98]) is only supported with protected windows, (see clause Q.2 in IEEE Std 802.1Q [98]), therefore, it is enough to support AdminControlList, AdminBaseTime, AdminCycleTime and TickGranularity for the configuration of the 5GS. The configuration information of 5GS Bridge as defined in IEEE Std 802.1Q [98], includes the following: - Chassis ID of 5GS Bridge; - Traffic forwarding information as defined in clause 8.8.1 of IEEE Std 802.1Q [98]: - Destination MAC address and VLAN ID of TSN stream; - Port number in the Port MAP as defined in clause 8.8.1 of IEEE Std 802.1Q [98]. - Configuration information per stream according to clause 8.6.5.1 of IEEE Std 802.1Q [98] including: - Stream filters. - Stream gates. NOTE 2: In order to support clause 8.6.5.2.1 of IEEE Std 802.1Q [98], it is required to support the Stream Identification function as specified by IEEE Std 802.1CB [83]. The SMF report the MAC address of the DS-TT port of the related PDU Session to TSN AF via PCF. The association between the DS-TT MAC address, 5GS Bridge ID and port number on DS-TT is maintained at TSN AF and further used to assist to bind the TSN traffic with the UE's PDU session. Two models are supported to configure 5GS QoS for TSN traffic: - Based on the assumption that PSFP information is always provided by CNC: In this case the QoS Flows are setup based on the PSFP information provided by CNC; NOTE 3: PSFP information may be provided by CNC if TSN AF has declared PSFP support to CNC. TSN AF indicates the support for PSFP to CNC only if each DS-TT and NW-TT of the 5GS bridge has indicated support of PSFP. - Without requiring PSFP information provided by the CNC.: In this case, pre-configured QoS Flows are used and configured e.g. during PDU session establishment as described in clause 5.28.4. Additional QoS Flows are setup as necessary based on the PSFP, if available, as described in this clause. When PSFP information is available, TSN AF identifies the ingress and egress port for the TSN stream as described in Annex I and determines the DS-TT port MAC address(es) identifying the corresponding PDU session(s) carrying the TSN stream. Flow direction of a TSN stream is determined as follows: if the ingress port is a DS-TT port, then the Flow direction is UL; otherwise if the ingress port(s) is (are) NW-TT port, the Flow direction is DL. Flow direction is part of the TSCAI as defined in clause 5.27.2. The TSN AF uses the stream filter instances of PSFP information to derive the service data flow for TSN streams. The TSN AF uses the Priority values in the stream filter instances in PSFP information (if available) as defined in clause 8.6.5.2.1 of IEEE Std 802.1Q [98], the 5GS bridge delay information (see clause 5.27.5) and may additionally use scheduled traffic information as defined in clause 8.6.8.4 of IEEE Std 802.1Q [98], to derive the TSN QoS information (i.e. priority and delay) for a given TSN stream or flow of aggregated TSN streams as specified in clause 5.28.4. The TSN AF identifies the egress port(s) for the TSN stream using local configuration or static filtering entry that matches the TSN stream. If the TSN AF determines that the TSN stream is for UE-UE communication (i.e. ingress and egress ports are in DS-TTs), the TSN AF divides the stream into one uplink stream and one or more downlink streams and provides the streams on AF Session basis to the PCF(s). The SMF applies local switching as specified in clause 5.8.2.13 or clause 5.8.2.5.3 in order to enable UPF locally forward uplink stream from one PDU session as downlink stream in another PDU session. When CNC configures the PSFP information to the TSN AF, TSN AF determines the TSC Assistance Container as described in clause 5.27.2. The TSN AF associates the TSN QoS information and TSC Assistance Container (if available) with the corresponding service data flow description and provides to the PCF and the SMF as defined in clause 6.1.3.23 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE 4: When the TSN stream priority information from PSFP is not available (priority value in stream filters is set to wild card), in certain configurations it can be possible to use the scheduled traffic information as defined in clause 8.6.8.4 of IEEE Std 802.1Q [98] to derive the Priority of the TSN stream. For example, when there is a single downlink stream for a given DS-TT port, it can be possible to determine the affected DS-TT port in the downlink and the associated TSN stream priority based on the scheduled traffic information of the affected egress port, and to derive an estimated MDBV based on the gate open interval and the assumed ingress port bitrate. If TSN AF provides PSFP and/or scheduled traffic information to DS-TT and NW-TT then DS-TT and NW-TT execute on this information relative to the time base of the TSN GM clock (identified by the TSN time domain number received in PMIC). NOTE 5: Configuration of TSN time domain number via PMIC is optional for NW-TT. NW-TT can instead be pre-configured with the single time domain that is used by the CNC for bridge configuration and reporting. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.28.2 |
3,384 | 5.3.11 Handling of S-NSSAI based congestion control | The AMF may detect and start performing S-NSSAI based congestion control when one or more S-NSSAI 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 AMF uses the selected DNN or the DNN associated with the PDU session corresponding to the 5GSM procedure. If the UE does not provide an S-NSSAI for a non-emergency PDU session, then the AMF uses the selected S-NSSAI or the S-NSSAI associated with the PDU session corresponding to the 5GSM procedure. The AMF may detect and start performing S-NSSAI based congestion control when the UE that does not support S-NSSAI location validity information requests a PDU session establishment for an S-NSSAI limited by NS-AoS and the UE is not in the NS-AoS. When S-NSSAI based congestion control is activated at the AMF, the AMF performs the congestion control as specified in subclause 5.4.5 and the UE performs the congestion control as specified in subclause 5.4.5 and subclause 6.2.8. | 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.11 |
3,385 | 4.3.7.5 PDN GW control of overload | The PDN GW may provide mechanisms for avoiding and handling overload situations. These include the rejection of PDN connection requests from UEs. The PDN GW may detect APN congestion and start and stop performing overload control based on criteria such as: - Maximum number of active bearers per APN; and/or - Maximum rate of bearer activations per APN. When performing overload control the PDN GW rejects PDN connection requests. When receiving the rejection from the PDN GW, the MME rejects the UE's PDN connection request as specified in clause 4.3.7.4.2. In addition the PDN GW may indicate a "PDN GW back-off time" for a specific APN to the MME. The MME should reject PDN connection requests, for the specific APN related to that PDN GW during the "PDN GW back-off time", by the means specified in clause 4.3.7.4.2. If a PDN GW indicates APN congestion by the "PDN GW back-off time" the MME may select another PDN GW of that APN instead of rejecting PDN connection requests unless there is already an existing PDN connection to the same APN for the UE, in which case, the MME shall reject PDN connection request. | 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.7.5 |
3,386 | 6.6.3.2 Remote UE Report initiated by the UE | The UE initiates the Remote UE Report procedure by sending a REMOTE UE REPORT message to the network, starting timer T3493 and entering the state PROCEDURE TRANSACTION PENDING (see example in figure 6.6.3.2.1). The UE shall include information of newly connected or disconnected remote UEs to the network in the REMOTE UE REPORT message. If any encrypted IMSI remote UE identity is included in the REMOTE UE REPORT message, the UE shall include the corresponding ProSe Key Management Function address. The UE shall include the default EPS bearer identity of the PDN connection associated with the remote UE connected to the ProSe UE-to-network relay or disconnected from the ProSe UE-to-network relay. If the UE allocated an IPv4 address to a remote UE and enabled UDP usage to the remote UE, the UE shall include in the REMOTE UE REPORT message the UDP port range assigned to the remote UE in the NAT function of ProSe layer-3 UE-to-network relay. If the UE allocated an IPv4 address to a remote UE and enabled TCP usage to the remote UE, the UE shall include in the REMOTE UE REPORT message the TCP port range assigned to the remote UE in the NAT function of ProSe layer-3 UE-to-network relay. NOTE: Encrypted IMSI remote UE identities corresponding to different ProSe Key Management Function addresses need to be reported using separate REMOTE UE REPORT messages. Figure 6.6.3.2.1: Remote UE Report procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.6.3.2 |
3,387 | M.3.2 Authentication and Authorization of IAB-node (Phase-1) | The IAB-UE function shall behave as a UE, and shall reuse the UE procedures specified in this document for the primary authentication (see clause 6), key derivation and distribution scheme, subscription credential(s) storage requirements, NAS security and AS security. NOTE 1: For isolated deployment scenarios, Annex B describes how additional EAP methods can be used. NOTE 2: Storage of subscription credentials for EAP AKA’ and 5G AKA is described in clause 6 of the present document. Authorization of IAB-nodes shall be performed by the 5G core network supporting IAB architecture as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | M.3.2 |
3,388 | 5.17.2.3 Interworking Procedures without N26 interface 5.17.2.3.1 General | For interworking without the N26 interface, IP address preservation is provided to the UEs on inter-system mobility by storing and fetching SMF+PGW-C and corresponding APN/DNN information via the HSS+UDM. In such networks AMF also provides an indication that interworking without N26 is supported to UEs during Initial Registration in 5GC or MME may optionally provide an indication that interworking without N26 is supported in the Attach procedure in EPC as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3] and TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. The UE provides an indication that it supports Request Type flag "handover" for PDN connectivity request during the attach procedure as described in clause 5.3.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26] and during initial Registration and Mobility Registration Update in 5GC. NOTE 1: The UE support of Request Type flag "handover" for PDN connectivity request during the attach procedure is needed for IP address preservation in the case of interworking without N26. The indication that interworking without N26 is valid for the entire Registered PLMN and for PLMNs equivalent to the Registered PLMN that are available in the Registration Area. The same indication is provided to all UEs served by the same PLMN. UEs that operate in interworking without N26 may use this indication to decide whether to register early in the target system. UEs that only support single registration mode may use this indication as described in clause 5.17.2.3.2. UE that support dual registration mode uses this indication as described in clause 5.17.2.3.3. Interworking procedures without N26 interface use the following two features: 1. When UE performs Initial Attach in EPC (with or without "Handover" indication in PDN CONNECTIVITY Request message) and indicates that it is moving from 5GC, the MME indicates to the HSS+UDM not to cancel the registration of AMF, if any. 2. When UE performs Initial Registration in 5GC and indicates that it is moving from EPC, the AMF indicates to the HSS+UDM not to cancel the registration of MME, if any. To support mobility both for single and dual registration mode UEs, the following also are supported by the network: 3. When PDU Session are created in 5GC, the SMF+PGW-C which supports EPS interworking stores the SMF+PGW-C FQDN along with DNN in the HSS+UDM. 4. The HSS+UDM provides the information about dynamically allocated SMF+PGW-C and APN/DNN information to the target CN network. If there are multiple SMF+PGW-C serving the UE for the same DNN which support EPS interworking in 5GS, the HSS+UDM select one of them according to operator's policy and provides together with the associated APN to the MME. 5. When PDN connections are created in EPC, the MME stores the SMF+PGW-C and APN information in the HSS+UDM. NOTE 2: Items 3, 4 and 5 are also supported in networks that support interworking with N26 procedures. This enables a VPLMN that does not deploy N26 interface to provide IP address preservation to roamed-in single-registration mode UEs from a HPLMN that only supports interworking with N26 procedures. When the network serving the UE supports 5GS-EPS interworking procedures without N26 interface, the SMF shall not provide the UEs with mapped target system parameters of the target system when UE is in the source network. A UE that operates in dual registration mode ignores any received mapped target system parameters (e.g. QoS parameters, bearer IDs/QFI, PDU Session ID, etc.). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.2.3 |
3,389 | 16.10.6.1 Session Management | For delivery of location dependent contents of a broadcast session, Area Session ID is included in the NGAP broadcast session resource setup procedure associated with MBS service area information and per Area Session ID NG-U tunnels are established. The 5GC may also provide information to the NG-RAN node whether the broadcast session is intended to be received by RedCap UEs only, non-RedCap UEs only or both non-RedCap and RedCap UEs. The NG-RAN may take this into account when configuring MBS session resources. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.6.1 |
3,390 | 5.31.7.3 MICO mode with Extended Connected Time | When a UE, using MICO mode, initiates MO signalling or MO data and the AMF is aware of pending or expected MT traffic, the AMF may keep the UE in CM-CONNECTED state and the RAN may keep the UE in RRC_CONNECTED state for an Extended Connected Time period in order to ensure the downlink data and/or signalling is delivered to the UE. The Extended Connected Time is determined by the AMF and is based on local configuration and/or the Maximum Response Time, if provided by the UDM. The AMF maintains the N2 connection for at least the Extended Connected Time and provides the Extended Connected Time value to the RAN. The Extended Connected Time value indicates the minimum time the RAN should keep the UE in RRC_CONNECTED state regardless of inactivity. The Extended Connected Time value is provided to the RAN together with the - NAS Registration Accept message; or - NAS Service Accept message. At inter-RAN node handovers, if some signalling or data are still pending, the target AMF may send the Extended Connected Time value to the target RAN node. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.7.3 |
3,391 | 6.20.1 Description | The 3GPP system is expected to support various enhanced V2X scenarios. Vehicles Platooning enables the vehicles to dynamically form a group travelling together. All the vehicles in the platoon receive periodic data from the leading vehicle, in order to carry on platoon operations. This information allows the distance between vehicles to become extremely small, i.e. the gap distance translated to time can be very low (sub second). Platooning applications can allow the vehicles following to be autonomously driven. Advanced Driving enables semi-automated or fully-automated driving. Longer inter-vehicle distance is assumed. Each vehicle and/or RSU shares data obtained from its local sensors with vehicles in proximity, thus allowing vehicles to coordinate their trajectories or manoeuvres. In addition, each vehicle shares its driving intention with vehicles in proximity. The benefits of this use case group are safer traveling, collision avoidance, and improved traffic efficiency. Extended Sensors enables the exchange of raw or processed data gathered through local sensors or live video data among vehicles, Road Site Units, UEs of pedestrians and V2X application servers. The vehicles can enhance the perception of their environment beyond what their own sensors can detect and have a more holistic view of the local situation. Remote Driving enables a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive themselves or a remote vehicle located in dangerous environments. For a case where variation is limited and routes are predictable, such as public transportation, driving based on cloud computing can be used. In addition, access to cloud-based back-end service platform can be considered for this use case group. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.20.1 |
3,392 | 5.1.2.1 UE - P-GW user plane with E-UTRAN | Legend: - GPRS Tunnelling Protocol for the user plane (GTP-U): This protocol tunnels user data between eNodeB 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]). - MME controls the user plane tunnel establishment and establishes User Plane Bearers between eNodeB and S-GW. - UDP/IP: These are the backbone network protocols used for routing user data and control signalling. - LTE-Uu: The radio protocols of E-UTRAN between the UE and the eNodeB are specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. Figure 5.1.2.1-1: User Plane | 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.1 |
3,393 | 4.25.7 SMF Initiated SMF-NEF Connection Release procedure | When the PDU Session Release is initiated and if a NEF has been selected as anchor of the Control Plane CIoT 5GS Optimisation enabled PDU session which is Unstructured PDU Session Type as described in clause 4.3.4.2, then the SMF initiates a SMF-NEF Connection Release procedure towards the NEF corresponding to the "NEF ID" for that DNN / S-NSSAI Combination. Figure 4.25.7-1: SMF Initiated SMF-NEF Connection Release procedure 1. The SMF performs Step 1 of PDU Session Release Procedure as described in clause 4.3.4.2. 2. If a NEF has been selected as anchor of the Control Plane CIoT 5GS Optimisation enabled PDU session which is Unstructured PDU Session Type as described in clause 4.3.2.2, the SMF initiates the SMF-NEF Connection release for this PDU Session by sending Nnef_SMContext_Delete Request (User Identity, PDU Session ID, S-NSSAI, DNN, Release Cause) message to the NEF. 3. The NEF deletes the NEF PDU Session Context associated with the User Identity and the PDU session ID. The NEF sends Nnef_SMContext_Delete Response (Cause, [Small Data Control Rate Status], [APN Rate Control Status]) to the SMF confirming release of the SMF-NEF session for the UE. The NEF includes Small Data Rate Control Status if PDU Session used Small Data Rate Control. 4. Steps 3-15 of PDU Session Release Procedure as described in clause 4.3.4.2. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.25.7 |
3,394 | – SRS-SwitchingTimeEUTRA | The IE SRS-SwitchingTimeEUTRA is used to indicate the SRS carrier switching time supported by the UE for one E-UTRA band pair. SRS-SwitchingTimeEUTRA information element -- ASN1START -- TAG-SRS-SWITCHINGTIMEEUTRA-START SRS-SwitchingTimeEUTRA ::= SEQUENCE { switchingTimeDL ENUMERATED {n0, n0dot5, n1, n1dot5, n2, n2dot5, n3, n3dot5, n4, n4dot5, n5, n5dot5, n6, n6dot5, n7} OPTIONAL, switchingTimeUL ENUMERATED {n0, n0dot5, n1, n1dot5, n2, n2dot5, n3, n3dot5, n4, n4dot5, n5, n5dot5, n6, n6dot5, n7} OPTIONAL } -- TAG-SRS-SWITCHINGTIMEEUTRA-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,395 | 5.7.3a.2 Initiation | A UE initiates the procedure to report EUTRA SCG failures when neither NR MCG nor EUTRA SCG transmission is suspended and in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.6.13.2. Actions the UE shall perform upon initiating the procedure, other than related to the transmission of the SCGFailureInformationEUTRA message are specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.6.13.2. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3a.2 |
3,396 | 4.3.2.6.1 MS behaviour towards a network that has failed the authentication procedure | If the MS deems that the network has failed the authentication check, then it shall request RR or RRC to release the RR connection and the PS signalling connection, if any, and bar the active cell or cells (see 3GPP TS 25.331[ None ] [23c], 3GPP TS 25.304[ None ] [98] and 3GPP TS 44.018[ None ] [84]). The MS shall start any retransmission timers (e.g. T3210, T3220 or T3230), if they were running and stopped when the MS received the first AUTHENTICATION REQUEST message containing an invalid MAC or invalid SQN, or no AUTN when a UMTS authentication challenge was expected. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2.6.1 |
3,397 | 9.9.2.1 EPS bearer context status | The purpose of the EPS bearer context status information element is to indicate the state of each EPS bearer context that can be identified by an EPS bearer identity. The EPS bearer context status information element is coded as shown in figure 9.9.2.1.1 and table 9.9.2.1.1. The EPS bearer context status information element is a type 4 information element with 4 octets length. Figure 9.9.2.1.1: EPS bearer context status information element Table 9.9.2.1.1: EPS bearer context status information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.2.1 |
3,398 | 8.9.4.1.2 Enhanced Downlink Control Channel Performance Requirement Type A - 4 Tx Antenna Port with Non-Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 4 transmit antennas for the case of dominant interferer with the non-colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.1-1 and Table 8.9.4.1.2-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.9.4.1.2-2. In Table 8.9.4.1.2-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes information on Cell 2 and Cell 3. Table 8.9.4.1.2-1: Test Parameters for PDCCH/PCFICH Table 8.9.4.1.2-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type A | 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.9.4.1.2 |
3,399 | – SL-ConfiguredGrantConfig | The IE SL-ConfiguredGrantConfig specifies the configured grant configuration information for NR sidelink communication. SL-ConfiguredGrantConfig information element -- ASN1START -- TAG-SL-CONFIGUREDGRANTCONFIG-START SL-ConfiguredGrantConfig-r16 ::= SEQUENCE { sl-ConfigIndexCG-r16 SL-ConfigIndexCG-r16, sl-PeriodCG-r16 SL-PeriodCG-r16 OPTIONAL, -- Need M sl-NrOfHARQ-Processes-r16 INTEGER (1..16) OPTIONAL, -- Need M sl-HARQ-ProcID-offset-r16 INTEGER (0..15) OPTIONAL, -- Need M sl-CG-MaxTransNumList-r16 SL-CG-MaxTransNumList-r16 OPTIONAL, -- Need M rrc-ConfiguredSidelinkGrant-r16 SEQUENCE { sl-TimeResourceCG-Type1-r16 INTEGER (0..496) OPTIONAL, -- Need M sl-StartSubchannelCG-Type1-r16 INTEGER (0..26) OPTIONAL, -- Need M sl-FreqResourceCG-Type1-r16 INTEGER (0..6929) OPTIONAL, -- Need M sl-TimeOffsetCG-Type1-r16 INTEGER (0..7999) OPTIONAL, -- Need R sl-N1PUCCH-AN-r16 PUCCH-ResourceId OPTIONAL, -- Need M sl-PSFCH-ToPUCCH-CG-Type1-r16 INTEGER (0..15) OPTIONAL, -- Need M sl-ResourcePoolID-r16 SL-ResourcePoolID-r16 OPTIONAL, -- Need M sl-TimeReferenceSFN-Type1-r16 ENUMERATED {sfn512} OPTIONAL -- Need S } OPTIONAL, -- Need M ..., [[ sl-N1PUCCH-AN-Type2-r16 PUCCH-ResourceId OPTIONAL -- Need M ]], [[ sl-StartRBsetCG-Type1-r18 INTEGER (0..4) OPTIONAL -- Need M ]] } SL-ConfigIndexCG-r16 ::= INTEGER (0..maxNrofCG-SL-1-r16) SL-CG-MaxTransNumList-r16 ::= SEQUENCE (SIZE (1..8)) OF SL-CG-MaxTransNum-r16 SL-CG-MaxTransNum-r16 ::= SEQUENCE { sl-Priority-r16 INTEGER (1..8), sl-MaxTransNum-r16 INTEGER (1..32) } SL-PeriodCG-r16 ::= CHOICE{ sl-PeriodCG1-r16 ENUMERATED {ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000, spare6, spare5, spare4, spare3, spare2, spare1}, sl-PeriodCG2-r16 INTEGER (1..99) } -- TAG-SL-CONFIGUREDGRANTCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,400 | 4.23.11.3 Xn based handover with re-allocation of intermediate SMF | This procedure is used to hand over a UE from a Source NG-RAN to a Target NG-RAN using Xn interface (in this case the AMF is unchanged) and the AMF decides that the intermediate SMF(I-SMF) is to be changed. This procedure is used for non-roaming or local breakout roaming scenario. In the case of home routed roaming scenario, this procedure is also used except the I-SMF is replaced by V-SMF. The call flow is shown in figure 4.23.11.3 -1. Figure 4.23.11.3-1: Xn based inter NG-RAN handover with intermediate I-SMF re-allocation 1-3. Steps 1-3 are same as steps 1-3 described in clause 4.23.11.2 except that in step 2 the AMF sends Nsmf_PDUSession_UpdateSMContext Request to source I-SMF and then the source I-SMF sends the Nsmf_PDUSession_Update Request to SMF. 4. The target I-SMF sends Nsmf_PDUSession_Context Request to Source I-SMF to retrieve 5G SM Context. 5a-11. Steps 5a-11 are same as steps 5a-11 described in clause 4.23.11.2 with the following difference: In step 6, the target I-SMF invokes Nsmf_PDUSession_Update Request (Secondary RAT usage data, UE Location Information, UE presence in LADN service area, DL CN Tunnel Info of the I-UPF, DNAI list supported by target I-SMF) toward the SMF; In step 9, the SMF respond with Nsmf_PDUSession_Update Response. The SMF may provide the DNAI(s) of interest for this PDU Session to I-SMF as described in step 1 of Figure 4.23.9.1-1. The SMF may update the CN PDB in the response or using a separate PDU Session Modification procedure, based on local configuration. Secondary RAT usage data is extracted from PDU Session To Be Switched with N2 SM Information received from NG RAN. 12a. The AMF sends Nsmf_PDUSession_ReleaseSMContext Request (I-SMF only indication) to source I-SMF. The source I-SMF removes the SM context of this PDU session. An indication is included in this message to avoid invoking resource release in SMF. 12b. The source I-SMF sends N4 Session Release to release the resource in source I-UPF. If the source I-UPF acts as UL CL and is not co-located with local PSA, the source I-SMF also sends N4 Session Release to the local PSA to release the resource for the PDU Session. 13-14. Steps 13-14 are same as steps 12-13 described in clause 4.23.11.2. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.11.3 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.