hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
556719e8696c25b4ac3572453768229c | 22.843 | 5.5 Use case on the 3GPP network as an information source to the UTM | |
556719e8696c25b4ac3572453768229c | 22.843 | 5.5.1 Description | The UTM is a complex system in which actors outside the 3GPP System work to ensure the required safety level of UAS operations. For this reason, the UTM is defined by GUTMA (Global UTM Association) as “a system of stakeholders and technical systems collaborating in certain interactions, and according to certain regulat... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.5.2 Pre-conditions | A UTM exists which is capable of accepting a 3GPP network as data source. A partner 3GPP operator is prepared to supply information to the UTM based on the capabilities of the network. Agreements on trust, responsibility, liability, privacy, and data management have been made. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.5.3 Service Flows | 1. A UTM determines what data is required from the 3GPP network which can act as an information source.
2. Based on the capabilities of the 3GPP network, an operator begins to gather data according to agreements made with a UTM operator where the UTM provides the type of information and optional conditions regarding su... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.5.4 Post-conditions | The UTM has an increased situational awareness because of the increased data provided by the 3GPP network. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.5.5 Existing features partly or fully covering the use case functionality | Related requirements in TS 22.125 [3]:
[R-5.1-003] The 3GPP system shall enable a UAS to send UTM the UAV data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV, make & model, serial number, take-off weight, position, owner identity, owner address, owner contact details, owner c... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.5.6 Potential New Requirements needed to support the use case | [P.R 5.5.6-001] Based on operator policy and UTM’s request, the 5G system shall be able to provide UTM with a UEs’ location (specifically 5GC Location Services derived positioning or UE-derived positioning e.g. from GNSS) and identity.
[P.R 5.5.6-002] Subject to user consent and national or regional regulation, based o... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.6 Use case on supporting UAV inflight operations | |
556719e8696c25b4ac3572453768229c | 22.843 | 5.6.1 Description | For UAVs operated using the 3GPP network access, the network needs to ensure that the UAVs can use the network reliably and with adequate performance. UAV flight mission need to be monitored for the real-time performance and stability of flight control link to guarantee the safety and continuity of the flight.
5G netwo... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.6.2 Pre-conditions | In the logistics company, UAV A and UAV B are both individual terminals for express delivery and subscribe the communication service from the 5G network.
Operator A provides 5G network coverage and communication services for remote commands and control (C2) communication between UAV and UAV control platform.
The UTM re... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.6.3 Service Flows | Figure 5.6.3-1: Supporting UAV inflight monitoring
1. The logistics company uses UAV A and UAV B to perform delivery operations. UAVs planned flight paths shared a common portion, along waypoint #1 and waypoint #2.
2. UAV/UAV-C A and UAV/UAV-C B register in 5G network and can communicate with UTM though 5G network.
3. ... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.6.4 Post-conditions | UAV A and UAV B can finish their delivery tasks with the support of 5G network. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.6.5 Existing features partly or fully covering the use case functionality | Existing related service requirements are captured in 3GPP TS 22.125 [3] clause 6.2 "Network exposure for UAV services".
[R-6.2-001] The 3GPP system shall provide means to allow a 3rd party to request and obtain real-time monitoring the status information (e.g., location of UAV, communication link status) of a UAV.
[R-... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.6.6 Potential New Requirements needed to support the use case | [P.R 5.6.6-001] Based on operator’s policy, the 5G system shall be able to provide a method to monitor and provide a 3rd party with information about network conditions and QoS (e.g. bitrate, latency, reliability) along a UAV flight path.
[P.R 5.6.6-002] Based on operator’s policy, the 5G system shall be able to provid... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.7 Use case on UAV flight route tracking at Rendezvous points | |
556719e8696c25b4ac3572453768229c | 22.843 | 5.7.1 Description | Commercial UAV flights are usually BVLOS. Tracking the UAV flights to ensure that they are sticking to the planned route is critical to the success of the mission and the safety of the public. For UAVs that have network communication capability, cellular networks can greatly assist in UAV flight route tracking thanks t... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.7.2 Pre-conditions | A USS/UTM provides environmental surveillance services in an area. It regularly sends out UAVs to fly a planned route collecting environmental data. The UAV is not the subscriber UE of the 5G cellular network operator and can be considered as non-networked UAV for the 5G operator.
A 5G cellular network operator provide... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.7.3 Service Flows | 1. The USS/UTM requests tracking of one of more UAVs from the 5G operator.
2. The 5G network to track those non-network UAVs. The USS/UTM provides the planned flight route information to the 5G network (e.g., waypoints, ETA).
3. The 5G network start to track those UAV, such as requests selected ground stations to monit... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.7.4 Post-conditions | The UAV finishes the mission with USS/UTM reassured during the whole flight. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.7.5 Existing features partly or fully covering the use case functionality | Identification of UAVs which don’t have subscription with the 5G operator for DAA has been specified in Rel-18. Tracking for such UAVs is currently not covered in Rel-18 because release 18 only supports the capability to allow the 5G operator tracking of those UAVs which have the subscription with the 5G operator. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.7.6 Potential New Requirements needed to support the use case | [P.R 5.7.6-001] The 5G system shall be able to support a mechanism to enable a network operator to track a UAV which doesn’t have subscription with this network operator. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.8 Use case on UAV simultaneous traffic over two networks | |
556719e8696c25b4ac3572453768229c | 22.843 | 5.8.1 Description | Reliability of UAV traffic is a very important challenge and target for the aviation industry, e.g., for command and control (C2) or other critical data. One scenario of interest includes UAVs, provided with dual SIM/subscription, able to connect simultaneously via two networks for transferring different type of traffi... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.8.2 Pre-conditions | SafeSky UAV has dual subscription (dual SIM, or SIM and NPN credentials) to two different PLMNs (or a PLMN and an NPN). It is assumed that SafeSky has negotiated with both MNOs proper data policies for traffic generated by its UAVs over their respective networks (e.g., QoS, traffic profile/activity, charging, etc.).
UA... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.8.3 Service Flows | Based on UAV configuration policy:
1. SafeSky UAV registers to both PLMN1/NPN1 and PLMN2, using their respective home subscription.
2. When monitoring surveillance service is started, UAV connects with both networks.
3. UAV traffic is transferred simultaneously on both networks, where C2 communication with the UAV-C is... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.8.4 Post-conditions | The surveillance service runs smoothly, with no glitch in UAV operation and manoeuvring. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.8.5 Existing features partly or fully covering the use case functionality | There are no service requirements in TS 22.125 [3] about UAS multi-NW/PLMN support. Other requirements (e.g., from TS 22.261 [4] or TS 22.101 [5]) do not cover the specific target UAV scenarios and functionalities. Some examples of existing requirements are captured below:
[from TS 22.261 [4] sec. 6.18: Multi-network c... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.8.6 Potential New Requirements needed to support the use case | [PR.5.8-001] The 5G system shall be able to support service enablement layer exposure mechanisms for the UTM or other authorized 3rd party to provide the UAV application with configuration information to route different traffic across different PLMN connections simultaneously, e.g. C2 traffic via one PLMN and other dat... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.9 Use case on UAV traffic over alternative networks | |
556719e8696c25b4ac3572453768229c | 22.843 | 5.9.1 Description | One of the Aviation industry recommendations for UAV operation (and AAM - Advanced Air Mobility) is the ability to support robust reliability and flexible redundancy of critical communication links, including cellular, e.g., for Command and Control (C2) and other flight-critical communications.
Within the context of im... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.9.2 Pre-conditions | SkyTV UAV has dual SIM subscription to PLMN1 and PLMN2. It is assumed that SkyTV has negotiated with both MNOs proper data subscriptions for traffic generated by its UAVs (e.g., QoS, traffic profile/activity, charging, etc.).
UAV’s application is configured to use both PLMNs via both subscriptions (USIM1/USIM2), transf... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.9.3 Service Flows | 1. An outdoor marathon event is starting, and SkyTV UAV is set to follow the peloton for all the itinerary (20 miles). SkyTV service provider has configured the UAV application with specific policy on how to route traffic over the two subscribed PLMN networks.
2. Before the kick-off, UAV’s communication module using US... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.9.4 Post-conditions | SkyTV video service runs smoothly for all 20 miles, with no service degradation when transitioning in and out of PLMN-1 spotty coverage areas and the UAV is under control and monitored by USS/UTM and UAV-C all the time. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.9.5 Existing features partly or fully covering the use case functionality | There are no service requirements in TS 22.125 [3] about UAS multi-NW/PLMN support. Other requirements (e.g., from TS 22.261 [4] or TS 22.101 [5]) do not cover the specific target UAV scenarios and functionalities. Some examples of existing requirements are captured below:
[from TS 22.261 [4] sec. 6.18: Multi-network c... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.9.6 Potential New Requirements needed to support the use case | [PR 5.9.6-001] The 5G system shall be able to support service enablement layer exposure mechanisms for the UTM or other authorized 3rd party to provide the UAV application with configuration information to route and switch traffic between one active and one standby PLMN connection, e.g. for C2 communication reliability... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.10 Use case on UAV control in different aerial flight zones | |
556719e8696c25b4ac3572453768229c | 22.843 | 5.10.1 Description | 5G networks can provide connectivity to UAV for a variety of services, e.g., command and control, telemetry, remote ID, DAA, payload transfer (e.g., video), etc. In some scenarios, it would be beneficial to control and differentiate UAV operation and communication, e.g., regarding the use of specific network resources ... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.10.2 Pre-conditions | A UAV service provider (U-Serv), offering monitoring & surveillance UAV services in multiple cities of the country, has an agreement with PLMN-A operator, including the configuration of two different flight zones (for all cities) mapped to different parts of the territory and network, with the following UAV application... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.10.3 Service Flows | 1. 1. A U-Serv UAV, located in Zone A, is registered to PLMN-A and starts its daily surveillance service.
2. 2. The UAV detects it is in Zone A, e.g., if indicated by the network or based on UAV available information or pre-configuration, and connects to the network using the corresponding traffic policy for Zone A (no... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.10.4 Post-conditions | U-Serv UAV application can provide smooth service and is able to adapt its communication settings when flying across special locations/areas (zone B), based on UAV traffic policies and flight zone settings under control of UTM and network. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.10.5 Existing features partly or fully covering the use case functionality | None identified. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.10.6 Potential New Requirements needed to support the use case | [PR 5.10.6-001] The 5G system shall be able to support mechanisms for the UTM to configure different aerial flight zones where UAV application settings and communication QoS may be different, and provide network and UAV with means to identify those flight zones.
[PR 5.10.6-002] The 5G system shall be able to support me... |
556719e8696c25b4ac3572453768229c | 22.843 | 6 Consolidated potential requirements | |
556719e8696c25b4ac3572453768229c | 22.843 | 6.1 Network support and exposure for UAV usage | CPR #
Consolidated Potential Requirement
Original PR #
Comment
CPR 6.1-001
Based on operator’s policy, the 5G system shall be able to support a method to predict, monitor network conditions and QoS (e.g. bitrate, latency, reliability) and report to 3rd party along a continuous geographic planned flight path of a UAV at... |
556719e8696c25b4ac3572453768229c | 22.843 | 6.2 Safety and Security | CPR #
Consolidated Potential Requirement
Original PR #
Comment
CPR 6.2-001
The 5G system shall be able to detect that a connected UE is airborne, when the UE doesn’t have an aerial subscription..
PR 5.1.6-001
CPR 6.2-002
The 5G system shall support means to determine whether UTM supports regulatory requirements e.g., m... |
556719e8696c25b4ac3572453768229c | 22.843 | 7 Conclusion and recommendations | The present document contains several use cases and service requirements for enhanced UAV usage and safety. It is recommended to define normative service requirements based on the consolidated potential requirements identified in Section 6. Annex A (informative): Change history Change history Date Meeting TDoc CR Rev C... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 1 Scope | The present document describes use cases and aspects related to interconnect of SNPNs as well as Scalable SNPN Interconnect with dynamic connections.
Potential service requirements are derived for these use cases and are consolidated in a dedicated chapter.
The report ends with recommendations regarding the continuatio... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 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... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 3 Definitions of terms, symbols and abbreviations | |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
SNPN Credential Provider: Entity within the 5G system that creates and manages identity in... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
SNPN Standalone Non-Public Network |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 4 Overview | The present document captures a set of use cases and potential service requirements related to the following topics:
1. Scalable SNPN Interconnect with dynamic connections (to support SNPN cellular hotspots).
2. Interconnect of SNPNs |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5 Use cases | |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.1 Use case on Scalable SNPN Interconnect with dynamic connections | |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.1.1 Description | This use case relates only to SNPNs that provide services in a similar way as provided by WLAN hotspots.
Today's PLMNs have a centralized database of IP addresses of all operator nodes that connect to the inter-PLMN IP backbone network, including AAA Servers/Proxies. This information is used for firewall and Border Gat... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.1.2 Pre-conditions | 1) NetAbove is an Internet service provider that operates SNPNs and serves as a SNPN Credential Provider. As part of the subscription contract, NetAbove allows its subscribers to connect to SNPNs owned by a variety of companies (e.g., hospitality and convention centres, airports, government institutions, schools, resta... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.1.3 Service Flows | 1) Roy is a subscriber of NetAbove.
2) Roy is visiting a Kaffa Koffee shop and wants to access Kaffa Koffee’s famous entertainment system using his 5G-capable laptop.
3) Using the connection manager on his laptop, Roy selects his NetAbove subscription credentials for connection to Kaffa Koffee’s SNPN.
4) Kaffa Koffee’s... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.1.4 Post-conditions | 1) Once Roy’s laptop is connected to the Kaffa Koffee’s SNPN network, Roy can enjoy access to Kaffa Koffee’s entertainment system and access to the Internet.
2) After some time, Roy disconnects gracefully from Kaffa Koffee’s SNPN and the disconnection event is signalled to NetAbove’s SNPN Credential Provider server. |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.1.5 Existing features partly or fully covering the use case functionality | None. The existing interface for interconnect between SNPN and SNPN Credential Provider (aka Credentials Holder) relies on permanent signalling connection between the SNPN and the SNPN Credential Provider. |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.1.6 Potential New Requirements needed to support the use case | [PR 5.1.6-001] Based on the Standalone Non-Public Network (SNPN) configuration, the 5G system shall support a mechanism for a SNPN to be able to interconnect with a large number of SNPN Credential Providers with which the SNPN might not have preconfigured information detailing the IP addresses used by these SNPN Creden... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.2 Use case on Interconnect between SNPNs | |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.2.1 Description | SNPNs are expected to be deployed in government offices, banks, hotels, hospitals, schools, etc. in an administrative area. Each SNPN exposes its localized services.
Interconnect between different SNPN, subject to appropriate agreements, can make access to localized services seamless. Namely, when SNPNs, deployed by di... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.2.2 Pre-conditions | It is assumed that a hub & spoke model is deployed in a central hospital and family clinics for this service flow. SNPN-1 is the root, deployed in central hospital and SNPN-2 and SNPN-3 are leaves, deployed in family clinics #2 and #3, respectively. SNPN-1, SNPN-2 and SNPN-3 are connected to the backbone network and th... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.2.3 Service Flows | 1. An interconnect for a hub & spoke model is designed by a producer of SNPN-1, deployed in the central hospital. The interconnect describes a collection of interconnectivity endpoints for the root and branches and how to access to the interconnectivity endpoints from SNPN-1, SNPN-2 and SNPN-3.
2. The interconnect prov... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.2.4 Post-conditions | The interconnect between SNPN-1, SNPN-2 and SNPN-3 is realised using the selected topology model and 5GS endpoints, and then the SNPNs can exchange data. |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.2.5 Existing features partly or fully covering the use case functionality | Further existing features that partly or fully cover the use case functionality are FFS. |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.2.6 Potential New Requirements needed to support the use case | [PR 5.2.6-001] Subject to SNPNs operators’ agreement, the 5G system shall be able to support mechanisms to enable interconnect between standalone non-public networks.
[PR 5.2.6-002] Subject to SNPNs operators’ agreement, the 5G system shall be able to support mechanisms for a selection of 5GS endpoints for SNPNs’ inter... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.3 Use case on interconnection of standalone naval non-public networks | |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.3.1 Description | This use case deals with self-organizing, broadband, low latency, connectivity solutions between ships in a fleet. It can apply to different sectors including military, coast guard fleet, or fleet of fishing vessels… in short to any situation where intra-fleet communication and coordination is needed.
In this use case,... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.3.2 Pre-conditions | User A terminal is loaded with a USIM that is registered to SNPN A.
SNPN A has local coverage on-board ship A and SNPN B has coverage on-board ship B.
Service B is offered by an application B instantiated on ship B. Application B has 5G connectivity through SNPN B.
User A has needed credentials to access service B. |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.3.3 Service Flows | 1) User A on-board ship A and attached to the on-board SNPN A establishes a PDU session to access service B.
2) In the process of establishing the PDU session, the 5G system identifies that communication with service B shall be routed from SNPN A to SNPN B through SNPN D to fulfil the quality of service required by ser... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.3.4 Post-conditions | User A is attached to SNPN A. |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.3.5 Existing features partly or fully covering the use case functionality | None |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.3.6 Potential New Requirements needed to support the use case | [PR 5.3.6-001] Based on SNPN configuration and subject to SNPN operator’s policy, the 5G system shall be able to support interconnect of standalone non-public networks through links established on a temporary basis forming a group of interconnected Standalone Non-Public Networks with a variable topology.
[PR 5.3.6-002]... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.4 Use case on mobility in a group of interconnected standalone naval non-public networks | |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.4.1 Description | This use case deals with self-organizing, broadband, low latency, connectivity solution between ships in a fleet. It is an extension of the use case 5.3 on interconnection of standalone naval non-public networks.
This network architecture, unusual in the world of public cellular networks, will however have to support a... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.4.2 Pre-conditions | User A terminal is loaded with a USIM that is registered to SNPN A.
SNPA A has local coverage on-board ship A and SNPN B has coverage on-board ship B.
Service B is offered by an application B hosted on ship B. Application B has 5G connectivity through SNPN B.
User A has needed credentials to access service B. |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.4.3 Service Flows | 1) User A on-board ship A and attached to the on-board SNPN A establishes a PDU session to access service B.
2) User A takes a speed boat, equipped with necessary communication equipment to deploy locally SNPN around the speed boat and to enable connectivity with any vessels in the fleet through wireless links. Once it... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.4.4 Post-conditions | User A is attached to SNPN B and still in communication with service B. |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.4.5 Existing features partly or fully covering the use case functionality | None |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.4.6 Potential New Requirements needed to support the use case | [PR 5.4.6-001] Based on SNPN configuration and subject to SNPN operator’s policy, the 5G system shall be able to support discovery, addition and authentication, or detachment of Standalone Non-Public Networks in a group of interconnected Standalone Non-Public Networks without interrupting ongoing communications.
[PR 5.... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.5 Use case on quality of service differentiation and resource prioritization in a group of interconnected standalone naval non-public networks | |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.5.1 Description | This use case deals with self-organizing, broadband, low latency, connectivity solution between ships in a fleet. It is an extension of the use case 5.3 on interconnection of standalone naval non-public networks.
In this use case, several users located on different ships are involved in a real time mission critical com... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.5.2 Pre-conditions | All User Equipment are loaded with a USIM and are registered to their local SNPN.
A MCX service is available onboard ship A (called MCX A in the following section)
All users involved in the use case have needed credentials to access MCX A service. |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.5.3 Service Flows | 1) User A requests a real time video streaming involving a MCX server located onboard ship A to users B and D respectively located on ship B and D.
2) If the requested quality of service can be reached, users A, B, D on-board ships A, B, D, and attached to the on-board SNPNs A, B, D, can establish a PDU session to acce... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.5.4 Post-conditions | Users A, B, D are attached to SNPN A, B, D and still in communication with MCX service A. |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.5.5 Existing features partly or fully covering the use case functionality | None |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 5.5.6 Potential New Requirements needed to support the use case | [PR 5.5.6-001] Based on SNPN configuration and subject to SNPN operator’s policy, the 5G system shall be able to support prioritization of resources for a service offered by a Standalone Non-Public Network that is consumed by users attached to other interconnected Standalone Non-Public Networks.
[PR 5.5.6-002] Based on... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 6 Consolidated requirements | |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 6.1 Groups of interconnected SNPNs | The potential requirements for enabling groups of interconnected SNPNs correspond to the use cases in clauses 5.2 to 5.5 and are listed in Table 6.1-1.
A group of interconnected SNPNs consists of one or more pairs of interconnected SNPNs. The determination of whether a given SNPN can or should be able to participate wi... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 6.2 Consolidated requirements for enabling of SNPN cellular hotspots | The potential requirements for enabling of SNPN cellular hotspots correspond to the use case in clause 5.1 (Scalable SNPN Interconnect with dynamic connections) and are listed in Table 6.2-1.
The requirements for SNPN cellular hotspots are intended to enable support of connectivity hotspots based on 3GPP 5G network tha... |
6fd8bf2627f82827816dd131ee257054 | 22.848 | 7 Conclusions and recommendations | This technical report identifies several use cases and potential new requirements related to the interconnect of SNPNs with two aspects: - Groups of interconnected SNPNs - Enabling of SNPN cellular hotspots (Scalable SNPN Interconnect with dynamic connections) The resulting service requirements have been consolidated i... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 1 Scope
| This study investigates ongoing AI/ML work in TSG CT, TSG RAN and TSG SA Working Groups, identifies instances of any potential misalignment and/or inconsistencies and provides information on any potential outcome to the respective WGs to resolve any issues with appropriate SA-level co-ordination as necessary.
The stud... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 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.
-... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 3 Definitions of terms and abbreviations
| |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] apply.
|
fba61181a0f9993b18933fec82e25a47 | 22.850 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply.
|
fba61181a0f9993b18933fec82e25a47 | 22.850 | 4 Background
| In Rel-18 and Rel-19, most working groups in TSG SA, TSG CT and TSG RAN have already performed SIs and/or have WIs relating to the AI/ML topic. These activities address different usage scenarios and associated specific use cases exploiting AI/ML for the operation of the 3GPP System ranging from radio interface operatio... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 5 AI/ML related activities in all Working Groups
| |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 5.1 General
| This clause investigates and identifies AI/ML related activities of all working groups of Rel-18 features and Rel-19 studies and work items in TSG CT, TSG RAN and TSG SA Working Groups, as given in the list in Table 5.1-1.
Table 5.1-1: List of Rel-18 work items and Rel-19 studies and work items for AI/ML activities in... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.