hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
17.3.2 Information flows for notification management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
18 Data Delivery
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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]
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
19 Application Data Analytics Enablement
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
20 AIML Enablement
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21 SEAL services over Satellite Access
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.1 General
|
This clause provides clarifications on the procedures and information flows for enabling SEAL services using satellite access.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.2 Satellite coverage availability information configuration
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.2.1 General
|
The following clauses describe the satellite coverage availability information provisioning procedure.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.2.2 Procedures
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.2.2.1 Procedures of the satellite coverage availability information provisioning
|
The procedure for VAL UE obtaining the satellite coverage availability information 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].
- The configuration management server may interact with the SEAL location management server to obtain the VAL UE’s information (e.g., location).
Figure 21.2.2.1-1: The satellite coverage availability information provisioning
1. The configuration management server obtains the satellite coverage availability information locally or from the satellite service provider, and in order to provide accurate information to the UE, the VAL UE’s information (e.g. location data) may also be considered. 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 example of satellite coverage availability information can refer to the Annex Q of 3GPP TS 23.501 [10].
2. The configuration management server sends the satellite coverage availability information configuration request to the configuration management client to indicate whether the 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.2.2.2 Procedures of UE requesting the satellite coverage availability information(SCAI)
|
The procedure for VAL UE/VAL server requesting and obtaining the satellite coverage availability information from the application enabler is illustrated in figure 21.2.2.2-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] and has not received the satellite coverage availability information from the network yet.
- The configuration management server has obtained the satellite coverage availability information as described in clause 21.2.2.1.
Figure 21.2.2.2.1-1: VAL UE requests the satellite coverage availability information
1. The consumer (Configuration management client, VAL server) sends Get satellite coverage availability information (SCAI) request to the configuration management server to require satellite coverage availability information 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 SCAI is available or not. If it’s not available, the configuration management server obtains the SCAI 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 satellite coverage availability information to the consumer (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 satellite coverage availability information.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.2.3 Information flows
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.2.3.1 Satellite coverage availability information 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 satellite coverage availability information.
Table 21.2.3.1-1: Satellite coverage availability information 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 coverage availability information(NOTE)
M
Indicates when the satellite coverage is available for a particular location and time.
NOTE: The example of satellite coverage availability information refers to the Annex Q of 3GPP TS 23.501 [10].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.2.3.2 Satellite coverage availability information 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 satellite coverage availability information configuration request.
Table 21.2.3.2-1: Satellite coverage availability information configuration response
Information element
Status
Description
Identity
M
Identity of the requesting VAL user or VAL UE.
Result
M
Indicates the request result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.2.3.3 Get satellite coverage availability information 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 satellite coverage availability information.
Table 21.2.3.3-1: Get satellite coverage availability information 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.2.3.4 Get satellite coverage availability information 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 satellite coverage availability information.
Table 21.2.3.4-1: Get satellite coverage availability information 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.
Satellite coverage availability information(NOTE)
M
Indicates when the satellite coverage is available for a particular location and time.
NOTE: The example of satellite coverage availability information refers to the Annex Q of 3GPP TS 23.501 [10].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.3 Satellite S&F events information
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.3.2 Procedures
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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 in S&F Mode, re-transmit the pending DL data when the feeder link is available, adjust the DL traffic volume according to the DL estimated 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 2: 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.3.3 Information flows
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
> The DL S&F estimated 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.
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 of 3GPP TS 23.682 [13].
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
O
Indicates the maximum data retention for the VAL UE per service on the application layer.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
O
Indicates the maximum data retention per UE per service on the application layer when the UE is using the satellite S&F operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.3.4 APIs for Satellite S&F events information
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
21.3.4.2 SS_SatelliteS&FInfoEvent API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
22 Spatial anchors (SAn) service
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
23 Spatial map (SM) service
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
24 Digital Asset
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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): 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
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
1 Scope
|
The present document specifies the procedures and information flows necessary for Network Slice Capability Exposure for Application Layer Enablement on the basis of SEAL.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[3] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[4] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[5] GSMA NG.116 - Generic Network Slice Template.
[6] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
[7] 3GPP TS 28.532: "Management and orchestration; Generic management services".
[8] 3GPP TS 28.531: "Management and orchestration; Provisioning".
[9] 3GPP TS 28.537: "Management and orchestration; Management capabilities".
[10] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[11] 3GPP TS 28.535: "Management and orchestration; Management services for communication service assurance; Requirements".
[12] 3GPP TS 23.502: "Procedures for the 5G System (5GS)".
[13] 3GPP TS 29.536: "5G System; Network Slice Admission Control Service; Stage 3".
[14] 3GPP TS 33.501: "Security architecture and procedures for 5G System"
[15] 3GPP TS 28.530: "Management and orchestration; Concepts, use cases and requirements"
[16] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[17] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[18] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[19] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[20] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[21] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics".[22] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
[22] 3GPP TS 33.434: "Service Enabler Architecture Layer (SEAL); Security aspects for Verticals".
[23] 3GPP TS 28.545: "Management and orchestration; Fault Supervision (FS) "
[24] 3GPP TS 32.111-1: "Management and orchestration; Fault management, Part 1: 3G fault management requirements".
[25] 3GPP TS 28.533: "Management and orchestration; Architecture framework".
[26] 3GPP TS 23.436: "Procedures for Application Data Analytics Enablement Service"
[27] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction ".
[28] 3GPP TS 28.202: "Charging management; Network slice management charging in the 5G System (5GS); Stage 2"。
…
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
3 Definitions of terms, symbols and abbreviations
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
3.1 Terms
|
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
VAL server policy: Network slice management Policy which can be seen as application function policy from VAL Provider/ slice customer/ASP, abstracted based on the slice usage pattern of application, consisting of trigger event and expected action. When provided to NSCE server, the NSCE server will trigger the expected action based on the policy.
MNO policy: The network slice management policy between the VAL and MNO pertaining to a specific service and slice, including ranges of network slice capabilities which can be adapted, i.e. Network slice Service level agreement.
NSCE service provider policy (NSPP): The network slice capability enablement service policy between the VAL and NSCE service provider pertaining to a specific service and slice, including ranges of network slice capability enablement service which can be adapted, i.e. NSCE service level agreement.
Policy harmonization: The NSCE service that harmonizing the VAL server policy parameter, to make sure the VAL server policy is compatible with the policies of the MNO and NSCE service provider policy for the same service or slice.
Requirement alignment: The NSCE service that aligning the network slice performance and the VAL service requirement in the request.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
ASP Application Service Provider
Auto-NS-LCM Automatic Application Layer Network Slice Lifecycle Management
EDN Edge Data Network
EGMF Exposure Governance Management Function
GST Generic Network Slice Template
KPI Key Performance Indicator
KQI Key Quality Indicator
MnS Management Service
MNO Mobile Network Operator
NEF Network Exposure Function
NEST Network Slice Template
NOP Network Operator
NSCE Network Slice Capability Enablement
NSaaS Network Slice as a Service
NSI Network Slice Instance
NSSI Network Slice Subnet Instance
NWDAF Network Data Analytics Function
NSACF Network Slice Admission Control Function
NSC Network Slice consumer
NSP Network Slice Provider
NSMF Network Slice Management Function
OAM Operation, administration and maintenance
QoE Quality of Experience
S-NSSAI Single Network Slice Selection Assistance Information
SLA Service Level agreement
VAL Vertical Application Layer
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4 Overview
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.1 Registration
|
This functionality enables the VAL server to become a recognized user of CAPIF. VAL server registration procedures are specified in clause 9.2.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.2 Slice API configuration and translation
|
This functionality is provided to the vertical application specific layer and configures the exposure of APIs in a slice-tailored manner. It is assumed that the VAL server is not initially aware of the all the API exposure capabilities and information which will be needed for the given slice based on the SLA, and NSCE plays a vital role in configuring and translating the slice API based on the per slice requirements to service APIs. Slice API configuration and translation procedures are specified in clause 9.3.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.3 Application layer network slice lifecycle management
|
Application layer network slice lifecycle management is provided to the VAL to better meet consumer's requirement without having to interact with 5GS frequently, based on network slice status collected from 5GS and QoE collected from application layer. Application layer network slice lifecycle management procedures are specified in clause 9.4.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.4 Network slice optimization based on VAL server policy
|
Network slice optimization based on VAL server policy optimizes the network slice for the vertical applications by triggering the network slice modification exposed by EGMF defined in SA5. Network slice optimization based on VAL server policy procedures are specified in clause 9.5.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.5 Discovery of management service exposure
|
This network slice capability enablement feature supports the initial discovery of MnS for a given slice based on VAL server request, and the discovery of new/modified MnS with the required exposure (for example the permissions of the VAL server over the target MnS, e.g. read, write operations). This feature consists of two procedures, which are specified in clause 9.6:
- Discovery of management service capabilities and related permissions (e.g. permitted CRUD operations) based on VAL server request;
- Discovery and exposure of new or modified management service capabilities based on changes at OAM.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.6 Network slice performance and analytics monitoring
|
This functionality is provided to the VAL to get end to end network slice related performance and analytic monitoring. The NSCE server identifies which data are needed, collects the data from different data sources (e.g., the OAM system, the 5GC Network, etc.), performs data processing and abstraction, exposes the processed data to VAL servers. Network slice performance and analytics monitoring procedures are specified in clause 9.7.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.7 Information collection from NSCE server(s)
|
The network slice status collected by the NSCE server could be exposed to other NSCE server(s) if some agreement has been made. Information collection from NSCE server(s) procedures are specified in clause 9.8.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.8 Predictive slice modification in edge based NSCE deployments
|
This feature addresses scenarios where the NSCE server is deployed at the edge and the migration to different Data Network will require that the ongoing slice is supported at the target area to ensure meeting the application session requirements. The slice parameters monitoring at the target area (e.g. for per NSI/NSSI resource situation) need to be known at the server NSCE server to allow for pro-active slice (or slice subnet) modification trigger to avoid degradation of the application service performance. Predictive slice modification procedures are specified in clause 9.9.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.9 Multiple slices coordinated resource optimization
|
This functionality is provided to the VAL to monitor the slice usage status of multiple slices (PNI-NPN slice(s) and its private slice in the PLMN) of the PNI-NPN owner in a combined manner. It makes resource adjustment between different slices in one PLMN to realize optimized and efficient resource usage among multiple slices sharing common network resources. Coordinated PLMN and PNI-NPN slice resource optimization procedures are specified in clause 9.10.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.10 Network slice adaptation for VAL application
|
This functionality is provided to the VAL to adapt the network slice for the VAL application. Such adaptation assumes that the UE is subscribed to more than one slice and is done via providing a guidance to update the URSP rules at the 5GS. The network slice adaptation request can be triggered by VAL server or VAL UE. Network slice adaptation for VAL application procedures are specified in clause 9.11.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.11 Slice related communication service lifecycle management
|
This functionality is provided to the VAL server to make slice related communication service lifecycle management. The NSCE server can acquire the application services related requirements for a specific VAL service from the vertical industry perspective, evaluate these requirements and then determines the network slice by pre-configured industry mapping relations or by KQI-KPI translation algorithms. After the network slice requirements are determined, the NSCE server allocates proper network slice resources to support the application services. Slice related communication service lifecycle management exposure procedures are specified in clause 9.12.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.12 Predictive slice modification in Inter-PLMN based slice service continuity
|
This functionality is provided to the VAL to make predictive slice modification where NSCE service provider provides its services when connected to two PLMNs and has SLA with them. The NSCE server checks with 5GS (OAM, 5GC) whether the serving slice is available and can offer the same performance at the target PLMN and make slice modification decision if needed. Predictive slice modification in Inter-PLMN based slice service continuity procedures are specified in clause 9.13.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.13 Network slice diagnostics
|
Network slice diagnostics provides possibility for the vertical/ASP using VAL server to receive information about the specific event(s) related to service experience. The vertical/ASP using the VAL server has estimated bad QoE for a mobile user or service – either reported from a mobile user or service or detected by application, can initiate a check with NSCE. The NSCE server can provide Network slice diagnostics details related to the identified event as specified in clause 9.14.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.14 Network slice fault management capability exposure
|
Network slice fault management capability exposure gathers data from different sources (e.g., OAM, VAL server, NSCE client) and provides fault data that characterize the quality of the network connections and services to ensure a quick reaction to identify network connectivity, performance related problems. The Network slice fault management capability exposure is specified in clause 9.15.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.15 Slice requirements verification and alignment capability exposure
|
Slice requirements verification and alignment capability exposure provides the capability of comparing the QoS achievement status together with the OAM QoS data versus real customer QoS data (e.g., Mean Opinion Score) collected from VAL client by checking whether the existing QoS/Slice related data is able to satisfy the VAL clients. Periodically alignment notifications are sent to VAL server for the slice requirements alignment. The Slice requirements verification and alignment capability exposure is specified in clause 9.16.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.16 Network Slice Information delivery
|
The Network Slice information delivery sends the Network Slice information to VAL server and NSCE client. With that information, the VAL server is able to manage the network slice for their service such as preparation, creation, activation and termination (tear-down) of network slice. The Network Slice Information delivery is specified in clause 9.17.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
4.17 Network Slice Allocation
|
The NSCE server performs the Network Slice allocation operation on behalf of the VAL server if non-trusted 3rd party application (i.e., VAL server) cannot access to the 5GS management system directly. The specific service is specified in clause 9.18.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
5 Business models and relationships for NSCE
|
NSCE layer provides value added services to VAL customers, based on consuming 5GS services related to slicing (from OAM, 5GC) and based on interacting with the VAL UE side. The variety of services and the deployment aspects depend on the different assumptions for the slice owner / provider, the slice customer and the SEAL service provider. With respect to NSCE, the NSCE server belongs to the SEAL provider (as stated in TS 23.434 [2] clause 5) who can be either the MNO itself, or the vertical customer (e.g. factory owner, automaker X) or the edge/cloud provider (e.g. hyperscaler) who provides such platform services related to slice capability exposure to the vertical customer on top of the MNO. Thus, NSCE can play different roles based on the business models. For example, NSCE server can be:
- deployed by NOP / MNO.
- deployed by an Edge / Cloud Provider. In this case, it is assumed that the NSCE server is acting as an authorized AF/AS.
- deployed by a vertical industry, which can be the end slice customer.
From business perspective, the following business model applies. In Figure 5-1, the different interactions among all the involved entities are provided. More specifically, in this model the end user is the consumer of the applications provided by the vertical/ASP and can have app-level service agreement with vertical/ASP(s).
The end user/UE also has a PLMN subscription arrangement with the MNO. The UE used by the end user is allowed to be registered on the MNO's network. MNO (via OAM) can have a slice SLA with the vertical / ASP, which is optional when vertical customer is the NSC. In addition, due to the involvement of a NSCE service provider, additional agreements can be possible between the NSCE server and VAL/ASP layer and the NOP/MNO(s):
- the enablement service agreement between VAL/ASP layer and the NSCE service provider include the agreement on the value-added services, which in case on NSaaS these are services related to the consumed slice from NOP. So, the end customer (VAL) subscribes to NSCE server for receiving additional services for optimizing the slice utilization. In case that the NSCE server is a NSP towards VAL customer, then such agreement can relate to slice SLA (for the slice provided by the NSCE server). When the NSCE server is part of the vertical, the service agreement between VAL/ASP layer and the NSCE service provider is internal to a single organization.
- the service agreement between MNO and NSCE service provider is for consuming 5GS services (and being also authorized to provide additional services on top). Such agreement could be also a slice SLA for the scenarios when NSCE server is the NSC of the MNO (in NSaaS model).
Figure 5-1: Business relationships
In case of shared RAN between operators, one NSCE service provider (slice service provider) can use NSCE to offer slice services using resources of these operators to end customer (VAL) using the shared RAN via one or both operators.
In case of national roaming between operators, one NSCE service provider (slice service provider) can use NSCE to offer slice services using resources of these operators to end customer (VAL).
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
6 Architectural requirements
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
6.1 General Description
|
The following clauses specify the requirements for network slice capability enablement services for application layers.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
6.2 General requirements
|
[AR-6.2-1] The NSCE architecture shall support the NSCE server to communicate with the VAL server with one or more applications.
[AR-6.2-2] The NSCE architecture shall support the NSCE server to communicate with one or more VAL servers.
[AR-6.2-3] The NSCE architecture shall support the NSCE server to interact with 3GPP network management system(s) to consume network slice management services provided by MNO(s). The network management system(s) can belong to the same PLMN or different PLMNs on which the NSCE service provider offers its services.
[AR-6.2-4] The APIs interactions between the vertical application server(s) and NSCE server(s) shall conform to CAPIF as specified in 3GPP TS 23.222 [3].
[AR-6.2-5] The NSCE architecture shall support the NSCE server to communicate with one or more other NSCE server(s).
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
6.3 Network slice Lifecycle management requirements
|
[AR-6.3-1] The NSCE architecture shall enable lifecycle management capability exposure of network slice by authorized VAL server.
[AR-6.3-2] The NSCE architecture shall enable lifecycle management capability exposure of network slice communication service to authorized VAL server.
[AR-6.3-3] The NSCE architecture shall support the interactions with 3GPP network management system to consume network slice lifecycle management service provided by MNO.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
6.4 Performance data retrieval requirement
|
[AR-6.4-1] The NSCE architecture shall support the end-to-end network slice performance and analytics monitoring capability exposure to authorized VAL server.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
6.5 Network slice adaption requirement
|
[AR-6.5-1] The NSCE architecture shall support the network slice adaption capability exposure to authorized VAL server.
[AR-6.5-2] The NSCE architecture shall support the network slice adaption capability exposure to authorized NSCE client.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
6.6 Network slice configuration and translation requirement
|
[AR-6.6-1] The NSCE architecture shall support the network slice configuration capability exposure to authorized VAL server.
[AR-6.6-2] The NSCE architecture shall support the network slice translation capability to enable the translation of slice API invocated by VAL server.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
6.7 Multiple slices combined management requirement
|
[AR-6.7-1] The NSCE architecture shall support the interactions with OAM or 5GC of 3GPP PLMN to provide multiple slices combined management service of that PLMN.
[AR-6.7-2] The NSCE architecture shall provide multiple slices combined performance monitoring service of the PLMN and its PNI-NPNs to authorized VAL server.
[AR-6.7-3] The NSCE architecture shall provide multiple slices coordinated resource optimization service between the PLMN and its PNI-NPNs to authorized VAL server.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
6.8 Security requirements
|
[AR-6.8-1] The NSCE architecture shall provide mechanisms to authorize the usage of network slicing related services by the VAL servers and NSCE clients, conform to CAPIF as specified in 3GPP TS 23.222 [3].
[AR-6.8-2] The NSCE architecture shall support mutual authentication and authorization check between clients and servers, servers and servers that interact, conform to CAPIF as specified in 3GPP TS 23.222 [3].
NOTE: The authentication and authorization aspects related to VAL servers and NSCE enablers are out scope of this study and to be addressed by SA3, in TS 33.434[21].
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
7 Application architecture for NSCE
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
7.1 General
|
The architecture for the network slice capability enablement is based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [2]. It is organized into functional entities to describe a functional architecture which addresses the support for network slice capability enablement aspects for vertical applications. Since the slicing is a feature which considers the Uu interfaces, only the on-network functional model is specified in this clause.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
7.2 Architecture description
|
Figure 7.2-1 depicts the network slice capability enablement architecture in the non-roaming case, using the reference point representation showing how various entities interact with each other.
Figure 7.2-1: Architecture for network slice capability enablement – reference points representation
The network slice capability enablement client communicates with the network slice capability enablement server over the NSCE-UU reference point. The network slice capability enablement client provides the support for network slice capability enablement functions to the VAL client(s) over NSCE-C reference point. The VAL server(s) communicates with the network slice capability enablement server over the NSCE-S reference point. It is assumed that the network slice capability enablement server is deployed at the 5G system domain. The network slice capability enablement server, acting as AF, may communicate with the 5G Core Network functions via NEF (N33) reference point (for interactions with PCF, NSACF, etc.). The network slice capability enablement server may interact with OAM system over NSCE-OAM reference point, as consumer in both NSaaS and NoP model defined in the clause 4.1.6 and clause 4.1.7 of 3GPP TS 28.530 [15] (for Network Slice Provisioning capabilities, Performance Assurance, Fault Supervision etc.).
NOTE: OAM interfaces and/or network slice information can be exposed to an authorized (trusted) third-party (NSCE) only after a contract has been signed between the MNO and this third-party. Whether and how CAPIF/EGMF can be used to expose management services (MnS) is up to SA5 decision.
Figure 7.2-2 illustrates the architecture for interconnection between NSCE servers.
Figure 7.2-2: Interconnection between NSCE servers
The NSCE server could interact with another NSCE server over NSCE-E reference point.
Figure 7.2-3 illustrates the architecture for inter-service communication between NSCE servers and other SEAL server.
Figure 7.2-3: Inter-service communication between NSCE server and other SEAL server
The NSCE server interacts with another SEAL server for inter-service communication over SEAL-X reference point.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
7.3 Functional entities description
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
7.3.1 General
|
The functional entities for network slice capability enablement SEAL service are described in the following subclauses.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
7.3.2 Network slice capability enablement server
|
The network slice capability enablement server functional entity provides the application layer enablement of the network slicing aspects to support the VAL applications. The network slice capability enablement server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [3].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.