hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.4.4 Unsubscribe_Unicast_QoS_Monitoring operation
| API operation name: Unsubscribe_Unicast_QoS_Monitoring
Description: Unsubscribing from QoS monitoring of a unicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.20
Outputs: See subclause 14.3.2.21
See subclause 14.3.3.4.3 for the details of usage of this API operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.4.5 Obtain_Unicast_QoS_Monitoring_Data operation
| API operation name: Obtain_Unicast_QoS_Monitoring_Data
Description: Request QoS monitoring data of a unicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.33
Outputs: See subclause 14.3.2.34
See subclause 14.3.3.4.4 for the details of usage of this API operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.4.6 Update_Unicast_QoS_Monitoring_Subscription operation
| API operation name: Update_Unicast_QoS_Monitoring_Subscription
Description: Updates the QoS monitoring subscription of a unicast resource.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.38
Outputs: See subclause 14.3.2.39
See subclause 14.3.3.4.5 for the details of usage of this API operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.5 SS_MMetaServiceRequirements API
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.5.1 Subscribe_ MMeta_Service Requirements operation
| API operation name: Subscribe_ MMeta_Service Requirements.
Description: Subscribing for notification related to the MMeta service requirements translation.
Known Consumers: VAL server.
Inputs: See subclause 14.3.2.74
Outputs: See subclause 14.3.2.75
See subclause 14.3.9.2.3 for the details of usage of this API operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 14.4.5.2 Notify_ MMeta_Service Requirements operation
| API operation name: Notify_ MMeta_Service Requirements
Description: Notification of latest QoS data of a monitored unicast resource.
Known Consumers: VAL server.
Inputs: -
Outputs: See subclause 14.3.2.78
See subclause 14.3.9.2.3 for the details of usage of this API operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 15 Service-based interface representation of the functional model for SEAL services
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 15.1 General
| The functional models for SEAL services is represented using functional entities and reference points between the functional entities as specified in subclause 6. The vertical applications consume the SEAL services in the form of APIs. Each SEAL service offers these APIs on a service-based interface to all its consumer entities.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 15.2 Functional model representation
| Figure 15.2-1 illustrates the service-based interface representation of the functional model for SEAL services.
Figure 15.2-1: SEAL generic functional model representation using service-based interfaces
The SEAL function(s) exhibit the service-based interfaces which are used for providing and consuming SEAL services. The service APIs are specified for each SEAL function enabled over the service-based interface. The service-based interfaces of specific SEAL services are specified in this document. All the interactions with SEAL are governed based on the reference point interactions of the functional models specified in subclause 6. VAL function represents the functionalities of the VAL server.
NOTE: The service-based interface Sval for the VAL function is out of scope of the present document.
The service APIs offered by the SEAL function(s) are published and discovered on the CAPIF core function as specified in 3GPP TS 23.222 [8].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 15.3 Service-based interfaces
| Table 15.3-1 specifies the service-based interfaces supported by SEAL.
Table 15.3-1: Service-based interfaces supported by SEAL
Service-based interface
Application functionEntity
Mapping server entity
APIs offered
Slm
Location management function
Location management server
Specified in subclause 9.4
Sgm
Group management function
Group management server
Specified in subclause 10.4
Scm
Configuration management function
Configuration management server
Specified in subclause 11.4
Sim
Identity management function
Identity management server
Specified in subclause 12.4
Skm
Key management function
Key management server
Specified in subclause 13.4
Snrm
Network resource management function
Network resource management server
Specified in subclause 14.4
Snsce
Network slice capability enablement function
Network slice capability enablement server
Specified in 3GPP TS 23.435 [40]
Sdd
Data delivery function
Data delivery server
Specified in 3GPP TS 23.433 [48]
Cccf
CAPIF core function
Not applicable
Specified in subclause 10 of 3GPP TS 23.222 [8]
Snm
Notification management function
Notification management server
Specified in subclause 17.4
Sadae
Application data analytics enablement function
Application data analytics enablement server
Specified in 3GPP TS 23.436 [49]
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 16 Network slice capability enablement
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 16.1 General
| The network slice capability enablement is a SEAL service that offers network slice capability enablement capabilities, such as support for vertical application to slice re-mapping (which can be defined as the mapping of the UEs running a vertical application to different slice), to one or more vertical applications. The NSCE service provides additional functionality and exposes slice capabilities based on 5GS management system services (e.g. MnS services) and 5GS network services (e.g. NEF APIs, NWDAF APIs, NSACF APIs). The detailed specification of NSCE is provided in 3GPP TS 23.435 [40].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 16.2 Functional model
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 16.2.1 General
| The functional model for the network slice capability enablement is specified in 3GPP TS 23.435 [40].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 16.2.2 Void
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 16.2.3 Void
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 16.2.4 Void
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 16.3 Procedures and information flows for network slice capability enablement
| The Procedures and information flows for the network slice capability enablement are specified in 3GPP TS 23.435 [40].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 16.4 SEAL APIs for network slice capability enablement
| The SEAL APIs for the network slice capability enablement are specified in 3GPP TS 23.435 [40].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17 Notification Management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.1 General
| The notification management is a SEAL service that offers the notification functionality to one or more verticals. This service enables VAL clients to subscribe and receive notifications from the VAL servers and thereby offloading the complexity of delivery and reception of notifications to the enabler layer. It provides common notification delivery service to vertical applications.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2 Functional model
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.1 General
| The functional model for the notification management is based on the generic functional model specified in clause 6.2. It is organized into functional entities to describe a functional architecture which addresses the notification management aspects required for vertical applications. Since the notification management is a feature which considers the Uu interfaces, only the on-network functional model is specified in this clause.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.2 Functional model description
| Figure 17.2.2-1 illustrates the generic functional model for notification management.
Figure 17.2.2-1: Functional model for notification management
The notification management client communicates with the notification management server over the NM-UU reference point. The notification management client provides the support for notification management functions to the VAL client(s) over NM‑C reference point. The VAL server(s) communicates with the notification management server over the NM-S reference point for delivering the notification messages which is targeted for the VAL client(s). Notification management server sends these notification messages to the notification management client either through NM-UU interface for direct delivery (e.g. Long-polling, WebSocket) or through the OEM PUSH server for indirect delivery (e.g. FCM, APNS, OMA PUSH) which is implementation specific and outside the scope of this specification.
NOTE: Notification messages from PUSH notification server to the PUSH notification client are delivered either through 3GPP network system or through any non-3GPP system, which is implementation specific.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.3 Functional entities description
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.3.1 General
| The functional entities for notification management service are described in the following subclauses.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.3.2 Notification Management client
| The notification management client functional entity acts as the application client for notification management aspects. It interacts with the notification management server. It handles the notification messages received from the notification management server and deliver it to the corresponding VAL clients residing on the VAL UE.
The notification management client functional entity is supported by the HTTP client functional entities of the signalling control plane.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.3.3 Notification Management server
| The notification management server is a functional entity that handles the notification management aspects by interacting with the notification management client and the VAL servers. The notification management server receives the notification messages from the vertical application layer and delivers it to the notification management client. The notification management server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [8].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.4 Reference points description
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.4.1 General
| The reference points for the functional model for notification management are described in the following subclauses.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.4.2 NM-UU
| The interactions related to notification management functions between the notification management client and the notification management server are supported by NM-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [9] and 3GPP TS 23.501 [10].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.4.3 NM-C
| The interactions related to notification management functions between the VAL client(s) and the notification management client within a VAL UE are supported by NM-C reference point.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.2.4.4 NM-S
| The interactions related to notification management functions between the VAL server(s) and the notification management server are supported by NM-S reference point. This reference point is an instance of CAPIF 2 reference point as specified in 3GPP TS 23.222 [8].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3 Procedures and information flows for notification management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.1 General
| This sub-clause describes the procedure and information flows for notification management service. The notification management procedures apply to on-network VAL service only.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.2 Information flows for notification management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.2.1 Create notification channel request
| Table 17.3.2.1-1 describes the information flow create notification channel request from the notification management client to the notification management server.
Table 17.3.2.1-1: Create notification channel request
Information element
Status
Description
Requestor identity
M
Identity of the requesting notification management client
Channel type
M
Indicates PULL or PUSH method to be used for delivering the notification messages
PUSH channel details (see NOTE)
O
Carries the details of the type of PUSH delivery and its associated data
Validity Duration
M
How long the notification channel will last (i.e. channel lifetime) as requested by the notification management client.
NOTE : This IE shall be present of the channel type is PUSH
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.2.2 Create notification channel response
| Table 17.3.2.2-1 describes the information flow create notification channel response from the notification management server to the notification management client.
Table 17.3.2.2-1: Create notification channel response
Information element
Status
Description
Notification URL
O
The URL to receive the notification message if a PULL method is requested. For some PUSH method implementation (such as WebSockets) this URL is used to start the PUSH notification service from the notification management server
Callback URL
M
The URL to be shared to the VAL server by the VAL client for sending the notifications to the notification management server. The callback URL is unique to the notification management client.
Validity duration
O
How long the notification channel will last (i.e. channel lifetime) as granted by the notification management server.
Channel ID
M
Unique identifier for the created notification channel
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.2.3 Open notification channel
| Table 17.3.2.3-1 describes the information flow open notification channel from the notification management client to the notification management server.
Table 17.3.2.3-1: Open notification channel
Information element
Status
Description
Identity
M
Identity of the requesting notification management client
Notification URL
M
The URL to receive the notification message and it is same as received in the Create notification channel response
Channel ID
M
Identifies the notification channel and the value shall be same as returned in Create notification channel response
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.2.4 Notification message
| Table 17.3.2.4-1 describes the information flow notification message from VAL server to the notification management server and from notification management server to the notification management client.
Table 17.3.2.4-1: Notification Message
Information element
Status
Description
VAL Application ID
M
Identity of the VAL application residing in the VAL UE this notification message is targeted
VAL Service ID
M
Identity of the VAL service for which this notification is generated
Notification data
M
This information element carries the details of the notification data such as type of the event and the data corresponding to the event
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.2.5 Delete notification channel request
| Table 17.3.2.5-1 describes the information flow delete notification channel request from notification management client to the notification management server.
Table 17.3.2.5-1: Delete notification channel request
Information element
Status
Description
Identity
M
Identity of the requesting notification management client
Channel ID
M
Identifies the notification channel to be deleted
Request type
M
De-register or delete channel
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.2.6 Delete notification channel response
| Table 17.3.2.6-1 describes the information flow delete notification channel response from notification management server to the notification management client.
Table 17.3.2.6-1: Delete notification channel response
Information element
Status
Description
Identity
M
Identity of the requesting notification management client
Result
M
Indicates if the deletion of the channel is success or failure or if the VAL server de-registered from channel successfully
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.2.7 Update notification channel request
| Table 17.3.2.7-1 describes the information flow Update notification channel request from notification management client to the notification management server.
Table 17.3.2.7-1: Update notification channel request
Information element
Status
Description
Requestor identity
M
Identity of the requesting notification management client
Channel ID
M
Identifies the notification channel to be updated
Validity Duration
O
How long the notification channel will last (i.e. channel lifetime) as requested by the notification management client.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.2.8 Update notification channel response
| Table 17.3.2.8-1 describes the information flow Update notification channel request from notification management server to the notification management client.
Table 17.3.2.8-1: Update notification channel response
Information element
Status
Description
Validity duration
O
How long the notification channel will last (i.e. channel lifetime) as granted by the notification management server.
Result
M
Indicates if updating of the channel is success or failure
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.3 Procedure for creating notification channel to receive notifications
| Figure 17.3.3-1 below illustrates the procedure for receiving notifications from the notification management server by the notification management client.
Pre-conditions:
1. The notification management client does not have any notification channel open with the notification management server.
Figure 17.3.3-1: Receiving notifications from notification management server
1. The VAL client requests the notification management client to subscribe to and receive notifications from the VAL server.
2. The notification management client creates notification channels (i.e. endpoint URLs), if not created already, to be used by the VAL server to send notification messages. To create notification channel, the notification management client sends a create notification channel request to the notification management server. The desired validity duration for the channels to be used and the notification channel type (PUSH or PULL) are included in the request. The notification management client decides which type of the notification channel to be used based on the UE capability.
3. The notification management server authenticates the notification management client and authorizes its request.
4. The notification management server sends the notification management client the Create notification channel response with the endpoint URLs that will be used by the VAL server to send the notification messages and the notification management client to receive the notification messages. The notification management server also includes what is the valid duration for these endpoint URLs to be used and the channel ID to uniquely identify the channel created in the response.
5. If the notification type is PULL method, the notification management client sends the Open notification channel to the notification management server to start receiving the notification message. For certain PUSH method notification type (such as WebSockets) the notification management client requests the notification management server to start the PUSH notification service with its specific protocol that is outside the scope of this specification.
NOTE 1: This step is not required if the notification client wants to receive the notification messages via PUSH notification server.
6. The notification management client responds to the VAL client the status of its request as in step 1 to receive notifications from the VAL server. It also includes the callback URL which needs to be used by the VAL client while subscribing to the VAL server for receiving notifications. The callback URL is unique to SEAL NMC.
7. The VAL client subscribes to the VAL server for receiving notifications. This request includes the subscription data and the callback URL returned from the notification management server in step 4.
NOTE 2: This step is outside the scope of this specification.
8. The VAL server generates the notification message for the subscription request from the VAL client.
9. The VAL server sends the notification message to the notification management server containing the VAL UE or VAL user ID, VAL service ID, VAL application ID and the notification data utilizing the callback URL provided in step 7.
10. If the delivery method is PULL, the notification management server sends the notification message to the notification management client over the opened notification channel.
NOTE 3: If the delivery method is PUSH via PUSH notification server, the notification management server sends the notification message to the OEM Push server (not shown in the figure and is outside the scope of this specification) to deliver to the notification management client.
11. The notification management client delivers the received notification message to the appropriate VAL client based on the details as received in the notification message from the notification management server.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.4 Procedure for deleting notification channel
| Figure 17.3.4-1 below illustrates the procedure for deleting notification channel by the notification management client.
Pre-conditions:
1. The notification management client has notification channel open with the notification management server.
Figure 17.3.4-1: Deletion of notification channel by the notification management client
1. The VAL client decides to stop receiving notifications from the VAL server and deletes the subscription with the VAL server.
NOTE: Step 1 is outside the scope of 3GPP but triggers step 2.
2. The VAL client requests the notification management client to stop receiving the notifications.
3. If the same notification channel is being used for other VAL clients in the UE, the notification management client sends the delete notification channel request with request type as de-register otherwise the notification management client sends the delete notification channel request with request type as delete to the notification management server. The delete notification channel request carries the channel ID of the notification channel.
4. The notification management server acknowledges the request and sends the delete notification channel response to the notification management client.
5. The notification management client indicates to the VAL client about the status (de-registered or channel deleted or failure) of its request to stop receiving the notification.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 17.3.5 Procedure for updating notification channel
| Figure 17.3.5-1 below illustrates the procedure for updating the notification channel by the notification management client.
Pre-conditions:
1. The notification management client has notification channel open with the notification management server.
Figure 17.3.5-1: Updating notification channel by the notification management client
1. The notification management client detects the expiry timer of the active notification channel being approached and a need for updating the new expiry time on notification management server.
2. To update notification channel, the notification management client sends an update notification channel request to the notification management server with the proposed new validity duration for the active channel.
3. The notification management server authenticates the notification management client and authorizes its request.
4. The notification management server checks whether the new proposed expiry timer is valid or not. The NMS may accept the proposed validity duration from the request or assign a different validity duration based on the local policy.
5. The notification management server sends the notification management client the Update notification channel response with the valid duration for this active notification channel. The notification management client shall store the new valid duration of the notification management channel.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 18 Data Delivery
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 18.1 General
| With increasing demand of applications consumption over mobile networks, more and more application content is transmitted over the mobile networks. Vertical applications have diverse requirements for the application content distribution and delivery. To ease the various data delivery demands for vertical applications, a data delivery enabler offers the data delivery and storage capabilities to one or more vertical applications. The detailed specification of SEAL Data Delivery is provided in 3GPP TS 23.433 [48]
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 19 Application Data Analytics Enablement
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 19.1 General
| The application data analytics enablement is a SEAL service that offers value-add application data analytics capabilities which cover stats/predictions for the end-to-end application service. Considering vertical-specific applications and edge applications as the major consumers of 3GPP-provided data analytics services, the application enablement layer can play role on the exposure of data analytics services from different 3GPP domains to the vertical/ASP in a unified manner; and on defining, at an overarching layer, value-add application data analytics services which cover stats/predictions for the end-to-end application service. The detailed specification of ADAE is provided in 3GPP TS 23.436 [49].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 20 AIML Enablement
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 20.1 General
| AIML enablement (AIMLE) SEAL service exposes the capabilities assisting the VAL layer for providing AIML services. The detailed specification of AIMLE is provided in 3GPP TS 23.482 [56].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21 SEAL services over Satellite Access
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.1 General
| This clause provides clarifications on the procedures and information flows for enabling SEAL services using satellite access.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2 Application satellite coverage availability information (ASCAI) configuration
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.1 General
| The following clauses describe the ASCAI provisioning procedure.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.2 Procedures
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.2.1 Procedures of the ASCAI provisioning
| The procedure for VAL UE obtaining the ASCAI configuration for a particular location of UE is illustrated in figure 21.2.2.1-1.
Pre-conditions:
- The VAL UE has registered to the 3GPP network via satellite access as defined in clause 5.3.2.1 of 3GPP TS 23.401 [9] or clause 4.2.2.2.2 of 3GPP TS 23.502 [11].
Figure 21.2.2.1-1: The ASCAI provisioning
1. The configuration management server obtains the ASCAI locally or from the satellite service provider, and may interact with NWDAF to obtain the target VAL UE's mobility analytics as defined in clause 6.7.2 of 3GPP TS 23.288 [34] and may interact with the SEAL location management server to obtain the VAL UE's information (e.g., location) in order to provide accurate information to the UE. If the configuration management server receives the different kinds of satellite information from different satellite information providers for the same satellite, it may consolidate them in a unified format. The information elements of ASCAI can refer to the table 21.2.3.1-1.
2. The configuration management server sends the ASCAI configuration request to the configuration management client to indicate whether the satellite coverage is available for a particular location and time when the VAL UE uses the satellite access.
3. The configuration management client acknowledges the configuration management server if it supports the satellite access.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.2.2 Procedures for obtaining the application satellite coverage availability information (ASCAI)
| The procedure for VAL UE/VAL server requesting and obtaining the ASCAI from the application enabler is illustrated in figure 21.2.2.2-1.
Pre-conditions:
- The VAL UE is a consumer and has registered to the 3GPP network via satellite access as defined in clause 5.3.2.1 of 3GPP TS 23.401 [9] or clause 4.2.2.2.2 of 3GPP TS 23.502 [11] and has not received the satellite coverage availability information from the network yet.
- The configuration management server has obtained the ASCAI as described in clause 21.2.2.1.
Figure 21.2.2.2.1-1: Obtaining the ASCAI
1. The consumer (i.e. Configuration management client, VAL server) sends Get application satellite coverage availability information (ASCAI) request to the configuration management server to require ASCAI when it is using the satellite access. The request may contain the dedicated satellite ID for the requested UE, the current UE location data, etc.
2. The configuration management server authorizes the request. If the request is granted, it checks the requested ASCAI is available or not. If it’s not available, the configuration management server obtains the ASCAI as described in step 1 of clause 21.2.2.1.
NOTE: If the dedicated satellite ID for the requested UE is included in the request, the configuration management server will only consider the satellite coverage availability information for the dedicated satellite. Otherwise, the configuration management server will consider all of satellites which can serve the requested UE.
3. The configuration management server replies the ASCAI to the consumer (i.e. VAL UE/configuration management client, VAL server) to guide them how to minimize the service impact (e.g. indicate when to trigger the UL/DL service flow if the VAL UE is accessing the satellite). And the VAL UE may retrieve the UE unavailability period (e.g., unavailability period duration or the start time for the unavailability period) as defined in clause 5.4.1.4 of 3GPP TS 23.501 [10] based on the received ASCAI.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.3 Information flows
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.3.1 Application satellite coverage availability information (ASCAI) configuration request
| Table 21.2.3.1-1 describes the information flow from the configuration management server to the configuration management client to configure the ASCAI.
Table 21.2.3.1-1: ASCAI configuration request
Information element
Status
Description
Identity
M
Identity of the requesting VAL user or VAL UE.
VAL service ID
O
Identity of the VAL service that is requested.
ASCAI
M
Defines the application satellite coverage information including a list of geographical areas, corresponding available time periods and satellite RAT types.
> Geographical area
M
It includes a list of geographical area information (e.g. coordinates, as defined in 3GPP TS 29.572 [51]) where the satellite coverage is available.
> Availability time period
M
It provides the time periods when the satellite coverage is available over the indicated geographical area.
> Availability satellite RAT types
O
It provides the satellite RAT types information corresponding to the satellite availability in the indicated geographical area.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.3.2 Application Satellite coverage availability information (ASCAI) configuration response
| Table 21.2.3.2-1 describes the information flow from the configuration management client to the configuration management server for the response of the ASCAI configuration request.
Table 21.2.3.2-1: ASCAI configuration response
Information element
Status
Description
Identity
M
Identity of the requesting VAL user or VAL UE.
Result
M
Indicates the request result.
Cause
O
The cause for the request failure.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.3.3 Get application satellite coverage availability information (ASCAI) request
| Table 21.2.3.3-1 describes the information flow from the configuration management client or VAL server to the configuration management server to obtain the ASCAI.
Table 21.2.3.3-1: Get ASCAI request
Information element
Status
Description
Identity
M
Identities of the requesting VAL user or VAL UE or VAL server.
VAL service ID
O
Identity of the VAL service that is requested.
Satellite ID
O
Indicates the dedicated satellite ID for the requested VAL UE.
Location
O
Indicates the current location data for the VAL UE.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.3.4 Get application satellite coverage availability information (ASCAI) response
| Table 21.2.3.4-1 describes the information flow from the configuration management server to the configuration management client or VAL server to notify the ASCAI.
Table 21.2.3.4-1: Get ASCAI response
Information element
Status
Description
Identity
M
Identity of the requesting VAL user or VAL UE.
VAL service ID
O
Identity of the VAL service that is requested.
ASCAI
M
Defines the application satellite coverage information including a list of geographical areas, corresponding available time periods and satellite RAT types.
> Geographical area
M
It includes a list of geographical area information (e.g. coordinates, as defined in 3GPP TS 29.572 [51]) where the satellite coverage is available.
> Availability time period
M
It provides the time periods when the satellite coverage is available over the indicated geographical area.
> Availability satellite RAT types
O
It provides the satellite RAT types information corresponding to the satellite availability in the indicated geographical area.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.4 APIs for application satellite coverage availability information (ASCAI)
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.4.1 General
| Table 21.2.4.1.1-1 illustrates the APIs for ASCAI.
Table 21.2.4.1-1: List of APIs for ASCAI
API Name
API Operations
Known Consumer(s)
Communication Type
SS_ASCAIInfoRetrieval
Obtain_ASCAI_Info
VAL server
Request/Response
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.4.2 SS_ASCAIInfoRetrieval API
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.4.2.1 General
| API description: This API enables the VAL server to obtain the application satellite coverage availability information (ASCAI) from the configuration management server.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.2.4.2.2 Obtain_ASCAI_Info operation
| API operation name: Obtain_ASCAI_Info
Description: Request the application satellite coverage availability information.
Known Consumers: VAL server.
Inputs: Refer subclause 21.2.3.3
Outputs: Refer subclause 21.2.3.4
See subclause 21.22.2.2 for the details of usage of this API operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3 Satellite S&F events information
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.1 General
| This following sub-clauses shows how the application enablers provisioning the satellite S&F configuration to the VAL UE and expose the satellite S&F events information to the VAL server to help minimize the service interruption (e.g., adjust the DL frequency, etc.) when the VAL UE starts to perform the satellite S&F operation.
NOTE 1: In S&F Satellite operation, the end-to-end exchange of traffic is handled in a sequence of steps reflecting the intermittent availability of the service link (when the satellite can exchange data with the NRM client) and the intermittent availability of the feeder (ground) link (when the satellite can exchange data with the ground network (NRM server)). To support S&F satellite operation, network functionality needs to be deployed on the satellite, as specified in 3GPP TS 23.401 [9].
NOTE 2: The network functionality deployed on the satellite enables that the NRM server can also send/receive request/responses when the feeder link is available and that the NRM client can also send/receive request/responses when the service link is available.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.2 Procedures
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.2.1 NRM Server exposing the S&F events to the VAL server procedure
| Pre-condition:
- The NRM client, the NRM server and the VAL server all are deployed on the ground.
- The PGW-U in 3GPP CN is deployed on the satellite.
- The VAL UE has registered to the 3GPP network via satellite access as defined in clause 5.3.2.1 of 3GPP TS 23.401 [9] and supports the S&F mode.
Figure 21.3.2.1-1: NRM Server exposing the satellite S&F events to the VAL server procedure
1. The VAL server sends the satellite S&F events subscription request to the NRM server in which the subscribed events may include the UE status in S&F mode, the DL estimated delivery time, the trigger conditions, etc.
NOTE: Step 1 is also applicable to the update procedure when the VAL server requires to update the satellite S&F events subscription request.
2. The NRM server authorizes the subscription request from the VAL server.
3. If the subscription request is authorized, the NRM server sends the satellite S&F events subscription request to the NRM client and/or the 3GPP CN respectively.
4. The NRM client and/or 3GPP CN acknowledge the NRM server with the satellite S&F events subscription response respectively.
5. The NRM server responds to the VAL server with the satellite S&F events subscription response.
6. If the trigger condition in the subscription request is met, the NRM client and/or 3GPP CN may report the requested satellite S&F events as specified in table 21.3.3.3 to the NRM server via the satellite S&F events subscription notification.
7. The NRM server notifies the VAL server for the received satellite S&F events in step 6. The VAL server may take them into consideration and adjust the application behaviour (e.g., pending the DL data transition when the UE is registered in S&F Mode, re-transmit the pending DL data when the feeder link is available, adjust the DL traffic volume according to the Estimated S&F DL Delivery Time, etc.) to minimize the service interruption.
8. The VAL server sends the satellite S&F events unsubscribe request to the NRM server to unsubscribe the subscription to monitor the satellite S&F events.
9. The NRM server relays the satellite S&F events unsubscribe request to the NRM client and/or 3GPP CN. And receives the response from the NRM client and/or 3GPP CN respectively.
10. The NRM server replies to the VAL server with the satellite S&F events unsubscribe response.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.2.2 VAL UE reports the UE satellite information procedure
| The Figure 21.3.2.2-1 illustrates the procedure of the VAL UE/NRM client reports the UE satellite information to the NRM server.
This procedure also applies when the VAL UE/NRM client updating its UE satellite information to the NRM server.
Pre-condition:
- The VAL UE has registered to the 3GPP network via satellite access as defined in clause 5.3.2.1 of 3GPP TS 23.401 [9] and supports the S&F mode.
Figure 21.3.2.2-1: VAL UE reports the UE satellite information procedure
1. The NRM client reports the UE satellite information to the NRM server which may contain the UE identity, the UE type (e.g. IoT) and the UE satellite related information, such as the serving satellite ID, the accessing satellite types (LEO, MEO and GEO), the S&F mode indicator, the maximum data storage quota which indicates the maximum data storage quota per application layer on the UE for all of services, etc.
2. The NRM server checks the authorization for the request from the NRM client.
3. After successful authorization, the NRM server sends a Report UE satellite capability response to the NRM client and stores the UE identity and the satellite information.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.2.3 NRM server provisioning the S&F configuration procedure
| Figure 21.3.2.3-1 shows how the NRM Server provides the S&F configuration to the NRM Client based on the service request from VAL server and the VAL UE reported satellite information.
This procedure also applies when the NRM server provides the updated S&F configuration to the NRM client.
Pre-condition:
- The NRM client and the NRM server are deployed on the ground.
- The PGW-U in 3GPP CN is deployed on the satellite.
- The NRM Client has reported the UE satellite information to the NRM server as described in clause 21.3.2.2.
Figure 21.3.2.3-1: NRM Server providing the S&F configuration to the NRM Client procedure
1. The NRM server takes advantage of the service request initiated by the VAL server, the reported UE satellite information (e.g. serving satellite ID, the maximum data storage quota per UE) as described in clause 21.3.2.2 and its pre-configuration, etc. to determine the on-board S&F parameters for the application layer (e.g., maximum S&F data storage quota per UE/service, maximum S&F data retention per UE/service, etc.).
2. After determined the satellite S&F parameters, the NRM server provides such information to the NRM client via sending a satellite S&F configuration request.
3. The NRM client/VAL UE stores the received satellite S&F parameters and may take them into account when the VAL UE starts to operate the S&F operations based on its satellite S&F configuration per service.
NOTE: The VAL UE may consider the pre-configuration, the received parameters from the application enabled layer to determine/update its satellite S&F configuration per service.
4. The NRM client sends the satellite S&F configuration response to the NRM server.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.3 Information flows
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.3.1 Satellite S&F events subscription request
| Table 21.3.3.1-1 describes the information flow from VAL server to NRM server or from the NRM server to NRM client for satellite S&F events subscription request.
Table 21.3.3.1-1: Satellite S&F status events subscription request
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.3.2 Satellite S&F events subscription response
| Table 21.3.3.2-1 describes the information flow from NRM server to the VAL server or from NRM client to NRM server for response of satellite S&F events subscription request.
Table 21.3.3.2-1: Satellite S&F events subscription response
Information element
Status
Description
Identity
M
Identity of the requesting VAL server/VAL users or VAL UEs or NRM server.
Subscription status
M
It indicates the subscription result
Cause
O
The cause for the request failure.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.3.3 Satellite S&F events notification
| Table 21.3.3.3-1 describes the information flow from NRM server to VAL server or from the NRM client to NRM server to notify the subscribed satellite S&F events.
Table 21.3.3.3-1: Satellite S&F status events notification
Information element
Status
Description
Identity
M
Identity of the requesting VAL server/VAL users or VAL UEs or NRM server.
Satellite S&F events
O
List the notification for satellite S&F events that to be monitored for one or more UE(s).
> UE status in S&F mode
O
(NOTE)
Indicates the UE is registered in S&F mode or moving from S&F mode to not registered in S&F mode.
> Estimated S&F DL Delivery Time
O
(NOTE)
Indicates the estimated/expected time required to deliver the data to the UE from the time data has been received in the network.
> Feeder link availability period
O
(NOTE)
Indicates the availability period when the feeder link is available.
Triggering events
M
Identifies the events that triggered NRM client sending the report.
Timestamp
O
Timestamp of the notification report.
NOTE: The definition refers to the clause 5.6.3.10 of 3GPP TS 23.682 [13].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.3.4 Satellite S&F events unsubscribe request
| Table 21.3.3.4-1 describes the information flow from VAL server to NRM server or from the NRM server to NRM client for satellite S&F events unsubscribe request.
Table 21.3.3.4-1: Satellite S&F status events unsubscribe request
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.3.5 Satellite S&F events unsubscribe response
| Table 21.3.3.5-1 describes the information flow from NRM server to the VAL server or from NRM client to NRM server for response of satellite S&F events unsubscribe request.
Table 21.3.3.5-1: Satellite S&F events unsubscribe response
Information element
Status
Description
Request status
M
It indicates the unsubscribe request result.
Cause
O
The cause for the request failure.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.3.6 Report UE satellite information request
| Table 21.3.3.6-1 describes the information flow from the NRM client to the NRM server for reporting the UE satellite related capabilities.
Table 21.3.3.6-1: Report UE satellite information request
Information element
Status
Description
Identity
M
Identity of the VAL user or identity of the VAL UE.
UE type
O
Indicate the type of VAL UEs (e.g. IoT).
Satellite information
O
The satellite information of VAL UE when the VAL UE supports the satellite access.
> Satellite ID
O
Indicates the serving satellite ID for the VAL UE.
> Satellite type
O
Indicates the accessing satellite RAT types (LEO, MEO and GEO) for the VAL UE.
> S&F mode indicator
O
Indicates the UE support the S&F mode or not.
> Maximum data storage quota
O
Indicates the maximum data storage quota for the VAL UE for all of services on the application layer.
> Maximum data retention timer
O
Indicates the maximum data retention timer value for the VAL UE per service on the application layer.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.3.7 Report UE satellite information response
| Table 21.3.3.7-1 describes the information flow the NRM server to the NRM client for the response of reporting the UE satellite related information request.
Table 21.3.3.7-1: Report UE satellite information response
Information element
Status
Description
Result
M
It indicated the request result.
Cause
O
The cause for the request failure.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.3.8 Satellite S&F configuration request
| Table 21.3.8-1 describes the information flow from the NRM server to the NRM client for satellite S&F configuration request.
Table 21.3.3.8-1: Satellite S&F configuration request
Information element
Status
Description
Identity
M
Identity of the requesting VAL user or VAL UE.
VAL service ID
O
Identity of the VAL service that is requested.
Satellite S&F configuration information
O
Indicates the S&F configuration per UE per service when it is using the satellite S&F operation.
> Maximum S&F data storage quota
O
Indicates the maximum data storage quota per UE per service on the application layer when the UE is using the satellite S&F operation.
> Maximum S&F data retention timer
O
Indicates the maximum data retention timer value per UE per service on the application layer when the UE is using the satellite S&F operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.3.9 Satellite S&F configuration response
| Table 21.3.3.9-1 describes the information flow from the NRM client to the NRM server for the response of satellite S&F configuration request.
Table 21.3.3.9-1: Satellite S&F events subscription response
Information element
Status
Description
Identity
M
Identity of the requesting VAL users or VAL UEs or NRM server.
Result
M
It indicates the request result
Cause
O
The cause for the request failure.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.4 APIs for Satellite S&F events information
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.4.1 General
| Table 21.3.4.1-1 illustrates the APIs for Satellite S&F events information.
Table 21.3.4.1-1: List of APIs for Satellite S&F events
API Name
API Operations
Known Consumer(s)
Communication Type
SS_SatelliteS&FInfoEvent
Subscribe_S&F_Info
VAL server
Subscribe/Notify
Unsubscribe_ S&F _Info
VAL server
Update_ S&F _Info_Subscription
VAL server
Notify_ S&F _Info
VAL server
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.4.2 SS_SatelliteS&FInfoEvent API
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.4.2.1 General
| API description: This API enables the VAL server to trigger reporting of satellite S&F information from the NRM server over LM-S.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.4.2.2 Subscribe_S&F_Info operation
| API operation name: Subscribe_S&F_Info
Description: Subscription to the satellite S&F events.
Known Consumers: VAL server.
Inputs: Refer subclause 21.3.3.1
Outputs: Refer subclause 21.3.3.2
See subclause 21.3.2.2 for the details of usage of this API operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.4.2.3 Unsubscribe_S&F_Info operation
| API operation name: Unsubscribe_S&F_Info
Description: Unsubscribe to the satellite S&F events.
Known Consumers: VAL server.
Inputs: Refer subclause 21.3.3.4
Outputs: Refer subclause 21.3.3.5
See subclause 21.3.2.2 for the details of usage of this API operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.4.2.4 Update_ S&F _Info_Subscription operation
| API operation name: Update_ S&F _Info_Subscription
Description: Update the subscription to the satellite S&F events.
Known Consumers: VAL server.
Inputs: Refer subclause 21.3.3.1
Outputs: Refer subclause 21.3.3.2
See subclause 21.3.2.2 for the details of usage of this API operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 21.3.4.2.5 Notify_ S&F _Info operation
| API operation name: Notify_ S&F _Info
Description: Notification to the existing subscription.
Known Consumers: VAL server.
Inputs: Refer subclause 21.3.3.3
Outputs: Refer subclause 21.3.3.3
See subclause 21.3.2.2 for the details of usage of this API operation.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 22 Spatial anchors (SAn) service
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 22.1 General
| Spatial anchors (SAn) SEAL service exposes the capabilities assisting the VAL layer for managing spatial anchors for their applications. The detailed specification of SAn service is provided in 3GPP TS 23.437 [58]. The spatial anchor service is used for metaverse applications enablement.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 23 Spatial map (SM) service
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 23.1 General
| Spatial map (SM) SEAL service exposes the capabilities assisting the VAL layer for managing spatial map for their applications. The detailed specification of SM service is provided in 3GPP TS 23.437 [58]. The spatial map service is used for metaverse application enablement.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 24 Digital Asset
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 24.1 General
| Digital Asset SEAL service exposes the capabilities for Digital Asset management towards the VAL application layer. The detailed specification of Digital Asset service is provided in 3GPP TS 23.438 [59].
Annex A (informative):
SEAL integration with 3GPP network exposure systems
NOTE: Not all possible SEAL integration with 3GPP network exposure systems are illustrated in this subclause.
Figure A-1 illustrates the service-based interface representation of the functional model for SEAL services integration with 5GC network exposure system.
Figure A-1: SEAL integration with 5GC network exposure system
The details of NEF and its role in exposing network capabilities of 5GS to 3rd party applications are specified in 3GPP TS 23.501 [10] and the details of NEF service operations are specified in 3GPP TS 23.502 [11].
Figure A-2 illustrates the service-based interface representation of the functional model for SEAL services integration with EPC network exposure system.
Figure A-2: SEAL integration with EPC network exposure system
The details of SCEF and its role in exposing network capabilities of EPS to 3rd party applications are specified in 3GPP TS 23.682 [13].
Annex B (informative):
SEAL functional model mapping with Common functional architecture (CFA)
The table B-1 shows the mapping between the SEAL functional model and the Common functional architecture (CFA). The details of CFA functional entities and reference points are specified in 3GPP TS 23.280 [4].
Table B-1: SEAL functional model mapping with CFA
SEAL service
Aspects
SEAL
CFA
Location management
Functional entity
Location management client
Location management client
Location management server
Location management server
Reference points
LM-UU
CSC-14
LM-S
CSC-15
LM-C
Not defined
LM-E
Not defined
LM-PC5
Not defined
Group management
Functional entity
Group management client
Group management client
Group management server
Group management server
Reference points
GM-UU
CSC-2
GM-S
CSC-3
GM-C
Not defined
GM-E
CSC-16
GM-PC5
CSC-12
Configuration management
Functional entity
Configuration management client
Configuration management client
Configuration management server
Configuration management server
Reference points
CM-UU
CSC-4
CM-S
CSC-5
CM-C
Not defined
CM-E
CSC-17
CM-PC5
CSC-11
Identity management
Functional entity
Identity management client
Identity management client
Identity management server
Identity management server
Reference points
IM-UU
CSC-1
IM-S
Not defined
IM-C
Not defined
IM-E
Not defined
IM-PC5
Not defined
Key management
Functional entity
Key management client
Key management client
Key management server
Key management server
Reference points
KM-UU
CSC-8
KM-S
CSC-9
KM-PC5
Not defined
Network resource management
Functional entity
Network resource management client
Not defined (see NOTE)
Network resource management server
Not defined (see NOTE)
Reference points
NRM-UU
Not defined (see NOTE)
NRM-S
Not defined
NRM-C
Not defined
NRM-E
Not defined
NRM-PC5
Not defined
NOTE: Defined in the application layer for Mission Critical service (e.g. MCPTT).
Annex C (normative):
Protocol realizations of LWP in the signalling control plane
C.1 General
This annex specifies protocol realizations of the light-weight protocol in the signalling control plane.
C.2 Usage of CoAP as LWP
This clause specifies how the CoAP protocol shall be used to realize the generic light-weight protocol in the signalling control plane.
The Constrained Application Protocol (CoAP) is a light-weight protocol defined by IETF in RFC 7252 [32] and designed specifically for application layer communication for constrained devices. CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments. RFC 7252 [32] specifies bindings to UDP and DTLS. IETF RFC 8323 [33] specifies bindings to TCP, WebSocket and TLS.
Figure C.2-1 illustrates the functional model for the LWP signalling control plane when CoAP is used as the LWP.
Figure C.2-1: Functional model for LWP signalling control plane when CoAP is used as LWP
When CoAP is used to realize the generic light-weight protocol defined in clause 6.2, then,
1. CoAP client is a realization of the LWP client
2. CoAP proxy is a realization of the LWP proxy, with the following clarifications:
a. CoAP proxy shall be able to terminate a DTLS, TLS or secure WebSocket session on LWP-1 reference point;
b. CoAP proxy shall be able to act as a cross-protocol CoAP-HTTP proxy to support LWP-HTTP-2 and LWP-HTTP-3 reference points;
3. CoAP server is a realization of the LWP server
4. CoAP supports the interactions over LWP-1, LWP-2 and LWP-3 reference points
5. The usage of CoAP by the SEAL service enablers shall follow the rules set out in clause 6.4.3.5.
Annex D (informative):
Exemplary location profile attributes
The table D-1 shows the example of attributes that can be used for the location profiles.
Table D-1: Exemplary location profile attributes
Profile ID / name
Vertical / use case/environment
Positioning Service Level (for IIOT) / QoS / accuracy
Positioning Method(s) / Priorities
Involved 3GPP functionalities / Priorities
Required APIs / API info
Other
Location profile #1
Industrial scenario; indoors; mobile robots/ AGVs
Service Level 6 /
cm level accuracy / absolute/relative/ both
1. DL-TDOA,
2. UL-TDOA,
3. Multi-RTT methods,
4. WLAN, 5. motion sensors,
6. Bluetooth
1. LMF
2. RAN-LMC, 3. SEAL LMS
NEF APIs, SEAL APIs
Verification / augmentation required
Location profile #2
V2X;
outdoor
Decimeter level accuracy /... absolute/relative/both
1. DL-TDOA,
2. Multi-RTT methods,
3. GNSS-RTK,
4. Sensor fusion,
5. A-GPS
1. LMF
2. SEAL LMS
3. Other UEs
NEF APIs, MEC APIs
Support for sidelink positioning
Annex E (informative):
Support for Mobile Metaverse use case
In Mobile Metaverse one use case is the 5G-enabled Traffic Flow Simulation and Situation Awareness in which the real conditions of a road including vehicles and other factors are captured with sensors, modelled in a simulation and used to provide guidance for vehicles and users for efficiency and safety. This is a specific example of a broad category of 'situational awareness' services that capture 'virtual representations' of the real world to then advise or control actions taken in the real world. As shown in Figure F-1. real-time processing and computing can be conducted to support traffic simulation and also situational awareness and real time path guidance and real-time safety, or security alerts can be generated for ICVs as well as the driver and passengers.
Figure F-1: Use case of 5G-enabled Traffic Flow Simulation and Situational Awareness [3GPP TR 22.856]
In this use case, the mobile metaverse service requirements are applicable to communication among different entities for multi-user interactions (as can be seen also in Figure F-1). The sessions include UE to UE communications and UE to virtual UE (at the server side) communications.
More specifically, in an example for two identified VAL UEs the following types of VAL sessions may be present:
- VAL session #1: Metaverse app in VAL client 1 sends to virtual UE 1 (in DN side at the VAL server) sensor data / measurements on the physical environment related to VAL UE1 over VAL-UU interface. Virtual UE1 sends back haptic feedback to UE1 (for UE1 and/or UE2 and the environment).
- VAL session #2: Metaverse app in VAL client 2 sends to virtual UE 2 (in DN side at the VAL server) sensor data / measurements on the physical environment related to VAL UE2 over VAL-UU interface. Virtual UE2 sends back haptic feedback to UE2 (for UE1 and/or UE2 and the environment).
- App-specific session #3: Exchange of service related / feedback data between virtual UEs (for example micro-transactions such as avatar updates/modifications or environment changes).
- App-specific session #4: Sensor data / measurements are exchanged between VAL UEs (communication can be over side link) for traffic related to the metaverse service.
To support such use case, SEAL NRM as in clause 14.3.9.2.3 supports the discovery of the virtual UEs (as counterparts of the physical UEs) and identify the sessions required as well as the per session requirement in both physical and virtual world.
Annex F (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2019-01
SA6#28
TS skeleton
0.0.0
2019-01
SA6#28
Implementation of the following pCRs approved by SA6:
S6-190283, S6-190284, S6-190285, S6-190301, S6-190210, S6-190286, S6-190272, S6-190287, S6-190295, S6-190215, S6-190296, S6-190297
0.1.0
2019-03
SA6#29
Implementation of the following pCRs approved by SA6:
S6-190446, S6-190447, S6-190448, S6-190509, S6-190526, S6-190515, S6-190452, S6-190453, S6-190510, S6-190511, S6-190456, S6-190457, S6-190458
0.2.0
2019-03
SA#83
SP-190063
Presentation for information at SA#83
1.0.0
2019-04
SA6#30
Implementation of the following pCRs approved by SA6:
S6-190661, S6-190663, S6-190848, S6-190746, S6-190747, S6-190748, S6-190749, S6-190750, S6-190872
1.1.0
2019-05
SA6#31
Implementation of the following pCRs approved by SA6:
S6-191003, S6-191115, S6-191005, S6-191116, S6-191117, S6-191007, S6-191189, S6-191212, S6-191121, S6-191012, S6-191229, S6-191191, S6-191124, S6-191013, S6-191192, S6-191193
1.2.0
2019-05
SA#84
SP-190473
Presentation for Approval at SA#84
2.0.0
2019-06
SA#84
SP-190473
MCC Editorial update for publication after TSG SA approval (SA#84)
16.0.0
2019-09
SA#85
SP-190733
0001
2
F
Architecture requirements group management
16.1.0
2019-09
SA#85
SP-190733
0002
3
F
Group announcement and join
16.1.0
2019-09
SA#85
SP-190733
0003
6
F
Corrections to network resource management procedures
16.1.0
2019-09
SA#85
SP-190733
0004
F
N5 reference point description
16.1.0
2019-09
SA#85
SP-190733
0006
1
F
Change of service-based interface representation of the functional model for SEAL
16.1.0
2019-09
SA#85
SP-190733
0007
F
Remove EN on bearer type identification
16.1.0
2019-09
SA#85
SP-190733
0008
F
Remove EN on granularity of decision of NRM server
16.1.0
2019-12
SA#86
SP-191111
0009
1
F
Corrections to naming and other fixes
16.2.0
2019-12
SA#86
SP-191111
0010
2
F
Result element missing
16.2.0
2019-12
SA#86
SP-191111
0011
1
F
Anonymous requests
16.2.0
2019-12
SA#86
SP-191111
0012
1
F
No multicast resource management in 5GS
16.2.0
2019-12
SA#86
SP-191111
0013
2
F
Mention of SA3 responsibility in a published TS is not relevant.
16.2.0
2019-12
SA#86
SP-191111
0014
2
F
SEAL APIs corrections
16.2.0
2019-12
SA#86
SP-191111
0015
1
F
Update to location configuration procedure
16.2.0
2020-03
SA#87-E
SP-200114
0016
F
Complete SS_NetworkResourceAdaptation API
16.3.0
2020-03
SA#87-E
SP-200114
0017
F
Correct dynamic MBMS bearer establishment
16.3.0
2020-03
SA#87-E
SP-200114
0019
F
MBMS procedures alignment
16.3.0
2020-07
SA#88-E
SP-200338
0021
1
F
Align the Group Management API operation name with CT3
16.4.0
2020-07
SA#88-E
SP-200338
0022
2
F
Clarification and correction on media direction mode
16.4.0
2020-09
SA#89-E
SP-200841
0023
2
F
Correct location trigger configuration
16.5.0
2020-09
SA#89-E
SP-200841
0024
1
F
Clarifications on MBMS listening status uage
16.5.0
2020-09
SA#89-E
SP-200841
0025
2
F
Correct SEAL location API operations
16.5.0
2020-09
SA#89-E
SP-200841
0026
1
F
Correction to NRM unicast procedures
16.5.0
2020-12
SA#90-E
SP-200991
0029
1
F
Clarification on group join notification
16.6.0
2020-12
SA#90-E
SP-200991
0030
1
F
Resolution of ENs on security aspects
16.6.0
2020-12
SA#90-E
SP-200991
0033
1
F
Clarifications for T8 interface
16.6.0
2020-12
SA#90-E
SP-200991
0036
1
F
Correction to location notification to VAL server
16.6.0
2020-12
SA#90-E
SP-200998
0027
3
B
Tracking UE and obtaining dynamic UE information
17.0.0
2020-12
SA#90-E
SP-200998
0031
2
B
Support local MBMS
17.0.0
2020-12
SA#90-E
SP-200999
0032
2
B
Network slice adaptation for VAL applications
17.0.0
2020-12
SA#90-E
SP-200999
0034
1
F
Clarifications for T8 interface
17.0.0
2020-12
SA#90-E
SP-200999
0035
1
B
Temporary Groups formation
17.0.0
2021-04
SA#91-E
SP-210181
0038
3
B
Service identification in location management procedures
17.1.0
2021-04
SA#91-E
SP-210181
0039
2
B
Group management support for 5G-VN groups
17.1.0
2021-04
SA#91-E
SP-210181
0040
2
B
Add location criteria to group creation request
17.1.0
2021-04
SA#91-E
SP-210181
0042
1
B
Update to LMS server APIs
17.1.0
2021-04
SA#91-E
SP-210181
0044
B
Enhancement of information flows to add VAL service specific information
17.1.0
2021-04
SA#91-E
SP-210181
0045
1
B
Service identification in location management procedures
17.1.0
2021-06
SA#92-E
SP-210484
0037
3
B
Network Slice Capability Management functional model
17.2.0
2021-06
SA#92-E
SP-210484
0043
3
B
Off-network location management
17.2.0
2021-06
SA#92-E
SP-210485
0047
1
B
Location report timestamp support
17.2.0
2021-06
SA#92-E
SP-210484
0049
2
F
Update to GMS APIs
17.2.0
2021-06
SA#92-E
SP-210484
0051
2
B
SEAL support for CoAP
17.2.0
2021-06
SA#92-E
SP-210484
0052
1
B
Resolve EN for group management
17.2.0
2021-06
SA#92-E
SP-210484
0053
1
B
Coordinated QoS/resource management for network-assisted UE-to-UE communications
17.2.0
2021-06
SA#92-E
SP-210484
0054
1
B
Group list fetch procedure
17.2.0
2021-06
SA#92-E
SP-210484
0055
1
B
Group management enhancements
17.2.0
2021-06
SA#92-E
SP-210485
0056
4
B
SEAL Location Deviation Service
17.2.0
2021-06
SA#92-E
SP-210485
0057
1
B
SEAL Event Monitoring Service
17.2.0
2021-06
SA#92-E
SP-210484
0058
1
B
Requirements for Location management service
17.2.0
2021-06
SA#92-E
SP-210485
0059
B
Supplementary location information to verticals
17.2.0
2021-06
SA#92-E
SP-210485
0060
2
B
add VAL UE Information to configuration management procedure
17.2.0
2021-06
SA#92-E
SP-210483
0062
1
A
Complete resource reservation with PCC procedure
17.2.0
2021-06
SA#92-E
SP-210484
0063
1
F
QoS Monitoring support
17.2.0
2021-06
SA#92-E
SP-210484
0064
2
B
Unified support for TSC/TSN services
17.2.0
2021-06
SA#92-E
SP-210484
0065
2
B
SEAL enable 5G CN capabilities for SEAL groups
17.2.0
2021-06
SA#92-E
SP-210485
0066
2
B
SEAL Location Deviation Service Information flows and APIs
17.2.0
2021-06
SA#92-E
SP-210484
0067
1
B
API and information flow description for Temporary groups
17.2.0
2021-06
SA#92-E
SP-210483
0069
1
A
Fixing the descriptions of IEs in Information flows for location information
17.2.0
2021-09
na
na
0043
3
B
Editorial re-application of CR0043r3 "Off-network location management"
17.3.0
2021-09
SA#93-E
SP-210964
0075
2
C
Improved Event Monitoring Service
17.3.0
2021-09
SA#93-E
SP-210964
0076
2
B
Utilize NEF location service for SEAL LM
17.3.0
2021-09
SA#93-E
SP-210964
0078
5
B
Updates to Location based Group
17.3.0
2021-09
SA#93-E
SP-210964
0079
2
F
Support for TSC services procedures
17.3.0
2021-09
SA#93-E
SP-210964
0080
1
F
Support for TSN services procedures
17.3.0
2021-09
SA#93-E
SP-210964
0081
1
B
Unicast QoS monitoring data retrieval
17.3.0
2021-12
SA#94-E
SP-211525
0082
1
F
Corrections to network slice adaptation
17.4.0
2021-12
SA#94-E
SP-211521
0083
1
F
Group Deletion procedure
17.4.0
2021-12
SA#94-E
SP-211525
0084
1
F
Replace the NSCM with NSCE to align the terminologies
17.4.0
2021-12
SA#94-E
SP-211525
0086
1
F
Removal of PCP from TSC stream discovery
17.4.0
2021-12
SA#94-E
SP-211525
0087
F
Add missing location area monitoring API
17.4.0
2022-03
SA#95-E
SP-220101
0087
F
Clarify the VAL UE ID
17.5.0
2022-03
SA#95-E
SP-220101
0092
1
F
Correct QoS monitoring service
17.5.0
2022-03
SA#95-E
SP-220101
0093
F
Correct TSC stream availability discovery
17.5.0
2022-03
SA#95-E
SP-220102
0091
1
B
Complete location retrieval in an area
18.0.0
2022-06
SA#96
SP-220473
0097
2
A
Minor essential corrections to TS 23.434
18.1.0
2022-06
SA#96
SP-220473
0101
A
Minor corrections on network resource management for 5G TSC
18.1.0
2022-06
SA#96
SP-220473
0103
2
A
QoS monitoring clarification
18.1.0
2022-09
SA#97-E
SP-220925
0104
3
B
SEAL Notification Management service – Functional Model
18.2.0
2022-09
SA#97-E
SP-220925
0105
3
B
SEAL Notification Management service – Information Flows and Procedures
18.2.0
2022-09
SA#97-E
SP-220920
0108
1
A
EN resolution for network slice adaptation request
18.2.0
2022-09
SA#97-E
SP-220925
0110
1
B
Establishing communication with service requirements
18.2.0
2022-09
SA#97-E
SP-220925
0111
2
B
Information flows and procedures to maintain notification channel
18.2.0
2022-09
SA#97-E
SP-220925
0112
1
B
Update_Unicast_QoS_Monitoring_Subscription operation in the SS_NetworkResourceMonitoring API
18.2.0
2022-09
SA#97-E
SP-220920
0115
2
A
Correction on location management information flow
18.2.0
2022-09
SA#97-E
SP-220925
0116
B
Update the scope and reference to support 5MBS
18.2.0
2022-09
SA#97-E
SP-220925
0117
2
B
Update the requirement to support 5MBS
18.2.0
2022-09
SA#97-E
SP-220925
0118
1
B
Update the NRM functional model to support 5MBS
18.2.0
2022-09
SA#97-E
SP-220925
0119
1
B
MBS session creation and MBS session announcement
18.2.0
2022-09
SA#97-E
SP-220925
0120
2
B
Updating MBS resources for group communications
18.2.0
2022-09
SA#97-E
SP-220925
0121
1
B
MBS session deletion
18.2.0
2022-09
SA#97-E
SP-220925
0122
B
Activate or de-activate multicast MBS sessions
18.2.0
2022-09
SA#97-E
SP-220925
0123
B
Group media transmissions over 5G MBS sessions
18.2.0
2022-09
SA#97-E
SP-220925
0124
B
Application level control signalling over 5G MBS sessions
18.2.0
2022-12
SA#98-E
SP-221244
0106
9
B
VAL Server provisioning
18.3.0
2022-12
SA#98-E
SP-221244
0126
2
B
Update the NSCE functional
18.3.0
2022-12
SA#98-E
SP-221244
0127
2
B
Enhance the APIs of the network slice adaptation
18.3.0
2022-12
SA#98-E
SP-221249
0129
B
Update to SEAL architecture to include SEALDD
18.3.0
2022-12
SA#98-E
SP-221244
0130
1
F
Definition of MBS session announcement
18.3.0
2022-12
SA#98-E
SP-221244
0131
1
B
Information flows for MBS procedures
18.3.0
2022-12
SA#98-E
SP-221244
0133
1
B
Updating MBS with dynamic PCC
18.3.0
2022-12
SA#98-E
SP-221244
0134
2
B
NRM coordination for redundant PDU Session establishment
18.3.0
2022-12
SA#98-E
SP-221244
0136
2
B
VAL service area identifier usage
18.3.0
2022-12
SA#98-E
SP-221244
0137
F
Add Cause IE to NSCE information flows
18.3.0
2022-12
SA#98-E
SP-221244
0138
2
F
ADAE functional model in SEAL architecture
18.3.0
2022-12
SA#98-E
SP-221244
0139
2
F
Service continuity between 5G MBS delivery and unicast delivery
18.3.0
2022-12
SA#98-E
SP-221244
0140
3
B
VAL service inter-system switching between 5G and LTE
18.3.0
2022-12
SA#98-E
SP-221244
0141
1
B
VAL service over 5GS supporting EPS interworking
18.3.0
2023-03
SA#99
SP-230283
0142
3
B
Update the on-network functional model and reference points for location management
18.4.0
2023-03
SA#99
SP-230283
0147
2
B
Location profiling for supporting fused location service enablement
18.4.0
2023-03
SA#99
SP-230283
0148
4
B
Add information flow for location reporting configuration update
18.4.0
2023-03
SA#99
SP-230283
0149
2
B
Location service registration and initialization
18.4.0
2023-03
SA#99
SP-230283
0152
1
B
Improved location monitoring procedure
18.4.0
2023-03
SA#99
SP-230293
0153
1
F
Service based interface representation of location management service
18.4.0
2023-03
SA#99
SP-230293
0154
1
F
Service based interface representation of group managment
18.4.0
2023-03
SA#99
SP-230293
0155
1
F
Service based interface representation of network resource management service
18.4.0
2023-03
SA#99
SP-230293
0156
1
F
Update Annex A with details of new SEAL services added
18.4.0
2023-03
SA#99
SP-230293
0158
1
F
Updates to service based interface represeentation of functional model
18.4.0
2023-03
SA#99
SP-230293
0159
2
B
Information flow for VAL server provisioning to the Identity Management Server
18.4.0
2023-03
SA#99
SP-230284
0162
D
Alignment between TS 23.434 and TS 23.436
18.4.0
2023-03
SA#99
SP-230292
0163
1
D
Alignment between TS 23.434 and TS 23.435
18.4.0
2023-03
SA#99
SP-230294
0164
1
B
Update to the SEALDD description
18.4.0
2023-03
SA#99
SP-230293
0168
3
F
Add “supplementary location information source” parameter in related information flows
18.4.0
2023-03
SA#99
SP-230283
0169
2
B
Update the Procedure and information flow to add location QoS
18.4.0
2023-03
SA#99
SP-230293
0170
1
F
Add the information flow for “Location reporting configuration cancel request response”
18.4.0
2023-03
SA#99
SP-230283
0172
2
B
Add third party location management server in existing procedure
18.4.0
2023-03
SA#99
SP-230293
0174
F
Adding missing SEAL services
18.4.0
2023-03
SA#99
SP-230293
0179
1
F
Resolving ENs related to functions enabled over SEAL-E reference point
18.4.0
2023-03
SA#99
SP-230293
0182
1
B
RAT change report via the LMS
18.4.0
2023-03
SA#99
SP-230293
0183
1
F
Clarification on MBS service area in pre-conditions
18.4.0
2023-03
SA#99
SP-230293
0184
1
F
Clarification on UE session join notification
18.4.0
2023-03
SA#99
SP-230293
0185
1
F
Clarification on the unicast deliver stop after multicast MBS delivery
18.4.0
2023-03
SA#99
SP-230293
0186
1
B
Adding MBS listening status report
18.4.0
2023-03
SA#99
SP-230293
0189
1
F
Minor correction on get VAL service
18.4.0
2023-04
Correction of the step 8 style in clause 9.3.14.2
18.4.1
2023-06
SA#100
SP-230712
0143
4
B
Service operations for the SS_VALServiceAreaConfiguration API
18.5.0
2023-06
SA#100
SP-230712
0160
4
B
VAL server provisioning for Key Management Server
18.5.0
2023-06
SA#100
SP-230696
0190
1
C
Update Location service registration request
18.5.0
2023-06
SA#100
SP-230696
0191
1
C
Update Location information request IE
18.5.0
2023-06
SA#100
SP-230696
0192
2
B
Add “location information unsubscribe” and “Monitor location unsubscribe” information flow, procedure and APIs
18.5.0
2023-06
SA#100
SP-230696
0193
1
B
Add “Location service update” procedure and information flow
18.5.0
2023-06
SA#100
SP-230696
0194
1
B
Add “Location service deregistration” procedure and information flow
18.5.0
2023-06
SA#100
SP-230696
0195
1
B
Add “Location service deregistration” procedure and information flow
18.5.0
2023-06
SA#100
SP-23712
0197
1
B
Notification channel expiry handling
18.5.0
2023-06
SA#100
SP-23712
0202
1
F
Create_Group service operation in the SS_GroupManagement API
18.5.0
2023-06
SA#100
SP-23712
0205
2
C
QoS management for network-assisted UE-to-UE communications update
18.5.0
2023-06
SA#100
SP-23704
0206
1
B
Location report considering non-3GPP positioning technology
18.5.0
2023-06
SA#100
SP-23712
0207
F
Minor fixes
18.5.0
2023-06
SA#100
SP-23712
0208
1
F
Abbreviation for Uu
18.5.0
2023-06
SA#100
SP-23712
0209
F
Correction to table 17.3.2.2-1
18.5.0
2023-06
SA#100
SP-23712
0212
2
B
Unified Traffic Pattern and Monitoring management
18.5.0
2023-06
SA#100
SP-23712
0213
2
B
NRM BDT configuration
18.5.0
2023-06
SA#100
SP-23712
0215
2
B
Coordinated application-level direct UE-to-UE communications
18.5.0
2023-06
SA#100
SP-23696
0216
F
Update reference for location access type
18.5.0
2023-06
SA#100
SP-23696
0217
F
Update Annex D
18.5.0
2023-06
SA#100
SP-23696
0218
1
B
Add SEAL-3P reference point
18.5.0
2023-06
SA#100
SP-23696
0219
1
F
Editorial change for Location area monitoring unsubscribe response
18.5.0
2023-06
SA#100
SP-23696
0221
1
F
Clarify non-3GPP access
18.5.0
2023-06
SA#100
SP-23712
0223
2
B
SEAL NRM determines time synchronization activation for TSC stream
18.5.0
2023-09
SA#101
SP-231009
0225
1
F
Correct location monitoring verification
18.6.0
2023-09
SA#101
SP-231009
0226
F
Correct NRM reference point in TSC
18.6.0
2023-09
SA#101
SP-231009
0227
2
F
VAL service area triggering criteria in the SS_LocationReporting API
18.6.0
2023-09
SA#101
SP-231009
0228
2
F
EN resolution for the subscribe-notify service operations for the SS_VALServiceAreaConfiguration API
18.6.0
2023-09
SA#101
SP-231009
0229
F
Add reason IE to Group deletion
18.6.0
2023-09
SA#101
SP-231000
0231
2
F
NRM BDT configuration API
18.6.0
2023-09
SA#101
SP-231000
0232
F
NRM united traffic pattern and monitoring management API
18.6.0
2023-12
SA#102
SP-231565
0233
1
F
Complete functional description of VAL-UDB reference point
18.7.0
2023-12
SA#102
SP-231565
0235
F
Missing Notification Target URI in Location area monitoring subscription operations
18.7.0
2023-12
SA#102
SP-231565
0237
1
F
Update subscription service operation for SS_LocationInfoEvent
18.7.0
2023-12
SA#102
SP-231565
0238
1
F
Update subscription service operation for SS_LocationMonitoring
18.7.0
2023-12
SA#102
SP-231564
0241
A
Notification service operation in the SS_LocationReporting API
18.7.0
2023-12
SA#102
SP-231555
0243
A
Correction of the TSC stream creation request
18.7.0
2023-12
SA#102
SP-231565
0244
2
F
Subscription update service operation for the SS_VALServiceAreaConfiguration API
18.7.0
2023-12
SA#102
SP-231565
0246
2
F
SS_IdmParameterProvisioning API service operations
18.7.0
2023-12
SA#102
SP-231565
0248
1
F
Removal of KMS service provisioning procedure
18.7.0
2023-12
SA#102
SP-231555
0250
2
A
Corrections to Location-based group creation request Information flow
18.7.0
2023-12
SA#102
SP-231564
0253
1
A
Corrections to the Information flows and APIs for Group Management
18.7.0
2023-12
SA#102
SP-231564
0256
1
A
Corrections to the information flows related to CM
18.7.0
2023-12
SA#102
SP-231564
0259
A
Subscription procedure for group membership changes is missing
18.7.0
2023-12
SA#102
SP-231565
0262
1
F
Clarification on Location reporting trigger
18.7.0
2023-12
SA#102
SP-231565
0264
1
F
Correction steps in VAL service area identifier procedure
18.7.0
2023-12
SA#102
SP-231565
0265
2
F
Missing request expiration time in BDT configuration request
18.7.0
2023-12
SA#102
SP-231565
0266
1
A
Group configuration data unsubscribe
18.7.0
2023-12
SA#102
SP-231565
0267
1
A
Group configuration data subscription update
18.7.0
2023-12
SA#102
SP-231565
0270
1
F
Correction duplicated numbering clause 14.3.2.57
18.7.0
2023-12
SA#102
SP-231565
0271
1
F
Adding the information flow and AP for NRM reliable transmission
18.7.0
2023-12
SA#102
SP-231565
0272
F
Corrections for BDT configuration
18.7.0
2023-12
SA#102
SP-231565
0273
1
F
Corrections for BDT configuration information flows
18.7.0
2023-12
SA#102
SP-231565
0274
1
F
Correction to add missing get operation for BDT configuration
18.7.0
2023-12
SA#102
SP-231565
0275
1
F
Correction to add missing update operation for BDT configuration
18.7.0
2023-12
SA#102
SP-231565
0276
2
F
Correction to add missing delete operation for BDT configuration
18.7.0
2023-12
SA#102
SP-231565
0277
1
F
Correction to add missing API operations for BDT configuration
18.7.0
2023-12
SA#102
SP-231572
0245
4
B
NRM device triggering
19.0.0
2023-12
SA#102
SP-231572
0269
1
B
RRC inactive support
19.0.0
2024-03
SA#103
SP-240298
0285
1
A
UE identifiers correction in the SS_LocationAreaInfoRetrieval API
19.1.0
2024-03
SA#103
SP-240318
0286
1
B
Termination indication in the SS_NetworkResourceMonitoring API
19.1.0
2024-03
SA#103
SP-240298
0291
A
Correct IE presence condition
19.1.0
2024-03
SA#103
SP-240316
0292
1
B
NRM Network resource adaptation enhancement for BDT
19.1.0
2024-06
SA#104
SP-240773
0287
3
B
Monitoring profiles in the SS_NetworkResourceMonitoring API
19.2.0
2024-06
SA#104
SP-240750
0296
A
Solve EN in location info request
19.2.0
2024-06
SA#104
SP-240762
0298
A
Correct location triggering criteria in update request
19.2.0
2024-06
SA#104
SP-240762
0300
A
Solve EN in NM related to CAPIF
19.2.0
2024-06
SA#104
SP-240762
0302
A
Solve EN in SEAL clause 14.3.12
19.2.0
2024-09
SA#105
SP-241229
0261
2
F
Clarification on the callback URL usage
19.3.0
2024-09
SA#105
SP-241220
0304
1
B
Support for adaptive location configuration and reporting
19.3.0
2024-09
SA#105
SP-241229
0305
1
F
Alignment, correction and clarification of the location-based group creation procedure
19.3.0
2024-09
SA#105
SP-241220
0306
2
B
Add Geofencing subscription/unsubscribe procedure
19.3.0
2024-09
SA#105
SP-241220
0307
2
B
Add procedure of Geofencing UE(s) Information request/response
19.3.0
2024-09
SA#105
SP-241220
0309
3
B
Add procedure of querying for history location
19.3.0
2024-09
SA#105
SP-241220
0310
2
B
LMS reuse the stored UE location information
19.3.0
2024-09
SA#105
SP-241220
0311
2
B
Exposure of value-added UE location information
19.3.0
2024-09
SA#105
SP-241212
0312
1
B
General description of application enablement of AIML services
19.3.0
2024-09
SA#105
SP-241220
0313
3
B
Dynamic geofencing
19.3.0
2024-09
SA#105
SP-241220
0314
3
B
Target UE location provided by surrounding UEs
19.3.0
2024-09
SA#105
SP-241229
0315
D
Editorial change for location information subscription update
19.3.0
2024-09
SA#105
SP-241229
0316
F
Update clause 14.3.9.2.1
19.3.0
2024-12
SA#106
SP-241710
0318
1
A
Remove reference for 23.545 in SEAL
19.4.0
2024-12
SA#106
SP-241710
0320
2
A
Solve EN in SEAL clause 9.5.1
19.4.0
2024-12
SA#106
SP-241710
0322
2
A
TS 23.434 Rel-19 - Handling Editors Notes
19.4.0
2024-12
SA#106
SP-241720
0323
1
D
Editorial changes for Geofencing subscription/unsubscribe procedure
19.4.0
2024-12
SA#106
SP-241720
0324
1
B
Add new architectural requirements for SEAL LMS
19.4.0
2024-12
SA#106
SP-241720
0325
2
B
APIs for location history request procedure
19.4.0
2024-12
SA#106
SP-241720
0326
1
B
Add valued location services functions for SEAL LMS
19.4.0
2024-12
SA#106
SP-241720
0327
F
Remove the overlap information
19.4.0
2024-12
SA#106
SP-241720
0328
2
B
LMS reuse the stored UE location information considering the location validity
19.4.0
2024-12
SA#106
SP-241720
0329
4
B
Location services for multiple UEs that sharing the same location
19.4.0
2024-12
SA#106
SP-241717
0330
5
B
Satellite access with discontinuous coverage
19.4.0
2024-12
SA#106
SP-241717
0331
1
B
Add SEAL functional requirements for satellite connectivity
19.4.0
2024-12
SA#106
SP-241717
0332
5
B
Support the satellite S&F operation
19.4.0
2024-12
SA#106
SP-241727
0333
2
B
SEAL updates for metaverser services
19.4.0
2024-12
SA#106
SP-241720
0335
3
B
Enhancements to location reporting procedure
19.4.0
2024-12
SA#106
SP-241733
0336
5
B
Application QoS coordination for Mobile Metaverse Services
19.4.0
2024-12
SA#106
SP-241720
0337
1
B
Support for sidelink positioning management
19.4.0
2024-12
SA#106
SP-241720
0338
4
B
Add procedure for exposing Sidelink ranging information
19.4.0
2024-12
SA#106
SP-241729
0339
B
Correction of misalignments of Background Data Transfer information
19.4.0
2024-12
SA#106
SP-241720
0340
3
B
Resolve the 2nd EN in 9.3.11.2
19.4.0
2024-12
SA#106
SP-241720
0341
4
B
Resolve the 1st EN in 9.3.11.2
19.4.0
2024-12
SA#106
SP-241720
0342
1
B
Verify UE location
19.4.0
2024-12
SA#106
SP-241720
0343
2
F
EN resolution on Geofencing monitoring events
19.4.0
2024-12
SA#106
SP-241720
0344
1
B
Add the velocity in location reporting related procedures
19.4.0
2024-12
SA#106
SP-241720
0345
1
B
Keep consistent with the event triggers for reusing the stored UE location
19.4.0
2024-12
SA#106
SP-241720
0347
1
B
Resolve the EN for using SL/Ranging positioning method
19.4.0
2024-12
SA#106
SP-241710
0349
2
A
Void MBMS bearer event notification procedure in clause 14.3.4.8
19.4.0
2024-12
SA#106
SP-241710
0351
1
A
Resolve the 2nd EN in clause 15.2
19.4.0
2024-12
SA#106
SP-241710
0353
1
A
Resolve the EN in clause 14.3.4.5.2
19.4.0
2024-12
SA#106
SP-241710
0354
3
A
MBS service area handling at NRM
19.4.0
2024-12
SA#106
SP-241728
0355
1
F
Upcase correction of location management client and location management server
19.4.0
2024-12
SA#106
SP-241727
0357
B
Digital asset service description
19.4.0
2025-01
Due to conflict between the digital asset service proposal in CR0333R2 and CR0357, only the latter was implemented.
19.4.1
2025-01
Re-application of CR0332R5 “Support the satellite S&F operation”
19.4.2
2025-03
SA#107
SP-250205
0363
2
B
Add the business relationship for SEAL deployment with satellite connectivity
19.5.0
2025-03
SA#107
SP-250216
0364
1
F
Handling of Editors Notes in TS 23.434
19.5.0
2025-03
SA#107
SP-250201
0366
1
A
Resolve the EN about the security and privacy aspects for location management
19.5.0
2025-03
SA#107
SP-250210
0367
1
F
Resolve the EN for handling the “loss of connectivity” in LM server
19.5.0
2025-03
SA#107
SP-250210
0368
1
F
Uniform the IE description for the velocity
19.5.0
2025-03
SA#107
SP-250210
0371
1
F
Correction on reference UE usage
19.5.0
2025-06
SA#108
SP-250592
0361
1
C
Addition of response elements in the 5GSAT procedure in TS23.434
19.6.0
2025-06
SA#108
SP-250592
0362
2
F
Correction of the description of the procedures for UE requesting satellite coverage availability information in TS 23.434
19.6.0
2025-06
SA#108
SP-250592
0369
2
B
Add the APIs for VAL server obtaining the SCAI
19.6.0
2025-06
SA#108
SP-250618
0373
2
F
Consolidation of Reserve Network Resource and Request Unicast Resource
19.6.0
2025-06
SA#108
SP-250615
0375
1
A
Group management fix
19.6.0
2025-06
SA#108
SP-250590
0377
A
Correction in Configure VAL service area identifier procedure
19.6.0
2025-06
SA#108
SP-250601
0378
F
Correction to the reference and clause numbering of location management procedure
19.6.0
2025-06
SA#108
SP-250601
0379
1
F
Update the information flow of location reuse procedure
19.6.0
2025-06
SA#108
SP-250601
0380
1
F
Update the procedure of verify UE locations and APIs
19.6.0
2025-06
SA#108
SP-250592
0381
1
F
Update the procedure of SCAI provisioning
19.6.0
2025-06
SA#108
SP-250592
0382
3
F
Correction to NRM enabled S&F transmission
19.6.0
2025-06
SA#108
SP-250601
0383
2
B
Resolve limitation introduced in a NOTE related to reference UE selection by the LMS
19.6.0
2025-06
SA#108
SP-250592
0384
1
F
Update satellite coverage availability information by also considering UE's mobility
19.6.0
2025-06
SA#108
SP-250621
0385
5
B
Update satellite coverage availability information by also considering UE's mobility
19.6.0
2025-06
SA#108
SP-250601
0387
1
F
Correction to 9.4.1 SEAL APIs for location management
19.6.0
2025-06
SA#108
SP-250592
0388
F
Clarification on Maximum S&F data retention IE
19.6.0
2025-06
SA#108
SP-250601
0389
1
F
Correction related to cell identifier information in the Confirm location request and response messages
19.6.0
2025-06
SA#108
SP-250601
0390
2
F
Essential corrections to various eLSAPP procedures
19.6.0
2025-06
SA#108
SP-250601
0392
2
F
Correct the procedure and IEs for SL positioning management service
19.6.0
2025-06
SA#108
SP-250601
0393
1
F
Correct the procedure and IEs for Short-Range based positioning information
19.6.0
2025-06
SA#108
SP-250592
0394
2
F
Correct the reference of Satellite coverage availability information
19.6.0
2025-06
SA#108
SP-250592
0395
1
F
Correct the S&F events to align with SA2 exposure
19.6.0
2025-06
SA#108
SP-250601
0396
F
Corrections of clause 9.3.11.2
19.6.0
2025-09
SA#109
SP-251050
0399
F
Correct the term of Satellite coverage availability information
19.7.0
2025-09
SA#109
SP-251055
0400
F
Clarification on the relative location in clause 9.3.11.2
19.7.0
2026-01
SA#110
SP-251475
0404
F
Corrections to SS_LocationReporting Service
19.8.0
2026-01
SA#110
SP-251489
0407
F
SEAL references
19.8.0
2026-01
SA#110
SP-251494
0401
1
B
CR for 23.434 for UE ID usage correction
20.0.0
2026-01
SA#110
SP-251490
0402
4
B
API consumer clarification
20.0.0
2026-01
SA#110
SP-251490
0403
B
Include power saving configuration within the NRM services for IoT devices
20.0.0
2026-01
SA#110
SP-251490
0408
3
B
The deployment options of SEAL client
20.0.0
2026-01
SA#110
SP-251490
0409
1
B
The business relationship involving SEAL client provider
20.0.0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.