hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.15.1 Key Issue mapping | This solution aims to resolve Key Issue #3, " Support of No Transmit Zones ". |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.15.2 Description | Besides preconfiguration, this solution addresses the dynamical update of NTZ policies. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.15.3 Procedures | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.15.3.1 NTZ Provisioning | The call flow below is based on clause 4.15.6.7 Service-specific parameter provisioning in TS 23.502 [4].
NOTE 1: The UE can be preconfigured with NTZ polices and updates can be applied based on the procedure below.
The procedure can also be delta update.
Figure 6.15.3.1-1 NTZ Parameter provisioning
1. To create a new ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.15.3.2 UE Configuration Update procedure for transparent UE Policy delivery | This procedure is initiated when the PCF wants to update UE policy information (i.e. UE policy) in the UE configuration. The below call flow procedure follows the steps from clause 4.2.4.3 of TS 23.502 [4]. The UE policy delivery mechanism is reused for NTZ policy delivery. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.15.3.3 No-transmission zone parameters & UE behaviour | The NTZ policy information will be based on the coordinates and the indication flag whether NTZ is applicable, as well as the list of allowed frequency bands. The below tables are described as an example. More details on the data structure need to be defined by stage 3.
Editor's note: This clause represents an example ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.15.4 Impacts on services, entities and interfaces | UE
- Complying to new NTZ information based on policy information.
NEF
- Supporting new API/new parameters to support NTZ provisioning.
UDR
- Storage of new NTZ information.
PCF
- Support of new NTZ policy. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.16 Solution #16: NTZ Enforcement in 5GC | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.16.1 Key Issue mapping | This solution addresses KI#3, "Support of No Transmit Zones". |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.16.2 Description | This solution assumes that NTZ enforcement is provided to the 5GC from USS dynamically. This solution is intended for 5GC to enforce NTZ information for the UAV dynamically so that UAV does not transmit in the NTZ after receiving NTZ enforcement.
In this solution, the NTZ enforcement request is initiated from the USS/U... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.16.3 Procedures | Figure 6.16.3-1: NTZ enforcement in 5GC
1. The UAS NF receives the NTZ update request from the USS/UTM. The request includes the NTZ information to be updated for all UAVs. The NTZ information includes one or multiple NTZ areas, frequency bands that UAVs are not allowed to transmit, etc.
The UAS NF query NRF to identif... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.16.4 Impacts on services, entities and interfaces | UAS NF:
- Supports handling of NTZ update request, including forwarding the request to other NFs (e.g. AMF).
AMF:
- Supports notification of NTZ information to the affected UAVs using NAS signalling.
- Supports requesting the SMF to enforce the NTZ (e.g. deactivate PDU Sessions).
- Supports requesting the RAN to enforc... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.17 Solution #17: Support of No Transmit Zone | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.17.1 Key Issue mapping | This solution addresses KI#3. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.17.2 Description | This paper proposes solution for Aerial UEs/UAVs and 5GC/EPC to ensure the support for No Transmit Zone. The following are the main principles of the solution:
- The No Transmit Zone is a kind of restricted area for UAVs not to avail any services from the network. Therefore, this No Transmit Zone information, which may... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.17.3 Procedures | The procedure of ensuring support of No Transmit Zone by Aerial UE and network.
Figure 6.17.3-1: Procedure for NTZ support information
1a. UAV is pre-configured with NTZ information.
1b. UDM is provisioned with NTZ information for the UAV.
2. UAV sends Registration Request with capability indication for support of NTZ.... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.17.4 Impacts on services, entities and interfaces | This solution may have the following impacts to existing entities and interfaces:
UAV:
- will send its capability indication of supporting NTZ.
- will enforce of cell selection/reselection with respect to available NTZ information.
AMF:
- will provide updated NTZ information in registration accept and UE configuration ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 7 Overall Evaluation | Editor's note: This clause provides evaluations of different solutions, if exists. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 8 Conclusions | Editor's note: This clause will list conclusions that have been agreed during the course of the study item activities. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 8.1 Conclusion for Key Issue #1: Enhancement of NEF services to support service exposure and interactions between MNOs and UTM functions | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 8.1.1 Conclusion for Key Issue #1 - Pre-mission flight planning and in-mission flight monitoring for UAVs | It is agreed to take the following principles and way forwards for normative work:
- NEF Assist Pre-mission Flight Planning and NEF Assist In-mission Flight Monitoring should focus on operations by and with UAV while excluding operations by and with UAV-C.
- Solution#1 with necessary update is considered for developing... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 8.1.2 Conclusion for Key Issue #1 - Multiple USS serving different geographical areas corresponding to the UAV flight path | In order for 3GPP network to perform a changeover from one UAS Service Supplier (USS) to another, the following main principles apply:
- USS is responsible for its geographical area, and a geographical area does not necessary identically match tracking areas or cells of a 3GPP network. However, it is assumed that TAs a... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 8.1.3 Conclusion for Key Issue #1: C2 communication reliability | It is concluded that there is no normative impact for the C2 communication reliability.
It is agreed to capture Solution#12 and Solution#14 for C2 communication reliability into Informative Annex in TS 23.256 [2] without details on application layers aspects. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 8.2 Conclusion for Key Issue#2 | Following information are agreed to be utilised to enable NWDAA:
- Absolute location of a UAV provided by LoCation Service;
- Relative Location of UAVs provided by Ranging Service;
- Output of Relative Proximity Analytics provided by NWDAF.
Absolute location of a UAV is generated/derived in 5G network by using the exis... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 8.3 Interim Conclusion for Key Issue #3: Support of No Transmit Zones | NOTE: Clause 8.3 is no longer used as the basis for conclusion of Key Issue #3. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 8.3.1 General | The following principles are agreed to support NTZ.
1) NTZ enforcement applies to the UE that is a UAV UE (aka an aerial UE) with aerial subscription.
2) NTZs are supported for both LTE and NR.
3) An NTZ may map to one or more cells or a fraction of a cell, or overlap different cells in a mobile operator network.
NOTE:... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 8.3.2 Configuring/Provisioning NTZ assistance information to UAV UE and NTZ enforcement by UAV UE | The following NTZ assistance information (or NTZ policy) is configured/provisioned in the UAV UE.
- A list of the restricted frequency band(s) with Geographical Area (including coordinates with longitude, latitude and height restrictions).
NOTE 1: It is assumed UAV UE is configured with NTZ assistance information befor... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 8.4 Final Conclusion for Key Issue #3: Support of No Transmit Zones | The Interim conclusion described in clause 8.3 is superseded by Final conclusion described in this clause. The following principles are agreed to support NTZ. 1) NTZ enforcement applies to the UE that is a UAV UE (aka an aerial UE) with aerial subscription. 2) NTZ enforcement by UAV UE applies for both LTE and NR. 3) A... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 1 Scope | This Technical Report continues the study on key issue description, solution and conclusion on UPF enhancement for Exposure and SBA Phase 2.
The scopes include the following aspects:
- Study potential enhancements on UPF selection to discover UPF with specific user plane functionalities, e.g. NAT, Packet inspection, et... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 3 Definitions of terms and abbreviations | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 4 Architectural Assumptions and Requirements | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 4.1 Architectural Assumptions | - The architecture and framework as specified in TS 23.501 [2], TS 23.502 [3], and TS 23.503 [4] are regarded as the baseline for this study.
- User plane architecture changes are outside of scope and user plane architecture as defined in TS 23.501 [2] will be taken as a basis.
- The functional split in 5GS between UPF... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 4.2 Architectural Requirements | The following architectural requirements are applicable to this study:
- Solutions shall build on the 5G System architectural principles as defined in TS 23.501 [2], including flexibility and modularity for newly introduced functionalities.
- UPF event exposure service registration/deregistration and discovery as defin... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 5 Key Issues | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 5.1 Key Issue #1: Selection of UPF providing a selected user plane functionality | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 5.1.1 Description | Currently a UPF advertises the features it supports in the NF profile of UPF registered in NRF as specified in e.g. clause 6.1.6.2.13 of TS 29.510 [5] and/or over PFCP as defined in TS 29.244 [6]. An SMF leverages the exposed UPF information for proper UPF discovery and selection. A UPF implementation may support more ... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 5.2 Key Issue #2: Enhancements on UPF information exposure | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 5.2.1 Description | UPF Event Exposure service is supported in 5GS since Rel-17 and enhanced in Rel-18. Rel-18 UPEAS has defined mechanisms for both direct and indirect subscription to the UPF Event Exposure Service. In Release 19, further study is proposed on whether and how to enhance UPF information exposure, including the direct or in... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 5.3 Key Issue #3: Study enhancements for UPF handling of headers | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 5.3.1 Description | This KI maps to the WT#3 of the SID.
The KI will study the enhancements needed to permit additional handling of packet headers by UPF. The following aspects will be studied:
- Analyse the use cases and problems to be solved and the feasibility of headers handling (i.e. insert, detect) in UPF for the different protocol ... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6 Solutions | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of Solutions to Key Issues
Key Issues
Solutions
Key Issue #1
Key Issue #2
Key Issue #3
Solution #1: Provisioning of information for header handling
X
Solution #2: UPF provision and selection based on new UPF functionality #2
X
Solution #3: Selection on UPF with extended user plane capabilities
X
So... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.1 Solution #1: Provisioning of information for header handling | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.1.1 Description | Network operators can reach agreements with Application Service Providers to handle traffic specific to their applications in a particular way and/or under specific conditions, in terms of SLAs between both business parties.
Automation capabilities of 5G for network slicing, charging, interactions with AFs, use of anal... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.1.2 Procedures | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.1.2.1 Insertion/detection request | The proposed rule shall include:
Table 6.1.2.1-1:Input parameters from AF
Input parameters from AF
Header/Tag information (NOTE 3)
Identifier
Example: tagID (1) pointing to preconfigured Tag Type= RAT and Tag Value to be included by 5GC nodes
Tag Type + Tag Value
Example: Tag Type=FQDN, Tag Value=domain.com
Action
Valu... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.1.2.2 Header/tag reporting/notification | When a detection action is requested by the AF, SMF and UPF are instructed to report information included by the client or server side under the SLA. The instruction for detecting a header/tag may or may not be associated with an insertion/removal/modification/replacement.
The AF may decide whether the Nnef_TrafficInfl... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.1.2.2.1 Header/tag reporting/notification leveraging Nnef_TrafficInfluence_Notify | The following simplified sequence , derived from clause 4.3.6.3 of TS 23.502 [3], is to apply for this solution upon notification from the UPF:
Figure 6.1.2.2.1-1: Notification of header detection to AF using Nnef_TrafficInfluence service
Based on the configuration by AF, upon receiving N4 Session Report from SMF, SMF ... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.1.2.2.2 Header/tag reporting/notification leveraging UPF Exposure Service | There are two possible options:
OPTION 1
The AF can include Report Correlation ID and UPF event consumer notification URI values in the Traffic Influence rule in the request of new Nnef_TrafficInfluence service and after that the same ID can be used in subscribing new Traffic Influence Reporting event of UPF Exposure S... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.1.3 Impacts on services, entities and interfaces | NEF:
- Nnef_TrafficInfluence service, include the new Header handling and reporting information for a new event as described in clause 6.1.2.1 and handling new event in the Event ID reported to AF.
UDR:
- Nudr_DataManagement service, adding new data subset in the Application data set.
PCF:
- PCC rule to add header hand... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.2 Solution #2: UPF provision and selection based on new UPF functionality | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.2.1 Key Issue mapping | This solution is for KI #1 Selection of UPF providing a selected user plane functionality. |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.2.2 Description | UPF has supported to register in NRF. This registration phase uses the Nnrf_NFManagement_NFRegister operation. But some the UPF capabilities are not included in the UPF Provisioning Information in the NRF.
For example, there are identified 3 scenarios that justify use case that necessitate a need to extend the existing... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.2.3 Procedures | Procedures in clause 4.17.1 and clause 4.17.2 of TS 23.502 [3] are reused to support registering specific UPF functionalities in NRF. The following UPF functionalities are added in UPF profile stored in NRF:
- NAT functionality, and the type of the NAT functionality e.g. static NAT, pooled NAT, NAPT, easy IP, and NAT ... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.2.4 Impacts on services, entities and interfaces | NRF:
- Storing new UPF functionalities in UPF profile.
- Support of new query parameters accords with the new UPF functionalities, e.g. NAT, packet inspection.
SMF:
- Discovery of several UPFs that accords with the new UPF functionalities, e.g. NAT, packet inspection.
UPF:
- Enhanced to register new UPF functionalities... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.3 Solution #3: Selection on UPF with extended user plane capabilities | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.3.1 Description | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.3.1.1 Solution Description | This solution proposes to improve current UPF selection by extending the baseline UPF capabilities announced in N4 and UPF NF profile in NRF by defining an open and generic value (e.g. octet string) which can be used for non-standard or partially supported features:
- The content of this new information element shall b... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.3.2 Procedures | The solution enhances the following procedures:
- It extends the PFCP Association Setup (see clause 4.4.3.1 with "N4 Association Setup Procedure" and clause 4.4.3.2 "N4 Association Update Procedure" in TS 23.502 [3]) adding new capabilities for supported functionalities. This is for stage 3 to define, for example exten... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.3.3 Impacts on existing nodes and functionality | UPF, SMF, NRF are impacted.
Impacts results from adding the AdditionalSupport Info information in UPF configuration and in the procedures for:
- PFCP Association Setup.
- UPF registration in NRF.
- UPF discovery assisted by NRF.
- UPF selection by the SMF.
As described in clause 6.3.1. |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.4 Solution #4: Selection of UPF providing specific user plane functionalities | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.4.1 Key Issue mapping | This solution addresses Key Issue #1. |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.4.2 Description | The functionality of the UPF is defined in clause 6.2.3 of TS 23.501 [2]. Currently a UPF advertises the features it supports in the NF profile of the UPF registered in NRF as specified in e.g. clause 6.1.6.2.13 of TS 29.510 [5], and/or over PFCP as defined in TS 29.244 [6]. An SMF leverages the exposed UPF informatio... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.4.3 Procedures | Figure 6.4.3-1 depicts the procedure summarizing the solution. Only changes to existing TS 23.502 [3] procedures to include new parameters are mentioned.
Figure 6.4.3-1: Procedure for selecting the optimal UPF for a PDU Session supporting required and desired functionalities
1. A PDU Session Establishment (Modification... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.4.4 Impacts on services, entities and interfaces | UDM/UDR:
- Session subscription information might include required and/or desired functionalities for the PDU Session of the subscription.
PCF:
- Includes in the PCC rule required and/or desired functionalities for the PDU Session.
NRF:
- Supports the UPF profile with the extended functionalities. The NRF also supports... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.5 Solution #5: Direct subscription of UPF event exposure service for TSC management | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.5.1 Description | This solution is applicable for a case the UPF employs the NW-TT functionality. According to the latest TS 23.501 [2] specification, the assumptions are as follows.
- 5GS TSN bridge has a single NW-TT entity within UPF.
- Bridge ID is to distinguish between bridge instances within 5GS.
- To support TSN, the user plane ... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.5.2 Procedures | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.5.2.1 Direct subscription of UPF Event Exposure service for TSC management | Figure 6.5.2.1: Direct subscription of UPF Event Exposure service for TSC management
1. TSN AF or TSCTSF gets user plane node ID as Bridge ID or Router ID through PDU session establishment procedure.
2. TSN AF or TSCTSF gets UMIC for the address of user plane node ID through PDU session modification procedure via PCF a... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.5.3 Impacts on services, entities and interfaces | TSN AF or TSCTSF:
- Supports direct subscription of UPF event exposure services for TSC management (i.e. Event ID).
UPF:
- Supports direct subscription of event exposure services for TSC management (i.e. Event ID). |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.6 Solution #6: UPF selection based on the status of the supported functionalities | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.6.1 Key Issue mapping | The solution applies to Key Issue #1: Selection of UPF providing a selected user plane functionality. |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.6.2 Description | As described in the Key Issue #1, UPF advertises the features it supports in the NF profile of UPF registered in NRF. A UPF implementation may support more optional functionalities like NAT, Packet Inspection, etc. An SMF leverages the exposed UPF information for UPF selection.
In the context of TS 23.501 [2], the expo... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.6.3 Procedures | Figure 6.6.3-1: Procedure to notify status of functionalities in UPF
1. UPF invokes Nnrf_NFManagement_NFRegister service to request NRF to register the configured NF Profile for the UPF.
2. In PDU session establishment, for example, SMF invokes Nnrf_NFDiscovery service to request NRF to discover UPF(s) that supports ev... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.6.4 Impacts on services, entities and interfaces | SMF:
- UPF selection based on the status of the supported functionalities.
UPF:
- Notification about status of supported functionalities.
NRF:
- Notification about status of supported running functionalities. |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.7 Solution #7: Translating SUPI/GPSI to NATed IP address | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.7.1 Description | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.7.1.1 Background and problem description | While in R18 UPEAS item, the NAT related issues are introduced and solved. If NAT deployed in network, there exists the mapping table between internal private UE IP address (used in 5GC internally) and public UE IP address used in application server.
If NAT is supported in network, there exists the problem that in eNA ... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.7.1.2 High level description | NWDAF can subscribe to the AF in order for the AF to collect data from UE which can be used by NWDAF for analytics to the UE. In the subscription, the NWDAF can provide the SUPI/GPSI to the AF, and the AF then needs to be able to correlate the IP flow between itself and the UE with the received SUPI/GPSI. The NWDAF can... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.7.2 Procedures | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.7.2.1 Procedure | Figure 6.7.2-1: Getting NATed IP address and port
0. PDU session(s) has been established. If GPSI is known, NF(e.g. NEF or NWDAF)/AF has translated GPSI to SUPI. NF has discovered SMF(s) handling a the PDU session(s) for the combination of SUPI and DNN and S-NSSAI. The NF needs to know the endpoint addresses of the rem... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.7.2.2 Service definition | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.7.2.2.1 Nupf_GetPublicIPaddressAndPort | Service operation name: Nupf_GetPublicIPaddressAndPort_Get
Description: NF service consumer gets the NATed UE public IP address and Port, for the IP flow between the UE and a remote end, e.g. an AF.
Inputs, Required: Private UE address (UE IP address assigned by 5GC for the PDU session).
Inputs, Optional: DNN, S-NSSAI,... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.7.3 Impacts on services, entities and interfaces | NWDAF:
- New service operation, need to know the end point addresses of the remote end, e.g. via configuration.
NEF:
- New service operation, need to know the end point addresses of the remote end, e.g. via configuration, or via signalling from AF.
AF:
- New service operation, can provide the end point addresses of the... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.8 Solution #8: UPF event exposure during UPF relocation | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.8.1 Key Issue mapping | This solution is for KI #2: Enhancements on UPF information exposure. |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.8.2 Description | Rel-18 UPEAS has defined mechanisms that consumer (e.g. NWDAF) can subscribe to UPF for the events (e.g. QoS Monitoring) via SMF, and the UPF can directly send the event notification to the consumer.
NOTE 1: This solution focuses on the indirect subscription of UPF via SMF.
After the consumer subscribes to the UPF even... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.8.2 Procedures | Figure 6.8.2-1: Procedure for UPF relocation
1-3. Consumer (e.g. NWDAF) subscribes to the UPF via the SMF, and the UPF sends notification for the subscribed event directly to the consumer. The consumer may include a relocation reporting indication, which indicates how to handle the data collected by the source UPF when... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.8.3 Impacts to Services, Entities and Interfaces | Consumer NF:
- Indicate how to handle the data collected by source UPF when the UPF relocation occurs.
- Unsubscribe or update the subscription for the UPF event exposure based on the last notification from source UPF.
SMF:
- Indicate the source UPF how to handle the collected data when unsubscribing the source UPF.
So... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.9 Solution #9: DNAI Mapping information exposure | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.9.1 Description | In clause 6.8 of TS 23.548 [7], the AF may request DNAI mapping information from 5GC via NEF. The DNAI mapping information includes the EAS address information (i.e. IP address(es), EAS IP range(s) or FQDN(s)) and the associated DNAI. The DNAI mapping information is statically configured in the NEF/UDR by the OAM. This... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.9.2 Procedures | Figure 6.9.2-1: DNAI Mapping Information Exposure
0. The NEF may discover L-UPF via NRF by invoking Nnrf_NFDiscovery_Request providing the DNAI. The NEF may also discover the L-UPF supporting the DNAI via local configuration.
1. The NEF sends the Nupf_EventExposure_Subscribe Request to the L-UPF to subscribe the DNAI m... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.9.3 Impacts on services, entities and interfaces | UPF:
- Nupf_EventExposure service is enhanced to provide the DNAI mapping information.
NEF:
- Subscribe and receive the DNAI mapping information from the L-UPF.
- Store the DNAI mapping information in the UDR. |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.10 Solution #10: Subscription to UPF Event Exposure Services in the event of UP Path change | |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.10.1 Key Issue mapping | This solution addresses KI#2. |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.10.2 Description | This solution aims to provide a mechanism to support UPF relocation when a consumer NF has directly subscribed to UPF for Event exposure. As per Rel-18, in case the UPF relocation happens, the consumer NF (which is in operator's Trusted Domain) needs to perform the discovery of the relevant UPF again in order to subscr... |
2facdcc6644a494bf137778aa1623db2 | 23.700-63 | 6.10.3 Procedures | Figure 6.10.3-1: Overview of procedure
It is assumed that the Consumer NF is inside the operator's trusted domain, i.e. it is either NWDAF, TSCTSF, Trusted AF or NEF (in case an external AF subscribes to UPF event exposure via NEF). So authorization of consumer NF for using Nupf_EventExposure service can be done based ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.