hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.22.1 Description | Mobile metaverse services allow people to enjoy an online digital concert with their avatars beyond the limitation of time and space. In order to provide immersive interactive location agnostic service experience to mobile metaverse service customers, large amount of computing resouces is needed to perform real-time processing for audio, video, and interactive data, etc. The thing to realise here is that different customers will use terminals e.g. XR glasess with different brands and different processing capabilities, some of the glasses will not have enough computing resources to perform the real-time rendering. Through split rendering, most of the computing work task can offload to the network, the high speed and low latency transmission provided by 5G system can cooperate with the edge cloud side for real-time rendering, and combine with the local optimized rendering of the XR terminal side to provide the immersive and unbounded XR experience. In addition to this, similar to the real world, people are more likely to watch a concert together with their friends, further, the mobile metaverse live concert service is also provides private boxs for group of avatars to enjoy the concert privately, and different types of social authority can be provided in the private box on demand. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.22.2 Pre-conditions | 1) Alex, Bob and Carey are good friends live in different cities, they agree to watch the mobile metaverse live concert together.
2) Alex, Bob and Carey are equipment with XR glasses and tactile, the equipment can capture their voice, facial expression, pose information to generate avatars and interact with the whole live concert.
3) Enough computing resources can be provided to the mobile metaverse live concert service and the 5G network is capable of providing sufficiently high throughput and low latency network transmission. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.22.3 Service Flows | 1. Alex, Bob and Carey’s subscribe to the mobile metaverse live concert services and order a “private box” which can only be used by themselves. Alex, Bob and Carey will be represented at the virtual concert event by their avatars.
2. Due to extensive computing resource requirement for image rendering in the interactive live concert, and Alex and Carey’s glasses are not strong enough to perform this processing, the UEs negotiate with the mobile network operator to offload the rendering service to the edge cloud. Carey's glasses can only receive the rendered image and show it in the field of view. Bob’s glass is more advanced, which can render the image itself.
3. The concert begins and the three friends access the mobile metaverse service. The live singer is presented to the audience as her own avatar. During the show, the singer and all the audience will be represented by their own avatars in the virtual space. Alex, Bob and Carey can adjust their own visual perspective, such as panoramic view, close range or even backstage. At the same time, they can also view the singer's voice and movement, and immerse themselves in the concert.
4. At the same time, extra VIP services can be provided in the “private box”, e.g. to chat with other audience members in the private box without being overheard. The virtual singer may also enter the "private box" to hold a personal meeting with her selected fans. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.22.4 Post-conditions | The consumers in the mobile metaverse live concert service enjoy a great immersive experience and socialize with their friends.
The 5G system is capable of supporting the communication required by the immersive mobile metaverse live concert service. Some extra edge computing services are also provided to some consumers whose equipment has insufficient computing capacity. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.22.5 Existing feature partly or fully covering use case functionality | The functional and performance requirements for AR/VR services have been captured in TS 22.261 clause 7.6. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.22.6 Potential New Requirements needed to support the use case | [PR 5.22.6-1] Subject to operator policy, the 5G system shall be able to support avatar-based multiparty communication in mobile metaverse service. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.23 Use Case on cooperation between metaverse and network using interactive XR | |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.23.1 Description | The mobile metaverse allows users to access an endless virtual world at anytime and anywhere through their terminals. The mobile metaverse are expected to behave as the real world, which means in addition to rendering a virtual environment like the physical world, the perceived spatial-temporal consistency is also the key point to achieve an immersive location agnostic service experience.
In mobile metaverse, spatial-temporal consistency for single user could mean, for example, dropping a virtual pen and seeing this pen fall subsequently. While for multiple players, this consistency could mean, for example, that one person cuts down a tree and other people see the tree falling down. This user experience requires the motion-to-photon latency in the range of 7 ms to 15ms [5] at least for a single user viewing the consequence of her own actions. Immersive VR requires the delivery of massive amount of data (in the order of Gigabyte) at ultra-low latency (less than 20 ms) [54].
NOTE: For location agnostic service experience involving multiple users who are not in the same location, the requirements above do not apply, since the service can impose ordering and timing of representations of virtual events in an arbitrary manner.
It should be noted that the computation resources for rendering involved in the mobile metaverse is different from the cloud gaming and traditional VR. For example, running a typical massively multiplayer online game today requires multiple tera FLOPS of graphics horsepower, and the demand is expected to grow by two orders of magnitude to create fully immersive mobile metaverse experiences. [55]
For the mobile metaverse world, distributed computation is an inevitable processing mode, so the selection of proper servers and data centers should consider the requirements of network delay, processing delay, storage and computation resource. The goal is to minimize the user's perception of delay.
Therefore, in order to obtain consistent experience in mobile metaverse service anytime and anywhere, deep collaboration between mobile metaverse and 5G network is needed. The potential collaboration aspects may include caching location, computation location, communication path, traffic scheduling and resource allocation in network. For example, when a service request emerges, the network control policy needs to coordinate the selection of (i) caching locations to provide digital objects, (ii) computation locations to execute service functions, and (iii) communication paths to route all associated data streams, jointly optimized with dynamic decisions on (iv) traffic scheduling and (v) resource allocation at all network locations. [55] |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.23.2 Pre-conditions | There are about 12,000 players sign up for a popular game and appear simultaneously in a specific setting, such as Eve Online in 2021. Due to the limitations of the existing server processing, it is not possible to support such a large number of high concurrency, so the network and application server need to cooperate to support the distribution of visitors to other servers while ensuring low latency requirement by XR applications. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.23.3 Service Flows | 1. Bob is a player who attends a popular AR interactive game and gathers with others in a shared environment, they are aware of each other’s action so that they need high synchronization.
2. The service provider will provide deployment information of each server to the 5G network, and request the Bob’s physical location and transmission delay in 5G network.
3. According to the cooperation agreement with application, 5G network will expose information to service providers, including the physical location and network delay of specific terminals or a group of terminals. The network delay includes the delay inside 5G system (UE to PSA UPF) and the latency information between PSA UPF and some potential servers.
4. The new server is selected by the service provider according to the UE location, network delay, business requirements, computation resource and storage resource of application servers. The decision result will be sent back to 5G network. Then the 5G network can then formulate corresponding policies for the service flows.
5. The content information will be synchronized to the new server in real time. 5G network should support the ultra-low latency data transmission, potentially among multiple operators. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.23.4 Post-conditions | Bob will have a good experience in this interactive AR game. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.23.5 Existing features partly or fully covering the use case functionality | 3GPP started the work of edge computing from R15 to R18. In R15, AF influence mechanism is introduced to inform the 5G network of the application deployment information to assist UPF selection. In R16, 5G system supports QoS monitoring mechanism for end-to-end delay monitoring for URLLC services. In R17, 5GS supports to solve the problem of edge DNS selection and service migration between different edge platforms. In R18, the work focuses on the edge computing platform access from other operator network, and the distribution of network policies for a group of local UEs. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.23.6 Potential New Requirements needed to support the use case | No potential new requirements have been identified. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.24 Use Case on Authorization of Avatar Usage rights | |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.24.1 Description | In metaverse, digital humans (avatars) are widely used in business activities, such as advertising, news reporting, live shows. With the maturity of digital human technologies and the continuous growth of market demands, lifelike avatars have become reality in recent years. In the future, more and more people are expected to use their own avatar to participate in business activities in the virtual world. Especially, celebrities, famous professors and other people with special social positions have influences also in the virtual world. In some scenarios, authorization of avatar usage rights is needed for commercial or other purposes. If there were no proper management of avatar usage rights, it could cause the spread of false information, even result in chaos in virtual world.
Therefore, the 5G system needs to support management and authorization of avatar usage rights. The owner of the avatar is expected to be responsible for the speech and behavior of his/her avatar. An individual or an enterprise has to be authorized by the owner of an avatar before using the avatar especially in business activities. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.24.2 Pre-conditions | Singer J has her own lifelike avatar, which is used for her live concerts in metaverse. Her touching voice has won hundreds of millions of fans. Company A is a clothing manufacturer. Seeing the commercial value of Singer J, the company invited her to be the company’s brand ambassador, who helps to increase brand awareness and attends product promotion activities. Singer J has signed one-year business contract with Company A. Subject to the contract, Singer J’s avatar is the brand ambassador for Company A in metaverse.
MNO B provides management services (including authorizing and deauthorizing) for the use of avatars in the mobile metaverse services. Each avatar has been assigned a unique identification code in MNO B’s management system. MNO B also provides avatar storage services.
Singer J is one of the subscribers of MNO B, and Company A is also served by MNO B. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.24.3 Service Flows | 1. Company A registers with the MNO B as an enterprise customer, while Singer J registers as an individual customer of MNO B. MNO B assigns IDs for Company A and Singer J respectively.
2. Singer J registers her personal avatar with MNO B. The avatar is lifelike and mapped to Singer J’s ID in real world. So MNO B identifies and stores the avatar and its ID, also associates with the avatar’s owner, Singer J’s ID.
3. Company A sends a request for the usage rights of Singer J’s avatar that is managed by MNO B.
4. MNO B sends a request to Singer J to ask for authorization of the avatar to be used in the mobile metaverse services.
5. After being confirmed by Singer J, Company A’s usage rights of avatar has been authorized. MNO B updates the system with the information that Company A has the usage rights of Sing J’s avatar. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.24.4 Post-conditions | Upon authorization, Singer J has granted the usage rights of her avatar to Company A for one year to be used in mobile metaverse services. During this year, Company A is authorized to use Singer J’s avatar for business purposes. When Company A wants to use Singer J’s avatar in a mobile metaverse service, the 5GS searches the avatar by its ID, and pushes the requested avatar to company A. At the end of the year, Company A’s usage rights of Singer J’s avatar will be duly terminated. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.24.5 Existing features partly or fully covering the use case functionality | None. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.24.6 Potential New Requirements needed to support the use case | [PR 5.24.6-1] Subject to regulatory requirements, user consent and operator’s policy, the 5G system shall support mechanisms to identify an avatar and associate the avatar with a subscriber (i.e. the owner of the avatar).
[PR 5.24.6-2] Subject to regulatory requirements, user consent and operator’s policy, the 5G system shall be able to authorize the avatar to be used in mobile metaverse services.
[PR 5.24.6-3] Subject to regulatory requirements, user consent and operator’s policy, the 5G system shall provide time-bound authorization services for an avatar to be used in mobile metaverse services.
[PR 5.24.6-4] Subject to regulatory requirements, user consent and operator’s policy, the 5G system shall be able to support mechanisms to manage the authorization information about the use of an avatar in mobile metaverse services (e.g. the applied time-bound authorization services, the authorized users).
[PR 5.24.6-5] Subject to regulatory requirements, user consent and operator’s policy, the 5G system shall be able to identify the subscriber who has the right to use an avatar in mobile metaverse services. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.25 Use Case on Enabling Metaverse services to users via multiple access connections | |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.25.1 Description | The metaverse enables immersive virtual media, 3D avatar and holographic communications for realizing use cases such as interactive gaming, virtualized shared workspaces, and immersive conference rooms for remote collaboration, etc. The goal is to create a virtual world we can work in, interact with, and even escape to. Many mobile metaverse use cases are applicable to indoor and/or localized areas such as home, offices, stadiums, shopping malls, movie theatres, theme parks, hospitals, universities, concert halls, etc. Even though metaverse services go beyond virtual reality media presenting virtual worlds that seem to be distant, the scenarios that this use case focusses on are tied to a single physical location which is mostly indoors and serving a localized area. Such physical locations may prefer non-3GPP (trusted, untrusted or wireline) access.
Some mobile metaverse services require more bandwidth and lower latencies which can be challenging to meet. Major improvements to satisfy these requirements of uninterrupted, lag-free, immersive mobile metaverse service experience using non-3GPP access have been made such as:
- incorporation of 1200 MHz of new spectrum in the 6 GHz band with Wi-Fi 6E enabling bigger channel sizes up to 160 MHz
- support up to 1024 QAM with Wi-Fi 6 and 6E and Wi-Fi 7 aiming to support up to 4096 QAM
- doubling maximum channel bandwidth available to each device to 320MHz in the 6GHz band with Wi-Fi 7
- incorporation of High Band Simultaneous (HBS) Multi-Link Operation (MLO) in 802.11be that aggregates two simultaneous 160 MHz channels (four streams) in 5 GHz and 6 GHz bands reducing latency to < 2msec
In case of converged or hybrid network architecture, a single mobile metaverse user can access mobile metaverse services via 5GS using both 3GPP and non-3GPP accesses simultaneously. In such scenario, the metaverse traffic would need to be synchronized as it may be subject to varying latencies when routed over both 3GPP and non-3GPP access. Alternatively, a single mobile metaverse service can be accessed by multiple users across multiple access networks from a network operator. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.25.2 Pre-conditions | Two friends and neighbors Mark and Bob want to enjoy their weekend using a Metaverse application for immersive gaming. Mark is using his home residential broadband (non-3GPP) while Bob is using the 3GPP access network from the same network operator. Both the 3GPP and non-3GPP access network are connected to the network operators 5GC. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.25.3 Service Flows | 1. Mark starts the immersive gaming via an authorized 3rd party metaverse application using the network operators broadband access network (non-3GPP access).
2. Bob joins the immersive gaming to play along with Mark via the same authorized 3rd party mobile metaverse services using the same network operator but connecting to the 3GPP access network.
3. Both Mark and Bob experience different network conditions, e.g., bitrate, reliability, latency across the access networks.
4. 5GS exposes varying network condition changes across the two access networks to an authorized 3rd party mobile metaverse service.
5. Based on the real-time network condition information shared by 5GS, the authorized 3rd party mobile metaverse service adjusts the requested QoS for both users for coordinated user experience.
6. Based on the requested QoS from the authorized 3rd party mobile metaverse service, the 5GS performs dynamic policy updates for the users to meet the desired QoS levels for the metaverse traffic and synchronizes the metaverse application data streams for both users using different access networks. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.25.4 Post-conditions | Both Mark and Bob accessing the same mobile metaverse service across different access networks from the same operator can get the same coordinated user experience even when experiencing different network conditions. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.25.5 Existing features partly or fully covering the use case functionality | The 5G system supports non-3GPP access concurrent with 3GPP access and traffic steering already. The traffic steering aspects are covered in TS 24.193.
It is already possible to expose QoS monitoring information to third parties, when using 3GPP access.
Dynamic QoS policy updates are also possible in the 5GS in the HPLMN and VPLMN.
In clause 6.43.2 of 3GPP TS 22.261, there are the following requirements:
The 5G system shall enable an authorized 3rd party to provide policy(ies) for flows associated with an application.
The policy may contain e.g., the set of UEs and data flows, the expected QoS handling and associated triggering events, and other coordination information.
The 5G system shall support means to apply 3rd party provided policy(ies) for flows associated with an application. The policy may contain e.g., the set of UEs and data flows, the expected QoS handling and associated triggering events, and other coordination information.
NOTE: The policy can be used by a 3rd party application for the coordination of the transmission of multiple UEs’ flows (e.g., haptic, audio, and video) of a multi-modal communication session. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.25.6 Potential New Requirements | [PR 5.25.6-1] Subject to operator policy and user consent, 5G system shall be able to provide means to expose network performance information (e.g., bitrate, latency) to an authorized 3rd party metaverse application.
NOTE: The network performance information can be per UE and take into account all available 5G access network types with the aim of improving user experience.
[PR 5.25.6-2] 5G system shall be able to provide means to enable authorized 3rd party to synchronize the metaverse traffic which is routed or steered over available 5G access networks. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.26 Use Case on IMS-based 3D Avatar Call Support for Accessibility Use Case | |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.26.1 Description | 3GPP has long standardized functionality to support availability of communication for users with disabilities. Global Text Telephony [56] provides a character-by-character text conversation to enable Global Text for those who rely on it, even for emergency service access. With the advent of speech recognition, it is possible to encode audio calls into text and text can be converted to speech. This kind of conversion goes a long way to achieve ITU-T SG16's Total Conversation vision: "Total Conversation is an ITU-T defined concept that encompasses voice telephony, video telephony and text telephony. The idea is that it gives everyone the chance to communicate with one another regardless of whether they are hearing, hearing impaired or deaf." [57]
There are a number of additional valuable scenarios that could be enabled through the use of IMS 3D Avatar Call, as described in 5.11.
Figure 5.26.1-1: Accessibility Scenarios for IMS 3D Avatar Call
In scenario 1, above, a hearing-impaired user communicates with another using signage. Each user's gestures as well as facial expression and movements are captured by sensors (e.g. these sensors could be part of the terminal equipment) and transformed into an avatar encoding before transmission to the conversational partner. The experience of both parties is natural, and the user experience should resemble that of a video call, albeit with 'idealized lighting and contrast' due to the animation.
In scenario 2, one person speaks while the other signs. The signage of the person on the right is captured as described in scenario 1, but in addition it is analyzed. Research results indicate the likelihood that it will soon be possible to reliably use AI-based programs to capture signage to generate text. [57] It is clear that text to speech is possible. Thus for the user on the left, they can see the person on the right signing and receive an audio rendering of the text they generate.
The speech of the user on the left can be converted to text by means of voice recognition. There is extensive research into text to signage as well as some commercial products already available in this area. It is therefore possible for the user on the right to both see the user on the left speaking, as well as an avatar providing signage, or even an avatar rendering of the user on the left performing signage.
In scenario 3, one of the users may not be able to use IMS 3D Avatar call, e.g. they use terminal equipment without this support. In this case, the user on the left enters text and this is rendered as an avatar signing for the user on the right, if this is desired. The user on the right can express herself using signing, which is captured as text (as described for scenario 2) and sent as GTT text media to the user on the left.
One element is currently not possible with text conversion to other media, be it speech or generated avatar media of signage: the timing and emotions expressed in the communication. As part of scenario 3, we consider the possibility of capturing specific text conventions to indicate speech pauses or emotions.
An additional consideration is that the display equipment used to present the IMS 3D Avatar call may either be a UE itself or a separate monitor that the UE is able to use or is available through the display connected another UE, as by Inter-Device Connectivity (a feature of IMS.)
Finally, the possibility to support a communicating user that is 'software generated' is supported well by this use case. In this case, a variant of scenario 2 could be used where the user on the left is in fact an automated customer support centre representative. The computer-generated speech is rendered as signage to the user on the right, and the signage of the user on the right is rendered as speech to the software-based customer service party. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.26.2 Pre-conditions | Both communicating parties AeCha, Bharathi and Carlos have a mobile subscription with PLMNs Absolute Telecom (PLMN A) and Benefit Wireless (PLMN B) and Celestial Cellular (PLMN C).
Both Arndt and Berndt have UEs that support sensors capable of capturing their facial expressions and movements as well as gestures sufficiently for this use case. They also are able to set their terminal equipment down so they have free hands (either on a tripod or table, etc.) Carl has a UE that is only capable of voice calls. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.26.3 Service Flows | Scenario 1: IMS 3D Avatar Call between two callers employing accessibility features and translation
AeCha calls Bharati. AeCha and Bharati use IMS 3D Avatar Call to communicate through sign language.
AeCha signs using Korean sign language. Bharathi signs using Hindi sign language. There are many forms of sign language in the world that are not mutually comprehensible internationally, and we assume that AeCha and Bharathi would not be able to understand each other's signage directly.
There are a set of services available in the communication channel between AeCha and Bharathi that enable the two of them can communicate.
Figure 5.26.3-1: IMS Avatar Call with Services for Signage to Text and Text Translation
AeCha's signing is captured by the sensors and encoded as Avatar Codec, capturing her use of Korean sign language. In the network, the signage is transcoded into Korean text. The Korean text can be translated into English text. This text can then be used to generate Indian Sign Language (shown in the transcoding function in PLMN B).
It is acknowledged that the translation services included in this use case are not exact, however the possibility to communicate directly using signage, and even with the avatar of the corresponding party could be quite valuable.
The avatars seen by AeCha and Bharathi are a representation of the other party, as sufficient information is exchanged by the 5G system to enable the transcoders that produce the avatar codec in PLMN A and PLMN B to do so.
Scenario 2: IMS 3D Avatar Call and Audio between two callers, with accessibility enhancements
Figure 5.26.3-2: IMS Avatar Call with Services for Signage to Text and Text to Voice
Carlos speaks. His speech is recognized (in a transcoder in PLMN C) and encoded as English Text. This text is transported as media. The text is transcoded (in PLMN B) to Indian sign language encoded in an avatar codec. Bharathi views an avatar signing, using Indian sign language to represent Carlos' speech. The avatar is not a representation of Carlos as there are no sensors capturing Carlos, unless there is a means to configure the transcoder in PLMN B with the avatar information corresponding to Carlos' appearance. This is out of scope of this use case.
Bharathi signs, and this is captured in an Avatar codec that identifies her gestures, facial expression and movements. This is converted to English text in a transcoder function in PLMN B. The English text is sent as media to PLMN C, where a transcoder converts the text to speech. This speech is transported as audio media to Carlos, who hears a synthesized voice expressing the communication that Bharathi signed.
Scenario 3: IMS 3D Avatar Call and GTT between two callers, with accessibility enhancements
Figure 5.26.3-3: IMS Avatar Call with Services for Signage to Text and Text to Voice
In this scenario, Carlos uses a GTT terminal to supply GTT media uplink. This media is converted in a transcoder to avatar codec representing signing in Indian sign language to Bharathi. The avatar is not a representation of Carlos as there are no sensors capturing Carlos, unless there is a means to configure the transcoder in PLMN B with the avatar information corresponding to Carlos' appearance. This is out of scope of this use case.
Bharathi signs, and this is captured in an Avatar codec that identifies her gestures, facial expression and movements. This is converted to GTT text in a transcoder function in PLMN B. The GTT media is delivered to Carlos, who reads text expressing the communication that Bharathi signed. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.26.4 Post-conditions | In each of three scenarios one or both parties are able to sign and see signage in their native sign language in order to communicate with the other party. The possibility to interwork with legacy GTT terminals and legacy audio terminals is also supported. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.26.5 Existing feature partially or fully covering use case functionality | The 5G system supports IMS which is able to handle diverse media, establish calls and support media codec transcoding services.
The 5G system supports GTT. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.26.6 Potential New Requirements | [P.R.-5.26.6-1]The 5G system shall support the encoding of sensor data capturing the facial expression and movement and gestures of a person, in a standard form, such that as part of the avatar encoding
[P.R 5.26.6-2] The 5G system shall support a set of transcoders from and to avatar representations e.g. between text, speech and avatar encoding.
[P.R-5.26.6-3] The 5G system shall support the avatar transcoding functionality to control the appearance of the avatar based on the preferences of its associated user Examples of the controlled appearance could be for the avatar to express behavior, movement, affect, emotions, etc.
[P.R 5.26.6-4] The 5G system shall support a set of transcoders to facilitate accessibility of avatar representation from and to GTT to control the appearance of the encoded avatar
[P.R. 5.26.6-5] The 5G system shall be able to collect charging information for transcoding services associated with IMS-based avatar call. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.27 Use Case on Localized Mobile Metaverse Overload | |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.27.1 Description | The mobile metaverse offering a location related service experience may reach its limits, as significant resource intensive communication is required to support uplink sensor data and downlink media for each user In a crowded environment, such as an amusement park, users may want to experience augmented reality in their local environment.
In this use case, Dream Park is a huge theme park in a city. This theme park has been in operation for several decades. The attractions (roller coasters, etc.) are no longer 'new' or 'state of the art.' In order to increase interest for visitors without upgrading the attractions, the owners now provide extensive virtual content for each location in the park. This allows customers to enjoy and experience the theme park’s thrilling rides in exciting new ways and to share the park with all sorts of animated characters and decoration.
Figure 5.27.1-1: A theme park that offers localized metaverse services
Visitors can select the type of experience they wish. If they do not buy the premium content they can still enjoy the 'brick and mortar' rides, and conditionally (that is, if there is no congestion,) also the premium content. Paid premium users (i.e. users who have purchased tickets to experience special augmented content) can enjoy the premium content at any time, even if there is congestion.
NOTE: This aspect of the use case is not further developed. It is assumed that the support of premium content can be supported in different ways using existing mechanisms.
There is general content that is provided to all visitors, for example, AR public safety messages and announcements. This class of content needs to be delivered very efficiently so it does not produce congestion, but it is not highly interactive or personalized for the specific viewer. This content still perfectly fits the context in which it is displayed, e.g. at the entrance to buildings or along a pathway.
In a major amusement park in 2019, there were an average of 119,000 visitors a day. The park has 2.023 km2 surface area. The resulting user density is 58,824 visitors per km2.
This use case considers how the 5GS can reasonably provide localized mobile metaverse services (AR that fits the location) even in high user density conditions. We will consider three aspects.
- Support for AR content communicated by mass distribution
Attributions for Figure 5.27.1-1.
The amusement park icon is available given creative commons license from thenounproject.com:
Amusement park - Created by Lars Meiertoberens from Noun Project
AR User, per creative commons.
The amusement park image is available at:
Amusement park image - Parque Salitre - Amusement park - Wikipedia: https://en.wikipedia.org/wiki/Amusement_park#/media/File:Parque_Salitre.JPG as per creative commons license. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.27.2 Pre-conditions | Ajay and Vijay also have subscriptions with the operator to receive XR multimedia communication service. They both have a mobile subscription to the local operator, Salvo Net.
Ajay has a premium ticket to the amusement park. Vijay has a normal ticket.
Dream Park offers mobile metaverse services to the park visitors by means of communication services from Salvo Net. They have arranged a specific network slice to suit their localized mobile metaverse services.
In this use case we do not assume that all content is 'all or nothing', that is, either one buys a premium ticket and gets the content, or one does not get any premium content at all. If there is sufficient capacity in the theme park, anyone can access the premium content. This ensure that the park will fill up every day! The availability of 'premium experiences' after a waiting interval gives an incentive to those who visit on weekdays, when there is bad weather, etc. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.27.3 Service Flows | Support for mass distribution of AR content
3.1 The amusement park network slice is 'congested' and there is limited access to premium content. Still, in any case there is 'general content' that has to be delivered to all visitors. This includes public safety announcement, so Dream Park considers the delivery of general content to park visitors crucial to support at all times.
3.2 The amusement park's mobile metaverse service requests exposed functionality of Salvo Net to deliver AR content to all visitors by means of efficient multicast or broadcast transmission, even though the density of visitors is very high (e.g. 60,000 per km2).
3.3 Salvo Net distributes the AR content as requested efficiently and avoiding as much as possible further congestion of the amusement park network slice. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.27.4 Post-conditions | As a result of support for mass distribution of AR content is delivered to all users in the park efficiently, even though there is very high user density.
Different mobile metaverse services are delivered to the user simultaneously, i.e. it is not necessary to deliver only one XR content at the same time. It is therefore necessary to ensure that different mobile metaverse servers can synchronize their delivery of content to prevent clashes in the presentation to the user. This is even more important if there are different mobile metaverse servers that produce different components of multi-modal media that has to be delivered to one or more users. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.27.5 Existing features partly or fully covering the use case functionality | The 5G system provides extensive support for mobile broadband communication and multicast and broadcast services.
The 5G system provides a means by which resources can be dedicated to multicast and broadcast services, so that these resources are dedicated, and do not diminish when the network is congested.
The 5G system supports network slices to provide services according to the requirements of customers who deliver services to mobile users.
The 5G system supports a means to support differentiated QoS policy for different subscribers who are using a particular service. The ARP parameter and other mechanisms for response to congestion in the 5G system cannot be set or otherwise influenced by a third party. There is no way for an AF to request a specific ARP be applied to the session. |
8fc4e7e237d7663b7a5c6a2b6436bde3 | 22.856 | 5.27.6 Potential New Requirements needed to support the use case | [PR 5.27.6-1] Subject to operator policy, the 5G system shall support mechanisms to expose functionality to a trusted third party to be able to select subscribers to whom mobile metaverse media can be distributed in a resource efficient manner.
[PR 5.27.6-2] Subject to operator policy, subject to user consent, the 5G system shall support efficient mechanisms to provide resource efficient communication of third party mobile metaverse media to one or more subscribers.
[PR 5.27.6-3] Subject to operator policy, the 5G system shall support a mechanism to enable multiple authorized third parties to synchronize media communications from multiple service data flows delivered to one or more UEs.
[PR 5.27.6-4] 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-5] Subject to operator policy and regulatory requirements, the 5G system shall support a means by which an authorized third-party service provider can request differentiated handling of specific subscribers using the third party's service during network congestion. |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.