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 ope... |
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... |
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 servi... |
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
Grou... |
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. T... |
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 provid... |
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 ... |
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 ... |
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... |
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 notifica... |
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 notificat... |
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 ... |
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
Notific... |
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 ... |
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... |
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 manageme... |
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 ... |
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 l... |
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: Rec... |
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... |
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 notificatio... |
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, ... |
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... |
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 ... |
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... |
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... |
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... |
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.
... |
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
... |
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 o... |
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... |
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... |
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 c... |
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 V... |
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 ... |
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 unsubsc... |
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
I... |
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 c... |
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 V... |
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 serv... |
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
U... |
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 integratio... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.