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,501 | 4.11.6.1 Subscription and Notification of availability or expected level of support of a service API | Figure 4.11.6.1 1 represent the information flow subscribing and notifying the availability or expected level of support of a service API. For the subscription to Nnef_APISupportCapability service, the subscription request may include the Duration of Reporting. If the Duration of Reporting is expired, the SCEF+NEF deletes the subscription without any explicit signalling interaction. For the CN type Change Event subscription to the HSS+UDM, the subscription request may include the Duration of Reporting. If the Duration of Reporting is expired, the HSS+UDM locally unsubscribe the CN Type Change Event without any explicit signalling interaction. The SCEF+NEF informs the AF of the API Indication which indicates list of available north-bound API(s). Figure 4.11.6.1-1: Subscription and Notification of availability or expected level of support of a service API 1. The AF subscribes to Nnef_APISupportCapability service for a UE or a group of UEs by sending Nnef_APISupportCapability_Subscribe Request (UE ID or External Group ID, Report Type, callback URI, Duration of Reporting) message. The callback URI parameter is optional and is used in step 6 if provided. The Report Type can be either One-time report or Continuous report. If this is a subscription for Continuous report type, then the Duration of Reporting may be included. The Duration of Reporting is optional and is used to indicate when the subscription is invalid. If the SCEF+NEF has established direct connection with MME or AMF or SMF, steps 2 - 3 and step 5 are omitted. If this is a subscription for One-time report type and if the Freshness Timer of last One-time report type subscribe request is not expired or a direct connection has been set up with MME or AMF or SMF, the SCEF+NEF determines the CN type locally, steps 2 - 3 are omitted. 2. SCEF+NEF subscribes the CN Type Change Event to HSS+UDM by sending Nudm_EventExposure_Subscribe Request (CN Type Change, Report Type, UE ID or External Group ID, Duration of Reporting) message. If Duration of Reporting is received at step 1, it shall include Duration of Reporting in this message. 3. The HSS+UDM determines the CN type that is serving the indicated UE or the indicated group of UEs based on the registered MME or AMF. The HSS+UDM informs SCEF+NEF of the CN type by sending Nudm_EventExposure_Subscribe Response (CN Type) message. If the Report Type indicates One-time report, the HSS+UDM delete the CN Type Change Event subscription after sending the response with CN Type. The Freshness Timer is set in SCEF+NEF per operator's policy, e.g. based on the statistics of UE activities. If the Report Type indicates Continuous report, HSS+UDM stores the CN Type Change Event subscription. 4. According to the CN type received or local stored, the SCEF+NEF determines the availability or expected level of support of common north-bound APIs for the indicated UE or the indicated group of UEs. SCEF+NEF responds to AF by sending Nnef_APISupportCapability_Subscribe Response (API Indication). If the subscription is for One-time report type, then steps 5 - 6 are omitted. 5. When HSS+UDM detects that the indicated UE is switching between EPC and 5GC the HSS+UDM determines the CN type that is serving the indicated UE or the indicated group of UEs. The HSS+UDM informs SCEF+NEF of the CN type by sending Nudm_EventExposure_Notify (CN type). The CN type denotes the 5GC or EPC or 5GC+EPC serving the UE or the group of UEs. 6. According to the CN type received and local detected, the SCEF+NEF node determines the availability or expected level of support of common north-bound APIs for the indicated UE or the indicated group of UEs. SCEF+NEF inform AF of such API information by sending Nnef_APISupportCapability_Notify (API Indication) message. If callback URI is provided at step 1, then SCEF+NEF will send the Nnef_APISupportCapability_Notify (API Indication) message to the node addressed by callback URI. Upon reception of API Indication in step 4 or step 6, the AF obtains the availability or expected level of support of a given service for the indicated UE or the indicated group of UEs. If required, the AF can select the valid north-bound API based on such API information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.6.1 |
3,502 | 20.3.3 Private User Identity | The Private User Identity shall take the form of an NAI, and shall have the form "username@realm" as specified in clause 2.1 of IETF RFC 4282 [53]. The MSC Server enhanced for ICS shall derive the Private User Identity from the subscriber's IMSI as follows: 1. Use the whole string of digits as the username part of the private user identity; and 2. convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in clause 20.3.2. The result will be a Private User Identity of the form "<IMSI>@ics.mnc<MNC>.mcc<MCC>.3gppnetwork.org". For example if the IMSI is 234150999999999 (MCC = 234, MNC = 15), the private user identity then takes the form [email protected] | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 20.3.3 |
3,503 | 4.2.8.5.3 Network Functions | Trusted WLAN Access Point (TWAP): It is a particular type of a Trusted Non-3GPP Access Point (TNAP) specified in clause 4.2.8.2, that supports a WLAN access technology, e.g. IEEE 802.11. This function is outside the scope of the 3GPP specifications. Trusted WLAN Interworking Function (TWIF): It provides interworking functionality that enables N5CW devices to access 5GC. The TWIF supports the following functions: - Terminates the N1, N2 and N3 interfaces. - Implements the AMF selection procedure. - Implements the NAS protocol stack and exchanges NAS messages with the AMF on behalf of the N5CW device. - On the user plane, it relays protocol data units (PDUs) between the Yw interface and the N3 interface. - May implement a local mobility anchor within the trusted WLAN access network. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8.5.3 |
3,504 | – RadioLinkMonitoringConfig | The IE RadioLinkMonitoringConfig is used to configure radio link monitoring for detection of beam- and/or cell radio link failure. See also TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1. RadioLinkMonitoringConfig information element -- ASN1START -- TAG-RADIOLINKMONITORINGCONFIG-START RadioLinkMonitoringConfig ::= SEQUENCE { failureDetectionResourcesToAddModList SEQUENCE (SIZE(1..maxNrofFailureDetectionResources)) OF RadioLinkMonitoringRS OPTIONAL, -- Need N failureDetectionResourcesToReleaseList SEQUENCE (SIZE(1..maxNrofFailureDetectionResources)) OF RadioLinkMonitoringRS-Id OPTIONAL, -- Need N beamFailureInstanceMaxCount ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10} OPTIONAL, -- Need R beamFailureDetectionTimer ENUMERATED {pbfd1, pbfd2, pbfd3, pbfd4, pbfd5, pbfd6, pbfd8, pbfd10} OPTIONAL, -- Need R ..., [[ beamFailure-r17 BeamFailureDetection-r17 OPTIONAL -- Need R ]] } BeamFailureDetection-r17 ::= SEQUENCE { failureDetectionSet1-r17 BeamFailureDetectionSet-r17 OPTIONAL, -- Need R failureDetectionSet2-r17 BeamFailureDetectionSet-r17 OPTIONAL, -- Need R additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL -- Need R } RadioLinkMonitoringRS ::= SEQUENCE { radioLinkMonitoringRS-Id RadioLinkMonitoringRS-Id, purpose ENUMERATED {beamFailure, rlf, both}, detectionResource CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId }, ... } BeamFailureDetectionSet-r17 ::= SEQUENCE { bfdResourcesToAddModList-r17 SEQUENCE (SIZE(1..maxNrofBFDResourcePerSet-r17)) OF BeamLinkMonitoringRS-r17 OPTIONAL, -- Need N bfdResourcesToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofBFDResourcePerSet-r17)) OF BeamLinkMonitoringRS-Id-r17 OPTIONAL, -- Need N beamFailureInstanceMaxCount-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10} OPTIONAL, -- Need R beamFailureDetectionTimer-r17 ENUMERATED {pbfd1, pbfd2, pbfd3, pbfd4, pbfd5, pbfd6, pbfd8, pbfd10} OPTIONAL, -- Need R ... } BeamLinkMonitoringRS-r17 ::= SEQUENCE { beamLinkMonitoringRS-Id-r17 BeamLinkMonitoringRS-Id-r17, detectionResource-r17 CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId }, ... } BeamLinkMonitoringRS-Id-r17 ::= INTEGER (0..maxNrofFailureDetectionResources-1-r17) -- TAG-RADIOLINKMONITORINGCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,505 | C.3.4 Guidelines for the allocation of the index values in the array scheme | - General rule: index values used in the array scheme, according to Annex C.1.2, shall be allocated cyclically within its range 0, ... , a-1. This means that the index value used with the previously generated authentication vector is stored in SQNHE , and the next authentication vector shall use index value +1 mod a. It may be useful to allow exceptions to this general rule when additional information is available. This includes: - Authentication vectors distributed within the same batch shall have the same index value. The Authentication Data Request MAP message contains information about the domain type (CS or PS) of the requesting serving node from which the request originates. It is recommended to use this information in the following way. Support for this use is, however, not required for an implementation to claim compliance to Annex C. - Authentication vectors distributed to different service domains shall have different index values (i.e. separate ranges of index values are reserved for PS and CS operation). In future releases there may be additional information about the requesting node identity. If this information is available it is recommended to use it in the following way: - If the new request comes from the same serving node as the previous request, then the index value used for the new request shall be the same as was used for the previous request. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | C.3.4 |
3,506 | 6.5.2F.3 In-band emissions | The in-band emission is defined as a function of the tone offset from the edge of the allocated UL transmission tone(s) within the transmission bandwidth configuration. The in-band emission is measured as the ratio of the UE output power in a non–allocated tone to the UE output power in an allocated tone. The basic in-band emissions measurement interval is defined over one slot in the time domain. The category NB1 and NB2 UE relative in-band emission shall not exceed the values specified in Table 6.5.2F.3-1. Table 6.5.2F.3-1: Minimum requirements for in-band emissions | 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.5.2F.3 |
3,507 | A.19 Use case of RSRP | E-UTRAN RSRP measurement is important for analyzing coverage probability and coverage balance of downlink. From the distribution of this measurement, the general coverage information can be learned. So that coverage hole can be found more easily by driving test. Much more measurment values with small granularity are necessary to analyze coverage probability for specific area, such as from ratio of the number of RSRP that is larger than or equal to threshld to the total number of it, So it is necessary to define RSRP measurement. According to optimization experience and the transmission bandwidth requirement reduced, several granularity of this measurement is proposed. For -120 dBm RSRP < -115dBm, the granularity is 5dB, for -115 dBm RSRP < -80dBm, the granularity is 1dB, and for -80 dBm RSRP < -60dBm, the granularity is 2dB. The measurement period should be preconfigured by . | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.19 |
3,508 | – ResourceConfigNRDC | The IE is used to indicate or request the maximum values that can be used by the SCG in NR-DC, with each value equal to or lower than the value of the corresponding field in the UE capability, as reported by the UE, unless specified otherwise. ResourceConfigNRDC information element -- ASN1START -- TAG-RESOURCECONFIGNRDC-START ResourceConfigNRDC-r17 ::= SEQUENCE { fr1-ResourceConfig-r17 ResourceConfigPerFR-r17 OPTIONAL, fr2-ResourceConfig-r17 ResourceConfigPerFR-r17 OPTIONAL, maxNumberResAcrossCC-AcrossFR-r17 INTEGER (0..256) OPTIONAL, ... } ResourceConfigPerFR-r17 ::= SEQUENCE { bm-MaxNumberCSI-RS-Resource-r17 INTEGER (0..64) OPTIONAL, bm-MaxNumberAperiodicCSI-RS-Resource-r17 INTEGER (0..64) OPTIONAL, cg-MaxNumberConfigsAllCC-r17 INTEGER (0..32) OPTIONAL, maxNumberCSI-RS-BFD-r17 INTEGER (0..64) OPTIONAL, maxNumberCSI-RS-SSB-CBD-r17 INTEGER (0..256) OPTIONAL, maxNumberSSB-BFD-r17 INTEGER (0..64) OPTIONAL, sps-MaxNumberConfigsAllCC-r17 INTEGER (0..32) OPTIONAL, trs-MaxConfResourceSetsAllCC-r17 INTEGER (0..256) OPTIONAL, ... } -- TAG-RESOURCECONFIGNRDC-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,509 | 8.13.2.3 Management based MDT Activation in gNB-DU | The signalling flow for Management based MDT Activation in gNB-DU is shown in Figure 8.13.2.3-1. Figure 8.13.2.3-1 Management based MDT Activation in gNB-DU 1. The gNB-CU-CP sends UE CONTEXT SETUP REQUEST message to the gNB-DU, including Management based MDT PLMN List. The message may include the Polluted Measurement Indicator IE. If the gNB-DU has received the Polluted Measurement Indicator IE, the gNB-DU includes the information contained in such indicator as part of the measurement report to be sent to the TCE, so that the TCE is able to correlate and filter the affected measurements. 2. The gNB-DU sends UE CONTEXT SETUP RESPONSE message to the gNB-CU-CP. 3. The EM sends a Trace Session activation request to the gNB-DU. This request includes the parameters for configuring UE measurements. 4. The gNB-DU shall select the suitable UEs for MDT data collection. If the UE is not in the specified area or if the serving PLMN is not within the Management Based MDT PLMN List the UE shall not be selected by the gNB-DU for MDT data collection as defined in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. For each selected UE, the gNB-DU may send CELL TRAFFIC TRACE message to the gNB-CU-CP in the F1 UE associated signalling, including Trace ID for MDT. 5. Upon reception of a CELL TRAFFIC TRACE message from F1, the gNB-CU-CP shall send CELL TRAFFIC TRACE message to the AMF for this UE, including Trace ID for MDT. The AMF forwards Trace ID and other information to the TCE as specified in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.13.2.3 |
3,510 | I.2.5 Requirements for secure environment | The secure environment is logically defined within the RNC in an exposed location and is a composition of functions for the support of sensitive operations. 1. The secure environment shall support secure storage of sensitive data, e.g. long term cryptographic secrets and vital configuration data. 2. The secure environment shall support the execution of sensitive functions, e.g. en-/decryption of user data and the basic steps within protocols which use long term secrets (e.g. in authentication protocols). 3. Sensitive data used within the secure environment shall not be exposed to external entities. 4. The secure environment shall support the execution of sensitive parts of the boot process. 5. The secure environment's integrity shall be assured. 6. Only authorised access shall be granted to the secure environment, i.e. to data stored and used within, and to functions executed within. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | I.2.5 |
3,511 | 5.3.3 Temporary identities | A temporary user identity for 5GS-based services, the 5G globally unique temporary identity (5G-GUTI), is used for identification within the signalling procedures. In case of PLMN the 5G-GUTI is globally unique and in case of SNPN the 5G-GUTI is unique within an SNPN. When the UE is registered to the same PLMN or SNPN over 3GPP and non-3GPP access, the UE and the AMF maintain one 5G-GUTI that is common to both 3GPP and non-3GPP access. When the UE is required to delete the 5G-GUTI according to a NAS procedure, the UE shall delete the 5G-GUTI only if it is not registered to the same PLMN or SNPN through other access. When the UE is registered to different PLMNs or SNPNs over 3GPP access and non-3GPP access, the UE maintains two 5G-GUTIs, a 5G-GUTI for the registration with a PLMN or SNPN over the 3GPP access and another 5G-GUTI for the registration with another PLMN or SNPN over the non-3GPP access. In the paging and service request procedures, a shortened form of the 5G-GUTI, the 5G S-temporary mobile subscriber identity (5G-S-TMSI), is used to enable more efficient radio signalling. The purpose of the 5G-GUTI and 5G-S-TMSI is to provide identity confidentiality, i.e., to protect a user from being identified and located by an intruder. The structure of the 5G-GUTI and its derivatives are specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [4]. The 5G-GUTI has two main components (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]): a) the GUAMI; and b) the 5G-TMSI that provides an unambiguous identity of the UE within the AMF(s) identified by the GUAMI. The 5G-S-TMSI has three main components: a) the AMF set ID that uniquely identifies the AMF set within the AMF region; b) the AMF pointer that identifies one or more AMFs within the AMF set; and c) the 5G-TMSI. A UE supporting N1 mode includes a valid 5G-GUTI, if any is available, in the REGISTRATION REQUEST and DEREGISTRATION REQUEST messages. In the SERVICE REQUEST message, the UE includes a valid 5G-S-TMSI as user identity. The AMF shall assign a new 5G-GUTI for a particular UE: a) during a successful initial registration procedure; b) during a successful registration procedure for mobility registration update; c) after a successful service request procedure invoked as a response to a paging request from the network and before the: 1) release of the N1 NAS signalling connection; or 2) suspension of the N1 NAS signalling connection due to user plane CIoT 5GS optimization i.e. before the UE and the AMF enter 5GMM-IDLE mode with suspend indication; as specified in subclause 5.4.4.1; and d) after the AMF receives an indication from the lower layers that it has received the NGAP UE context resume request message as specified in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [31] for a UE in 5GMM-IDLE mode with suspend indication and this resumption is a response to a paging request from the network, and before the: 1) release of the N1 NAS signalling connection; or 2) suspension of the N1 NAS signalling connection due to user plane CIoT 5GS optimization i.e. before the UE and the AMF enter 5GMM-IDLE mode with suspend indication; as specified in subclause 5.4.4.1. The AMF should assign a new 5G-GUTI for a particular UE during a successful registration procedure for periodic registration update. The AMF may assign a new 5G-GUTI at any time for a particular UE by performing the generic UE configuration update procedure. If a new 5G-GUTI is assigned by the AMF, the UE and the AMF handle the 5G-GUTI as follows: a) Upon receipt of a 5GMM message containing a new 5G-GUTI, the UE considers the new 5G-GUTI as valid and the old 5G-GUTI as invalid, stops timer T3519 if running, and deletes any stored SUCI. The new 5G-GUTI is stored in a non-volatile memory in the USIM if the corresponding file is present in the USIM, else in the non-volatile memory in the ME, as described in annex C. b) The AMF considers the old 5G-GUTI as invalid as soon as an acknowledgement for a registration or generic UE configuration update procedure is received. | 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.3 |
3,512 | 6.3.5G.1 Absolute power tolerance | Absolute power tolerance is the ability of the UE to set its output power to a specific value for each subframe. For V2X sidelink communication transmissions in the operating bands specified in Table 5.5G-1, the minimum requirement for absolute power tolerance is given in Table 6.3.5G.1-1 over the power range bounded by the Maximum output power as defined in subclause 6.2.2G and the Minimum output power as defined in subclause 6.3.2G. For operating bands under NOTE 2 in Table 6.2.2-1, the absolute power tolerance as specified in Table 6.3.5G.1-1 is relaxed by reducing the lower limit by 1.5 dB when the transmission bandwidth is confined within FUL_low and FUL_low + 4 MHz or FUL_high – 4 MHz and FUL_high. Table 6.3.5G.1-1: Absolute power tolerance For intra-band contiguous multi-carrier operation the absolute power control tolerance specified in Table 6.3.5G.1-1 shall apply for each component carrier. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.5G.1 |
3,513 | 9.8.3.1 FDD and half-duplex FDD | The following requirements apply to UE supporting ce-ModeA-r13 and ce-PDSCH-64QAM-r15. For the parameters specified in Table 9.8.3.1-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.31 FDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. Table 9.8.3.1-1: PUCCH 1-0 static test (FDD and half-duplex FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.8.3.1 |
3,514 | 5.3.4 Random access | Random access preamble sequences, of four different lengths are supported. Sequence length 839 is applied with subcarrier spacings of 1.25 and 5 kHz, sequence length 139 is applied with subcarrier spacings of 15, 30, 60, 120, 480, and 960 kHz, sequence length of 571 is applied with subcarrier spacings of 30, 120, and 480 kHz, and sequence length 1151 is applied with subcarrier spacings of 15 and 120 kHz. Sequence length 839 supports unrestricted sets and restricted sets of Type A and Type B, while sequence lengths 139, 571, and 1151 support unrestricted sets only. Sequence length 839 is only used for operation with licensed channel access while sequence length 139 can be used for operation with either licensed or shared spectrum channel access. For FR1, sequence lengths of 571 and 1151 can be used only for operation with shared spectrum channel access. For FR2-2, sequence lengths of 571 can be used for operation with either licensed or shared spectrum channel access only with subcarrier spacings of 120 kHz and 480 kHz and sequence lengths of 1151 can be used for operation with either licensed or shared spectrum channel access only with subcarrier spacings of 120 kHz. Multiple PRACH preamble formats are defined with one or more PRACH OFDM symbols, and different CP and guard time. The PRACH preamble configuration to use is provided to the UE in the system information. For IAB additional random access configurations are defined. These configurations are obtained by extending the random access configurations defined for UEs via scaling the periodicity and/or offsetting the time domain position of the RACH occasions. IAB-MTs can be provided with random access configurations (as defined for UEs or after applying the aforementioned scaling/offsetting) different from random access configurations provided to UEs. The UE calculates the PRACH transmit power for the retransmission of the preamble based on the most recent estimate pathloss and power ramping counter. The system information provides information for the UE to determine the association between the SSB and the RACH resources. The RSRP threshold for SSB selection for RACH resource association is configurable by network. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.4 |
3,515 | – ReportConfigInterRAT | The IE ReportConfigInterRAT specifies criteria for triggering of an inter-RAT measurement reporting event, or an L2 U2N relay measurement reporting event. The inter-RAT measurement reporting events for E-UTRA and UTRA-FDD are labelled BN with N equal to 1, 2 and so on. The measurement reporting events for L2 U2N relay UE are labelled YN with N equal to 1, 2 and so on. The measurement reporting events for L2 U2N relay UE are labelled Z1. Event B1: Neighbour becomes better than absolute threshold; Event B2: PCell becomes worse than absolute threshold1 AND Neighbour becomes better than another absolute threshold2; Event Y1: PCell becomes worse than absolute threshold1 AND candidate L2 U2N Relay UE becomes better than another absolute threshold2; Event Y2: Candidate L2 U2N Relay UE becomes better than absolute threshold; Event Z1: Serving L2 U2N Relay UE becomes worse than absolute threshold1 AND candidate L2 U2N Relay UE becomes better than another absolute threshold2; ReportConfigInterRAT information element -- ASN1START -- TAG-REPORTCONFIGINTERRAT-START ReportConfigInterRAT ::= SEQUENCE { reportType CHOICE { periodical PeriodicalReportConfigInterRAT, eventTriggered EventTriggerConfigInterRAT, reportCGI ReportCGI-EUTRA, ..., reportSFTD ReportSFTD-EUTRA } } ReportCGI-EUTRA ::= SEQUENCE { cellForWhichToReportCGI EUTRA-PhysCellId, ..., [[ useAutonomousGaps-r16 ENUMERATED {setup} OPTIONAL -- Need R ]] } ReportSFTD-EUTRA ::= SEQUENCE { reportSFTD-Meas BOOLEAN, reportRSRP BOOLEAN, ... } EventTriggerConfigInterRAT ::= SEQUENCE { eventId CHOICE { eventB1 SEQUENCE { b1-ThresholdEUTRA MeasTriggerQuantityEUTRA, reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger, ... }, eventB2 SEQUENCE { b2-Threshold1 MeasTriggerQuantity, b2-Threshold2EUTRA MeasTriggerQuantityEUTRA, reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger, ... }, ..., [[ eventB1-UTRA-FDD-r16 SEQUENCE { b1-ThresholdUTRA-FDD-r16 MeasTriggerQuantityUTRA-FDD-r16, reportOnLeave-r16 BOOLEAN, hysteresis-r16 Hysteresis, timeToTrigger-r16 TimeToTrigger, ... }, eventB2-UTRA-FDD-r16 SEQUENCE { b2-Threshold1-r16 MeasTriggerQuantity, b2-Threshold2UTRA-FDD-r16 MeasTriggerQuantityUTRA-FDD-r16, reportOnLeave-r16 BOOLEAN, hysteresis-r16 Hysteresis, timeToTrigger-r16 TimeToTrigger, ... } ]], [[ eventY1-Relay-r17 SEQUENCE { y1-Threshold1-r17 MeasTriggerQuantity, y1-Threshold2-Relay-r17 SL-MeasTriggerQuantity-r16, reportOnLeave-r17 BOOLEAN, hysteresis-r17 Hysteresis, timeToTrigger-r17 TimeToTrigger, ... }, eventY2-Relay-r17 SEQUENCE { y2-Threshold-Relay-r17 SL-MeasTriggerQuantity-r16, reportOnLeave-r17 BOOLEAN, hysteresis-r17 Hysteresis, timeToTrigger-r17 TimeToTrigger, ... } ]], [[ eventZ1-Relay-r18 SEQUENCE { z1-Threshold1-Relay-r18 SEQUENCE { sl-RSRP-r18 SL-MeasTriggerQuantity-r16, sd-RSRP-r18 SL-MeasTriggerQuantity-r16 OPTIONAL, -- Need S ... }, z1-Threshold2-Relay-r18 SL-MeasTriggerQuantity-r16, reportOnLeave-r18 BOOLEAN, hysteresis-r18 Hysteresis, timeToTrigger-r18 TimeToTrigger, ... } ]] }, rsType NR-RS-Type, reportInterval ReportInterval, reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, reportQuantity MeasReportQuantity, maxReportCells INTEGER (1..maxCellReport), ..., [[ reportQuantityUTRA-FDD-r16 MeasReportQuantityUTRA-FDD-r16 OPTIONAL -- Need R ]], [[ includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need R includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M ]], [[ reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL -- Need R ]]} PeriodicalReportConfigInterRAT ::= SEQUENCE { reportInterval ReportInterval, reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, reportQuantity MeasReportQuantity, maxReportCells INTEGER (1..maxCellReport), ..., [[ reportQuantityUTRA-FDD-r16 MeasReportQuantityUTRA-FDD-r16 OPTIONAL -- Need R ]], [[ includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need R includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M ]], [[ reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL -- Need R ]], [[ cellIndividualOffsetList-r18 SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF CellIndividualOffsetList-EUTRA-r18 OPTIONAL -- Need R ]] } MeasTriggerQuantityUTRA-FDD-r16 ::= CHOICE{ utra-FDD-RSCP-r16 INTEGER (-5..91), utra-FDD-EcN0-r16 INTEGER (0..49) } MeasReportQuantityUTRA-FDD-r16 ::= SEQUENCE { cpich-RSCP BOOLEAN, cpich-EcN0 BOOLEAN } CellIndividualOffsetList-EUTRA-r18 ::= SEQUENCE { physCellId-r18 EUTRA-PhysCellId, cellIndividualOffset-r18 EUTRA-Q-OffsetRange } -- TAG-REPORTCONFIGINTERRAT-STOP -- ASN1STOP Editor's Note: FFS how to include two thresholds for SL-RSRP and SD-RSRP in event X1, X2, Y2. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,516 | 5.16.3.10 IMS Voice Service via EPS Fallback or RAT fallback in 5GS | In order to support various deployment scenarios for obtaining IMS voice service, the UE and NG-RAN may support the mechanism to direct or redirect the UE from NG-RAN either towards E-UTRA connected to 5GC (RAT fallback) or towards EPS (E-UTRAN connected to EPC System fallback). Following principles apply for IMS Voice Service: - The serving AMF indicates toward the UE during the Registration procedure that IMS voice over PS session is supported. - If a request for establishing the QoS Flow for IMS voice reaches the NG-RAN, the NG-RAN responds indicating rejection of the establishment request and the NG-RAN may trigger one of the following procedures depending on UE capabilities, N26 availability, network configuration and radio conditions: - Redirection to EPS; - Handover procedure to EPS; - Redirection to E-UTRA connected to 5GC; or - Handover to E-UTRA connected to 5GC. - If needed, Network Provided Location Information is provided as described in clauses 4.13.6.1 and 4.13.6.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - The ongoing IMS voice session is not impacted by a change of the IMS voice over PS session indicator from supported to unsupported (e.g. the UE receives during RAT Fallback or EPS Fallback the IMS voice over PS session indicator indicating that IMS voice over PS sessions are not supported). NOTE: Any change in IMS voice over PS session indicator applies to new IMS sessions initiated only after the ongoing IMS voice session is terminated. During any release of RRC connection including after EPS/RAT fallback is performed, the eNB or NG-RAN node may provide to the UE dedicated idle mode priorities for NR as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51] taking into account RFSP, PLMNs contained in Handover Restriction List and local operator policy. If the UE remains ECM/CM-CONNECTED after the voice call has ended, the eNB or NG-RAN node may trigger handover to NR connected to 5GC, if configured to do so, taking into account local operator policy and Handover Restriction List. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.3.10 |
3,517 | 6.10.5 CSI reference signals | CSI reference signals are transmitted on 1, 2, 4, 8, 12, 16, 20, 24, 28, or 32 antenna ports using , , , , , ,, , and, respectively. For CSI reference signals using more than eight antenna ports, CSI-RS configurations in the same subframe, numbered from 0 to , where value 0 corresponds to the configured resourceConfig-r11 or resourceConfig-r10 and value k (k>0) corresponds to the configured k-th entry of NZP-ResourceConfig-r13 from an aggregated list consisting of nzp-resourceConfigList-r13 followed by nzp-resourceConfigListExt-r14 (if configured), are aggregated to obtain antenna ports in total. Each CSI-RS configuration in such an aggregation corresponds to antenna ports and one of the configurations in the range 0-19 in Table 6.10.5.2-1 for normal cyclic prefix, and one of the configurations in the range 0-15 in Table 6.10.5.2-2 for extended cyclic prefix. The supported configurations of aggregated CSI-RS configurations are shown in Table 6.10.5-1. If the higher layer parameter NZP-TransmissionComb is not configured, unique CSI-RS configurations from Table 6.10.5.2-1 for normal cyclic prefix and from Table 6.10.5.2-2 for extended cyclic prefix are aggregated to form 12, 16, 20, 24, 28, or 32 antenna ports. For CSI reference signals using more than sixteen antenna ports, when higher layer parameter NZP-TransmissionComb is configured, the number of unique CSI-RS configurations from Table 6.10.5.2-1 for normal cyclic prefix and from Table 6.10.5.2-2 for extended cyclic prefix that are aggregated to form 20, 24, 28, or 32 antenna ports can be less than or equal to . The number of antenna ports within each such unique CSI-RS resource configuration is an integer multiple of . CSI reference signals are defined for only. Table 6.10.5-1: Aggregation of CSI-RS configurations. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.10.5 |
3,518 | 4.23.5.3 PDU Session modification procedure | For the non-roaming or LBO roaming case, the procedure defined in clause 4.3.3.3 (UE or network requested PDU Session Modification for Home-routed Roaming) is used to modify the PDU Session, with the V-SMF and V-UPF are replaced by I-SMF and I-UPF and H-SMF and H-UPF are replaced by SMF and UPF(PSA) respectively. If the QoS Monitoring as defined in clause 5.33.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] is triggered, the following enhancement to clause 4.3.3.3 applies: - In step 3, if the SMF determines the need for QoS Monitoring for a QoS flow according to the information received from the PCF in step 1b, or based on SMF local policy, SMF includes QoS Monitoring indication and how frequently QoS Monitoring reporting to be performed, in Nsmf_PDUSession_Update Request message. - In step 3, if, according to the information received from the PCF in step 1b, or based on SMF local policy, the SMF determines the need for GTP-U Path Monitoring as defined in clause 5.33.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF includes QoS monitoring policy in Nsmf_PDUSession_Update Request message. - In step 4b, if in step 3 the I-SMF received QoS Monitoring indication and may receive how frequently QoS Monitoring reporting to be performed in Nsmf_PDUSession_Update Request the I-SMF includes the QoS Monitoring indication and how frequently QoS Monitoring reporting to be performed in N2 SM message sent to the 5G AN. - In step 4b, if in step 3 the I-SMF received QoS monitoring policy indication and may receive how frequently QoS Monitoring reporting to be performed in Nsmf_PDUSession_Update Request, the I-SMF includes such QoS monitoring policy also to I-UPF for GTP-U path monitoring. - In step 15, the I-SMF sends Nsmf_PDUSession_Update Response to SMF. The SMF updates N4 session of the UPF PSA as defined for the case where is no I-SMF. - If later on the RAN provides over N2 the QoS Monitoring Result with UL packet delay information comprising the packet delays of RAN and N3 interface, the I-SMF forwards this information to the SMF in Nsmf_PDUSession_Update Request message. - I-SMF shall forward monitoring report (for QoS monitoring per GTP-U path) from I-UPF to SMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.5.3 |
3,519 | 5.1.1 Control Plane 5.1.1.1 General | The control plane consists of protocols for control and support of the user plane functions: - controlling the E-UTRA network access connections, such as attaching to and detaching from E-UTRAN; - controlling the attributes of an established network access connection, such as activation of an IP address; - controlling the routing path of an established network connection in order to support user mobility; and - controlling the assignment of network resources to meet changing user demands. The following control planes are used in E-UTRAN mode. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.1.1 |
3,520 | 4.12.4.1 Service Request procedures via Untrusted non-3GPP Access | The Service Request procedure via Untrusted non-3GPP Access shall be used by a UE in CM-IDLE state over non-3GPP access to request the re-establishment of the NAS signalling connection and the re-establishment of the user plane for all or some of the PDU Sessions which are associated to non-3GPP access. The Service Request procedure via Untrusted non-3GPP Access shall be used by a UE in CM-CONNECTED state over non-3GPP access to request the re-establishment of the user plane for one or more PDU Sessions which are associated to non-3GPP access. When the UE is in CM-IDLE state over non-3GPP access, the Service Request procedure via Untrusted non-3GPP Access is as described in clause 4.2.3.2 (UE Triggered Service Request) with the following exceptions: - The Service Request procedure is never a response to a Paging, i.e. there is no Network Triggered Service Request procedure via Untrusted non-3GPP Access. - The (R)AN corresponds to an N3IWF. - The UE establishes a "signalling IPsec SA" with the N3IWF by using the procedure specified in clause 4.12.2 for the registration via untrusted non-3GPP access. In particular, the UE includes the Service Request and the AN parameters in an EAP-5G packet, which is further encapsulated in an IKE_AUTH request. - The AN parameters include the Selected PLMN ID (or PLMN ID and NID, see clause 5.30 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and Establishment cause. The Establishment cause provides the reason for requesting a signalling connection with the 5GC. The UE includes GUAMI information in the AN parameters. The N3IWF selects the AMF according to GUAMI information. - The N2 parameters sent from N3IWF to AMF include the Establishment cause. - The user plane between the UE and N3IWF is established not with RRC signalling but with IKEv2 signalling, as specified in clause 4.12.5 (i.e. by using an IKEv2 Create_Child_SA exchange). The IKEv2 Create Child SA Request may include the Additional QoS Information to reserve non-3GPP specific QoS resources as defined in clause 4.12a.5. The user plane of each PDU Session consists of one or more Child SAs. When the UE is in CM-CONNECTED state over non-3GPP access, the Service Request procedure via Untrusted non-3GPP Access is as described in clause 4.2.3.2 (UE Triggered Service Request) with the following exceptions: - All NAS signalling exchanged between the UE and network is transferred within the established "signalling IPsec SA". - The (R)AN corresponds to an N3IWF. - The user plane between the UE and N3IWF is established not with RRC signalling but with IKEv2 signalling, as specified in clause 4.12.5 (i.e. by using an IKEv2 Create_Child_SA exchange). The user plane of each PDU Session consists of one or more Child SAs. When the UE is in CM-CONNECTED state over non-3GPP access and the network receives downlink data for a PDU Session over non-3GPP access that has no user plane, the steps 1-4a in clause 4.2.3.3 (Network Triggered Service Request) shall be performed with the following exceptions: - The (R)AN corresponds to an N3IWF. - The user plane between the UE and N3IWF is established (in step 4a) with IKEv2 signalling, as specified in clause 4.12.5 (i.e. by using an IKEv2 Create_Child_SA exchange). The user plane of each PDU Session consists of one or more Child SAs. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12.4.1 |
3,521 | 4.7.5.1.2 GMM Common procedure initiation | If the network receives a ROUTING AREA UPDATE REQUEST message containing the P-TMSI type IE, and the network does not follow the use of the most significant bit of the <LAC> to distinguish the node type as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [10] subclause 2.8.2.2.2, the network shall use the P-TMSI type IE to determine whether the mobile identity included in the P-TMSI IE, if any, or the mobile identity used by the MS to derive a foreign TLLI (see subclause 4.7.1.4.1) is a native P-TMSI or a mapped P-TMSI. The network may initiate GMM common procedures, e.g. the GMM authentication and ciphering procedure. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.5.1.2 |
3,522 | 5.7.2.5 Flow Bit Rates | For GBR QoS Flows only, the following additional QoS parameters exist: - Guaranteed Flow Bit Rate (GFBR) - UL and DL; - Maximum Flow Bit Rate (MFBR) -- UL and DL. The GFBR denotes the bit rate that is guaranteed to be provided by the network to the QoS Flow over the Averaging Time Window. The MFBR limits the bit rate to the highest bit rate that is expected by the QoS Flow (e.g. excess traffic may get discarded or delayed by a rate shaping or policing function at the UE, RAN, UPF). Bit rates above the GFBR value and up to the MFBR value, may be provided with relative priority determined by the Priority Level of the QoS Flows (see clause 5.7.3.3). GFBR and MFBR are signalled to the (R)AN in the QoS Profile and signalled to the UE as QoS Flow level QoS parameter (as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]) for each individual QoS Flow. NOTE 1: The GFBR is recommended as the lowest acceptable service bitrate where the service will survive. NOTE 2: For each QoS Flow of Delay-critical GBR resource type, the SMF can ensure that the GFBR of the QoS Flow can be achieved with the MDBV of the QoS Flow using the QoS Flow binding functionality described in clause 6.1.3.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE 3: The network can set MFBR larger than GFBR for a particular QoS Flow based on operator policy and the knowledge of the end point capability, i.e. support of rate adaptation at application / service level. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.2.5 |
3,523 | J.2 Usage of the TIN | The UE may have valid MM parameters both from MME and from SGSN. The "Temporary Identity used in Next update" (TIN) is a parameter of the UE's MM context, which identifies the UE identity to be indicated in the next RAU Request or TAU Request message. The TIN also identifies the status of ISR activation in the UE. The TIN can take one of the three values, "P-TMSI", "GUTI" or "RAT-related TMSI". The UE sets the TIN when receiving an Attach Accept, a TAU Accept or RAU Accept message as specified in table 4.3.5.6-1. "ISR Activated" indicated by the RAU/TAU Accept message but the UE not setting the TIN to "RAT-related TMSI" is a special situation. Here the UE has deactivated ISR due to special situation handling (see clause J.6). By maintaining the old TIN value the UE remembers to use the RAT TMSI indicated by the TIN when updating with the CN node of the other RAT. Only if the TIN is set to "RAT-related TMSI" ISR behaviour is enabled for the UE, i.e. the UE can change between all registered areas and RATs without any update signalling and it listens for paging on the RAT it is camped on. If the TIN is set to "RAT-related TMSI", the UE's P-TMSI and RAI as well as its GUTI and TAI(s) remain registered with the network and valid in the UE. When ISR is not active the TIN is always set to the temporary ID belonging to the currently used RAT. This guarantees that always the most recent context data are used, which means during inter-RAT changes there is always context transfer from the CN node serving the last used RAT. The UE identities, old GUTI IE and additional GUTI IE, indicated in the next TAU Request message, and old P-TMSI IE and additional P-TMSI/RAI IE, indicated in the next RAU Request message depend on the setting of TIN and are specified in table 4.3.5.6-2. The UE indicates also information elements "additional GUTI" or "additional P-TMSI" in the Attach Request, TAU or RAU Request. These information elements permit the MME/SGSN to find the already existing UE contexts in the new MME or SGSN, when the "old GUTI" or "old P-TMSI" indicate values that are mapped from other identities. | 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") | J.2 |
3,524 | 5.2.6.7.2 Nnef_TrafficInfluence_Create operation | Service operation name: Nnef_TrafficInfluence_Create Description: Authorize the request and forward the request for traffic influence. Inputs, Required: AF Transaction Id, AF Identifier. The AF Transaction Id refers to the request. Inputs, Optional: The address (IP or Ethernet) of one or more UE(s) if available, one or more GPSIs if available, DNN if available, S-NSSAI if available, External Group Identifier(s) if available, External Application Identifier or traffic filtering information, AF-Service-Identifier, a list of DNAI(s) and corresponding routing profile ID(s) or N6 traffic routing information, Indication of traffic correlation, Indication of application relocation possibility, Indication of UE IP address preservation, Early and/or late notifications about UP path management events, Notification Target Address, immediate reporting flag, Temporal validity condition, Spatial validity condition, User Plane Latency Requirements, Information for EAS IP Replacement in 5GC, Indication for EAS Relocation and AF indication for simultaneous connectivity over source and target PSA at edge relocation, EAS Correlation indication, External Subscriber Category(s), SFC Identifier(s), Metadata, Common EAS IP address, Traffic Correlation ID, FQDN(s) as described in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], HPLMN of the UE. If an IP address of one or more UE(s) is provided, a corresponding port number (e.g. TCP or UPDP) for each IP address. The IP address of one or more UE(s) may be provided together with the corresponding port number allowing to support the case where the PSA UPF is carrying out NAT on the traffic exchanged with the EAS. NOTE 1: When only one DNAI and corresponding routing profile ID(s) and the Indication for EAS Relocation are available, the presented DNAI is the target DNAI as defined in clause 6.3.7 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. NOTE 2: In this Release the following cannot be used by AFs in VPLMN influencing traffic on Home Routed PDU sessions: - External Group Identifier; - External Subscriber Category. Outputs, Required: Operation execution result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.7.2 |
3,525 | 9.2.3.5.2 C-Plane Handling | Cell switch command is conveyed in a MAC CE, which contains the necessary information to perform the LTM cell switch. The overall procedure for LTM is shown in Figure 9.2.3.5.2-1 below. Subsequent LTM is done by repeating the early synchronization, LTM cell switch execution, and LTM cell switch completion steps without releasing other LTM candidate configurations after each LTM cell switch completion. The general procedure over the air interface is applicable to SCG LTM. Further details of SCG LTM can be found in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21]. Figure 9.2.3.5.2-1. Signalling procedure for LTM The procedure for LTM is as follows: 1. The UE sends a MeasurementReport message to the gNB. The gNB decides to configure LTM and initiates LTM preparation. 2. The gNB transmits an RRCReconfiguration message to the UE including the LTM candidate configurations. 3. The UE stores the LTM candidate configurations and transmits an RRCReconfigurationComplete message to the gNB. 4a. The UE performs DL synchronization with the candidate cell(s) before receiving the cell switch command. 4b. When UE-based TA measurement is configured, UE acquires the TA value(s) of the candidate cell(s) by measurement. UE performs early TA acquisition with the candidate cell(s) as requested by the network before receiving the cell switch command as specified in clause 9.2.6. This is done via CFRA triggered by a PDCCH order from the source cell, following which the UE sends preamble towards the indicated candidate cell. In order to minimize the data interruption of the source cell due to CFRA towards the candidate cell(s), the UE does not receive random access response from the network for the purpose of TA value acquisition and the TA value of the candidate cell is indicated in the cell switch command. The UE does not maintain the TA timer for the candidate cell and relies on network implementation to guarantee the TA validity. 5. The UE performs L1 measurements on the configured candidate cell(s) and transmits L1 measurement reports to the gNB. L1 measurement should be performed as long as RRC reconfiguration (step 2) is applicable. 6. The gNB decides to execute cell switch to a target cell and transmits a MAC CE triggering cell switch by including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by candidate configuration index. 7. The UE performs the random access procedure towards the target cell, if UE does not have valid TA of the target cell as specified in clause 6.1.3.xy of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. 8. The UE completes the LTM cell switch procedure by sending RRCReconfigurationComplete message to target cell. If the UE has performed a RA procedure in step 7 the UE considers that LTM cell switch execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE considers that LTM cell switch execution is successfully completed when the UE determines that the network has successfully received its first UL data. The steps 4-8 can be performed multiple times for subsequent LTM using the LTM candidate configuration(s) provided in step 2. The procedure over the air interface described in Figure x is applicable to both intra-gNB-DU LTM and inter-gNB-DU LTM. The overall LTM procedures over F1-C interface are captured in TS 38.401[ NG-RAN; Architecture description ] [4]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.3.5.2 |
3,526 | 8.8.4.1 FDD | For the parameters specified in Table 8.8.4.1-1 the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.8.4.1-2. The purpose of this test is to verify the localized EPDCCH performance, when the EPDCCH transmission in the serving cell is interfered by the CRS of the interfering cells, applying the CRS interference model defined in clause B.6.5. In Table 8.8.4.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.4.1-1: Test Parameters for EPDCCH Table 8.8.4.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.4.1 |
3,527 | 4.3.31 Subscription handling for Aerial UEs | This clause describes subscription information handling in order to support operating Aerial UE function over E-UTRAN as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. The eNodeB supporting Aerial UE function handling uses the per user information supplied by the MME to determine whether or not to allow the UE to use Aerial UE function. Support of Aerial UE function is stored in the user's subscription information in HSS. HSS transfers this information to the MME via Update Location message during Attach and Tracking Area Update procedures. Home Operator may revoke user's subscription authorisation for operating Aerial UEs at any time. MME that supports Aerial UE function provides the user's subscription information on Aerial UE authorisation to the eNodeB via the S1 AP Initial Context Setup Request during Attach, Tracking Area Update and Service Request procedures. For the intra and inter MME S1 based handover (intra RAT) or Inter-RAT handover to E-UTRAN, the Aerial UE subscription information for the user is included in the S1-AP UE Context Modification Request message sent to the target eNodeB after the handover procedure. For X2-based handover, the Aerial UE subscription information for the user is sent to target eNodeB as follows: - If the source eNodeB supports Aerial UE function and the user's Aerial UE subscription information is included in the UE context, the source eNodeB shall include the information in the X2-AP Handover Request message to the target eNodeB. - The MME shall send the Aerial UE subscription information to the target eNodeB in the Path Switch Request Acknowledge message. If the Aerial UE subscription information has changed, the updated Aerial UE subscription information is included in the S1-AP UE Context Modification Request message sent to the eNodeB. | 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.31 |
3,528 | 5.5.2.2 UTRAN Iu mode to E-UTRAN Inter RAT handover 5.5.2.2.1 General | The UTRAN Iu mode to E-UTRAN Inter RAT handover procedure takes place when the network decides to perform a handover. The decision to perform PS handover from UTRAN Iu mode to E-UTRAN is taken by the network based on radio condition measurements reported by the UE to the UTRAN RNC. If emergency bearer services are ongoing for the UE, the MME checks as part of the Tracking Area Update in the execution phase, if the handover is to a restricted area and if so MME releases the non-emergency bearers as specified in clause 5.10.3. If emergency bearer services are ongoing for the UE, the source SGSN evaluates the handover to the target CSG cell independent of the UE's CSG subscription. If the handover is to a CSG cell that the UE is not subscribed, the target eNodeB only accepts the emergency bearers and the target MME releases the non-emergency PDN connections that were not accepted by the target eNodeB as specified in clause 5.10.3. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.2.2 |
3,529 | 4.1.1.1 Types of MM and GMM procedures | Depending on how they can be initiated, three types of MM procedures can be distinguished: 1) MM common procedures: A MM common procedure can always be initiated whilst a RR connection exists. The procedures belonging to this type are: Initiated by the network: - TMSI reallocation procedure; - authentication procedure; - identification procedure; - MM information procedure; - abort procedure. However, abort procedure is used only if an MM connection is being established or has already been established i.e. not during MM specific procedures or during IMSI detach procedure, see subclause 4.3.5. Initiated by the mobile station: - IMSI detach procedure (with the exceptions specified in subclause 4.3.4). 2) MM specific procedures: A MM specific procedure can only be initiated if no other MM specific procedure is running or no MM connection exists. The procedures belonging to this type are: - normal location updating procedure; - periodic updating procedure; - IMSI attach procedure; and - eCall inactivity procedure. 3) MM connection management procedures: These procedures are used to establish, maintain and release a MM connection between the mobile station and the network, over which an entity of the upper CM layer can exchange information with its peer. A MM connection establishment can only be performed if no MM specific procedure is running. More than one MM connection may be active at the same time. Depending on how they can be initiated, three types of GMM procedures can be distinguished: 1) GMM common procedures: In Iu mode, a GMM common procedure can always be initiated whilst a PS signalling connection exists. The procedures belonging to this type are: Initiated by the network when a GMM context has been established: - P-TMSI (re-) allocation; - GPRS authentication and ciphering; - GPRS identification; - GPRS information. 2) GMM specific procedures: Initiated by the network and used to detach the IMSI in the network for GPRS services and/or non-GPRS services and to release a GMM context: - GPRS detach. Initiated by the MS and used to attach or detach the IMSI in the network for GPRS services and/or non-GPRS services and to establish or release a GMM context: - GPRS attach and combined GPRS attach; - GPRS detach and combined GPRS detach; - eCall inactivity procedure. Initiated by the MS when a GMM context has been established: - normal routing area updating and combined routing area updating; - periodic routing area updating. 3) GMM connection management procedures (Iu mode only): Initiated by the MS and used to establish a secure connection to the network and/or to request the resource reservation for sending data: Service Request. The Service Request procedure can only be initiated if no MS initiated GMM specific procedure is ongoing. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.1.1 |
3,530 | 5.2.7.2.3 Nnrf_NFManagement_NFUpdate service operation | Service Operation name: Nnrf_NFManagement_NFUpdate. Description: Provides the updated NF profile of NF consumer to NRF. Inputs, Required: NF instance ID. Inputs, Optional: If replacing the full NF profile, the full NF profile shall be provided. If updating parts of the NF profile, the NF profile elements that needs to be updated shall be provided. Outputs, Required: Result indication. Outputs, Optional: None. See clause 5.21.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the AMF adds or updates the associated GUAMI(s). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.7.2.3 |
3,531 | – SIB4 | SIB4 contains information relevant for inter-frequency cell re-selection (i.e. information about other NR frequencies and inter-frequency neighbouring cells relevant for cell re-selection), which can also be used for NR idle/inactive measurements. The IE includes cell re-selection parameters common for a frequency as well as cell specific re-selection parameters. SIB4 information element -- ASN1START -- TAG-SIB4-START SIB4 ::= SEQUENCE { interFreqCarrierFreqList InterFreqCarrierFreqList, lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ interFreqCarrierFreqList-v1610 InterFreqCarrierFreqList-v1610 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1700 InterFreqCarrierFreqList-v1700 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1720 InterFreqCarrierFreqList-v1720 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1730 InterFreqCarrierFreqList-v1730 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1760 InterFreqCarrierFreqList-v1760 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1800 InterFreqCarrierFreqList-v1800 OPTIONAL -- Need R ]] } InterFreqCarrierFreqList ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo InterFreqCarrierFreqList-v1610 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1610 InterFreqCarrierFreqList-v1700 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1700 InterFreqCarrierFreqList-v1720 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1720 InterFreqCarrierFreqList-v1730 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1730 InterFreqCarrierFreqList-v1760 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1760 InterFreqCarrierFreqList-v1800 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1800 InterFreqCarrierFreqInfo ::= SEQUENCE { dl-CarrierFreq ARFCN-ValueNR, frequencyBandList MultiFrequencyBandListNR-SIB OPTIONAL, -- Cond Mandatory frequencyBandListSUL MultiFrequencyBandListNR-SIB OPTIONAL, -- Need R nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need S absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need S smtc SSB-MTC OPTIONAL, -- Need S ssbSubcarrierSpacing SubcarrierSpacing, ssb-ToMeasure SSB-ToMeasure OPTIONAL, -- Need S deriveSSB-IndexFromCell BOOLEAN, ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, -- Need R q-RxLevMin Q-RxLevMin, q-RxLevMinSUL Q-RxLevMin OPTIONAL, -- Need R q-QualMin Q-QualMin OPTIONAL, -- Need S p-Max P-Max OPTIONAL, -- Need S t-ReselectionNR T-Reselection, t-ReselectionNR-SF SpeedStateScaleFactors OPTIONAL, -- Need S threshX-HighP ReselectionThreshold, threshX-LowP ReselectionThreshold, threshX-Q SEQUENCE { threshX-HighQ ReselectionThresholdQ, threshX-LowQ ReselectionThresholdQ } OPTIONAL, -- Cond RSRQ cellReselectionPriority CellReselectionPriority OPTIONAL, -- Need R cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need R q-OffsetFreq Q-OffsetRange DEFAULT dB0, interFreqNeighCellList InterFreqNeighCellList OPTIONAL, -- Need R interFreqExcludedCellList InterFreqExcludedCellList OPTIONAL, -- Need R ..., [[ mobileIAB-Freq ENUMERATED {true} OPTIONAL -- Need R ]] } InterFreqCarrierFreqInfo-v1610 ::= SEQUENCE { interFreqNeighCellList-v1610 InterFreqNeighCellList-v1610 OPTIONAL, -- Need R smtc2-LP-r16 SSB-MTC2-LP-r16 OPTIONAL, -- Need R interFreqAllowedCellList-r16 InterFreqAllowedCellList-r16 OPTIONAL, -- Cond SharedSpectrum2 ssb-PositionQCL-Common-r16 SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectrum interFreqCAG-CellList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF InterFreqCAG-CellListPerPLMN-r16 OPTIONAL -- Need R } InterFreqCarrierFreqInfo-v1700 ::= SEQUENCE { interFreqNeighHSDN-CellList-r17 InterFreqNeighHSDN-CellList-r17 OPTIONAL, -- Need R highSpeedMeasInterFreq-r17 ENUMERATED {true} OPTIONAL, -- Need R redCapAccessAllowed-r17 ENUMERATED {true} OPTIONAL, -- Need R ssb-PositionQCL-Common-r17 SSB-PositionQCL-Relation-r17 OPTIONAL, -- Cond SharedSpectrum interFreqNeighCellList-v1710 InterFreqNeighCellList-v1710 OPTIONAL -- Cond SharedSpectrum2 } InterFreqCarrierFreqInfo-v1720 ::= SEQUENCE { smtc4list-r17 SSB-MTC4List-r17 OPTIONAL -- Need R } InterFreqCarrierFreqInfo-v1730 ::= SEQUENCE { channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL -- Need R } InterFreqCarrierFreqInfo-v1760 ::= SEQUENCE { frequencyBandList-v1760 MultiFrequencyBandListNR-SIB-v1760 OPTIONAL, -- Need R frequencyBandListSUL-v1760 MultiFrequencyBandListNR-SIB-v1760 OPTIONAL -- Need R } InterFreqCarrierFreqInfo-v1800 ::= SEQUENCE { frequencyBandListAerial-r18 MultiFrequencyBandListNR-Aerial-SIB-r18 OPTIONAL, -- Need S mobileIAB-CellList-r18 PCI-Range OPTIONAL, -- Need R eRedCapAccessAllowed-r18 ENUMERATED {true} OPTIONAL, -- Need R tn-AreaIdList-r18 SEQUENCE (SIZE (1..maxTN-AreaInfo-r18)) OF TN-AreaId-r18 OPTIONAL -- Need R } InterFreqNeighHSDN-CellList-r17 ::= SEQUENCE (SIZE (1..maxCellInter)) OF PCI-Range InterFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo InterFreqNeighCellList-v1610 ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo-v1610 InterFreqNeighCellList-v1710 ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo-v1710 InterFreqNeighCellInfo ::= SEQUENCE { physCellId PhysCellId, q-OffsetCell Q-OffsetRange, q-RxLevMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R q-RxLevMinOffsetCellSUL INTEGER (1..8) OPTIONAL, -- Need R q-QualMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R ... } InterFreqNeighCellInfo-v1610 ::= SEQUENCE { ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16 OPTIONAL -- Cond SharedSpectrum2 } InterFreqNeighCellInfo-v1710 ::= SEQUENCE { ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17 OPTIONAL -- Cond SharedSpectrum2 } InterFreqExcludedCellList ::= SEQUENCE (SIZE (1..maxCellExcluded)) OF PCI-Range InterFreqAllowedCellList-r16 ::= SEQUENCE (SIZE (1..maxCellAllowed)) OF PCI-Range InterFreqCAG-CellListPerPLMN-r16 ::= SEQUENCE { plmn-IdentityIndex-r16 INTEGER (1..maxPLMN), cag-CellList-r16 SEQUENCE (SIZE (1..maxCAG-Cell-r16)) OF PCI-Range } -- TAG-SIB4-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,532 | 5.5.7.1 Start DTMF request by the mobile station | A user may cause a DTMF tone to be generated e.g. by depression of a key in the mobile station. The relevant action is interpreted by the mobile station as a requirement for a DTMF digit to be sent in a START DTMF message on an established FACCH. This message contains the value of the digit to be transmitted (0, 1, ..., 9, A, B, C, D, *, #). Only a single digit will be transferred in each START DTMF message. On sending a START DTMF message the MS shall start timer T336. Where a previous START DTMF message has been sent, another START DTMF message shall only be sent by the MS following receipt of its STOP DTMF ACKNOWLEDGE message (see subclause 5.5.7.4) or a START DTMF REJECT message from the network (see subclause 5.5.7.2) or following the expiry of timers T336 and T337. If timer T336 expires, the MS shall terminate the ongoing DTMF procedure without any retransmissions, and is free to begin another DTMF procedure (e.g. another START DTMF message). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.7.1 |
3,533 | 4.11.3.2 Handover from 5GC-N3IWF to EPS | Figure 4.11.3.2-1: Handover from 5GC-N3IWF to EPS 0. Initial status: one or more PDU Sessions have been established in 5GC between the UE and the SMF/UPF via untrusted non-3GPP access and N3IWF. During PDU Session setup and in addition to what is specified in clause 4.3.2.2.1 and clause 4.3.2.2.2, the AMF includes an indication that EPS interworking is supported to the SMF+PGW-C as specified in clause 4.11.5.3 and the SMF+PGW-C sends the FQDN related to the S5/S8 interface to the HSS+UDM which stores it as described in clause 4.11.5. 1. For the UE to move PDU session(s) from 5GC/N3IWF to EPC/E-UTRAN, the UE's behaviour is as follows: - If the UE is operating in single-registration mode (as described in clause 5.17.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and the UE is registered via 3GPP access to 5GC; - the UE behaves as specified in clause 4.11.1 or 4.11.2 and moves its PDU session from 5GC/N3IWF to EPC/E-UTRAN using the PDN connection establishment with "Handover" indication procedure as described in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. - otherwise, i.e. either the UE is operating in single registration mode and is not registered via 3GPP access to 5GC, or the UE is operating in dual registration mode; and - if the UE is not attached to EPC/E-UTRAN, the UE initiates Handover Attach procedure in E-UTRAN as described in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] for a non-3GPP to EPS handover with "Handover" indication, except note 17. - otherwise (i.e. the UE is attached to EPC/E-UTRAN), the UE initiates the PDN Connection establishment with "Handover" indication procedure as described in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 2. The combined PGW+SMF/UPF initiates a network requested PDU Session Release via untrusted non-3GPP access and N3IWF according to Figure 4.12.7-1 steps 3 to 12 to release the 5GC and N3IWF resources with the following exception: - the H-SMF indicates in the Nsmf_PDUSession_Update Request that the UE shall not be notified. This shall result in the V-SMF not sending the N1 SM Container (PDU Session Release Command) to the UE. - Nsmf_PDUSession_StatusNotify service operation invoked by H-SMF to V-SMF indicates the PDU Session is moved to a different system; - Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the (V-)SMF indicates the PDU Session is moved to another system. - The Npcf_SMPolicyControl_Delete service operation to PCF shall not be performed. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.3.2 |
3,534 | 5.43.3 Local switch for UE-to-UE communications via UPF deployed on GEO satellite 5.43.3.1 General | The UE to UE traffic may be locally routed by UPF(s) deployed on satellite (i.e. through local switch) to the target UE without traversing back to the satellite gateway on the ground. Local switching via UPF(s) deployed on satellite in this clause only applies on GEO satellite backhaul case and considers only DNNs and slices for 5G VN. N19 tunnel may be established between two UPFs deployed on different satellites for traffic between UEs. Also, N6 may be used for carrying traffic between UPFs deployed on different satellites. Only a single SMF is supported for local switching and N19 forwarding, i.e. both UEs are served by the same SMF. NOTE: The latency optimisation that can be gained by inter-satellite link between UPFs on different GEO satellites depends on the distance between the satellites that can be substantial, depending on the number of deployed satellites. Clause 5.43.3.2 describes the case of PSA UPF deployed on satellite, clause 5.43.3.3 describes the case of UL CL/BP and local PSA deployed on satellite (PSA UPF is on the ground). Selection of PSA UPF or UL CL/BP/local PSA on satellite is described in clause 6.3.3 and determination of DNAI to select the UPF deployed on the corresponding GEO satellite reuses the mechanism described in clause 5.43.2. A combination of DNN/S-NSSAI is assigned by the operator for the communications between UEs where backhaul with UPF is deployed on GEO satellite, the URSP is described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and its configuration to enable the selection PSA UPF on the GEO satellite reuses the mechanism described in clause 5.43.2. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.43.3 |
3,535 | 16.19.2.2 Timing Advance | For the serving cell, the network broadcasts coarse gNB location information. The UE shall have valid GNSS position as well as gNB location before connecting to an ATG cell. To achieve synchronisation, before and during connection to an ATG cell, the UE shall compute the RTT between UE and the gNB based on the GNSS position and the gNB location parameters, and autonomously pre-compensate the TTA for the RTT between the UE and the gNB. In connected mode, the UE shall be able to continuously update the Timing Advance. The UE may be configured to report Timing Advance during Random Access procedures or in connected mode. For an RRC_CONNECTED UE, event-triggered reporting of the Timing Advance is supported. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.19.2.2 |
3,536 | 5.4.3.1 Logical channel prioritization | The Logical Channel Prioritization procedure is applied when a new transmission is performed. RRC controls the scheduling of uplink data by signalling for each logical channel: priority where an increasing priority value indicates a lower priority level, prioritisedBitRate which sets the Prioritized Bit Rate (PBR), bucketSizeDuration which sets the Bucket Size Duration (BSD), and optionally allowedTTI-Lengths which sets the allowed TTI lengths. For NB-IoT, prioritisedBitRate, bucketSizeDuration and the corresponding steps of the Logical Channel Prioritisation procedure (i.e., Step 1 and Step 2 below) are not applicable. The MAC entity shall maintain a variable Bj for each logical channel j. Bj shall be initialized to zero when the related logical channel is established, and incremented by the product PBR × TTI duration for each TTI, where PBR is Prioritized Bit Rate of logical channel j. However, the value of Bj can never exceed the bucket size and if the value of Bj is larger than the bucket size of logical channel j, it shall be set to the bucket size. The bucket size of a logical channel is equal to PBR × BSD, where PBR and BSD are configured by upper layers. Before the successful completion of the contention based Random Access procedure initiated for DAPS handover, the target MAC entity shall not select the logical channel(s) corresponding to non-DAPS DRB(s) for the uplink grant received in a Random Access Response. The source MAC entity shall select only the logical channel(s) corresponding to DAPS DRB(s) during DAPS handover. The MAC entity shall perform the following Logical Channel Prioritization procedure when a new transmission is performed on an UL grant with a certain TTI length: - The MAC entity shall allocate resources to the logical channels that are allowed to transmit using the TTI length of the grant, in the following steps: - Step 1: All the allowed logical channels with Bj > 0 are allocated resources in a decreasing priority order. If the PBR of a logical channel is set to "infinity", the MAC entity shall allocate resources for all the data that is available for transmission on the logical channel before meeting the PBR of the lower priority logical channel(s); - Step 2: the MAC entity shall decrement Bj by the total size of MAC SDUs served to logical channel j in Step 1; NOTE 1: The value of Bj can be negative. - Step 3: if any resources remain, all the allowed logical channels are served in a strict decreasing priority order (regardless of the value of Bj) until either the data for that logical channel or the UL grant is exhausted, whichever comes first. Logical channels configured with equal priority should be served equally. - The UE shall also follow the rules below during the scheduling procedures above: - the UE should not segment an RLC SDU (or partially transmitted SDU or retransmitted RLC PDU) if the whole SDU (or partially transmitted SDU or retransmitted RLC PDU) fits into the remaining resources of the associated MAC entity; - if the UE segments an RLC SDU from the logical channel, it shall maximize the size of the segment to fill the grant of the associated MAC entity as much as possible; - the UE should maximise the transmission of data. - if the MAC entity is given an UL grant size that is equal to or larger than 4 bytes while having data available for transmission, the MAC entity shall not transmit only padding BSR and/or padding (unless the UL grant size is less than 7 bytes and an AMD PDU segment needs to be transmitted); - for transmissions on serving cells operating according to Frame Structure Type 3, the MAC entity shall only consider logical channels for which laa-UL-Allowed has been configured; - if a logical channel has been configured with lch-CellRestriction and if PDCP duplication within the same MAC entity (i.e. CA duplication) is activated, for this logical channel the MAC entity shall consider the cells indicated by lch-CellRestriction to be restricted for transmission. - the MAC entity shall map the logical channel configured with allowedHARQ-mode to the HARQ process with corresponding UL HARQ mode for transmission. - for NB-IoT UEs, BL UEs or UEs in enhanced coverage, if edt-SmallTBS-Enabled is set to TRUE for the corresponding PRACH resource, the UE shall choose a TB size among the set of possible TB sizes as described in clauses 8.6.2 and 16.3.3 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] The MAC entity shall not transmit data for a logical channel corresponding to a radio bearer that is suspended (the conditions for when a radio bearer is considered suspended are defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). If the MAC PDU includes only the MAC CE for padding BSR or periodic BSR with zero MAC SDUs and there is no aperiodic CSI requested for this TTI, as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], the MAC entity shall not generate a MAC PDU for the HARQ entity in the following cases: - in case the MAC entity is configured with skipUplinkTxDynamic and the grant indicated to the HARQ entity was addressed to a C-RNTI; or - in case the MAC entity is configured with skipUplinkTxSPS and the grant indicated to the HARQ entity is a configured uplink grant activated by the MAC entity's Semi-Persistent Scheduling C-RNTI or by the MAC entity's UL Semi-Persistent Scheduling V-RNTI; or - in case the grant indicated to the HARQ entity is a configured uplink grant activated by the MAC entity's AUL C-RNTI; or - in case the grant indicated to the HARQ entity is a preconfigured uplink grant. NOTE 1a: If at least one MAC PDU is to be generated for the HARQ entity for this TTI, the MAC entity generates MAC PDUs corresponding to all UL grants indicated to the HARQ entity for this TTI. For the Logical Channel Prioritization procedure, the MAC entity shall take into account the following relative priority in decreasing order: - MAC control element for C-RNTI or data from UL-CCCH; - MAC control element for DPR; - MAC control element for SPS confirmation; - MAC control element for AUL confirmation; - MAC control element for Timing Advance Report; - MAC control element for GNSS Validity Duration Report; - MAC control element for BSR, with exception of BSR included for padding; - MAC control element for PHR, Extended PHR, or Dual Connectivity PHR; - MAC control element for Sidelink BSR, with exception of Sidelink BSR included for padding; - MAC control element for DCQR and AS RAI, with exception of when DCQR is to be included in Msg3; - data from any Logical Channel, except data from UL-CCCH; - MAC control element for DCQR and AS RAI, when DCQR is to be included in Msg3; - MAC control element for Recommended bit rate query; - MAC control element for BSR included for padding; - MAC control element for Sidelink BSR included for padding. When AS RAI has been triggered, DCQR and AS RAI MAC control element shall have higher priority than data from any Logical Channel, except data from UL-CCCH, only if after logical channel prioritization including AS RAI in the resulting MAC PDU does not require segmenting RLC SDU. Otherwise data from any Logical Channel shall have higher priority than DCQR and AS RAI MAC control element. NOTE 2: When the MAC entity is requested to transmit multiple MAC PDUs in one TTI, steps 1 to 3 and the associated rules may be applied either to each grant independently or to the sum of the capacities of the grants. Also the order in which the grants are processed is left up to UE implementation. It is up to the UE implementation to decide in which MAC PDU a MAC control element is included when MAC entity is requested to transmit multiple MAC PDUs in one TTI. When the UE is requested to generate MAC PDU(s) in two MAC entities in one TTI, it is up to UE implementation in which order the grants are processed. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.3.1 |
3,537 | 4.2.4 Behaviour in state GMM-DEREGISTERED | The state GMM-DEREGISTERED is entered when: - the MS is switched on; - the GPRS capability has been enabled in the MS; - a GPRS detach or combined GPRS detach procedure has been performed; - a GMM procedure has failed (except routing area updating, see subclause 4.7.5); or - the MS attached for emergency bearer services is in PMM-IDLE mode and its periodic routing area update timer expires (see subclause 4.7.2.2). The selection of the appropriate substate of GMM-DEREGISTERED after switching on is described in subclause 4.2.4.1. The specific behaviour of the MS in state GMM-DEREGISTERED is described in subclause 4.2.4.2. The substate chosen when the GMM-DEREGISTERED state is returned to from another state except state GMM-NULL is described in subclause 4.2.4.3. It should be noted that transitions between the various substates of GMM-DEREGISTERED are caused by (e.g.): - insertion or removal of the SIM/USIM; - cell selection/reselection (see also 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]); - PLMN search; - loss/regain of coverage; or - change of RA. How various GMM procedures affect the GMM-DEREGISTERED substates and the GPRS update status is described in the detailed description of the GMM procedures in subclause 4.7. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.4 |
3,538 | 4.7.2.1.2 Handling of READY timer in the MS in Iu mode and S1 mode | The READY timer is not applicable for Iu mode in S1 mode. Upon completion of a successful GPRS attach or routing area updating procedure in Iu mode, the MS shall stop the READY timer, if running. Upon completion of a successful EPS attach or tracking area updating procedure, the MS shall stop the READY timer, if running. In Iu mode, an MS may indicate a READY timer value to the network in the ATTACH REQUEST and the ROUTING AREA UPDATE REQUEST messages. If a READY timer value is received by an MS capable of both Iu mode and A/Gb mode in the ATTACH ACCEPT or the ROUTING AREA UPDATE ACCEPT message, then the MS shall store the received value in order to use it at an intersystem change from Iu mode to A/Gb mode. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.2.1.2 |
3,539 | 9.5.2.1 FDD | The minimum performance requirement in Table 9.5.2.1-2 is defined as a) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be ≥ ; b) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 2 shall be ≥ ; For the parameters specified in Table 9.5.2.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.5.2.1-2. Table 9.5.2.1-1: RI Test (FDD) Table 9.5.2.1-2: Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.5.2.1 |
3,540 | 5.7.3b.2 Initiation | In case of MR-DC, a UE configured with split SRB1 or SRB3 initiates the procedure to report MCG failures when neither MCG nor SCG transmission is suspended, the SCG is not deactivated, t316 is configured, and when the following condition is met; or In case of MP, a MP remote UE configured with split SRB1 initiates the procedure to report direct path failures when neither MCG (i.e. direct path) nor indirect path transmission is suspended, t316 is configured, and when the following condition is met: 1> upon detecting radio link failure of the MCG, in accordance with 5.3.10.3, while T316 is not running. Upon initiating the procedure, the UE shall: 1> stop timer T310 for the PCell, if running; 1> stop timer T312 for the PCell, if running; 1> suspend MCG transmission for all SRBs, DRBs, multicast MRBs, except SRB0, and, if any, BH RLC channels; 1> reset MCG MAC; 1> stop conditional reconfiguration evaluation for CHO, if configured; 1> stop conditional reconfiguration evaluation for CPC or subsequent CPAC, if configured; 1> initiate transmission of the MCGFailureInformation message in accordance with 5.7.3b.4. NOTE: The handling of any outstanding UL RRC messages during the initiation of the fast MCG link recovery is left to UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3b.2 |
3,541 | 6.10.2.2.1 Mapping to resource elements for 15 kHz and 7.5 kHz subcarrier spacing | The reference-signal sequence in OFDM symbol shall be mapped to complex-valued modulation symbols with according to where Figure 6.10.2.2-1 illustrates the resource elements used for MBSFN reference signal transmission in case of . In case of , the MBSFN reference signal shall be mapped to resource elements according to Figure 6.10.2.2-3. The notation is used to denote a resource element used for reference signal transmission on antenna port. Figure 6.10.2.2-1: Mapping of MBSFN reference signals (extended cyclic prefix, ) Figure 6.10.2.2-3: Mapping of MBSFN reference signals (extended cyclic prefix, ) | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.10.2.2.1 |
3,542 | 24.3.2 Format of PLMN ID in ProSe Application Code | The PLMN ID in the ProSe Application Code is composed as shown in Figure 24.3.2-1: Figure 24.3.2-1: Structure of PLMN ID in ProSe Application Code The PLMN-ID is composed of four parts: - Scope indicates whether the MNC, or both the MCC and the MNC, or neither are wild carded in the ProSe Application ID associated with the ProSe Application Code, with the following mapping: 00 global scope. 01 reserved. 10 country-specific scope. 11 PLMN-specific scope. - Spare bit that shall be set to 0 and shall be ignored if set to 1. - E bit indicates whether the MCC and the MNC of the ProSe Function that has assigned the ProSe Application Code are included in the PLMN ID in ProSe Application Code, with the following mapping: 0 Neither MCC nor MNC is included. 1 MCC and MNC included. - When present, the MCC and the MNC shall each have a fixed length of 10 bits and shall be coded as the binary representation of their decimal value. In this release, the MCC and the MNC of the ProSe Function that has assigned the ProSe Application Code shall always be included in the PLMN ID in ProSe Application Code. The E bit shall always be set to 1. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.3.2 |
3,543 | 5.32.6.3.1 ATSSS-LL Functionality | The ATSSS-LL functionality in the UE does not apply a specific protocol. It is a data switching function, which decides how to steer, switch and split the uplink traffic across 3GPP and non-3GPP accesses, based on the provisioned ATSSS rules and local conditions (e.g. signal loss conditions). The ATSSS-LL functionality in the UE may be applied to steer, switch and split all types of traffic, including TCP traffic, UDP traffic, Ethernet traffic, etc. The ATSSS-LL functionality does not support the Redundant Steering Mode. The ATSSS-LL functionality may be enabled in the UE when the UE provides an "ATSSS-LL capability" during the PDU Session Establishment procedure. The ATSSS-LL functionality is mandatory in the UE for MA PDU Session of type Ethernet. In addition: - When the UE neither supports the MPTCP functionality nor the MPQUIC functionality, the ATSSS-LL functionality is mandatory in the UE for an MA PDU Session of type IP. - When the UE supports the MPTCP functionality and does not support the MPQUIC functionality, the ATSSS-LL functionality with Active-Standby Steering Mode is mandatory in the UE for an MA PDU Session of type IP to support non-MPTCP traffic. - When the UE supports the MPQUIC functionality and does not support the MPTCP functionality, the ATSSS-LL functionality with Active-Standby Steering Mode is mandatory in the UE for an MA PDU Session of type IP to support non-MPQUIC traffic. - When the UE supports both the MPTCP functionality and the MPQUIC functionality, the ATSSS-LL functionality with Active-Standby Steering Mode is mandatory in the UE for an MA PDU Session of type IP to support non-MPTCP and non-MPQUIC traffic. The network shall also support the ATSSS-LL functionality as defined for the UE. The ATSSS-LL functionality in the UPF is enabled for a MA PDU Session by ATSSS-LL functionality indication received in the Multi-Access Rules (MAR). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.6.3.1 |
3,544 | 5.5.2.3.4 E-UTRAN to GERAN A/Gb mode Inter RAT handover reject | The Target BSS may reject the use of the Handover procedure if none of the requested PFCs in the PS Handover Request message could be established. In this case no UE context is established in the target SGSN/BSS and no resources are allocated. The UE remains in the Source eNodeB/MME. Figure 5.5.2.3.4-1: E-UTRAN to GERAN A/Gb Inter RAT HO reject 1. Steps 1 to 5 in the flow are identical to the ones in clause 5.5.2.3.2. 6. If the Target BSS fails to allocate any resources for any of the requested PFCs it sends a PS Handover Request Nack (Cause) message to the Target SGSN. When the Target SGSN receives the PS Handover Request Nack message from Target BSS the Target SGSN clears any reserved resources for this UE. 7. This step is only performed for Serving GW relocation, i.e. if Steps 4/4a have been performed. The Target SGSN deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages. 8. The Target SGSN sends the Forward Relocation Response (Cause) message to the Source MME. 9. When the Source MME receives the Forward Relocation Response message it send a Handover Preparation Failure (Cause) message to the Source eNodeB. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.2.3.4 |
3,545 | 28.4.3 Ranges of S-NSSAIs | In the 5G Core Network, an NF Instance may indicate (e.g., while registering its NF profile in the NRF) support for several S-NSSAIs having a common SST value and different SDs, by including such SST value and adding, either a list of ranges of SDs, or a "wildcard" flag representing all SD values for the common SST (see 3GPP TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [129], clause 5.4.5.1). For an NF registering a list of supported S-NSSAIs in terms of ranges of SDs, or wildcard, the NF may associate a common network slicing policy (such as, e.g., for an AMF to assign a specific DNN to be used with a certain slice) to all S-NSSAIs derived from that SD range. NOTE: The usage of SD ranges to define sets of S-NSSAIs is restricted to be used only by certain protocols/APIs in the 5G Core Network (e.g., NRF, NSSF, AMF…). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.4.3 |
3,546 | 9.11.2.6 Intra N1 mode NAS transparent container | The purpose of the Intra N1 mode NAS transparent container information element is to provide the UE with parameters that enable the UE to handle the 5G NAS security context after N1 mode to N1 mode handover. The Intra N1 mode NAS transparent container information element is coded as shown in figure 9.11.2.6.1 and table 9.11.2.6.1. The Intra N1 mode NAS transparent container is a type 4 information element with a length of 9 octets. The value part of the Intra N1 mode NAS transparent container information element is included in specific information elements within some RRC messages sent to the UE. NOTE: For these cases the coding of the information element identifier and length information of RRC is defined in 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]. Figure 9.11.2.6.1: Intra N1 mode NAS transparent container information element Table 9.11.2.6.1: Intra N1 mode NAS transparent container information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.2.6 |
3,547 | 5.3.8 Abnormal cases in the UE | The following abnormal case can be identified: a) EMM uplink message transmission failure indication by lower layers When it is specified in the relevant procedure that it is up to the UE implementation to rerun the ongoing procedure that triggered that procedure, the procedure can typically be re-initiated using a retransmission mechanism of the uplink message (the one that has previously failed to be transmitted) with new sequence number and message authentication code information thus avoiding to restart the whole procedure. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.8 |
3,548 | 4.7.4.2.1 Network initiated GPRS detach procedure initiation | The network initiates the GPRS detach procedure by sending a DETACH REQUEST message to the MS. The DETACH REQUEST message shall include a detach type IE. In addition, the network may include a cause IE to specify the reason for the detach request. The network shall start timer T3322. If the detach type IE indicates "re-attach required", or "re-attach not required" and the cause code is not #2 "IMSI unknown in HLR", the network shall deactivate the PDP contexts, the MBMS contexts and deactivate the logical link(s), if any, and shall change to state GMM-DEREGISTERED-INITIATED. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.4.2.1 |
3,549 | 6.16.1 Description | A key aspect of 5G system flexibility is the ability to support both the very high-end markets as well as very low-end markets. Some systems will be deployed in areas where there are constraints on energy resources (e.g. sporadic access to power) and lower end user expectations for availability, reliability, and data rates. In such cases, the system needs additional flexibility to adapt power consumption needs based on fluctuations in power availability. The system should be efficient in order to provide essential services in harsh environments (e.g. far remote rural areas, very large territories) while taking into account the local constraints (adapting resources consumptions to long distances, dealing with variable conditions and possibly disconnections). Content delivery should be optimized in order to reduce constraints on transport networks, on low-end UEs (e.g. small screen, limited energy consumption), variable network conditions, and client profiles. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.16.1 |
3,550 | 7.2.2 Message too long | The maximum size of a NAS message for NR connected to 5GCN is specified in 3GPP TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [29]. The maximum size of a NAS message for E-UTRA connected to 5GCN is specified 3GPP TS 36.323[ Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification ] [25]. The maximum size of a NAS message for non-3GPP access connected to 5GCN is specified in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18] | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.2.2 |
3,551 | 4.14.2.4 Number of successful WLAN releases from the LWIP WLAN mobility set | a) This measurement provides the number of successful WLAN releases from the LWIP WLAN mobility set. b) CC c) On receipt of RRCConnectionReconfigurationComplete message corresponding to transmitted RRCConnectionReconfiguration message which includes the wlan-ToReleaseList in the lwip-MobilityConfig of lwip-Configuration information element (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). d) An integer value e) LWI.LwipWlanRelSucc f) WLANMobilitySet g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.14.2.4 |
3,552 | 5.21.3.2 NF Set and NF Service Set | Equivalent Control Plane NFs may be grouped into NF Sets, e.g. several SMF instances are grouped into an SMF Set. NFs within a NF Set are interchangeable because they share the same context data, and may be deployed in different locations, e.g. different data centres. In the case of SMF, multiple instances of SMFs within an SMF Set need to be connected to the same UPF: - If the N4 association is established between a SMF instance and an UPF, each N4 association is only managed by the related SMF instance. - If only one N4 association is established between a SMF Set and an UPF, any SMF in the SMF Set should be able to manage the N4 association with the UPF. Furthermore, for a given UE and PDU Session any SMF in the SMF Set should be able to control the N4 session with the UPF (however, at any given time, only one SMF in the SMF Set will control the UPF for a given UE's PDU Session). A Control Plane NF is composed of one or multiple NF Services. Within a NF a NF service may have multiple instances. These multiple NF Service instances can be grouped into NF Service Set if they are interchangeable with each other because they share the same context data. NOTE: The actual mapping of instances to a given Set is up to deployment. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.3.2 |
3,553 | 4.3.2.2.3 Rating Function | The Rating Function (RF) determines the value of the network resource usage (described in the charging event received by the OCF from the network) on behalf of the OCF. To this end, the OCF furnishes the necessary information, obtained from the charging event, to the RF and receives in return the rating output (monetary or non-monetary units), via the Re reference point. The RF may handle a wide variety of rateable instances, such as: - Rating of data volume (e.g. based on charging initiated by an access network entity, i.e. on the bearer level); - Rating of session / connection time (e.g. based on charging initiated by a SIP application, i.e. on the subsystem level); - Rating of service events (e.g. based on charging of web content or MMS, i.e. on the service level). | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.2.2.3 |
3,554 | 4.3.4.1 Non-roaming architecture | Figure 4.3.4.1-1 represents the non-roaming architecture for interworking between ePDG/EPC and 5GS. Figure 4.3.4.1-1: Non-roaming architecture for interworking between ePDG/EPC and 5GS NOTE 1: The details of the interfaces between the UE and the ePDG, and between EPC nodes (i.e. SWm, SWx, S2b and S6b), are documented in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43]. NOTE 2: Interworking with ePDG is only supported with GTP based S2b. S6b interface is optional (see clause 4.11.4.3.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.4.1 |
3,555 | 5.3.3 User data and signalling data integrity | The gNB shall support integrity protection and replay protection of user data between the UE and the gNB. The gNB shall activate integrity protection of user data based on the security policy sent by the SMF. The gNB shall support integrity protection and replay protection of RRC-signalling. The gNB shall support the following integrity protection algorithms: - NIA0, 128-NIA1, 128-NIA2 as defined in Annex D of the present document. The gNB may support the following integrity protection algorithm: - 128-NIA3 as defined in Annex D of the present document. Integrity protection of the user data between the UE and the gNB is optional to use, and shall not use NIA0. NOTE: Integrity protection of user plane adds the overhead of the packet size and increases the processing load both in the UE and the gNB. NIA0 will add an unnecessary overhead of 32-bits MAC with no security benefits. All RRC signalling messages except those explicitly listed in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [22] as exceptions shall be integrity-protected with an integrity protection algorithm different from NIA0, except for unauthenticated emergency calls. NIA0 shall be disabled in gNB in the deployments where support of unauthenticated emergency session is not a regulatory requirement. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.3.3 |
3,556 | 6.1.3.6b Dual Connectivity Power Headroom Report MAC Control Element | The Dual Connectivity Power Headroom Report (PHR) MAC control element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2. It has a variable size and is defined in Figure 6.1.3.6b-1 and Figure 6.1.3.6b-2. One octet with Ci fields is used for indicating the presence of PH per serving cell other than PCell, when the highest SCellIndex of SCell with configured uplink is less than 8, otherwise four octets are used. In case EN-DC, NE-DC or NGEN-DC is configured, four octets with Ci fields is always used. When Type 2 PH is reported for the PCell, the octet containing the Type 2 PH field is included first after the octet(s) indicating the presence of PH per cell (PSCell and all SCells of all MAC entities) and followed by an octet containing the associated PCMAX,c field (if reported). Then after that, when Type 2 PH is reported for the PSCell, the octet containing the Type 2 PH field is included followed by an octet containing the associated PCMAX,c field (if reported). Then follows an octet with the Type 1 PH field and an octet with the associated PCMAX,c field (if reported), for the PCell. If SRS-ConfigAdd-r16 is configured for the PCell then follows an octet with the Type 3 PH field and an octet with the associated PCMAX,c field (if reported), for the PCell. And then follows in ascending order based on the ServCellIndex, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], an octet with the Type x PH field, wherein x is either 1 or 3 according to TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] and TS 38.213[ NR; Physical layer procedures for control ] [18] and an octet with the associated PCMAX,c field (if reported), for all serving cells of all MAC entities indicated in the bitmap. In case of EN-DC and NGEN-DC, for serving cells in the other MAC entity in which the UE does not support dynamic power sharing or dynamic power sharing is not applicable (clause 4.2.7.9, TS 38.306[ NR; User Equipment (UE) radio access capabilities ] [22]), the UE may omit the octets containing Power Headroom field and PCMAX,c field for those serving cells. In case of NE-DC, for serving cells in the other MAC entity in which the UE does not support dynamic power sharing or dynamic power sharing is not applicable, the UE may omit the octets containing Power Headroom field and PCMAX,f,c field for those serving cells except for the PCell in the other MAC entity and the reported values of Power Headroom and PCMAX,f,c for the PCell are up to UE implementation. The Dual Connectivity PHR MAC Control Element is defined as follows: - Ci: this field indicates the presence of a PH field for the serving cell of any MAC entity, except the PCell, with ServCellIndex (for EN-DC, NE-DC or NGEN-DC case) or SCellIndex i as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. The Ci field set to "1" indicates that a PH field for the serving cell with ServCellIndex (for EN-DC, NE-DC or NGEN-DC case) or SCellIndex i is reported. The Ci field set to "0" indicates that a PH field for the serving cell with ServCellIndex (for EN-DC, NE-DC or NGEN-DC case) or SCellIndex i is not reported; - R: reserved bit, set to "0"; - V: this field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, V=0 indicates real transmission on PUSCH and V=1 indicates that a PUSCH reference format is used. For Type 2 PH, V=0 indicates real transmission on PUCCH and V=1 indicates that a PUCCH reference format is used. For Type 3 PH, V=0 indicates real transmission on SRS and V=1 indicates that an SRS reference format is used. Furthermore, for Type 1 ,Type 2 and Type 3 PH, V=0 indicates the presence of the octet containing the associated PCMAX,c field, and V=1 indicates that the octet containing the associated PCMAX,c field is omitted. Whether the reported PH value for an activated NR Serving Cell is based on real transmission or a reference format is determined based on UL transmissions that have been scheduled or configured until 4 ms prior to the TTI in which this PHR MAC CE is transmitted; - Power Headroom (PH): this field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 (the corresponding measured values in dB for the E-UTRA Serving Cell are specified in clause 9.1.8.4 of TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9] while the corresponding measured values in dB for the NR Serving Cell are specified in TS 38.133[ NR; Requirements for support of radio resource management ] [19]); - P: this field indicates whether power backoff due to power management is applied (as allowed by P-MPRc, see TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [10] and TS 38.101[ None ] -3 [21]). The MAC entity shall set P=1 if the corresponding PCMAX,c field would have had a different value if no power backoff due to power management had been applied; - PCMAX,c: if present, this field indicates the PCMAX,c or , as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] for the E-UTRA Serving Cell and the PCMAX,f,c or P̃CMAX,f,c, as specified in TS 38.213[ NR; Physical layer procedures for control ] [18]) for the NR Serving Cell used for calculation of the preceding PH field. The reported PCMAX,c and the corresponding nominal UE transmit power levels are shown in Table .6a-1 (the corresponding measured values in dBm for the E-UTRA Serving Cell can be found in TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9] while the corresponding measured values in dBm for the NR Serving Cell can be found in TS 38.133[ NR; Requirements for support of radio resource management ] [19]). Figure 6.1.3.6b-1: Dual Connectivity PHR MAC Control Element Figure 6.1.3.6b-2: Dual Connectivity PHR MAC Control Element supporting 32 serving cells with configured uplink | 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 | 6.1.3.6b |
3,557 | 5.2.2.5 Namf_Location service 5.2.2.5.1 General | Service description: This service enables an NF to request location information for a target UE. The following are the key functionalities of this NF service. - Allow NFs to request the current or last known geodetic and optionally local and/or civic location of a target UE. - Allow NFs to be notified of event information related to emergency sessions or deferred UE location. - Allow NFs to request Network Provided Location Information (NPLI) and/or local time zone corresponding to the location of a target UE. - Allow NFs to request a deferred geodetic and optionally local and/or civic location of a target UE for Periodic, Triggered and UE Available Location Events. - Allow NFs to cancel an ongoing session for periodic or triggered location of a target UE. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.5 |
3,558 | 5.15.19 Support of Network Slice Replacement | The Network Slice Replacement feature is used to temporarily replace an S-NSSAI with an Alternative S-NSSAI when an S-NSSAI becomes unavailable or congested. The Network Slice Replacement may be triggered in the following cases: - If the NSSF detects that an S-NSSAI becomes unavailable or congested (e.g. based on OAM or NWDAF analytics output), it sends network slice availability notification for the S-NSSAI to the AMF. The notification may include an Alternative S-NSSAI which can be used by the AMF to replace the S-NSSAI. The NSSF notifies the AMF when the S-NSSAI is available again. - If the PCF detects that an S-NSSAI becomes unavailable or congested for a UE (e.g. based on OAM or NWDAF analytics output), it sends access and mobility related policy notification to the AMF. The notification may include an Alternative S-NSSAI which can be used by the AMF to replace the S-NSSAI. The PCF notifies the AMF when the S-NSSAI is available again for the UE. - The OAM sends notification to AMF when an S-NSSAI becomes unavailable or congested (and also when this S-NSSAI becomes available again) and provides the Alternative S-NSSAI to AMF. The network slice associated with the Alternative S-NSSAI is assumed in this specification to have NS-AoS to be covering at least the NS-AoS of the replaced network slice. NOTE 1: It is recommended to use a network slice associated with the Alternative S-NSSAI that is able to support requirements for the services that the replaced network slice supports. NOTE 2: There are no means for the PLMN to prevent the UE from obtaining service in the Alternative network slice in cells outside the NS-AoS of the replaced network slice but within the NS-AoS of the Alternative network slice if the Alternative network slice NS-AoS exceeds the NS-AoS of the replaced network slice. Based on the notification above from NSSF or PCF or OAM, the AMF may determine that an S-NSSAI is to be replaced with Alternative S-NSSAI. For roaming case, the AMF subscribes the network slice availability notification of the HPLMN S-NSSAI from the NSSF in VPLMN and the NSSF in VPLMN subscribes the notification from NSSF in the HPLMN as described in clause 5.15.6. NOTE 3: It is recommended that, the operator configures to use only one option, i.e. OAM, PCF or NSSF, for determining an Alternative S-NSSAI and triggering the Network Slice Replacement for S-NSSAI. The AMF uses the Alternative S-NSSAI received in the notification from the NSSF, or from OAM or from the PCF If the NSSF or PCF or OAM do not provide an Alternative S-NSSAI in the notification, the AMF uses an Alternative S-NSSAI based on local configuration. The Alternative S-NSSAI shall be supported in the UE Registration Area. If AMF cannot determine the Alternative S-NSSAI for the S-NSSAI, e.g. OAM or NSSF doesn't provide Alternative S-NSSAI and there is no Alternative S-NSSAI in the AMF local configuration, the AMF may further interact with the PCF to determine the Alternative S-NSSAI. The event trigger in AMF for interacting with PCF is described in clause 6.1.2.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. If the Alternative S-NSSAI is subject to NSSAA, the Alternative S-NSSAI shall only be used for UEs for which the Alternative S-NSSAI is included in the Subscribed S-NSSAIs. In this case, the AMF performs the NSSAA procedure for the Alternative S-NSSAI as described in clause 5.15.10 before the AMF triggers Network Slice Replacement as specified below. The UE indicates the support of Network Slice Replacement feature during the UE Registration procedure. For supporting UE in CM-CONNECTED state and if there is a PDU Sessions in the UE context associated with the S-NSSAI that needs to be replaced, the AMF additionally provides the Alternative S-NSSAI for this S-NSSAI in the Allowed NSSAI and in the Configured NSSAI, if not included yet, and the mapping between S-NSSAI(s) to Alternative S-NSSAI(s) to the UE in UE Configuration Update message as follows: - for non-roaming UEs, the AMF provides the mapping of the S-NSSAI to the Alternative S-NSSAI to the UE. NOTE 4: In the non-roaming case, the Alternative S-NSSAI does not have to be a Subscribed S-NSSAIs, as the replaced S-NSSAI is always a subscribed S-NSSAI. - for roaming UEs when the VPLMN S-NSSAI has to be replaced by a VPLMN Alternative S-NSSAI, the AMF provides the mapping of the VPLMN S-NSSAI to the Alternative VPLMN S-NSSAI to the UE. - for roaming UEs when the HPLMN S-NSSAI has to be replaced by an Alternative HPLMN S-NSSAI, the AMF provides the mapping of the HPLMN S-NSSAI to the Alternative HPLMN S-NSSAI to the UE. NOTE 5: In the roaming cases, the Alternative HPLMN S-NSSAI does not have to be one of the Subscribed S-NSSAIs as the replaced HPLMN S-NSSAI is always part of the Subscribed S-NSSAIs. For the supporting UE when the UE has a NAS signalling connection, i.e. it is CM-CONNECTED or it has become CM-CONNECTED, e.g. through a Service Request procedure or through a UE registration procedure, if the AMF determines that the S-NSSAI is to be replaced and there is a PDU Session associated with the S-NSSAI in the UE context (see also NOTE 3), the AMF sends the mapping of the S-NSSAI to the Alternative S-NSSAI to the UE in the UE Configuration Update message or in the Registration Accept message. NOTE 6: It is left to AMF local policy whether to send the mapping of the S-NSSAI to the Alternative S-NSSAI to the UE when there is no PDU session associated with the S-NSSAI or wait and send the mapping of the S-NSSAI to the Alternative S-NSSAI to the UE when the UE establishes a PDU Session associated with the S-NSSAI. During a new PDU Session establishment procedure for a S-NSSAI, - if the UE has received together with the Allowed NSSAI a mapping of the S-NSSAI to an Alternative S-NSSAI, the UE shall provide both the Alternative S-NSSAI and the S-NSSAI in the PDU Session Establishment message. When the AMF receives the Alternative S-NSSAI and the S-NSSAI in the PDU Session Establishment message, the AMF includes both the Alternative S-NSSAI and the S-NSSAI to the SMF in Nsmf_PDUSession_CreateSMContext service operation. - if the UE has not yet received with the Allowed NSSAI a mapping of the S-NSSAI to the Alternative S-NSSAI, the UE provides only the S-NSSAI in the PDU Session Establishment message. If the AMF determines that the requested S-NSSAI is to be replaced with the Alternative S-NSSAI and if the UE supports Network Slice Replacement, the AMF performs UE Configuration Update procedure to reconfigure the UE with the Alternative S-NSSAI. The AMF continues the PDU Session establishment procedure with the Alternative S-NSSAI and provides both the Alternative S-NSSAI and the S-NSSAI to the SMF in Nsmf_PDUSession_CreateSMContext service operation. The SMF proceeds with the PDU Session establishment using the Alternative S-NSSAI. The SMF sends the Alternative S-NSSAI to NG-RAN in N2 SM information and to UE in PDU Session Establishment Accept message. For existing PDU Session associated with an S-NSSAI that is replaced with the Alternative S-NSSAI, after the AMF sends mapping of the S-NSSAI to the Alternative S-NSSAI to the supporting UE in UE Configuration Update message, the AMF sends updates to the SMF of the PDU Session, e.g. triggering Nsmf_PDUSession_UpdateSMContext service operation, that the PDU Session is to be transferred to Alternative S-NSSAI and includes the Alternative S-NSSAI as follows (see details in clause 4.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]): - If the SMF determines that the PDU Session is to be retained (e.g. if the anchor UPF can be reused with the alternative S-NSSAI and SSC mode 1), the SMF sends the Alternative S-NSSAI to the UPF in the N4 message, to the NG-RAN in N2 message and to the supporting UE in PDU Session Modification Command message. The S-NSSAI provided to the (R)AN and to the UPF is the Alternative S-NSSAI. - If the SMF determines that the PDU Session is to be re-established, the SMF sends the Alternative S-NSSAI to the supporting UE either in PDU Session Modification Command if the PDU Session is of SSC mode 3, or in PDU Session Release if the PDU Session is of SSC mode 2 or SSC mode 1, to trigger the re-establishment of the PDU Session. The UE includes both, the S-NSSAI and the Alternative S-NSSAI in the PDU Session Establishment message. When the AMF is notified that the S-NSSAI is available again (e.g. the congestion of the S-NSSAI has been mitigated), if the AMF has configured the supporting UE with the Alternative S-NSSAI, and the AMF determines for the UE to use the replaced S-NSSAI again, the AMF reconfigures the supporting UE (e.g. by using UE Configuration Update procedure or in the next registration procedure) to use the replaced S-NSSAI again by removing the mapping of the replaced S-NSSAI to Alternative S-NSSAI. If there is an existing PDU Session associated with the Alternative S-NSSAI, the AMF updates the SMF(s) of the PDU Session(s), by Nsmf_PDUSession_UpdateSMContext service operation, causing the PDU Session to be transferred to the S-NSSAI. The event trigger in SMF for interacting with PCF is described in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. During a handover procedure, if an S-NSSAI has to be replaced with an Alternative S-NSSAI, the handover procedure (including any PDU session associated with the S-NSSAI to be replaced) shall continue unaffected by the Network Slice Replacement. Any Network Slice Replacement for the S-NSSAI shall not take place during the handover. During NSSAA re-authentication procedure for an S-NSSAI, if the S-NSSAI has to be replaced with Alternative S-NSSAI, the AMF shall continue with the NSSAA procedure unaffected by the Network Slice Replacement and the AMF executes the Network Slice Replacement after the NSSAA procedure is completed. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.19 |
3,559 | 5.2.8.2.6 Nsmf_PDUSession_UpdateSMContext service operation | Service operation name: Nsmf_PDUSession_UpdateSMContext. Description: It allows to update the AMF-SMF association to support a PDU Session and/or to provide SMF with N1/N2 SM information received from the UE or from the AN, or allows to establish forwarding tunnel between UPFs controlled by different SMFs (e.g. by UPF controlled by old I-SMF and UPF controlled by new I-SMF). Input, Required: SM Context ID. Input, Optional: N1 SM container received from the UE, N2 SM information received from the AN (e.g. N3 addressing information, notification indicating that the QoS targets cannot be fulfilled for a QFI, Secondary RAT Usage Data), Operation Type (e.g. UP activate, UP deactivate, UP To Be Switched), Serving GW Address(es) and Serving GW DL TEID(s) for data forwarding during HO from 5GS to EPS, UE location information, AN type, UE Time Zone, H-SMF identifier/address, EPS Interworking indication, EBI(s) to be revoked, PDU Session(s) to be re-activated, Direct Forwarding Flag, ARP list, S-NSSAI, Data Forwarding Tunnel (setup/release), UE presence in LADN service area, Target ID, Target AMF ID, GUAMI, backup AMF(s) (if NF Type is AMF), Indication of Access Type can be changed, RAT Type. Backup AMF(s) sent only once by the AMF to the SMF in its first interaction with the SMF. Release indication and release cause, forwarding tunnel information, Handover Complete Indication, Relocation Cancel Indication. MA PDU request indication, MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses, access on which signalling was received, Subscription to DDN Failure Notification, NEF Correlation ID, MO Exception Data Counter, access for MA PDU Session Release, list of NWDAF IDs and corresponding Analytics ID(s), Satellite backhaul category, GEO Satellite ID, N9 forwarding tunnel to support the EAS session continuity required, target UL CL tunnel info for N9 forwarding tunnel to support the EAS session continuity, value of the timer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity, CN based MT handling indication, Alternative S-NSSAI, Indication of UE supporting non-3GPP access path switching, Indication of non-3GPP access path switching while using old AN resources. Output, Required: Result Indication. Output, Optional: PDU Session ID, Cause, released EBI list, allocated EBI information, N2 SM information (e.g. QFI, UE location information, notification indication indicating that the QoS targets cannot be fulfilled), N1 SM container to be transferred to the AN/UE, type of N2 SM information. MA PDU session Accepted indication, list of NWDAF IDs and corresponding Analytics ID(s), source UL CL tunnel info for N9 forwarding tunnel info to support the EAS session continuity. See clause 4.3.3.2 and clause 4.3.3.3 for an example usage of this service operation. See clause 4.9.1.2.2 for the usage of the "UP To Be Switched" Operation Type. For the use of the "EBI(s) to be revoked" information, see clause 4.11.1.4.1. For the use of the "Direct Forwarding Flag", see clause 4.11.1.2.2.2. For the use of the "Indication of Access Type can be changed", see clause 4.2.3.2. For the use of "release indication and release cause", see clause 4.3.4.2. For the use of the "forwarding tunnel information", see clause 4.23.4.3. If the consumer NF is AMF and the SMF determines that some EBIs are not needed, the SMF will put the EBIs back in the released EBI list. If the consumer NF is AMF and Inter-system mobility happens, the SMF sends allocated EBI information to AMF. If the ARP of QoS flow is changed, the SMF uses this operation to update EBI-ARP information in the AMF. If the AMF does not have PDU Session ID, the PDU Session ID is not required for Input and is required for Output. If consumer NF is AMF and SMF includes N2 SM information in the Output, the SMF indicates type of N2 SM information. The Small Data Rate Control Status is included if a PDU Session is being released and the UPF or NEF provided Small Data Rate Control Status for the AMF to store. APN Rate Control Status is included if a PDU Session is being released and the UPF or NEF provided APN Rate Control Status for the AMF to store. NOTE: The N2 SM information is not interpreted by the AMF. See clauses 4.22.6.3, 4.22.9 and 4.22.10.2 for detailed usage of this service operation for ATSSS. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.2.6 |
3,560 | 13 Interworking with PDN (DHCP) 13.1 General | In current LAN environments the most commonly used configuration protocol is DHCP (Dynamic Host Configuration Protocol, RFC 2131 [26]) and DHCPv6 (Dynamic Host Configuration Protocol for IPv6, IETF RFC 3315 [46]). It provides a mechanism for passing a large set of configuration parameters to hosts connected to a TCP/IP network (IP address, sub-net mask, domain name, MTU, etc.) in an automatic manner. Moreover DHCP may assign IP addresses to clients for a finite lease time, allowing for sequential reassignment of addresses to different users. The lease time is chosen by the administrator of the DHCP server (in the external network), and is therefore out of the scope of the present document. The Packet Domain may obtain IP address via external DHCP server during the packet bearer establishment procedures (e.g. PDP Context activation, default bearer establishment). The GGSN/P-GW acts as a DHCP client towards the external DHCP server. The Packet Domain offers the end user the possibility to run DHCP end-to-end the same way as he does when connected directly to a LAN (e.g. an enterprise Intranet). No modifications should be required in common implementations of DHCP clients and servers. However in non-EPC based Packet Domain, a DHCP relay agent function is needed in the GGSN so as to allow correct routing of DHCP requests and replies between the TE and the DHCP servers. In EPC based Packet Domain for 3GPP access networks, the P-GW acts a DHCP server towards the UE and it acts as a DHCP client towards the external DHCP server. For trusted non-3GPP access networks, the non-3GPP access network may act as a DHCP relay or DHCP server. In the trusted WLAN access network, the TWAN acts a DHCP server towards the UE and PGW acts as a DHCP client towards the external DHCP server for the GTP/PMIP-based S2a. In non-EPC based Packet Domain,at PDP context activation no IP address is allocated, this is done afterwards through DHCP. After the TE’s configuration has been completed by DHCP, the PDP context is updated by means of the GGSN-initiated PDP Context Modification Procedure in order to reflect the newly assigned IP address. In the following cases the bearer associated with the allocated IP address (i.e. IPv4 address or IPv6 prefix) shall be released: - if the DHCP lease expires; - if the DHCP renewal is rejected by the DHCP server; - if the IP address is changed during the renewal process. Usually when the lease is renewed, the IP address remains unchanged. However, if for any reason (e.g. poor configuration of the DHCP server), a different IP address is allocated during the lease renewal process the associated bearer shall be released. | 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 | 13 |
3,561 | 5.7.13.2 Relaxed measurement criterion for good serving cell quality | The relaxed measurement criterion of good serving cell quality for RLM is fulfilled when the downlink radio link quality on the configured RLM-RS resource is evaluated to be better than the threshold Qin+XdB, wherein - Qin is specified in clause 8.1 of TS 38.133[ NR; Requirements for support of radio resource management ] [14]. - X is the parameter offset in goodServingCellEvaluationRLM for the evaluated serving cell. The relaxed measurement criterion of good serving cell quality for BFD is fulfilled when the downlink radio link quality on the configured BFD-RS resource is evaluated to be better than the threshold Qin+XdB, wherein - Q in is specified in clause 8.1 of TS 38.133[ NR; Requirements for support of radio resource management ] [14]. - X is the parameter offset in goodServingCellEvaluationBFD for the evaluated serving cell. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.13.2 |
3,562 | 5.8.2.7 PDU Session and QoS Flow Policing | ARP is used for admission control (i.e. retention and pre-emption of the new QoS Flow). The value of ARP is not required to be provided to the UPF. For every QoS Flow, the SMF shall determine the transport level packet marking value (e.g. the DSCP in the outer IP header) based on the 5QI, the Priority Level (if explicitly signalled) and optionally, the ARP priority level and provide the transport level packet marking value to the UPF. The SMF shall provide the Session-AMBR values of the PDU Session to the UPF so that the UPF can enforce the Session-AMBR of the PDU Session across all Non-GBR QoS Flows of the PDU Session. SMF shall provide the GFBR and MFBR value for each GBR QoS Flow of the PDU Session to the UPF. SMF may also provide the Averaging window to the UPF, if Averaging window is not configured at the UPF or if it is different from the default value configured at the UPF. SMF may decide to activate ECN marking for L4S by PSA UPF for the QoS Flow (see clause 5.37). In this case, the SMF shall send an ECN marking for L4S indicator to UPF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.7 |
3,563 | 5.4.1.2.4 EAP message reliable transport procedure | 5.4.1.2.4.1 General The purpose of the EAP message reliable transport procedure is to provide a reliable transport of an EAP-request message, the ngKSI and the ABBA from the network to the UE and of an EAP-response message from the UE to the network. The EAP message reliable transport procedure is initiated by an AUTHENTICATION REQUEST message with the EAP message IE. 5.4.1.2.4.2 EAP message reliable transport procedure initiation by the network In order to initiate the EAP message reliable transport procedure, the AMF shall create an AUTHENTICATION REQUEST message. The AMF shall set the EAP message IE of the AUTHENTICATION REQUEST message to the EAP-request message to be sent to the UE. The AMF shall set the ngKSI IE of the AUTHENTICATION REQUEST message to the ngKSI value selected in subclause 5.4.1.2.2.2, subclause 5.4.1.2.3.1 or subclause 5.4.1.2.3A.1. In this release of specification, the AMF shall set the ABBA IE of the AUTHENTICATION REQUEST message with the length of ABBA IE to 2 and the ABBA contents to be 2 octets in length with value 0000H as described in subclause 9.11.3.10. The AMF shall send the AUTHENTICATION REQUEST message to the UE, and the AMF shall start timer T3560 (see example in figure 5.4.1.2.4.2.1). Figure 5.4.1.2.4.2.1: EAP message reliable transport procedure Upon receipt of an AUTHENTICATION REQUEST message with the EAP message IE, the UE handles the EAP message received in the EAP message IE and the ABBA of the AUTHENTICATION REQUEST message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1.2.4 |
3,564 | 4.7.7.2 Serving PLMN Rate Control | The Serving PLMN Rate Control value is configured in the MME. NOTE 1: Homogeneous support of Serving PLMN Rate Control in a network is assumed. At PDN connection establishment, the MME may inform the UE and PDN GW/SCEF (as specified in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46] and TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]) of any per PDN connection local Serving PLMN Rate Control that the Serving PLMN intends to enforce for NAS Data PDUs. The MME shall only indicate Serving PLMN Rate Control command to the PDN GW if the PDN connection is using S11-U and set to Control Plane only. The MME shall only indicate Serving PLMN Rate Control command to the SCEF if that PDN connection is using SCEF. This rate control is operator configurable and expressed as "X NAS Data PDUs per deci hour" where X is an integer that shall not be less than 10. There are separate limits for uplink and downlink NAS Data PDUs: - The UE shall limit the rate at which it generates uplink NAS Data PDUs to comply with the Serving PLMN policy. In the UE the indicated rate control applies only on the PDN connection where it was received, and therefore the UE shall limit the rate of its uplink NAS Data PDUs to comply with the rate that is indicated for the PDN connection. The indicated rate is valid until the PDN connection is released. - The PDN GW/SCEF shall limit the rate at which it generates downlink Data PDUs. In the PDN GW/SCEF the indicated rate control applies only on the PDN connection where it was received, and therefore the PDN GW/SCEF shall limit the rate of its downlink Data PDUs to comply with the rate that is indicated for the PDN connection. - The MME may enforce these limits per PDN connection by discarding or delaying packets that exceed this these limits. The Serving PLMN Rate does not include SMS sent via NAS Transport PDUs. The MME starts the Serving PLMN Rate Control when the first NAS Data PDU is received. NOTE 2: If the UE/PDN GW/SCEF start the Serving PLMN rate control at a different time than the MME, PDUs sent within the limit enforced at the UE/PDN GW/SCEF can still exceed the limit enforced by the MME. NOTE 3 It is assumed that the Serving PLMN Rate is sufficiently high to not interfere with the APN Rate Control as the APN Rate Control, if used, is assumed to allow fewer messages. NAS PDUs related to exception reports are not subject to the Serving PLMN Rate Control. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.7.7.2 |
3,565 | 16.14.5 NG-RAN signalling | The Cell Identity, as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [26] and TS 38.423[ NG-RAN; Xn Application Protocol (XnAP) ] [50], used in following cases corresponds to a Mapped Cell ID, irrespective of the orbit of the NTN payload or the types of service links supported: - The Cell Identity indicated by the gNB to the Core Network as part of the User Location Information; - The Cell Identity used for Paging Optimization in NG interface; - The Cell Identity used for Area of Interest; - The Cell Identity used for PWS. The Cell Identity included within the target identification of the handover messages allows identifying the correct target cell. The cell identity used in the NG and Xn handover messages, Xn Setup and Xn NG-RAN Node Configuration Update procedures is expected to be Uu Cell ID. The Cell Identities used in the RAN Paging Area during Xn RAN paging allow the identification of the correct target cells for RAN paging. NOTE 1: The Cell Identity used for RAN Paging is assumed to typically represent a Uu Cell ID. The mapping between Mapped Cell IDs and geographical areas is configured in the RAN and Core Network. NOTE 2: A specific geographical location may be mapped to multiple Mapped Cell ID(s), and such Mapped Cell IDs may be configured to indicate differerent geographical areas (e.g. overlapping and/or with different dimensions). The gNB is responsible for constructing the Mapped Cell ID based on the UE location information received from the UE, if available. The mapping may be pre-configured (e.g., up to operator's policy) or up to implementation. NOTE 3: As described in TS 23.501[ System architecture for the 5G System (5GS) ] [3], the User Location Information may enable the AMF to determine whether the UE is allowed to operate at its present location. Special Mapped Cell IDs or TACs may be used to indicate areas outside the serving PLMN's country. The gNB reports the broadcasted TAC(s) of the selected PLMN to the AMF as part of ULI. In case the gNB knows the UE's location information, the gNB may determine the TAI the UE is currently located in and provide that TAI to the AMF as part of ULI. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.5 |
3,566 | 28.14 Data Network Access Identifier (DNAI) | A Data Network Access Identifier (DNAI) is an operator defined identifier of a user plane access to one or more DN(s) where applications are deployed (see clauses 3.1 and 5.6.7 in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]). The same DN may also be referred to by multiple DNAIs. DNAI is represented as an operator specific string (see clause A.2 in 3GPP TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [129]. The format of the DNAI is defined by the operator and is not standardized. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.14 |
3,567 | 7.2.13 Delete Indirect Data Forwarding Tunnel Response | The Delete Indirect Data Forwarding Tunnel Response message is sent on the S4/S11 interface by the SGW to the SGSN/MME as part of the following procedures: - S1-based handover - UTRAN Iu mode to E-UTRAN Inter RAT handover - GERAN A/Gb mode to E-UTRAN Inter RAT handover - E-UTRAN to UTRAN Iu mode Inter RAT handover - E-UTRAN to GERAN A/Gb mode Inter RAT handover - MME to SGSN combined hard handover and SRNS relocation procedure - SGSN to MME combined hard handover and SRNS relocation procedure - Inter RAT handover Cancel - S1-based handover Cancel - Optimised Active Handover: E-UTRAN Access to CDMA2000 HRPD Access - EPS to 5GS handover using N26 interface - 5GS to EPS handover using N26 interface - N26 based Handover cancel Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted". - "Request accepted partially" - "Context not found". Table 7.2.13-1: Information Element in Delete Indirect Data Forwarding Tunnel Response | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.2.13 |
3,568 | 5.7.1.5 QoS Flow mapping | The SMF performs the binding of PCC rules to QoS Flows based on the QoS and service requirements (as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). The SMF assigns the QFI for a new QoS Flow and derives its QoS profile, corresponding UPF instructions and QoS Rule(s) from the PCC rule(s) bound to the QoS Flow and other information provided by the PCF. When applicable, the SMF provides the following information for the QoS Flow to the (R)AN: - QFI; - QoS profile as described in clause 5.7.1.2. - optionally, Alternative QoS Profile(s) as described in clause 5.7.1.2a; For each PCC rule bound to a QoS Flow, the SMF provides the following information to the UPF enabling classification, bandwidth enforcement and marking of User Plane traffic (the details are described in clause 5.8): - a DL PDR containing the DL part of the SDF template; - an UL PDR containing the UL part of the SDF template; NOTE 1: If a DL PDR for an bidirectional SDF is associated with a QoS Flow other than the one associated with the default QoS rule and the UE has not received any instruction to use this QoS Flow for the SDF in uplink direction (i.e. neither a corresponding QoS rule is sent to the UE nor the Reflective QoS Indication is set in the PCC rule), it means that the UL PDR for the same SDF has to be associated with the QoS Flow associated with the default QoS rule. - the PDR precedence value (see clause 5.7.1.9) for both PDRs is set to the precedence value of the PCC rule; - QoS related information (e.g. MBR for an SDF, GFBR and MFBR for a GBR QoS Flow) as described in clause 5.8.2; - the corresponding packet marking information (e.g. the QFI, the transport level packet marking value (e.g. the DSCP value of the outer IP header); - optionally, the Reflective QoS Indication is included in the QER associated with the DL PDR (as described in clause 5.7.5.3). For each PCC rule bound to a QoS Flow, when applicable, the SMF generates an explicitly signalled QoS rule (see clause 5.7.1.4) according to the following principles and provides it to the UE together with an add operation: - A unique (for the PDU Session) QoS rule identifier is assigned; - The QFI in the QoS rule is set to the QFI of the QoS Flow to which the PCC rule is bound; - The Packet Filter Set of the QoS rule is generated from the UL SDF filters and optionally the DL SDF filters of the PCC rule (but only from those SDF filters that have an indication for being signalled to the UE, as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]); - The QoS rule precedence value is set to the precedence value of the PCC rule for which the QoS rule is generated; - for a dynamically assigned QFI, the QoS Flow level QoS parameters (e.g. 5QI, GFBR, MFBR, Averaging Window, see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]) are signalled to UE in addition to the QoS rule(s) associated to the QoS Flow. The QoS Flow level QoS parameters of an existing QoS Flow may be updated based on the MBR and GBR information received in the PCC rule (MBR and GBR per SDF are however not provided to UE over N1 in the case of more than one SDF) or, if the PCF has not indicated differently, when Notification control or handover related signalling indicates that the QoS parameter the NG-RAN is currently fulfilling for the QoS Flow have changed (see clause 5.7.2.4). Changes in the binding of PCC rules to QoS Flows as well as changes in the PCC rules or other information provided by the PCF can require QoS Flow changes which the SMF has to provide to (R)AN, UPF and/or UE. In the case of changes in the explicitly signalled QoS rules associated to a QoS Flow, the SMF provides the explicitly signalled QoS rules and their operation (i.e. add/modify/delete) to the UE. NOTE 2: The SMF cannot provide, update or remove pre-configured QoS rules or UE derived QoS rules. The principle for classification and marking of User Plane traffic and mapping of QoS Flows to AN resources is illustrated in Figure 5.7.1.5-1. Figure 5.7.1.5-1: The principle for classification and User Plane marking for QoS Flows and mapping to AN Resources In DL, incoming data packets are classified by the UPF based on the Packet Filter Sets of the DL PDRs in the order of their precedence (without initiating additional N4 signalling). The UPF conveys the classification of the User Plane traffic belonging to a QoS Flow through an N3 (and N9) User Plane marking using a QFI. The AN binds QoS Flows to AN resources (i.e. Data Radio Bearers of in the case of 3GPP RAN). There is no strict 1:1 relation between QoS Flows and AN resources. It is up to the AN to establish the necessary AN resources that QoS Flows can be mapped to, and to release them. The AN shall indicate to the SMF when the AN resources onto which a QoS Flow is mapped are released. If no matching DL PDR is found, the UPF shall discard the DL data packet. In UL: - For a PDU Session of Type IP or Ethernet, the UE evaluates UL packets against the UL Packet Filters in the Packet Filter Set in the QoS rules based on the precedence value of QoS rules in increasing order until a matching QoS rule (i.e. whose Packet Filter matches the UL packet) is found. - If no matching QoS rule is found, the UE shall discard the UL data packet. - For a PDU Session of Type Unstructured, the default QoS rule does not contain a Packet Filter Set and allows all UL packets. NOTE 3: Only the default QoS rule exist for a PDU Session of Type Unstructured. The UE uses the QFI in the corresponding matching QoS rule to bind the UL packet to a QoS Flow. The UE then binds QoS Flows to AN resources. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1.5 |
3,569 | 19.5 Access Network Identity | A trusted non-3GPP access network used by the UE to access EPS can be identified using the Access Network Identity. The Access Network Identity is used as an input parameter in the EPS security procedures as specified in 3GPP TS 33.402[ 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses ] [69]. The format and signalling of the parameter between the network and the UE is specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [77] and the format and signalling of this parameter between access network and core network is specified in 3GPP TS 29.273[ Evolved Packet System (EPS); 3GPP EPS AAA interfaces ] [78]. The encoding of the Access Network Identity shall be specified within 3GPP, but the Access Network Identity definition for each non-3GPP access network is under the responsibility of the corresponding standardisation organisation respectively. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.5 |
3,570 | 4.1.6.1 Number of successful RRC connection setups in relation to the time between successful RRC connection setup and last RRC connection release | a) This measurement provides the histogram as function of the number of successful RRC Connection setups and the time between the successful RRC Connection setup attempt and last RRC Connection release for the UE with the same S-TMSI and long inactivity timer configured. It is not counted to the histogram in case last RRC Connection release of the UE with the same S-TMSI is caused by call drops or handover. b) CC. c) On receipt by the eNodeB of an RRCConnectionSetupComplete message from the UE. Each RRCConnectionSetupComplete message received is added to the relevant measurement per time bin for the time between the successful RRC connection setup and last RRC Connection release for the UE with the same S-TMSI. d) Each measurement is an integer value. e) The measurement name has the form RRCConn.Setup.TimeBin where TimeBin identifies the given bin from the histogram f) EUtranCellFDD EUtranCellTDD g) Valid for packet switching. h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.1.6.1 |
3,571 | Annex A (informative): Bibliography | This annex contains guidelines for the references in all the charging specifications. a) The 3GPP charging specifications [1] - [99]. One example: [20] 3GPP TS 32.260[ Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging ] : "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging". b) Common 3GPP specifications [100] - [199] One example: [101] 3GPP TS 22.115[ Service aspects; Charging and billing ] : "Service aspects; Charging and billing". c) other Domain and Service specific 3GPP / ETSI specifications [200] - [299] One example: [201] 3GPP TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] : "IP Multimedia Subsystem (IMS); Stage 2". d) Relevant ITU Recommendations [300] - [399] One example: [300] ITU-T Recommendation D.93: "Charging and accounting in the international land mobile telephone service (provided via cellular radio systems)". e) Relevant IETF RFCs [400] - [499] One example: [402] IETF RFC 4006 (2005): "Diameter Credit-Control Application". f) Others [500] - [699] One example: [601] Broadband Forum TR-134: "Broadband Policy Control Framework (BPCF)". | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | Annex |
3,572 | 8.133 UP Function Selection Indication Flags | The UP Function Selection Indication Flags information element shall be coded as depicted in Figure 8.133-1. Figure 8.133-1: UP Function Selection Indication Flags For each message, the applicable flags of the UP Function Selection Indication Flags IE shall be clearly specified in the individual message clause. The remaining flags of the UP Function Selection Indication Flags IE not so indicated shall be discarded by the receiver. The receiver shall consider the value of the applicable flags as "0", if the UP Function Selection Indication Flags IE is applicable for the message but not included in the message by the sender. The following bits within Octet 5 shall indicate: - Bit 8 to 2 – Spare, for future use and set to zero. - Bit 1 – DCNR (Dual connectivity with NR): If this bit is set to 1, it indicates to the SGW-C and PGW-C that it is desired to select a specific SGW-U and PGW-U for UEs supporting dual connectivity with NR and not restricted from using NR by user subscription. UE signals its support for dual connectivity with NR to the MME and S4-SGSN with the DCNR of the UE network capability IE in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23]. Subscription restriction to use NR as secondary RAT is specified in "NR as Secondary RAT Not Allowed" bit within Access Restriction Data in 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [70]. | 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.133 |
3,573 | 4.1.1.1.1 Integrity Checking of Signalling Messages in the Mobile Station (Iu mode only) | In Iu mode only, integrity protected signalling is mandatory with one exception regarding emergency calls (see subclause 4.1.1.1.1a). In Iu mode only, all layer 3 protocols shall use integrity protected signalling once the security mode procedure has been successfully activated in the network and the MS. Integrity protection of all layer 3 signalling messages is the responsibility of lower layers. It is the network which activates integrity protection. This is done using the security mode control procedure (3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). The supervision that integrity protection is activated shall be the responsibility of the MM and GMM layer in the MS (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]). In order to do this, the lower layers shall provide the MM and GMM layer with an indication on when the integrity protection is activated in the MS (i.e. one indication to the MM layer when a security mode control procedure for the CS domain is processed successfully and one indication to the GMM layer when a security mode control procedure for the PS domain is processed successfully). The CS and PS domains in the network and the MM and GMM layers in the MS, are not aware of whether integrity protection has been started in the lower layers by the other domain. It is mandatory for the network to initiate one security mode control procedure for the CS domain and one for the PS domain. Except the messages listed below, no layer 3 signalling messages shall be processed by the receiving MM and GMM entities or forwarded to the CM entities, unless the network has activated the integrity protection for that domain. - MM messages: - AUTHENTICATION REQUEST - AUTHENTICATION REJECT - IDENTITY REQUEST - LOCATION UPDATING ACCEPT (at periodic location update with no change of location area or temporary identity, and, any Per MS T3212 value is not changed) - LOCATION UPDATING REJECT (if the cause is not #25) - CM SERVICE ACCEPT, if the following two conditions apply: - no other MM connection is established; and - the CM SERVICE ACCEPT is the response to a CM SERVICE REQUEST with CM SERVICE TYPE IE set to 'emergency call establishment' - CM SERVICE REJECT (if the cause is not #25) - ABORT - GMM messages: - AUTHENTICATION & CIPHERING REQUEST - AUTHENTICATION & CIPHERING REJECT - IDENTITY REQUEST - ATTACH REJECT (if the cause is not #25) - ROUTING AREA UPDATE ACCEPT, if any of the following conditions applies: - the MS performs periodic routing area updating with: - no change in routing area or temporary identities; - no change in T3312 extended value; - no change in Network feature support value; and - extended DRX parameters IE not included. - the GMM entity in the MS has received an ATTACH ACCEPT message with neither ciphering nor integrity protection applied in response to an ATTACH REQUEST message with attach type set to "emergency attach"; or - the MS has performed intersystem change from S1 mode to Iu mode with a PDN connection for emergency bearer services for which the "null integrity protection algorithm" EIA0 has been used while in S1 mode. - ROUTING AREA UPDATE REJECT (if the cause is not #25) - SERVICE REJECT (if the cause is not #25) - DETACH ACCEPT (for non power-off) - ATTACH ACCEPT, if the ATTACH ACCEPT is the response to an ATTACH REQUEST with attach type set to "emergency attach". - SERVICE ACCEPT, if any of the following conditions applies: - the GMM entity in the MS has received an ATTACH ACCEPT message with neither ciphering nor integrity protection applied in response to an ATTACH REQUEST message, with attach type set to "emergency attach"; or - the MS has performed intersystem change from S1 mode to Iu mode with a PDN connection for emergency bearer services for which the "null integrity protection algorithm" EIA0 has been used while in S1 mode. - CC messages: - all CC messages, if the following two conditions apply: - no other MM connection is established; and - the MM entity in the MS has received a CM SERVICE ACCEPT message with no ciphering or integrity protection applied as response to a CM SERVICE REQUEST message, with CM SERVICE TYPE set to 'Emergency call establishment’ sent to the network; - the MM connection was established locally due to the SRVCC handover of a PDN connection for emergency bearer services for which the "null integrity protection algorithm" EIA0 has been used while in S1 mode or for which integrity protection has not been activated while in Iu mode; or - the MM connection was established locally due to the 5G-SRVCC handover from NG-RAN to UTRAN of an emergency PDU session for which the "null integrity protection algorithm" 5G-IA0 has been used while in N1 mode. - SM messages: - all SM messages, if any of the following conditions applies: - the GMM entity in the MS has received an ATTACH ACCEPT message with neither ciphering nor integrity protection applied in response to an ATTACH REQUEST message, with attach type set to "emergency attach"; or - the MS has performed intersystem change from S1 mode to Iu mode with a PDN connection for emergency bearer services for which the "null integrity protection algorithm" EIA0 has been used while in S1 mode. Once integrity protection is activated, the receiving layer 3 entity in the MS shall not process any layer 3 signalling messages unless they have been successfully integrity checked by the lower layers. If any signalling messages, having not successfully passed the integrity check, are received, then the lower layers in the MS shall discard that message (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). If any layer 3 signalling message is received, in either PS or CS domains, as not integrity protected even though the integrity protection has been activated in the MS by that domain in the network, then the lower layers shall discard this message (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). Integrity checking on the network side is performed by the RNC and is described in 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.1.1.1 |
3,574 | 4.7.3.1.5 Abnormal cases in the MS | The following abnormal cases can be identified: a) Access barred because of access class control, EAB or ACDC The GPRS attach procedure shall not be started. The MS stays in the current serving cell and applies normal cell reselection process. The GPRS attach procedure is started as soon as possible, i.e. when access is granted or because of a cell change. If access is barred because of access class control, ACDC is applicable to the request from the upper layers and the MS supports ACDC, then the GPRS attach procedure shall be started. If access is barred for a certain ACDC category, a request with a higher ACDC category is received from the upper layers and the MS supports ACDC, then the GPRS attach procedure shall be started. If an access request for an uncategorized application is barred due to ACDC, a request with a certain ACDC category is received from the upper layers and the MS supports ACDC, then the GPRS attach procedure shall be started. b) Lower layer failure without "Extended Wait Time" received from lower layers before the ATTACH ACCEPT or ATTACH REJECT message is received The procedure shall be aborted and the MS shall proceed as described below, except in the following implementation option cases b.1 and b.2. b.1) Release of PS signalling connection in Iu mode before the completion of the GPRS attach procedure If the release of the PS signalling connection occurs before completion of the GPRS attach procedure, then the GPRS attach procedure shall be initiated again, if the following conditions apply: i) The original GPRS attach procedure was initiated over an existing PS signalling connection; and ii) The GPRS attach procedure was not due to timer T3310 expiry; and iii) No SECURITY MODE COMMAND message and no Non-Access Startum (NAS) messages relating to the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the ATTACH REQUEST message was transmitted. b.2) RR release in Iu mode (i.e. RRC connection release) with, for example, cause "Normal", or "User inactivity" (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) The GPRS attach procedure shall be initiated again, if the following conditions apply: i) The original GPRS attach procedure was initiated over an existing RRC connection; and ii) The GPRS attach procedure was not due to timer T3310 expiry; and iii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the ATTACH REQUEST message was transmitted. NOTE 1: The RRC connection release cause that triggers the re-initiation of the GPRS attach procedure is implementation specific. c) T3310 time-out On the first expiry of the timer, the MS shall reset and restart timer T3310 and shall retransmit the ATTACH REQUEST message. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3310, the MS shall abort the GPRS attach procedure and, in Iu mode, release the PS signalling connection (see 3GPP TS 25.331[ None ] [23c]). The MS shall proceed as described below. d) ATTACH REJECT, other causes than those treated in subclause 4.7.3.1.4, and cases of GMM cause values #22 and #25, if considered as abnormal cases according to subclause 4.7.3.1.4 If the attach request is neither for emergency bearer services nor for initiating a PDN connection for emergency bearer services with attach type not set to "emergency attach", upon reception of the cause codes # 95, # 96, # 97, # 99 and # 111 the MS should set the GPRS attach attempt counter to 5. The MS shall proceed as described below. e) Change of cell within the same RA (A/Gb mode only) If a cell change occurs within the same RA when the MS is in state GMM-REGISTERED-INITIATED, then the cell update procedure shall be performed before completion of the attach procedure. f) Change of cell into a new routing area If a cell change into a new routing area occurs before an ATTACH ACCEPT or ATTACH REJECT message has been received, the GPRS attach procedure shall be aborted and re-initiated immediately. If a routing area border is crossed when the ATTACH ACCEPT message is received but before an ATTACH COMPLETE message is sent, the GPRS attach procedure shall be aborted and the routing area updating procedure shall be initiated. If a P-TMSI was allocated during the GPRS attach procedure, this P-TMSI shall be used in the routing area updating procedure. If a P-TMSI signature was allocated together with the P-TMSI during the GPRS attach procedure, this P-TMSI signature shall be used in the routing area updating procedure. g) Mobile originated detach required If the MS is in state GMM-REGISTERED-INITIATED, the GPRS attach procedure shall be aborted and the GPRS detach procedure shall be performed (see subclause 4.7.4.1). h) Detach procedure collision If the MS receives a DETACH REQUEST message from the network in state GMM-REGISTERED-INITIATED with detach type "re-attach not required" and no cause code, or "re-attach not required"' and the cause code is not #2 "IMSI unknown in HLR", the GPRS detach procedure shall be progressed and the GPRS attach procedure shall be aborted. Otherwise the GPRS attach procedure shall be progressed and the DETACH REQUEST message shall be ignored. i) "Extended wait time" for PS domain from the lower layers If the ATTACH REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall start timer T3346 with the "Extended wait time" value and reset the attach attempt counter. In other cases the MS shall ignore the "Extended wait time". The MS shall abort the attach procedure, stay in the current serving cell, change the state to GMM-DEREGISTERED.ATTEMPTING-TO-ATTACH and apply the normal cell reselection process. j) Timer T3346 is running The MS shall not start the GPRS attach procedure unless the MS needs to attach for emergency bearer services or the MS is an MS configured to use AC11 – 15 in selected PLMN or the MS needs to attach without the NAS signalling low priority indication and if the timer T3346 was started due to rejection of a NAS request message (e.g. ATTACH REQUEST, ROUTING AREA UPDATE REQUEST or SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority". The MS stays in the current serving cell and applies normal cell reselection process. NOTE 2: It is considered an abnormal case if the MS needs to initiate an attach procedure while timer T3346 is running independent on whether timer T3346 was started due to an abnormal case or a non successful case. In cases b, c, d, i and j, the MS shall proceed as follows: - Timer T3310 shall be stopped if still running. - For the cases b, c, d, and i when the "Extended wait time" is ignored, if the attach request is neither for emergency bearer services nor for initiating a PDN connection for emergency bearer services with attach type not set to "emergency attach", the GPRS attach attempt counter shall be incremented. - If the GPRS attach attempt counter is less than 5: - for the cases i and j, the GPRS attach procedure is started, if still necessary, when timer T3346 expires or is stopped. - for the cases b, c, d, and i when the "Extended wait time" is ignored, if the attach request is neither for emergency bearer services nor for initiating a PDN connection for emergency bearer services with attach type not set to "emergency attach", timer T3311 is started and the state is changed to GMM-DEREGISTERED.ATTEMPTING-TO-ATTACH. - If the GPRS attach attempt counter is greater than or equal to 5: - the MS shall delete any RAI, P-TMSI, P-TMSI signature, list of equivalent PLMNs, and GPRS ciphering key sequence number, shall set the GPRS update status to GU2 NOT UPDATED, shall start timer T3302. The state is changed to GMM-DEREGISTERED. ATTEMPTING-TO-ATTACH or optionally to GMM-DEREGISTERED.PLMN-SEARCH (see subclause 4.2.4.1.2) in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. - If S1 mode is supported by the MS, the MS shall in addition handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the abnormal case when a normal attach procedure fails and the attach attempt counter is equal to 5. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.1.5 |
3,575 | 19.4.2.4 Mobility Management Entity (MME) | A Mobility Management Entity (MME) within an operator's network is identified using a MME Group ID (MMEGI), and an MME Code (MMEC). A subdomain name shall be derived from the MNC and MCC by adding the label "mme" to the beginning of the Home Network Realm/Domain (see clause 19.2). The MME node FQDN shall be constructed as: mmec<MMEC>.mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org Where <MMEC> and <MMEGI> are the hexadecimal strings of the MMEC and MMEGI. An MME pool FQDN shall be constructed as: mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org If there are less than 2 significant digits in <MMEC>, "0" digit(s) shall be inserted at the left side to fill the 2 digit coding. If there are less than 4 significant digits in <MMEGI>, "0" digit(s) shall be inserted at the left side to fill the 4 digit coding. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.4 |
3,576 | 13.2.4.7 Message verification by the receiving SEPP | The receiving SEPP shall decrypt the JWE ciphertext using the shared session key and the following parameters obtained from the JWE object – Initialization Vector, Additional Authenticated Data value (clearTextEncapsulatedMessage in "aad") and JWE Authentication Tag ( "tag"). If the reformattedData IE is not empty, the receiving SEPP shall check the integrity and authenticity of the clearTextEncapsulatedMessage and the encrypted text by verifying the JWE Authentication Tag in the JWE object with the JWE AAD algorithm. The algorithm returns the decrypted plaintext (dataToIntegrityProtectAndCipher) only if the JWE Authentication Tag is correct. The receiving SEPP refers to the NF API data-type placement mapping table to re-construct the original reformatted message by updating corresponding entries in clearTextEncapsulatedMessage with values in the dataToIntegrityProtectAndCipher array. The receiving SEPP shall next verify IPX provider updates, if included, by verifying the JWS signatures added by the Roaming Intermediaries. The SEPP shall verify the JWS signature, using the corresponding raw public key or certificate that is contained in the IPX provider’s security information list obtained during parameter exchange in the related N32-c connection setup or, alternatively, has been configured for the particular peer SEPP. If the reformattedData IE is not empty, the receiving SEPP shall then check that the raw public key or certificate of the JWS signature IPX's Identity in the modifiedDataToIntegrity block matches to the IPX provider referred to in the "authorizedIPX ID" field added by the sending SEPP, based on the information given in the IPX provider security information list. If the reformattedData IE is empty, the receiving SEPP shall check that the raw public key or certificate of the JWS signature IPX's identity in the modifiedDataToIntegrityProtect block matches to the adjacent roaming hub in the N32-f security context extracted from the modifiedDataToIntegrityProtect block which is defined in clause 13.2. 4. 5.1, of the first roaming hub. Editor's Note: Whether an N32-f security context of the roaming hub can be extracted from the modifiedDataToIntegrityProtect is ffs. The receiving SEPP shall check whether the modifications performed by the Roaming Intermediaries were permitted by the respective modification policies. The receiving SEPP shall use the modification policy of the cIPX obtained during parameter exchange in the related N32-c connection setup, and use the modification policy of pIPX configured within the receiving SEPP. If this is the case, the receiving SEPP shall apply the patches in the Operations field in order, perform plausibility checks, and create a new HTTP request according to the "patched" clearTextEncapsulatedMessage. The receiving SEPP shall verify that the PLMN-ID contained in the incoming N32-f message matches the PLMN-ID in the related N32-f context. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4.7 |
3,577 | 6.1.3.2.1a Successful Secondary PDP Context Activation Procedure Requested by the network | In order to request a PDP context activation with the same PDP address and APN as an already active PDP context, the network shall send a REQUEST SECONDARY PDP CONTEXT ACTIVATION message to the MS and start timer T3385. The message contains the required QoS, Linked TI, and optionally protocol configuration options and a TFT. The network shall always include a TFT in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message. If present, the TFT shall be sent transparently through the SGSN to the MS to enable packet classification and policing for uplink and downlink data transfer. The network shall allocate packet filter identifiers for all packet filters included in the TFT. NOTE: A network implementing an earlier release of this specification can send a REQUEST SECONDARY PDP CONTEXT ACTIVATION message without any TFT. Upon receipt of a REQUEST SECONDARY PDP CONTEXT ACTIVATION message, if the MS sent an APN for the establishment of the PDN connection, the MS shall stop the timer T3396 if it is running for the APN sent by the MS. If the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall stop the timer T3396 associated with no APN if it is running. If the REQUEST SECONDARY PDP CONTEXT ACTIVATION message was received for an emergency PDN connection, the UE shall not stop the timer T3396 associated with no APN if it is running. For any case, the MS shall then either initiate the secondary PDP context activation procedure as described in the subclause 6.1.3.2.1 or shall reject the activation request by sending a REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message as described in subclause 6.1.3.2.2a. The value of the reject cause IE of the REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message shall indicate the reason for rejection, e.g. "insufficient resources to activate another context". The MS shall maintain the previously negotiated Bearer Control Mode (BCM) for all active PDP contexts sharing the same PDP Address and APN and ignore any BCM parameter, if included in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message. If the previously negotiated BCM is 'MS only', the MS should reject the PDP context activation (see subclause 6.1.3.2.2a). The ACTIVATE SECONDARY PDP CONTEXT REQUEST message sent by the MS in order to initiate the secondary PDP context activation procedure shall contain the QoS and Linked TI required in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message. The MS shall also include a TFT with packet filters as specified in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message. Upon receipt of the ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the network shall stop timer T3385. The same procedures then apply as described for MS initiated secondary PDP context activation. | 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.1a |
3,578 | K.2.2.2 Configuration for Sync and Announce reception timeouts | The NW-TT shall be able to determine the timeout of the reception of (g)PTP Announce (when the 5GS operates as a time-aware system or Boundary Clock) and gPTP Sync messages (when the 5GS operates as time-aware system). To enable this, the TSCTSF or TSN AF shall configure the NW-TT for the following information via PMIC for each PTP port in NW-TT and "Time synchronization information for each DS-TT port" element in UMIC for each PTP port in DS-TT: portDS.announceReceiptTimeout (for time-aware system and Boundary Clock); portDS.syncReceiptTimeout (for time-aware system); portDS.logAnnounceInterval (for Boundary Clock). portDS.initialLogAnnounceInterval, portDS.useMgtSettableLogAnnounceInterval and portDS.mgtSettableLogAnnounceInterval (for time-aware system). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | K.2.2.2 |
3,579 | 4.17.3 NF service deregistration | Figure 4.17.3-1: NF Service Deregistration procedure 1. NF service consumer i.e. an NF instance sends Nnrf_NFManagement_NFDeregister Request message to NRF to inform the NRF of its unavailability when e.g. it's about to gracefully shut down or disconnect from the network. 2. The NRF marks the NF service consumer unavailable. NRF may remove the NF profile of NF service consumer according to NF management policy. 3. The NRF acknowledge NF Deregistration is accepted via Nnrf_NFManagement_NFDeregister response. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.3 |
3,580 | 5.4.13.1 Mobility Management and Power Saving Optimization | For NR satellite access that provides discontinuous network coverage the Mobility Management and Power Saving Optimization functionality may be used. If both the UE and the network support "Unavailability Period Support", and if the UE determines it will lose coverage and will become unavailable, and the UE decides to remain in no service during that time, then: - the UE triggers the Mobility Registration Update procedure to inform the network of its unavailability, as described in clause 5.4.1.4. - The UE may be able to determine, including considering current and expected future locations of the UE, a Start of Unavailability Period and/or Unavailability Period Duration for when it expects to be out of coverage and include them in the Mobility Registration Update procedure, as described in clause 5.4.1.4. - The UE should trigger the Mobility Registration Update procedure early enough such that the procedure, under normal conditions, is able to complete before the start of the unreachability period. NOTE 1: A UE based on implementation can combine successive periods of no satellite coverage into a single continuous period that is notified to the network if the UE does not require network access during this period. NOTE 2: UE informing the network of coverage gaps would increase signalling and UE power consumption if coverage gaps are more frequent than UE's communication period. In case the UE requests power saving features the AMF uses the procedures defined in other clauses to provide the UE with timers (e.g. Periodic Registration Update timer), extended DRX in CM-IDLE configuration (see clause 5.31.7.2), and MICO mode configuration (see clause 5.4.1.3), and to provide the NG-RAN with Extended Connected Time (see clause 5.31.7.3) and may also consider the Unavailability Period Duration and Start of Unavailability Period (if available). This is to keep UE in power saving mode and avoid the network attempting to page the UE if it is out of satellite network coverage. The AMF should adjust the mobile reachable timer or Implicit Deregistration timer or both such that the AMF does not implicitly deregister the UE while the UE is unavailable, see clause 5.4.1. Features described for High latency communication in clause 5.31.8 may be used to handle mobile terminated (MT) communication with UEs being unreachable due to NR satellite access discontinuous coverage and the Unavailability Period Duration (if available) and Start of Unavailability Period (if available) may be used when determining the Estimated Maximum Wait Time. Tracking Area or RAT specific configuration in the AMF may be used to set timer values based on typical coverage periods of a satellite system. NOTE 3: For example, if a satellite system only provides coverage to a UE for 20 minutes when a satellite passes, and the maximum time before a satellite passes any point on the earth is 10 hours, the AMF could configure the periodic registration timer and Mobile Reachable timer to be just greater than 20 minutes and the Implicit Deregistration timer to be greater than 10 hours to avoid unintended implicit detach due to coverage gap. Such configuration does not require AMF to be aware of detailed coverage times for each UE or for different locations. The UE may send Mobility Registration Update procedure to inform the network of its UE unavailability period (see clause 5.4.1.4) even if Mobility Management back-off timer is running. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.13.1 |
3,581 | 4.10 HNB Unique Identity | HNB Unique Identity uniquely identifies a Home NodeB or Home eNodeB. The HNB unique identity shall be defined as either a 48-bit or 64-bit extended unique identifier (EUI-48 or EUI-64) as defined in [45] (EUI-48) and [46] (EUI-64). For use in HNB certificates, the HNB Unique Identity shall be transformed into a FQDN in the form: - <EUI-48/64>.<REALM> <EUI48/64> is the first label which shall be the EUI-48 or EUI-64, represented as a string of 12 or 16 hexadecimal digits including any leading zeros. <REALM> denotes the realm which may consist of 3 labels , e.g. hnb. femtocellvendor.com. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.10 |
3,582 | 6.3.4.6 Subslot PUCCH / subslot PUSCH / SRS time mask for subslot TTI | The subslot PUCCH/subslot PUSCH/SRS time mask defines the observation period between sounding reference symbol (SRS) in the last symbol in subslot N and an adjacent subslot PUSCH/subslot PUCCH symbol in subslot N+1. 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 Following time masks requirement shall be applied when SRS is either transmitted or blanked: - the transient period shall be placed in Reference symbol when the transient is in between Reference symbol and SRS (figure 6.3.4.6-1, figure 6.3.4.6-2, figure 6.3.4.6-5 and figure 6.3.4.6-7). - the transient period shall be equally shared when the transien is in between Data symbol and SRS (figure 6.3.4.6-3 and figure 6.3.4.6-4). Figure 6.3.4.6-1: subslot PUSCH/SRS time mask when there is a Reference symbol before SRS (or SRS blanking) and data symbol after Figure 6.3.4.6-2:subslot PUSCH/SRS time mask when there is a Reference symbol before SRS (or SRS blanking) and Reference symbol after Figure 6.3.4.6-3: subslot PUSCH/SRS time mask when there is a data symbol before SRS (or SRS blanking) and data symbol after Figure 6.3.4.6-4: subslot PUSCH/SRS time mask when there is a data symbol before SRS (or SRS blanking) and Reference symbol after Figure 6.3.4.6-5: subslot PUSCH/SRS time mask when there is a no symbol before SRS Figure 6.3.4.6-6: subslot PUSCH/SRS time mask when there is a no symbol after SRS Figure 6.3.4.6-7: subslot PUSCH/SRS time mask when there is a no symbol before and after SRS | 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.6 |
3,583 | 4.3.14 Location Service functions | LCS procedures are described in the LCS stage 2 specification, see TS 23.271[ Functional stage 2 description of Location Services (LCS) ] [57]. In addition, in the Detach and Bearer Deactivation procedures, the MME shall inform the S-GW of the last known location of the UE, and shall provide information to enable the determination of the time at which the UE was in that location. The S-GW shall (if necessary taking into account information from the SGSN) inform the PDN GW of the last known location of the UE, and shall provide information to enable the determination of the time at which the UE was in that location. If requested by the PCRF the PDN GW shall indicate this information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. The information can also be made available on the SGi interface as specified in TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38] and on the CDRs at network elements such as the S-GW and PDN GW as specified in TS 32.251[ Telecommunication management;Charging management;Packet Switched (PS) domain charging ] [44]. | 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.14 |
3,584 | 9.9 Other information elements 9.9.1 General | The different formats (V, LV, T, TV, TLV, LV-E, TLV-E) and the five categories of information elements (type 1, 2, 3, 4 and 6) are defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]. The first octet of an information element in the non-imperative part contains the IEI of the information element. If this octet does not correspond to an IEI known in the message, the receiver shall determine whether this IE is of type 1 or 2 (i.e. it is an information element of one octet length), an IE of type 4 (i.e. that the next octet is the length indicator indicating the length of the remaining of the information element or an IE of type 6 (i.e. that the next 2 octets are the length indicator indicating the length of the remaining of the information element) (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]). This allows the receiver to jump over unknown information elements and to analyse any following information elements. The definitions of information elements which are common for the EMM and ESM protocols or which are used by access stratum protocols are described in clause 9.9.2. The information elements of the EMM or ESM protocols can be defined by reference to an appropriate specification, e.g., "see clause 10.5.6.3 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 | 9.9 |
3,585 | 1.8 Handling of NAS signalling low priority indication | An MS configured for NAS signalling low priority (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135], 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) indicates this by including the Device properties IE in the appropriate NAS message and setting the low priority indicator to "MS is configured to NAS signalling low priority" except for the following cases in which the MS shall set the low priority indicator to "MS is not configured for NAS signalling low priority": - the MS is performing an attach for emergency bearer services; - the MS has a PDN connection for emergency bearer services established and is performing mobility management procedures, or is establishing a PDN connection for emergency bearer services; - the MS configured for dual priority is requested by the upper layers to establish a PDN connection with the low priority indicator set to "MS is not configured for NAS signalling low priority"; - the MS configured for dual priority is performing session management procedures related to the PDN connection established with low priority indicator set to "MS is not configured for NAS signalling low priority"; - the MS configured for dual priority has a PDN connection established by setting the low priority indicator to "MS is not configured for NAS signalling low priority" and is performing mobility management procedures; - the MS is establishing or re-establishing an MM connection for an emergency call; - the MS is an MS configured to use AC11 – 15 in selected PLMN; or - the MS is responding to paging. The network may use the NAS signalling low priority indication for NAS level mobility management congestion control on a per core network node basis and APN based congestion control. If the NAS signalling low priority indication is provided in an ACTIVATE PDP CONTEXT REQUEST message, the SGSN stores the NAS signalling low priority indication within the default PDP context activated due to this request. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 1.8 |
3,586 | 16.9.9.5 Resource Allocation | A UE using mode 2 resource allocation may support resource selection enhancements to avoid LBT blocking and increase COT resource utilization. If transmission in slot(s) before a reserved resource is able to share its initiated COT to the reservation, the UE may be (pre)configured to prioritize/select resource(s) in the slot(s) for transmission. To avoid blocking, a UE may avoid selection of a number of consecutive resources (up to UE implementation) before a reserved resource. Furthermore, a UE may avoid selection of a number of consecutive resources (up to UE implementation) after a reserved resource. A UE using mode 2 resource allocation supports resource selection for multiple consecutive slot transmission (MCSt). A UE autonomously determines whether to use MCSt, and the number of consecutive slots in an MCSt up to the maximum COT duration for a specific SL-CAPC as defined in TS 37.213[ Physical layer procedures for shared spectrum channel access ] [37]. MCSt can be used for transmission of a single TB or multiple TBs. For each TB transmitted in an MCSt, the UE triggers resource (re)selection only when LBT failure is detected on the resources for the initial transmission and all retransmissions of the TB. When performing LCP procedure for transmission of multiple TBs in an MCSt, a UE may perform an enhanced LCP procedure as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6] based on the SL-CAPC used for LBT of the first TB. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.9.5 |
3,587 | 5.15.2.3 Relaying | The SGSN performs relaying between BSSGP messages, RANAP messages and GTP messages as described in TS 48.018[ None ] [42], TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [22], TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [14] and TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. The MME performs relaying between S1 and S3/Gn messages as described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36] and TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43] / TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [14]. | 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.15.2.3 |
3,588 | 6.4.1.6 Abnormal cases in the UE | The following abnormal cases can be identified: a) Expiry of timer T3580 The UE shall, on the first expiry of the timer T3580: - if the PDU SESSION ESTABLISHMENT REQUEST message was sent with request type set to "initial emergency request" or "existing emergency PDU session", then the UE may: a) inform the upper layers of the failure of the procedure; or NOTE 1: This can result in the upper layers requesting another emergency call attempt using domain selection as specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. b) de-register locally, if not de-registered already, attempt initial registration for emergency services. If the UE sent the PDU SESSION ESTABLISHMENT REQUEST message in order to perform a handover of an existing emergency PDU session between 3GPP access and non-3GPP access, the UE shall consider that the emergency PDU session is associated with the source access type. - otherwise, retransmit the PDU SESSION ESTABLISHMENT REQUEST message and the PDU session information which was transported together with the initial transmission of the PDU SESSION ESTABLISHMENT REQUEST message and shall reset and start timer T3580, if still needed. This retransmission can be repeated up to four times, i.e. on the fifth expiry of timer T3580, the UE shall abort the procedure, release the allocated PTI and enter the state PROCEDURE TRANSACTION INACTIVE. If the UE sent the PDU SESSION ESTABLISHMENT REQUEST message in order to perform a handover of an existing non-emergency PDU session between 3GPP access and non-3GPP access, the UE shall consider that the PDU session is associated with the source access type. b) Upon receiving an indication that the 5GSM message was not forwarded due to routing failure along with a PDU SESSION ESTABLISHMENT REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3580 and shall abort the procedure. If the UE sent the PDU SESSION ESTABLISHMENT REQUEST message in order to perform a handover of an existing PDU session between 3GPP access and non-3GPP access, the UE shall consider that the PDU session is associated with the source access type. b1) Upon receiving an indication that the 5GSM message was not forwarded due to service area restrictions along with a PDU SESSION ESTABLISHMENT REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3580 and shall abort the procedure. If the UE sent the PDU SESSION ESTABLISHMENT REQUEST message in order to perform a handover of an existing PDU session between 3GPP access and non-3GPP access, the UE shall consider that the PDU session is associated with the source access type. b2) Upon receiving an indication that the 5GSM message was not forwarded because the UE is registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location along with a PDU SESSION ESTABLISHMENT REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3580 and shall abort the procedure. b3) Upon receiving an indication that the 5GSM message was not forwarded because the UE is marked in the UE's 5GMM context that it is not allowed to request UAS services along with a PDU SESSION ESTABLISHMENT REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3580 and shall abort the procedure. The UE shall not trigger the PDU session establishment procedure until the UE is deregistered from the PLMN. b4) Upon receiving an indication that the 5GSM message was not forwarded because the PLMN's maximum number of PDU sessions has been reached along with a PDU SESSION ESTABLISHMENT REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3580 and shall abort the procedure. c) Collision of UE-requested PDU session establishment procedure and network-requested PDU session release procedure. If the UE receives a PDU SESSION RELEASE COMMAND message after sending a PDU SESSION ESTABLISHMENT REQUEST message to the network, and the PDU session ID in the PDU SESSION RELEASE COMMAND message is the same as the PDU session ID in the PDU SESSION ESTABLISHMENT REQUEST message: i) if the UE-requested PDU session establishment procedure was to request the establishment of user plane resources on the second access for an MA PDU session established on a first access and the Access type IE is not included in PDU SESSION RELEASE COMMAND or the Access type IE included in PDU SESSION RELEASE COMMAND indicates the first access, the UE shall proceed with the network-requested PDU session release procedure, abort the UE-requested PDU session establishment procedure, stop timer T3580, release the allocated PTI and enter the state PROCEDURE TRANSACTION INACTIVE; ii) if the PDU SESSION ESTABLISHMENT REQUEST message was sent with request type set to "existing PDU session" or "existing emergency PDU session" in order to perform a handover of an existing PDU session between 3GPP access and non-3GPP access, the UE shall abort the PDU session establishment procedure and proceed with the network-requested PDU session release procedure; or iii) otherwise, the UE shall ignore the PDU SESSION RELEASE COMMAND message and proceed with the UE-requested PDU session establishment procedure. d) Inter-system change from N1 mode to S1 mode triggered during UE-requested PDU session establishment procedure. If the UE-requested PDU session establishment procedure is triggered for handover of an existing PDU session from non-3GPP access to 3GPP access, and the inter-system change from N1 mode to S1 mode is triggered by the NG-RAN and the UE did not receive response to PDU session establishment request, then the UE shall abort the procedure, stop timer T3580, and notify the upper layer of the handover failure. NOTE 2: This can result in the upper layer requesting re-initiation of handover from non-3GPP access to 3GPP access after the inter-system change is completed, if still required. e) For an MA PDU session established on a single access, upon receipt of a PDU SESSION ESTABLISHMENT ACCEPT message over the other access, if any value of the selected PDU session type, selected SSC mode, 5GSM cause, PDU address, S-NSSAI, DNN IEs in the PDU SESSION ESTABLISHMENT ACCEPT message is different from the corresponding stored value, the UE shall perform a local release of the MA PDU session, and perform the registration procedure for mobility and periodic registration update with a REGISTRATION REQUEST message including the PDU session status IE over both accesses. f) For an MA PDU session has a PDN connection as a user-plane resource, upon receipt of a PDU SESSION ESTABLISHMENT ACCEPT message over non-3GPP access, if any value of the selected PDU session type, selected SSC mode, 5GSM cause, PDU address, S-NSSAI, DNN IEs in the PDU SESSION ESTABLISHMENT ACCEPT message is different from the corresponding stored mapped value, the UE shall perform a local release of the MA PDU session, perform the registration procedure for mobility and periodic registration update with a REGISTRATION REQUEST message including the PDU session status IE over non-3GPP access, and perform the tracking area updating procedure as specified in subclause 5.5.3.2.2 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] with a TRACKING AREA UPDATE REQUEST message including EPS bearer context status IE. g) Collision of UE-requested PDU session establishment procedure initiated to perform handover of an existing PDU session from non-3GPP access to 3GPP access and a notification from the network with access type indicating non-3GPP access. If the UE receives a notification from the network with access type indicating non-3GPP access after sending a PDU SESSION ESTABLISHMENT REQUEST message to perform handover of an existing PDU session from non-3GPP access to 3GPP access, the UE shall abort the PDU session establishment procedure, stop timer T3580, proceed with the service request procedure to perform handover of existing PDU session(s) from non-3GPP access to 3GPP access. h) Collision of UE-requested PDU session establishment procedure and N1 NAS signalling connection release The UE may immediately retransmit the PDU SESSION ESTABLISHMENT REQUEST message and stop, reset and restart timer T3580, if the following conditions apply: 1) The original UE-requested PDU session establishment procedure was initiated over an existing N1 NAS signalling connection; 2) the previous transmission of the PDU SESSION ESTABLISHMENT REQUEST message was not initiated due to timer T3580 expiry; and 3) no 5GSM message related to the PDU session (e.g. PDU SESSION AUTHENTICATION COMMAND message) was received after the PDU SESSION ESTABLISHMENT REQUEST message was transmitted. i) Collision of UE-requested PDU session establishment procedure and network-requested PDU session modification procedure If the UE receives a PDU SESSION MODIFICATION COMMAND message after sending a PDU SESSION ESTABLISHMENT REQUEST message to the network, and the PDU session ID in the PDU SESSION MODIFICATION COMMAND message is the same as the PDU session ID in the PDU SESSION ESTABLISHMENT REQUEST message: i) if the UE-requested PDU session establishment procedure was to request the establishment of user plane resources on the second access for an MA PDU session established on a first access, the UE shall proceed with both the UE-requested PDU session establishment procedure and the network-requested PDU session modification procedure; or ii) if the PDU SESSION ESTABLISHMENT REQUEST message was sent with request type set to "existing PDU session" or "existing emergency PDU session" in order to perform a handover of an existing PDU session between 3GPP access and non-3GPP access, the UE shall proceed with the UE-requested PDU session establishment procedure and abort the network-requested PDU session modification procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.1.6 |
3,589 | 5.7.3a.3 Actions related to transmission of SCGFailureInformationEUTRA message | The UE shall set the contents of the SCGFailureInformationEUTRA message as follows: 1> include failureType within failureReportSCG-EUTRA and set it to indicate the SCG failure in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.6.13.4; 1> include and set measResultSCG-FailureMRDC in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.6.13.5; 1> for each EUTRA frequency the UE is configured to measure by measConfig for which measurement results are available: 2> set the measResultFreqListMRDC to include the best measured cells, ordered such that the best cell is listed first using RSRP to order if RSRP measurement results are available for cells on this frequency, otherwise using RSRQ to order if RSRQ measurement results are available for cells on this frequency, otherwise using SINR to order, and based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available; NOTE: Field measResultSCG-FailureMRDC is used to report available results for E-UTRAN frequencies the UE is configured to measure by E-UTRA RRC signalling. 1> if available, set the locationInfo as in 5.3.3.7.: The UE shall submit the SCGFailureInformationEUTRA message to lower layers for transmission. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3a.3 |
3,590 | 9.2.2.2 TDD | The following requirements apply to UE Category ≥2. For the parameters specified in table 9.2.2.2-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 – Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 – 1 and median CQI1 – 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.2.2.2-1: PUCCH 1-1 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.2.2 |
3,591 | 6.1.4 Protocol stacks of IAB | Figure 6.1.4-1 shows the protocol stack for F1-U between IAB-DU and the IAB-donor-CU-UP, and Figure 6.1.4-2 shows the protocol stack for F1-C between IAB-DU and the IAB-donor-CU-CP. In these example figures, F1-U and F1-C traffic are carried over two backhaul hops. NOTE: F1 needs to be security-protected as described in TS 33.501[ Security architecture and procedures for 5G System ] . The security layer is not shown in the Figure 6.1.4-1, Figure 6.1.4-2 and Figure 6.1.4-3. Figure 6.1.4-1: Protocol stack for F1-U of IAB Figure. 6.1.4-2: Protocol stack for F1-C of IAB Figure 6.1.4-3 shows the protocol stack for F1-C between IAB-DU and the IAB-donor-CU-CP, when the F1-C traffic is exchanged via the MeNB. Fig. 6.1.4-3: Protocol stack for IAB F1-C traffic exchanged via the MeNB Figure 6.1.4-4 shows the protocol stack for F1-C between IAB-DU and the IAB-donor-CU-CP, when the F1-C traffic is exchanged via the MgNB. Fig. 6.1.4-4: Protocol stack for IAB F1-C traffic exchanged via the MgNB Figure 6.1.4-5 shows the protocol stack for F1-C between IAB-DU and the IAB-donor-CU-CP, when the F1-C traffic is exchanged via the SgNB. Fig. 6.1.4-5: Protocol stack for IAB F1-C traffic exchanged via the SgNB | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 6.1.4 |
3,592 | 5.2.6.9.3 Nnef_AFsessionWithQoS_Notify service operation | Service operation name: Nnef_AFsessionWithQoS Notify Description: NEF reports the QoS Flow level event(s) to the consumer. Inputs, Required: Reports of the events as defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], Transaction Reference ID if a list of UE is targeted. NOTE: When the event report is for Consolidated Data Rate monitoring, the QoS Flow data rate reporting for the list of UEs provided to the AF by the NEF only when the Consolidated Data Rate threshold is exceeded. Inputs, Optional: When the event report is for QoS Monitoring, includes QoS Monitoring report for the QoS parameter(s) to be measured defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], e.g. UL packet delay, DL packet delay, or round trip packet delay, UL and/or DL data rate of the single UP path or two UP paths in the case of redundant transmission, as defined in clause 5.33.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the AF has provided Capability for BAT Adaptation or BAT Window, can include BAT offset as described in clause 5.27.2.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the delivery report is for Consolidated Data Rate Monitoring, includes Consolidated Data Rate Monitoring report. Outputs, Required: None. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.9.3 |
3,593 | – PDCCH-ConfigCommon | The IE PDCCH-ConfigCommon is used to configure cell specific PDCCH parameters provided in SIB as well as in dedicated signalling. PDCCH-ConfigCommon information element -- ASN1START -- TAG-PDCCH-CONFIGCOMMON-START PDCCH-ConfigCommon ::= SEQUENCE { controlResourceSetZero ControlResourceSetZero OPTIONAL, -- Cond InitialBWP-Only commonControlResourceSet ControlResourceSet OPTIONAL, -- Need R searchSpaceZero SearchSpaceZero OPTIONAL, -- Cond InitialBWP-Only commonSearchSpaceList SEQUENCE (SIZE(1..4)) OF SearchSpace OPTIONAL, -- Need R searchSpaceSIB1 SearchSpaceId OPTIONAL, -- Need S searchSpaceOtherSystemInformation SearchSpaceId OPTIONAL, -- Need S pagingSearchSpace SearchSpaceId OPTIONAL, -- Need S ra-SearchSpace SearchSpaceId OPTIONAL, -- Need S ..., [[ firstPDCCH-MonitoringOccasionOfPO CHOICE { sCS15KHZoneT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139), sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279), sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559), sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119), sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239), sCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479), sCS120KHZoneEighthT-SCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959), sCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919) } OPTIONAL -- Cond OtherBWP ]], [[ commonSearchSpaceListExt-r16 SEQUENCE (SIZE(1..4)) OF SearchSpaceExt-r16 OPTIONAL -- Need R ]], [[ sdt-SearchSpace-r17 CHOICE { newSearchSpace SearchSpace, existingSearchSpace SearchSpaceId } OPTIONAL, -- Need R searchSpaceMCCH-r17 SearchSpaceId OPTIONAL, -- Need R searchSpaceMTCH-r17 SearchSpaceId OPTIONAL, -- Need S commonSearchSpaceListExt2-r17 SEQUENCE (SIZE(1..4)) OF SearchSpaceExt-v1700 OPTIONAL, -- Need R firstPDCCH-MonitoringOccasionOfPO-v1710 CHOICE { sCS480KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..35839), sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..71679) } OPTIONAL, -- Need R pei-ConfigBWP-r17 SEQUENCE { pei-SearchSpace-r17 SearchSpaceId, firstPDCCH-MonitoringOccasionOfPEI-O-r17 CHOICE { sCS15KHZoneT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..139), sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..279), sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..559), sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..1119), sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..2239), sCS480KHZoneT-SCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..4479), sCS480KHZhalfT-SCS120KHZoneEighthT-SCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..8959), sCS480KHZquarterT-SCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..17919), sCS480KHZoneEighthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..35839), sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..71679) } } OPTIONAL -- Cond InitialBWP-Paging ]], [[ followUnifiedTCI-State-v1720 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ applyIndicatedTCI-State-r18 ENUMERATED {first, second, both, none} OPTIONAL, -- Cond FollowUTCI commonSearchSpaceListExt-r18 SEQUENCE (SIZE(1..4)) OF SearchSpaceExt-v1800 OPTIONAL, -- Need R searchSpaceMulticastMCCH-r18 SearchSpaceId OPTIONAL, -- Need R searchSpaceMulticastMTCH-r18 SearchSpaceId OPTIONAL -- Need S ]] } -- TAG-PDCCH-CONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,594 | 5.12.2 Usage Data Reporting for Secondary RAT | When NG-RAN is deployed in dual connectivity configuration, the HPLMN or VPLMN operator may wish to record the data volume sent and received on the Secondary RAT. In order to reduce the complexity of this procedure, the following principles are used in this release: a) The PLMN locally activates the Secondary RAT Usage Data Reporting by NG-RAN OAM. The activation is based on configuration in NG-RAN and NG-RAN determines whether the data volume report will contain data volumes consumed for the whole PDU Session or for selected QoS Flows or both as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. The activation can happen separately for Data Volume Reporting of NR in licensed or unlicensed spectrum and E-UTRA in licensed or unlicensed spectrum. If the PLMN uses this feature, it should ensure that this functionality is supported by all NG-RAN nodes that support NR or E-UTRA as a Secondary RAT. b) Depending on its configuration the NG-RAN reports uplink and downlink data volumes to the 5GC for the Secondary RAT (including the using of unlicensed spectrum for NR or E-UTRA) for the PDU Session or for selected QoS Flows or both and per time interval. c) During Xn handover and N2 handover, the source NG-RAN node reports the data volume to the 5GC. The reported data volume excludes data forwarded to the target RAN node. d) At the time of NG connection release, Secondary RAN Node change/release, deactivation of UP connection for a PDU Session, the NG-RAN node reports the data volumes to the 5GC. e) To assist "partial CDR" generation, NG-RAN OAM can instruct the NG-RAN to also make periodic reports (as described in clause 5.12.3) if no event has triggered a report before the period expires. NOTE 2: The timing of these periodic NG-RAN reports is not expected to align with the timing of partial CDR generation. Hence the frequency of NG-RAN reports might be greater than that of partial CDR generation. NOTE 3: RAN needs to be able to partition the measurements in a report to indicate usage that occurred before and after an absolute time. An example of the absolute time is that RAN is configured to partition data usage reports that occurred before and after midnight. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.12.2 |
3,595 | 5.15.12.2 UE and UE configuration aspects | A UE may support the subscription-based restrictions to simultaneous registration of network slices feature. In this case, the UE indicates its support in the Registration Request message in the Initial Registration and the Mobility Registration Update as part of the UE 5GMM Core Network Capability. When the serving AMF provides the Configured NSSAI to the UE, and the UE has indicated it supports the subscription-based restrictions to simultaneous registration of network slices feature, the AMF also provides the UE with the NSSRG information related to the S-NSSAIs of the HPLMN which are in the mapping information of the Configured NSSAI. A UE which receives the NSSRG values in the network slicing configuration information shall only include in the Requested NSSAI S-NSSAIs that share a common NSSRG as per the received information. If the UE has stored Pending NSSAI and the UE is still interested in the Pending NSSAI then all the S-NSSAIs in the Requested NSSAI and the Pending S-NSSAI shall share a common NSSRG. If the HPLMN changes NSSRG information in the subscription information for a UE, the UDM updates the supporting AMF serving the UE with the new NSSRG information and the AMF, possibly after interaction with the NSSF (see clause 5.2.16.2.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), updates the UE as necessary with network slicing configuration by means of the UE Configuration Update procedure (this may include changes in the Configured NSSAI (and related mapping information) and changes in the Allowed NSSAI as applicable). The UE acknowledges this UE Configuration Update according to clause 4.2.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. At any time, a UE supporting subscription-based restrictions to simultaneous registration of network slices feature and that has received NSSRG information together with the Configured NSSAI shall only request S-NSSAIs, across all Access Type(s) regardless of whether the same PLMN or different PLMNs are used, that share one or more common NSSRG. NOTE: In Requested NSSAI across all Access Type(s), the UE needs to include S-NSSAIs that share at least one common NSSRG. An AMF which supports the subscription-based restrictions to simultaneous registration of network slice feature configures a non-supporting UE with a Configured NSSAI including only the S-NSSAIs sharing all the NSSRG values of the default S-NSSAI(s), except if it has been instructed otherwise by the UDM. In addition to the default S-NSSAI(s), the AMF sends to the UE in the Configured NSSAI any other subscribed S-NSSAI whose NSSRG match at least those defined for the default S-NSSAI(s). The UDM in a supporting HPLMN may optionally keep a record of the PEIs or Type Allocation Codes values regarding UE ability to handle network slices that cannot be provided simultaneously in Allowed NSSAI. The UDM may, based on configuration or the optional PEI records, indicate the AMF to provide the non-supporting UEs with the full set of subscribed S-NSSAIs even if they do not share a common NSSRG. The UDM instructs the supporting AMFs of a PLMN to do so by indicating that the UE can be given a Configured NSSAI with all the S-NSSAIs in the subscription information. If this indication is received from the UDM by the AMF, this is included in the UE context. Based on its policy (including configuration or optionally checking the specific PEI or Type Allocation Code used by the UE, and subject to roaming agreement) the UDM may also provide the serving AMF in a non-supporting VPLMN with all the S-NSSAI in the subscription information. In this case the AMF provides the UE with a Configured NSSAI including all the S-NSSAIs in the subscription information the AMF receives. The AMF provides no NSSRG information to a non-supporting UE. When an AMF which supports the subscription-based restrictions to simultaneous registration of network slice feature, receives from a UE a Requested NSSAI including S-NSSAIs that are supported in the Tracking Area but do not share a common NSSRG, or the AMF has pending NSSAI stored for the UE, and the S-NSSAI(s) of the requested NSSAI and the pending NSSAI do not share a common NSSRG, the AMF assumes the UE configuration is not up-to-date, and provides the following: - a supporting UE with an updated configuration including the up-to-date NSSRG information for the S-NSSAIs in the Configured NSSAI as described above. - a non-supporting UE with an updated Configured NSSAI including only the S-NSSAIs sharing all the NSSRG values of the default S-NSSAI(s), only for the case where the UE context does not include an indication to provide all the subscribed S-NSSAIs in the subscription information in the Configured NSSAI for the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.12.2 |
3,596 | A.21 Use case of UE power headroom | E-UTRAN UE power headroom measurement is important for analyzing UE power distribution, to learn whether the uplink signal strength can be increased or not. So it is very useful to do trouble shooting of coverage hole and coverage balance for uplink. It is also used to evaluate the power control performance and increase UE power headroom as possible with QoS is guaranteed for the purpose of energy saving. These questions are determined by the ratio of the number of larger or less than threshold to the total number of it and the threshold is configurable. According to network optimization experience, the granularity of measurement 1dB is enough to do trouble shooting of coverage hole and evaluation of power control. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.21 |
3,597 | 10.5.4.20 Notification indicator | The purpose of the notification indicator information element is to indicate information pertaining to a call. The notification indicator element is coded as shown in figure 10.5.106/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.126/ 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The notification indicator is a type 3 information element with 2 octets length. Figure 10.5.106/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Notification indicator information element Table 10.5.126/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Notification indicator information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.20 |
3,598 | 5.8.9.1.2 Actions related to transmission of RRCReconfigurationSidelink message | The UE shall set the contents of RRCReconfigurationSidelink message as follows: 1> for each sidelink DRB that is to be released, according to clause 5.8.9.1a.1.1, due to configuration by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or by upper layers: 2> set the entry included in the slrb-ConfigToReleaseList corresponding to the sidelink DRB; 1> for each sidelink DRB that is to be established or modified, according to clause 5.8.9.1a.2.1, due to receiving sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR: 2> if the sidelink DRB is a per-hop sidelink DRB (i.e. the UE is not acting as a L2 U2U Remote UE): 3> if a sidelink DRB is to be established: 4> assign a new logical channel identity for the logical channel to be associated with the sidelink DRB and set sl-MAC-LogicalChannelConfigPC5 in the SLRB-Config to include the new logical channel identity; 3> set the SLRB-Config included in the slrb-ConfigToAddModList, according to the received sl-RadioBearerConfig and sl-RLC-BearerConfig corresponding to the sidelink DRB; 2> else if the sidelink DRB is an end-to-end sidelink DRB (i.e. the UE is acting as a L2 U2U Remote UE, and configure peer L2 U2U Remote UE with end-to-end SDAP and PDCP, or provide the L2 Relay UE with the QoS flow to end-to-end DRB mapping): 3> if the UE is in RRC_CONNECTED: 4> set the SLRB-Config included in the slrb-ConfigToAddModList, according to the received sl-RadioBearerConfig in sl-ConfigDedicatedNR; 3> else if the UE is in RRC_IDLE/RRC_INACTIVE: 4> set the SLRB-Config included in the slrb-ConfigToAddModList, which is derived by end-to-end QoS profile, according to the sl-RadioBearerConfig in SIB12; 3> if the UE is out of coverage: 4> set the SLRB-Config included in the slrb-ConfigToAddModList, which is derived by end-to-end QoS profile, according to the sl-RadioBearerConfig in SidelinkPreconfigNR; 1> for each additional sidelink RLC bearer that is to be released, according to clause 5.8.9.1a.5.1, due to configuration by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or by upper layers: 2> set the entry included in the sl-RLC-BearerToReleaseList corresponding to the additional sidelink RLC bearer; 1> for each additional sidelink RLC bearer that is to be established or modified, according to clause 5.8.9.1a.6.1, due to receiving sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR: 2> if an additional sidelink RLC bearer is to be established: 3> assign a new logical channel identity for the logical channel to be associated with the sidelink DRB and set sl-MAC-LogicalChannelConfigPC5 in the SL-RLC-BearerConfig to include the new logical channel identity; 2> set the SL-RLC-BearerConfig included in the sl-RLC-BearerToAddModList, according to the received sl-RadioBearerConfig and sl-RLC-BearerConfig corresponding to the additional sidelink RLC bearer; 1> set the entry included in the sl-CarrierToReleaseList corresponding to the sidelink carrier(s) for which MAC entity indicates that the maximum number of consecutive HARQ DTX for a specific destination has been reached; 1> set the entry included in the sl-CarrierToAddModList corresponding to the sidelink carrier, taking into account of at least carrier(s) mapped to the sidelink QoS flow(s) configured by the upper layer, carriers configured in sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR, and carrier(s) supported by both UEs; 1> set the sl-MeasConfig as follows: 2> If the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12: 3> if UE is in RRC_CONNECTED: 4> set the sl-MeasConfig according to stored NR sidelink measurement configuration information for this destination; 3> if UE is in RRC_IDLE or RRC_INACTIVE: 4> set the sl-MeasConfig according to stored NR sidelink measurement configuration received from SIB12; 2> else: 3> set the sl-MeasConfig according to the sl-MeasPreConfig in SidelinkPreconfigNR; 1> set the sl-LatencyBoundIUC-Report; 1> start timer T400 for the destination; 1> set the sl-CSI-RS-Config; 1> set the sl-LatencyBoundCSI-Report; 1> set the sl-ResetConfig; NOTE 1: Whether/how to set the parameters included in sl-LatencyBoundIUC-Report, sl-CSI-RS-Config, sl-LatencyBoundCSI-Report and sl-ResetConfig is up to UE implementation. 1> set the sl-DRX-ConfigUC-PC5 as follows: 2> If the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12: 3> if UE is in RRC_CONNECTED and if sl-ScheduledConfig is included in sl-ConfigDedicatedNR within RRCReconfiguration: 4> set the sl-DRX-ConfigUC-PC5 according to stored NR sidelink DRX configuration information for this destination; NOTE 2: If UE is in RRC_IDLE or in RRC_INACTIVE or out of coverage, or in RRC_CONNECTED and sl-UE-SelectedConfig is included in sl-ConfigDedicatedNR within RRCReconfiguration, it is up to UE implementation to set the sl-DRX-ConfigUC-PC5. 1> for each PC5 Relay RLC channel that is to be released due to configuration by sl-ConfigDedicatedNR: 2> set the SL-RLC-ChannelID corresponding to the PC5 Relay RLC channel in the sl-RLC-ChannelToReleaseListPC5; 1> for each PC5 Relay RLC channel that is to be established or modified due to receiving sl-ConfigDedicatedNR: 2> if a PC5 Relay RLC channel is to be established: 3> assign a new logical channel identity for the logical channel to be associated with the PC5 Relay RLC channel and set sl-MAC-LogicalChannelConfigPC5 in the SL-RLC-ChannelConfigPC5 to include the new logical channel identity; 2> set the SL-RLC-ChannelConfigPC5 included in the sl-RLC-ChannelToAddModListPC5 according to the received SL-RLC-ChannelConfig corresponding to the PC5 Relay RLC channel, including setting sl-RLC-ChannelID-PC5 to the same value of sl-RLC-ChannelID received in SL-RLC-ChannelConfig; 1> if the UE is operating as a L2 U2N Relay UE: 2> if the destination UE is a L2 U2N Remote UE that requested the SFN-DFN offset in a previous RemoteUEInformationSidelink message: 3> if the SFN-DFN offset has changed since a previous transmission of the RRCReconfigurationSidelink message, or no previous transmission of the RRCReconfigurationSidelink message has occurred since the reception of the RemoteUEInformationSidelink message: 4> set the sl-SFN-DFN-Offset according to the relation between the SFN timeline of the PCell and the DFN timeline; 1> if the UE is acting as L2 U2U Relay UE, and if the procedure is initiated to configure local ID to the connected L2 U2U Remote UEs: 2> if the local ID pair is to be assigned or modified for an end-to-end PC5 connetion, and if both the PC5-RRC connection with L2 U2U Remote UE and the PC5-RRC connection with peer L2 U2U Remote UE are successfully established: 3> include an entry in sl-LocalID-PairToAddModList, and set the fields as below: 4> according to association between User Info and L2 ID as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65], set sl-RemoteUE-LocalIdentity to include the new local UE ID, and set sl-RemoteUE-L2Identity to include the source L2 ID of L2 U2U Remote UE in the SL-SRAP-ConfigPC5, if needed; 4> according to association between User Info and L2 ID as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65], set sl-PeerRemoteUE-LocalIdentity to include the new local UE ID, and and set sl-PeerRemoteUE-L2Identity to include the destination L2 ID of peer L2 U2U Remote UE in the SL-SRAP-ConfigPC5, if needed; 2> else if the local ID pair is to be released for an end-to-end PC5 connetion: 3> include an entry in sl-LocalID-PairToReleaseList, with the value of SL-DestinationIdentity set to the destination L2 ID of the peer L2 U2U Remote UE; 1> if the UE is acting as L2 U2U Remote UE (i.e. Tx UE), and if the procedure is initiated to configure the first hop PC5 Relay RLC channel of an end-to-end sidelink DRB to the connected L2 U2N Relay UE (i.e. Rx UE), based on configuration in SIB12 or SidelinkPreconfigNR; or 1> if the UE is acting as L2 U2U Relay UE (i.e. Tx UE) and is in RRC_IDLE or in RRC_INACTIVE or OoC, and if the procedure is initiated to configure the second hop PC5 Relay RLC channel to the connected L2 U2N Remote UE (i.e. Rx UE) based on configuration in SIB12 or SidelinkPreconfigNR: 2> if a PC5 Relay RLC channel is to be established: 3> assign a new RLC channel ID and set sl-RLC-ChannelID-PC5 in the SL-RLC-ChannelConfigPC5 to include the new RLC channel ID; 3> assign a new logical channel identity for the logical channel to be associated with the PC5 Relay RLC channel and set sl-MAC-LogicalChannelConfigPC5 in the SL-RLC-ChannelConfigPC5 to include the new logical channel identity; 3> if the UE is in RRC_IDLE or in RRC_INACTIVE: 4> set the SL-RLC-ChannelConfigPC5 included in the sl-RLC-ChannelToAddModListPC5 according to the SL-RLC-BearerConfig derived based on the per-hop QoS of the end-to-end SLRB according to SIB12; 3> else if the UE is out of coverage: 4> set the SL-RLC-ChannelConfigPC5 included in the sl-RLC-ChannelToAddModListPC5 according to the SL-RLC-BearerConfig derived based on the per-hop QoS of the SLRB according to SidelinkPreconfigNR; NOTE 3: If UE is in RRC_IDLE or in RRC_INACTIVE or out of coverage, how to merge the split per-flow QoS on the first/second hop into a per-SLRB level QoS for RLC channel configuration derivation is up to UE implementation. The UE shall submit the RRCReconfigurationSidelink message to lower layers for transmission. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1.2 |
3,599 | 4.8.2.3.1 Interworking between NG-RAN and E-UTRAN | At inter-system change from N1 mode to S1 mode in EMM-IDLE mode when: a) the UE supports non-IP PDN type and at least one PDU session of Unstructured PDU session type is active; b) the UE supports IPv4 PDN type and at least one PDU session of IPv4 PDU session type is active; c) the UE supports IPv6 PDN type and at least one PDU session of IPv6 PDU session type is active; d) the UE supports IPv4v6 PDN type and at least one PDU session of IPv4v6 PDU session type is active; or e) at least one PDU session of Ethernet PDU session type is active and: 1) the UE supports non-IP PDN type; or 2) the UE and the network support Ethernet PDN type in S1 mode; the UE shall proceed as follows: a) if the UE supports sending an ATTACH REQUEST message containing a PDN CONNECTIVITY REQUEST message with request type set to "handover" or "handover of emergency bearer services" to transfer a PDU session from N1 mode to S1 mode and the UE has received an "interworking without N26 interface supported" indication from the network, the UE shall: 1) enter substates EMM-DEREGISTERED.NORMAL-SERVICE and 5GMM- DEREGISTERED.NO-CELL-AVAILABLE for 3GPP access; NOTE: Since MM context transfer is not possible between MME and AMF in a network that indicates "Interworking without N26 supported", it is up to the UE implementation as to how to keep the 5GMM and EMM states in the UE in sync. 2) map the PDU session(s) which the UE intends to transfer to EPS to the default EPS bearer context of the corresponding PDN connection(s) as specified in subclause 6.1.4.2; and 3) initiate an EPS attach procedure and include in the ATTACH REQUEST message a PDN CONNECTIVITY REQUEST message with: - the request type set to "handover of emergency bearer services" to activate a default EPS bearer context for an active emergency PDU session, if the session to be transferred is an emergency PDU session; or - the request type set to "handover" message to activate a default EPS bearer context for an active non-emergency PDU session, if the session to be transferred is a non-emergency PDU session. If the selected PDU session is an MA PDU session established over 3GPP access, the UE shall include the ATSSS request parameter in the Protocol configuration options IE or the Extended protocol configuration options IE of the ESM INFORMATION RESPONSE message. After successful completion of the EPS attach procedure, the UE shall reset the registration attempt counter for 3GPP access and the attach attempt counter (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), enter substates EMM-REGISTERED.NORMAL-SERVICE and 5GMM-REGISTERED.NO-CELL-AVAILABLE for 3GPP access and attempt to activate each of the other default EPS bearer contexts, if any, by initiating a stand-alone PDN connectivity procedure with request type set to "handover" for non-emergency PDU session or "handover of emergency bearer services" for emergency PDU session in the PDN CONNECTIVITY REQUEST message. If the EPS attach procedure is unsuccessful the UE shall enter substates EMM-DEREGISTERED.NORMAL-SERVICE and 5GMM-DEREGISTERED.NO-CELL-AVAILABLE for 3GPP access; and b) otherwise, enter substates EMM-REGISTERED.NORMAL-SERVICE and 5GMM-REGISTERED.NO-CELL-AVAILABLE for 3GPP access and initiate a tracking area update procedure (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]). At inter-system change from N1 mode to S1 mode in EMM-IDLE mode when: a) the UE does not support non-IP PDN type or no PDU session of Unstructured PDU session type is active; b) the UE does not support IPv4 PDN type or no PDU session of IPv4 PDU session type is active; c) the UE does not support IPv6 PDN type or no PDU session of IPv6 PDU session type is active; d) the UE does not support IPv4v6 PDN type or no PDU session of IPv4v6 PDU session type is active; and e) no PDU session of Ethernet PDU session type is active or: 1) the UE does not support non-IP PDN type; and 2) the UE, the network or both do not support Ethernet PDN type in S1 mode; the UE shall enter substates EMM-DEREGISTERED.NORMAL-SERVICE and 5GMM-DEREGISTERED.NO-CELL-AVAILABLE for 3GPP access, and initiate an attach procedure. At inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode, the UE shall: a) enter substate 5GMM-REGISTERED.NORMAL-SERVICE for 3GPP access and substate EMM-REGISTERED.NO-CELL-AVAILABLE; b) map the default EPS bearer context(s) of the PDN connection(s) which the UE intends to transfer to 5GS, if any, to the corresponding PDU session(s) as specified in subclause 6.1.4.2; and c) initiate the registration procedure for mobility and periodic registration update over 3GPP access indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message (see subclause 5.5.1.3). After having successfully registered in N1 mode over 3GPP access, the UE shall reset the registration attempt counter for 3GPP access, and the attach attempt counter or tracking area updating attempt counter (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]) and: a) if the UE supports the PDU session establishment procedure with request type set to "existing PDU session" or "existing emergency PDU session" to transfer a PDN connection from S1 mode to N1 mode and the UE has received an "interworking without N26 interface supported" indication from the network, attempt to transfer the PDN connection(s) which the UE intends to transfer to 5GS, if any, from S1 mode to N1 mode by: - if the PDN connection which the UE intends to transfer is a PDN connection for emergency bearer services, initiating the PDU session establishment procedure with request type set to "existing emergency PDU session" to transfer the PDN connection for emergency bearer services; and - if the PDN connection which the UE intends to transfer is a non-emergency PDN connection, initiating the PDU session establishment procedure with request type set to: 1) "MA PDU request", if the PDN connection to be transferred is a user-plane resource of an MA PDU session; or 2) "existing PDU session" to transfer the non-emergency PDN connection; and b) otherwise, establish PDU session(s) corresponding to the PDN connection(s) which the UE intends to transfer to 5GS, if any, by initiating the PDU session establishment procedure with request type set to "initial request". See subclause 5.1.4.3 for coordination between 5GMM and EMM and subclause 6.1.4.2 for coordination between 5GSM and ESM. | 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.8.2.3.1 |
3,600 | 16.4 Public Warning System | NR connected to 5GC provides support for public warning systems (PWS) through means of system information broadcast capability. NR is responsible for scheduling and broadcasting of the warning messages as well as for paging the UE to provide indication that the warning message is being broadcast: - Earthquake and Tsunami Warning System: ETWS is a public warning system developed to meet the regulatory requirements for warning notifications related to earthquake and/or tsunami events (see TS 22.168[ Earthquake and Tsunami Warning System (ETWS) requirements; Stage 1 ] [14]). ETWS warning notifications can either be a primary notification (short notification) or secondary notification (providing detailed information). - Commercial Mobile Alert System: CMAS is a public warning system developed for the delivery of multiple, concurrent warning notifications (see TS 22.268[ Public Warning System (PWS) requirements ] [15]). Different SIBs are defined for ETWS primary notification, ETWS secondary notification and CMAS notification. Paging is used to inform UEs about ETWS indication and CMAS indication (see clause 9.2.5). UE monitors ETWS/CMAS indication in its own paging occasion for RRC_IDLE and for RRC_INACTIVE while no SDT procedure (see clause 18.0) is ongoing. UE monitors ETWS/CMAS indication in any paging occasion for RRC Connected and during the SDT procedure in RRC_INACTIVE. Paging indicating ETWS/CMAS notification triggers acquisition of system information (without delaying until the next modification period). Enhancements of public warning system (ePWS) enable broadcast of language-independent content and notifications to UEs with no user interface or with a user interface that is incapable of displaying text, see clause 9 in TS 22.268[ Public Warning System (PWS) requirements ] [15] and TS 23.041[ Technical realization of Cell Broadcast Service (CBS) ] [54]. ETWS/CMAS notifications with ePWS functionality use the same AS mechanisms as ETWS/CMAS. KPAS and EU-Alert are public warning systems developed for the delivery of multiple, concurrent warning notifications (see TS 22.268[ Public Warning System (PWS) requirements ] [15]). KPAS and EU-Alert uses the same AS mechanisms as CMAS. Therefore, the NR procedures defined for CMAS equally apply for KPAS and EU-Alert. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.4 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.