hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
7c76e660d457710d658498e24c37271e | 23.700-59 | 5.1 Key Issue #1: Enhancement of NEF services to support service exposure and interactions between MNOs and UTM functions | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 5.1.1 Description | In this key issue, the following aspects are required to be studied:
- whether and how to enhance NEF services to support service exposure and interactions between MNOs and UTM functions for supporting i.e.
- Pre-mission flight planning and in-mission flight monitoring for UAVs.
- C2 communication reliability.
- The sc... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 5.2 Key Issue #2: Network-assisted/ground-based mechanism for DAA (Detect And Avoid) with 5GS information | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 5.2.1 Description | Network-assisted/ground-based mechanism for DAA (NWDAA) for tactical deconfliction, collision avoidance, and UTM control of UAV flight path, can be considered a complement for existing DAA based on the PC5 reference point specified in Rel-18.
In this key issue, the following aspects are required to be studied:
- Study ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 5.3 Key Issue #3: Support of No Transmit Zones | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 5.3.1 Description | This key issue relates to the introduction by CEPT ECC Decision 22(07) [3] of No Transmit Zones for aerial UEs. The ECC Decision asserts that a mechanism is necessary to ensure that aerial UEs respect no-transmit zones in order to protect incumbent radio systems from potential interference from aerial UEs.
Since the EC... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6 Solutions | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of Solutions to Key Issues
Solutions
<Key Issue #1>
<Key Issue #2>
<Key Issue #3>
#1
X
#2
X
#3
X
#4
X
#5
X
#6
X
#7
X
#8
X
#9
X
#10
X
#11
X
#12
X
#13
X
#14
X
#15
X
#16
X
#17
X |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.1 Solution #1: Support Pre-Mission Planning and In-Mission Monitoring Flight | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.1.1 Key Issue mapping | This solution addresses KI#1 aspects. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.1.2 Description | Enhance NEF services to support service exposure and interactions between MNOs and UTM functions for supporting pre-mission flight planning and in-mission flight monitoring for UAVs, is one of the study aspects in KI#1. This solution proposes to enhance NEF services, enable USS/UTM to request NEF assistance for pre-mis... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.1.3 Procedures and Parameters | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.1.3.1 Procedure for NEF Assist Pre-mission Flight Planning | Figure 6.1.3.1-1: Procedure for NEF Assist Pre-mission Flight Planning
1. The UAV (or UAV-C) establishes a PDU Session for communication with the USS/UTM as described in clause 5.2.3 of TS 23.256 [2].
2. The UAV (or via its paired UAV-C) requests Pre-mission flight planning service from USS/UTM. The request message inc... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.1.3.2 Procedure for NEF Assist In-mission Flight Monitoring | Figure 6.1.3.2-1: Procedure for NEF Assist In-mission Flight Monitoring
NOTE 1: The NFs in Figure 6.1.3.2-1 represents all the other NFs beside GMLC and NEF/UAS NF involved in the procedure.
1. The USS/UTM sends In-mission flight monitoring assist request to NEF. The request message includes identifier of the UAV (e.g.... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.1.3.3 Parameters in Request for Movement Behaviour Analytics | The USS acting as an Application Function communicates with the NEF which corresponds to the NF consumer in clause 6.21.4 of TS 23.288 [6].
Editor's note: The final list of parameters is FFS.
The USS can either subscribe to notifications from the NEF (i.e. a Subscribe-Notify model) or request a single notification from... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.1.4 Impacts on services, entities and interfaces | UAS NF/NEF:
- Enhance for supporting pre-mission flight planning assistance service.
- Enhance for supporting in-mission flight monitoring assistance service.
NWDAF:
- Enhance the inputs and the outputs of Movement Behaviour Analytics.
USS/AF:
- Enhance for supporting UAV/UAV-C trigger pre-mission flight planning servi... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.2 Solution #2: UAV flight path deviation exposure | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.2.1 Key Issue mapping | This solution aims to resolve
Key Issue #1, "Enhancement of NEF services to support service exposure and interactions between MNOs and UTM functions". |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.2.2 Description | The solution also makes use of UE flight path reporting feature (AAM). It is assumed, in this solution, the UE flight path reporting is also implemented/available in 5G NR. Alternatively, or complementary, this solution can use MDT reports that also bring an insight of the radio conditions and UE location. The solution... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.2.3 Procedures | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.2.3.1 Monitoring & reporting of UAV flight path deviation | The USS/UTM (acting as an external AF) can access 3GPP exposed services using public identifier of the UE (used in the UAV). Below pre-conditions apply:
- When UAV authentication/authorization procedure is used:
- UAV is authenticated during PDU session establishment (or optionally at 5GS registration) by USS/UTM.
- 3G... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.2.4 Impacts on services, entities and interfaces | NWDAF:
- Support for new analytics ID and analytics event.
NEF:
- Potential impact to existing exposure API due to new analytics, if any. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.3 Solution #3: UAV flight planning and monitoring | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.3.1 Key Issue mapping | This solution addresses Key Issues #1 which proposes to enhance the notification on QoS Sustainability Analytics mechanism to the AF (e.g. USS/UTM) for pre-mission flight planning and in-mission flight monitoring.
The enhancement of QoS Sustainability Analytics supported by NWDAF is to consider the height information, ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.3.2 Description | An AF (e.g. USS/UTM) may request notifications on QoS Sustainability Analytics from the NEF for an indicated geographic area or a path of interest and a target time interval in order to adjust the application behaviour in advance according to the potential QoS change. How the AF (e.g. UTM/USS) makes use of QoS Sustaina... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.3.3 Procedures | Editor's note: This clause describes high-level procedures and information flows for the solution. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.3.4 Impacts on services, entities and interfaces | AF (USS/UTM):
- Provide location information (waypoints defined as 3D locations) to NEF when request QoS Sustainability Analytics.
NWDAF:
- Consider 3D location for deriving QoS Sustainability Analytics in order to identify the performance measurement information of the most appropriate ground and/or sky cell and to es... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.4 Solution #4: Network-supported Tactical Deconfliction | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.4.1 Key Issue mapping | This solution applies to Key Issue #2. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.4.2 Description | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.4.2.1 Introduction | Sense and Avoid (SAA), Detect and Avoid (DAA), or tactical deconfliction systems are technologies that allow uncrewed aerial vehicles (UAVs) and drones to integrate safely into civilian airspace, avoiding collisions with other aircraft, buildings, power lines, birds and other obstacles. These systems observe the enviro... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.4.2.2 Solution Overview | The solution proposed assumes the deployment of an AIML-based localized USS/UTM function tailored specifically to provide NWDAA services to UAVs and UTM. We identify this function as Localized DAA Server (LDS) for tactical deconfliction. We assume that LDS is a functionality separate from USS/UTM due to the different s... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.4.2.3 Solution Architecture | The solution assumes that the LDS is deployed by the MNO at the edge of the network, and communications over the UAV and the LDS are carried out over user plane.
The LDS can interface with NEF/UAS NF using existing or new/extended service exposure functionality. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.4.3 Procedures | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.4.3.1 Overall Information Flow | The following logical flow is assumed:
Figure 6.4.3.1-1: Overall Information Flow for NWDAA Solution
NOTE: Steps 4 to 7 are exchanged at application layer and are outside the scope of 3GPP. They are described here to provide an overview of how the solution would work as a whole.
1. The UAV registers to the 5G System us... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.4.3.2 UAV-LDS Connectivity Establishment for LDS@Edge | UAV UE that is capable of LDS provides the LDS indication during a PDU Session Establishment for UAS services as described in TS 23.256 [2] and may be for a PDU session established for C2, for C2 and UTM services, or dedicated for LDS services depending on UAV UE configuration as to which DNN shall be used for LDS serv... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.4.4 Impacts on services, entities and interfaces | The following entities are impacted:
- UE:
- NWDAA capability indication in 5GSM;
- ability to receive policies for LDS information transmission;
- ability to receive LDS@Edge addressing information transmission.
- SMF:
- verify LDS service subscription;
- configuration of LDS service availability;
- provide UAV UE wit... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.5 Solution #5: Support Network-assisted DAA with Existing 5GC Services | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.5.1 Key Issue mapping | This solution addresses KI#2 aspects. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.5.2 Description | Study which existing information collected and generated in the 5GS can be utilised to enable NWDAA is one of the study aspects in KI#2. This solution proposes to utilize the GMLC service on Ranging/Sidelink Positioning location and Relative Proximity predictions on collision generated at NWDAF to support Network-assis... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.5.3 Procedures and Parameters | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.5.3.1 Procedure for UAV/UAV-C Triggered Network-assisted DAA | Figure 6.5.3.1-1: Procedure for UAV/UAV-C Triggered Network-assisted DAA
1. The UAV (or UAV-C) establishes a PDU Session for communication with the USS as described in clause 5.2.3 of TS 23.256 [2].
2. The DAA service may be triggered by UAV(s) or UAV-C. The UAV(s) (via its paired UAV-C) or the UAV-C requests DAA servi... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.5.3.2 Procedure for AAM Triggered Network-assisted DAA | Figure 6.5.3.2-1: Procedure for AAM Triggered Network-assisted DAA
1. As described in clause 5.7.2 steps 1-6 of TS 23.256 [2], the UAV(s) listens for signals on the correspondingly destination Layer-2 ID configured for the used service type. The AAM scans the airspace over the area/arena for UAV(s), retrieves for each ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.5.3.3 Parameters in Request for Relative Proximity Analytics | The USS acting as an Application Function communicates with the NEF which corresponds to the NF consumer in clause 6.19.4 of TS 23.288 [6].
The USS can either subscribe to notifications from the NEF (i.e. a Subscribe-Notify model) or request a single notification from the NEF (i.e. a Request-Response model). The USS re... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.5.4 Impacts on services, entities and interfaces | UAS NF/NEF:
- Enhance Nnef_AnalyticsExposure service, e.g. additional parameters.
NWDAF:
- Enhance the inputs and the outputs of Relative Proximity Analytics.
Editor's note: It is FFS if existing data is enough or enhancement is needed.
USS/AF:
- Enhance for supporting UAV/UAV-C trigger DAA service.
- Enhance for suppo... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.6 Solution #6: UTM requests information used for DAA | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.6.1 Key Issue mapping | This solution address key issue #2: Network-assisted/ground-based mechanism for DAA (Detect And Avoid) with 5GS information. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.6.2 Description | In this solution, it is the UTM request the following existing information from 5GC used for DAA:
- Sidelink positioning location results when certain trigger events occur. The trigger events are described in clause 6.20.4 of TS 23.273 [7], e.g. one trigger event occurs if the distances between at least one UE of the n... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.6.3 Procedures | Figure 6.6.3-1: UTM requests information from 5GC
1-3. USS/UTM obtains the aerial UE list in a geographical area by invoking the existing procedure of obtaining list of Aerial UEs in a geographic area in clause 5.3.4 of TS 23.256 [2].
4-5. USS/UTM requests the relative proximity analytics of the UEs obtained in steps 1... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.6.4 Impacts on services, entities and interfaces | UTM/USS:
- Obtain aerial UE list in a geographical area.
- Obtain the NWDAF analytics on relative proximity analytics of the aerial UEs.
- Obtain the sidelink positioning location results when certain trigger events occur. The trigger events are described in clause 6.20.4 of TS 23.273 [7], e.g. one trigger event occurs... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7 Solution #7: Mobility Enhancements for enforcements of NTZ | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.1 Key Issue mapping | This solution applies to Key Issue #3. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.2 Description | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.2.1 Introduction | The solution addresses the following aspects:
- How to ensure an aerial UE respects no-transmit zones. This includes the following scenarios:
- mobile network cells overlapping completely or partially with the NTZ and using the restricted frequency bands of the NTZ.
- support NTZ of any size, depending on regional requ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.2.2 Solution Overview | The solution assumes the following:
- NTZ information is provided to the PLMN functions (depending on the solution options described below) via OAM by external parties, with the idea that at national level there will be entities in charge of defining NTZs and providing related information to PLMNs.
Editor's note: Wheth... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.2.3 Extension of Service Restrictions for NTZs | In this solution component, a UAV UE supporting NTZ restrictions provides an indication in 5GMM of support of NTZ Restrictions.
The CN receives the NTZ information (e.g. via OAM from external party) and maps the NTZ information to a Restricted Transmission Area (RTA). If the AMF determines that the supporting UE is an ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.2.4 NTZ Restriction Policies | This component of the solution re-uses concepts similar to the PC5 policy configuration that was adopted in previous releases to define geofence where certain frequencies are not allowed. However, in the case of NTZs, a blocklist of frequencies associated to the specific area are provided, whereas in the case of PC5 a ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.2.5 Per-cell indication of the presence of NTZs: | For potential solutions where a per-cell indication is provided to UAV UEs on the presence of NTZs (independently of the mechanism adopted to do so by e.g. RAN solutions), three categories of UEs need to be considered:
1. new UEs (i.e. Rel-19) that support NTZ restriction functionality: in a cell where the NTZ indicati... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.2.6 Solution Architecture | No architectural modifications are assumed by the proposed solution. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.3 Procedures | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.3.0 General | NOTE: It is assumed that the following procedures take place when the UAV UE is outside an area corresponding to an NTZ. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.3.1 Extension of Service Restrictions for NTZs | Figure 6.7.3.1-1: Delivery of NTZ information via Service Area Restrictions
1. The UE registers indicating support for NTZ.
2. If the AMF determines that the supporting UE is an UAV UE, i.e. the UE provided indication of NTZ support, the UE has an aerial subscription, and after successful UUAA procedure when it is perf... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.3.2 NTZ Restriction Policies | Figure 6.7.3.2-1: Delivery of NTZ restriction policies to UAV UEs
1. The UE registers indicating support for NTZ.
2. If the AMF determines that the supporting UE is an UAV UE, i.e. the UE provided indication of NTZ support, the UE has an aerial subscription, and after successful UUAA procedure when it is performed, the... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.7.4 Impacts on services, entities and interfaces | The following entities are impacted:
- UE:
- indication of NTZ support for UAV UEs;
- receive and process NTZ information, and modify idle mode mobility and connected mode mobility based on received NTZ information as described in options above ;
- abstain from transmission in areas corresponding to NTZ;
- for per-cell... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.8 Solution #8: Network support for NTZ management | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.8.1 Key Issue mapping | This solution addresses part of KI#3 regarding non-NTZ-support UE. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.8.2 Description | This solution addresses Key Issue #3 "Support of No Transmit Zones".
In case that the UE doesn't support NTZ, e.g. legacy UE, both the UE and RAN side may not have effective solution to force the UE for following the NTZ setting, hence there is the need to have network support for UAV usage within the restricted area f... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.8.3 Procedures | Figure 6.8.3-1: Procedure for network support for NTZ
0. The AMF can store the NTZ information which is configured locally or obtained from the UTM/USS via UAS-NF/NEF.
1. The UE, which doesn't support functions defined for NTZs, e.g. legacy UE, sends a Registration request message and, and it shall provide a CAA-level ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.8.4 Impacts on Existing Nodes and Functionality | AMF:
- Obtain data from UTM/USS referring to NTZ and store it as NTZ information. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.9 Solution #9: Enabling NTZ support for aerial UEs | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.9.1 Key Issue mapping | This solution addresses KI#3 aspects. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.9.2 Description | The solution assumes that an aerial UE indicates its capability to respect no-transmit zones (NTZ), and UE's subscription data has a record about that, as Operators have to enforce the NTZ respect, and the subscription-based approach is one possibility, as described below.
Several options/alternatives are considered wh... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.9.3 Procedures | The main procedural steps to provision RAN nodes (gNB/eNB) with the NTZ information is shown in Figure 6.9.3-1.
Editor's note: The current procedures assume 5GC signalling. The adaptation for EPC is going to be handled during normative phase.
Figure 6.9.3-1: Procedure to provision RAN nodes (gNB/eNB) with the NTZ infor... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.9.4 Impacts on services, entities and interfaces | Impact depends on which options/alternatives selected for delivering NTZ information to UEs and RAN nodes and for updating them about any change from the AF/UTM. Overall, the impacts could be the following:
AF:
- Invoking a Naf_Authentication_Notification or a new service to request NTZ compliance from the network.
- R... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.10 Solution #10: Enabling 5GC support for multiple USS serving different geographical areas | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.10.1 Key Issue mapping | This solution addresses KI#1 aspect related to 5GC support for multiple UAS Service Suppliers (USS-s) serving different geographical areas that fully or partly fall within UAV’s flight path. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.10.2 Description | The focus in this scenario is with two USS-s – USS 1 serving a geographical area confined within tracking area (TA 1), TA 2 and TA 3 and USS 2 serving a geographical area confined within TA 4 and TA 5; each of the TAs has different number of cells, etc. see Figure 6.10.2-1.
Figure 6.10.2-1: USS-s serving different geog... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.10.3 Procedures | Procedures for USS changeover in cases when a serving USS triggers communication with a target USS to jointly determine UAV's flight path is shown in Fig. 6.10.3-1.
Figure 6.10.3-1: Procedure for UAV changeover from one USS to another serving different geographical areas
This procedure utilises Solution #1 of the NEF-a... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.10.4 Impacts on services, entities and interfaces | Impacts are similar as for Solution #1 (see clause 6.1.4) since this solution utilises pre-mission flight planning, if available. Additionality there may be other impacts such as:
AF/USS:
- receiving notification from NEF when a UAV enters/leaves a border cell/TA under responsibility of the current serving USS;
- provi... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.11 Solution #11: Multi-USS Support in 5GC | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.11.1 Key Issue mapping | This solution addresses KI#1, "Enhancement of NEF services to support service exposure and interactions between MNOs and UTM functions", focusing on the following aspect:
- The scenario of multiple USS serving different geographical areas corresponding to the UAV flight path. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.11.2 Description | The procedure for authentication and authorization of UAV by USS (UUAA) in clause 5.2 of TS 23.256 [2] allows a particular USS to authenticate and authorize the UAV when it Registers or establishes a PDU Session. In current release a UAV is served by single USS for the duration of the connectivity between the USS and t... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.11.3 Procedures | In 5GS, the following procedures are used for the authorization to support multiple USSs:
- The UE indicates multi-USS capability in the service level container.
- The procedure for UUAA-MM as specified in clause 5.2.2.2 of TS 23.256 [2], with the following enhancements:
- In step 2 and 3, an indication of multi-USS su... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.11.4 Impacts on services, entities and interfaces | UAS NF:
- Receives multi-USS support indication from AMF/SMF during UUAA procedures.
- Receives from USS and stores in UUAA context a list of serving USS info during UUAA procedures.
- Authorizes USS requests (location tracking, change of USS/AF session configuration) based on the list of serving USS info in the UUAA c... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.12 Solution #12: Support redundant connections for C2 communication reliability | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.12.1 Key Issue mapping | This solution addresses the C2 communication reliability aspect in key issues #1 "Enhancement of NEF services to support service exposure and interactions between MNOs and UTM function". |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.12.2 Description | To achieve C2 communication reliability in some scenarios, e.g. UAV is hovering in area for some critical work, a UAV can establish two redundant C2 connections, which can be either with the same UAV-C or UTM. For redundant C2 connections with the same control entities, existing redundant transmission mechanism with di... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.12.3 Procedures | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.12.3.1 UE initiates PDU Session establishment for 2 redundant PDU Sessions for C2 communications with a UAV-C for End-to-End reliability | Figure 6.12.3.1-1: Procedure for PDU Session establishment for 2 redundant C2 communications
0. The UAV has performed a successful UUAA with the USS.
1. The UE first initiates PDU session establishment request for establishing the first PDU session for C2 connection with the UAV-C. In the PDU Session establishment requ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.12.4 Impacts on services, entities and interfaces | USS/UTM:
- Add C2 redundant information in C2 aviation payload and C2 authorization payload for End-to-End reliability.
UE:
- Need to support dual connectivity for End-to-End reliability. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.13 Solution #13: Enhancement of NEF services for C2 communication assistance information | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.13.1 Key Issue mapping | This is a solution for Key Issue #1, in particular, this solution addresses whether and how to enhance NEF services to support service exposure and interactions between MNOs and UTM functions for supporting C2 communication reliability. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.13.2 Description | This solution proposes to enhance NEF services and enable USS/UTM to request NEF assistance for C2 communication reliability. This solution enables UAV to decide to use or change to other C2 connectivity based on the C2 connectivity related information received from the USS/UTM such that C2 communication reliability (e... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.13.3 Procedures | Figure 6.13.3-1: Procedure for C2 communication reliability support assisted by NEF
1. The UAV establishes a PDU Session for C2 communication as described in clause 5.2.3 of TS 23.256 [2].
2. Authorization for C2 over Uu is performed as described in clause 5.2.5 of TS 23.256 [2] if not performed at step 1.
3. The UAV r... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.13.4 Impacts on services, entities and interfaces | UAS NF/NEF:
- Enhance for supporting C2 connectivity assistance service.
USS/UTM:
- Enhance for providing C2 connectivity related information to UAV. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.14 Solution #14: C2 Communication Reliability with Redundant User Plane Paths | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.14.1 Description | The study aspect on whether and how to enhance NEF services to support service exposure and interactions between MNOs and UTM functions for supporting C2 communication reliability is contained in KI#1. This solution proposes to reuse the redundant user plane paths introduced in TS 23.501 [5] Annex F with changes and en... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.14.2 Procedures | This clause describes an approach to realize C2 communication reliability with multiple user plane paths. The approach assumes a RAN deployment where redundant coverage by multiple gNBs (in the case of NR) is generally available, and a UAV can connect to multiple gNBs independently.
The UAV with redundant connections w... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.14.3 Impacts on services, entities and interfaces | UAV:
- Support redundancy connections to same control entities with multiple gNBs.
AMF:
- Enhanced to enable reliability group for multiple connections of UAV with multiple gNBs, reusing existing parameters can mitigate that AMF does not identify redundant connections. |
7c76e660d457710d658498e24c37271e | 23.700-59 | 6.15 Solution #15: NTZ restriction Provisioning aspects |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.