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
⌀ |
|---|---|---|---|---|---|---|---|
4,101 | 13b.3 Forwarding of user plane packets at the MBMS GW | If user plane data are to be sent to the MBMS Gateway using IP unicast, the MBMS Gateway allocates an IP transport address and a separate UDP port for each MBMS bearer ( i.e the service uniquely identified by its TMGI and Flow ID and provided by the EPS to deliver the same IP datagrams to multiple receivers in a designated location). The MBMS Gateway uses that destination unicast IP address and destination UDP port of user plane packets received over the SGi-mb interface to determine on which MBMS bearer to forward the received user plane packet. If user plane data are to be sent to the MBMS Gateway using IP multicast encapsulation, the MBMS Gateway uses, the SGi-mb (transport) plane destination multicast address used and the SGi-mb (transport) plane source UDP port number provided by the BM-SC of user plane packets received over the SGi-mb interface to determine on which MBMS bearer to forward the received user plane packet. | 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 | 13b.3 |
4,102 | 4.13.1.3 Number of UEs with DL LWA PDUs successfully transmitted over Xw interface | a) This measurement provides the number of UEs for which the outgoing LWA PDUs are successfully transmitted over Xw interface. b) CC. c) On receipt of DL DATA DELIVERY STATUS frame by the eNB from WT indicating the downlink LWA PDUs have been successfully transmitted over the Xw interface (see TS 36.465[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Wireless Local Area Network (WLAN); Xw interface user plane protocol ] [24]) for a UE, the measurement is incremented by 1 in case the UE has not been counted yet for this measurement in the collection period. d) A real value. e) LWI.UeWithDlLwaPDU. f) EP_Xw (Contained by ENBFunction). g) Valid for packet switched traffic. h) EPS. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.13.1.3 |
4,103 | 5.7.10.6 Actions for the successful handover report determination | The UE shall for the PCell: 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync; or 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync; or 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync; or 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if sourceDAPS-FailureReporting is included in the successHO-Config before executing the last reconfiguration with sync and is set to true and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running; or: 1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last Mobility from NR to E-UTRA; or 1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the Mobility from NR to E-UTRA and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last Mobility from NR to E-UTRA: 2> store the successful handover information in VarSuccessHO-Report and determine the content in VarSuccessHO-Report as follows: 3> clear the information included in VarSuccessHO-Report, if any; 3> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN); 3> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., includes the registered SNPN), if available; 3> set the c-RNTI to the C-RNTI assigned by the target PCell of the handover; 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied: 4> set the sourcePCellID in sourceCellInfo to the global cell identity and tracking area code, if available, of the source PCell; 4> set the sourceCellMeas in sourceCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 4> set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 4> if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running: 5> set the rlf-InSourceDAPS in sourceCellInfo to true; 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync: 4> set the targetPCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell; 4> set the targetCellMeas in targetCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message; 4> set the rsIndexResults in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message; 4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig: 5> set the timeSinceCHO-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the last conditionalReconfiguration including the condRRCReconfig of the target PCell in the source PCell; 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the target PCell indicated in the last applied MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA: 4> set the targetPCellId in eutraTargetCellInfo to the global cell identity and tracking area code, if available, of the target PCell; 4> set the targetCellMeas in eutraTargetCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available measurements collected up to the moment the UE sends RRCConnectionReconfigurationComplete message; 3> if the procedure is triggered due to successful completion of reconfiguration with sync and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync: 4> set t304-cause in shr-Cause to true; 4> set the ra-InformationCommon to include the random-access related information associated to the random access procedure in the target PCell, as specified in clause 5.7.10.5; 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or the last Mobility from NR to E-UTRA, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA: 4> set t310-cause in shr-Cause to true; 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync, or Mobility from NR to E-UTRA: 4> set t312-cause in shr-Cause to true; 3> if the procedure is triggered due to successful completion of reconfiguration with sync and if sourceDAPS-FailureReporting included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running: 4> set sourceDAPS-Failure in shr-Cause to true; 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied;or: 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectNR, configured by the source PCell, in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied: 4> if measRSSI-ReportConfig is configured for the frequency of the source PCell: 5> if the procedure is triggered due to successful completion of reconfiguration with sync: 6> set the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the RRCReconfigurationComplete message 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA: 6> set the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message; 4> for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency: 5> if the procedure is triggered due to successful completion of reconfiguration with sync: 6> set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the RRCReconfigurationComplete message; 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA: 6> set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message; 4> if measurements are available for the measObjectNR: 5> if the SS/PBCH block-based measurement quantities are available: 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the cell with highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the cell with highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 6> for each neighbour cell included, include the optional fields that are available; NOTE 1: For the neighboring cells set included in measResultListNR in measResultNeighCells ordered based on the SS/PBCH block measurement quantities, the UE includes also the CSI-RS based measurement quantities, if available. 5> if the CSI-RS measurement quantities are available: 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 6> for each neighbour cell included, include the optional fields that are available; NOTE 2: For the neighboring cells set ordered based on the CSI-RS measurement quantities, the UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS/PBCH block-based ordered measurements. 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or: 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectEUTRA, configured by the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied: 4> if measurements are available for the measObjectEUTRA: 5> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; 5> for each neighbour cell included, include the optional fields that are available; 3> for each of the neighbour cells included in measResultNeighCells: 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied: 5> set the choCandidate to true in measResultNR; 3> if available, set the locationInfo as in 5.3.3.7; 1> release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by the target PCell. The UE may discard the successful handover information, i.e., release the UE variable VarSuccessHO-Report, 48 hours after the last successful handover information is added to the VarSuccessHO-Report. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.10.6 |
4,104 | 6.13 Signalling procedure for PDCP COUNT check | The following procedure is used optionally by the gNB to periodically perform a local authentication. At the same time, the amount of data sent during the AS connection is periodically checked by the gNB and the UE for both up and down streams. If UE receives the Counter Check request, it shall respond with Counter Check Response message. NOTE: The PDCP COUNT check is used to detect maliciously inserted packets. Packet insertion is detected automatically in integrity protected DRBs; therefore, the PDCP COUNT check procedure is superfluous for integrity protected bearers. The gNB is monitoring the PDCP COUNT values associated to each radio bearer. The procedure is triggered whenever any of these values reaches a critical checking value. The granularity of these checking values and the values themselves are defined by the visited network. All messages in the procedure are integrity protected. Figure 6.13-1: gNB periodic local authentication procedure 1. When a checking value is reached (e.g. the value in some fixed bit position in the hyperframe number is changed), a Counter Check message is sent by the gNB. The Counter Check message contains the most significant parts of the PDCP COUNT values (which reflect amount of data sent and received) from each active radio bearer. 2. The UE compares the PDCP COUNT values received in the Counter Check message with the values of its radio bearers. Different UE PDCP COUNT values are included within the Counter Check Response message. 3. If the gNB receives a counter check response message that does not contain any PDCP COUNT values, the procedure ends. If the gNB receives a counter check response that contains one or several PDCP COUNT values, the gNB may release the connection or report the difference of the PDCP COUNT values for the serving AMF or O&M server for further traffic analysis for e.g. detecting the attacker. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.13 |
4,105 | 13.2.4.3.1.1 clearTextEncapsulatedMessage | The clearTextEncapsulatedMessage is a JSON object that contains the non-encrypted portion of the original message.Specifically, it consists of the following objects: 1.a) Pseudo_Headers – the JSON object that includes all the Pseudo Headers in the message. - For HTTP Request messages, the object contains one entry for each of the ":method", ":path", ":scheme" and ":authority" pseudo headers. If the ":path" pseudoheader contains multiple parts separated by a slash (/) or includes a query parameter (following a "?"), an array is used to represent :path, with one element per part of the path (i.e. per "directory"). NOTE: This enables encryption of individual elements of the path (e.g. if SUPI is passed). - For HTTP Response messages, the object contains the ":status" pseudo header. 1.b) HTTP_Headers – the JSON object that includes all the Headers in the message. All the headers of the request are put into a JSON array called HTTP_Headers.Each entry contains a header name and value, where the value part can be an encoded index to the dataToIntegrityProtectAndCipher block, if the header value is encrypted. 1.c) Payload – the JSON object that includes the content of the payload of the HTTP message. Each attribute or IE in the payload shall form a single entry in the Payload JSON object. If there is any attribute value that requires encryption, it shall be moved into the dataToIntegrityProtectAndCipher JSON object (clause 13.2.4.2), and the original value in this element shall be replaced by the index in the form {"encBlockIdx": <num>} where "num" is the index of the corresponding entry in the dataToIntegrityProtectAndCipher array. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4.3.1.1 |
4,106 | 6.4.1.4 Default EPS bearer context activation not accepted by the UE | If the default EPS bearer context activation is part of the attach procedure, the ESM sublayer shall notify the EMM sublayer of an ESM failure. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, the ESM sublayer shall additionally provide an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message to the EMM sublayer. If the default EPS bearer context activation is not part of the attach procedure, the UE shall send an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message and enter the state BEARER CONTEXT INACTIVE. The ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message contains an ESM cause that typically indicates one of the following cause values: #26: insufficient resources; #31: request rejected, unspecified; or #95 – 111: protocol errors. Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message, the MME shall enter the state BEARER CONTEXT INACTIVE and stop the timer T3485, if the timer is running. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.1.4 |
4,107 | P.3 Inter-system change between A/Gb mode and Iu mode | An MS is required to perform routing area updating for IMS voice termination if: 1) the upper layers have indicated that the MS is available for voice calls in the IMS (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], subclause 3.1); 2) the MS is enabled for mobility management for IMS voice termination; 3) the "IMS voice over PS session indicator" received for Iu mode has the value "IMS voice over PS session supported in Iu mode, but not supported in A/Gb mode"; and 4) the voice domain preference for UTRAN as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [134] is not "CS voice only". | 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 | P.3 |
4,108 | 4.4.2.4 Average number of active UEs | a) This measurement provides the average number of UEs that have DTCH data queued on the downlink, or have DTCH data queued on the uplink, or both. This measurement can’t be calculated from the Average number of active UEs on the DL per QCI and Average number of active UEs on the UL per QCI according to 2 out of 3 approach. For an eNodeB serving one or more RNs, the measurement refers to the number of active UEs conneted directly to the eNodeB, excluding RNs. The measurement is also applicable to RNs. b) SI c) This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. d) An integer value. e) The measurement name has the form DRB.UEActive f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffics 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.4.2.4 |
4,109 | V.2 Requirements | The UDM shall support the following services related to the user consent. - Retrieval of user consent parameters. - Notification of user consent parameters change. The user consent parameters shall be stored in the UDM/UDR as subscription data. The user consent parameters shall be bound to a SUPI/GPSI. The user consent parameters shall be bound to the purpose of data processing. The user consent parameters shall include whether the user consent is granted or not. The user consent shall be effective only after the point in time that user consent was given.The user consent shall be effective until revoked. It means that there is no expiry/validity timer for the user consent parameters stored in the subscription data. NOTE: UDM does not provide user consent revocation service, it only provides notifications of user consent parameter changes. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | V.2 |
4,110 | 4.2.2.2 Triggered Messages | The IP Destination Address of a GTPv2 Triggered message and for a Triggered Reply message shall be copied from the IP Source Address of the message to which this GTPv2 entity is replying, except in the case of the SGSN pool scenario. The IP Source Address of a GTPv2 Triggered message and for a Triggered Reply message shall be copied from the IP destination address of the message to which this GTPv2 entity is replying, except in the case of SGSN pool scenario and handover scenario when the CIoT feature is deployed. In the SGSN pool scenario, if the Identification Request, the Context Request or the Suspend Notification messages have been forwarded by another SGSN in the pool, the IP Source address for the Identification Response, the Context Response or the Suspend Acknowledge messages shall be locally allocated by the sending GTP entity. The IP Destination Address for the Identification Response, the Context Response or the Suspend Acknowlegde messages shall be determined in the following way. The value from the information element "Address for Control Plane", which was sent in the corresponding Identification Request or the Suspend Notification message; or the value from the information element "S3/S16/S10 Address and TEID for Control Plane", which was sent in the corresponding Context Request message, shall be copied into the IP Destination Address field. In the handover scenario when the CIoT feature is deployed, if the Forward Relocation Request message has been forwarded by the target MME, the IP Source address of the Forward Relocation Response shall be locally allocated by the sending GTP entity. The IP Destination Address field of the Forward Relocation Response shall be set to the value of the "Sender's F-TEID for Control Plane" IE received in the Forward Relocation Request message. | 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 | 4.2.2.2 |
4,111 | 4.2.4.2 In-session activity time for E-RABs | a) This measurement provides the aggregated active session time for E-RABs in a cell. The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) Number of s“in ession ”seconds aggregated for E-RABs with a certain QCI. , where “in session” has the following definitions: - E-RABs with bursty flow is said to be “in session” for a UE if any E-RAB data on any Data Radio Bearer (UL or DL) has been transferred during the last 100 ms for that QCI - E-RABs with continuous flow are always seen as being “in session” in the context of this measurement, and the session time is increased from the first data transmission on the E-RAB until 100 ms after the last data transmission on the E-RAB. The possible QCIs are described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per QCI measurements shall equal the total session seconds. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. How to decide for a particular QCI if the E-RAB is of type continuous flow is outside the scope of this document. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.SessionTimeQCI.QCI f) where QCI identifies the E-RAB level quality of service class. g) EUtranCellFDD EUtranCellTDD h) Valid for packet switched traffic i) EPS j) This measurement is to support the Retainability KPI “E-RAB Retainability” defined in [13]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.4.2 |
4,112 | 5.4.1.3.6 Authentication not accepted by the UE | In the 5G authentication challenge, the UE shall check the 5G authentication challenge data (RAND, AUTN and ngKSI) received in the AUTHENTICATION REQUEST message to verify authenticity of the 5G core network. The ME shall check that ngKSI received in the AUTHENTICATION REQUEST message is not already in use. The ME shall forward the RAND and AUTN to the USIM to check. The UE may reject the core network due to an incorrect AUTN or ngKSI parameter. If the UE has to reject the 5G authentication challenge, the UE shall return AUTHENTICATION FAILURE message to the network with a cause value indicating the reason for the failure (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). Incorrect 5G authentication challenge data contains four possible causes for authentication failure: a) MAC code failure: If the UE finds the MAC code (supplied by the core network in the AUTN parameter) to be invalid, the UE shall send an AUTHENTICATION FAILURE message to the network, with the 5GMM cause #20 "MAC failure". The UE shall then follow the procedure described in subclause 5.4.1.3.7, item c. b) Non-5G authentication unacceptable: If the UE finds that the "separation bit" in the AMF field of AUTN supplied by the core network is set to 0, the UE shall send an AUTHENTICATION FAILURE message to the network, with the 5GMM cause #26 "non-5G authentication unacceptable" (see subclause 6.1.3 in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). The UE shall then follow the procedure described in subclause 5.4.1.3.7, item d. c) ngKSI already in use: If the UE detects that ngKSI received in the AUTHENTICATION REQUEST message is already in use in the UE shall send an AUTHENTICATION FAILURE message to the network, with the 5GMM cause #71 "ngKSI already in use". The UE shall then follow the procedure described in subclause 5.4.1.3.7, item e. d) SQN failure: If the UE finds the sequence number SQN (supplied by the core network in the AUTN parameter) to be out of range, the UE shall send an AUTHENTICATION FAILURE message to the network, with the 5GMM cause #21 "synch failure" and a re-synchronization token AUTS provided by the USIM (see 3GPP TS 33.102[ 3G security; Security architecture ] [23]). The UE shall then follow the procedure described in subclause 5.4.1.3.7, item f. If the UE returns an AUTHENTICATION FAILURE message to the network, the UE shall delete any previously stored RAND and RES* and shall stop timer T3516, if running. If the UE has an emergency PDU session established or is establishing such a PDU session, additional UE requirements are specified in subclause 5.4.1.3.7, under "for items c, d, e and f". | 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.3.6 |
4,113 | 6.4.9.2 Security procedures not applied | As a serving network option, emergency calls, or PS connections for emergency sessions, may be established without the network having to apply the security mode procedure as defined in TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [35]. The following are the only cases where the "security procedure not applied" option may be used: a) Authentication is impossible because the (U)SIM is absent; b) Authentication is impossible because the serving network cannot obtain authentication vectors due to a network failure; c) Authentication is impossible because the (U)SIM is not permitted to receive non-emergency services from the serving network (e.g. there is no roaming agreement or the IMSI is barred); d) Authentication is possible but the serving network cannot successfully authenticate the (U)SIM. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.9.2 |
4,114 | 4.11 UE configuration parameter updates | The 5GS in a PLMN supports updating UE parameters via NAS signalling. The feature enables the HPLMN to securely and dynamically re-configure the UE configuration parameters stored on the USIM and the ME. - In this release of the specification, updates of the following USIM configuration parameters are supported: - routing indicator. - In this release of specification, updates of the following ME configuration parameters are supported: - default configured NSSAI. - disaster roaming information. The 5GS in an SNPN supports updating UE parameters via NAS signalling. The feature enables the SNPN to securely and dynamically re-configure the UE configuration parameter stored on the USIM if the UE used the USIM for registration to the SNPN. - In this release of the specification, updates of the following USIM configuration parameters are supported: - routing indicator. - In this release of specification, updates of the following ME configuration parameters are supported: - routing indicator. - default configured NSSAI. The update of UE configuration parameters is initiated by the network using the network-initiated downlink NAS transport procedure as described in subclause 5.4.5.3. The ME acknowledgement of successful reception of the updated UE configuration parameter information is sent back to the network using the UE-initiated uplink NAS transport procedure as described in subclause 5.4.5.2. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.11 |
4,115 | 10.12.1 EN-DC | The Activity Notification function is used to report user plane activity within SN resources. It can either report inactivity or resumption of activity after inactivity was reported. In EN-DC the Activity Reporting is provided from the SN only. The MN may take further actions. EN-DC Activity Notification Figure 10.12.1-1: Support of Activity Notification in EN-DC Support of Activity Notification in EN-DC is used to keep the MN informed about user traffic activity in resources owned by the SN. The MN may take appropriate action upon receiving such notification. 1. The SN informs the MN about user data inactivity of resources owned by the SN. 2. The MN decides to keep SN resources. 3. After a while the SN reports resumption of user plane activity. EN-DC with suspended RRC connection – SCG configuration released in SN The Activity Notification function may be used to enable EN-DC with suspended RRC connected operation. The MN node may decide, after inactivity is reported from the SN and also MN resources show no activity, to send the UE to suspended RRC connection. Resumption to RRC_CONNECTED may take place after activity is reported from the SN for SN terminated bearers. Figure 10.12.1-2: Support of Activity Notification in EN-DC with suspended RRC connection – SCG configuration released in SN Figure 10.12.1-2 shows how Activity Notification function interacts with E-UTRAN functions for suspended RRC connection and SgNB Modification procedures in order to keep the higher layer EN-DC E-UTRAN resources established for UEs in suspended RRC connection, including S1 and X2 interface C-plane, U-plane and bearer contexts established while lower layer MCG and SCG resources are released. E-UTRAN memorises the cell group configuration for MCG in order to apply delta signalling at resume, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [4]. After the UE has transited successfully back to RRC_CONNECTED, lower layer SCG resources are established afterwards by means of RRC Connection Reconfiguration. 1. The SN notifies the MN about user data inactivity for SN terminated bearers. 2. The MN decides to send the UE to suspended RRC connection. 3/4. The MN triggers the MN initiated SgNB Modification procedure, requesting the SN to release lower layers. 5. The UE is sent to suspended RRC connection. 6-8. After a period of suspended RRC connection, upon activity notification from the SN, the UE returns to RRC_CONNECTED. 8bis. MN decides whether to reactivate the SN terminated bearers. If (e.g. due to UE mobility), MN decides not to reactivate the SN terminated bearers, it initiates the MN initiated SN release procedure and the procedure ends. 9/10. The MN triggers the MN initiated SgNB Modification procedure to re-establish lower layers. The SN provides configuration data within an SN RRC configuration message. 11-14. The RRC Connection Reconfiguration procedure commences. EN-DC with suspended RRC connection - SCG configuration suspended in SN The Activity Notification function may be used to enable EN-DC with suspended RRC connection operation. The MN node may decide, after inactivity is reported from the SN and also MN resources show no activity, to send the UE to suspended RRC connection, while keeping the SCG configuration. Resumption to RRC_CONNECTED may take place after activity is reported from the SN for SN terminated bearers. Figure 10.12.1-3: Support of Activity Notification in EN-DC with suspended RRC connection - SCG configuration suspended in SN Figure 10.12.1-3 shows how Activity Notification function interacts with functions for suspended RRC connection and SgNB Modification procedures in order to keep the full EN-DC resources established for UEs in suspended RRC connection. When the UE transits successfully back to RRC_CONNECTED, lower layer MCG and SCG configurations are restored or reconfigured by means of RRC Connection Resume. 1. The SN notifies the MN about user data inactivity for SN terminated bearers. 2. The MN decides to send the UE to suspended RRC connection. 3/4. The MN triggers the MN initiated SN Modification procedure, requesting the SN to suspend lower layers. 5. The UE is sent to suspended RRC connection. 6-7. After a period of suspended RRC connection, the MN receives activity notification from the SN. 8. The MN decides whether to reactivate the SN terminated bearers. If (e.g. due to UE mobility), the MN decides not to reactivate the SN terminated bearers, it initiates the MN initiated SN release procedure, rather than the MN initiated SN modification procedure in steps 9/10. If the MN decides to return the UE to RRC_CONNECTED, the network triggered state transition from suspended RRC connection to RRC_CONNECTED commences. 9/10. The MN triggers the MN initiated SN Modification procedure to resume the SCG lower layers. If the SCG configuration needs to be updated, the SN provides the configuration data within an SN RRC configuration message. 11/12. The UE is instructed to resume both the MCG and the SCG. If the SCG configuration is to be updated, the new configuration is provided in the RRCConnectionResume message. 13. The MN informs the SN that the UE has completed the reconfiguration procedure successfully, via the SgNB Reconfiguration Complete message, including the SN RRC response message, if received from the UE. 14. The UE performs synchronisation towards the PSCell of the SN. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.12.1 |
4,116 | A.3.1.1 ASN.1 clauses | The RRC PDU contents are formally and completely described using abstract syntax notation (ASN.1), see X.680 [6], X.681 [7]. The complete ASN.1 code is divided into a number of ASN.1 clauses in the specifications. In order to facilitate the extraction of the complete ASN.1 code from the specification, each ASN.1 clause begins with the following: - a first text paragraph consisting entirely of an ASN.1 start tag, which consists of a double hyphen followed by a single space and the text string "ASN1START" (in all upper case letters); - a second text paragraph consisting entirely of a block start tag is included, which consists of a double hyphen followed by a single space and the text string "TAG-NAME-START" (in all upper case letters), where the "NAME" refers to the main name of the paragraph (in all upper-case letters). Similarly, each ASN.1 clause ends with the following: - a first text paragraph consisting entirely of a blockstop tag, which consists of a double hyphen followed by a single space and the text string "TAG-NAME-STOP" (in all upper-case letters), where the "NAME" refers to the main name of the paragraph (in all upper-case letters); - a second text paragraph consisting entirely of an ASN.1 stop tag, which consists of a double hyphen followed by a singlespace and the text "ASN1STOP" (in all upper case letters). This results in the following tags: -- ASN1START -- TAG-NAME-START -- TAG-NAME-STOP -- ASN1STOP The text paragraphs containing either of the start and stop tags should not contain any ASN.1 code significant for the complete description of the RRC PDU contents. The complete ASN.1 code may be extracted by copying all the text paragraphs between an ASN.1 start tag and the following ASN.1 stop tag in the order they appear, throughout the specification. NOTE: A typical procedure for extraction of the complete ASN.1 code consists of a first step where the entire RRC PDU contents description (ultimately the entire specification) is saved into a plain text (ASCII) file format, followed by a second step where the actual extraction takes place, based on the occurrence of the ASN.1 start and stop tags. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.1.1 |
4,117 | 5.2.5.6.3 Npcf_UEPolicyControl_UpdateNotify service operation | Service operation name: Npcf_UEPolicyControl_UpdateNotify Description: Provides to the NF Service Consumer updated Policy information for the UE context evaluated based on the information previously provided by the PCF. NOTE: This notification corresponds to an implicit subscription. Inputs, Required: Notification endpoint, UE Policy Association ID. Inputs, Optional: Policy Control Request Trigger of UE Policy Association. In the case of H-PCF is producer, UE Access and PDU session related information as defined in clause 5.2.5.1, indication of successful delivery of UE policies. NOTE: The indication of successful delivery of UE policies is used, e.g. as defined in clauses 4.12.2.2 and 4.12a.2.2. Outputs, Required: Success or failure. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.6.3 |
4,118 | 5.3.5.5.4 RLC bearer addition/modification | For each RLC-BearerConfig received in the rlc-BearerToAddModList IE the UE shall: 1> if the UE's current configuration contains an RLC bearer with the received logicalChannelIdentity/LogicalChannelIdentityExt within the same cell group: 2> if the RLC bearer is associated with an DAPS bearer, or 2> if any DAPS bearer is configured and the RLC bearer is associated with an SRB: 3> reconfigure the RLC entity or entities for the target cell group in accordance with the received rlc-Config; 3> reconfigure the logical channel for the target cell group in accordance with the received mac-LogicalChannelConfig; 2> else: 3> if reestablishRLC is received: 4> re-establish the RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4]; 3> reconfigure the RLC entity or entities in accordance with the received rlc-Config; 3> reconfigure the logical channel in accordance with the received mac-LogicalChannelConfig; 3> if servedMBS-RadioBearer is received: 4> associate this logical channel with the PDCP entity identified by servedMBS-RadioBearer; NOTE 1: For DRB and SRB, the network does not re-associate an already configured logical channel with another radio bearer. Hence, servedRadioBearer is not present in this case. For MRB, the network does not re-associate an already configured logical channel with DRB or SRB or another MRB (i.e. MRB with another PDCP entity). Hence multicastRLC-BearerConfig is not present in this case. If a radio bearer is released and another is added with the same radio bearer identity, it is considered as a new (different) radio bearer. Hence, the network also releases the RLC bearer(s) associated with the released radio bearer. NOTE 2: In DAPS handover, the UE may perform RLC entity re-establishment (if reestablishRLC is set) for an RLC bearer associated with a non-DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]. 1> else (a logical channel with the given logicalChannelIdentity/LogicalChannelIdentityExt is not configured within the same cell group, including the case when full configuration option is used): 2> if the servedRadioBearer associates the logical channel with an SRB and rlc-Config is not included: 3> establish an RLC entity in accordance with the default configuration defined in 9.2 for the corresponding SRB; 2> else: 3> establish an RLC entity in accordance with the received rlc-Config; 2> if the servedRadioBearer associates the logical channel with an SRB and if mac-LogicalChannelConfig is not included: 3> configure this MAC entity with a logical channel in accordance to the default configuration defined in 9.2 for the corresponding SRB; 2> else: 3> configure this MAC entity with a logical channel in accordance to the received mac-LogicalChannelConfig; 2> associate this logical channel with the PDCP entity identified by servedRadioBearer or servedMBS-RadioBearer. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.5.4 |
4,119 | 6.2.4.2a IPv6 prefix delegation via DHCPv6 | In order to perform the IPv6 prefix delegation via DHCPv6, the UE shall use DHCPv6 to request additional IPv6 prefixes (i.e. prefixes shorter than the default /64 prefix) from the SMF. The UE shall act as a "Requesting Router" as described in IETF RFC 8415 [33D] and shall insert one or more identity association for prefix delegation options into a DHCPv6 Solicit message. If the IPv6 address allocation using IPv6 stateless address autoconfiguration is used, the UE sends the DHCPv6 message to request additional IPv6 prefixes to the SMF after the PDU session establishment and IPv6 prefix allocation. When the UE requests additional prefixes using DHCPv6, the UE may include DHCPv6 Rapid Commit option as specified in IETF RFC 8415 [33D] in a DHCPv6 Solicit message, and the UE other than the ones specified in subclause 6.2.4.3 shall include DHCPv6 OPTION_ORO option with the OPTION_PD_EXCLUDE option code as specified in IETF RFC 6603 [40A] in the DHCPv6 message. Upon receiving one or more identity association for prefix delegation prefixes in a DHCPv6 Reply message, the UE is allowed to use the allocated additional prefixes after inter-system change from N1 mode to S1 mode or from S1 mode to N1 mode. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.4.2a |
4,120 | 6.1.3.2.2.3 Handling of network rejection due to SM cause other than SM cause #26 | If the SM cause value is different from #26 "insufficient resources" and #65 "maximum number of PDP contexts reached", and the Back-off timer value IE is included, the MS takes different actions depending on the timer value received in the Back-off timer value IE (if the MS is an MS configured to use AC11 – 15 in selected PLMN, exceptions are specified in subclause 6.1.3.13): i) if the timer value indicates neither zero nor deactivated, the MS shall start the back-off timer with the value provided in the Back-off timer value IE for the secondary PDP context activation procedure and PLMN and combination and not send another ACTIVATE SECONDARY PDP CONTEXT REQUEST message in the PLMN for the same until the back-off timer expires, the MS is switched off or the /USIM is removed; ii) if the timer value indicates that this timer is deactivated, the MS shall not send another ACTIVATE SECONDARY PDP CONTEXT REQUEST message in the PLMN for the same until the MS is switched off or the /USIM is removed; and iii) if the timer value indicates that this timer is zero, the MS may send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message in the PLMN for the same . If the Back-off timer value IE is not included, then the MS shall ignore the Re-attempt indicator IE provided by the network, if any. i) Additionally, if the SM cause value is #32 "service option not supported", or #33 "requested service option not subscribed", the MS shall proceed as follows: - if the MS is registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the MS shall behave as described above in the present subclause, using the configured SM_RetryWaitTime value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112], if available, as back-off timer value; and - otherwise, if the MS is not registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), or if the SM_RetryWaitTime value is not configured, the MS shall behave as described above in the present subclause using the default value of 12 minutes for the back-off timer. ii) For SM cause values different from #32 "service option not supported", or #33 "requested service option not subscribed", the MS behaviour regarding the start of a back-off timer is unspecified. The MS shall not stop any back-off timer upon a PLMN change or inter-system change. If the network indicates that a back-off timer for the secondary PDP context activation procedure and PLMN and APN combination is deactivated, then it remains deactivated upon a PLMN change or inter-system change. NOTE 1: This means the back-off timer can still be running or be deactivated for the given SM procedure and PLMN and APN combination when the MS returns to the PLMN or when it performs inter-system change back from S1 mode to A/Gb or Iu mode. Thus the MS can still be prevented from sending another ACTIVATE SECONDARY PDP CONTEXT REQUEST message in the PLMN for the same APN. If the back-off timer is started upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REJECT message (i.e. the timer value was provided by the network, a configured value is available or the default value is used as explained above) or the back-off timer is deactivated, the MS behaves as follows: i) after a PLMN change the MS may send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message for the same in the new PLMN, if the back-off timer is not running and is not deactivated for the secondary PDP context activation procedure and the combination of new PLMN and APN; Furthermore as an implementation option, for the SM cause values #32 "service option not supported" or #33 "requested service option not subscribed", if the network does not include a Re-attempt indicator IE, the MS may decide not to automatically send another ACTIVATE SECONDARY PDP CONTEXT REQUEST message for the same APN, if the MS registered to a new PLMN which is in the list of equivalent PLMNs. ii) if the network does not include the Re-attempt indicator IE to indicate whether re-attempt in S1 mode is allowed, or the MS ignores the Re-attempt indicator IE, e.g. because the Back-off timer value IE is not included, then: - if the MS is registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the MS shall apply the configured SM_RetryAtRATChange value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112], if available, to determine whether the MS may attempt a bearer resource allocation procedure for the same PLMN and APN combination in S1 mode; and - if the MS is not registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), or if the NAS configuration MO as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] is not available and the value for inter-system change is not configured in the USIM file NASCONFIG, then the MS behaviour regarding a bearer resource allocation procedure for the same PLMN and APN combination in S1 mode is unspecified; and iii) if the network includes the Re-attempt indicator IE indicating that re-attempt in an equivalent PLMN is not allowed, then depending on the timer value received in the Back-off timer value IE, for each combination of a PLMN from the equivalent PLMN list and the APN the MS shall start a back-off timer for the secondary PDP context activation procedure with the value provided by the network, or deactivate the respective back-off timer as follows: - If the Re-attempt indicator IE additionally indicates that re-attempt in S1 mode is allowed, the MS shall start or deactivate the back-off timer for A/Gb and Iu mode only; and - otherwise the MS shall start or deactivate the back-off timer for A/Gb, Iu, and S1 mode. If the back-off timer for a PLMN and APN combination was started or deactivated in S1 mode upon receipt of a BEARER RESOURCE ALLOCATION REJECT message (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]) and the network indicated that re-attempt in A/Gb or Iu mode is allowed, then this back-off timer does not prevent the MS from sending an ACTIVATE SECONDARY PDP CONTEXT REQUEST message in this PLMN for the same APN in A/Gb or Iu mode. If the network indicated that re-attempt in A/Gb or Iu mode is not allowed, the MS shall not send any ACTIVATE SECONDARY PDP CONTEXT REQUEST message in this PLMN for the same APN in A/Gb or Iu mode, until the timer expires, the MS is switched off or the USIM is removed. NOTE 2: The back-off timer is used to describe a logical model of the required MS behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp. NOTE 3: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the MS. Whether the MS uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to MS implementation. This back-off timer is stopped when the MS is switched off or the SIM/USIM is removed. If the SM cause value is #65 "maximum number of PDP contexts reached", the MS shall determine the PLMN's maximum number of PDP contexts in A/Gb or Iu mode (see subclause 6.1.3.0) as the number of active PDP contexts it has. The MS shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. NOTE 4: In some situations, when attempting to establish multiple PDP contexts, the number of active PDP contexts that the MS has when cause #65 is received is not equal to the maximum number of PDP contexts reached in the network. The PLMN's maximum number of PDP context in A/Gb or Iu mode applies to the PLMN in which the SM cause #65 "maximum number of PDP contexts reached" is received. When the MS is switched off or when the USIM is removed, the MS shall clear all previous determinations representing any PLMN's maximum number of PDP contexts in A/Gb or Iu mode (see subclause 6.1.3.0). Upon successful registration with a new PLMN, the MS may clear previous determinations representing any PLMN's maximum number of PDP contexts in A/Gb or Iu 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 | 6.1.3.2.2.3 |
4,121 | 6.3.6.4.2 Stand-alone N3IWF selection | If the UE is attached to 5GC via an N3IWF that is located in the same country as the country in which the UE is currently located and the AMF has previously indicated support for emergency services over non-3GPP access as defined in clause 5.16.4.1, the UE reuses the existing N3IWF connection for emergency services. Otherwise, the UE terminates any existing N3IWF connection and continues as follows: If the UE is equipped with a UICC: - The UE determines whether it is located in the home country or a visited country; - If the UE is located in the home country, then the UE selects the Home PLMN for emergency services and selects an N3IWF based on the procedure defined in clause 6.3.6.2. - If the UE is located in a visited country, the UE performs a DNS query using the Visited Country Emergency N3IWF FQDN, as specified in TS 23.003[ Numbering, addressing and identification ] [19] to determine which PLMNs in the visited country support emergency services in non-3GPP access via N3IWF; and: - If the DNS response contains one or more records, the UE selects a PLMN that supports emergency services in non-3GPP access via N3IWF. Each record in the DNS response shall contain the identity of a PLMN in the visited country supporting emergency services in non-3GPP access via N3IWF. - The UE shall consider these PLMNs based on their priorities in the Non-3GPP Access Node Selection Information (if available). If the UE cannot select a PLMN in the Non-3GPP Access Node Selection Information or if non-3GPP Access Node Selection Information is not available, the UE shall attempt to select any PLMN in the list of PLMNs returned in the DNS response. - Once the UE has selected a PLMN the UE shall select an N3IWF for the selected PLMN as follows: - If non-3GPP Access Node Selection Information is available for the selected PLMN the UE constructs the Tracking Area Identity based N3IWF FQDN or the Operator Identifier based N3IWF FQDN as indicated in the non-3GPP Access Node Selection Information for the selected PLMN. - If non-3GPP Access Node Selection Information is not available for the selected PLMN the UE constructs the Operator Identifier based N3IWF FQDN for the selected PLMN. - If the DNS response does not contain any record, or if the DNS response contains one or more records but the UE fails to select a PLMN that supports emergency services in non-3GPP access, or if the Emergency Registration procedure has failed for all PLMNs supporting emergency services in non-3GPP access, the UE notifies the user that an emergency session cannot be established. If the UE is not equipped with a UICC, the UE shall perform the emergency N3IWF selection procedure above as if always in a visited country and without using the Non-3GPP Access Node Selection Information, i.e. the UE may construct the Operator Identifier based N3IWF FQDN format based on a PLMN ID obtained via implementation specific means. When an N3IWF has been selected, the UE initiates an Emergency Registration. If the Emergency Registration fails, the UE shall select another PLMN supporting emergency services in non-3GPP access. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.6.4.2 |
4,122 | 5.32.4 QoS Support | The 5G QoS model for the Single-Access PDU Session is also applied to the MA PDU Session, i.e. the QoS Flow is the finest granularity of QoS differentiation in the MA PDU Session. One difference compared to the Single-Access PDU Session is that in a MA PDU Session there can be separate user-plane tunnels between the AN and the PSA, each one associated with a different access. However, the QoS Flow is not associated with specific access, i.e. it is access agnostic, so the same QoS is supported when the traffic is distributed over 3GPP and non-3GPP accesses. The SMF shall provide the same QFI in 3GPP and non-3GPP accesses so that the same QoS is supported in both accesses. A QoS Flow of the MA PDU Session may be either Non-GBR or GBR depending on its QoS profile. For a Non-GBR QoS Flow, the SMF provides a QoS profile to both 5G-ANs during MA PDU Session Establishment or MA PDU Session Modification procedure: - During MA PDU Session Establishment procedure, the QoS profile to both ANs if the UE is registered over both accesses. - During MA PDU Session Modification procedure, the QoS profile is provided to the 5G-AN(s) over which the user plane resources are activated. For a GBR QoS Flow, the SMF shall provide a QoS profile to 5G-AN(s) as follows: - If the PCC rule allows a GBR QoS Flow in a single access, the SMF provides the QoS profile for the GBR QoS Flow to the access network allowed by the PCC rule. - If the PCC rule allows a GBR QoS Flow in both accesses and the Steering Mode is different from Redundant, the SMF decides to which access network to provide the QoS profile for the GBR QoS Flow based on its local policy (e.g. the access where the traffic is ongoing according to the Multi Access Routing rule). - If the PCC rule allows a GBR QoS Flow in both accesses and the Steering Mode is Redundant, the SMF provides the QoS profile for the GBR QoS Flow to both access networks. Whenever the SMF recognizes that resources are not allocated in one access network, the SMF shall notify the PCF about the resource allocation failure and indicate the respective Access Type. Whenever the SMF recognizes that resources are not allocated in both access networks, the SMF shall release the resources for the GBR QoS Flow and report to the PCF about the removal of the PCC rule. NOTE 1: The SMF knows about the allocation of resources in an access network from the interaction with the access network during GBR QoS Flow establishment/modification as well as during the release of resources by the access network. For a GBR QoS Flow, traffic splitting is not supported. If the UPF determines that it cannot send GBR traffic over the current ongoing access e.g. based on the N4 rules and access availability and unavailability report from the UE as described in clause 5.32.5.3, the UPF shall send an Access Availability report to the SMF. Based on the Access Availability report and if the Steering Mode is different from Redundant, the SMF decides whether to move GBR QoS Flows to the other access when one access is not available: - if the PCC rule allows the GBR QoS Flows only on this access, the SMF shall release the resources for the GBR QoS Flow and report to the PCF about the removal of the PCC rule. - if the corresponding PCC rule allows the GBR QoS Flow on both accesses and the other access is not available, the SMF shall release the resources for the GBR QoS Flow and report to the PCF about the removal of the PCC rule. - if the PCC rule allows the GBR QoS Flow on both accesses and the other access is available, the SMF shall try to move the GBR QoS Flow to the other access. The SMF may trigger a PDU session modification procedure to provide the QoS profile to the other access and release the resources for the GBR QoS Flow in the current access. - if Notification Control parameter is not included in the PCC rule for the GBR QoS Flow and the other access does not accept the QoS profile, the SMF shall release the resources for the GBR QoS Flow and report to the PCF about the removal of the PCC rule. - if the Notification Control parameter is included in the PCC rule, the SMF shall notify the PCF that GFBR can no longer be guaranteed. After the other access accepts the QoS profile, the SMF shall notify the PCF that GFBR can again be guaranteed. If the other access does not accept the QoS profile, the SMF shall delete the GBR QoS Flow and report to the PCF about the removal of the PCC rule. NOTE 2: The ATSSS rule for GBR QoS Flow only allows the UE to steer traffic over a single access so that the network knows in which access the UE sends GBR traffic. If the network wants to move GBR QoS Flow to the other access, the network needs to update ATSSS rule of the UE. Based on the Access Availability report and if the Steering Mode is Redundant, the SMF behaves as follows: - if both accesses are not available, the SMF shall release the resources for the GBR QoS Flow and report to the PCF about the removal of the PCC rule. NOTE 3: The UPF can detect that both accesses are not available based on implementation specific means. - when one of the accesses becomes unavailable while the other access is still available, the SMF shall neither release the resources for the GBR QoS Flow nor notify the PCF that GFBR can no longer be guaranteed (if the Notification Control parameter is included in the PCC rule). NOTE 4: The access network will typically release the resources for a GBR QoS Flow if there is no traffic transferred for a certain amount of time and this will then trigger the SMF notification to PCF described above. When the MA PDU Session is established or when the MA PDU Session is modified, the SMF may provide QoS rule(s) to the UE via one access, which are applied by the UE as specified in clause 5.7.1.4. The QoS rule(s) provided by SMF via one access are commonly used for both 3GPP access and non-3GPP access, so the QoS classification is independent of ATSSS rules. The derived QoS rule generated by Reflective QoS is applied independently of the access on which the RQI was received. When the MPTCP functionality and/or the MPQUIC functionality is used in the UE, the UE shall use the IP address/prefix of the MA PDU Session and the final destination address to generate the derived QoS rule. When the MPTCP functionality and/or MPQUIC functionality is enabled for the MA PDU Session: - any QoS rules or PDRs that apply to the MA PDU Session IP address/prefix and port also apply (a) to the MPTCP "link-specific multipath" addresses/prefixes and ports used by the UE to establish MPTCP subflows over 3GPP and non-3GPP accesses , and (b) to the "MPQUIC link-specific multipath" addresses and ports used by the UE to transmit UDP flows over 3GPP and non-3GPP accesses; and - any QoS rules or PDRs that apply to the IP address/prefix and port of the final destination server in DN also apply (a) to the IP address and port of the MPTCP proxy for corresponding MPTCP subflows that are terminated at the proxy and (b) to the IP address and port of the MPQUIC proxy for corresponding UDP flows that are terminated at the proxy. NOTE 5: How these associations are made is left up to the UE and UPF implementations. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.4 |
4,123 | 16.12.2.2 L2 UE-to-UE Relay | The protocol stacks for the user plane and the control plane of the L2 U2U Relay architecture are illustrated in Figure 16.12.2.2-1 and Figure 16.12.2.2-2. The SRAP sublayer is placed above the RLC sublayer for both CP and UP at both PC5 interfaces. The sidelink SDAP, PDCP and RRC are terminated between two L2 U2U Remote UEs (i.e., end-to-end), while SRAP, RLC, MAC and PHY are terminated in each hop of PC5 link. Figure 16.12.2.2-1: User plane protocol stack for L2 UE-to-UE Relay Figure 16.12.2.2-2: Control plane protocol stack for L2 UE-to-UE Relay For L2 UE-to-UE Relay, the SRAP sublayer at L2 U2U Remote UE: - The SRAP sublayer at L2 U2U Remote UE performs bearer mapping between end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of the L2 U2U Remote UE and at each hop of PC5 Relay RLC Channel between the L2 U2U Remote UE and the L2 U2U Relay UE. - For the traffic transmitted from an L2 U2U Remote UE to an L2 U2U Relay UE, the different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) towards the same peer L2 U2U Remote UE and/or different peer L2 U2U Remote UEs can be multiplexed to the same PC5 Relay RLC channel, which is between the L2 U2U Remote UE(s) and the L2 U2U Relay UE. - For the traffic received at L2 U2U Remote UE, the same PC5 Relay RLC channel from one L2 U2U Relay UE can be de-multiplexed to the different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of the same peer L2 U2U Remote UE and/or different peer L2 U2U Remote UEs. - The SRAP sublayer at L2 U2U Remote UE supports identification of the peer L2 U2U Remote UE and itself. The local IDs are assigned by L2 U2U Relay UE to both L2 U2U Remote UEs for identification. For the two local IDs, one of them identifies L2 U2U Remote UE and the other identifies the peer L2 U2U Remote UE. The local ID of the peer L2 U2U Remote UE and the local ID of L2 U2U Remote UE are delivered by L2 U2U Relay UE to the L2 U2U Remote UEs along with the corresponding L2 ID of the peer L2 U2U Remote UE. The identity information of the end-to-end PC5 Radio Bearer and two local IDs are included in the SRAP header in order for the peer L2 U2U Remote UE to correlate the received packets for the specific PDCP entity associated with the right end-to-end PC5 Radio Bearer of the L2 U2U Remote UEs. For L2 UE-to-UE Relay, the SRAP sublayer at L2 U2U Relay UE: - The SRAP sublayer at L2 U2U Relay UE determines the egress PC5 Relay RLC Channel based on the mapping of the end-to-end PC5 Radio Bearer and egress PC5 Relay RLC Channel for a particular pair between the L2 U2U Remote UE and the peer L2 U2U Remote UE. - For the ingress traffic received from an/multiple L2 U2U Remote UE(s) at L2 U2U Relay UE, the different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of the same L2 U2U Remote UE and/or the same/different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of L2 U2U Remote UEs can be multiplexed to the same egress PC5 Relay RLC channel, which is in between the L2 U2U Relay UE and the peer L2 U2U Remote UE. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.2.2 |
4,124 | 5.31.3 Selection, steering and redirection between EPS and 5GS | The UE selects the core network type (EPC or 5GC) based on the broadcast indications for both EPC and 5GC, and the UE's EPC and 5GC Preferred Network Behaviour. Networks that support NB-IoT shall broadcast an indication whether N3 data transfer is supported or not in system information. When the UE performs the registration procedure it includes its Preferred Network Behaviour (for 5G and EPC) in the Registration Request message and the AMF replies with the 5G Supported Network Behaviour in the Registration Accept message. If the UE supports any of the CIoT 5GS Optimisations included in 5GC Preferred Network Behaviour, then when the UE performs an Attach or TAU procedure and the UE includes its EPC Preferred Network Behaviour then the UE shall also include its 5GC Preferred Network Behaviour. In networks that support CIoT features in both EPC and 5GC, the operator may steer UEs from a specific CN type due to operator policy, e.g. due to roaming agreements, Preferred and Supported Network Behaviour, load redistribution, etc. Operator policies in EPC and 5GC are assumed to avoid steering UEs back and forth between EPC and 5GC. To redirect a UE from 5GC to EPC, when the UE sends a Registration Request or Service Request, the AMF sends a Registration Reject or Service Reject with an EMM cause value indicating that the UE should not use 5GC. The UE disables N1 mode and re-enables S1 mode, if it was disabled. The UE then performs either an Attach or TAU in EPC as described in clause 5.17.2. To redirect a UE from EPC to 5GC, when the UE requests an Attach or TAU procedure or Service Reject, the MME sends a reject message with an EMM cause indicating the UE should not use EPC. The UE disables S1 mode and re-enables N1 mode, if it was disabled. The UE then registers with 5GC as described in clause 5.17.2. When determining whether to redirect the UE, the AMF/MME takes into account the UE support of S1/N1 mode, respectively, and the UE's Preferred Network Behaviour and the Supported Network Behaviour of the network the UE is being redirected towards. When determining to redirect the UE in 5GMM-CONNECTED mode to EPC, the AMF shall initiate the UE Configuration Update procedure to indicate registration requested and release of the N1 NAS signalling connection not requested, then the AMF redirects the UE to EPC by rejecting the subsequent Registration Request, see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. If after redirection the UE cannot find a cell supporting connectivity, the UE may re-enable the disabled N1/S1 mode and then perform Registration, Attach or TAU. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.3 |
4,125 | D.6.8 VPS URSP configuration | The purpose of the VPS URSP configuration information element is to transfer the VPS URSP configuration from the PCF to the UE. The VPS URSP configuration contains zero or more tuples. Each tuple contains the tuple ID identifying the tuple, the network descriptor identifying one or more VPLMNs, and zero or more UPSCs of HPLMN's UE policy sections which contain solely one or more UE policy parts with the UE policy part type set to "URSP", such that the URSP rules in those one or more UE policy parts are applicable to the VPLMN and its equivalent PLMN. The VPS URSP configuration information element is coded as shown in figure D.6.8.1, figure D.6.8.2, figure D.6.8.3, figure D.6.8.4, figure D.6.8.5, figure D.6.8.6, figure D.6.8.7, figure D.6.8.8, figure D.6.8.9, and table D.6.8.1. The VPS URSP configuration is type 6 information element with a minimum length of 3 octets and a maximum length of 65533 octets. Figure D.6.8.1: VPS URSP configuration information element Figure D.6.8.2: Tuple Figure D.6.8.3: Network descriptor Figure D.6.8.4: Network descriptor entry Figure D.6.8.5: Network descriptor entry value for network descriptor entry type set to "one or more VPLMNs" Figure D.6.8.6: PLMN ID Figure D.6.8.7: Network descriptor entry value for network descriptor entry type set to "one or more MCCs" Figure D.6.8.8: MCC pair Figure D.6.8.9: Odd MCC Table D.6.8.1: VPS URSP configuration information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | D.6.8 |
4,126 | 11.2.1 Access to Internet, Intranet or ISP through Packet Domain | The access to Internet, Intranet or ISP may involve specific functions such as user authentication, user’s authorization, end to end encryption between MS and Intranet/ISP, allocation of a dynamic address belonging to the PLMN/Intranet/ISP addressing space, IPv6 address autoconfiguration, etc. For this purpose the Packet Domain may offer: - either direct transparent access to the Internet; or - a non transparent access to the Intranet/ISP. In this case the Packet Domain, i.e. the GGSN/P-GW, takes part in the functions listed above. The mechanisms for host configuration and user authentication described in this subclause and its subclauses are applicable for the initial IP-CAN session establishment to allocate IP addresses (IPv4 and/or IPv6) to the MS. For GTP based access, the activation of any subsequent IP-CAN bearers for that IP-CAN session, (i.e.secondary PDP context activation Procedure’, dedicated bearer activation), as well as the use of TFTs, is described in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3], 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77]. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.2.1 |
4,127 | 13.3.3 Authentication and authorization between SEPP and network functions | NOTE 1: This clause also describes authentication and authorization between SEPP and NRF, because the NRF is a network function. Authentication between SEPP and network functions within one PLMN shall use one of the following methods: - If the PLMN uses protection at the transport layer, authentication provided by the transport layer protection solution shall be used for authentication between SEPP and NFs. - If the PLMN does not use protection at the transport layer, authentication between SEPP and NFs within one PLMN may be implicit by NDS/IP or physical security (see clause 13.1). A network function and the SEPP shall mutually authenticate before the SEPP forwards messages sent by the network function to network functions in other PLMN, and before the SEPP forwards messages sent by other network functions in other PLMN to the network function. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.3 |
4,128 | D.4.2.0 Overview | In order to avoid region- or even nation-wide power outages, wide-area power system protection is on the rise. "When a major power system disturbance occurs, protection and control actions are required to stop the power system degradation, restore the system to a normal state, and minimize the impact of the disturbance. The present control actions are not designed for a fast-developing disturbance and can be too slow. Local protection systems are not able to consider the overall system, which can be affected by the disturbance. Wide area disturbance protection is a concept of using system-wide information and sending selected local information to a remote location to counteract propagation of the major disturbances in the power system." [15]. Protection actions include, "among others, changes in demand (e.g. load shedding), changes in generation or system configuration to maintain system stability or integrity and specific actions to maintain or restore acceptable voltage levels." [16]. One specific application is phasor measurement for the stabilisation of the alternating-current phase in a transport network. For this, the voltage phase is measured locally and sent to a remote-control centre. There, this information is processed, and automated actions are triggered. One action can be the submission of telegrams to power plants, instructing them to either accelerate or deaccelerate their power generators in order to keep the voltage phase in the transport network stable. A comprehensive overview of this topic can be found elsewhere in the literature [17]. This kind of automation requires very low end-to-end latencies (5 ms) [16] and―due to its critical importance for the operation of society―a very high communication service availability (99,9999%). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | D.4.2.0 |
4,129 | 6.1.3.4.3 Abnormal cases | The following abnormal cases can be identified: a) Expiry of timers In the mobile station: On the first expiry of timer T3390, the MS shall resent the message DEACTIVATE PDP CONTEXT REQUEST and shall reset and restart the timer T3390. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3390, the MS shall release all resources allocated and shall erase the PDP context related data. On the network side: On the first expiry of timer T3395, the network shall resent the message DEACTIVATE PDP CONTEXT REQUEST and shall reset and restart timer T3395. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3395, the network shall erase the PDP context related data for that MS. b) Collision of MS and network initiated PDP context deactivation requests If the MS and the network initiated PDP context deactivation requests collide, the MS and the network shall each reply with the messages DEACTIVATE PDP CONTEXT ACCEPT and shall stop timer T3390 and T3395, respectively. c) Network initiated PDP context deactivation request without tear down indicator information element for a default PDP context If an MS supporting S1 mode receives a DEACTIVATE PDP CONTEXT REQUEST message without tear down indicator information element, and the PDP context associated with the specific TI is a default PDP context, the MS shall deactivate the default PDP context as specified in subclause 6.1.3.4.2. Additionally the MS shall deactivate all other active PDP contexts sharing the same PDP address and APN as the default PDP context locally without peer-to-peer signalling. An MS not supporting S1 mode may apply the same behaviour. Figure 6.8/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MS initiated PDP context deactivation procedure Figure 6.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network initiated PDP context deactivation procedure | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.4.3 |
4,130 | 6.10.4.2 Mapping to resource elements | If PRS frequency hopping is not configured by higher layers, the reference signal sequence shall be mapped to complex-valued modulation symbols used as reference signal for antenna port in slot according to where Normal cyclic prefix: Extended cyclic prefix: The bandwidth for positioning reference signals is configured by higher layers and the cell-specific frequency shift is given by where if no value for is configured by higher layers. If PRS frequency hopping is configured by higher layers, a PRS frequency hopping configuration provided by higher layers contains the following: - The length of the PRS occasion group, - Number of PRS frequency hopping bands, - defined as twice the starting PRB index of PRS frequency hopping band where - if , - where is the index of the first PRB in the PRS frequency hopping narrowband configured by higher layers if If PRS frequency hopping is configured by higher layers, the reference signal sequence in the PRS occasion , , in the PRS occasion group shall be mapped to complex-valued modulation symbols used as reference signal for antenna port in slot according to where - for normal cyclic prefix - for extended cyclic prefix Figure 6.10.4.2-1: Mapping of positioning reference signals (normal cyclic prefix) Figure 6.10.4.2-2: Mapping of positioning 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.4.2 |
4,131 | 9.2.3.1 FDD | The following requirements apply to UE Category ≥2. For the parameters specified in table 9.2.3.1-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.3.1-1: PUCCH 1-1 static test (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.2.3.1 |
4,132 | 9.11.2.14 Service-level-AA response | The purpose of the Service-level-AA response information element is to provide information regarding the service level authentication and authorization request, e.g. to indicate that the authentication and authorization request to the service level authentication server was successful, or to notify that service level authorization is revoked. The Service-level-AA response information element is coded as shown in figure 9.11.2.14.1 and table 9.11.2.14.1. The Service-level-AA response information element is a type 4 information element with length of 3 octets. Figure 9.11.2.14.1: Service-level-AA response information element Table 9.11.2.14.1: Service-level-AA response 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.14 |
4,133 | 9.11.4.30 Requested MBS container | The purpose of the Requested MBS container information element is for UE to request to join or leave one or more multicast MBS sessions. The Requested MBS container information element is coded as shown in figure 9.11.4.30.1, figure 9.11.4.30.2, figure 9.11.4.30.3, figure 9.11.4.30.4 and table 9.11.4.30.1. The Requested MBS container is a type 6 information element with a minimum length of 8 octets and a maximum length of 65538 octets. Figure 9.11.4.30.1: Requested MBS container information element Figure 9.11.4.30.2: multicast MBS session information Figure 9.11.4.30.3: multicast MBS session ID for Type of multicast MBS session ID = "Temporary Mobile Group Identity (TMGI)" Figure 9.11.4.30.4: multicast MBS session ID for Type of multicast MBS session ID = "Source specific IP multicast address for IPv4" or "Source specific IP multicast address for IPv6" Table 9.11.4.30.1: Requested MBS 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.4.30 |
4,134 | – SL-AccessInfo-L2U2N | The IE SL-AccessInfo-L2U2N includes the radio information included in Discovery Message used for L2 U2N relay operation. SL-AccessInfo-L2U2N information elements -- ASN1START -- TAG-SL-ACCESSINFO-L2U2N-START NR-Sidelink-DiscoveryMessage DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS CellAccessRelatedInfo, SL-ServingCellInfo-r17 FROM NR-RRC-Definitions; SL-AccessInfo-L2U2N-r17 ::= SEQUENCE { cellAccessRelatedInfo-r17 CellAccessRelatedInfo, sl-ServingCellInfo-r17 SL-ServingCellInfo-r17, ... } END -- TAG-SL-ACCESSINFO-L2U2N-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,135 | 4.2.5.1.7 Substate, ATTEMPTING-TO-UPDATE-MM | The MS shall: - perform cell selection/reselection according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]; - receive and transmit user data and signalling information; - initiate routing area update indicating "combined RA/LA updating with IMSI attach" on the expiry of timers T3311 or T3302; - initiate routing area update indicating "combined RA/LA updating with IMSI attach" when the routing area of the serving cell has changed and the location area this cell is belonging to is not in the list of forbidden LAs. GPRS MSs in operation modes C or A shall answer to paging requests. GPRS MS in operation mode B may answer to paging requests. | 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.5.1.7 |
4,136 | 4.7.2.11 Interaction between power saving mode and extended idle mode DRX cycle | The MS can request the use of both PSM and eDRX during an attach or routing area update procedure but it is up to the network to decide to enable none, one of them or both (see 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [133A] and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). If the network accepts the use of both PSM (see subclause 4.7.2.9) and eDRX (see subclause 4.7.2.10), the extended DRX parameters IE provided to the MS should allow for multiple paging occasions before the active timer expires. | 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.11 |
4,137 | 6.3.7 PCF discovery and selection 6.3.7.0 General principles | Clause 6.3.7.0 describes the underlying principles for PCF selection and discovery: - There may be multiple and separately addressable PCFs in a PLMN. - The PCF must be able to correlate the AF service session established over N5 or Rx with the associated PDU Session (Session binding) handled over N7. - It shall be possible to deploy a network so that the PCF may serve only specific DN(s). For example, Policy Control may be enabled on a per DNN basis. - Unique identification of a PDU Session in the PCF shall be possible based on the (UE ID, DNN)-tuple, the (UE (IP or MAC) Address(es), DNN)-tuple and the (UE ID, UE (IP or MAC) Address(es), DNN). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.7 |
4,138 | 16.15.4.2.1 Assistance Information | In order to enhance the scheduling of uplink resources for XR, the following improvements are introduced: - One additional buffer size table to reduce the quantisation errors in BSR reporting (e.g. for high bit rates): - Whether, for an LCG, the new table can be used in addition to the regular one is configured by the gNB; - When the new table is configured for an LCG, it is used whenever the amount of the buffered data of that LCG is within the range of the new table, otherwise the regular table is used. - Delay Status Report (DSR) of buffered data via a dedicated MAC CE: - Triggered for an LCG when the remaining time before discard of any buffered PDCP SDU goes below a configured threshold (threshold configured per LCG by the gNB); - When triggered for an LCG, reports the amount of data buffered with a remaining time before discard below the configured threshold, together with the shortest remaining time of any PDCP SDU buffered. - Reporting of uplink assistance information (jitter range, burst arrival time, UL data burst periodicity) per QoS flow by the UE via UE Assistance Information. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.15.4.2.1 |
4,139 | 5.7A.2 Usage Data Reporting for Secondary RAT | When a Secondary RAT can be used in conjunction with E-UTRAN, the HPLMN or VPLMN operator may wish to record the data volume sent on the Secondary RAT. In order to reduce the complexity of this procedure, and to align with existing per EPS bearer accounting procedures, the following principles are used in this release: a) The PLMN locally activates the Secondary RAT Usage Data Reporting by E-UTRAN O&M. The activation can happen separately for Data Volume Reporting of NR and Unlicensed Spectrum. If the PLMN uses this feature, it should ensure that this functionality is supported by all eNodeBs that support NR, Unlicensed Spectrum aggregation (if used to record data volume sent over unlicensed spectrum) as a Secondary RAT. b) The E-UTRAN reports uplink and downlink data volumes to the EPC for the Secondary RAT on a per EPS bearer basis and per time interval. NOTE 1: Secondary RAT includes access type NR and usage data reporting for Secondary RAT includes reporting of the combination of NR usage as defined in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [85]. c) At X2 handover and S1 handover, the source eNodeB reports the data volumes to the EPC. The reported data volume excludes data forwarded to the target RAN node. d) At S1 Release, Connection Suspend, and EPS Bearer Deactivation the eNodeB reports the data volumes to the EPC. e) To assist "partial CDR" generation at the Serving GW and the PDN GW, E-UTRAN O&M can instruct the E-UTRAN to also make periodic reports if no event has triggered a report before the period expires. NOTE 2: The timing of these periodic E-UTRAN reports is not expected to align with the timing of partial CDR generation. Hence the frequency of E-UTRAN 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. f) As an option, the Serving Gateway sends the data volume reports on to PDN GWs identified in bilateral roaming agreements. | 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.7A.2 |
4,140 | 4.3.5.1 Change of SSC mode 2 PDU Session Anchor with different PDU Sessions | The following procedure is triggered by SMF in order to change the PDU Session Anchor serving a PDU Session of SSC mode 2 for a UE when neither multi-homing nor UL CL applies to the PDU Session. This procedure releases the existing PDU Session associated with an old PDU Session Anchor (i.e. UPF1 in figure 4.3.5.1-1) and immediately establishes a new PDU Session with a new PDU Session Anchor (i.e. UPF2 in figure 4.3.5.1-1) to the same DN. Figure 4.3.5.1-1: Change of SSC mode 2 PSA for a PDU Session 1. The SMF determines that the serving UPF needs to be changed due to events that may benefit from such change. 1a. If the UPF (PSA) cannot connect to the target DNAI that SMF received from SM-PCF, the SMF invokes Nsmf_PDUSession_SMContextStatusNotify Request (target DNAI information) service operation to the AMF. The SMF also indicates the SMF selection is expected. The target DNAI information is used for SMF selection which can control UPF connecting to that DNAI at next PDU session establishment towards the same DNN and S-NSSAI. Due to it is for SMF selection, the AMF stores the target DNAI information received from SMF. The target DNAI information is not transferred outside, e.g. to support the UE context transfer between AMFs for AMF relocation. 2. The PDU Session Release procedure is initiated as described in clause 4.3.4. The SMF sends an N1 SM Information to the UE via the AMF by invoking Namf_Communication_N1N2MessageTransfer as described in Step 3b of clause 4.3.4.2. The PDU Session Release Command message in N1 SM Information contains the PDU Session ID and Cause indicating that a PDU Session re-establishment to the same DN is required. 3. Upon reception of PDU Session Release Command with Cause indicating that a PDU Session re-establishment to the same DN is required as sent in step 2, the UE generates a new PDU Session ID and initiates PDU Session Establishment procedure as described in clause 4.3.2.2. Then, the AMF selects an SMF as described in clause 6.4.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the SMF can select a new UPF (i.e. UPF2) for the re-established PDU Session of SSC mode 2. If the AMF has received target DNAI information from old SMF (i.e. SMF1), for the PDU Session toward same DNN and S-NSSAI the AMF selects the SMF using the stored target DNAI information. The AMF includes the target DNAI in the Nsmf_PDUSession_CreateSMContext Request and deletes the stored target DNAI information. The SMF selects the new PDU Session Anchor using the target DNAI. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.5.1 |
4,141 | 6.3.4B ON/OFF time mask for UL-MIMO | For UE supporting UL-MIMO, the ON/OFF time mask requirements in subclause 6.3.4 apply at each transmit antenna connector. For UE with two transmit antenna connectors in closed-loop spatial multiplexing scheme, the general ON/OFF time mask requirements specified in subclause 6.3.4.1 apply to each transmit antenna connector. The requirements shall be met with the UL-MIMO configurations specified in Table 6.2.2B-2. If UE is configured for transmission on single-antenna port, the requirements in subclause 6.3.4 apply. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.4B |
4,142 | 4.7.5 Routing area updating procedure | This procedure is used for: - normal routing area updating to update the registration of the actual routing area of an MS in the network. This procedure is used by GPRS MSs in MS operation mode C and by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS and non-GPRS services if the network operates in network operation mode II; - combined routing area updating to update the registration of the actual routing and location area of an MS in the network. This procedure is used by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS and non-GPRS services provided that the network operates in network operation mode I; - periodic routing area updating. This procedure is used by GPRS MSs in MS operation mode C and by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS or for GPRS and non-GPRS services independent of the network operation mode; - IMSI attach for non-GPRS services when the MS is IMSI attached for GPRS services. This procedure is used by GPRS MSs in MS operation modes A or B, if the network operates in network operation mode I; - in A/Gb mode, resuming GPRS services when the RR sublayer indicated a resumption failure after dedicated mode was left, see 3GPP TS 44.018[ None ] [84]; - in A/Gb mode, updating the network with the new MS Radio Access Capability IE when the content of the IE has changed; - updating the network with the new DRX parameter IE when the content of the IE has changed; NOTE 1: Such changes can be used e.g. when the MS activates a PDP context with service requirements that cannot be met with the current DRX parameter. As PDP context(s) are activated and deactivated, the GMM context will be updated with an appropriate DRX parameter; - re-negotiation of the READY timer value; - Iu mode to A/Gb mode and for A/Gb mode to Iu mode intersystem change, see subclause 4.7.1.7; - in Iu mode, re-synchronizing the PMM mode of MS and network after RRC connection release with cause "Directed signalling connection re-establishment", see subclause 4.7.2.5; - in Iu mode and A/Gb mode after intersystem change from S1 mode, and the GMM receives an indication of "RRC connection failure" from lower layers due to lower layer failure while in S1 mode; - S1 mode to Iu mode or S1 mode to A/Gb mode intersystem change and ISR is not activated; - S1 mode to Iu mode or S1 mode to A/Gb mode intersystem change and ISR is activated, but the MS changes to a routeing area it has not previously registered with the network; - indicating to the network that due to a manual CSG selection the MS has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the MS's Allowed CSG list or in the MS's Operator CSG list; - indicating to the network that the mobile station classmark 2, mobile station classmark 3 or the supported codecs have changed for a MS supporting SRVCC; or - indicating the current radio access technology to the network for the support of terminating access domain selection for voice calls or voice sessions (for details see subclause 4.7.5.1 and subclause 4.7.5.2.1). While an MS has a PDN connection for emergency bearer services, the MS shall not perform manual CSG selection. The routing area updating procedure shall also be used by a MS which is attached for GPRS services if a new PLMN is entered (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]), unless the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112] and the new PLMN is neither the registered PLMN nor in the list of equivalent PLMNs. An eCall only mobile station that is not capable of eCall over IMS shall not perform a normal or combined routing area updating procedure. Subclause 4.7.5.1 describes the routing area updating procedures for updating the routing area only. The combined routing area updating procedure used to update both the routing and location area is described in subclause 4.7.5.2. The routing area updating procedure is always initiated by the MS. It is only invoked in state GMM-REGISTERED. To limit the number of consecutive rejected routing area update attempts, a routing area updating attempt counter is introduced. The routing area updating attempt counter shall be incremented as specified in subclause 4.7.5.1.5. Depending on the value of the routing area updating attempt counter, specific actions shall be performed. The routing area updating attempt counter shall be reset when: - a GPRS attach or combined GPRS attach procedure is successfully completed; - a normal or periodic routing area updating or combined routing area updating procedure is successfully completed; - a combined GPRS attach procedure or a combined routing area updating procedure is completed for GPRS services only with cause #2 or #28; - a normal or periodic routing area updating or combined routing updating procedure is rejected with cause #11, #12, #13, #14, #15 or #25; - a new PLMN is selected. and additionally when the MS is in substate ATTEMPTING-TO-UPDATE: - a new routing area is entered; - expiry of timer T3302; - at request from registration function; or - timer T3346 is started. The mobile equipment shall contain a list of "forbidden location areas for roaming", as well as a list of "forbidden location areas for regional provision of service". The handling of these lists is described in subclause 4.4.1. In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. The MS shall construct the Routing Area Identification of the cell from this chosen PLMN identity, and the LAC and the RAC received on the BCCH. If the constructed RAI is different from the stored RAI, the MS shall initiate the routing area updating procedure. For: - a shared GERAN, in A/Gb mode, the chosen PLMN identity is indicated to the GERAN in the first RLC data block of an upper layer PDU (see 3GPP TS 44.060[ None ] [76]) when a foreign TLLI is used by the network sharing supporting MS for the transmission. - a shared UTRAN, the chosen PLMN identity shall be indicated to the UTRAN in the RRC INITIAL DIRECT TRANSFER message (see 3GPP TS 25.331[ None ] [23c]). For GERAN Iu mode, network sharing is not supported. Whenever a ROUTING AREA UPDATE REJECT message with the cause "PLMN not allowed" is received by the MS, the chosen PLMN identity shall be stored in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. Whenever a ROUTING AREA UPDATE REJECT message is received by the MS with the cause "Roaming not allowed in this location area", "Location Area not allowed", or "No suitable cells in Location Area", the LAI that is part of the constructed RAI which triggered the routing area updating procedure shall be stored in the suitable list. In A/Gb mode, user data transmission in the MS shall be suspended during the routing area updating procedure, except if the routing area updating procedure is triggered by a PS handover procedure as described in 3GPP TS 43.129[ None ] [113]; user data reception shall be possible. User data transmission in the network may be suspended during the routing area updating procedure. In Iu mode, user data transmission and reception in the MS shall not be suspended during the routing area updating procedure. User data transmission in the network shall not be suspended during the routing area updating procedure. In Iu mode, when a ROUTING AREA UPDATE REQUEST is received by the SGSN over a new PS signalling connection while there is an ongoing PS signalling connection (network is already in mode PMM-CONNECTED) for this MS, the network shall progress the routing area updating procedure as normal and release the previous PS signalling connection when the routing area updating procedure has been accepted by the network. NOTE 2: The re-establishment of the radio bearers of active PDP contexts is done as described in subclause "Service Request procedure". The network informs the MS about the support of specific features, such as LCS-MOLR, MBMS, IMS voice over PS session, emergency bearer services in Iu mode in the Network feature support information element. The information is either explicitly given by sending the Network feature support IE or implicitly by not sending it. The handling in the network is described in subclause 9.4.15.11The network can also use the Additional network feature support IE in order to inform the MS about the support of specific features such as the delivery of SMS via GPRS (GPRS-SMS) or implicitly by not sending it. The MS may use the support indications for LCS-MOLR, MBMS and GPRS-SMS to inform the user about the availability of the appropriate services. The MS shall not request the LCS-MOLR or MBMSservices, if the service has not been indicated as available. The indication for MBMS is defined in subclause "MBMS feature support indication" in 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [106]. In an MS with IMS voice over PS capability, the IMS voice over PS session indicator and the emergency bearer services indicator shall be provided to the upper layers. The upper layers take the IMS voice over PS session indicator into account as specified in 3GPP TS 23.221[ Architectural requirements ] [131], subclause 7.2a and subclause 7.2b, when selecting the access domain for voice sessions or calls in Iu mode. When initiating an emergency call in Iu mode, the upper layers also take the emergency bearer services indicator into account for the access domain selection. The MS may use the GPRS-SMS indication in order to obtain SMS. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.5 |
4,143 | 13.5 Security capability negotiation between SEPPs | The security capability negotiation over N32-c allows the SEPPs to negotiate which security mechanism to use for protecting NF service-related signalling over N32-f. There shall be an agreed security mechanism between a pair of SEPPs before conveying NF service-related signalling over N32-f. When a SEPP notices that it does not have an agreed security mechanism for N32-f protection with a peer SEPP or if the security capabilities of the SEPP have been updated, the SEPP shall perform security capability negotiation with the peer SEPP over N32-c in order to determine, which security mechanism to use for protecting NF service-related signalling over N32-f. Certificate based authentication shall follow the profiles given in 3GPP TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3], clause 6.2. A mutually authenticated TLS connection as defined in clause 13.1 shall be used for protecting security capability negotiation over N32-c. The TLS connection shall provide integrity, confidentiality and replay protection. Figure 13.5-1 Security capability negotiation 1. The SEPP which initiated the TLS connection shall issue a POST request to the exchange-capability resource of the responding SEPP including the initiating SEPP’s supported security mechanisms for protecting the NF service-related signalling over N32-f (see table Table 13.5-1). The security mechanisms shall be ordered in the initiating SEPP’s priority order. 2. The responding SEPP shall compare the received security capabilities to its own supported security capabilities and selects, based on its local policy (e.g. based on whether there are IPX providers on the path between the SEPPs), a security mechanism, which is supported by both initiating SEPP and responding SEPP. 3. The responding SEPP shall respond to the initiating SEPP with the selected security mechanism for protecting the NF service-related signalling over N32. Table 13.5-1: NF service-related signalling traffic protection mechanisms over N32 If the selected security mechanism is PRINS, the SEPPs shall behave as specified in clause 13.2. If the selected security mechanism is TLS, the SEPPs shall behave as specified in clause 13.1.2, tear down the N32-c connection and forward the NF service related signalling over N32-f using a TLS connection. If the selected security mechanism is a mechanism other than the ones specified in Table 13.5-1, the two SEPPs shall terminate the N32-c TLS connection. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.5 |
4,144 | 19.3.6 Emergency NAI for Limited Service State | This clause describes the format of the UE identification needed to access the 3GPP EPC from both 3GPP and non-3GPP accesses, when UE is performing an emergency attach and IMSI is not available or not authenticated (see clause 19.3.1). For more information, see clauses 4.6.1 and 5.2 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [68]. The Emergency NAI for Limited Service State 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 exact format shall be: imei<IMEI>@sos.invalid NOTE: The top level domain ".invalid" is a reserved top level domain, as specified in IETF RFC 2606 [64], and is used here due to the fact that this NAI never needs to be resolved for routing (as specified in 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [68]). or mac<MAC>@sos.invalid For example, if the IMEI is 219551288888888, the Emergency NAI for Limited Service State then takes the form of [email protected]. For example, if the MAC address is 44-45-53-54-00-AB, the Emergency NAI for Limited Service State then takes the form of [email protected], where the MAC address is represented in hexadecimal format without separators. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.3.6 |
4,145 | 4.6.2.9 Mobility management based network slice usage control | If the UE and the network support network slice usage control, the AMF monitors network slice usage by running a slice deregistration inactivity timer per S-NSSAI and access type. The AMF may also provide on-demand NSSAI to the UE in the REGISTRATION ACCEPT message or in the CONFIGURATION UPDATE COMMAND message. The on-demand NSSAI consists of one or more on-demand S-NSSAIs and, optionally, the slice deregistration inactivity timer per on-demand S-NSSAI. The slice deregistration inactivity timer is: a) started when there is no established PDU session, including any MA PDU session, associated with the S-NSSAI over the corresponding access type; and b) stopped and reset when at least a PDU session, including any MA PDU session, associated with the S-NSSAI is successfully established over the corresponding access type(s) or the S-NSSAI is removed from the allowed NSSAI. If the slice deregistration inactivity timer value is updated, the AMF updates the stored timer value and may provide the updated timer value to the UE in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message. When the UE receives an updated slice deregistration inactivity timer value in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message from the AMF, the UE updates the stored timer value. Upon expiry of the slice deregistration inactivity timer, the AMF locally removes the S-NSSAI from the allowed NSSAI over the access type. In addition, the AMF may send the CONFIGURATION UPDATE COMMAND message to the UEs with the new allowed NSSAI. The UE includes the on-demand S-NSSAI which the UE requests in the requested NSSAI during the registration procedure. Upon expiry of the slice deregistration inactivity timer, the UE locally removes the S-NSSAI from the allowed NSSAI over the access type. If the UE supports network slice usage control, the AMF provides on-demand NSSAI in the Configured NSSAI to the UE in the REGISTRATION ACCEPT message or in the UE Configuration Update Command message. The on-demand NSSAI consists of one or more configured S-NSSAIs. The on-demand S-NSSAI(s) is deleted by the UE from the stored on-demand NSSAI, when the associated configured S-NSSAI(s) is deleted by the UE from the stored configured NSSAI. NOTE: The network slice usage control feature is not supported in roaming scenarios. | 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.6.2.9 |
4,146 | – CG-Config | This message is used to transfer the SCG radio configuration as generated by the SgNB or SeNB. It can also be used by a CU to request a DU to perform certain actions, e.g. to request the DU to perform a new lower layer configuration. Direction: Secondary gNB or eNB to master gNB or eNB, alternatively CU to DU. CG-Config message -- ASN1START -- TAG-CG-CONFIG-START CG-Config ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ cg-Config CG-Config-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } CG-Config-IEs ::= SEQUENCE { scg-CellGroupConfig OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, scg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, configRestrictModReq ConfigRestrictModReqSCG OPTIONAL, drx-InfoSCG DRX-Info OPTIONAL, candidateCellInfoListSN OCTET STRING (CONTAINING MeasResultList2NR) OPTIONAL, measConfigSN MeasConfigSN OPTIONAL, selectedBandCombination BandCombinationInfoSN OPTIONAL, fr-InfoListSCG FR-InfoList OPTIONAL, candidateServingFreqListNR CandidateServingFreqListNR OPTIONAL, nonCriticalExtension CG-Config-v1540-IEs OPTIONAL } CG-Config-v1540-IEs ::= SEQUENCE { pSCellFrequency ARFCN-ValueNR OPTIONAL, reportCGI-RequestNR SEQUENCE { requestedCellInfo SEQUENCE { ssbFrequency ARFCN-ValueNR, cellForWhichToReportCGI PhysCellId } OPTIONAL } OPTIONAL, ph-InfoSCG PH-TypeListSCG OPTIONAL, nonCriticalExtension CG-Config-v1560-IEs OPTIONAL } CG-Config-v1560-IEs ::= SEQUENCE { pSCellFrequencyEUTRA ARFCN-ValueEUTRA OPTIONAL, scg-CellGroupConfigEUTRA OCTET STRING OPTIONAL, candidateCellInfoListSN-EUTRA OCTET STRING OPTIONAL, candidateServingFreqListEUTRA CandidateServingFreqListEUTRA OPTIONAL, needForGaps ENUMERATED {true} OPTIONAL, drx-ConfigSCG DRX-Config OPTIONAL, reportCGI-RequestEUTRA SEQUENCE { requestedCellInfoEUTRA SEQUENCE { eutraFrequency ARFCN-ValueEUTRA, cellForWhichToReportCGI-EUTRA EUTRA-PhysCellId } OPTIONAL } OPTIONAL, nonCriticalExtension CG-Config-v1590-IEs OPTIONAL } CG-Config-v1590-IEs ::= SEQUENCE { scellFrequenciesSN-NR SEQUENCE (SIZE (1.. maxNrofServingCells-1)) OF ARFCN-ValueNR OPTIONAL, scellFrequenciesSN-EUTRA SEQUENCE (SIZE (1.. maxNrofServingCells-1)) OF ARFCN-ValueEUTRA OPTIONAL, nonCriticalExtension CG-Config-v1610-IEs OPTIONAL } CG-Config-v1610-IEs ::= SEQUENCE { drx-InfoSCG2 DRX-Info2 OPTIONAL, nonCriticalExtension CG-Config-v1620-IEs OPTIONAL } CG-Config-v1620-IEs ::= SEQUENCE { ueAssistanceInformationSCG-r16 OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL, nonCriticalExtension CG-Config-v1630-IEs OPTIONAL } CG-Config-v1630-IEs ::= SEQUENCE { selectedToffset-r16 T-Offset-r16 OPTIONAL, nonCriticalExtension CG-Config-v1640-IEs OPTIONAL } CG-Config-v1640-IEs ::= SEQUENCE { servCellInfoListSCG-NR-r16 ServCellInfoListSCG-NR-r16 OPTIONAL, servCellInfoListSCG-EUTRA-r16 ServCellInfoListSCG-EUTRA-r16 OPTIONAL, nonCriticalExtension CG-Config-v1700-IEs OPTIONAL } CG-Config-v1700-IEs ::= SEQUENCE { candidateCellInfoListCPC-r17 CandidateCellInfoListCPC-r17 OPTIONAL, twoPHRModeSCG-r17 ENUMERATED {enabled} OPTIONAL, nonCriticalExtension CG-Config-v1730-IEs OPTIONAL } CG-Config-v1730-IEs ::= SEQUENCE { fr1-Carriers-SCG-r17 INTEGER (1..32) OPTIONAL, fr2-Carriers-SCG-r17 INTEGER (1..32) OPTIONAL, nonCriticalExtension CG-Config-v1800-IEs OPTIONAL } CG-Config-v1800-IEs ::= SEQUENCE { candidateServingFreqRangeListNR-r18 CandidateServingFreqRangeListNR-r18 OPTIONAL, candidateServingFreqListNR-r16 CandidateServingFreqListNR-r16 OPTIONAL, idc-TDM-AssistanceConfig-r18 ENUMERATED {enabled} OPTIONAL, candidateCellInfoListSubsequentCPC-r18 CandidateCellInfoListCPC-r17 OPTIONAL, scpac-ReferenceConfigurationSCG-r18 ReferenceConfiguration-r18 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } ServCellInfoListSCG-NR-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF ServCellInfoXCG-NR-r16 ServCellInfoXCG-NR-r16 ::= SEQUENCE { dl-FreqInfo-NR-r16 FrequencyConfig-NR-r16 OPTIONAL, ul-FreqInfo-NR-r16 FrequencyConfig-NR-r16 OPTIONAL, -- Cond FDD ... } FrequencyConfig-NR-r16 ::= SEQUENCE { freqBandIndicatorNR-r16 FreqBandIndicatorNR, carrierCenterFreq-NR-r16 ARFCN-ValueNR, carrierBandwidth-NR-r16 INTEGER (1..maxNrofPhysicalResourceBlocks), subcarrierSpacing-NR-r16 SubcarrierSpacing } ServCellInfoListSCG-EUTRA-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCellsEUTRA)) OF ServCellInfoXCG-EUTRA-r16 ServCellInfoXCG-EUTRA-r16 ::= SEQUENCE { dl-CarrierFreq-EUTRA-r16 ARFCN-ValueEUTRA OPTIONAL, ul-CarrierFreq-EUTRA-r16 ARFCN-ValueEUTRA OPTIONAL, -- Cond FDD transmissionBandwidth-EUTRA-r16 TransmissionBandwidth-EUTRA-r16 OPTIONAL, ... } TransmissionBandwidth-EUTRA-r16 ::= ENUMERATED {rb6, rb15, rb25, rb50, rb75, rb100} PH-TypeListSCG ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF PH-InfoSCG PH-InfoSCG ::= SEQUENCE { servCellIndex ServCellIndex, ph-Uplink PH-UplinkCarrierSCG, ph-SupplementaryUplink PH-UplinkCarrierSCG OPTIONAL, ..., [[ twoSRS-PUSCH-Repetition-r17 ENUMERATED{enabled} OPTIONAL ]] } PH-UplinkCarrierSCG ::= SEQUENCE{ ph-Type1or3 ENUMERATED {type1, type3}, ... } MeasConfigSN ::= SEQUENCE { measuredFrequenciesSN SEQUENCE (SIZE (1..maxMeasFreqsSN)) OF NR-FreqInfo OPTIONAL, ... } NR-FreqInfo ::= SEQUENCE { measuredFrequency ARFCN-ValueNR OPTIONAL, ... } ConfigRestrictModReqSCG ::= SEQUENCE { requestedBC-MRDC BandCombinationInfoSN OPTIONAL, requestedP-MaxFR1 P-Max OPTIONAL, ..., [[ requestedPDCCH-BlindDetectionSCG INTEGER (1..15) OPTIONAL, requestedP-MaxEUTRA P-Max OPTIONAL ]], [[ requestedP-MaxFR2-r16 P-Max OPTIONAL, requestedMaxInterFreqMeasIdSCG-r16 INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, requestedMaxIntraFreqMeasIdSCG-r16 INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, requestedToffset-r16 T-Offset-r16 OPTIONAL ]], [[ reservedResourceConfigNRDC-r17 ResourceConfigNRDC-r17 OPTIONAL ]] } BandCombinationIndex ::= INTEGER (1..maxBandComb) BandCombinationInfoSN ::= SEQUENCE { bandCombinationIndex BandCombinationIndex, requestedFeatureSets FeatureSetEntryIndex } FR-InfoList ::= SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF FR-Info FR-Info ::= SEQUENCE { servCellIndex ServCellIndex, fr-Type ENUMERATED {fr1, fr2} } CandidateServingFreqListNR ::= SEQUENCE (SIZE (1.. maxFreqIDC-MRDC)) OF ARFCN-ValueNR CandidateServingFreqListEUTRA ::= SEQUENCE (SIZE (1.. maxFreqIDC-MRDC)) OF ARFCN-ValueEUTRA T-Offset-r16 ::= ENUMERATED {ms0dot5, ms0dot75, ms1, ms1dot5, ms2, ms2dot5, ms3, spare1} CandidateCellInfoListCPC-r17 ::= SEQUENCE (SIZE (1..maxFreq)) OF CandidateCellInfo-r17 CandidateCellInfo-r17 ::= SEQUENCE { ssbFrequency-r17 ARFCN-ValueNR, candidateList-r17 SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF CandidateCell-r17 } CandidateCell-r17 ::= SEQUENCE { physCellId-r17 PhysCellId, condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL } -- TAG-CG-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,147 | 5.2.8.3.2A Nsmf_EventExposure_AppRelocationInfo service operation | Service operation name: Nsmf_EventExposure_AppRelocationInfo Description: Acknowledge the notification from the SMF regarding UE PDU Session related event(s). Input Required: Notification Correlation Information, cause code. The Notification Corrrelation Information is provided by the SMF in the event notification. Cause code indicates this acknowledgement is positive or negative. Input, Optional: Event specific parameter list as described in clause 5.2.8.3.1, Indication that buffering of uplink traffic should start, Information for EAS IP Replacement in 5GC. Output Required: None. Output, Optional: None. See clause 4.3.6.3 for details on usage of this service operation for example for the usage of the Indication that buffering of uplink traffic should start. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.3.2A |
4,148 | 12.2.4.2 Justifications for APN load control support | Following are the justifications to support the APN level load control in the network when the pre-condition specified in 12.2.3.1 is applicable: 1) To achieve load balancing at the APN level granularity: The PGW may be configured to handle more than one APN in the network. In such a case, the PGW may be additionally configured to allocate different resources for each of the configured APNs, e.g. the PGW may be configured to handle "X" number of sessions for the "consumer" APN and to handle "Y" number of session for the "corporate" APN. The ratio of this limit, i.e. "X" and "Y", to the PGW's capacity may not be the same across all the PGWs in the network. In this case, the load information with node level granularity is not sufficient and could result in a network where one PGW has more sessions for the "consumer" APN while another PGW has more sessions for the "corporate" APN. Thus, an evenly load balanced network at APN level load granularity cannot be realized. 2) To ensure effective overload control in the network: If the distribution of sessions at APN level is uneven, then there is a higher risk of overload of some PGWs, as compared to other PGWs, e.g. the PGW handling more sessions for "consumer" APN may have to handle more messages, (e.g. generated due to mobility events resulting from a change of ULI, RAT type, Serving GW, etc.) as compared to the PGW handling more sessions for the "stationary-machine" APN. Hence, the PGW handling "consumer" APN sessions may be at higher risk of overload, as compared to the other PGWs in the network, and hence, this situation may result in poor overload control of the network. 3) To ensure an efficient node selection algorithm: Based on the node level load information, the source node, (e.g. the MME) may end-up selecting the PGW for a new session for the given APN. However, the selected PGW may reject the new session request, if it is running at 100% load capacity for the given APN, or the new session request may be throttled by the source node based on the overload information of the APN for the given PGW. Thus the new session request may be denied, (i.e. rejected by the selected PGW or throttled by the source node based on PGW's APN level overload information) while the other PGW may have the capacity to handle the same. Thus, the lack of APN level load information may result in inefficient node selection algorithm by the source node. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.2.4.2 |
4,149 | O.4.4 IM Status | The purpose of the IM Status is to provide information about the IMS capability and registration state of a specific public user identity and it MS. NOTE: The definition of what is a public user identity can be found in 3GPP TS 23.003[ Numbering, addressing and identification ] [10]. The IM Status information element is coded as shown in figure O.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table O.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The IM Status is a type 1 information element with 1 octet length. Figure O.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] IM Status contents Table O.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : IM Status contents | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | O.4.4 |
4,150 | – RRCSetupRequest | The RRCSetupRequest message is used to request the establishment of an RRC connection. Signalling radio bearer: SRB0 RLC-SAP: TM Logical channel: CCCH Direction: UE to Network RRCSetupRequest message -- ASN1START -- TAG-RRCSETUPREQUEST-START RRCSetupRequest ::= SEQUENCE { rrcSetupRequest RRCSetupRequest-IEs } RRCSetupRequest-IEs ::= SEQUENCE { ue-Identity InitialUE-Identity, establishmentCause EstablishmentCause, spare BIT STRING (SIZE (1)) } InitialUE-Identity ::= CHOICE { ng-5G-S-TMSI-Part1 BIT STRING (SIZE (39)), randomValue BIT STRING (SIZE (39)) } EstablishmentCause ::= ENUMERATED { emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess, spare6, spare5, spare4, spare3, spare2, spare1} -- TAG-RRCSETUPREQUEST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,151 | 6.8C.1 SPDCCH formats | The short physical downlink control channel (SPDCCH) carries scheduling assignments and other control information for subslot PDSCH, slot-PDSCH, subslot-PUSCH, and slot-PUSCH. A SPDCCH is transmitted using an aggregation of one or several consecutive short control channel elements (SCCEs) where each SCCE consists of multiple short resource element groups (SREGs), defined in clause 6.2.4B. The number of resource elements used for one SPDCCH depends on the SPDCCH format as given by Table 6.8C.1-2 and the number of SREGs per SCCE is given by Table 6.8C.1-1. Table 6.8C.1-1: Number of SREGs per SCCE, Table 6.8C.1-2: Supported SPDCCH formats A UE shall monitor multiple SPDCCHs as defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. One or two resource sets which a UE shall monitor for SPDCCH transmissions in a slot/subslot can be configured. The SPDCCH can use either localized or distributed transmission. All SPDCCH candidates in SPDCCH set use either only localized or only distributed transmission as configured by higher layers (see transmissionType in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]). Similarly, all SPDCCH candidates in SPDCCH set use either only CRS-based demodulation or only DMRS-based demodulation as configured by higher layers (see spdcch-SetReferenceSig in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]). For a resource set with CRS-based SPDCCH, the distributed transmission is implemented at the SREG level, i.e. in the SCCE-to-SREG mapping. For a resource set with DMRS-based SPDCCH, the distributed transmission is implemented at the SCCE level, i.e. in the SPDCCH candidate-to-SCCE mapping. The number of OFDM symbols spanned by a SPDCCH resource set configured with CRS based demodulation can be configured to be one or two. For slot based transmission, the number of OFDM symbols spanned by each SPDCCH candidate of a resource set configured with DMRS-based demodulation is fixed to 2. For subslot based transmission, the number of OFDM symbols spanned by each SPDCCH candidate of a resource set configured with DMRS-based demodulation is equal to the number of OFDM symbols used for the subslot based PDSCH transmission (which depends on the starting symbol index, as specified in Table 6.4.2-1). The physical resource blocks in frequency domain constituting SPDCCH set are in this paragraph assumed to be numbered in ascending order from 0 to . For a CRS-based SPDCCH, SREGs within an SPDCCH set are numbered in a frequency-first time-second manner from 0 to, where is the number of configured OFDM symbols (OS). The frequency-first, time-second mapping of the SREGs within a SPDCCH set is performed from the lowest resource block in frequency domain to the highest resource blocks in frequency domain for the first symbol, and from the highest resource block in frequency domain to the lowest resource block in frequency domain for the second symbol. For a DMRS-based SPDCCH, SREGs within an SPDCCH set are numbered in a time-first frequency-second manner from 0 to. Within CRS-based SPDCCH set , the SCCEs available for transmission of SPDCCHs are numbered from 0 to where for localized mapping and for distributed mapping. Within DMRS-based SPDCCH set , the SCCEs available for transmission of SPDCCHs are numbered from 0 to where . The SCCE number corresponds - SREGs numbered for localized SPDCCH mapping with CRS and DMRS based demodulation and for distributed SPDCCH mapping with DMRS-based demodulation - SREGs numbered for distributed SPDCCH mapping with CRS-based demodulation. where and is the number of SREGs per SCCE. NOTE:represents the number of SREGs per each configured OFDM symbol in the SPDCCH resource set and is the total number of SREGs in SPDCCH resource set . | 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.8C.1 |
4,152 | – NCR-PeriodicFwdResourceSetId | The IE NCR-PeriodicFwdResourceSetId is used to identify one NCR-PeriodicFwdResourceSet. NCR-PeriodicFwdResourceSetId information element -- ASN1START -- TAG-NCR-PERIODICFWDRESOURCESETID-START NCR-PeriodicFwdResourceSetId-r18 ::= INTEGER (0..maxNrofPeriodicFwdResourceSet-1-r18) -- TAG-NCR-PERIODICFWDRESOURCESETID-STOP -- ASN1STOP – NCR-SemiPersistentFwdResourceSet The IE NCR-SemiPersistentFwdResourceSet is used to configure a list of semi-persistent forwarding resources for NCR-Fwd access link. Each semi-persistent forwarding resource configuration includes a list of semi-persistent forwarding resources, a common periodicity and a common reference SCS. NCR-SemiPersistentFwdResourceSet information element -- ASN1START -- TAG-NCR-SEMIPERSISTENTFWDRESOURCESET-START NCR-SemiPersistentFwdResourceSet-r18 ::= SEQUENCE { semiPersistentFwdRsrcSetId-r18 NCR-SemiPersistentFwdResourceSetId-r18, semiPersistentFwdRsrcToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSemiPersistentFwdResource-r18)) OF NCR-SemiPersistentFwdResource-r18 OPTIONAL, -- Need N semiPersistentFwdRsrcToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSemiPersistentFwdResource-r18)) OF NCR-SemiPersistentFwdResourceId-r18 OPTIONAL, -- Need N referenceSCS-r18 SubcarrierSpacing OPTIONAL, -- Need M priorityFlag-r18 ENUMERATED {true} OPTIONAL, -- Need R ... } NCR-SemiPersistentFwdResource-r18 ::= SEQUENCE { semiPersistentFwdRsrcId-r18 NCR-SemiPersistentFwdResourceId-r18, beamIndex-r18 INTEGER (0..63), semiPersistentTimeRsrc-r18 SEQUENCE { periodicityAndOffset-r18 NCR-PeriodicityAndOffset-r18, symbolOffset-r18 INTEGER (0..maxNrofSymbols-1), durationInSymbols-r18 INTEGER (1..112) } } NCR-SemiPersistentFwdResourceId-r18 ::= INTEGER (0..maxNrofSemiPersistentFwdResource-1-r18) -- TAG-NCR-SEMIPERSISTENTFWDRESOURCESET-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,153 | A.3 Causes related to PLMN or SNPN specific network failures and congestion/authentication failures | Cause #20 – MAC failure This 5GMM cause is sent to the network if the USIM detects that the MAC in the AUTHENTICATION REQUEST message is not fresh. Cause #21 – Synch failure This 5GMM cause is sent to the network if the USIM detects that the SQN in the AUTHENTICATION REQUEST message is out of range. Cause #22 – Congestion This 5GMM cause is sent to the UE because of congestion in the network (e.g. no channel, facility busy/congested etc.). Cause #23 – UE security capabilities mismatch This 5GMM cause is sent to the network if the UE detects that the UE security capability does not match the one sent back by the network. Cause #24 – Security mode rejected, unspecified This 5GMM cause is sent to the network if the security mode command is rejected by the UE for unspecified reasons. Cause #26 – Non-5G authentication unacceptable This 5GMM cause is sent to the network in N1 mode if the "separation bit" in the AMF field of AUTN is set to 0 in the AUTHENTICATION REQUEST message (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). Cause #28 – Restricted service area This 5GMM cause is sent to the UE if it requests service in a tracking area of the 3GPP access or in an area of the wireline access, which is a part of the UE's non-allowed area or is not a part of the UE's allowed area. Cause #43 – LADN not available This 5GMM cause is sent to the UE if the user-plane resources of the PDU session are not established when the UE is located outside the LADN service area. Cause #62 – No network slices available This 5GMM cause is sent by the network if there are no available network slices allowed for use by the UE. NOTE: Network does not send this cause in REGISTRATION REJECT message if the UE does not include a requested NSSAI in the REGISTRATION REQUEST message. In that case, if the UE is not registered for onboarding services in SNPN, the network uses other causes (e.g. #13, #15, etc.) based on the subscription. Cause #65 – Maximum number of PDU sessions reached This 5GMM cause is used by the network to indicate that the procedure requested by the UE was rejected as the network has reached the maximum number of simultaneously active PDU sessions for the UE. Cause #67 – Insufficient resources for specific slice and DNN This 5GMM cause is sent by the network to indicate that the requested service cannot be provided due to insufficient resources for specific slice and DNN. Cause #69 – Insufficient resources for specific slice This 5GMM cause is sent by the network to indicate that the requested service cannot be provided due to insufficient resources for specific slice. Cause #71 – ngKSI already in use This 5GMM cause is sent to the network in N1 mode if the ngKSI value received in the AUTHENTICATION REQUEST message is already associated with one of the 5G security contexts stored in the UE. Cause #73 – Serving network not authorized This 5GMM cause is sent to the UE if the UE initiates registration towards a serving network and the serving network fails to be authorized by the UE's home network. Cause #78 –PLMN not allowed to operate at the present UE location This 5GMM cause is sent to the UE to indicate that the PLMN is not allowed to operate at the present UE location. NOTE: This cause is only applicable for satellite NG-RAN access. Cause #81 – Selected N3IWF is not compatible with the allowed NSSAI This 5GMM cause is sent by the network to indicate that the requested service cannot be provided due to the selected N3IWF is not compatible with the allowed NSSAI. Cause #82 – Selected TNGF is not compatible with the allowed NSSAI This 5GMM cause is sent by the network to indicate that the requested service cannot be provided due to the selected TNGF is not compatible with the allowed NSSAI. Cause #90 – Payload was not forwarded This 5GMM cause is sent by the network to indicate that the requested service cannot be provided because payload could not be forwarded by AMF. Cause #91 – DNN not supported or not subscribed in the slice This 5GMM cause is sent by the network to indicate that the requested service cannot be provided because payload could not be forwarded by AMF because the DNN is not supported or not subscribed in the slice selected by the network if the UE did not indicate a slice, or the DNN is not supported or not subscribed in the slice indicated by the UE. Cause #92 – Insufficient user-plane resources for the PDU session This 5GMM cause is sent by the network to indicate that the requested service cannot be provided due to insufficient user-plane resources for the PDU session. Cause #93 – Onboarding services terminated This 5GMM cause is sent by the network if the network initiates a de-registration procedure because the onboarding services are terminated. | 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 | A.3 |
4,154 | C.3.4.1 Profile A | The ME and SIDF shall implement this profile. The ECIES parameters for this profile shall be the following: - EC domain parameters : Curve25519 [46] - EC Diffie-Hellman primitive : X25519 [46] - point compression : N/A - KDF : ANSI-X9.63-KDF [29] - Hash : SHA-256 - SharedInfo1 : (the ephemeral public key octet string – see [29] section 5.1.3) - MAC : HMAC–SHA-256 - mackeylen : 32 octets (256 bits) - maclen : 8 octets (64 bits) - SharedInfo2 : the empty string - ENC : AES–128 in CTR mode - enckeylen : 16 octets (128 bits) - icblen : 16 octets (128 bits) - backwards compatibility mode : false | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | C.3.4.1 |
4,155 | 5.1.2 Authentication and Authorization | The 5G system shall satisfy the following requirements. Subscription authentication: The serving network shall authenticate the Subscription Permanent Identifier (SUPI) in the process of authentication and key agreement between UE and network. Serving network authentication: The UE shall authenticate the serving network identifier through implicit key authentication. NOTE 1: The meaning of 'implicit key authentication' here is that authentication is provided through the successful use of keys resulting from authentication and key agreement in subsequent procedures. NOTE 2: The preceding requirement does not imply that the UE authenticates a particular entity, e.g. an AMF, within a serving network. UE authorization: The serving network shall authorize the UE through the subscription profile obtained from the home network. UE authorization is based on the authenticated SUPI. Serving network authorization by the home network: Assurance shall be provided to the UE that it is connected to a serving network that is authorized by the home network to provide services to the UE. This authorization is 'implicit' in the sense that it is implied by a successful authentication and key agreement run. Access network authorization: Assurance shall be provided to the UE that it is connected to an access network that is authorized by the serving network to provide services to the UE. This authorization is 'implicit' in the sense that it is implied by a successful establishment of access network security. This access network authorization applies to all types of access networks. Unauthenticated Emergency Services: In order to meet regulatory requirements in some regions, the 5G system shall support unauthenticated access for emergency services. This requirement applies to all MEs and only to those serving networks where regulatory requirements for unauthenticated emergency services exist. Serving networks located in regions where unauthenticated emergency services are forbidden shall not support this feature. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.1.2 |
4,156 | 5.2.1 EPS bearer identity | An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-UTRAN. The EPS Bearer Identity is allocated by the MME. When using an EPS Radio Bearer, there is a one to one mapping between EPS RB and EPS Bearer, and the mapping between EPS RB Identity and EPS Bearer Identity is made by E-UTRAN. The E-RAB ID value used at S1 and X2 interfaces to identify an E-RAB is the same as the EPS Bearer ID value used to identify the associated EPS Bearer. When using Control Plane CIoT EPS Optimisation for user data transport for the PDN connectivity service, the MME (for uplink) and UE (for downlink) uses the EPS Bearer Identity contained within the NAS PDUs to identify the associated EPS bearer. When there is a mapping between an EPS bearer and a PDP context, the same identity value is used for the EPS bearer ID and the NSAPI/RAB ID. In some SM signalling messages in GERAN/UTRAN, transaction identifier (TI) represents NSAPI. The TI is dynamically allocated by the UE for UE-requested PDP context activation, and by the network for network-requested PDP context activation. A corresponding allocation is also needed for EPS Bearers in order to successfully transfer Bearers to GERAN/UTRAN. The TI is deallocated when a PDP context/EPS Bearer has been deactivated. TI usage is defined in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. | 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.2.1 |
4,157 | 4.4.4.1 DL PDCP SDU air interface loss rate | This measurement provides the fraction of IP packets (PDCP SDUs) which are lost (not successfully transmitted) on the downlink air interface. Only user-plane traffic (DTCH) is considered. A lost packet is one whose context is removed from the eNodeB/RN after an attempt has been made to transmit part or all of the packet on the air interface but the whole packet has not been successfully transmitted. The measurement is split into subcounters per E-RAB QoS level (QCI). The packets transmitted between the eNodeB (or RN) and UEs and the packets transmitted between E-UTRAN and RN are counted seperately. The measurement is also applicable to RNs. SI This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. Separate counters are maintained for each QCI. In case only a subset of per QCI measurements is supported, a loss rate subcounter calculated across all QCIs will be provided first. Each measurement is an integer value representing the air interface loss rate multiplied by 1E6. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. The measurement name has the form DRB. PdcpSduAirLossRateDl.QCI, which indicates the DL PDCP SDU air interface loss rate between the eNodeB (or RN) and UE DRB. PdcpSduAirLossRateDlRN.QCI, which indicates the DL PDCP SDU air interface loss rate between the E-UTRAN and RN. where QCI identifies the target E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic 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.4.4.1 |
4,158 | B.5 Derivation of Kc128 | This input string is used when there is a need to derive Kc128 from CK and IK. The key Kc128 is used as input to the GSM A5 and GEA ciphering algorithms which requires 128-bit keys. Kc128 shall only be derived by the MS and the network when in UMTS security context. Kc128 shall not be derived by the MS or the network when in GSM security context. This implies that GSM A5 using Kc128 and GEA using Kc128 can only be selected by the network (see TS 43.020[ Security related network functions ] [36]) when the UE and network are in UMTS security context as there is otherwise no key which the ciphering algorithms can use. - FC = 0x32 The Key input is the concatenation of CK and IK (i.e., CK || IK). No input parameters (Pi, Li) are used by this function. The KDF returns a 256-bit output, where the 128 most significant bits are identified with Kc128 . | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | B.5 |
4,159 | 5.6.1 Architecture Principles for E-UTRAN to GERAN NACC | Introducing NACC from E-UTRAN to GERAN follows the principles of the Network Assisted Cell Change between UTRAN and GERAN as described in TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [22] and TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. It specifies the RAN Information Management (RIM) procedures as specified in clause 5.15 and depicted in figure 5.6-1. Figure 5.6-1: E-UTRAN to GERAN NACC basic network architecture The support for the NACC from E-UTRAN to GERAN has the following impacts on E-UTRAN / GERAN architecture: - Affected nodes: BSC, eNodeB, MME, SGSN; - Affected network interfaces: Gb, Iu, S3, Gn, S1; - Affected radio interfaces: Um and Uu. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.1 |
4,160 | – TAR-Config | The IE TAR-Config is used to configure Timing Advance reporting in non-terrestrial networks and ATG network. TAR-Config information element -- ASN1START -- TAG-TAR-CONFIG-START TAR-Config-r17 ::= SEQUENCE { offsetThresholdTA-r17 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5, ms6 ,ms7, ms8, ms9, ms10, ms11, ms12, ms13, ms14, ms15, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need R timingAdvanceSR-r17 ENUMERATED {enabled} OPTIONAL, -- Need R ... } TAR-Config-r18 ::= SEQUENCE { offsetThresholdTA-r18 INTEGER (1..56) OPTIONAL, -- Need R timingAdvanceSR-r18 ENUMERATED {enabled} OPTIONAL, -- Need R ... } -- TAG-TAR-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,161 | 8.16.1 MN initiated Conditional PSCell Addition | The procedure for MN initiated Conditional PSCell Addition (CPA) is shown in Figure 8.16-1. Figure 8.16.1-1 Conditional Secondary Node Addition procedure 1-12. The steps 1-12 are as defined in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12]. a1-a5. The steps a1-a5 are as defined in clause 8.9.2 and with conditional indications. a6. After Random Access procedure successfully performed at the candidate gNB-DU which becomes the target SN gNB-DU, the target gNB-DU sends a Downlink Data Delivery Status frame to inform the target gNB-CU-UP. The target gNB-DU also sends an ACCESS SUCCESS message to inform the target gNB-CU-CP of which cell the UE has successfully accessed. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.16.1 |
4,162 | – SL-SRAP-Config | The IE SL-SRAP-Config is used to set the configurable SRAP parameters used by L2 U2N Relay UE and L2 U2N Remote UE as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66]. SL-SRAP-Config information element -- ASN1START -- TAG-SL-SRAP-CONFIG-START SL-SRAP-Config-r17 ::= SEQUENCE { sl-LocalIdentity-r17 INTEGER (0..255) OPTIONAL, -- Need M sl-MappingToAddModList-r17 SEQUENCE (SIZE (1..maxLC-ID)) OF SL-MappingToAddMod-r17 OPTIONAL, -- Need N sl-MappingToReleaseList-r17 SEQUENCE (SIZE (1..maxLC-ID)) OF SL-RemoteUE-RB-Identity-r17 OPTIONAL, -- Need N ... } SL-MappingToAddMod-r17 ::= SEQUENCE { sl-RemoteUE-RB-Identity-r17 SL-RemoteUE-RB-Identity-r17, sl-EgressRLC-ChannelUu-r17 Uu-RelayRLC-ChannelID-r17 OPTIONAL, -- Cond L2RelayUE sl-EgressRLC-ChannelPC5-r17 SL-RLC-ChannelID-r17 OPTIONAL, -- Need N ... } SL-RemoteUE-RB-Identity-r17 ::= CHOICE { srb-Identity-r17 INTEGER (0..3), drb-Identity-r17 DRB-Identity, ... } -- TAG-SL-SRAP-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,163 | 11.1 Multiple TNLAs for Xn-C | In the following, the procedure for managing multiple TNLAs for Xn-C is described. Figure 11.1-1: Managing multiple TNLAs for Xn-C. 1. The NG-RAN node1 establishes the first TNLA with the NG-RAN node2 using a configured TNL address. NOTE: The NG-RAN node1 may use different source and/or destination IP end point(s) if the TNL establishment towards one IP end point fails. How the NG-RAN node1 gets the remote IP end point(s) and its own IP address are outside the scope of this specification. 2-3. Once the TNLA has been established, the NG-RAN node1 initiates the Xn Setup procedure to exchange application level configuration data 4-6. The NG-RAN node2 may add additional TNL Endpoint(s) to be used for Xn-C signalling between the NG-RAN node1 and the NG-RAN node2 pair using the NG-RAN node Configuration Update procedure. NG-RAN node Configuration Update procedure also allows the NG-RAN node2 to request the NG-RAN node1 to modify or release TNLA(s). 7-9. The NG-RAN node1 may add additional TNL Endpoint(s) to be used for Xn-C signalling between the NG-RAN node1 and the NG-RAN node2 pair using the NG-RAN node Configuration Update procedure. NG-RAN node Configuration Update procedure also allows the NG-RAN node1 to request the NG-RAN node2 to modify or release TNLA(s). The XnAP UE TNLA binding is a binding between a XnAP UE association and a specific TNL association for a given UE. After the XnAP UE TNLA binding is created, the NG-RAN node1 or the NG-RAN node2 can update the UE TNLA binding by sending the first available XnAP message for the UE to the peer NG-RAN node via a different TNLA. The peer NG-RAN node shall update the XnAP UE TNLA binding with the new TNLA. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 11.1 |
4,164 | – PosSRS-RRC-Inactive-OutsideInitialUL-BWP | The IE PosSRS-RRC-Inactive-OutsideInitialUL-BWP is used to convey the capabilities supported by the UE for Positioning SRS transmission in RRC_INACTIVE state configured outside initial UL BWP. PosSRS-RRC-Inactive-OutsideInitialUL-BWP information element -- ASN1START -- TAG-POSSRS-RRC-INACTIVE-OUTSIDEINITIALUL-BWP-START PosSRS-RRC-Inactive-OutsideInitialUL-BWP-r17::= SEQUENCE { -- R1 27-15b: Positioning SRS transmission in RRC_INACTIVE state configured outside initial UL BWP maxSRSposBandwidthForEachSCS-withinCC-FR1-r17 ENUMERATED {mhz5, mhz10, mhz15, mhz20, mhz25, mhz30, mhz35, mhz40, mhz45, mhz50, mhz60, mhz70, mhz80, mhz90, mhz100} OPTIONAL, maxSRSposBandwidthForEachSCS-withinCC-FR2-r17 ENUMERATED {mhz50, mhz100, mhz200, mhz400} OPTIONAL, maxNumOfSRSposResourceSets-r17 ENUMERATED {n1, n2, n4, n8, n12, n16} OPTIONAL, maxNumOfPeriodicSRSposResources-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, maxNumOfPeriodicSRSposResourcesPerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} OPTIONAL, differentNumerologyBetweenSRSposAndInitialBWP-r17 ENUMERATED {supported} OPTIONAL, srsPosWithoutRestrictionOnBWP-r17 ENUMERATED {supported} OPTIONAL, maxNumOfPeriodicAndSemipersistentSRSposResources-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, maxNumOfPeriodicAndSemipersistentSRSposResourcesPerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} OPTIONAL, differentCenterFreqBetweenSRSposAndInitialBWP-r17 ENUMERATED {supported} OPTIONAL, switchingTimeSRS-TX-OtherTX-r17 ENUMERATED {us100, us140, us200, us300, us500} OPTIONAL, -- R1 27-15c: Support of positioning SRS transmission in RRC_INACTIVE state outside initial BWP with semi-persistent SRS maxNumOfSemiPersistentSRSposResources-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, maxNumOfSemiPersistentSRSposResourcesPerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} OPTIONAL, ... } -- TAG-POSSRS-RRC-INACTIVE-OUTSIDEINITIALUL-BWP-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,165 | 8.2.1.4.1E Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Ports with CRS assistance information | The requirements are specified in Table 8.2.1.4.1E-2, with the addition of parameters in Table 8.2.1.4.1E-1. The purpose is to verify the closed loop rank-one performance with wideband precoding when CRS assistance information [7] is configured. In Table 8.2.1.4.1E-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] includes Cell 2 and Cell 3. Table 8.2.1.4.1E-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) Table 8.2.1.4.1E-2: Minimum Performance Single-Layer Spatial Multiplexing (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.4.1E |
4,166 | 4.27 Mobile base station relay support | A 5GS can support a MBSR-UE and a UE accessing to MBSR (see subclause 5.35A of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). This subclause describes NAS-specific aspects of the 5GS features to support the authorization of the MBSR-UE, and the control of the UE access via MBSR. The AMF authorizes the UE's request to act as a MBSR based on the subscription information. The AMF can indicate to the MBSR-UE that it is not allowed to operate as MBSR during registration procedure as specified in subclause 5.5.1.2. Enhanced CAG information can be used for the control of UE's access via MBSR. CAG identifier is used to control the access of UE via MBSR. 5GC supports the UE access control based on the PLMND ID and CAG identifier broadcast by the MBSR and the CAG-ID authorized based on "Allowed CAG list" in the PLMN's entry of "CAG information list" stored in the UE. Time validity information can be provided to the UE together with the CAG identifier for accessing to MBSR in order to control that UE not accessing the MBSR cell outside of the time validity information. For the UE not supporting CAG functionality, 5GC can control the access of the UE with managing the forbidden tracking area. | 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.27 |
4,167 | 11.2.1.2.2 EPC based IPv4 Non Transparent access | In this case: - a static or a dynamic IPv4 address belonging to the Intranet/ISP addressing space is allocated to a UE at IP-CAN session establishment. The methods of allocating IP address to the UE are specified in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3], 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [78]. The allocated IPv4 address is used for packet forwarding within the P-GW and for packet forwarding on the Intranet/ISP; - as a part of the IP-CAN session establishment, the P-GW may request user authentication from an external AAA server (i.e. RADIUS, Diameter) belonging to the Intranet/ISP; - the IPv4 address allocation to the UE may be performed based on the subscription or a local address pool, which belongs to the Intranet/ISP addressing space, provisioned in the P-GW. The IPv4 address allocation to the UE may also be done via the address allocation servers (i.e. DHCPv4, RADIUS AAA, Diameter AAA) belonging to the Intranet/ISP; - if requested by the UE at IP-CAN session establishment, the P-GW may retrieve the Protocol Configuration Options or IPv4 configuration parameters from a locally provisioned database in P-GW and/or from some external server (i.e. DHCPv4, RADIUS AAA, Diameter AAA) belonging to the Intranet/ISP; - the communication between the Packet Domain and the Intranet/ISP may be performed over any network, even an insecure network ,e.g. the Internet. In case of an insecure connection between the P-GW and the Intranet/ISP, there may be a specific security protocol in between. This security protocol is defined by mutual agreement between PLMN operator and Intranet/ISP administrator. Table 0 summarizes the IPv4 address allocation and parameter configuration use cases between the UE and the P-GW that may lead the P-GW to interwork with the external DHCPv4, RADIUS AAA and Diameter AAA servers over Sgi reference point. For detailed description of the signalling flows between the UE and the P-GW, see the references in the table. The detailed description of the signalling use cases that may be triggered between the P-GW and the external servers are specified in this document, as referenced in the table. Table 0 : IPv4 address allocation and parameter configuration use cases | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.2.1.2.2 |
4,168 | 4.22.9.3 N2 based handover | Inter NG-RAN node N2 based handover, as described in clauses 4.9.1.3.2 and 4.9.1.3.3, is supported for the 3GPP access with the differences and clarifications described below. - In step 2 of clause 4.9.1.3.2, the S-AMF determines whether or not the T-AMF supports ATSSS based on the supported features of the T-AMF provided by NRF or based on local configuration. - In step 3 of clause 4.9.1.3.2, if the S-AMF determined in step 2 that the T-AMF does not support ATSSS, the S-AMF does not include the PDU Session context of the MA PDU Session(s) in the UE context transferred to the T-AMF. - After step 6a of clause 4.9.1.3.3, if the S-AMF has not included MA PDU Session(s) in the UE context in step 3 of clause 4.9.1.3.2, the S-AMF informs the corresponding SMF(s) to release the MA PDU Session(s) by invoking the Nsmf_PDUSession_ReleaseSMContext service operation as described in clause 4.22.10. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.9.3 |
4,169 | 4.7.4 Support for Application / Service Layer Rate Adaptation | The E-UTRAN/UTRAN and the UE support the RFC 3168 [55] Explicit Congestion Notification (ECN), as described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5], TS 25.401[ None ] [16] and TS 26.114[ IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction ] [56]. The IP level ECN scheme enables the E-UTRAN/UTRAN to trigger a rate adaptation scheme at the application / service / transport layer. To make sufficient time available for end-to-end codec rate adaptation the E-UTRAN/UTRAN should attempt to not drop any packets on a bearer for a default grace period of at least 500 ms after it has indicated congestion with ECN on the bearer for packets within the packet delay budget. During this ECN grace period the E-UTRAN/UTRAN should also attempt to meet the QCI characteristics / QoS class associated with the bearer. NOTE 1: Note that the receiving end-point should interpret all ECN-CE signals received within one end-to-end round-trip time as one "congestion event" (see IETF RFC 3168 [55] and TS 26.114[ IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction ] [56]). The MBR of a particular GBR bearer may be set larger than the GBR. NOTE 2: Enforcement of APN-AMBR / UE-AMBR is independent of whether the MBR of a particular GBR bearer has been set larger than the GBR (see clause 4.7.3). The EPC does not support E-UTRAN/UTRAN-initiated "QoS re-negotiation". That is, the EPC does not support an eNodeB/RNC initiated bearer modification procedure. If an eNodeB/RNC can no longer sustain the GBR of an active GBR bearer then the eNodeB/RNC should simply trigger a deactivation of that bearer. | 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.4 |
4,170 | H.4 Path and Link delay measurements | The procedure described in this clause is applicable if DS-TT and NW-TT support operating as a boundary clock or as a time-aware system or as peer to peer Transparent Clock or end to end Transparent Clock, and when the PTP instance in 5GS is configured to operate as a time-aware system or as a Boundary Clock or as peer to peer Transparent Clock or as end to end Transparent Clock. Whether DS-TT/NW-TT support operating as a boundary clock or peer to peer Transparent Clock or end to end Transparent Clock or as a time-aware system (support of the IEEE Std 802.1AS [104] PTP profile) may be determined as described in clause K.2.1. PTP ports in DS-TT and NW-TT may support the following delay measurement mechanisms: - Delay request-response mechanism as described in clause 11.3 of IEEE Std 1588 [126]; - Peer-to-peer delay mechanism as defined in clause 11.4 of IEEE Std 1588 [126]; - Common Mean Link Delay Service. Depending on the measurement mechanisms supported by DS-TT and NW-TT as well as the configured clock mode of 5GS, the PTP ports in DS-TT and NW-TT are configured as follows: - PTP ports configured to operate as a time-aware system according to IEEE Std 802.1AS [104] may be configured to use the peer-to-peer delay mechanism or Common Mean Link Delay Service; - PTP ports configured to operate as a Boundary Clock according to IEEE Std 1588 [126] may be configured to use the delay request-response mechanism, the peer-to-peer delay mechanism or Common Mean Link Delay Service. - PTP ports in 5GS configured to operate as a peer-to-peer Transparent Clock according to IEEE Std 1588 [126] shall use the peer-to-peer delay mechanism. - PTP ports in 5GS configured to operate as an end-to-end Transparent Clock according to IEEE Std 1588 [126] do not actively participate in path and link measurements mechanisms but shall calculate and add residence time and delay asymmetry information to PTP messages as defined in clause 10.2.2 of IEEE Std 1588 [126]. If DS-TT and NW-TT support operating as an end-to-end Transparent Clock, then the residence time for one-step operation as an end-to-end Transparent Clock for the path and link measurements is calculated as follows: - Upon reception of a PTP Delay_Req/Pdelay_Req/Pdely_Resp message from the upstream PTP instance, the ingress TT (i.e. NW-TT or DS-TT) makes an ingress timestamping (TSi) for the message. - The ingress timestamp is conveyed to the egress TT via the PDU Session as described in clause H.2. - The PTP port in the egress TT then creates egress timestamping (TSe) for the PTP message for external PTP network. The difference between TSi and TSe is considered as the calculated residence time spent within the 5G system for this PTP message expressed in 5GS time. If needed, the PTP port in the egress TT convert the calculated resident time in 5GS into the residence time expressed in PTP GM time e.g. by means of the factor as specified in Equation (6) of clause 12.2.2 of IEEE Std 1588 [126]. - The PTP port in the egress TT modifies the payload of the PTP Delay_Req/Pdelay_Req/Pdelay_Resp message that it sends towards the downstream PTP instance as follows: - Adds the calculated residence time to the correction field. - Removes Suffix field that contains TSi. If DS-TT and NW-TT support operating as an end-to-end Transparent Clock, then the residence time for two-step operation as an end-to-end Transparent Clock for the path and link measurements is calculated as follows: - Upon reception of a PTP Delay_Req/Pdelay_Req/Pdelay_Resp message from the upstream PTP instance, the ingress TT (i.e. NW-TT or DS-TT) makes an ingress timestamping (TSi) for the message. - If the ingress TT receives a Pdelay_Resp message with the twoStepFlag set to FALSE, then the ingress TT modifies the twoStepFlag to TRUE and creates a PTP Pdelay_Resp_Follow_Up message. - The ingress timestamp is conveyed to the egress TT via the PDU Session as described in clause H.2. - The PTP port in the egress TT then creates egress timestamping (TSe) for the PTP message for external PTP network. The difference between TSi and TSe is considered as the calculated residence time spent within the 5G system for this PTP message expressed in 5GS time. If needed, the PTP port in the egress TT converts the calculated residence time in 5GS into the residence time expressed in PTP GM time, e.g. by means of the factor as specified in Equation (6) of clause 12.2.2 of IEEE Std 1588 [126]. The egress TT then stores the calculated residence time expressed in PTP GM time and removes Suffix field that contains TSi before sending the PTP Delay_Req/Pdelay_Req/Pdelay_Resp message towards the downstream PTP instance. - Upon reception of the PTP Delay_Resp message associated with the PTP Delay_Req, the egress TT for the PTP Delay_Req message (i.e. the ingress TT for the PTP Delay_Resp message) modifies the payload of the PTP Delay_Resp message that it sends towards the ingress TT of the PTP Delay_Req message (i.e. egress TT for the PTP Delay_Resp message) as follows: - Adds the (previously stored) calculated residence time to the correction field. - Upon reception (or local creation) of the PTP Pdelay_Resp_Follow_Up message associated with the previously received PTP Pdelay_Resp message, the ingress TT for the PTP Pdelay_Resp_Follow_Up message modifies the payload of the PTP Pdelay_Resp_Follow_Up message that it sends towards the egress TT for the PTP Pdelay_Resp_Follow_Up message as follows: - Adds the (previously stored) calculated residence time of the associated PTP Pdelay_Req message to the correction field. - Upon reception of the PTP Pdelay_Resp_Follow_Up message associated with the PTP Pdelay_Resp, the egress TT for PTP Pdelay_Resp_Follow_Up message modifies the payload of the PTP Pdelay_Resp_Follow_Up message that it sends towards the downstream PTP instance as follows: - Adds the (previously stored) calculated residence time of the associated PTP Pdelay_Resp messages to the correction field. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | H.4 |
4,171 | 6.5.3.4 UE requested bearer resource allocation procedure not accepted by the network 6.5.3.4.1 General | If the bearer resource allocation requested cannot be accepted by the network, the MME shall send a BEARER RESOURCE ALLOCATION REJECT message to the UE. The message shall contain the PTI and an ESM cause value indicating the reason for rejecting the UE requested bearer resource allocation. The ESM cause value typically indicates one of the following: #26: insufficient resources; #30: request rejected by Serving GW or PDN GW; #31: request rejected, unspecified; #32: service option not supported; #33: requested service option not subscribed; #34: service option temporarily out of order; #35: PTI already in use; #37: EPS QoS not accepted; #41: semantic error in the TFT operation; #42: syntactical error in the TFT operation; #43: invalid EPS bearer identity; #44: semantic error(s) in packet filter(s); #45: syntactical error(s) in packet filter(s); #56: collision with network initiated request; #59: unsupported QCI value; #60: bearer handling not supported; #65: maximum number of EPS bearers reached; or #95 – 111: protocol errors. If the bearer resource allocation requested is for an established LIPA PDN connection or SIPTO at the local network PDN connection, then the network shall reply with a BEARER RESOURCE ALLOCATION REJECT message with ESM cause #60 "bearer handling not supported". If the requested new TFT is not available, then the BEARER RESOURCE ALLOCATION REJECT message shall be sent. The TFT in the request message is checked by the network for different types of TFT IE errors as follows: a) Semantic errors in TFT operations: 1) When the TFT operation is an operation other than "Create a new TFT". The network shall reject the allocation request with ESM cause #41 "semantic error in the TFT operation". b) Syntactical errors in TFT operations: 1) When the TFT operation = "Create a new TFT" and the packet filter list in the TFT IE is empty. 2) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list. The network shall reject the allocation request with ESM cause #42 "syntactical error in the TFT operation". c) Semantic errors in packet filters: 1) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the network determines a semantic error in a packet filter is outside the scope of the present document. 2) When the resulting TFT does not contain any packet filter which applicable for the uplink direction. The network shall reject the allocation request with ESM cause #44 "semantic errors in packet filter(s)". d) Syntactical errors in packet filters: 1) When the TFT operation = "Create a new TFT" and two or more packet filters in the resultant TFT would have identical packet filter identifiers. 2) When the TFT operation = "Create a new TFT" and two or more packet filters among all TFTs associated with the PDN connection would have identical packet filter precedence values. 3) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. In case 2, if the old packet filters do not belong to the default EPS bearer context, the network shall not diagnose an error, shall further process the new request and, if it was processed successfully, shall delete the old packet filters which have identical filter precedence values. Furthermore, the network shall perform an EPS bearer context deactivation request procedure to deactivate the dedicated EPS bearer context(s) for which it has deleted the packet filters. In case 2, if one or more old packet filters belong to the default EPS bearer context, the network shall release the relevant PDN connection using the EPS bearer context deactivation procedure. If it is the last remaining PDN connection and EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the network shall detach the UE using detach type "re-attach required". Otherwise the network shall reject the allocation request with ESM cause #45 "syntactical errors in packet filter(s)". The network may include a Back-off timer value IE in the BEARER RESOURCE ALLOCATION REJECT message. If the Back-off timer value IE is included and the ESM cause value is different from #26 "insufficient resources" and #65 "maximum number of EPS bearers reached", the network may include the Re-attempt indicator IE to indicate: - whether the UE is allowed to attempt a secondary PDP context activation procedure in the PLMN for the same in A/Gb or Iu mode or a PDU session modification procedure in the PLMN for the same APN in N1 mode; and - whether another attempt in A/Gb and Iu mode, in S1 mode or in N1 mode is allowed in an equivalent PLMN. Upon receipt of a BEARER RESOURCE ALLOCATION REJECT message, the UE shall stop the timer T3480, release the traffic flow aggregate description associated to the PTI value, and enter the state PROCEDURE TRANSACTION INACTIVE. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.3.4 |
4,172 | 9.9.3.58 UE radio capability ID availability | The purpose of the UE radio capability ID availability information element is to indicate that the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected PLMN. The UE radio capability ID availability is a type 4 information element with a length of 3 octets. The UE radio capability ID availability information element is coded as shown in figure 9.9.3.58.1 and table 9.9.3.58.1. Figure 9.9.3.58.1: UE radio capability ID availability information element Table 9.9.3.58.1: UE radio capability ID availability information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.58 |
4,173 | – FreqSeparationClass | The IE FreqSeparationClass is used for an intra-band non-contiguous CA band combination to indicate frequency separation between lower edge of lowest CC and upper edge of highest CC in a frequency band. FreqSeparationClass information element -- ASN1START -- TAG-FREQSEPARATIONCLASS-START FreqSeparationClass ::= ENUMERATED { mhz800, mhz1200, mhz1400, ..., mhz400-v1650, mhz600-v1650} FreqSeparationClassDL-v1620 ::= ENUMERATED {mhz1000, mhz1600, mhz1800, mhz2000, mhz2200, mhz2400} FreqSeparationClassUL-v1620 ::= ENUMERATED {mhz1000} -- TAG-FREQSEPARATIONCLASS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,174 | 4.7.5.2 RACH-less handover | During the mobile IAB-DU migration procedure, RACH-less handover can be configured for a UE that is migrated from the source logical mobile IAB-DU to the target logical mobile IAB-DU. The RACH-less handover procedure applies the following functionality: The UE uses the same timing advance at the cell of the target logical mobile IAB-DU as signalled by the cell of the source logical mobile IAB-DU. The handover command for the UE contains a beam identifier for the beam to be used by the UE at the target logical mobile-IAB cell. The beam may be determined based on a UE measurement report and/or based on implementation, e.g., using the target cell's knowledge about the beam(s) used by the UE at the co-located source cell. The handover command may include a pre-allocated UL grant. Alternatively, an UL grant is dynamically signalled by the target logical IAB-DU cell. The UE transmits the RRCReconfigurationComplete message using the pre-allocated or dynamically signalled UL grant. The UE's successful UL data reception on the target logical mobile-IAB cell terminates the RACH-less handover execution. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.7.5.2 |
4,175 | 5.2.6.9.2 Nnef_AFsessionWithQoS_Create service operation | Service operation name: Nnef_AFsessionWithQoS Create Description: The consumer requests the network to provide a specific QoS for an AF session for a UE or a list of UEs. Inputs, Required: AF Identifier, UE address (i.e. IP address or MAC address and only applicable for a single UE AF session), a list of UE addresses (as described in clause 4.15.6.13, and only applicable for a Multi-member AF session). Flow description information as described in clause 6.1.3.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] or External Application Identifier, QoS Reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE 1: In this Release, when a list of UE addresses is provided, the Flow description information is common for all UE addresses in the list. Further details are described in clause 4.15.6.13.2. Inputs, Optional: Time period, traffic volume, Alternative Service Requirements (containing one or more QoS Reference parameters or Requested Alternative QoS Parameter Sets in a prioritized order), QoS Monitoring parameter(s) as defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Reporting frequency, Target of reporting and optional an indication of local event notification as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], DNN if available, S-NSSAI if available. Only applicable for a single UE AF session: flow direction, Burst Arrival Time at UE (uplink) or UPF (downlink), Periodicity as described in clause 5.27.2 or clause 5.37.8.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Time domain, Survival Time, BAT Window or Capability for BAT adaptation, Packet Delay Variation requirements as described in clause 6.1.3.26 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], Periodicity Range, RT Latency Indication as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], PDU Set QoS Parameters as described in clause 5.7.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Protocol Description (as described in clause 5.37.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Indication of ECN marking for L4S as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], QoS duration, QoS inactivity interval, Multi-Modal Service ID together with Multi-modal Service Requirements information for each data flow as described in clause 6.1.3.27.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Only applicable for a Multi-member AF session: Consolidated Data Rate Threshold, a list of UE addresses subject to Consolidated Data Rate monitoring. NOTE 2: If Consolidated Data Rate Threshold is provided, the QoS Monitoring parameter(s) indicates the Guaranteed Bitrate shall be provided. NOTE 3: When the AF request is for Consolidated Data Rate monitoring is set for event reporting, 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. NOTE 4: When the Consolidated Data Rate threshold is provided, it applies to the list of UE addresses by default. However, if the list of UE addresses subject for Consolidated Data Rate monitoring is also provided, then such list has to be the subset of the list of UE addresses. Outputs, Required: Transaction Reference ID, result (result as described in clause 4.15.6.13 if a list of UE is targeted). 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.2 |
4,176 | 12.3 CN Identifier | A CN node is uniquely identified within a PLMN by its CN Identifier (CN-Id). The CN-Id together with the PLMN identifier globally identifies the CN node. The CN-Id together with the PLMN-Id is used as the CN node identifier in RANAP signalling over the Iu interface. - Global CN-Id = PLMN-Id || CN-Id The CN-Id is defined by the operator, and set in the nodes via O&M. For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [17]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 12.3 |
4,177 | 4.7.8 Inter-UE QoS for NB-IoT UEs using Control Plane CIoT EPS Optimisation | To allow the E-UTRAN to prioritise resource allocation between different NB-IoT UEs when some of the UEs are using the Control Plane CIoT EPS Optimisation, the eNodeB may request, based on configuration, the MME to supply the eNodeB with the negotiated QoS profile for any UE that is using the Control Plane CIoT EPS Optimisation. The QoS profile sent to the eNodeB by the MME consists of the E-RAB Level QoS Parameter in the E-RAB to be Setup List IE (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]). In order to reduce signalling load on the MME, the eNodeB may be configured to request the QoS profile from the MME by using the UE's S-TMSI as identifier, e.g., when the eNodeB's NB-IoT load exceeds certain threshold(s) or when the eNodeB needs to cache the QoS profile. If the UE has more than one EPS bearer active, the MME sends QoS profile for only one EPS bearer to the eNodeB. In this case the MME uses local configuration (e.g. considering table 6.1.7 in TS 23.203[ Policy and charging control architecture ] [6], the MME chooses the non-GBR EPS bearer with the QCI corresponding to the highest Priority Level) to determine which EPS bearer's QoS to send to the eNodeB. If the MME has no EPS bearers active for the UE, then this fact is indicated to the eNodeB. The eNodeB can use the QoS profile to assist with resource prioritisation decisions between different NB-IoT UEs (irrespective of whether the UE/eNodeB is using the Control Plane CIoT EPS Optimisation, or, the User Plane CIoT EPS Optimisation). | 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.8 |
4,178 | 5.4.11.5 Network selection for NR satellite access | Network selection principles specified in clause 5.2.2 apply also for NR satellite access. For NR satellite access, a UE with location capability should use its awareness of its location to select a PLMN that is allowed to operate in the UE location as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. In order to ensure that the regulatory requirements are met, the network may be configured to enforce this UE choice by verifying the UE location, as described in clause 5.4.11.4. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.11.5 |
4,179 | 6.3 Authentication and key agreement 6.3.1 General | The mechanism described here achieves mutual authentication by the user and the network showing knowledge of a secret key K which is shared between and available only to the USIM and the AuC in the user's HE. In addition the USIM and the HE keep track of counters SQNMS and SQNHE respectively to support network authentication. The sequence number SQNHE is an individual counter for each user and the sequence number SQNMS denotes the highest sequence number the USIM has accepted. The method was chosen in such a way as to achieve maximum compatibility with the current GSM security architecture and facilitate migration from GSM to UMTS. The method is composed of a challenge/response protocol identical to the GSM subscriber authentication and key establishment protocol combined with a sequence number-based one-pass protocol for network authentication derived from ISO/IEC 9798-4 [10] (section 5.1.1). An overview of the mechanism is shown in Figure 5. Figure 5: Authentication and key agreement Upon receipt of a request from the VLR/SGSN, the HE/AuC sends an ordered array of n authentication vectors (the equivalent of a GSM "triplet") to the VLR/SGSN. The authentication vectors are ordered based on sequence number. Each authentication vector consists of the following components: a random number RAND, an expected response XRES, a cipher key CK, an integrity key IK and an authentication token AUTN. Each authentication vector is good for one authentication and key agreement between the VLR/SGSN and the USIM. When the VLR/SGSN initiates an authentication and key agreement, it selects the next authentication vector from the ordered array and sends the parameters RAND and AUTN to the user. Authentication vectors in a particular node are used on a first-in / first-out basis. The USIM checks whether AUTN can be accepted and, if so, produces a response RES which is sent back to the VLR/SGSN. The USIM also computes CK and IK. The VLR/SGSN compares the received RES with XRES. If they match the VLR/SGSN considers the authentication and key agreement exchange to be successfully completed. The established keys CK and IK will then be transferred by the USIM and the VLR/SGSN to the entities which perform ciphering and integrity functions. VLR/SGSNs can offer secure service even when HE/AuC links are unavailable by allowing them to use previously derived cipher and integrity keys for a user so that a secure connection can still be set up without the need for an authentication and key agreement. Authentication is in that case based on a shared integrity key, by means of data integrity protection of signalling messages (see 6.4). The authenticating parties shall be the AuC of the user's HE (HE/AuC) and the USIM in the user's mobile station. The mechanism consists of the following procedures: A procedure to distribute authentication information from the HE/AuC to the VLR/SGSN. This procedure is described in 6.3.2. The VLR/SGSN is assumed to be trusted by the user's HE to handle authentication information securely. It is also assumed that the intra-system links between the VLR/SGSN to the HE/AuC are adequately secure. It is further assumed that the user trusts the HE. A procedure to mutually authenticate and establish new cipher and integrity keys between the VLR/SGSN and the MS. This procedure is described in 6.3.3. A procedure to distribute authentication data from a previously visited VLR to the newly visited VLR. This procedure is described in 6.3.4. It is also assumed that the links between VLR/SGSNs are adequately secure. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3 |
4,180 | 1.7.2.1 Packet services in GSM (A/Gb mode only) | For mobile stations supporting the General Packet Radio Service (GPRS), it is explicitly mentioned throughout the technical specification if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave. A GPRS MS may operate in one of the following MS operation modes, see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]: - MS operation mode A; - MS operation mode B; or - MS operation mode C. The MS operation mode depends on the services that the MS is attached to, i.e., only GPRS or both GPRS and non-GPRS services, and upon the MS's capabilities to operate GPRS and other GSM services simultaneously. Mobile stations that are capable to operate GPRS services are referred to as GPRS MSs. NOTE: Other GSM technical specifications may refer to the MS operation modes A, B, and C as GPRS class-A MS, GPRS class-B MS, and GPRS class-C MS. It should be noted that it is possible that for a GPRS MS, the GMM procedures currently described in the ETS do not support combinations of VGCS, VBS and GPRS. The possible interactions are not studied yet. | 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.7.2.1 |
4,181 | 5.5.1.3.6 Mobility and periodic registration update for initiating an emergency PDU session not accepted by the network | If the mobility and periodic registration update request for initiating an emergency PDU session cannot be accepted by the network, the UE shall perform the procedures as described in subclause 5.5.1.3.5. If the mobility and periodic registration update request for initiating an emergency PDU session fails due to receiving the AUTHENTICATION REJECT message, the UE shall perform the procedures as described in subclauses 5.4.1.2.2.11, 5.4.1.2.3.1, 5.4.1.2.3A.1 or 5.4.1.3.5. Then if the UE is in the same selected PLMN where the last mobility and periodic registration update request was attempted, the UE shall: a) inform the upper layers of the failure of the procedure; or NOTE 1: This can result in the upper layers requesting implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] can result in the emergency call being attempted to another IP-CAN. b) perform de-registration locally, if not de-registered already, and attempt initial registration for emergency services. If the mobility and periodic registration update request for initiating an emergency PDU session fails due to abnormal case b) in subclause 5.5.1.3.7, the UE shall perform the actions as described in subclause 5.5.1.3.7 and inform the upper layers of the failure to access the network. NOTE 2: This can result in the upper layers requesting implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] can result in the emergency call being attempted to another IP-CAN. If the mobility and periodic registration update request for initiating an emergency PDU session fails due to abnormal cases c), d), e) or g) in subclause 5.5.1.3.7, the UE shall perform the procedures as described in subclause 5.5.1.3.7. Then if the UE is in the same selected PLMN where the last mobility and periodic registration update request was attempted, the UE shall: a) inform the upper layers of the failure of the procedure; or NOTE 3: This can result in the upper layers requesting implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] can result in the emergency call being attempted to another IP-CAN. b) perform de-registration locally, if not de-registered already, and attempt initial registration for emergency services. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.3.6 |
4,182 | 5.3.18 Restriction on use of enhanced coverage | In order to deal with use of extensive resources from the network, the operator may prevent specific subscribers from using enhanced coverage (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). When in NB-N1 mode, the UE shall indicate support for restriction on use of enhanced coverage. When in WB-N1 mode, the UE supporting either CE mode A or CE mode B shall indicate support for restriction on use of enhanced coverage. The UE supporting restriction on use of enhanced coverage indicates its support for restriction on use of enhanced coverage in the REGISTRATION REQUEST message. If the UE supports restriction on use of enhanced coverage, the AMF indicates in the REGISTRATION ACCEPT message (see subclause 5.5.1.2 and subclause 5.5.1.3) that: a) when in WB-N1 mode, whether CE mode B is restricted for the UE, or both CE mode A and CE mode B are restricted for the UE, or both CE mode A and CE mode B are not restricted for the UE; or b) when in NB-N1 mode, whether the use of enhanced coverage is restricted or not for the UE. If: a) the use of enhanced coverage is restricted; b) the use of CE mode B is restricted; or c) the use of CE mode A and CE mode B is restricted, the UE shall not use enhanced coverage in the registered PLMN and in any PLMN which is in the list of equivalent PLMNs. If the UE supports CE mode B and the network determines that a) the use of enhanced coverage is not restricted for the UE; or b) CE mode B is not restricted for the UE, the applicable NAS timer values shall be calculated by the network as described in subclause 4.19 and subclause 4.20. For a UE that supports restriction on use of enhanced coverage or CE mode B, if: a) the AMF determines to enforce a change in restriction on the use of enhanced coverage or a change in the restriction on the use of CE mode B as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]; and b) the UE is in 5GMM-CONNECTED mode and there is no ongoing registration procedure, the AMF shall initiate the generic UE configuration update procedure to indicate registration requested and release of the N1 NAS signalling connection not requested as described in subclause 5.4.4. After the successful completion of the registration procedure for mobility registration update including change of the restriction on the use of enhanced coverage, for any SMF with which the UE has an established PDU session, the AMF updates the SMF with the indication on the use of extended NAS timer setting as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. | 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.18 |
4,183 | 4.7.8.4 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure Upon detection of a lower layer failure before the IDENTITY RESPONSE is received, the network shall abort any ongoing GMM procedure. b) Expiry of timer T3370 The identification procedure is supervised by the network by the timer T3370. The network shall, on the first expiry of the timer T3370, retransmit the IDENTITY REQUEST message and reset and restart the timer T3370. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3370, the network shall abort the identification procedure and any ongoing GMM procedure. c) Collision of an identification procedure with a GPRS attach procedure If the network receives an ATTACH REQUEST message before the ongoing identification procedure has been completed and no GPRS attach procedure is pending on the network (i.e. no ATTACH ACCEPT/REJECT message has still to be sent as an answer to an ATTACH REQUEST message), the network shall proceed with the GPRS attach procedure. d) Collision of an identification procedure with a GPRS attach procedure when the identification procedure has been caused by a GPRS attach procedure If the network receives an ATTACH REQUEST message before the ongoing identification procedure has been completed and a GPRS attach procedure is pending (i.e. an ATTACH ACCEPT/REJECT message has to be sent as an answer to an earlier ATTACH REQUEST message), then: - If one or more of the information elements in the ATTACH REQUEST message differs from the ones received within the previous ATTACH REQUEST message, the network shall proceed with the GPRS attach procedure; or - If the information elements do not differ, then the network shall not treat any further this new ATTACH REQUEST. d1) Collision of an identification procedure with an MS initiated GPRS detach procedure GPRS detach containing cause "power off": If the network receives a DETACH REQUEST message before the ongoing identification procedure has been completed, the network shall abort the identification procedure and shall progress the GPRS detach procedure. GPRS detach containing other causes than "power off": If the network receives a DETACH REQUEST message before the ongoing identification procedure has been completed, the network shall complete the identification procedure and shall respond to the GPRS detach procedure as described in subclause 4.7.4. e) Collision of an identification procedure with a routing area updating procedure If the network receives a ROUTING AREA UPDATE REQUEST message before the ongoing identification procedure has been completed, the network shall progress both procedures. f) Collision of an identification procedure with a service request procedure If the network receives a SERVICE REQUEST message before the ongoing identification procedure has been completed, the network shall progress both procedures. Figure 4.7.8/1 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Identification 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.8.4 |
4,184 | 5.2.2.3.3a Request for on demand positioning system information | The UE shall, while SDT procedure is not ongoing: 1> if SIB1 includes si-SchedulingInfo containing posSI-RequestConfigSUL-MSG1-Repetition and criteria to select supplementary uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met and if criteria to apply MSG1 repetition as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1e for the concerned posSI-RequestConfigSUL-MSG1-Repetition is met: 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in posSI-RequestConfigSUL-MSG1-Repetition corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 1> else if the UE is a RedCap UE and if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing posSI-RequestConfigRedCap-MSG1-Repetition and criteria to select normal uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met and if criteria to apply MSG1 repetition as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1e for the concerned posSI-RequestConfigRedCap-MSG1-Repetition is met: 2> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in posSI-RequestConfigRedCap-MSG1-Repetition corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 1> else if SIB1 includes posSI-SchedulingInfo containing posSI-RequestConfigSUL and criteria to select supplementary uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met: 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) in posSI-RequestConfigSUL corresponding to the SI message(s) that the UE upper layers require for positioning operations, and for which posSI-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 1> else if the UE is an (e)RedCap UE and if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if SIB1 includes posSI-SchedulingInfo containing posSI-RequestConfigRedCap and criteria to select normal uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met: 2> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) in posSI-RequestConfigRedCap corresponding to the SI message(s) that the UE upper layers require for positioning operations, and for which posSI-BroadcastStatus is set to notBroadcasting; 2> if acknowledgement for SI request is received from lower layers: 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 1> else: 2> if the UE is not a RedCap UE and if SIB1 includes si-SchedulingInfo containing posSI-RequestConfigMSG1-Repetition and criteria to select normal uplink and to apply MSG1 repetition as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1e for the concerned posSI-RequestConfigMSG1-Repetition are met; or 2> if the UE is a RedCap UE and if initialUplinkBWP-RedCap is not configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing posSI-RequestConfigMSG1-Repetition and criteria to select normal uplink and to apply MSG1 repetition as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1e for the concerned posSI-RequestConfigMSG1-Repetition are met: 3> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in posSI-RequestConfigMSG1-Repetition corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 3> if acknowledgement for SI request is received from lower layers: 4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 2> else if the UE is not an (e)RedCap UE and if SIB1 includes posSI-SchedulingInfo containing posSI-RequestConfig and criteria to select normal uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met; or 2> if the UE is an (e)RedCap UE and if initialUplinkBWP-RedCap is not configured in UplinkConfigCommonSIB and if SIB1 includes posSI-SchedulingInfo containing posSI-RequestConfig and criteria to select normal uplink as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1 is met: 3> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] using the PRACH preamble(s) and PRACH resource(s) in posSI-RequestConfig corresponding to the SI message(s) that the UE upper layers require for positioning operations , and for which posSI-BroadcastStatus is set to notBroadcasting; 3> if acknowledgement for SI request is received from lower layers: 4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 2> else: 3> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1; 3> apply the default MAC Cell Group configuration as specified in 9.2.2; 3> apply the timeAlignmentTimerCommon included in SIB1; 3> apply the CCCH configuration as specified in 9.1.1.2; 3> initiate transmission of the RRCSystemInfoRequest message with rrcPosSystemInfoRequest in accordance with 5.2.2.3.4; 3> if acknowledgement for RRCSystemInfoRequest message with rrcPosSystemInfoRequest is received from lower layers: 4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; 1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers: 2> reset MAC; 2> if SI request is based on RRCSystemInfoRequest message with rrcPosSystemInfoRequest: 3> release RLC entity for SRB0. NOTE: After RACH failure for SI request it is up to UE implementation when to retry the SI request. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.3.3a |
4,185 | – SL-LogicalChannelConfig | The IE SL-LogicalChannelConfig is used to configure the sidelink logical channel parameters. SL-LogicalChannelConfig information element -- ASN1START -- TAG-SL-LOGICALCHANNELCONFIG-START SL-LogicalChannelConfig-r16 ::= SEQUENCE { sl-Priority-r16 INTEGER (1..8), sl-PrioritisedBitRate-r16 ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, kBps512, kBps1024, kBps2048, kBps4096, kBps8192, kBps16384, kBps32768, kBps65536, infinity}, sl-BucketSizeDuration-r16 ENUMERATED {ms5, ms10, ms20, ms50, ms100, ms150, ms300, ms500, ms1000, spare7, spare6, spare5, spare4, spare3,spare2, spare1}, sl-ConfiguredGrantType1Allowed-r16 ENUMERATED {true} OPTIONAL, -- Need R sl-HARQ-FeedbackEnabled-r16 ENUMERATED {enabled, disabled } OPTIONAL, -- Need R sl-AllowedCG-List-r16 SEQUENCE (SIZE (0.. maxNrofCG-SL-1-r16)) OF SL-ConfigIndexCG-r16 OPTIONAL, -- Need R sl-AllowedSCS-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF SubcarrierSpacing OPTIONAL, -- Need R sl-MaxPUSCH-Duration-r16 ENUMERATED {ms0p02, ms0p04, ms0p0625, ms0p125, ms0p25, ms0p5, spare2, spare1} OPTIONAL, -- Need R sl-LogicalChannelGroup-r16 INTEGER (0..maxLCG-ID) OPTIONAL, -- Need R sl-SchedulingRequestId-r16 SchedulingRequestId OPTIONAL, -- Need R sl-LogicalChannelSR-DelayTimerApplied-r16 BOOLEAN OPTIONAL, -- Need R ..., [[ sl-ChannelAccessPriority-r18 INTEGER (1..4) OPTIONAL, -- Need R sl-AllowedCarriers-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) OPTIONAL -- Cond CONNECTED ]] } -- TAG-SL-LOGICALCHANNELCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,186 | 5.2.2.4.5 Actions upon reception of SIB4 | Upon receiving SIB4 the UE shall: 1> if in RRC_IDLE, or in RRC_INACTIVE or in RRC_CONNECTED while T311 is running: 2> for each entry in the interFreqCarrierFreqList: 3> if the UE is neither a RedCap nor an eRedCap UE; or 3> if the UE is a RedCap UE and the interFreqCarrierFreqList-v1700 is absent; or 3> if the UE is an eRedCap UE and the interFreqCarrierFreqList-v1800 is absent; or 3> if the UE is a RedCap UE and redCapAccessAllowed is present in interFreqCarrierFreqList-v1700; or 3> if the UE is an eRedCap UE and eRedCapAccessAllowed is present in interFreqCarrierFreqList-v1800: 4> select the first frequency band in the frequencyBandList (or for aerial UE frequencyBandListAerial), and frequencyBandListSUL, if present, which the UE supports and for which the UE supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxList (or for aerial UE nr-NS-PmaxListAerial), if present: 4> if, the frequency band selected by the UE in frequencyBandList or frequencyBandListAerial to represent a non-serving NR carrier frequency is not a downlink only band: 5> if, for the selected frequency band, the UE supports at least one additionalSpectrumEmission in the nr-NS-PmaxList within the frequencyBandList; or 5> if, for the selected frequency band, the UE supports at least one additionalSpectrumEmission in the nr-NS-PmaxListAerial within the frequencyBandListAerial: 6> if the UE is aerial UE and it supports at least one additionalSpectrumEmission values in nr-NS-PmaxListAerial within the frequencyBandListAerial: 7> apply the first listed additionalSpectrumEmission which it supports among the values included in nr-NS-PmaxListAerial within frequencyBandListAerial; 6> else: 7> apply the first listed additionalSpectrumEmission which it supports among the values included in nr-NS-PmaxList within frequencyBandList; 6> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within nr-NS-PmaxList or nr-NS-PmaxListAerial: 7> apply the additionalPmax; 6> else: 7> apply the p-Max; 6> if frequencyBandListSUL is present in SIB4 and, for the frequency band selected in frequencyBandListSUL, the UE supports at least one additionalSpectrumEmission in the nr-NS-PmaxList within FrequencyBandListSUL: 7> apply the first listed additionalSpectrumEmission which it supports among the values included in nr-NS-PmaxList within frequencyBandListSUL; 7> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within nr-NS-PmaxList: 8> apply the additionalPmax; 7> else: 8> apply the p-Max; 6> else: 7> apply the p-Max; 5> else: 6> apply the p-Max; 1> if in RRC_IDLE or RRC_INACTIVE, and T331 is running: 2> perform the actions as specified in 5.7.8.1a; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.4.5 |
4,187 | 4.22.6.2.3 EPS bearer ID allocation | Based on the signalling flow in Figure 4.11.1.4.1-1, additionally for the MA PDU Session, with the following differences and clarifications: - In step 1, the following procedures and relevant steps are also initiated during the UE Requested MA PDU Session Establishment, the UE Requested PDU Session Establishment with Network Modification to MA PDU Session and the UE or network requested MA PDU Session Modification procedures. - In step 2, if the QoS Flow(s) of the MA PDU Session is established and the MA PDU Session is established over 3GPP access and other existing conditions satisfies EPS interworking, the SMF requests EBI allocation for the QoS Flow(s) of the MA PDU Session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.6.2.3 |
4,188 | 4.11.5.2 Registration procedure | The following impacts are applicable to clause 4.2.2.2 (Registration procedure): - Step 1: If the Registration type is set to "Initial Registration", the UE is not registered in EPS and the UE provides the 5G-GUTI mapped from EPS GUTI as the old GUTI, then the UE includes complete EPS Attach Request in the Registration request message. - Step 4: If the Registration type is "Initial Registration" as in step 1 of the Registration Procedure captured in clause 4.2.2.2.2, the target AMF may perform Identification Request towards MME along with complete EPS Attach Request message for MME to verify it as in step 3 as specified in clause 5.3.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. NOTE 1: The steps above apply to interworking with N26. - Step 14a: - If the AMF does not have event subscription information from the UDM, the AMF indicates it in Nudm_UECM_Registration. The UDM then provides event subscriptions (possibly retrieved from UDR) if any. - If mobility between GERAN/UTRAN and 5GS is required (as specified in clause 5.17.2.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), at Initial Registration, the AMF serving 3GPP access shall also register with the Nudm_UECM_Registration even if the AMF has a valid context. - Step 14d: If mobility between GERAN/UTRAN and 5GS is required (as specified in clause 5.17.2.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), when the UDM stores the associated 3GPP Access Type together with the serving AMF as indicated in step 14a, it will also cause cancellation of any other previously registered serving node (e.g. MME if AMF does not indicate not to cancel or SGSN) via HSS/HLR. NOTE 2: Upon mobility from GERAN/UTRAN to 5GS as specified in clause 5.17.2.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the previously registered SGSN needs to be cancelled from HSS/HLR, otherwise the incoming session can fail. - Step 15: As described in clause 6.3.7.1 , clause TS 23.501[ System architecture for the 5G System (5GS) ] [2], if the AMF receives PCF Selection Assistance info and PCF ID(s) from the UDM, the AMF checks the PCF Selection Assistance info provided by UDM. If a list of DNN,S-NSSAI combinations are provided in the PCF Selection Info the AMF checks local configuration to determine which DNN,S-NSSAI to use then selects the PCF ID included in the corresponding UE Context in the SMF data. If no PCF ID is received, e.g. EPS interworking is not supported, or no PDN connection and related PCC association exists , the AMF select the PCF by considering other criteria, defined in clause 6.3.7.1 TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - At the end of registration procedure, the AMF may initiate synchronization of event subscriptions with the UDM if the AMF does not indicate unavailability of event subscription in step 14a. NOTE 3: The details how synchronization can be done is left to stage 3. For PDU Session via 3GPP access the following impacts are applicable to clause 4.2.2.2 (Registration procedure) when the UE has established PDU Session(s): In clause 4.3.2.2.1 Non-roaming and Roaming with Local Breakout: - Step 17: Additional trigger for step 17 Nsmf_PDUSession_UpdateSMContext are: - If status of interworking with EPS for a PDU session changes, e.g. due to change of 5GMM capability (e.g. "S1 mode supported"), the UE subscription data change (e.g. Core Network Type Restriction to EPC), the AMF invokes Nsmf_PDUSession_UpdateSMContext (EPS Interworking Indication with N26 or without N26) to SMF. The SMF determines whether the PDU session supports interworking with EPS need be changed. If it needs to be changed, the SMF invokes Nudm_UECM_Update service operation to add or remove the PGW-C FQDN for S5/S8 interface from the UE context in SMF data stored at the UDM. For interworking with the N26 interface, if status of interworking with EPS for a PDU session is changed at SMF+PGW-C, the SMF+PGW-C invokes EBI allocation or revocation as described in clause 4.11.1.4.1 and clause 4.11.1.4.2 respectively. For PDU Session via non-3GPP access, the AMF determines if EPS interworking is supported and sends the indication to the SMF in the same way as for PDU Session via 3GPP access. The SMF makes the final decision on the EPS interworking in the same way as for PDU Session via 3GPP access with the following modification: If the SMF does not receive the interworking indication, the SMF makes its decision based on subscription. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.5.2 |
4,189 | 21.2.2 Format of HA-APN Network Identifier | The HA-APN Network Identifier follows the format defined for APNs in clause 9.1.1. In addition to what has been defined in clause 9.1.1 the HA-APN Network Identifier shall not contain "ha-apn." or "w-apn." and not end in ".3gppnetwork.org". A HA-APN Network Identifier may be used to access a service associated with a HA. This may be achieved by defining: - a HA-APN which corresponds to a FQDN of a HA, and which is locally interpreted by the HA as a request for a specific service, or - a HA-APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or a HA-APN Network Identifier consisting of a Reserved Service Label alone, which indicates a HA by the nature of the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed between operators who have roaming agreements. As an example, the HA-APN for MCC 345 and MNC 12 is coded in the DNS as: "internet.ha-apn.mnc012.mcc345.pub.3gppnetwork.org". where "internet" is the HA-APN Network Identifier and "mnc012.mcc345.pub.3gppnetwork.org " is the HA-APN Operator Identifier. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 21.2.2 |
4,190 | 11.2.1 Timer T3240 and Timer T3241 | Timer T3240 is started in the mobile station when: - the mobile station receives a LOCATION UPDATING ACCEPT message completing a location updating procedure in the cases specified in subclauses 4.4.4.6 and 4.4.4.8; - the mobile station receives a LOCATION UPDATING REJECT message in the cases specified in subclause 4.4.4.7; - the mobile station has sent a CM SERVICE ABORT message as specified in subclause 4.5.1.7; - the mobile station has released or aborted all MM connections in the cases specified in 4.3.2.5, 4.3.5.2, 4.5.1.1, and 4.5.3.1; - the mobile station receives the paging message from network and enter the MM state 9 (WAIT FOR NETWORK COMMAND). Timer T3240 is stopped, reset, and started again at receipt of an MM message. Timer T3240 is stopped and reset (but not started) at receipt of a CM message that initiates establishment of an CM connection (an appropriate SETUP, REGISTER, or CP-DATA message as defined in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] , 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21] or 3GPP TS 24.011[ Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface ] [22]). If timer T3240 expires, the MS shall abort the RR connection and enter the MM state MM IDLE. Timer T3241 is started in the mobile station when entering MM state RR CONNECTION RELEASE NOT ALLOWED. Timer T3241 is stopped and reset (but not started) when the MM state RR CONNECTION RELEASE NOT ALLOWED is left. If timer T3241 expires, the MS shall abort the RR connection and enter the MM state MM IDLE. | 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 | 11.2.1 |
4,191 | 5.8.10.4.2 Event S1 (Serving becomes better than threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition S1-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition S1-2, as specified below, is fulfilled; 1> for this NR sidelink measurement, consider the NR sidelink frequency corresponding to the associated sl-MeasObject associated with this event. Inequality S1-1 (Entering condition) Ms – Hys > Thresh Inequality S1-2 (Leaving condition) Ms + Hys < Thresh The variables in the formula are defined as follows: Ms is the NR sidelink measurement result of the NR sidelink frequency, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. sl-Hysteresis as defined within sl-ReportConfig for this event). Thresh is the threshold parameter for this event (i.e. s1-Threshold as defined within sl-ReportConfig for this event). Ms is expressed in dBm in case of RSRP. Hys is expressed in dB. Thresh is expressed in the same unit as Ms. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.4.2 |
4,192 | 5.19.3 MME/SGSN or HSS initiated Dedicated Core Network Reselection | If DCNs are deployed, this procedure is used by the HSS to update (i.e. add, modify or delete) the UE Usage Type subscription parameter in the serving node. This procedure may result in change of serving node of the UE. This procedure may also be used for MME/SGSN initiated serving node change for UEs, e.g. when configuration about the UE Usage Types served by MME/SGSN is changed. This procedure may also be used after a handover procedure by the target MME/SGSN to redirect a UE to a serving node of another DCN. If UE assisted DCN selection feature is supported by the Core Network, the UE is provided with the new DCN-ID. The subscription change may be applied to a large number of UEs and similar considerations as in the case of MME/SGSN rebalancing specified in clause 4.3.7.3 should be applied to avoid sudden redirection of UEs that could overload the core network nodes (and possibly the RAN if paging is needed). Figure 5.19.3-1: MME/SGSN or HSS Initiated Dedicated Core Network Reselection Steps 1 and 2 apply for HSS initiated Dedicated Core Network Reselection procedure only. 1. The HSS sends an Insert Subscriber Data Request (IMSI, Subscription Data) message to the MME/SGSN. The Subscription Data includes UE Usage Type information or UE Usage Type withdrawal information. NOTE 1: If the UE Usage Type subscription change or withdrawal needs to be applied for a large number of subscribers, the HSS should stagger the insertion of subscription changes to serving nodes, e.g. based on OAM. 2. The MME/SGSN updates the stored Subscription Data and acknowledges the Insert Subscriber Data Request message by returning an Insert Subscriber Data Answer (IMSI) message to the HSS. The procedure ends if the MME/SGSN can continue to serve the UE. 3. If the MME/SGSN decides to transfer the UE immediately to another CN or if the MME/SGSN determines that DCN-ID immediately needs to be updated and the UE is in idle-mode, the MME/SGSN pages the UE. Alternatively the MME waits until the UE becomes active. If MME/SGSN decides to transfer the UE to another CN either Steps 4 through 7 or Step 8 occur. Steps 4 through 7 occur if the UE is already in connected mode or UE enters connected mode by initiating data transfer. Step 8 occurs if the UE is in idle mode and performs a TAU/RAU procedure. If the MME/SGSN determines that only DCN-ID shall be updated in the UE (i.e. serving CN node is kept) only step 4 and 5 occurs. 4. Either triggered by the paging or by uplink data the UE initiates NAS connection establishment. Alternatively the UE initiates NAS connection establishment by sending a TAU/RAU Request. 5. When a NAS connection already exists or when a NAS connection is established for initiating data transfer, the MME/SGSN triggers the GUTI Reallocation/P-TMSI Reallocation procedure. If DCN-ID is available and the MME/SGSN determines that the UE shall be updated with a new DCN-ID, the new DCN-ID shall be included in the GUTI Reallocation Command/P-TMSI Reallocation Command. If the MME/SGSN determines that a CN node re-selection needs to be performed, a non-broadcast TAI/RAI shall be included. 6. The MME/SGSN releases RAN resources and UE is moved to idle mode. NOTE 2: If a large number of UEs need to be offloaded the MME/SGSN should not release RAN resources for all UEs immediately to avoid sudden redirection of UEs that could overload the core network nodes (and possibly the RAN if paging is needed). The MME/SGSN should wait until the release is performed due to inactivity. 7. The non-broadcast TAI/RAI triggers the UE to immediately start the TAU/RAU procedure. If available, the new DCN-ID shall be sent from the UE to the RAN. The MME/SGSN receives the TAU/RAU Request message. 8. The UE performs a TAU/RAU request. The MME/SGSN receives the TAU/RAU Request message. 9. If the UE Usage Type for the UE has been added or modified and if it is not served by the MME/SGSN, or if the UE Usage Type has been withdrawn from the HSS subscription data and subscriptions without UE Usage Type are not served by the MME/SGSN, the MME/SGSN triggers the NAS Message redirection procedure of clause 5.19.1 to redirect the UE. This is followed by step 7 of clause 5.19.2 where the TAU/RAU procedure completes at the MME of the selected DCN. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.19.3 |
4,193 | 5.15.11.3.1 VPLMN NSAC Admission Mode | For NSAC of roaming UEs for maximum number of UEs per network slice and/or maximum number of PDU Sessions per network slice managed by the VPLMN, the following principles shall be used: - For NSAC for the maximum number of UEs for S-NSSAI of the HPLMN, a NSACF in the VPLMN can be configured with the maximum number of allowed roaming UEs per mapped S-NSSAI of the HPLMN for a S-NSSAI of the HPLMN that is subject to NSAC. In such a case, the AMFs trigger a request to a NSACF of the VPLMN. - For NSAC for the maximum number of PDU Sessions for S-NSSAI of the HPLMN, a NSACF in the VPLMN can be configured with the maximum number of allowed PDU Sessions in LBO mode per mapped S-NSSAI of the HPLMN for a S-NSSAI of the HPLMN that is subject to NSAC. In such a case, the anchor SMF in the VPLMN triggers a request to a NSACF of the VPLMN. - For NSAC for the maximum number of UEs for S-NSSAI of the VPLMN, AMFs trigger a request to a NSACF of the VPLMN to perform NSAC based on the S-NSSAI of the VPLMN subject to NSAC. The NSACF of the HPLMN is not involved. - For NSAC for the maximum number of PDU Sessions for S-NSSAI of the VPLMN in the LBO roaming case, the SMF triggers a request to a NSACF of the VPLMN to perform NSAC based on the S-NSSAI of the VPLMN subject to NSAC. The NSACF of the HPLMN is not involved. ‐ The AMF or SMF (in LBO roaming case) in the VPLMN provides both the S-NSSAI in the VPLMN and the corresponding mapped S-NSSAI in the HPLMN to the NSACF in the VPLMN. The NSACF in the VPLMN performs NSAC for both S-NSSAI of the VPLMN and the corresponding mapped S-NSSAI of the HPLMN based on the SLA between the VPLMN and the HPLMN. In addition to configuring the VPLMN NFs with the maximum number of allowed roaming UEs per mapped S-NSSAI of the HPLMN subject to NSAC, and the maximum number of allowed PDU Sessions in LBO mode per mapped S-NSSAI of the HPLMN subject to NSAC, the VPLMN can optionally fetch this information from the HPLMN primary NSACF in a hierarchal architecture or centralized NSACF in a centralized architecture. If the NSACF in VPLMN does not have quota configured but can receive quota from the HPLMN, the NSACF in VPLMN may interact with the HPLMN for retrieving the quota before processing any incoming request. The VPLMN is either configured or discovers the NSACF in the HPLMN for quota retrieval. However, in this case, the VPLMN rejects any additional requests exceeding the received information. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.3.1 |
4,194 | 10.5.5.6 DRX parameter | The purpose of the DRX parameter information element is to indicate whether the MS uses DRX mode or not. The DRX parameter is a type 3 information element with a length of 3 octets. The value part of a DRX parameter information element is coded as shown in table 10.5.139/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.122/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : DRX parameter information element Table 10.5.139/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : DRX parameter information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.6 |
4,195 | 6.2.4 MAC header for SL-SCH | The MAC header is of variable size and consists of the following fields: - V: The MAC PDU format version number field indicates which version of the SL-SCH subheader is used. In this version of the specification three format versions are defined, and this field shall therefore be set to "0001", "0010", and "0011". If the DST field is 24 bits this field shall be set to "0011". The V field size is 4 bits; - SRC: The Source Layer-2 ID field carries the identity of the source. It is set to the ProSe UE ID. The SRC field size is 24 bits; - DST: The DST field can be 16 bits or 24 bits. If it is 16 bits, it carries the 16 most significant bits of the Destination Layer-2 ID. If it is 24 bits, it is set to the Destination Layer-2 ID. For sidelink communication, the Destination Layer-2 ID is set to the ProSe Layer-2 Group ID or Prose UE ID. For V2X sidelink communication, the Destination Layer-2 ID is set to the identifier provided by upper layers as defined in TS 23.285[ Architecture enhancements for V2X services ] [14]. If the V field is set to "0001", this identifier is a groupcast identifier. If the V field is set to "0010", this identifier is a unicast identifier; - LCID: The Logical Channel ID field uniquely identifies the logical channel instance within the scope of one Source Layer-2 ID and Destination Layer-2 ID pair of the corresponding MAC SDU or padding as described in table 6.2.4-1. There is one LCID field for each MAC SDU or padding included in the MAC PDU. In addition to that, one or two additional LCID fields are included in the MAC PDU, when single-byte or two-byte padding is required but cannot be achieved by padding at the end of the MAC PDU. The values of LCID from "01011" to "10100" identify the logical channels used to send duplicated RLC SDUs from logical channels of which the values of LCID from "00001" to "01010" respectively in sequential order. The LCID field size is 5 bits; - L: The Length field indicates the length of the corresponding MAC SDU in bytes. There is one L field per MAC PDU subheader except for the last subheader. The size of the L field is indicated by the F field; - F: The Format field indicates the size of the Length field as indicated in table 6.2.4-2. There is one F field per MAC PDU subheader except for the last subheader. The size of the F field is 1 bit. If the size of the MAC SDU is less than 128 bytes, the value of the F field is set to 0, otherwise it is set to 1; - E: The Extension field is a flag indicating if more fields are present in the MAC header or not. The E field is set to "1" to indicate another set of at least R/R/E/LCID fields. The E field is set to "0" to indicate that either a MAC SDU or padding starts at the next byte; - R: Reserved bit, set to "0". The MAC header and subheaders are octet aligned. Table 6.2.4-1 Values of LCID for SL-SCH Table 6.2.4-2 Values of F field: | 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.2.4 |
4,196 | 8.3.2.3 Dual-Layer Spatial Multiplexing (with multiple CSI-RS configurations) | For dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.3.2.3-2, with the addition of the parameters in Table 8.3.2.3-1 where Cell 1 is the serving cell and Cell 2 is the interfering cell. The downlink physical channel setup is set according to Annex C.3.2. The purpose of these tests is to verify the rank-2 performance for full RB allocation, to verify rate matching with multiple CSI reference symbol configurations with non-zero and zero transmission power, and to verify that the UE correctly estimate SNR. Table 8.3.2.3-1: Test Parameters for Testing CDM-multiplexed DM RS (dual layer) with multiple CSI-RS configurations Table 8.3.2.3-2: Minimum performance for CDM-multiplexed DM RS (FRC) with multiple CSI-RS configurations | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.2.3 |
4,197 | 7.7.3.2 Conditional IE errors | When upon receipt of a 5GMM or 5GSM message the UE diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error for the contents of a Type 6 IE container information element, or when it receives a 5GMM or 5GSM message with a Type 6 IE container information element containing at least one syntactically incorrect conditional IE, the UE shall ignore the message and shall return a status message (5GMM STATUS or 5GSM STATUS depending on the EPD) with cause #100 "conditional IE error". When the network receives a message and diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error for the contents of a Type 6 IE container information element or when it receives a message with a Type 6 IE container information element containing at least one syntactically incorrect conditional IE, the network shall either: a) try to treat the message (the exact further actions are implementation dependent); or b) ignore the message except that it should return a status message (5GMM STATUS or 5GSM STATUS depending on the EPD) with cause #100 "conditional IE error". | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.7.3.2 |
4,198 | 4.11.4.3.7 5GC NAS capability (re-)enabled and disabled | When 5G NAS (i.e. N1 mode) capability is (re-)enabled, the UE does not report the UE capability change to ePDG. NOTE: The ePDG is not aware of the N1 mode Enabled / Disabled status at the UE. If a standalone PGW was previously selected, the ePDG is not able to initiate PDN disconnection with reactivation required for the purpose of re-selecting an SMF+PGW-C. When N1 is re-enabled, how to handle PDN connection(s) established over EPC/ePDG and without a mapped S-NSSAI is defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.4.3.7 |
4,199 | 6.4.2.2 UE-requested PDU session modification procedure initiation | In order to initiate the UE-requested PDU session modification procedure, the UE shall create a PDU SESSION MODIFICATION REQUEST message. The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION MODIFICATION REQUEST message to the allocated PTI value. The UE shall not perform the UE-requested PDU session modification procedure for an emergency PDU session, except for a procedure initiated according to subclause 6.4.2.1, item e) only, and for the error cases described in subclause 6.4.1.3 and subclause 6.3.2.3. The UE shall not perform the UE-requested PDU session modification procedure for a PDU session for LADN when the UE is located outside the LADN service area except for indicating a change of 3GPP PS data off UE status. If the UE requests a specific QoS handling and the PDU session is not associated with the control plane only indication, the UE shall include the Requested QoS rules IE indicating requested QoS rules or the Requested QoS flow descriptions IE indicating requested QoS flow descriptions or both for the specific QoS handling. The Requested QoS rules IE includes the packet filters which describe the service data flows requested by the UE. The specific QoS parameters requested by the UE are specified in the Requested QoS flow descriptions IE. If the UE requests the network to bind specific service data flows to a dedicated QoS flow, the UE shall create a new QoS rule by setting the rule operation code to "Create new QoS rule" and shall set the segregation bit to "Segregation requested" for the corresponding QoS rule in the Requested QoS rules IE. The UE shall set the QRI values to "no QoS rule identifier assigned" in the Requested QoS rules IE, if the QoS rules are newly created; otherwise, the UE shall set the QRI values to those of the existing QoS rules for which the specific QoS handling applies. The UE shall set the QFI values to "no QoS flow identifier assigned" in the Requested QoS flow descriptions IE, if the QoS flow descriptions are newly created; otherwise, the UE shall set the QFI values to the QFIs of the existing QoS flow descriptions for which the specific QoS handling applies. The UE shall not request to create more than one QoS flow in a UE-requested PDU session modification procedure. If the SMF receives a PDU SESSION MODIFICATION REQUEST message with a Requested QoS rules IE containing more than one QoS rule with the rule operation code set to "Create new QoS rule", the SMF shall assign the same QFI to all the QoS rules which are created. If the UE requests to join or leave one or more multicast MBS sessions associated with a PDU session, the UE shall include the Requested MBS container IE in the PDU SESSION MODIFICATION REQUEST message and shall set the MBS operation to "Join multicast MBS session" for the join case or to "Leave MBS session" for the leave case. The UE shall include the multicast MBS session information(s) and shall set the Type of multicast MBS session ID for each of the multicast MBS session information to either "Temporary Mobile Group Identity (TMGI)" or "Source specific IP multicast address" depending on the type of the multicast MBS session ID available in the UE. Then the remaining values of each of the multicast MBS session informations shall be set as following: a) if the Type of multicast MBS session ID is set to "Temporary Mobile Group Identity (TMGI)", the UE shall set the multicast MBS session ID to the TMGI; or b) if the Type of multicast MBS session ID is set to "Source specific IP multicast address for IPv4" or " Source specific IP multicast address for IPv6", the UE shall set the Source IP address information and the Destination IP address information to the corresponding values. The UE should not request to join a multicast MBS session for local MBS service if neither current TAI nor CGI of the current cell is part of the MBS service area(s) of the multicast MBS session, if the UE has valid information of the MBS service area(s) of the multicast MBS session. NOTE 1: The UE obtains the details of the multicast MBS session ID(s) e.g,TMGI, Source IP address information and Destination IP address information as a pre-configuration in the UE or during the MBS service announcement which is out of scope of this specification. Pre-configuration can be provided in one or more of the following ways: a) in a UE implementation-specific way (e.g. factory configuration); b) in the USIM (see EF5MBSUECONFIG file in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]); or c) in the UE pre-configuration MO for MBS (see 3GPP TS 24.575[ 5G System; Multicast/Broadcast UE pre-configuration Management Object (MO) ] [65]). For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is of "IPv4", "IPv6", "IPv4v6", or "Ethernet" PDU session type, the PDU session is not associated with the control plane only indication: a) the UE is performing the PDU session modification procedure to indicate the support of reflective QoS and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication, the UE shall set the RQoS bit to "Reflective QoS supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; or b) the UE is performing the PDU session modification procedure to indicate that reflective QoS is not supported and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication, the UE shall set the RQoS bit to "Reflective QoS not supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message. If the UE is performing the PDU session modification procedure to revoke the previously indicated support of reflective QoS and the PDU session is not associated with the control plane only indication, the UE shall set the RQoS bit to "Reflective QoS not supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message. The UE shall not indicate support for reflective QoS for this PDU Session for the remaining lifetime of the PDU Session. NOTE 2: The determination to revoke the usage of reflective QoS by the UE for a PDU session is implementation dependent. For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is of "IPv6" or "IPv4v6" PDU session type, the PDU session is not associated with the control plane only indication: a) the UE is performing the PDU session modification procedure to indicate the support of Multi-homed IPv6 PDU session and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication, the UE shall set the MH6-PDU bit to "Multi-homed IPv6 PDU session supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; or b) the UE is performing the PDU session modification procedure to indicate that Multi-homed IPv6 PDU session is not supported and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication, the UE shall set the MH6-PDU bit to "Multi-homed IPv6 PDU session not supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message. For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is of "IPv4", "IPv6", "IPv4v6", or "Ethernet" PDU session type, the PDU session is not associated with the control plane only indication, the UE supports more than 16 packet filters for this PDU session, and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication, the UE shall indicate the maximum number of packet filters supported for the PDU session in the Maximum number of supported packet filters IE of the PDU SESSION MODIFICATION REQUEST message. For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is not associated with the control plane only indication, and the UE has not previously successfully performed the UE-requested PDU session modification to include the Integrity protection maximum data rate IE in the PDU SESSION MODIFICATION REQUEST message, the UE shall include the Integrity protection maximum data rate IE in the PDU SESSION MODIFICATION REQUEST message. If the UE is performing the PDU session modification procedure a) to request the deletion of a non-default QoS rule due to errors in QoS operations or packet filters; b) to request the deletion of a QoS flow description due to errors in QoS operations; or c) to request the deletion of a mapped EPS bearer context due to errors in mapped EPS bearer operation, TFT operation or packet filters, the UE shall include the 5GSM cause IE in the PDU SESSION MODIFICATION REQUEST message as described in subclauses 6.3.2.3, 6.3.2.4 and 6.4.1.3. When the UE-requested PDU session modification procedure is used to indicate a change of 3GPP PS data off UE status for a PDU session, the UE shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION REQUEST message and setting the 3GPP PS data off UE status. For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is not associated with the control plane only indication, the UE requests the PDU session to be an always-on PDU session in the 5GS and the UE has not previously successfully performed the UE-requested PDU session modification to request this, the UE shall include the Always-on PDU session requested IE and set the value of the IE to "Always-on PDU session requested" in the PDU SESSION MODIFICATION REQUEST message. If a port management information container needs to be delivered (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]), the UE shall include a Port management information container IE in the PDU SESSION MODIFICATION REQUEST message. To request re-negotiation of IP header compression configuration, the UE shall include the IP header compression configuration IE in the PDU SESSION MODIFICATION REQUEST message if the network indicated "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature support IE. To request re-negotiation of Ethernet header compression configuration, the UE shall include the Ethernet header compression configuration IE in the PDU SESSION MODIFICATION REQUEST message if the network indicated "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature support IE. After an inter-system change from S1 mode to N1 mode, if: a) the UE is operating in single-registration mode in the network supporting N26 interface; b) the PDU session type value of the PDU session type IE is set to "IPv4", "IPv6" or "IPv4v6"; c) the UE indicates "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and d) the network indicates "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature IE of the REGISTRATION ACCEPT message; the UE shall initiate the PDU session modification procedure to negotiate the IP header compression configuration and include the IP header compression configuration IE in the PDU SESSION MODIFICATION REQUEST message. The UE shall include the Service-level-AA container IE in the PDU SESSION MODIFICATION REQUEST message, when requesting to modify an established PDU session for C2 communication. In the Service-level-AA container IE, the UE shall include: a) the service-level device ID with the value set to the CAA-level UAV ID of the UE; and b) if available, the service-level-AA payload with the value set to the C2 authorization payload and the service-level-AA payload type with the value set to "C2 authorization payload". NOTE 3: The C2 authorization payload in the service-level-AA payload can include one, some or all of the pairing information for C2 communication, an indication of the request for direct C2 communication, pairing information for direct C2 communication, and the UAV flight authorization information. The UE may include the Non-3GPP delay budget IE in the PDU SESSION MODIFICATION REQUEST message, when requesting to modify an established PDU session for PIN-DN communication or PIN indirect commmunication. NOTE 3A: The Non-3GPP delay budget IE can assist the network in providing specific QoS handling for a set of packet filter(s) for the PDU session as specified in subclause 5.44.3.4 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. After an inter-system change from S1 mode to N1 mode, if: a) the UE is operating in single-registration mode in a network that supports N26 interface; b) the PDU session type value of the PDU session type IE is set to "Ethernet"; c) the UE indicates "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and d) the network indicates "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature IE of the REGISTRATION ACCEPT message; the UE shall initiate the PDU session modification procedure to negotiate the Ethernet header compression configuration and include the Ethernet header compression configuration IE in the PDU SESSION MODIFICATION REQUEST message. For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, and if the UE is a UE operating in single-registration mode in a network supporting N26 interface, and the UE supports receiving DNS server addresses in protocol configuration options and the UE has not previously successfully performed the UE-requested PDU session modification to indicate this support, the UE shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION REQUEST message and: a) if the PDU session is of "IPv4" or "IPv4v6" PDU session type, the UE shall include the DNS server IPv4 address request; and b) if the PDU session is of "IPv6" or "IPv4v6" PDU session type, the UE shall include the DNS server IPv6 address request. For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, and if the UE is a UE operating in single-registration mode in a network supporting N26 interface, and the UE supports the EAS rediscovery and the UE has not previously successfully performed the UE-requested PDU session modification to indicate this support, the UE shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION REQUEST message and shall include the EAS rediscovery support indication in the Extended protocol configuration options IE. For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, and if the UE is a UE operating in single-registration mode in a network supporting N26 interface, and the UE supports the EDC and the UE has not previously successfully performed the UE-requested PDU session modification to indicate this support, then the UE shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION REQUEST message and shall include the EDC support indicator in the Extended protocol configuration options IE. If the UE supports reporting of URSP rule enforcement and is indicated to send URSP rule enforcement report to network based on the matching URSP rule which contains the URSP rule enforcement report indication set to "URSP rule enforcement report is required", the UE shall include connection capabilities in the PDU SESSION MODIFICATION REQUEST message. Editor’s note [CR#5362, eUEPO]: How to include connection capabilities in the the PDU SESSION MODIFICATION REQUEST message is FFS. The UE shall transport: a) the PDU SESSION MODIFICATION REQUEST message; b) the PDU session ID; and c) if the UE-requested PDU session modification: 1) is not initiated to indicate a change of 3GPP PS data off UE status associated to a PDU session, then the request type set to "modification request"; and 2) is initiated to indicate a change of 3GPP PS data off UE status associated to a PDU session, then without transporting the request type; using the NAS transport procedure as specified in subclause 5.4.5, and the UE shall start timer T3581 (see example in figure 6.4.2.2.1). For a PDN connection established when in S1 mode and not associated with the control plane only indication, after inter-system change from S1 mode to N1 mode, if the UE is registered in a network supporting the ATSSS, a) the UE may request to modify a PDU session to an MA PDU session; or b) the UE may allow the network to upgrade the PDU session to an MA PDU session. In order for the UE to allow the network to upgrade the PDU session to an MA PDU session, the UE shall set "MA PDU session network upgrade is allowed" in the MA PDU session information IE and set the request type to "modification request" in the UL NAS TRANSPORT message. NOTE 4: If the DNN corresponds to an LADN DNN, the AMF does not forward the MA PDU session information IE to the SMF but sends the message back to the UE to inform of the unhandled request (see subclause 5.4.5.2.5). In case the UE executes case a) or b): 1) if the UE supports ATSSS Low-Layer functionality with any steering mode (i.e., any steering mode allowed for ATSSS Low-Layer functionality) as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "ATSSS Low-Layer functionality with any steering mode allowed for ATSSS-LL supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; NOTE 5: The ATSSS Low-Layer functionality cannot be used together with the redundant steering mode. When the UE indicates that it is capable of supporting the ATSSS Low-Layer functionality with any steering mode, it implies that the UE supports the ATSSS Low-Layer functionality with any steering mode except the redundant steering mode. 2) if the UE supports MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; 3) if the UE supports MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality)as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; 4) if a performance measurement function in the UE can perform access performance measurements using the QoS flow of the non-default QoS rule as specified in subclause 5.32.5 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the APMQF bit to "Access performance measurements per QoS flow supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; 5) if the UE supports MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; 6) if the UE supports MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality) as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; 7) if the UE supports MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; and 8) if the UE supports MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality) as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message. Upon receipt of a PDU SESSION MODIFICATION REQUEST message for MA PDU session modification, the SMF shall check if the 5GSM capability IE in the PDU SESSION MODIFICATION REQUEST message, includes: a) the ATSSS-ST bits set to "MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" and: i) if the DNN configuration allows for the MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the modified PDU session has the capability of MPTCP with any steering mode and ATSSS-LL with any steering mode in the downlink and MPTCP with any steering mode and ATSSS-LL with only active-standby steering mode in the uplink; or ii) if the DNN configuration allows for the MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode, the SMF shall ensure that the modified PDU session has the capability of MPTCP with any steering mode and ATSSS-LL with only active-standby steering mode in the downlink and the uplink; b) the ATSSS-ST bits set to "MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" and: i) if the DNN configuration allows for the MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the modified PDU session has the capability of MPQUIC with any steering mode and ATSSS-LL with any steering mode in the downlink and MPQUIC with any steering mode and ATSSS-LL with only active-standby steering mode in the uplink; or ii) if the DNN configuration allows for the MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode, the SMF shall ensure that the modified PDU session has the capability of MPQUIC with any steering mode and ATSSS-LL with only active-standby steering mode in the downlink and the uplink; c) the ATSSS-ST bits set to "MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" and if the DNN configuration allows for the MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the modified PDU session has the capability of MPQUIC with any steering mode and ATSSS-LL with any steering mode in the downlink and the uplink; d) the ATSSS-ST bits set to "ATSSS Low-Layer functionality with any steering mode allowed for ATSSS-LL supported" and if the DNN configuration allows for the ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the modified PDU session has the capability of ATSSS-LL with any steering mode in the downlink and the uplink; e) the ATSSS-ST bits set to "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" and if the DNN configuration allows for the MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode, the SMF shall ensure that the modified PDU session has the capability of MPTCP with any steering mode and ATSSS-LL with any steering mode in the downlink and the uplink; f) the ATSSS-ST bits set to "MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" and if the DNN configuration allows for the MPTCP functionality with any steering mode, the MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the modified PDU session has the capability of MPTCP with any steering mode, the MPQUIC with any steering mode and ATSSS-LL with any steering mode in the downlink and the uplink; or g) the ATSSS-ST bits set to "MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby mode supported" and i) if the DNN configuration allows for the MPTCP functionality with any steering mode, the MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the modified PDU session has the capability of MPTCP with any steering mode, MPQUIC with any steering mode and ATSSS-LL with any steering mode in the downlink and MPTCP with any steering mode, MPQUIC with steering mode and ATSSS-LL with only active-standby steering mode in the uplink; or ii) if the DNN configuration allows for the MPTCP functionality with any steering mode, the MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode, the SMF shall ensure that the modified PDU session has the capability of MPTCP with any steering mode, MPQUIC with any steering mode and ATSSS-LL with only active-standby steering mode in the downlink and the uplink. Figure 6.4.2.2.1: UE-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.2.2 |
4,200 | 4.2.11.5.2 Network Slice Admission Control Support for Roaming by HPLMN | 4.2.11.5.2.1 General For maximum number of UEs in roaming case, there are two types of NSAC admission modes requiring interaction with HPLMN for inbound roamers; VPLMN with HPLMN assistance NSAC admission mode or HPLMN NSAC admission mode. For PDU sessions in the home-routed roaming case, the SMF in HPLMN performs NSAC for the S-NSSAI(s) subject to NSAC. For LBO PDU sessions, there are two types of NSAC admission mode requiring interaction with HPLMN for LBO PDU sessions; VPLMN with HPLMN assistance NSAC admission mode or HPLMN NSAC admission mode. 4.2.11.5.2.2 VPLMN with HPLMN assistance NSAC admission mode For inbound roamers, depending on the NSAC architecture deployed in the VPLMN, enforcement for the maximum number of registered UEs with an S-NSSAI is done in the VPLMN by an NSACF in the VPLMN per the procedure described in clause 4.2.11.2 or 4.2.11.2a with the following differences: - The AMF verifies the applicable NSAC admission mode for the inbound roamer based on the subscription data from UDM. - When the AMF invokes the Nnsacf_NSAC_NumOfUEsUpdate_Request service operation with the NSACF in the VPLMN, the AMF provides in the Request the additional NSAC admission mode parameter, i.e. VPLMN with HPLMN assistance NSAC admission mode. - If the maximum number of UEs is not available or the maximum number of UEs has been reached at the Primary (or Central) NSACF of the VPLMN and the type of NSAC admission mode is VPLMN with HPLMN assistance NSAC admission mode, the following is performed: - The Primary (or Central) NSACF in the VPLMN invokes Nnsacf_NSAC_NumOfUEsUpdate_Request to the Primary (or central) NSACF in the HPLMN for NSAC delegation and to receive an initial or a new allocated maximum number of UEs for the mapped S-NSSAI in HPLMN for inbound roamers. The request includes mapped S-NSSAI in HPLMN, PLMN ID and NSAC admission mode. - The Primary (or central) NSACF in HPLMN provides Nnsacf_NSAC_NumOfUEsUpdate_Response message to the Primary (or Central) NSACF of VPLMN. The response message includes mapped S-NSSAI in HPLMN, the new allocated maximum number of UEs for the mapped S-NSSAI in HPLMN for inbound roamers. Alternatively, the Primary (or central) NSACF rejects the request for the NSAC delegation. - The Primary (or central) NSACF in VPLMN updates the previous stored maximum number of UEs based on the new received allocated maximum UEs number. - At any time, the Primary (or central) NSACF in HPLMN may trigger Nnsacf_NSAC_LocalNumberUpdate Request message to the Primary (or central) NSAC in VPLMN to provide an updated maximum number of registered UEs for the mapped S-NSSAI in HPLMN for inbound roamers. Based on the updated maximum UEs number of the S-NSSAI, where applicable, the Primary NSACF in VPLMN may further perform distribution of local maximum UEs number to the NSACFs it interacts with. For more detail refer to clause 4.2.11.6. The complete procedure of the VPLMN with HPLMN assistance NSAC admission mode for number of registered UEs is described in clause 4.2.11.5.2.3. For LBO PDU sessions, depending on the NSAC architecture deployed in the VPLMN, enforcement for the maximum number of LBO PDU sessions established for an S-NSSAI is performed by the NSACF in the VPLMN per the procedure described in clause 4.2.11.4 or 4.2.11.4a with the following differences: - The SMF verifies the applicable NSAC admission mode for the S-NSSAI PDU session associated with the inbound roamer based on the subscription data from UDM. - When the SMF invokes the Nnsacf_NSAC_NumOfPDUsUpdate_Request service operation to the NSACF in the VPLMN, the SMF provides in the Request the additional NSAC admission mode parameter, i.e. VPLMN with HPLMN assistance NSAC admission mode. - If the maximum number of PDU Session is not available or the maximum number of PDU Sessions has been reached at the Primary (or Central) NSACF of the VPLMN and the type of NSAC admission mode is VPLMN with HPLMN assistance NSAC admission mode, the following is performed: - The Primary (or Central) NSACF in the VPLMN invokes Nnsacf_NSAC_NumOfPDUsUpdate_Request to the Primary (or central) NSACF in the HPLMN for the NSAC delegation and to receive an initial or a new allocated maximum number of LBO PDU Sessions for the mapped S-NSSAI in HPLMN for inbound roamers. The request includes mapped S-NSSAI in HPLMN, PLMN ID and NSAC admission mode. - The Primary (or central) NSACF in HPLMN provides the Nnsacf_NSAC_NumOfPDUsUpdate_Response message to the Primary NSACF of VPLMN. The response message includes mapped S-NSSAI in HPLMN, the allocated maximum number of LBO PDU Sessions for the mapped S-NSSAI in HPLMN for inbound roamers. Alternatively, the Primary (or central) NSACF rejects the request for the NSAC delegation. - The Primary (or central) NSACF in VPLMN updates the previous stored maximum number of PDU Sessions based on the new received allocated maximum number of LBO PDU Sessions. - At any time, the Primary (or central) NSACF in HPLMN may trigger Nnsacf_NSAC_LocalNumberUpdate Request message to the Primary (or central) NSAC in VPLMN to provide an updated new allocated maximum number of LBO PDU Sessions for the mapped S-NSSAI in HPLMN for the roaming UEs. Based on the updated maximum number of LBO PDU Sessions number of the S-NSSAI, where applicable, the Primary NSACF in VPLMN may further perform distribution of local maximum PDU Sessions number to the NSACFs it contacts. For more detail refer to clause 4.2.11.6. The complete procedure for the VPLMN with HPLMN assistance NSAC Admission mode for number of registered UEs and number of LBO PDU Sessions is described in Clause 4.2.11.5.2.4. NSACF nodes to be contacted in all the above are either configured or discovered. 4.2.11.5.2.3 VPLMN with HPLMN assistance NSAC Admission mode for number of Registered UEs Figure 4.2.11.5.2.3-1: HPLMN Delegated NSAC admission for UE number Procedure The procedure of NSAC for maximum number of UEs for a roaming UE registration is performed as follows: 1. Same as step 1 defined in clause 4.2.11.2. For the inbound roaming UE, the AMF checks the NSAC admission mode of the registered S-NSSAI based on the subscription data from UDM. If the Hierarchical NSAC architecture is deployed in the VPLMN, steps 2a-3a are executed and step 2b is skipped. 2a. The AMF invokes Nnsacf_NSAC_NumOfUEsUpdate request to the NSACF in VPLMN same as step 2 of clause 4.2.11.2a with the additional parameter NSAC admission mode, i.e. VPLMN with HPLMN assistance NSAC admission mode. 3a. Same procedure of steps 3-5 in clause 4.2.11.2a is executed. If the centralized NSAC architecture is deployed in the VPLMN, step 2b is executed and steps 2a-3a are skipped. 2b. The AMF invokes Nnsacf_NSAC_NumOfUEsUpdate request to the central NSACF in VPLMN same as step 2 of clause 4.2.11.2 with the additional parameter NSAC admission mode, i.e. VPLMN with HPLMN assistance NSAC admission mode. 4. If there is no allocated maximum number of UEs from HPLMN or the allocated maximum number of registered UEs has been reached and the type of NSAC admission mode is VPLMN with HPLMN assistance NSAC admission mode, the Primary (or central) NSACF in VPLMN interacts with HPLMN. In this case, steps 5-7 are executed. Otherwise, steps 5-7 are skipped. The Primary (or central) NSACF in VPLMN discovers the Primary (or central) NSACF in HPLMN. NOTE 1: The Primary (or central) NSACF in HPLMN can be configured or be discovered via NRF. 5. The Primary (or central) NSACF in the VPLMN invokes Nnsacf_NSAC_NumOfUEsUpdate Request to the Primary (or central) NSACF in the HPLMN for NSAC delegation and to receive an initial or an updated maximum number of registered UEs for the mapped S-NSSAI in HPLMN for the inbound roamers. The request includes mapped S-NSSAI in HPLMN, PLMN ID and NSAC admission mode. 6. The Primary (or central) NSACF in HPLMN invokes Nnsacf_NSAC_NumOfUEsUpdate Response message to the Primary (or central) NSACF of VPLMN. The response message includes mapped S-NSSAI in HPLMN, the allocated maximum number of registered UEs for the mapped S-NSSAI in HPLMN for inbound roamers. Alternatively, the Primary (or central) NSACF in HPLMN rejects the request for the NSAC delegation. 7. The Primary (or central) NSACF in VPLMN updates the previous stored maximum number of UE based on the received allocated maximum number of UEs. If the Hierarchical NSAC architecture is deployed in the VPLMN, steps 8a-9a are executed and steps 8b-9b are skipped. 8a. This step is executed only if the NSACF in VPLMN has interacted with Primary NSACF in VPLMN at step 3a before. The NSACF with the assistance of Primary NSACF in VPLMN perform NSAC according to the steps 6-8 in clause 4.2.11.2a. 9a. Based on the response from Primary NSACF in VPLMN, the NSACF in VPLMN returns the response (i.e. acceptance or rejection) message to the AMF. The AMF provides the corresponding response to the inbound roaming UE. If the centralized NSAC architecture is deployed in the VPLMN, steps 8b-9b are executed and steps 8a-9a are skipped. 8b. Same as the step 3 in clause 4.2.11.2 with the replacement of NSACF with Central NSACF. 9b. The Central NSACF in VPLMN returns the response (i.e. acceptance or rejection) message to the AMF. The AMF provides the corresponding response to the inbound roaming UE. 4.2.11.5.2.4 VPLMN with HPLMN assistance NSAC Admission mode for number of LBO PDU Sessions Figure 4.2.11.5.2.4-1: HPLMN Delegated NSAC admission for PDU Session number procedure The NSAC procedure for maximum number of LBO PDU Sessions for inbound roamers, is performed as follow: 1. Same as steps 1 defined in clause 4.2.11.4. For the inbound roaming UE, the SMF checks the NSAC admission mode of the S-NSSAI for the LBO PDU session based on the subscription data from UDM. If the Hierarchical NSAC architecture is deployed in the VPLMN, steps 2a-3a are executed and step 2b is skipped. 2a. The SMF invokes Nnsacf_NSAC_NumOfsPDUsUpdate request to the NSACF in VPLMN same as step 2 of clause 4.2.11.4 with the additional parameter NSAC admission mode, i.e. VPLMN with HPLMN assistance NSAC admission mode. 3a. Same procedure of steps 3-5 in clause 4.2.11.4a is executed. If the centralized NSAC architecture is deployed in the VPLMN, step 2b is executed and steps 2a-3a are skipped. 2b. The SMF invokes Nnsacf_NSAC_NumOfsPDUsUpdate request to the central NSACF in VPLMN same as step 2 of clause 4.2.11.4 with the additional parameter NSAC admission mode, i.e. VPLMN with HPLMN assistance NSAC admission mode. 4-7. The same procedure as step 4-7 of Figure 4.2.11.5.2.3-1 is applied with the difference that the maximum number of registered UE parameter is replaced with the maximum number of LBO PDU Sessions number. Nnsacf_NSAC_NumOfUEsUpdate service operation is replaced with Nnsacf_NSAC_NumOfPDUsUpdate service operation. If the Hierarchical NSAC architecture is deployed in the VPLMN, steps 8a-9a are executed and steps 8b are skipped. 8a. This step is executed only if the NSACF in VPLMN has interacted with Primary NSACF in VPLMN at step 3a before. The NSACF with the assistance of Primary NSACF in VPLMN performs NSAC according to the steps 6-8 in clause 4.2.11.4a. 9a. Based on the response from Primary NSACF in VPLMN, the NSACF in VPLMN returns the response (i.e. acceptance or rejection) message to the SMF. The SMF provides the corresponding response to the inbound roaming UE. If the centralized NSAC architecture is deployed in the VPLMN, steps 8b-9b are executed and steps 8a-9a are skipped. 8b. Same as the step 3 in clause 4.2.11.4 with the replacement of NSACF with Central NSACF. 9b. The Central NSACF in VPLMN returns the response (i.e. acceptance or rejection) message to the SMF. The SMF provides the corresponding response to the inbound roaming UE. 4.2.11.5.2.5 HPLMN NSAC Admission Monitoring and enforcement for the maximum number of UEs registered with a network slice monitoring is done by the NSACF in the HPLMN per the procedure described in clause 4.2.11.2 with the following differences: - Step 1, the AMF verifies the applicable NSAC admission mode for the registered S-NSSAI for the UE based on the subscription data from UDM. The S-NSSAI is the mapped S-NSSAI in HPLMN. - Step 2, in the Nnsacf_NSAC_NumOfUEsUpdate_Request service operation the V-AMF provides both the S-NSSAI in VPLMN and the corresponding mapped S-NSSAI in HPLMN to the NSACF in the HPLMN. - Step 3, the NSCAF in the HPLMN performs NSAC for the corresponding mapped S-NSSAI in HPLMN. Enforcement of the maximum number of LBO PDU Sessions established for an S-NSSAI is performed by the NSACF in the HPLMN as per the procedure described in clause 4.2.11.4 with the following differences: - Step 1, the SMF verifies the applicable NSAC admission mode for the S-NSSAI used for the established PDU session based on the subscription data from UDM. The S-NSSAI is the mapped S-NSSAI in HPLMN. - Step 2, in the Nnsacf_NSAC_NumOfPDUsUpdate_Request service operation the V-SMF provides both the S-NSSAI in VPLMN and the corresponding mapped S-NSSAI in HPLMN to the NSACF in the VPLMN. - Step 3, the NSACF in the HPLMN performs NSAC for the corresponding mapped S-NSSAI in HPLMN. NSACF nodes to be contacted in all the above are either configured or discovered as defined in clause 6.3.22 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.11.5.2 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.