hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.28 Use Case on user identities in a digital asset container | |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.28.1 Description | To ensure a seamless user experience across metaverse services, network operators offer digital asset management services that allow users to certify certain information, such as IDs. These services support multiple user identities, each representing different aspects of the user's life, such as their professional role and private life. As a result, each user identity may have its own set of information stored in the associated digital asset container, and this information can be managed differently based on the security requirements of the service. For example, the information associated with virtual banking requires a higher level of security in mobile communication due to the sensitive nature of the information, compared to that associated with virtual gaming. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.28.2 Pre-conditions | Bank B offers virtual financial services, e.g. avatar-based calls with financial managers, and the deposit and withdrawal of digital money through its virtual banks.
Mobile Operator T has established service level agreements with Bank B to provide multimedia communication services for virtual banking. Moreover, T provides digital asset management services for its subscribers, and some of this information is associated with the user's activities in Bank B.
Shaun, a senior employee at Bank B, has stored work-related digital assets in his digital asset container, which is supported by Mobile Operator T. This information includes his work ID, which is used to access Bank B's confidential database, and professional-looking avatar (dressed in a suit with Bank B’s watermark). Additionally, Shaun's digital asset container holds other digital assets for his private life, such as a cartoon avatar. Recognizing the importance of data security, Shaun restricts his access to work-related information in selected locations, such as when he is physically in the office. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.28.3 Service Flows | 1) Shaun registers with T by a UE that has a subscription with T. During his commute, he buys some digital clothes for his avatars in a virtual shop, which are then stored in his digital asset container.
2) Shaun arrives at his office. Having been authenticated by T and bank B, he initials a multimedia session with a customer. During the session, he uses his work ID to access the customer’s digital safe deposit box managed by B.
3) B assigns Shaun a new work ID as he obtains permission to highly sensitive business information of B.
4) Shaun requests to update his work ID in the digital asset container.
5) With T confirming his presence in the office building, Shaun is able to successfully update his work ID. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.28.4 Post-conditions | Shaun is able to access highly confidential information using his updated work ID when he is in the office. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.28.5 Existing features partly or fully covering the use case functionality | The functional requirements for user identity are captured in TS 22.101 clause 26a [4]. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.28.6 Potential New Requirements needed to support the use case | [PR 5.28.6-1] The 5G system shall be able to associate information with user identities in the digital asset container for a user.
[PR 5.28.6-2] Subject to operator policy, the 5G system shall be able to support users to define conditions (e.g. based on user location information) to restrict the access to, and management of, digital assets associated with user identities. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 6 Considerations | The task of determining impacts on regulatory services is difficult, as work on metaverse services is still being defined. Furthermore, regulations and policies related to metaverse services are still being defined in various regions. It is expected that the 5G system will meet regional/national regulatory rules and operator policy when supporting the use of metaverse services. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 7 Consolidated potential requirements and KPIs | |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 7.1 Consolidated potential requirements | |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 7.1.1 Localized Mobile Metaverse Service Functionality | Table 7.1.1-1 – Localized Mobile Metaverse Service Functionality Consolidated Requirements
CPR #
Consolidated Potential Requirement
Original PR #
Comment
[CPR 1.1]
Subject to operator policy, the 5G system shall provide a means to define and expose to an authorized third party a spatial anchor, i.e. an association between a physical location (a point or volume in three dimensional space) and service information.
NOTE: Service information can include information to enable users to discover and access services, e.g. type of service, URLs, configuration data, the distance between the user and the spatial anchor, etc.
[PR 5.1.6-1]
[PR 5.1.6-2]
[PR 5.1.6-3]
[PR 5.4.6-2]
[PR 5.4.6-3]
[CPR 1.2]
Subject to operator policy, the 5G system shall enable an authorized third party to request the information associated with a specific spatial anchor.
NOTE: How the service and location information is used by the third party to access a mobile metaverse server and the AR media itself is out of scope of this requirement.
[PR 5.4.6-4]
[CPR 1.3]
Subject to operator policy, the 5G system shall provide an authorized third party a means to define authorization to access spatial anchor information and to manage the spatial anchor(s), e.g. add, remove or modify spatial anchors.
[PR 5.4.6-5]
[CPR 1.4]
Subject to operator policy, regulatory requirements and user consent, the 5G system shall provide a means for a UE to provide sensor data, (e.g. from UE sensors, cameras, etc.) to the network in order to derive localization information, e.g. to produce or modify a spatial map or discover or find spatial anchors. The 5G system shall enable an authorized third party to obtain all of the spatial anchors located in a given three-dimensional area.
NOTE: How an authorized third party identifies which three-dimensional area to request spatial anchors in is not in scope of the 3GPP standard. Spatial localization and mapping information could be used to identify areas of interest.
[PR 5.5.6.1-1]
[PR 5.5.6.1-2]
[PR 5.5.6.2-2]
[PR 5.5.6.2-3]
[PR 5.4.6-3]
[CPR 1.5]
Subject to operator policy and regulatory requirements, the 5G system shall support mechanisms to expose a spatial map or derived localization information to authorized third parties.
[PR 5.5.6.1-3]
[CPR 1.6]
Subject to operator policy, regulatory requirements and user consent, the 5G System shall be able to process and expose information related to a UE’s location and direction of orientation to authorized third parties.
NOTE: This requirement does not affect the ability of regulatory services, e.g., legal intercept service, to access required information without consent of the user.
[PR 5.19.6-1] |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 7.1.2 Digital representation of users and avatar functionality | Table 7.1.2-1 – Digital representation of users and avatar functionality Consolidated Requirements
CPR #
Consolidated Potential Requirement
Original PR #
Comment
[CPR 2.1]
The 5G system shall support 5G CN to provide real-time feedback in support of conversational XR communication among multiple users simultaneously.
NOTE: The feedback can include information such as network condition, achieved QoS. Such information can be used by the IMS, for example, to trigger the codec negotiation.
[PR 5.3.6.2-1]
[CPR 2.2]
Subject to user consent, the 5G system (including IMS) shall support multimedia conversational communications between two or more users including transfer of real time avatar media and audio media.
NOTE 1: Avatar media can be transmitted on both uplink and downlink.
NOTE 2: Confidentiality of the data used to produce the avatar (e.g. from the UE cameras, etc.) is assumed.
[PR 5.11.6-1]
[PR 5.22.6-1]
[PR 5.11.6-2]
[PR 5.11.6-3]
[PR 5.7.6-3]
[CPR 2.3]
Subject to user consent, the 5G system (including IMS) shall support change of media types between video and avatar media for parties of a multimedia conversational communication.
[PR 5.11.6-4]
[CPR 2.4]
The 5G system (including IMS) shall support transcoding between media such as text, GTT, video and avatar media in multimedia conversational communications.
NOTE 1: Text, video or other media could allow a party to control the appearance of its avatar, e.g. to express behaviour, movement, affect, emotions, etc.
NOTE 2: The transcoding of media enables avatar communication, e.g. in scenarios in which UE participating in an IMS call or other service does not support e.g. FACS, encoding avatar media, generating avatar media, etc.
[PR 5.11.6-5]
[PR 5.26.6-2]
[PR 5.26.6-3]
[PR 5.26.6-4]
[CPR 2.5]
Subject to operator policy, regulatory requirements, and user consent, the 5G system (including IMS) shall support the capabilities of rendering the avatar based on the body movement information (e.g. body motion or facial expression) of a human user.
[PR 5.16.6.2-6]
[CPR 2.6]
The 5G system (including IMS) shall support the encoding of sensor data capturing the facial expression and movement and gestures of a person, in a standard form.
NOTE: The actual transmission and rendering of facial expression and movement and gestures of a person within a multimedia conversational communication is subject to that person’s consent.
[PR 5.26.6-1]
[PR 5.16.6.2-5]
[PR 5.16.6.2-6]
[CPR 2.7]
The 5G system (including IMS) shall support compensating for the end-to-end communication latency between the users and/or objects involved in a multimedia conversational communication prior/during rendering the digital representation (e.g. avatar) of the users and/or objects involved (e.g. by using a predictive digital representation model).
[PR 5.9.6.3]
[PR 5.9.6.4]
[CPR 2.8]
Subject to operator policy and regulatory requirements, the 5G system shall support mechanisms to uniquely identify an avatar and associate the avatar with a subscriber and to expose this association to authorized third parties.
[PR 5.18.6-1]
[PR 5.24.6-1] |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 7.1.3 Operational efficiency, exposure, and coordination of mobile metaverse services | Table 7.1.3-1 – Operational efficiency, exposure, and coordination of mobile metaverse services Consolidated Requirements
CPR #
Consolidated Potential Requirement
Original PR #
Comment
[CPR 3.1]
Subject to operator policy, the 5G system shall support a mechanism that enables flexible adjustment of communication services based on e.g. the type of devices (e.g., wearables), or communication duration (e.g. more than one hour), such that the services can be operated with reduced energy utilization.
NOTE: Metaverse service experience over an extended period of time (e.g. 2h) requires significant power consumption by the UE. In some cases, a device with no external power supply cannot sustain downloading and rendering of media over a long interval, e.g. for the duration of an entire feature film or athletic event.
[PR 5.7.6-1]
[PR 5.7.6-2]
[CPR 3.2]
The 5G system shall be able to provide a means to associate and coordinate data flows related to one or multiple UEs e.g. associated with the same object in digital twin applications provided by the mobile metaverse service.
[PR 5.20.6-1]
[PR 5.20.6-2]
[PR 5.20.6-3]
[CPR 3.3]
Subject to operator policy, regulatory requirements and user consent, the 5G system (including IMS) shall be able to expose network performance information (e.g., observed or predicted bitrate, latency or packet loss) related to one or more users to an authorized third party metaverse application.
NOTE: The network performance information can be per UE and take into account all available access network types, i.e. 3GPP and non-3GPP.
[PR 5.25.6-1]
[PR 5.9.6-2]
The addition was motivated by the change in 22.856 CR0007.
[CPR 3.4]
Subject to operator policy, the 5G system (including IMS) shall support a mechanism, including enabling one or more authorized third party(ies), to coordinate multiple service data flows of a single mobile metaverse service delivered to/from one or more UE(s). Multiple UEs may be associated with one user/location or different users at different locations potentially using different access networks, i.e. 3GPP and non-3GPP.
NOTE 1: Coordination refers to the ability to provide an acceptable level of user experience for a given service, e.g. based on latency and synchronization constraints (due to multiple sources or long distance between UEs/users). This can be based on a quantitative bound.
NOTE 2: It is not assumed that it is always possible to coordinate and provide the same capabilities regardless of whether 3GPP or non-3GPP access is used.
[PR 5.27.6-3]
[PR 5.9.6-1]
[PR 5.3.6.2-3]
[PR 5.25.6-2]
[PR 5.10.6-1]
[PR 5.12.6-1]
The addition was motivated by the change in 22.856 CR0007.
[CPR 3.5]
The 5G system shall enable the coordination of diverse media, transmitted to a UE from one or more mobile metaverse services associated with a physical location, to be combined to form a localized service experience.
[PR 5.1.6-4]
[PR 5.4.6-1]
[CPR 3.6]
Subject to operator policy, the 5G system shall support exposure mechanisms enabling an authorized third party to determine one or more subscribers to whom mobile metaverse media can be distributed in a resource efficient manner.
[PR 5.27.6-1]
[CPR 3.7]
Subject to operator policy and user consent, the 5G system shall support a means to provide resource efficient communication of third party mobile metaverse media to one or more subscribers.
[PR 5.27.6-2]
[CPR 3.8]
The 5G system shall provide a mechanism to maintain consistent user experience, for a given UE, when XR media from different mobile metaverse services have different communication performance, e.g., resolution, latency or packet loss.
[PR 5.8.6-1]
[PR 5.27.6-5] |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 7.1.4 Security and Privacy aspects of mobile metaverse services | Table 7.1.4-1 – Security and Privacy aspects of mobile metaverse services Consolidated Requirements
CPR #
Consolidated Potential Requirement
Original PR #
Comment
[CPR 4.1]
Subject to operator policies, regulatory requirements and user consent, the 5G system shall be able to support mechanisms to expose to a trusted third party (e.g. the conference focus) the result of the UE authenticating the user.
NOTE: How a UE authenticates the user's identity at the terminal equipment, e.g. using biometrics, is out of scope of the present document.
[PR 5.3.6.2-2]
[CPR 4.2]
Subject to operator policy, regulatory requirements and user consent, the 5GS shall support mechanisms to authorize Spatial Localization Service.
[PR 5.5.6.2-1]
[CPR 4.3]
Subject to operator policy, regulatory requirements and user consent, the 5G system shall be able to authorize the avatar to be used in mobile metaverse services.
[PR 5.24.6-2]
[CPR 4.4]
Subject to operator policy, regulatory requirements and user consent, the 5G system shall provide time-bound authorization for specified subscribers to use an avatar in mobile metaverse services.
[PR 5.24.6-3]
[PR 5.24.6-4]
[PR 5.24.6-5]
[CPR 4.5]
Subject to operator policy, regulatory requirements and user consent, the 5G system shall be able to identify the subscriber who has the right to use an avatar in mobile metaverse services.
[PR 5.24.6-5]
[CPR 4.6]
Subject to operator policy, regulatory requirements and subscriber consent, the 5G system shall provide a means to temporarily authorize a third party to use a subscriber’s digital representation and access specific multimedia communication services on behalf of the subscriber, including not by means of a UE, with restrictive conditions e.g., authorized list of parties.
[PR 5.17.6-1] |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 7.1.5 Digital Asset Management | Table 7.1.5-1 – Digital Asset Management Consolidated Requirements
CPR #
Consolidated Potential Requirement
Original PR #
Comment
[CPR 5.1]
Subject to operator policy, regulatory requirements and user consent, the 5G system shall be able to provide functionality to store digital assets associated with a user, and to remove such digital assets associated with a user.
[PR 5.13.6-1]
[PR 5.15.6-1]
[PR 5.16.6.2-1]
[CPR 5.2]
Subject to operator policy, regulatory requirements and user consent, the 5G system shall provide a means to allow a user to securely access and update their digital assets.
[PR 5.13.6-1]
[PR 5.15.6-1]
[PR 5.16.6.2-1]
[CPR 5.3]
Subject to user consent, the 5G system shall be able to allow a trusted third party to retrieve the digital asset(s) associated with a user, e.g. when the user accesses a specific application.
NOTE: When a user accesses an immersive mobile metaverse service, the authorized third party (service provider) could obtain relevant digital assets of a user associated with that service.
[PR 5.13.6-2]
[PR 5.13.6-3]
[PR 5.14.6-1]
[PR 5.15.6-2]
[CPR 5.4]
Subject to operator requirements and regulatory requirements, the 5G system shall provide secure means to authorize the use of digital assets associated with a user (e.g. digital assets belonging to a third party customer).
[PR 5.16.6.2-2]
[PR 5.13.6-5]
[PR 5.15.6-3]
[CPR 5.5]
The 5G system shall provide mechanisms to certify the authenticity of the digital assets associated with a user.
[PR 5.13.6-4]
[CPR 5.6]
The 5G system shall be able to associate a stored digital asset with one or more User Identities.
[PR 5.28.6-1]
[CPR 5.7]
Subject to operator policy, regulatory requirements and user consent, the 5G system shall support a mechanism for users to define conditions (e.g. based on user location information) to restrict the access to, and management of, stored digital assets associated with User Identity.
[PR 5.28.6-2]
[CPR 5.8]
The 5G system shall support mechanisms to request specific formats of stored digital assets associated with a user by an authorized mobile metaverse service.
NOTE: The main use case considered during development of this requirement was that stored digital assets such as avatar representation can be provided at different levels of graphical accuracy.
[PR 5.14.6-2] |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 7.1.6 Charging requirements for mobile metaverse services | Table 7.1.6-1 – Consolidated Requirements on charging for mobile metaverse services
CPR #
Consolidated Potential Requirement
Original PR #
Comment
[CPR 6.1]
The 5G system shall be able to collect charging information for the actions related to spatial anchors, where a third party creates, deletes or modifies a spatial anchor or associated service information.
NOTE: It is assumed that exposure of network anchors and associated service information can be a service provided by a network operator to third parties.
[PR 5.4.6-6]
[PR 5.4.6-7]
[CPR 6.2]
The 5G system shall support the collection of charging information associated with the exposure of a spatial map or derived localization information to authorized third parties.
[PR 5.5.6.1-4]
[CPR 6.3]
The 5G system shall support the collection of charging information associated with the production or modification of a spatial map on behalf of an authorized third party.
[PR 5.5.6.1-5]
[CPR 6.4]
The 5G system shall support the collection of charging information associated with exposing spatial location service information to authorized third parties.
[PR 5.5.6.2-4]
[CPR 6.5]
The 5G system shall support collection of charging information associated with initiating and terminating avatar call.
[PR 5.11.6-6]
[PR 5.17.6-2]
[CPR 6.6]
The 5G system shall be able to collect charging information for transcoding services associated with avatar call.
[PR 5.26.6-5]
[CPR 6.7]
The 5G system shall be able to collect charging information associated with distribution of third party mobile metaverse media to one or more subscribers.
[PR 5.27.6.4]
[CPR 6.8]
The 5G system shall be able to collect charging information per UE or per application, related to the use of digital assets associated with a user (e.g. typically a human user with a certain subscription).
[PR 5.16.6.2-3]
[PR 5.16.6.2-4]
[PR 5.17.6-2]
[CPR 6.9]
The 5G system shall be able to collect charging information per UE for managing the digital assets associated with a user (e.g. typically a human user with a certain subscription) or a third party.
NOTE: A third party who has digital assets could be an enterprise customer having service level agreement with the operator.
[PR 5.16.6.2-3] |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 7.2 Consolidated potential KPIs | The 5G system shall support various mobile metaverse services with the following KPIs.
NOTE: Unless stated otherwise, the “Max allowed end-to-end latency” refers to the maximum transmission delay expected between a UE and the mobile metaverse server or vice-versa.
Use Cases
Characteristic parameter (KPI)
Influence quantity
Remarks
Max allowed end-to-end latency
Service bit rate: user-experienced data rate
Reliability
Area Traffic capacity
Message size (byte)
Transfer Interval
Positioning accuracy
UE Speed
Service Area
5G-enabled Traffic Flow Simulation and Situational Awareness
(NOTE 2)
[5-20] ms (NOTE 1)
[10~100] Mbit/s
[25]
(NOTE 6)
> 99.9%
[~39.6] Tbit/s/km2
(NOTE 5)
-
20~100 ms
(NOTE 3)
-
< 250 km/h
City or Country wide
(NOTE 4)
UL
Collaborative and concurrent engineering
[≤10] ms
[14]
(NOTE 7)
[1-100] Mbit/s
[14]
[> 99.9%]
[14]
[1.55] Tbit/s/km2
(NOTE 8)
Video: 1500
Audio: 100
[14]
-
-
Stationary or Pedestrian
typically
< 100 km2
(NOTE 9)
UL and DL audio/video
[5] ms UL
[1-50] ms DL
[14]
(NOTE 7)
[<1] Mbit/s
[14]
[> 99.9%] (without compression)
[> 99.999%] (with compression (NOTE 10))
[26]
[2.25] Tbit/s/km2
(NOTE 8)
1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48
[14]
0.25-10 ms
[14]
UL and DL haptic feedback
Metaverse-based Tele-Operated Driving
(NOTE 16)
[100] ms [25] (NOTE 11)
[10~50] Mbit/s [25]
99% [25]
[~360] Mbit/s/km2
(NOTE 14)
-
20~100 ms [25]
(NOTE 12)
[10] cm [25]
[10-50] km/h (vehicle) [25]
Stationary/Pedestrian (user)
Up to 10km radius [25]
(NOTE 13)
UL real-time vehicle data (video streaming and/or sensor data) [25]
[20] ms [25]
[0.1~0.4] Mbit/s [25]
99,999% [25]
[~4] Mbit/s/km2
(NOTE 14)
Up to 8Kb
[25]
20 ms [25]
(NOTE 12)
[10] cm [25]
[10-50] km/h (vehicle) [25]
Stationary/Pedestrian (user)
Up to 10km radius [25]
(NOTE 13)
DL control traffic (commands from the remote driver) [25].
1-20 ms
(NOTE 15)
16 kbit/s -2 Mbit/s
(without haptic compression encoding);
0.8 - 200 kbit/s
(with haptic compression encoding)
(NOTE 15)
99.999%
(NOTE 15)
[~20] Mbit/s/km2
(NOTE 14)
2-8 (1 DoF) (NOTE 15)
Stationary/Pedestrian (user)
Up to 10km radius [25]
(NOTE 13)
Haptic feedback
Viewports streaming from rendering device to AR glasses through direct device connection
(tethered/relaying case)
(NOTE 17)
10 ms (i.e., UL+DL between AR Glasses display and the rendering UE) (NOTE 18)
[200-2000] Mbit/s
99.9 %
(NOTE 18)
-
-
-
-
Stationary or pedestrian (between rendering device and AR glasses)
Up to direct device connection ranging
Immersive AR interactive experience: tethered link
Pose information from AR glasses to rendering device through direct device connection
(tethered/relaying case)
(NOTE 17)
5 ms
(NOTE 18)
[100-400] Kbit/s
(NOTE 18)
99.9 %
(NOTE 18)
-
-
-
-
Stationary or pedestrian (between rendering device and AR glasses)
Up to direct device connection ranging
Movie streaming from metaverse server to the rendering device
(NOTE 20)
Only relevant for live streaming.
[1-5] s in case of live streaming
[0.1-50] Mbit/s (i.e., covering a complete OTT ladder from low resolution to 3D-8K)
(NOTE 19)
99.9 %
-
-
-
-
[up to 500 km/h]
-
Immersive AR interactive experience: NG-RAN multimodal communication link
Avatar information streaming between remote UEs (end to end)
10 ms (i.e., 20ms between both UEs excluding metaverse server processing time)
(NOTE 22)
[0.1-30] Mbit/s
(NOTE 21)
99.9 %
-
-
-
-
[up to 500 km/h]
-
Interactive data exchange: voice and text between remote UEs (end to end)
(NOTE 22)
10 ms (i.e., 20ms between both UEs excluding metaverse server processing time)
[0.1-0.5] Mbit/s
99.9 %
-
-
-
-
[up to 500 km/h]
-
NOTE 1: The mobile metaverse server receives the data from various sensors, performs data processing, rendering and provide feedback to the vehicles and users.
NOTE 2: Examples of typical data volume including 1) camera: 10 Mbit/s per sensor (unstructured), 2) LiDAR: 90 Mbit/s per sensor (unstructured), 3) radar: 10 Mbit/s per sensor (unstructured), and 4) real-time Status information including Telemetry data: [< 50 kbit/s] per sensor/vehicle/VRU (structured). This is to support at least 80 vehicles and 1600 users present at the same location (e.g. in an area of 40m*250m) to actively enjoy immersive metaverse services for traffic simulation and traffic awareness, the area traffic capacity is calculated considering 2 cameras, 2 Radars, 2 LiDARs on road side, 1600 user’s smart phones and 80 vehicles with 7 cameras, 4 radar and 2 LiDAR for each vehicle.
NOTE 3: The frequency considers different sensor types such as Radar/LiDAR (10Hz) and camera (10~50Hz).
NOTE 4: The service area for traffic flow simulation and situational awareness depends on the actual deployment, for example, it can be deployed for a city or a district within a city or even countrywide. In some cases a local approach (e.g. the application servers are hosted at the network edge) is preferred in order to satisfy the requirements of low latency and high reliability.
NOTE 5: The calculation is this table is done per one 5G network, in case of N 5G networks to be involved for such use case in the same area, this value can be divided by N.
NOTE 6: User experienced data rate refers to the data rate needed for the vehicle or human, the value is observed from industrial practice.
NOTE 7: The network based conference focus is assumed, which receives data from all the participants, performs rendering (image synthesis), and then distributes the results to all participants. As rendering and hardware introduce some delay, the communication delay for haptic feedback is typically less than 5ms.
NOTE 8: To support at least 15 users present at the same location (e.g. in an area of 20m*20m) to actively enjoy immersive Metaverse service concurrently, the area traffic capacity is calculated considering per user consuming non-haptic XR media (e.g. for video per stream up to 40000 kbit/s) and concurrently 60 haptic sensors (per haptic sensor generates data up to 1024 kbit/s).
NOTE 9: In practice, the service area depends on the actual deployment. In some cases a local approach (e.g. the application servers are hosted at the network edge) is preferred in order to satisfy the requirements of low latency and high reliability.
NOTE 10: The arrival interval of compressed haptic data usually follow some statistical distributions, such as generalized Pareto distribution, and Exponential distribution [26].
NOTE 11: The end-to-end latency does not include sensor acquisition or actuator control on the vehicle side, processing, and rendering on the user side (estimated additional 100ms total). Target e2e user experienced max delay depends on reaction time of the remote driver (e.g. at 50km/h, 20ms means 27cm of remote vehicle movement).
NOTE 12: UL data transfer interval around 20ms (video) to 100ms (sensor), DL data transfer interval (commands) around 20ms.
NOTE 13: The service area for teleoperation depends on the actual deployment; for example, it can be deployed for a warehouse, a factory, a transportation hub (seaport, airport etc.), or even a city district or city. In some cases, a local approach (e.g., the application servers are hosted at the network edge) is preferred to satisfy low latency and high-reliability requirements.
NOTE 14: The area traffic capacity is calculated for one 5G network, considering 4 cameras + sensors on each vehicle. Density is estimated to 10 vehicles/km2, each of the vehicles with one user controlling them. [25]
NOTE 15: KPI comes from [5] clause 7.11 “remote control robot” use case.
NOTE 16: Examples of typical data volume including 1) ~8Mbps video stream. Four cameras per vehicle (one for each side): 4*8=32Mbps. 2) sensor data (interpreted objects), assuming 1 kB/object/100 ms and 50 objects: 4 Mbps [25].
NOTE 17: These KPIs are only valid for cases where the viewport rendering is done in the tethered device and streamed down to the AR glasses. In the case of rendering capable AR glasses, these KPIs are not valid.
NOTE 18: These values are aligned with the tactile and multi-modal communication KPI table in TS 22.261 [5], clause 7.11.
NOTE 19: These values are aligned with “high-speed train” DL KPI from TS 22.261 [5] cl 7.1
NOTE 20: To leverage existing streaming assets and delivery ecosystem, it is assumed that the legacy streaming data are delivered to the rendering device, which incrusts this in the virtual screen prior to rendering. For a live streaming event, the user-experience end-to-end latency is expected to be competitive with traditional live TV services, typically [1-5] seconds.
NOTE 21: For example, the glTF format [60] can be used to deliver avatar representation and animation metadata in a standardized manner. Based on this format, the required bitrate for transmitting such data is highly dependent on avatar’s complexity (e.g., basic model versus photorealistic).
NOTE 22: These values are aligned with “immersive multi-modal VR” KPIs in TS 22.261 [5], clause 7.11. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 8 Conclusion and recommendations | The present document has analyzed a number of use cases for Mobile Metaverse Services enabled by the 5G system. Clause 7 contains consolidated requirements and KPIs. It is recommended that these be specified in normative specifications. NOTE: The present document will not be revised to align with normative specification. Annex A (informative): Avatar Service Considerations The term Avatar originated in writings associated with Hindu religion, referring to an incarnation of a divine being on Earth, significantly Vishnu. In computing an avatar is a graphical representation of a user or user’s character or persona. [Wikipedia-Avatar] The term was used to describe the player’s character in a number of games in the late 1970s into the late 1980s. In 1992, Neal Stephenson used the term to describe virtual simulation of the human form in his novel Snow Crash, in which he also coined the term metaverse. [2] Avatars are used in a number of ways today, besides as digital representations of characters in video games. The representation is often thought to be one to one (one person is represented by one digital representation), but this cannot be generalized. Some people are represented in multiple ways (especially over time), some groups use an avatar to represent them, sometimes programs or automated services are represented with an avatar (and these aren't human users at all.) In most applications, people can choose their own avatars and they may change these frequently, even adopting the avatars of other users if there is no policy to prevent this. Avatars may serve as a digital representation of a user in Internet forums. These are often a kind of cartoon version of a person’s face or an image representing them, often. For example, this is an avatar on Boardgamearena.com, for a community member known as “tree mile.” Figure A-1: Avatar as Iconic User Representation This digital representation is static (that is, it is generally not animated,) and serves to provide a user with a memorable and unique personality in the on-line forum, but without divulging my actual appearance. This is a common use on social media platforms. A social forum, in which avatars are remote controlled, animated. An early example of this was SecondLife. [Linden Lab] This is an example group of avatars in discussion. Figure A-2: Avatar as Animated User Representation This platform does not feature a ‘game.’ Rather players interact, build things, share information, purchase virtual accoutrements. Some institutions built an on-line virtual presence, such as universities, private corporations even political parties to enable interaction between users represented as avatars. Avatars have been used as a way to improve interaction between people using software or accessing on-line services and software. An example is “Clippy” a paperclip ‘help feature’ in Microsoft Office 97. Figure A-3: Avatar as Animated Interactive Automaton There are many other such digital representations that are used, e.g. for on-line chat services for service desks, etc. Motion capture / animated avatars are used to stand in for a person. They model and reproduce or mimic the user’s movements, facial expressions and often represent specific facial animation for ‘talking’ in a way reminiscent of cartoons. One area where this has developed is a kind of content production by ‘vtuber’ contributors. Tools to create avatars (vtube animation software) can be coupled with motion capture software to allow contributors to generate video content in the form of animation. The creator is represented by media generated by means of a model and cameras. Sound can be added or recorded along with the video input. Figure A-4: Avatar Live Animation Generated from Camera and Microphone Input A ‘live’ social media application can be designed around the techniques of animation and visual capture (as in the previous bullet) can provide an opportunity for users to communicate as cartoon digital representations of themselves with encoding and presentation in real-time. The communicating partner may be a human user or a ‘bot.’ Generally ‘chatbot’ services do not include such an animated figure – an icon or static image is used to represent the AI. A sophisticated ‘video capture,’ then transformation into a cartoon form with audio, and rendering this into media, is a very computationally intense task. There are many tools to create avatars and vtube video clips, however these are generally not ‘live.’ Figure A-5 presents ‘Kizuna AI’ a pioneering successful Vtuber personality. The media featuring these avatars is generated through tools that often involve animation editing and audio-visual production operations. Pure animation techniques can be enhanced with motion capture and facial expression capture. Figure A-5: Kizuna AI – an avatar celebrity References [Wikipedia-Avatar] https://en.wikipedia.org/wiki/Avatar_(computing) [Stephenson] Stephenson, Neal “Snow Crash,” Bantam Books, New York, 1992. [Linden Lab] https://secondlife.com/ Annex B (informative): The EU Digital Identity Wallet Initiative The European Commission intends to establish a sovereign digital/digital identity as part of its digital transformation strategy[B.2]. This digital identity [B.1] will allow by 2030 the citizens of the union to authenticate themselves to the main public services (or to some services of non-public companies), using a "wallet". This wallet will be an application that will store (in a secure way) a certain number of data and certified documents (identity card, driving license, certificates of personal qualities - like the majority -) in order to share them with the relevant services (e.g. school registration) securely. These solutions shall be compatible in all European countries. “Every time an App or website asks us to create a new digital identity or to easily log on via a big platform, we have no idea what happens to our data in reality. That is why the Commission will propose a secure European e-identity. One that we trust and that any citizen can use anywhere in Europe to do anything from paying your taxes to renting a bicycle. A technology where we can control ourselves what data is used and how."[B.1] The EU Digital ID Wallet [B.1] is intended to allow European citizens to safely save their documents and personal information in a manner that complies with privacy regulations, as well as to give the data owners full control how the data is used (who can access it), and to track how it has been used. The information stored in the wallet could have general utility in many circumstances, even outside of the country in which the information was issued. Examples given are driver's licenses, medical records or certification such as university degree titles. It is acknowledged that people need to establish their identity in many ways. This process is currently complex, as each activity requires different credentials and as the form of credentials vary, identification requires different process. Having a single digital identity wallet will simplify these processes. The goal of the program is to bring the following benefits: - To support the ability of every person eligible for a national ID card to have a digital identity that is recognized anywhere in the EU; - To provide a simple and safe way to control how much information you want to hsare with services that require the sharing of information; - To allow mobile phone apps and other devices to support a means to - provide identity services on- and off-line; - store and exchange information provided by governments, e.g. name, surname, date of birth, nationality; - to use information as confirmation ofthe right to reside, work, or study in a particular member state. Today only 60% of the EU population in 14 Member States are abile to use their national electronic ID (eID) beyond their own country. Only 14% of key public service providers across all Member states allow cross-border authenticaiton with an eID system, e.g. to prove a person's identity as part of authentication with a service accessed by means of the Internet without the need of a password.There are many situations where such identity information is needed, mainly during interaction with the government. For example, filing tax returns, changing one's address. Many other activities require identification, e.g. opening a bank account, renting a car, checking into a hotel, applying for a bank loan, etc. Various aspects of the intiative are of general interest for services offered over the internet, including: - Qualification of web sites and services, to ensure they are trustworthy and reliable. This could (partially) address threats such as phishing and illegitimate services; - An electronic signature framework, to express agreement to the content of a document; - A means to demonstrate that a set of data existed at a specific time, e.g. that a bill or fine was paid on time; - A 'seal of authenticity' that can be attached to digital content, such as football tickets, to avoid counterfeit in the digital domain. While the digital wallet initiative is specific to Europe, the ideas behind it may be generally applicable. That is, to encourage and ease e-commerce, e-government and provide users with control over how their data is accessed, a digital wallet approach may have applicability and value in a broader international context. Use Case Example: The use cases presented include identification on public websites, but also for banking or medical services, education, mobility, etc. It generally involves making life easier for citizens and businesses by producing a framework of trust in the exchange of identity papers without the need for verification by physical meeting. Figure Annex B-1: Example of use, applying for a bank loan [B.3] Benefits for the citizen: - Easy to identify itself - Management of identity information storage and usage permissions Benefits for businesses: - User-friendliness and compliance with user identification legislation. - Reduction in 'business integration requirements' for services, that currently has to contend with diverse documents and processes. References In mid-February 2022, a call for projects for the implementation of solutions and experimentation was launched <https://ec.europa.eu/info/funding-tenders/opportunities/docs/2021-2027/digital/wp-call /2022/call-fiche_digital-2022-deploy-02_en.pdf>, accessed 24.10.22. The "toolbox" defining the APIs and data schemas should be finalized by the end of 2022. The architecture of the technical solutions, such as the centralized or decentralized orientation, are not defined to date. [B.1] Quote from Ursula von der Leyen, President of the European Commission, in her State of the Union address, 16 September 2020, <https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-digital-identity_en>, accessed 24.10.22. [B.2] https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/shaping-europe-digital-future_en [B.3] The figure is from <https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-digital-identity_fr>, accessed 24.10.22. Annex C (Informative): Traffic Characteristics of Metaverse Media Communication Use Cases Device/Terminal Type Example Data Rate Traffic Characteristics Localized Mobile Metaverse Service Use Case AR capable glasses tethered to a UE - • Data transmission in short duration Mobile Metaverse for 5G-enabled Traffic Flow Simulation and Situational Awareness UE (different types, e.g., pedestrians, sensors) [10-100Mbit/s] • Data transmission in long duration • This use case motivates energy efficient content delivery to and from the UE, especially for pedestrians by using mobile phone Collaborative and Concurrent Engineering in Product Design using Metaverse Services XR devices, mobile phones, computers [1-100Mbit/s] • Data transmission in long duration • This use case motivates energy efficient content delivery to and from the UE Spatial Anchor Enabler Use Case AR glasses - • Data transmission in short duration Spatial Mapping and Localization Service Enabler Use Case UE - • Data transmission in short duration Mobile Metaverse for Immersive Gaming and Live Shows VR/AR/MR/Cloud Gaming mobile devices, such as mobile headsets or other haptic mobile devices, [1-1000Mbit/s] • Data transmission in long duration • This use case motivates energy efficient content delivery to and from the UE AR Enabled Immersive Experience AR glasses [200-2000Mbit/s] • Data transmission in long duration • This use case motivates energy efficient content delivery to and from the UE • Detailed discussion on energy utilization may be needed Supporting Multi-service Coordination in One Metaverse VR glasses, Tactile gloves - • Sustained diverse data transmission in long duration • This use case may motivate energy efficient content delivery support depending on the data transmission (uplink and downlink). Synchronized predictive avatars Metaverse devices - • Data transmission in long duration • This use case may motivate energy efficiency content delivery to and from the UE Use Case on Metaverse for Critical HealthCare Services Head mount device, tactile glove [1-100Mbit/s] • No requirement because it is life critical, it is assumed that a sufficient power supply exists to support an adequately long service life. IMS-based 3D Avatar Communication UE - • Data transmission in long duration with low data volume. Virtual humans in metaverse Head mount device, tactile glove - • Data transmission in long duration with low data volume. Work delegation to autonomous virtual alter ego UE - • Data transmission in short duration. Immersive Tele-Operated Driving in Hazardous Environment Head mount device [10~50 Mbit/s] • Data transmission in long duration. • This use case may motivate energy efficiency content delivery to and from the UE Virtual Emergency Drill over 5G Metaverse - - • Data transmission in short duration. Mobile Metaverse Live Concert Head mount device, tactile glove - • Data transmission in long duration • This use case motivates energy efficient content delivery to and from the UE • Detailed discussion on energy utilization may be needed IMS-based 3D Avatar Call Support for Accessibility Use Case UE - • Data transmission in long duration with low data volume. Localized Mobile Metaverse Overload - - • Data transmission in long duration. • This use case may motivate energy efficiency content delivery to and from the UE Table-C-1: Analysis of energy efficiency of content delivery in metaverse services Annex D (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 5.2022 SA1#98e S1-221264 - - - Initial Skeleton 0.0.0 5.2022 SA1#98e - - - Incorporation of approved pCRs: S1-221265; S1-221266; S1-221267; S1-221268; S1-221269. 0.1.0 9.2022 SA1#99e - - - Incorporation of approved pCRs: S1-222032; S1-222381; S1-222382; S1-222383; S1-222384; S1-222385; S1-222386; S1-222387; S1-222388; S1-222389; S1-222390; S1-222391 0.2.0 11.2022 SA1#100 - - - Incorporation of approved pCRs: S1-223054; S1-223249; S1-223440; S1-223442; S1-223464; S1-223465; S1-223609; S1-223611; S1-223612; S1-223613; ; S1-223614; S1-223615; S1-223617; S1-223622; ; S1-223677; S1-223709; S1-223710; S1-223711; ; S1-223712 0.3.0 02-2023 SA1#101 Incorporation of approved pCRs: S1-230182; S1-230774; S1-230743; ; S1-230766; S1-230491; S1-230492; S1-230767; ; S1-230769; ; S1-230796; ; S1-230771; S1-230498; S1-230682; S1-230568; ; S1-230570; S1-230572; ; S1-230433; S1-230573; ; S1-230574; ; S1-230436; S1-230575; ; S1-230775; S1-230578; S1-230768 0.4.0 03-2023 SA#99 SP-230223 MCC clean-up for presentation to SA 1.0.0 05-2023 SA1#102 Incorporation of approved pCRs: S1-231232; S1-231767 S1-231173; S1-231690; S1-231727; S1-231585; S1-231013; S1-231598; S1-231581; S1-231592; S1-231597; S1-231599; S1-231692; S1-231784; S1-231696; S1-231594 1.1.0 06-2023 SA#100 SP-230508 MCC clean-up for approval by SA 2.0.0 06-2023 SA#100 SP-230508 Raised to v.19.0.0 by MCC following approval by SA 19.0.0 2023-09 SA#101 SP-231017 0001 F Clean up 19.1.0 2023-09 SA#101 SP-231017 0008 F 22.856 CR addition of Digital wallet in section 3 Definitions of terms, symbols and abbreviations 19.1.0 2023-09 SA#101 SP-231017 0003 1 F Addition of consolidated KPI requirements 19.1.0 2023-09 SA#101 SP-231017 0004 2 F Consolidation of requirements on digital assets 19.1.0 2023-09 SA#101 SP-231017 0007 2 F Clarification of use case 5.9 for requirement consolidation 19.1.0 2023-09 SA#101 SP-231017 0002 3 F Addition of consolidated requirements 19.1.0 2023-12 SA#102 SP-231406 0009 1 F Essential correction to clause 7 19.2.0 |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 1 Scope | The present document describes use cases and aspects related to enhancements of the 5G system over satellite, including:
• Store and Forward (S&F) Satellite operation for delay-tolerant communication service
• UE-Satellite-UE communication
• GNSS independent operation
• Positioning enhancements for satellite access
Potential service requirements are derived for these use cases and are consolidated in a dedicated chapter.
The report ends with recommendations regarding the continuation of the work. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.261: "Service requirements for the 5G system ".
[3] 3GPP TR 22.822: "Study on using Satellite Access in 5G".
[4] 3GPP TR 38.811: "Study on New Radio (NR) to support non-terrestrial networks".
[5] Animal Tracking: https://www.movebank.org/cms/movebank-content/what-is-animal-tracking
[6] 13 Applications of remote sensing in Disaster management: https://grindgis.com/remote-sensing/13-applications-of-remote-sensing-in-disaster-management
[7] Havlicek, J. P., Mckeeman, J. C., & Remaklus, P. W. (1995). Networks of low-earth orbit store-and-forward satellites. IEEE Transactions on Aerospace and Electronic Systems, 31(2), 543-554.
[8] Antonini, M., De Luise, A., Ruggieri, M., & Teotino, D. (2005). Satellite data collection & forwarding systems. IEEE Aerospace and Electronic Systems Magazine, 20(9), 25-29.
[9] Abbasi-Moghadam, D., Hotkani, S. M. H. N., & Abolghasemi, M. (2016). Store and forward communication payload design for LEO satellite systems. Majlesi Journal of Electrical Engineering, 10(3).
[10] Mohit, K. (2021, September 13). 6 Benefits of Information Exchange in the Maritime Industry. Marine Insight. Retrieved Jun 10, 2022, from https://www.marineinsight.com/marine-safety/6-benefits-of-information-exchange-in-the-maritime-industry/.
[11] Akdağ, M., Solnør, P., & Johansen, T. A. (2022). Collaborative collision avoidance for Maritime Autonomous Surface Ships: A review. Ocean Engineering, 250, 110920.
[12] 3GPP TR 38.821, Solutions for NR to support non-terrestrial networks (NTN)
[13] Noman Shaikh, Significance of fleet management in logistics industry, January 02, 2020, https://www.peerbits.com/blog/significance-fleet-management-solution-for-logistics-industry.html
[14] Gure M , Ozel M E , Yildirim H H , et al. Use of satellite images for forest fires in area determination and monitoring. IEEE, 2009.
[15] 3GPP TS 22.125: "Uncrewed Aerial System (UAS) support in 3GPP".
[16] Hamza Benzerrouk , “Iridium Next LEO Satellites as an Alternative PNT in GNSS Denied Environments”, June 17, 2019 (https://insidegnss.com)
[17] “The human cost of disasters: an overview of the last 20 years (2000-2019)”，https://www.undrr.org/publication/human-cost-disasters-overview-last-20-years-2000-2019
[18] Xingqin Lin, Stefano Cioni, Gilles Charbit, Nicolas Chuberre, Sven Hellsten, and Jean-Francois Boutillon, “On the Path to 6G: Embracing the Next Wave of Low Earth Orbit Satellite Access,” IEEE Communications Magazine 59 (12), Dec. 2021, pp.36-42
[19] https://www.maine.gov/governor/mills/news/old-town-governor-mills-unveils-states-new-helicopter-fight-forest-fires-assist-search-rescue
[20] “Vision, requirements and evaluation guidelines for satellite radio interface(s) of IMT-2020”, https://www.itu.int/hub/publication/r-rep-m-2514-2022/
[21] “Why Korean telcos’ ride into flying car business”, https://www.koreaherald.com/view.php?ud=20220207000835, Feb. 2022
[22] The North American Interest Group of the GSM MoU ASSOCIATION: Location Based Services, Service Requirements Document of the Services Working Group |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 3 Definitions of terms, symbols and abbreviations | |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 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].
direct network connection: one mode of network connection, where there is no relay UE between a UE and the 5G network.
emergency report: in the context of this study, it is a data sent for emergency purpose (e.g., emergency messaging) and can be subject to international regulation.
indirect network connection: one mode of network connection, where there is a relay UE between a UE and the 5G network.
NOTE: The above definitions were taken from TS 22.261 [2].
satellite access: direct connectivity between the UE and the satellite.
NOTE: This definition was taken from TS 22.261 [2].
serving satellite: a satellite providing the satellite access to a UE. In the case of NGSO (Non-Geostationary Satellite Orbit), the serving satellite is always changing due to the nature of the constellation.
S&F Satellite operation: in the context of this study, S&F (Store and Forward) Satellite operation is an operation mode of a 5G system with satellite-access where the 5G system can provide some level of service (in storing and forwarding the data) when satellite connectivity is intermittently/temporarily unavailable, e.g. to provide communication service for UEs under satellite coverage without a simultaneous active feeder link connection to the ground segment.
S&F data retention period: it is the data storage validity period for the 5G system with satellite access supporting store and forward operation (e.g. after which undelivered data stored is being discarded).
UE-Satellite-UE Communication: for the 5G system with satellite access, it refers to the communication between UEs under the coverage of one or more serving satellites, using satellite access without going through the ground segment. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 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].
ISL Inter-Satellite Link
NGSO Non-Geostationary Satellite Orbit
S&F Store and Forward |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 4 Overview | The present document captures a set of use cases and potential service requirements related to the 5G system with satellite access taking into account new capabilities such as:
1. S&F Satellite operation for delay-tolerant communication services: S&F Satellite operation is an operation mode of a 5G system with satellite-access, where the 5G system can provide some level of service (in storing and forwarding the data) when satellite connectivity is intermittently/temporarily unavailable, e.g. to provide communication service for UEs under satellite coverage without a simultaneous active feeder link connection to the ground segment. This is particularly relevant for delay-tolerant IoT services via NGSO space segment.
2. UE-Satellite-UE communication: In some scenarios, UEs need to communicate using satellite access without going to the ground network in order to avoid long delays and limited data rate as well as reducing the consumption of backhaul resources.
3. GNSS independent operation: This would allow to provide satellite access to UEs without GNSS receiver or with no access to GNSS services.
4. Positioning enhancements for satellite access: 3GPP positioning methods are needed in some scenarios for UEs using only satellite access.
In addition, the TR includes several use cases on other aspects, including LAN using satellite access and information collection via satellite connections. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5 Use cases | |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.1 Use case on store and forward - MO | |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.1.1 Description | This use case illustrates the realization of a S&F service between a UE with satellite access and an Application Server for a delay-tolerant/non-real-time IoT NTN service in the case of a Mobile Originated message.
A description of store and forward operation is provided in Annex A.
Company TrackingInc offers a service of remote monitoring of fields and deploys and tracks many battery-powered IoT type UEs across the globe. All the IoT remote monitoring UEs deployed include a 5G communication with satellite access. Some of the UEs are deployed in a remote area where there is no mobile coverage by MNO and only satellite is possible.
For the satellite access, TrackingInc uses the service of IoTSAT for the 5G IoT connectivity by satellite and IoTSAT uses a LEO constellation which supports S&F operation mode.
All IoT remote monitoring UEs regularly send information related to the area they are monitoring to the application server of TrackingInc and sometimes receive new parameters from the application server. In most of the cases, the messages exchanged are delay-tolerant/non-real-time IoT. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.1.2 Pre-conditions | In the present use case, the IoT remote monitoring UE is in a remote area with no ground stations available for feeder link connectivity and the IoT remote monitoring UE is aware that IoTSAT constellation operates in S&F mode. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.1.3 Service Flows | The IoT remote monitoring UE needs to send a message to the TrackingInc application server. The UE waits for satellite network coverage and sends its message when the satellite passes by.
The IoT remote monitoring UE and the satellite providing coverage interact over the service link, allowing the UE to transfer the message to the satellite, which has no connectivity to the ground segment. And consequently, the satellite has to store locally the received message.
At this point:
• Limitations to the size/amount of data that can be sent from the UE could be enforced.
• Forwarding priority for the stored data to the ground station and data retention period for the exchanged data could be established.
• Acknowledgement of the received data by the satellite could be issued.
At a later time, the satellite with the stored message establishes connectivity with the ground network via a feeder link and relays/forwards/downloads the message to the ground network. All accumulated and stored MO messages are delivered to the ground once the feeder link is available, at the same time, all accumulated and stored relevant MT messages are also delivered to the satellite via the same feeder link, which will impact the performance of the feeder link, 5GC, and satellite significantly. The relevant performance optimization method will be taken into consideration accordingly.
The ground network, based on established connectivity configuration and routing, delivers message to the TrackingInc application server. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.1.4 Post-conditions | The message generated by the IoT remote monitoring UE has been either delivered successfully to the TrackingInc application server without relying on a continuous end-to-end network connectivity path between them or, in case the data retention period has been exceeded, the message has been discarded. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.1.5 Existing features partly or fully covering the use case functionality | 3GPP TS 22.261 [2], clause 6.3.2.3 on satellite access includes the following requirements:
The 5G system shall be able to provide services using satellite access.
The 5G system with satellite access shall be able to support low power MIoT type of communications.
However, it is not sufficient in regards of S&F operation especially for the delivery of delay-tolerant/non-real-time IoT NTN services with NGSO satellites. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.1.6 Potential New Requirements needed to support the use case | [PR 5.1.6-001] The 5G system with satellite access shall be able to support store and forward operation.
[PR 5.1.6-002] The 5G system with satellite access shall be able to inform a UE that "store and forward" operation is applied.
[PR 5.1.6-003] Subject to operator policy, the 5G system with satellite access supporting store and forward operation shall be able to allow the operator or a trusted 3rd party to set and enforce, on a per UE basis, a S&F data retention period.
[PR 5.1.6-004] Subject to operator policy, the 5G system with satellite access supporting store and forward operation shall be able to allow the operator or a trusted 3rd party to set and enforce, on a per UE basis, a S&F data storage quota.
[PR 5.1.6-005] The 5G system with satellite access supporting store and forward operation shall be able to support a mechanism to configure and provision specific required QoS and policies for S&F operation (e.g. forwarding priority, acknowledgment policy).
[PR 5.1.6-006] The 5G system with satellite access shall be able to provide integrity protection and confidentiality for communications between an authorized UE and the network when store and forward operation is applied.
[PR 5.1.6-007] The 5G system with satellite access supporting the S&F operation shall be able to support suitable means to resume communication between the ground station and satellite once the feeder link becomes available.
[PR.5.1.6-008] Subject to operator’s policies, a 5G system with satellite access supporting Store & Forward Satellite operation shall be able to support forwarding of the stored data from one satellite to another satellite, which has an available feeder link to the ground network, through Inter-Satellite Links.
[PR.5.1.6-009] A 5G system with satellite access supporting S&F Satellite operation shall support mechanisms for a UE to register with the network when the network is in S&F Satellite operation.
[PR.5.1.6-010] A 5G system with satellite access supporting S&F Satellite operation, shall support mechanisms to authorize subscribers for receiving services when the network is in S&F Satellite operation.
NOTE: It is assumed that the constellation knows which satellite has a feeder link available. However, this is outside the scope of 3GPP. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.2 Use case on store and forward - MT | |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.2.1 Description | This use case illustrates the realization of a S&F service between a UE with satellite access and an Application Server for a delay-tolerant/non-real-time IoT NTN service in the case of a Mobile Terminated message.
A description of store and forward operation is provided in Annex A.
Company TrackingInc offers a service of remote monitoring of fields and deploys and tracks many battery-powered IoT type UEs across the globe. All the IoT remote monitoring UEs deployed include a 5G communication with satellite access. Some of the UEs are deployed in a remote area where there is no mobile coverage by MNO and only satellite is possible.
For the satellite access, TrackingInc uses the service of IoTSAT for the 5G IoT connectivity by satellite and IoTSAT uses a LEO constellation which supports S&F operation mode.
All IoT remote monitoring UEs regularly send information related to the area they are monitoring to the application server of TrackingInc and sometimes receive new parameters from the application server. In most of the cases, the messages exchanged are delay-tolerant/non-real-time IoT. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.2.2 Pre-conditions | In the present use case, the IoT remote monitoring UE is in a remote area with no ground stations available for feeder link connectivity and the IoT remote monitoring UE is aware that IoTSAT constellation operates in S&F mode. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.2.3 Service Flows | The TrackingInc application server needs to send new parameters to the IoT remote monitoring UE. Based on the information provided by the network, the application server is aware that the communication with UE is in S&F mode.
The TrackingInc application server message will send new parameters through dedicated messages by conventional means (e.g. IP routing, tunnels) to the network entry-point (e.g. a SCEF, PDN-GW, SMSC), and may provide additional information about the delivery priority, the acknowledgement, etc. to the network.
At this point:
• Limitations on the amount of data to be transferred to the IoT remote monitoring UE could be enforced.
• Forwarding priority to the UE could be established.
• Acknowledgement of the received data by the network could be issued to the application server, possibly with the additional information about the store and forward, e.g. estimated time to deliver the messages.
• End-to-end acknowledgement policy can be established.
The network stores the message until it can be delivered/relayed to a satellite expected to fly over and provide coverage to the destination IoT remote monitoring UE.
When the satellite is connected via the feeder link to the ground network, the message is uploaded into the satellite. All accumulated and stored MT messages are uploaded into the satellite via the feeder link. At the same time, all accumulated and stored MO messages are also delivered to 5GC via the same feeder link, which will cause a performance impact on the feeder link, satellite, and 5GC. It needs a performance optimization method here.When flying over the area that the IoT remote monitoring UE is located, the satellite with the stored message triggers paging over the service link for the UE to connect to the network.
The stored message is delivered/downloaded from the satellite to the IoT remote monitoring UE. Acknowledgment may be requested/issued. Mechanisms to ensure integrity of the delivered information may be in place. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.2.4 Post-conditions | The message generated by the TrackingInc application server has been delivered successfully to the IoT remote monitoring UE without relying on a continuous end-to-end network connectivity path between them. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.2.5 Existing features partly or fully covering the use case functionality | 3GPP TS 22.261 [2], clause 6.3.2.3 on satellite access includes the following requirements:
The 5G system shall be able to provide services using satellite access.
The 5G system with satellite access shall be able to support low power MIoT type of communications.
However, it is not sufficient in regards of S&F operation especially for the delivery of delay-tolerant/non-real-time IoT NTN services with NGSO satellites. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.2.6 Potential New Requirements needed to support the use case | [PR 5.2.6-001] The 5G system with satellite access shall be able to inform a trusted application server whether store and forward operation is applied for communication with a UE.
[PR 5.2.6-002] Subject to operator policy, the 5G system with satellite access supporting store and forward operation shall be able to allow the operator or a trusted 3rd party to set and enforce, on a per UE basis, a S&F data retention period.
[PR 5.2.6-003] Subject to operator policy, the 5G system with satellite access supporting store and forward operation shall be able to allow the operator or a trusted 3rd party to set and enforce, on a per UE basis, a S&F data storage quota.
[PR 5.2.6-004] The 5G system with satellite access supporting store and forward operation shall support a mechanism to configure and provision specific required QoS and policies for S&F operation (e.g. forwarding priority, acknowledgment policy).
[PR 5.2.6-005] The 5G system with satellite access shall be able to provide to a trusted third-party application the information about the store and forward operation applied to a UE (e.g. estimated delivery time to the UE).
[PR 5.2.6-006] The 5G system with satellite access shall be able to provide integrity protection and confidentiality for communications between an authorized UE and the network when store and forward operation is applied.
[PR 5.2.6-007] The 5G system with satellite access supporting the S&F operation shall be able to support suitable means to resume communication between the ground station and satellite once the feeder link becomes available. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.3 Use case on store and forward - Inter-satellite | |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.3.1 Description | To expand the market of delay-tolerant IoT devices, store and forward operations are necessary to be developed to sustain the user plane data during the feeder link disconnection between the satellite and the terrestrial gateway. Based on the earlier studies [3][4], there are many use cases can be further improved with such mechanisms.
Regardless of scenarios describing a relative static location relationship of a IoT device, a satellite without an available terrestrial gateway (as shown in section 5.1 and 5.2), the serving satellite may change to another one during the time when the feeder link is unavailable. And such unavailable state of feeder link may be caused by the temporary reconstruction or update of terrestrial gateway.
As shown in Figure 5.3.1-1, a mobile IoT device may move from the coverage of one satellite to the other (e.g. containers tracing and tracking), or as shown in Figure 5.3.1-2, a NGSO satellite may fly away and the other one will come and turn to serving a static IoT device. Under such circumstances, the serving satellite may forward the stored user plane date to the next serving satellite through Inter-Satellite Links, and the next serving satellite may help forward the data to the gateway.
Meanwhile, if the feeder link of the next satellite is also unavailable, it will continue the store operation until the recovery of its feeder link. In this way, for every single IoT device, there will be only one satellite for its data storage in the overall satellite system. And the mobile operators will be easier to manage and maintain the data rather than dealing with the separate data which is belong to one device but among different satellites.
Significantly, during the period that the feeder link is unavailable, the serving satellite only stores or forwards (Inter-satellite) the data received from an IoT device which is already able to send data to the application server through the mobile network with satellite access. Because of the disconnection separates the two parts of the mobile network temporarily, the part in the serving satellite will not be able to fulfill common communication procedures and it will refuse any access from an unregistered device.
Furthermore, considering the limited data storage in satellite and the large amount of IoT devices, a maximum storage for each IoT device should be pre-configured based on the application data characteristics, user subscriptions and overall performance of satellite communication system.
Figure 5.3.1-1: Serving satellite change during the feeder link disconnection - IoT device moving
Figure 5.3.1-2: Serving satellite change during the feeder link disconnection - satellite moving |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.3.2 Pre-conditions | A delay-tolerant device has a subscription with the terrestrial operator TerrA, and it is tagged on one container for tracing and tracking.
TerrA has agreement with the satellite operator SatA for satellite access.
SatA maintains multiple serving satellites for the satellite access of TerrA’s subscribers all over the world, including Adam and Bob. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.3.3 Service Flows | 1. The container will be shipped from the Harbour A to the Harbour B across the Pacific. After the cargo ship leaves the Harbour A, the device can send some packets through the satellite access during the shipping time.
2. Due to some reasons, the feeder link between the serving satellite Adam and terrestrial gateway is interrupted temporarily or couldn’t be used for a time.
3. Based on the configuration of store and forward operations, Adam will go on to receive the packets from the device, and store these packets until the feeder link recovers.
4. However, during the period of feeder link is unavailable, the cargo ship approaches the border of coverage of Adam and will head to the coverage of another satellite Bob. So, based on the movement of the cargo ship, the serving satellite will change.
5. During the period of the change, Adam sends the stored packets to Bob through the inter-satellite link and Bob will forwards the packets to the gateway if its feeder link is available.
6. Particularly, Bob will continue storing the packets if its feeder link is also unavailable. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.3.4 Post-conditions | Those packets will be finally sent to the application server by the network behind the gateway, e.g. transportation network, core network, internet. And the application will parse some information from the packets. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.3.5 Existing features partly or fully covering the use case functionality | 3GPP TS 22.261 [2], clause 6.3.2.3 on satellite access includes the following requirements:
The 5G system shall be able to provide services using satellite access.
The 5G system with satellite access shall be able to support low power MIoT type of communications.
However, it is not sufficient in regards of S&F operation especially for the delivery of delay-tolerant/non-real-time IoT NTN services with NGSO satellites. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.3.6 Potential New Requirements needed to support the use case | [PR.5.3.6-001] Subject to operator’s policies, a 5G system with satellite access shall be able to store data received from authorized UEs using delay-tolerant communication service while the feeder link is unavailable.
[PR.5.3.6-002] Subject to operator’s policies, a 5G system with satellite access shall be able to support forwarding of the stored data received from authorized UEs using delay-tolerant communication service from one satellite to another satellite through Inter-Satellite Links while preserving integrity protection, confidentiality and security of the data.
[PR.5.3.6-003] Subject to operator’s policies, a 5G system with satellite access shall be able to define the maximum amount of data storage per satellite per authorized UEs using delay-tolerant communication service.
[PR.5.3.6-004] The 5G system with satellite access shall be able to authorize the communication of a UE when the satellite access is operating in store and forward mode. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.4 Use case on store and forward - data transfer for IoT devices in remote areas | |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.4.1 Description | Data transfer at remote sites is a very common requirement. Research institutions can obtain data from remote sites for scientific research, e.g. animal tracking [5]. Government agencies can obtain data from remote sites for disaster mitigation and avoidance, e.g. via remote sensing [6]. Commercial companies can obtain data from remote sites for proper resource allocation. Data transmission at many remote sites is delay-insensitive, and satellite coverage does not always ensure that satellites connect to both the service link and the feeder link. In the past 30 years, many scholars have devoted themselves to studying the data transmission problem of remote sites, and developed the store and forward mechanisms to solve the problem [7][8][9].
In remote areas, there is no terrestrial network for various reasons, e.g. it is difficult to build and maintain communication towers. As a result, this makes it challenging to collect information for environmental protection purposes in these areas. For example, sensors installed on animals need to be monitored regularly. In this scenario, the sensors installed on the animals send the status information, e.g. the movements, physiology and surrounding environment of the animals, to the satellite; and the satellite stores the received status information of the animals, and forwards the information to the scientific centre when a feeder link becomes available. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.4.2 Pre-conditions | EA Science Center has installed sensors (IoT devices) on the animals to collect information for environmental protection purposes in these remote areas. Satelles, the satellite communication operator, has launched the Store & Forward Satellite operation to support the data transferring for the remote areas. EA Science Center has signed contract with Satelles to allow sensors installed on animals to send the status information (e.g. the movements, physiology and surrounding environment of the animals) to the Science Center via satellite.
The satellite and the IoT devices are properly configured with sufficient information, e.g. credential/certificate that is needed for the devices to verify the authenticity of the satellite. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.4.3 Service Flows | Figure 5.4.3-1: Animal tracking in the remote areas
1. The IoT devices are installed on animals and powered on, they are registered with the 5G network for the Store & Forward Satellite operation. The satellite with the store and forward function enables the IoT devices to transfer data to the network, even when the feeder link to the ground is not available. A secured connection between an IoT device and the satellite is established to protect the data security and privacy.
2. The IoT devices send sensor status information to the satellite, the satellite stores the sensor status information received from the IoT devices.
3. When the satellite has the feeder link available to the ground segment, the satellite forwards the sensor status information, as well as other necessary information, to the ground core network. The ground core network verifies the IoT devices based on the information received; if it is allowed, the ground core network forwards the sensor status information to its destination data network.
4. The ground core network sends the result of the operation to the satellite (the same satellite or a different one that will pass through the remote area).
5. When the satellite (or next satellite) passes through the remote area, the satellite pages the UE, and based on the result received from ground core network, the satellite sends result of the operation to the IoT devices.
6. If an IoT device needs to update the sensor status information, it can send it to the satellite when it is connected to the satellite. The satellite stores it and forwards the sensor status information to the ground core network when feeder link becomes available. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.4.4 Post-conditions | After the scientific centre receives the sensor status information, the scientists can analyse the sensor status information, and track the status of the animals. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.4.5 Existing features partly or fully covering the use case functionality | None. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.4.6 Potential New Requirements needed to support the use case | [PR 5.4.6-001] The 5G system with satellite access shall support mechanisms to store user data, received from UEs via satellite access, on the satellite and forward it when feeder link between the satellite and the ground segment is available.
[PR 5.4.6-002] The 5G system with satellite access shall support mechanisms for a user to securely register a UE to use the Store & Forward Satellite operation when satellite connectivity is intermittently/temporarily unavailable.
NOTE: The user could be a human user using a UE with a certain subscription or a third party that is typically a business customer having service level agreement with the operator and interacting with the 5G network via an application server.
[PR 5.4.6-003] The 5G system with satellite access shall support mechanisms to authenticate and authorize a UE for the Store & Forward Satellite operation.
[PR 5.4.6-004] The 5G system with satellite access shall be able to limit the total amount of the stored data received from a UE when using the Store & Forward Satellite operation.
[PR 5.4.6-005] The 5G system with satellite access shall be able to collect charging information per UE for use of the Store & Forward Satellite operation (e.g., data volume, duration, involved satellites).
[PR 5.4.6-006] The 5G system with satellite access shall be able to collect charging information per application for use of the Store & Forward Satellite operation (e.g., number of UEs, data volume, duration, involved satellites).
5.5 Use case on LAN using Satellite Access |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.5.1 Description | Satellite access networks are designed to ensure ubiquitous coverage and availability to any users with communication need. Beyond wide coverage capabilities, satellite connectivity can add flexibility to the network topology by providing an alternative route through satellite when terrestrial link is unavailable. The integration of satellite system, to compensate for the limitation of terrestrial network will benefit more users with interim but necessary service need.
When scientist-explorers move to the “blink spots” of terrestrial access network networks (e.g. deserts, oceans, polar regions, etc.), they need to keep collecting scientific data during the regional expedition and store it in local Scientific Research Station for analytic, retrieval, and synchronization with remote Scientific Data Center. In such condition, a provisional local area network (LAN) using satellite access could be an option to provide a temporary reliable communication service.
Scientific Expedition Team with tens of explorers and vehicles arrives at Antarctica to start scientific expedition activities in area LocArea for a month as Figure 5.5.1-1 depicts.
Figure 5.5.1-1: LAN using Satellite Access
In Figure 5.5.1-1, the local Scientific Research Stationequipped with a data center LocDC will support the data analytics and research in LocArea. The remote Scientific Data Center RemDC located in area RemArea served by Terrestrial Operator TerrA, can support the data analytics, as well as retrieve all the data and research results from LocDC in a fixed time every day. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.5.2 Pre-conditions | All UEs of the Team capable of satellite access are the subscribers of TerrA in RemArea.
LocArea has no terrestrial network but covered by satellite-enabled NR-RAN (e.g. LEO) of Satellite Operator SatA.
SatA has an agreement with TerrA to provide 5G network services with the flexible network configuration of satellite and terrestrial elements in LocArea.
RemDC is connected through 5G core network of TerrA.
It’s assumed that UEs can always find serving satellites from the constellation. The serving satellite change is omitted from the flow. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.5.3 Service Flows | Once the explorers settle down in Scientific Research Station, LocDC is provisioned and authorized to connect to 5G core network of TerrA through satellite or ground gateway regarding the management policy agreed by SatA and TerrA.
All UEs of the Team are enabled the corresponding services in LocArea regarding the device setting and subscription information.
During the activities in LocArea, all UE register to TerrA 5G network through SatA’s satellite access network to upload data to LocDC with the optimal route in time.
LocDC can sync up data to RemDC through 5G network configured by SatA and TerrA with the optimal route in each fixed time slot.
When leave LocArea, there are available terrestrial access network of TerrA or other operators in service agreement with TerrA (e.g. roaming, shared network), UEs will be steered to upload data via satellite access to LocDC or terrestrial access network to RemDC regarding the policy.
When LocDC is disconnected from 5G network regarding the original provisioning information, all UE will upload data to RemDC. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.5.4 Post-conditions | Local satellite access network of SatA will be routed to LocDC for data exchange when LocDC is in service.
All the data is successfully transferred between UEs and LocDC, UE and RemDC, LocDC and RemDC. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.5.5 Existing features partly or fully covering use case functionality | Regarding TS 22.261 [2], satellite access and satellite connectivity are supported in Rel-18, as
The 5G system shall be able to provide services using satellite access.
UEs supporting satellite access shall support optimized network selection and reselection to PLMNs with satellite access, based on home operator policy.
The 5G system with satellite access shall support the use of satellite links between the radio access network and core network, by enhancing the 3GPP system to handle the latencies introduced by satellite backhaul.
The 5G network can also support multiple wireless backhaul connections (e.g. satellites and/or terrestrial), and efficiently route and/or bundle traffic among them.
As TS 22.261 clause 6.5 illustrates, the requirement of efficient user plane for 5G system with satellite access will be,
• A 5G system with satellite access shall be able to select the communication link providing the UE with the connectivity that most closely fulfils the agreed QoS. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.5.6 Potential New Requirements needed to support the use case | [PR 5.5.6-001] Subject to regulatory requirements and operator’s policies, the 5G system with satellite access shall be able to support an efficient communication path and resource utilization for a UE using only satellites access, e.g. to minimize the latencies introduced by satellite links involved.
[PR 5.5.6-002] Subject to regulatory requirements and operator policy, the 5G system with satellite access shall be able to support service continuity when the UE communication path moves between satellite access network and terrestrial access network. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.6 Use case on Information Exchange between Ships at sea | |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.6.1 Description | Information exchange in the maritime industry is very important [10] [11]. Information exchange allows for better coordination between ships, which is required regardless of the purpose for which ships are sailing. An effective information exchange system can better coordinate the ships and improve the safety of ships, such as resisting pirate attacks, avoiding accidents at sea, and rescuing.
At sea far from land, there is no terrestrial communication system. Ships can communicate directly with each other at short distance through various types of wireless technologies. At long distances, information can only be exchanged through satellites and then through remote data centres, which affects communication efficiency, especially in emergency situations. In addition, in some areas, the satellite has no available feeder link, which causes the communication interruption even though the communicating ships camp on the same satellite. In this scenario, communication between ships through satellites without going via remote data centres can improve communication efficiency and reduce losses caused by potential maritime accidents.
Satellite broadband can be suited to connecting remote areas which do not have reliable mobile or fixed broadband. There are new broadband satellites systems being developed, which use many satellites in a non-geostationary satellite orbit (NGSO) closer to the Earth than earlier satellites. Typically, the beam footprint size of Low-Earth Orbit (LEO) satellites and Medium-Earth Orbit (MEO) satellites is in the range of 100 – 1000 km [12]. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.6.2 Pre-conditions | MinosShipping, the shipping company, has many ships operating all over the world. MinosShipping signs a contract with Delphi, an operator with satellite communication services. Delphi has deployed NGSO satellites, which allows communication between ships via satellite without going through the ground network, that is, devices on a ship can communicate directly with devices on another ship via satellite. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.6.3 Service Flows | Figure 5.6.3-1: communication via the same satellite without going through the ground network
1. Device A on ship #1 register with the 5G network via satellite, and device B on ship #2 (small) also register with the 5G network via satellite. The devices A and B can communicate with each other via the 5G network.
2. When the ship #1 and the ship #2 are under the same satellite coverage, the devices A and B want to communicate with each other. The remote core network authorizes the communication between the devices A and B based on e.g., subscription, and location information. After getting authorized, the data traffic between the devices A and B is routed through the same satellite. During the data traffic communication between devices A and B without going through the ground network, if the feeder link becomes unavailable, device A still can have the communication with device B.
Figure 5.6.3-2: communication via satellites with ISL without going through the ground network
3. Along the long journey, ship #1 and ship #2 move across the coverage of different satellites, i.e. ship #2 moves to the coverage of satellite #2 while ship #1 remains in the coverage of satellite #1. Inter satellite link is available between satellite #1 and satellite #2.
4. During the journey, the communication between devices A and B via satellite(s) continues without interruption.
5. The charging information of the traffic data exchanged via the satellites is collected in the satellites and reported to the remote core network. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.6.4 Post-conditions | The ship #1 and the ship #2 can exchange information efficiently without data traffic transferred via the remote core network. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.6.5 Existing features partly or fully covering the use case functionality | None. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.6.6 Potential New Requirements needed to support the use case | [PR 5.6.6-001] The 5G system shall support mechanisms to authorize the communication between UEs using satellite access (without going through the ground network) based on e.g., location information and subscription.
[PR 5.6.6-002] The 5G system shall support mechanisms to collect charging information for the traffic data exchanged using satellite access without going through the ground network.
[PR 5.6.6-003] Subject to regulatory requirements and operator’s policy, the 5G system shall support communication between UEs using satellite access without going through the ground network.
[PR 5.6.6-004] Subject to regulatory requirements and operator’s policy, the 5G system shall maintain service continuity with minimum service interruption of the communication between UEs using satellite access without going through the ground network when a UE changes from the coverage of one satellite to another (due to the movement of the UE and/or the satellites).
[PR 5.6.6-005] Subject to regulatory requirements and operator’s policy, the 5G system with satellite access shall be able to support UE-Satellite-UE communication when the feeder link is temporarily unavailable.
5.7 Use case on the support of UE-satellite-UE phone call |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.7.1 Description | Known as the "Lung of the Earth", the Amazon Rainforest locates in the the Amazon Basin of South America, with a total area of 700 million hectares, spanning eight countries, and is the largest and most diverse tropical rainforest in the world. Although the Amazon rainforest is known as a paradise for animals and plants, it is a terrible "forbidden area" for human beings. Lives will be exposed to various dangers if we enter the Amazon rainforest without any preparation.
Vipers, crocodiles, bacteria and viruses, or even swamp can destroy the vulnerable human life. However, many explorers and tourists still step into this land every year. When they get into troubles, the most important thing is that they can communicate with the nearest first-aid station or other teams timely. However, in the deep of the dense primordial forest, there are no modern communication infrastructures and even no power supplies.
The satellite will help conquer such a desperate plight because it can provide timely access for the terminals without any surrounding terrestrial infrastructures. In this way, the injured can find the nearest first-aid station and make a quick phone call. Based on the potential positioning capability of the satellite, the rescue team can also find the position of the injured efficiently.
However, due to the explorers and tourists are always from different countries, they may not belong to only one mobile operator. So they need mechanisms, such as roaming, between different mobile operators’ network even all of them access the same one satellite.
Moreover, some studies show that the ground segment need to be detailed designed and implemented, and there will be a serious dilution of the communication efficiency based on existing mechanisms in both satellite network and mobile network, especially data transferring and switching. So, it will benefit that enhance the capabilities of data processing and switching within the satellites.
Figure 5.7.1-1: Phone call through one satellite without going through ground network |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.7.2 Pre-conditions | Ed is an explorer from Country A, and his phone has a subscription with the terrestrial operator TerrA.
Bell is a rescuer working in the Amazon Rainforest, and his phone has a subscription with the terrestrial operator TerrB.
TerrA has roaming agreement with TerrB and TerrB has agreements with the satellite operator SatA for satellite access.
SatA maintains multiple serving satellites for the 5G subscribers all over the world, Amazon Rainforest is one of SatA’s serving areas.
Ed signed up a roaming plan from TerrA for accessing TerrB’s mobile network in case of keeping in touch with others in the Amazon Rainforest. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.7.3 Service Flows | 1. Ed is hiking along the planned route in the Amazon Rainforest, with good connection to ground network through satellite access.
2. Suddenly, Ed is knocked by a piece of deadwood and his left arm is wounded.
3. Ed can not go on his ride with poor medical measures, so he dials the rescue phone number for help.
4. Based on the position information of Ed provided by SatA and TerrB, the rescue center finds Bell is the nearest rescuer and transfers the call to Bell.
5. Bell answers the phone call with satellite access and tries to find Ed based on the real-time position information of Ed. For lower communication latency, this phone call is routed by only one satellite without going through the ground network of TerrA and TerrB. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.7.4 Post-conditions | Bell runs towards to Ed as soon as possible and keeps talking to him, finally Ed is saved. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.7.5 Existing features partly or fully covering the use case functionality | 3GPP TS 22.261 [2],
clause 6.1.2.1 on network slice includes the following requirements:
The serving 5G network shall support providing connectivity to home and roaming users in the same network slice.
The 5G system shall be able to support IMS as part of a network slice.
clause 6.2.4 includes roaming related requirements in diverse mobility management:
For a 5G system with satellite access, the following requirements apply:
- A 5G system with satellite access shall enable roaming of UE supporting both satellite access and terrestrial access between 5G satellite networks and 5G terrestrial networks.
- UEs supporting satellite access shall support optimized network selection and reselection to PLMNs with satellite access, based on home operator policy.
clause 6.3.2.3 on satellite access includes the following requirement:
The 5G system shall be able to provide services using satellite access.
clause 9.1 on charging aspect includes the following requirement:
The 5G core network shall support collection of charging information based on the access type (e.g. 3GPP, non-3GPP, satellite access). |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.7.6 Potential New Requirements needed to support the use case | [PR 5.7.6-001] Subject to regulatory requirements and operator’s policy, the 5G system with satellite access shall support providing connectivity between UEs without going through the ground network regardless if they are registered in the HPLMN or a VPLMN.
[PR 5.7.6-002] The 5G system with satellite access shall support collection of charging information for a UE registered to the HPLMN or a VPLMN, without going through the ground network.
5.8 Use case on enabling multiple communication services between UEs |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.8.1 Description | The behaviours and trace of wild animals are the evidence of nature science. Researchers often use camouflage cameras blending in with their surroundings to observe wild animals. Meanwhile, researchers need to stay far enough away from the wild animals in order not to disturb their normal behaviour.
African savannah is a good place for research to observe and study lions. Usually, the researchers are camped far from the pride, and manipulate several mobile camouflage cameras to approach the pride and take videos for them. The camera with inner analysis functions can identify some typical behaviours and send corresponding notifications to the researchers. In this way, researchers can record and trace the pride and call the rescue centre for help when the lions get wounded.
In fact, to safeguard the ecology of wild animals, there is always no terrestrial network, and walkie-talkies are widely used for short distance communication there. However, because the camouflage camera, the rescue centre and the camp are usually far away from each other, the communication between them can only be easily realized with the help of satellites. In general, both the video stream and the voice call need to be transmitted to a nearby terrestrial network first, so it will affect communication efficiency, especially in emergency situations. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.8.2 Pre-conditions | There is no terrestrial network in the African savannah, but it is covered and served by the satellites owned by Satellite Operator SatA.
TerA which is a terrestrial network operator contracts with SatA to allow communication services between devices in the African savannah via satellite. That is, devices can communication directly via satellite without going through the ground network.
To support multiple communication services simultaneously, TerA provides a variety of plans for different purpose, e.g., video stream, voice call, etc.
Emily is the leader of the researching team. All devices in the camp are subscribers of TerA. Emily signs video stream plan for every camera which is 2km away from Emily’s camp, and she signs both video stream and voice call plan for her mobile phone.
Vincent is an assistant at the rescue centre which is 10km away from the camp, and he is also a subscriber of TerA with voice call plan.
Figure 5.8.2-1: Multiple communication services via satellite without going through the ground network |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.8.3 Service Flows | 1. One camera detects an injured lion, then it sends a notification to Emily’s phone via a satellite.
2. After receiving the notification, Emily opens the “Cam” App on her phone to watch the live video captured by the camera. The video stream from the camera to Emily’s phone is routed through the satellite.
3. By watching the video, Emily notices that the injured lion is being driven out of this pride. So Emily tracks the injured lion through the mobile camouflage camera. At the same time, she calls Vincent.
4. Vincent answers the phone and this voice call is also routed through the same satellite.
5. During the call, the satellite detects that the quality of voice call is impaired, so it re-choose a lower communication quality level for the video stream because of limited satellite resources and service priority. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.8.4 Post-conditions | Emily can watch real-time video with lower resolution from the camera and keep the call with Vincent at the same time.
Both the video stream and voice call can be routed through the same satellite without being transmitted to the remote core network. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.8.5 Existing features partly or fully covering use case functionality | There are a few related requirements specified in 3GPP TS 22.261 [2], which have been described as:
The 5G system shall be able to support E2E (e.g. UE to UE) QoS for a service.
NOTE 2: E2E QoS needs to consider QoS in the access networks, backhaul, core network, and network to network interconnect.
For a 5G system with satellite access, the following requirements apply:
- The 5G system shall support service continuity between 5G terrestrial access network and 5G satellite access networks owned by the same operator or owned by different operators having an agreement.
- A 5G system with satellite access shall be able to select the communication link providing the UE with the connectivity that most closely fulfils the agreed QoS
- A 5G system with satellite access shall enable roaming of UE supporting both satellite access and terrestrial access between 5G satellite networks and 5G terrestrial networks. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.8.6 Potential New Requirements needed to support the use case | [PR 5.8.6-001] Subject to regulatory requirements and operator’s policy, the 5G system with satellite access shall be able to provide a mechanism for QoS control of the communication between UEs using satellite access without going through the ground network.
[PR 5.8.6-002] Subject to regulatory requirements and operator’s policy, the 5G system with satellite access shall be able to support different types of communication (e.g. services including unicast, multicast, broadcast) using satellite access without going through the ground network.
5.9 Use case on usage of satellite connectivity for collection of information to aid terrestrial network planning |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.9.1 Description | Network deployment in sparsely populated areas has been a major concern worldwide due to numerous challenges like affordability, infrastructure unavailability, and landscape or topographic conditions. Satellite connectivity can help to serve such areas. However, satellite access may not suffice in all scenarios (for low latency and high throughput applications) and there may be a need for terrestrial network deployment also. In such a situation, satellite connectivity can also facilitate information collection related to UE location and usage statistics, which can later be used for terrestrial network planning in these areas.
Connectivity can be provided in sparsely populated areas through satellite access using direct or indirect access through relay nodes/relay UEs (as shown in Figure 5.9.1-1). This eliminates the requirement of everyone having to use satellite UEs. The service provider can implement a subset of Minimization Drive Test (MDT) procedures to collect information such as location of the UEs through satellite connectivity that can be used by Network Management System (NMS). In addition, usage statistics (for UEs) may also be collected and analysed for the purpose of terrestrial network planning.
Figure 5.9.1-1: Connectivity and data collection from UEs through Satellite Access |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.9.2 Pre-conditions | There is satellite access coverage but no terrestrial access network deployed in a sparsely populated area. However, satellite access does not suffice and the service provider needs to augment it with the terrestrial network. Hence, the service provider can conduct some tests to understand the network deployment and planning needs. The service provider’s 5G System supports direct connectivity of satellite UEs and indirect connectivity for other UEs via relay nodes/relay UEs. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.9.3 Service Flows | A village called Sittlingi has no terrestrial connectivity and residents of this village have to travel a few kilometres to a nearby village office for internet connectivity. Incidentally, this village is covered by satellite access from the service provider TTech Inc. The population in this village is not uniformly distributed and is sparsely populated. TTech is also interested in deploying terrestrial access networks in such areas. TTech wants to survey the area using some reliable mechanism to understand the usage needs of the villagers. Based on this knowledge, the number of base stations, their location and capabilities can be decided for deployment. TTech provides 5GS subscriptions to the users through satellite access. The provider also deploys relay nodes/UEs in the village to provide connectivity to people using non-satellite UEs. The relay nodes use satellite link as backhaul. Residents of the village subscribe and start availing services provided by 5GS. People who use standard off the shelf 5G UEs can be connected to satellite access through relay nodes/ relay UEs. As UEs are connected to the network, 5GS can collect traffic pattern related information from the 5G core user plane function and location related information through conventional Radio Resource Control (RRC) procedures. Based on this information, analysis for the needs and capabilities of terrestrial deployment can be done. Accordingly, terrestrial deployment is planned, designed and further executed. Once TTech completes terrestrial deployment, UEs can get connectivity through a terrestrial base station and satellite access connectivity can be terminated if desired. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.9.4 Post-conditions | Service provider TTech is not required to perform some other kind of survey to identify the requirements. The provider utilizes existing 3GPP procedures to get information on usage statistics and location (using 5GS Satellite access) for terrestrial access network planning using optimum resources. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.9.5 Existing features partly or fully covering the use case functionality | • Relay UE/ relay node (TR 38.821 [12], TS 22.261[2]) supports terrestrial connectivity to UEs on one end and connects to non-terrestrial access network on the other. The 5G system shall support connectivity using satellite access. (TS 22.261 [2])
• To collect UE specific measurements using control plane architecture, subset of MDT procedures (Reference: TS 37.320[x]) can be triggered. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.9.6 Potential New Requirements needed to support the use case | [PR 5.9.6-001] Subject to regulatory requirements and operator’s policies, the 5G system with satellite access shall be able to support collection of information on usage statistics and location of the UEs that are connected to the satellite, for network (e.g. terrestrial) planning. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.10 Use case on vehicle fleet management in the desert | |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.10.1 Description | With the help of the construction of the transportation infrastructure, communication and information infrastructure, the modern logistics can deliver the goods to almost any corner of the world in a fast and reliable manner. Fleet management is a critical part of the logistics industry [13], which is being changed by IoT technologies in live vehicle monitoring, cargo management, driver behaviours’ monitoring and etc. The real-time data exchange is important for the staff of fleet management in route scheduling, decision making and safety assurance.
The convoy sometimes need to go across the area with sparse population or in extreme condition, where the network status fluctuates. Thus, besides remote management, local management by the team leader will also play a role in ensuring the speed and reliability of the transportation. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.10.2 Pre-conditions | The logistic company ExpressX provides transportation services all over the world and well known for long distance transport. NetX, a mobile network operator has signed the contract with ExpressX to offer 5G communication service for all the vehicles and the staff, and promise the full coverage along all their transport routes including satellite services. NetX has deployed NGSO satellites to realize the radio coverage in rare population area and the deserts.
All the vehicles for long distance transport are equipped with Telematics Box (e.g Device #2) supporting all 5G RATs (e.g. NR, LEO) as well as on-vehicle IoT devices (e.g. Device#3) only capable of 5G NR for data service. The man-held UEs (e.g. UE1) of fleet team leaders support all 5G RATs.
Device#3 can connect to 5G network in either direct or indirect connection mode. Device#2 can help other UEs to connect to 5G network as a relay UE.
UE1, Device#2, and Device#3 have the subscription of NetX.
Figure 5.10.2-1: Fleet management in the desert via satellite access |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.10.3 Service Flows | 1. UE1, held by the fleet team leader is registered to NetX core network via terrestrial access network at departure.
2. The Device#2 and on-vehicle device Device#3 are registered to NetX network when the transport starts, and keep reporting the vehicle’s status and the driver’s behaviours to remote management platform and UE1 via terrestrial access network and ground core network.
3. When the convoy approaches the desert highway, the fleet team leader will manage the fleet locally regarding the request of the remote management platform or application need. Device#3 is authorized and provisioned by 5G network to connect to 5G network in indirect network connection mode regarding the subscription, the location and the operator’s policy.
4. When there is no coverage of terrestrial access network, Device#2 and UE1 will exchange data between each other via satellite access without going to the remote ground network. Also, Device#3 will use Device#2 as relay UE to communicate with UE1via satellite access without going to the remote ground network.
5. As the movement, there is available coverage of terrestrial access network. Device#2 and UE1 can continue the communication with minimum interruption via terrestrial access network. Device#3 will communication with UE1 via terrestrial access network in direct network connection mode. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.10.4 Post-conditions | UE1 can exchange data with Device#2 and Device#3, to obtain the vehicle status and driver’s information in real-time, and issue the action commands and distribute the route adjustment information in time. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.10.5 Existing features partly or fully covering use case functionality | SA1 has performed several studies on connectivity models and satellite access. As a result, the associated service requirements are introduced to TS 22.261 [2].
Clause 6.9.1 describes the connectivity models as
The UE (remote UE) can connect to the network directly (direct network connection), connect using another UE as a relay UE (indirect network connection), or connect using both direct and indirect connections. Relay UEs can be used in many different scenarios and verticals (inHome, SmartFarming, SmartFactories, Public Safety and others). In these cases, the use of relays UEs can be used to improve the energy efficiency and coverage of the system.
Clause 6.5.2 defines the requirements of efficient user plane about satellite access as below.
For a 5G system with satellite access, the following requirements apply:
A 5G system with satellite access shall be able to select the communication link providing the UE with the connectivity that most closely fulfils the agreed QoS
Clause 6.9.2.5 defines the requirements of connectivity models about satellite access as below.
A 5G system with satellite access shall be able to support relay UE's with satellite access.
NOTE: The connection between a relay UE and a remote UE is the same regardless of whether the relay UE is using satellite access or not.
A 5G system with satellite access shall support mobility management of relay UEs and the remote UEs connected to the relay UE between a 5G satellite access network and a5G terrestrial network, and between 5G satellite access networks.
There is no explicit discussion about the efficient user data path when all the UEs are connecting to the 5G network via the same satellite but in different network connection modes. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.10.6 Potential New Requirements needed to support the use case | [PR 5.10.6-001] Subject to regulatory requirements and operator’s policy, the 5G system with satellite access shall support mechanisms to authorize a remote UE to use UE-Satellite-UE communication via a relay UE (using satellite access).
NOTE 1: It is assumed that the 5G system with satellite access is authorized to assign spectrum resources for the communication between a remote UE and a relay UE.
[PR 5.10.6-002] Subject to regulatory requirements and operator’s policy, the 5G system with satellite access shall support service continuity for a remote UE when the UE communication path moves between a direct network connection via 5G terrestrial access network and an indirect network connection via a relay UE (using satellite access).
NOTE 2: It is assumed that the 5G terrestrial access network and the satellite access network belong to the same operator.
5. 11 Use case on service differentiation for UEs via satellite access |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.11.1 Description | Satellite network has been introduced to 5G system to improve the service availability and reliability since 3GPP Rel-15. In parallel, various UE models with different capabilities (e.g. eMTC UE, CPE) are defined to serve the vertical needs. How to facilitate different types of UEs to benefit from satellite network is worthwhile to study.
The current assumption of 3GPP normative work is, UE shall be capable of GNSS positioning to determine the location for obtaining 5G services via satellite access, which has excluded the possibility to provide 5G services to UEs without GNSS receiver, or unable to determine the location with GNSS receiver. In fact, some services such as broadcast or multicast service, public safety associated services are not highly sensitive to the precise location. Moreover, UEs in stationary mobility type such as for home access, for metering have fixed location to support the position relevant operation during satellite access. The use case illustrates how the UEs with different capabilities obtain 5G services via satellite access. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.11.2 Pre-conditions | It is assumed that network operator has deployed NGSO (e.g. LEO) satellite enabled NG-RAN to provide 5G network PLMN#X in the area Area#A, where have sparse population and no coverage of terrestrial access network as a result.
All UEs support 5G satellite RATs but with different subscription, positioning capabilities and mobility type as Table 5.11.2-1 shows.
Table 5.11.2-1: UEs with different capabilities
Subscription
Positioning Capability
Mobility Type
UE1
Subscriber of PLMN#X for eMBB services
No GNSS capability;
Support other 3GPP positioning technologies
Full mobility
UE2
Subscriber of other PLMN with roaming agreement to PLMN_X, for eMBB services
No GNSS capability;
Support other 3GPP positioning technologies
Full mobility
UE3
Subscriber of PLMN#X for MIoT services
No GNSS capability;
Not support any 3GPP positioning technologies
Full mobility.
UE4
Subscriber of PLMN#X for eMBB services
No GNSS capability;
Not support any 3GPP positioning technologies
Stationary
UE5
Subscriber of PLMN#X for eMBB services
No GNSS capability;
Not support any 3GPP positioning technologies
unknown |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.11.3 Service Flows | 1. All UEs are registering to PLMN_X to get services.
2. The network will provide the available services to authorized UEs considering UE’s location, the subscription and etc.:
• UE1: the network can determine UE’s location based on 3GPP positioning technologies, so it allows all the subscribed services after the location verification regarding regulatory requirements.
• UE2: the network can determine UE’s location based on 3GPP positioning technologies, but only allows limit broadband services such as public safety related services and emergency call regarding the roaming agreement.
• UE3: the network can’t determine UE’s location, so limit the services to those such as emergency message (e.g. PWS message) regarding the operator’s policy and regulatory requirements.
• UE4: the network knows UE4 is stationary and get the location from a reliable and trusted source. Then, the network allows subscribed eMBB services.
• UE5: the network detects UE5 is a dedicated user of digital broadband broadcast application, and fetch the location from the corresponding trusted application platform. Due to the lack of location verification, the network limits the services to those such as broadband broadcast services allowed by the regulatory requirements and the operator’s policy.
Figure 5.11.3-1: Service differentiation for UEs via satellite access |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.11.4 Post-conditions | All UEs can successfully register to PLMN_X and get services based on the subscription, the regulatory requirements, the roaming agreement and the operator’s policy. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.11.5 Existing features partly or fully covering use case functionality | SA1 has introduced several requirements about satellite access in TS 22.261[2].
Clause 6.3.2.3 describes basic requirements about satellite access for 5G system and UE.
The 5G system shall be able to provide services using satellite access.
A UE supporting satellite access shall be able to provide or assist in providing its location to the 5G network.
A 5G system with satellite access shall be able to determine a UE's location in order to provide service (e.g. route traffic, support emergency calls) in accordance with the governing national or regional regulatory requirements applicable to that UE.
The 5G system with satellite access shall be able to support low power MIoT type of communications.
Regarding the above requirements, UE shall have the ability to provide or assist in providing the location for obtaining the services from 5G system. The restriction of UE’s positioning capability has limited the potential users of 5G system using only satellite access, which expect to be served by 5G network. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.11.6 Potential New Requirements needed to support the use case | [PR 5.11.6-001] Subject to the regulatory requirements and operator’s policy, the 5G system with satellite access shall be able to provide services to an authorized UE independently of the UE’s GNSS capability.
[PR 5.11.6-002] Subject to the regulatory requirements and operator’s policy, the 5G system with satellite access shall be able to provide services to an authorized UE registered to VPLMN independently of the UE’s GNSS capability.
[PR 5.11.6-003] Subject to the operator’s policy, the 5G system with satellite access shall be able to determine the location of a UE using only satellite access (e.g. based on 3GPP positioning technologies, based on the information from reliable and trusted sources) in order to provide services in accordance with the governing national or regional regulatory requirements applicable to that UE. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.12 Use case on UAVs using satellite access | |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.12.1 Description | In Mediterranean climate regions, forest fires are quite common in summer months due to temperature rise [14]. The early detection and monitoring of forest fire is important for fire suppression quickly and reducing the loss of human and property. Therefore, how to detect the forest fire in real time and accurately is an urgent problem to be solved. Another problem is that due to extremely low population density and complex geography, these regions are often not covered by terrestrial networks.
UAV equipped with satellite access capabilities is a feasible method, mainly through the following steps:
• The UAV collects real-time information (including high-precision three-dimensional surface topographic data, real-time pictures, real-time video, etc.);
• This real-time information is transmitted to the forest fire monitoring centre via the 5G network with satellite access;
• The forest fire monitoring centre monitors whether there is a fire, and may request the position of the UAV and adjust its route;
• The positioning services request and adjustment command are sent to the UAV via the 5G network with satellite access.
Forest fire monitoring centre with AI system can optimize the route through real-time information collected by UAV. In addition, the 5G system provides high-precision positioning of the UAV, which has been specified in 3GPP TS 22.261 [2]. But for UAVs using only satellites access, 5G system is difficult to provide high-precision positioning service under low latency. The end-to-end delay of LEO based satellite access can reach 35 ms [2]. After 5G system gets the real-time location data of flying UAV, it sends them to a trusted third party (e.g., The forest fire monitoring centre equipped with AI system) for UAVs to assist flying. |
1c7e630f4af53df4342c640c46cce842 | 22.865 | 5.12.2 Pre-conditions | Forest fire monitoring centre has several UAVs to patrol the Forest A. Each UAV has a 4K camera for collecting real-time pictures.
In Forest A, there is no terrestrial network. So, the Forest fire monitoring centre has signed contract with Sat A, an operator with satellite communication services. Then, these UAVs can send real-time pictures to the forest fire monitoring centre via satellite.
The forest fire monitoring centre supports UTM function, and deploys AI system. It can evaluate these pictures to determine whether a fire is present or whether the UAV's flight route is off-course. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.