hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.2 UE IP Address Management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.2.1 General | The UE IP address management includes allocation and release of the UE IP address as well as renewal of the allocated IP address, where applicable.
The UE shall perform the association of the application to a new PDU Session described in clause 6.1.2.2.1 of TS 23.503 [45], with the following considerations:
- If there ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.2.2 Routing rules configuration | When the UE has an IPv6 multi-homed PDU Session the UE selects the source IPv6 prefix according to IPv6 multi-homed routing rules pre-configured in the UE or received from network. IPv6 multi-homed routing rules received from the network have a higher priority than IPv6 multi-homed routing rules pre-configured in the U... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.2.3 The procedure of Stateless IPv6 Address Autoconfiguration | If Stateless IPv6 Address Autoconfiguration is used for IPv6 address allocation to the UE, after PDU Session Establishment the UE may send a Router Solicitation message to the SMF to solicit a Router Advertisement message. The SMF sends a Router Advertisement message (solicited or unsolicited) to the UE. The Router Adv... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.2.4 IPv6 Prefix Delegation via DHCPv6 | Optionally, a single network prefix shorter than the default /64 prefix may be assigned to a PDU Session. In this case, the /64 default prefix used for IPv6 stateless autoconfiguration will be allocated from this network prefix; the remaining address space from the network prefix can be delegated to the PDU Session usi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.3 Management of CN Tunnel Info | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.3.1 General | CN Tunnel Info is the Core Network address of a N3/N9 tunnel corresponding to the PDU Session. It comprises the TEID and the IP address which is used by the UPF on the N3/N9 tunnel for the PDU Session.
The CN Tunnel Info allocation and release is performed by the UPF. The SMF shall indicate to the UPF when the UPF is r... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.3.2 Void | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.3.3 Management of CN Tunnel Info in the UPF | The UPF shall manage the CN Tunnel Info space. When a new CN Tunnel Info is needed, the SMF shall request over N4 the UPF to allocate CN Tunnel Info for the applicable N3/N9 reference point. In response, the UPF provides CN Tunnel Info to the SMF. In the case of PDU Session Release or a UPF is removed from the user pla... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.4 Traffic Detection | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.4.1 General | This clause describes the detection process at the UPF that identifies the packets belonging to a session, or a service data flow.
The SMF is responsible for instructing the UP function about how to detect user data traffic belonging to a Packet Detection Rule (PDR). The other parameters provided within a PDR describe ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.4.2 Traffic Detection Information | The SMF controls the traffic detection at the UP function by providing detection information for every PDR.
For IPv4 or IPv6 or IPv4v6 PDU Session type, detection information is a combination of:
- CN tunnel info.
- Network instance.
- QFI.
- IP Packet Filter Set as defined in clause 5.7.6.2.
- Application Identifier: ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.5 Control of User Plane Forwarding | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.5.1 General | The SMF controls user-plane packet forwarding for traffic detected by a PDR by providing a FAR with instructions to the UPF, including:
- Forwarding operation information;
- Forwarding target information.
The details of the forwarding target and operation will depend on the scenario and is described below. The followin... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.5.2 Data forwarding between the SMF and UPF | Scenarios for data forwarding between the SMF and UPF are defined as below:
Table 5.8.2.5.2-1: Scenarios for data forwarding between the SMF and UPF
Scenario description
Data forwarding direction
1
Forwarding of user-plane packets between the UE and the SMF e.g. DHCP signalling.
UPF to SMF
SMF to UPF
2
Forwarding of pa... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.5.3 Support of Ethernet PDU Session type | When configuring an UPF acting as PSA for an Ethernet PDU Session Type, the SMF may instruct the UPF to route the traffic based on detected MAC addresses as follows.
- The UPF learns the MAC address(es) connected via N6 based on the source MAC addresses of the DL traffic received on a N6 Network Instance.
- The UPF lea... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.6 Charging and Usage Monitoring Handling | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.6.1 General | The SMF shall support interfaces towards CHF and PCF. The SMF interacts with CHF and PCF based on information received from other control plane NFs and user plane related information received from the UPF.
QoS Flow level, PDU Session level and subscriber related information remain at the SMF and only usage information ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.6.2 Activation of Usage Reporting in UPF | Triggered by the PCC rules received from the PCF or preconfigured information available at SMF, as well as from the CHF for online charging method via quota management mechanisms, the SMF shall provide Usage Reporting Rules to the UPF for controlling how usage reporting is performed.
The SMF shall request the report of... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.6.3 Reporting of Usage Information towards SMF | The UPF shall support reporting of usage information to the SMF. The UPF shall be capable to support reporting based on different triggers, including:
- Periodic reporting with period defined by the SMF.
- Usage thresholds provided by the SMF.
- Report on demand received from the SMF.
The SMF shall make sure that the m... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.7 PDU Session and QoS Flow Policing | ARP is used for admission control (i.e. retention and pre-emption of the new QoS Flow). The value of ARP is not required to be provided to the UPF.
For every QoS Flow, the SMF shall determine the transport level packet marking value (e.g. the DSCP in the outer IP header) based on the 5QI, the Priority Level (if explici... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.8 PCC Related Functions | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.8.1 Activation/Deactivation of predefined PCC rules | A predefined PCC rule is configured in the SMF.
The traffic detection filters, e.g. IP Packet Filter, required in the UP function can be configured either in the SMF and provided to the UPF, as service data flow filter(s), or be configured in the UPF, as the application detection filter identified by an application ide... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.8.2 Enforcement of Dynamic PCC Rules | The application detection filters required in the UPF can be configured either in the SMF and provided to the UPF as the service data flow filter, or be configured in the UP function identified by an application identifier.
When receiving a dynamic PCC rule from the PCF which contains an application identifier and/or p... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.8.3 Redirection | The uplink application's traffic redirection may be enforced either in the SMF (as specified in 5.8.2.5 Control of user plane forwarding) or directly in the UPF. The redirect destination may be provided in the dynamic PCC rule or be preconfigured, either in the SMF or in the UPF.
When receiving redirect information (re... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.8.4 Support of PFD Management | The NEF (PFDF) shall provide PFD(s) to the SMF on the request of SMF (pull mode) or on the request of PFD management from NEF (push mode), as described in TS 23.503 [45]. In addition, the NEF (PFDF) may subscribe to NWDAF to be notified or request to get PFD "Determination analytics" for known applications (as specifie... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.9 Functionality of Sending of "End marker" | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.9.0 Introduction | Sending of "end marker" is a functionality which involve SMF and UPF in order to assist the reordering function in the Target RAN. As part of the functionality, constructing of end marker packets can either be done in the SMF or in the UPF, as described in clauses 5.8.2.9.1 and 5.8.2.9.2. Whether constructing of end ma... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.9.1 UPF Constructing the "End marker" Packets | In the case of inter NG-RAN Handover procedure without UPF change, SMF shall indicate the UPF to switch the N3 path(s) by sending an N4 Session Modification Request message with the new AN Tunnel Info of NG RAN and in addition, provide an indication to the UPF to send the end marker packet(s) on the old N3 user plane p... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.9.2 SMF Constructing the "End marker" Packets | UPF referred in this clause is the UPF terminates N3 reference point.
It is assumed that the PDU Session for the UE comprises of an UPF that acts as a PDU Session Anchor and an intermediate UPF terminating N3 reference point at the time of this Handover procedure.
In the case of inter NG-RAN Handover procedure without ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.10 UP Tunnel Management | 5GC shall support per PDU Session tunnelling on N3 between (R)AN and UPF and N9 between UPFs. If there exist more than one UPF involved for the PDU Session, any tunnel(s) between UPFs (e.g. in the case of two UPFs, between the UPF that is an N3 terminating point and the UPF for PDU Session Anchor) remains established w... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.11 Parameters for N4 session management (moved) | The parameters used by SMF to control the functionality of the UPF as well as to inform SMF about events occurring at the UPF are described in clause 5.8.5. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.12 Reporting of the UE MAC addresses used in a PDU Session | For Ethernet PDU Session type, the SMF may control the UPF to report the different MAC (Ethernet) addresses used as source address of frames sent UL by the UE in a PDU Session. These MAC addresses are called UE MAC addresses.
This control and the corresponding reporting takes place over N4.
NOTE: This is e.g. used to s... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.13 Support for 5G VN group communication | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.13.0 General | The SMF may configure the UPF(s) to apply different traffic forwarding methods to route traffic between PDU Sessions for a single 5G VN group. For example, depending on the destination address, some packet flows may be forwarded locally, while other packet flows are forwarded via N19 and other packet flows are forwarde... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.13.1 Support for unicast traffic forwarding of a 5G VN | To enable unicast traffic forwarding in a UPF, the following applies:
- The SMF provides for each 5G VN group member's N4 Session (i.e. N4 Session corresponding to PDU Session) the following N4 rules that enable the processing of packets received from this UE.
- in order to detect the traffic, a PDR containing Source I... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.13.2 Support for unicast traffic forwarding update due to UE mobility | To enable the service continuity when the PSA UPF serving the UE changed, the following applies:
- Keep the UE address unchanged if N6-based forwarding is not used.
- Configure the UE's N4 Session with N4 rules (PDR, FAR) to detect and forward the traffic to this UE via its PDU Session tunnel(i.e. N3 tunnel) on the tar... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.13.3 Support for user plane traffic replication in a 5G VN | 5.8.2.13.3.1 User plane traffic replication based on UPF internal functionality
For Ethernet PDU Sessions, the SMF may instruct the UPF to route traffic to be replicated as described in clause 5.8.2.5.
For IP PDU Session types, the SMF may instruct the UPF to manage IP multicast traffic as described in clauses 4.6.6 an... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.14 Inter PLMN User Plane Security functionality | Operators can deploy UPF(s) supporting the Inter PLMN User Plane Security (IPUPS) functionality at the border of their network to protect their networks from invalid inter PLMN N9 traffic.
The IPUPS functionality forwards GTP-U packets (received via the N9 interface) only if they belong to an active PDU Session and are... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.15 Void | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.16 Support for L2TP tunnelling on N6 | If requested by the SMF during N4 Session Establishment, the UPF (PSA) may setup L2TP towards an L2TP network server (LNS) in the DN and tunnel the PDU Session user plane traffic in this L2TP tunnel. In this case the UPF acts as a L2TP access concentrator (LAC).
To enable this, the SMF may provide L2TP information to t... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.17 Data exposure via Service Based interface | The UPF may expose information by means of UPF Event Exposure service as described in TS 23.502 [3] clause 5.2.26.2, via a service-based interface directly. The NF consumers, which may receive UPF event notifications, are AF/NEF, TSNAF/TSCTSF, SMF and NWDAF/DCCF/MFAF.
When the UPF supports the data exposure via the ser... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.18 QoS Flow related QoS monitoring and reporting | The SMF may configure the UPF to perform QoS monitoring for a QoS Flow and to report the monitoring results with the help of the following parameters provided in the Session Reporting Rule (SRR) described in clause 5.8.5.11:
- QoS monitoring parameter(s) indicating the subject of the QoS monitoring as defined in clause... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.19 Explicit Buffer Management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.19.1 General | 5GC supports buffering of UE's downlink packets for deactivated PDU Sessions.
Support for buffering in the UPF is mandatory and optional in the SMF.
When the UP connection of a PDU Session is deactivated, buffering in UPF can be activated by the SMF. If the SMF supports buffering capability, the SMF can decide to activ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.19.2 Buffering at UPF | When the SMF decided to activate buffering in UPF, the SMF shall inform the UPF to start buffering packets for this PDU Session.
The SMF provides instructions to the UPF for at least the following behaviour:
- buffer downlink packets with the following additional options:
- reporting the arrival of first downlink packe... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.19.3 Buffering at SMF | When the SMF supports buffering capability and the SMF decided to activate buffering in SMF for the PDU Session, the SMF shall inform the UPF to start forwarding the downlink packets towards the SMF.
When the UP connection of the PDU Session is activated, if there are buffered downlink packets available and their buffe... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.20 SMF Pause of Charging | The SMF Pause of Charging functionality is supported with the purpose that the charging and usage monitoring data in the core network more accurately reflects the downlink traffic actually sent to the (R)AN. When the amount of downlink data incoming at the UPF for a PDU Session that is in deactivated state goes above a... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.21 Operator configurable UPF capabilities | UPF may support operator defined non-standardized feature(s) (such as hardware features (e.g. xPUs information (e.g. CPU/GPU information)), computing features (e.g. computing resource type, computing capability) and protection features (e.g. Firewall, DDoS)) or partially supported standardized feature(s). If the UPF su... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.22 Handling of Payload Headers | Support of Handling of Payload Headers is an optional UPF feature as defined in clause 5.6.17.
The SMF receives Header Handling Control information in a PCC rule (as described in clause 6.3.1 of TS 23.503 [45]), it forwards the Header Handling Control information to the UPF via N4 interactions. The SMF adds the Header ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.2.23 N6 Delay Measurement and Reporting | The candidate UPF(s) may be configured by the SMF, as described in clause 4.4.3 of TS 23.502 [3], to measure the N6 delay for the connection between the UPF and measurement endpoint(s) in the DN (represented by one or more IP address(es)).
NOTE 1: The measurement endpoint in the DN used for delay measurements can be a ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.3 Explicit Buffer Management (moved) | The Explicit Buffer Management is described in clause 5.8.2.19. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.4 SMF Pause of Charging (moved) | The SMF Pause of Charging is described in clause 5.8.2.20. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5 Parameters for N4 session management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.1 General | These parameters are used by SMF to control the functionality of the UPF as well as to inform SMF about events occurring at the UPF.
The N4 session management procedures defined in clause 4.4.1 of TS 23.502 [3] will use the relevant parameters in the same way for all N4 reference points: the N4 Session Establishment pr... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.2 N4 Session Context | N4 Session Context is identified by an N4 Session ID. An N4 Session Context is generated by SMF and UPF respectively to store the parameters related to an N4 session, including the N4 session ID and following information (see TS 29.244 [65] for an exhaustive list):
1) general session related parameters such as S-NSSAI,... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.3 Packet Detection Rule | The following table describes the Packet Detection Rule (PDR) containing information required to classify a packet arriving at the UPF. Every PDR is used to detect packets in a certain transmission direction, e.g. UL direction or DL direction.
Table 5.8.5.3-1: Attributes within Packet Detection Rule
Attribute
Descripti... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.4 QoS Enforcement Rule | The following table describes the QoS Enforcement Rule (QER) that defines how a packet shall be treated in terms of bit rate limitation and packet marking for QoS purposes. All Packet Detection Rules that refer to the same QER share the same QoS resources, e.g. MFBR.
Table 5.8.5.4-1: Attributes within QoS Enforcement R... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.5 Usage Reporting Rule | The following table describes the Usage Reporting Rule (URR) that defines how a packet shall be accounted as well as when and how to report the measurements.
Table 5.8.5.5-1: Attributes within Usage Reporting Rule
Attribute
Description
Comment
N4 Session ID
Identifies the N4 session associated to this URR
Rule ID
Uniqu... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.6 Forwarding Action Rule | The following table describes the Forwarding Action Rule (FAR) that defines how a packet shall be buffered, dropped or forwarded, including packet encapsulation/decapsulation and forwarding destination.
Table 5.8.5.6-1: Attributes within Forwarding Action Rule
Attribute
Description
Comment
N4 Session ID
Identifies the ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.7 Usage Report generated by UPF | The UPF sends the Usage Report to inform the SMF about the measurement of an active URR or about the detection of application traffic of an active Packet Detection Rule. For each URR, the Usage Report may be generated repeatedly, i.e. as long as any one of the valid event triggers applies. A final Usage Report is sent ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.8 Multi-Access Rule | The following table describes the Multi-Access Rule (MAR) that includes the association to the two FARs for both 3GPP access and non-3GPP access in the case of supporting ATSSS.
Table 5.8.5.8-1: Attributes within Multi-Access Rule
Attribute
Description
Comment
N4 Session ID
Identifies the N4 session associated to this ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.9 Bridge/Router Information | The following table describes the User plane node Information (UI) that includes the information required to configure a 5GS logical bridge/router for TSC or Deterministic Networking PDU Sessions.
Table 5.8.5.9-1: User plane node Information
Attribute
Description
Comment
Port Number
Port Number allocated by the node fo... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.10 Void | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.11 Session Reporting Rule | The following table describes the Session Reporting Rule (SRR) that defines the detection and reporting events that the UPF shall report, that are not related to specific PDRs of the PDU Session, as follows:
- Per QoS Flow per UE QoS Monitoring Report, as specified in clause 5.33.3.2.
- Change of 3GPP or non-3GPP acces... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.12 Session reporting generated by UPF | The UPF sends the session report to inform the SMF the detected events for a PDU Session that are related to an SRR. The UPF may support notification to the AF possibly via local NEF as described in clause 6.4 of TS 23.548 [130].
Table 5.8.5.12-1: Attributes within Session Reporting
Attribute
Description
Comment
N4 Ses... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.13 Void | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.14 TSC Management Information | The following table describes the TSC Management Information Container (TSC MIC) that includes UMIC, PMIC and the associated NW-TT port number.
The SMF may include the notification target address for PMIC/UMIC UPF event provided by the PCF in the TSC Management Information sent to UPF if the UPF supports the related re... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.8.5.15 Downlink Data Report generated by UPF | The UPF sends the Downlink Data Report to inform the SMF about the events related to receiving or discarding of downlink packets. The SMF controls this type of UPF report by providing instructions in the Buffer Action Rule of a FAR.
Following attributes can be included:
Table 5.8.5.15-1: Attributes within Downlink Data... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9 Identifiers | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9.1 General | Each subscriber in the 5G System shall be allocated one 5G Subscription Permanent Identifier (SUPI) for use within the 3GPP system. The 5G System supports identification of subscriptions independently of identification of the user equipment. Each UE accessing the 5G System shall be assigned a Permanent Equipment Identi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9.2 Subscription Permanent Identifier | A globally unique 5G Subscription Permanent Identifier (SUPI) shall be allocated to each subscriber in the 5G System and provisioned in the UDM/UDR. The SUPI is used only inside 3GPP system and its privacy is specified in TS 33.501 [29].
The SUPI may contain:
- an IMSI as defined in TS 23.003 [19], or
- a network-speci... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9.3 Permanent Equipment Identifier | A Permanent Equipment Identifier (PEI) is defined for the 3GPP UE accessing the 5G System.
The PEI can assume different formats for different UE types and use cases. The UE shall present the PEI to the network together with an indication of the PEI format being used.
If the UE supports at least one 3GPP access technolo... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9.4 5G Globally Unique Temporary Identifier | The AMF shall allocate a 5G Globally Unique Temporary Identifier (5G-GUTI) to the UE that is common to both 3GPP and non-3GPP access. It shall be possible to use the same 5G-GUTI for accessing 3GPP access and non-3GPP access security context within the AMF for the given UE. An AMF may re-assign a new 5G-GUTI to the UE ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9.5 AMF Name | An AMF is identified by an AMF Name. AMF Name is a globally unique FQDN, the structure of AMF Name FQDN is defined in TS 23.003 [19]. An AMF can be configured with one or more GUAMIs. At a given time, GUAMI with distinct AMF Pointer value is associated to one AMF name only. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9.6 Data Network Name (DNN) | A DNN is equivalent to an APN as defined in TS 23.003 [19]. Both identifiers have an equivalent meaning and carry the same information.
The DNN may be used e.g. to:
- Select a SMF and UPF(s) for a PDU Session.
- Select N6 interface(s) for a PDU Session.
- Determine policies to apply to this PDU Session.
The wildcard DN... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9.7 Internal-Group Identifier | The subscription data for an UE in UDR may associate the subscriber with groups. A group is identified by an Internal-Group Identifier.
NOTE 1: A UE can belong to a limited number of groups, the exact number is defined in stage 3 specifications.
NOTE 2: In this Release of the specification, the support of groups is onl... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9.8 Generic Public Subscription Identifier | Generic Public Subscription Identifier (GPSI) is needed for addressing a 3GPP subscription in different data networks outside of the 3GPP system. The 3GPP system stores within the subscription data the association between the GPSI and the corresponding SUPI.
GPSIs are public identifiers used both inside and outside of ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9.9 AMF UE NGAP ID | An AMF UE NGAP ID is an identifier used to identify the UE in AMF on N2 reference point. AMF allocates the AMF UE NGAP ID and send it to the 5G-AN. For the following N2 signalling interaction sent from 5G-AN to AMF, AMF UE NGAP ID is used to identify the UE at the AMF. AMF UE NGAP ID is unique per AMF set. AMF UE NGAP ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.9.10 UE Radio Capability ID | The UE Radio Capability ID is a short pointer with format defined in TS 23.003 [19] that is used to uniquely identify a set of UE Radio Capabilities (excluding UTRAN and NB-IoT capabilities). The UE Radio Capability ID is assigned either by the serving PLMN or by the UE manufacturer, as follows:
- UE manufacturer-assig... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.10 Security aspects | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.10.1 General | The security features in the 5G System include:
- Authentication of the UE by the network and vice versa (mutual authentication between UE and network).
- Security context generation and distribution.
- User Plane data confidentiality and integrity protection.
- Control Plane signalling confidentiality and integrity pr... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.10.2 Security Model for non-3GPP access | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.10.2.1 Signalling Security | When a UE is connected via a NG-RAN and via a standalone non-3GPP accesses, the multiple N1 instances are secured using independent NAS security contexts, each created based on the security context in the corresponding SEAF (e.g. in the common AMF when the UE is served by the same AMF) derived from the UE authenticatio... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.10.3 PDU Session User Plane Security | The User Plane Security Enforcement information provides the NG-RAN with User Plane security policies for a PDU session. It indicates:
- whether UP integrity protection is:
- Required: for all the traffic on the PDU Session UP integrity protection shall apply.
- Preferred: for all the traffic on the PDU Session UP inte... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.11 Support for Dual Connectivity, Multi-Connectivity | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.11.1 Support for Dual Connectivity | Dual Connectivity involves two radio network nodes in providing radio resources to a given UE (with active radio bearers), while a single N2 termination point exists for the UE between an AMF and the RAN. The RAN architecture and related functions to support Dual Connectivity is further described in RAN specifications ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.12 Charging | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.12.1 General | 5GC supports interactions towards CHF for network resource usage, as defined in TS 32.240 [41]. The CHF and the Nchf service are defined in TS 32.290 [67].
The SMF supports the interactions towards the CHF, as defined in TS 32.255 [68]. The UPF supports functionality to collect and report usage data to SMF. The N4 refe... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.12.2 Usage Data Reporting for Secondary RAT | When NG-RAN is deployed in dual connectivity configuration, the HPLMN or VPLMN operator may wish to record the data volume sent and received on the Secondary RAT.
In order to reduce the complexity of this procedure, the following principles are used in this release:
a) The PLMN locally activates the Secondary RAT Usage... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.12.3 Secondary RAT Periodic Usage Data Reporting Procedure | Periodic reporting of the Secondary RAT usage data is an optional function. When NG-RAN, as defined in bullet e) of clause 5.12.12, is configured with a "time interval for Secondary RAT usage data reporting", the NG-RAN shall send a RAN Usage Data Report message for periodic reporting purposes to the SMF only when the ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.13 Support for Edge Computing | Edge computing enables operator and 3rd party services to be hosted close to the UE's access point of attachment, so as to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. Edge Computing support by 5GC is specified in this specification and in TS 23.548 [13... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.14 Policy Control | The policy and charging control framework for the 5G System is defined in TS 23.503 [45]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15 Network slicing | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.1 General | A Network Slice instance is defined within a PLMN or within an SNPN and shall include:
- the Core Network Control Plane and User Plane Network Functions, as described in clause 4.2,
and, in the serving PLMN, at least one of the following:
- the NG-RAN described in TS 38.300 [27];
- the N3IWF or TNGF functions to the no... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.2 Identification and selection of a Network Slice: the S-NSSAI and the NSSAI | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.2.1 General | An S-NSSAI identifies a Network Slice.
An S-NSSAI is comprised of:
- A Slice/Service type (SST), which refers to the expected Network Slice behaviour in terms of features and services;
- A Slice Differentiator (SD), which is optional information that complements the Slice/Service type(s) to differentiate amongst multip... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.2.2 Standardised SST values | Standardized SST values provide a way for establishing global interoperability for slicing so that PLMNs can support the roaming use case more efficiently for the most commonly used Slice/Service Types.
The SSTs which are standardised are in the following Table 5.15.2.2-1.
Table 5.15.2.2-1: Standardised SST values
Slic... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.3 Subscription aspects | The Subscription Information shall contain one or more S-NSSAIs i.e. Subscribed S-NSSAIs. The subscription information shall include at least one default S-NSSAI. The UDM sends at the most 16 Subscribed S-NSSAIs to AMF, i.e. the number that can fit in a Configured NSSAI. The subscription information the UDM sends to th... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.4 UE NSSAI configuration and NSSAI storage aspects |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.