hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3.4 SEALDD XR transmission connection establishment response
|
Table 9.12.3.4-1 describes the information flow from the SEALDD server to the SEALDD client for responding to the XR transmission connection establishment.
Table 9.12.3.4-1: SEALDD XR transmission connection establishment response
Information element
Status
Description
Result
M
Indicates the success or failure of establishing the SEALDD connection.
Multi-modal SEALDD flow ID
M
Identity of the Multi-modal SEALDD-UU flow associated with the multi-modal XR connection.
SEALDD traffic descriptors
O
SEALDD traffic descriptors for multiple flows (e.g. address(s), port(s), transport layer protocol) of the SEALDD server side used to establish SEALDD multi-modal connection.
Protocol description
O
The protocol description of VAL traffic. It includes header extension information (e.g. RTP extension with PDU set), packetization indication, payload type and format (e.g. H.264/RTP, H.265/RTP, H.264, H.265).
Header extension information is only applicable when payload indicates RTP.
Cause
O
(See NOTE)
Indicates the reason for the failure
NOTE: The IE is only present if the Result is failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3.5 SEALDD-UUc connection request
|
Table 9.12.3.5-1 describes the information flow from the SEALDD client on 3GPP UE to SEALDD client on tethered UE for SEALDD-UUc connection request.
Table 9.12.3.5-1: SEALDD-UUc connection request
Information element
Status
Description
Requestor’s ID or PIN ID
M
Identity of the requestor SEALDD client on 3GPP UE, or the PIN ID of the requestor.
SEALDD-UUc data transmission connection information
M
SEALDD-UUc data transmission connection information(e.g., address/port allocated)
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3.6 SEALDD-UUc connection response
|
Table 9.12.3.6-1 describes the information flow from the SEALDD client on 3GPP UE to SEALDD client on tethered UE for SEALDD-UUc connection response.
Table 9.12.3.6-1: SEALDD-UUc connection response
Information element
Status
Description
Result
M
Success or failure.
SEALDD-UUc data transmission connection information
O
SEALDD-UUc data transmission connection information(e.g., address/port allocated)
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3.7 Inform XR transmission request
|
Table 9.12.3.7-1 describes the information flow from the SEALDD client to the SEALDD server to inform XR transmission connection status between two UEs.
Table 9.12.3.7-1: Inform XR transmission request
Information element
Status
Description
Requestor ID
M
Identity of the requestor (i.e. SEALDD client).
VAL service ID
O
Identity of the VAL service
Identities
M
Identifier of UEs or VAL users involved in the UE-to-UE direct communication.
Status
M
Identifies the UE-to-UE direct communication status (e.g. establishment, release).
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3.8 Inform XR transmission response
|
Table 9.12.3.8-1 describes the information flow from the SEALDD server to the SEALDD client to acknowledge XR transmission connection status between two UEs.
Table 9.12.3.8-1: Inform XR transmission response
Information element
Status
Description
Result
M
Result of the operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3.9 Trigger XR transmission request
|
Table 9.12.3.9-1 describes the information flow from the SEALDD server to the SEALDD client to trigger XR transmission connection operation between two UEs.
Table 9.12.3.9-1: Trigger XR transmission request
Information element
Status
Description
Requestor ID
M
Identity of the requestor (i.e. SEALDD server).
VAL service ID
O
Identity of the VAL service
Identities
M
Identifier of UEs or VAL users involved in the UE-to-UE direct communication.
Operation
M
Identifies the action for UE-to-UE direct communication (e.g. establishment, release).
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.3.10 Trigger XR transmission response
|
Table 9.12.3.10-1 describes the information flow from the SEALDD client to the SEALDD server to acknowledge XR transmission connection operation between two UEs.
Table 9.12.3.10-1: Trigger XR transmission response
Information element
Status
Description
Result
M
Result of the operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.4 APIs
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.4.1 General
|
Table 9.12.4.1-1 illustrates the APIs exposed by SEALDD server for XR transmission.
Table 9.12.4.1-1: List of SEALDD server APIs for XR transmission
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_XRTransmission
Request
Request/Response
VAL server
Sdd_XRTransmissionConnnection
Establish
Request/Response
SEALDD client
Trigger (NOTE)
Request/Response
SEALDD server
Inform
Request/Response
SEALDD client
Sdd_SEALDD-UUcConnection
Establish
Request/Response
SEALDD client
NOTE: The Sdd_XRTransmissionConnection_Trigger API operation is exposed by the SEALDD client.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.4.2 Sdd_XRTransmission Request operation
|
API operation name: Sdd_XRTransmission Request
Description: The consumer requests for one time for multi-modal XR transmission service.
Inputs: See clause 9.12.3.1.
Outputs: See clause 9.12.3.2
See clause 9.12.2.1.2 and 9.12.2.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.4.3 Sdd_XRTransmissionConnection_Establish operation
|
API operation name: Sdd_XRTransmissionConnection_Establish
Description: The consumer requests for multi-modal transmission connection establishment.
Inputs: See clause 9.12.3.3.
Outputs: See clause 9.12.3.4.
See clause 9.12.2.1.2 and 9.12.2.2.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.4.4 Sdd_SEALDD-UUcConnectionEstablish operation
|
API operation name: Sdd_SEALDD-UUcConnectionEstablish
Description: The consumer requests for SEALDD-UUc connection establishment between the SEALDD client on 3GPP UE and tethered device.
Inputs: See clause 9.12.3.5.
Outputs: See clause 9.12.3.6.
See clause 9.12.2.3.4 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.4.5 Sdd_XRTransmissionConnection_Trigger operation
|
API operation name: Sdd_XRTransmissionConnection_Trigger
Description: The consumer requests to trigger direct multi-modal transmission connection establishment between two UEs.
Inputs: See clause 9.12.3.7.
Outputs: See clause 9.12.3.8.
See clause 9.12.2.4 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.12.4.6 Sdd_XRTransmissionConnection_Inform operation
|
API operation name: Sdd_XRTransmissionConnection_Inform
Description: The consumer informs direct multi-modal transmission connection establishment between two UEs.
Inputs: See clause 9.12.3.9.
Outputs: See clause 9.12.3.10.
See clause 9.12.2.4 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.13 SEALDD enabled adaptive data transmission
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.13.1 General
|
The following clauses specify procedures, information flows and APIs about SEALDD enabled adaptive data transmission.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.13.2 SEALDD enabled adaptive data transmission
|
Figure 9.13.2-1 illustrate the procedure for supporting adaptive data transmission. The SEALDD facilitates to transmit data between the VAL client and VAL server adaptively by using application enablement layer capabilities of the AIML Enablement server defined in 3GPP TS 23.482 [xx]. This procedure is used to support adaptive data transmission for XR services.
Pre-conditions:
- The AIMLE Server is known by the consumer and the SEALDD Server.
- The AI/ML services provided by the AIMLE Server is allowed for exposure to the consumer and the SEALDD Server.
- The consumer decides on the application which requires split image/video processing (distribute image/video processing tasks to multiple split endpoints for processing).
- Up to requirements of high layer application, SEALDD Server triggers interaction with AIMLE Server for assistance information.
Figure 9.13.2-1: SEALDD enabled adaptive data transmission procedure
1. The consumer (e.g. VAL server, VAL client via SEALDD client) sends adaptive data transmission request to the SEALDD server (e.g. for supporting XR service to deliver/distribute data to the split AI/ML endpoints (i.e. VAL client(s))). The request message contains message as defined in table 9.13.3.1-1.
2. Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server responses to the VAL server. The SEALDD server derives information for the request, for example, based on the message in the request to decide whether assistance from 5GC and/or AIMLE server is needed or not, and determine downstream entities and services needed based on the information derived.
Then the SEALDD server sends request to the AIMLE server for split operation assistance information for the data transmission. For example, for split AI/ML image/video processing, the request contains the information of split AI/ML endpoints (from the request in step 1), data information (e.g. data type, data size, range of data size) to be delivered/distributed to the split AI/ML endpoints, may contain QoS requirements on the data transmission, e.g. desired data transmission time. The information flow for the request reuses the mechanisms specified in 3GPP TS 23.482 [xx].
3. The SEALDD server may request and receive assistance from 5GC, as described in step 2, e.g. assistance information from NWDAF (or via NEF) about analytics on E2E data volume transfer time. In the request from SEALDD server to NWDAF for E2E data volume transfer time analytics, the split AI/ML endpoints information and a pre-configured data size (or data size range) may be used (the pre-configured data size may be the data size provided in step 1 or be decided by the SEALDD server according to the data size range in step 1 and based on its local policy. The data size range is provided in step 1.). The analytics subscription is modified when the actual data size changed. The actual data size may be obtained via measurement described in Sdd_TransmissionQuality Management API.
4. The SEALDD server triggers to establish connection among the consumer, SEALDD server, SEALDD client(s), and with the split AI/ML endpoints (i.e. VAL client(s)) for the data transmission. The split operation assistance information received in steps 2 and 3 is used by the SEALDD server separately or jointly based on need and local policy.
According to the assistance information, the SEALDD server may adjust the data volume to be transmission to each of the split AI/ML endpoints (if adaptive assign of date volume to the split AI/ML endpoints is allowed), or adjust the time point/time window for data transmission to the split endpoints.
NOTE 1: Adaptive assign of date volume to split AI/ML endpoints is allowed in the scenarios when there is no dependency of data processing at different split AI/ML endpoints and no specifical requirement on data assignment to different split AI/ML endpoints for processing.
NOTE 2: The connection establishment and data transmission procedures could use the existing mechanisms in clause 9.12.2.1.2.
5. Operations are performed at the consumer, SEALDD server, SEALDD client(s), and VAL client(s) for the data transmission, e.g. image/video/multi-modal data transmission from the consumer to the split AI/ML endpoints.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.13.3 Information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.13.3.1 SEALDD adaptive data transmission request
|
Table 9.13.3.1-1 describes the information flow from the consumer to the SEALDD server for requesting or updating request for an adaptive data transmission.
Table 9.13.3.1-1: SEALDD adaptive data transmission request
Information element
Status
Description
Requestor ID
M
(NOTE)
The identifier of the consumer (e.g. VAL server ID, SEALDD client ID, VAL client ID).
VAL service ID
O
Identity of the VAL service.
VAL UE ID(s)
O
Identifier(s) of the endpoints (i.e. VAL UE(s)).
Adaptive data assign Indicator
O
Indicate that the data can be assigned to different endpoints adaptively.
Data information
M
The information of the data needs to be delivered or distributed.
>Data type
O
The type of data, could be e.g. image, video, multi-model data (e.g. audio, video, positioning, haptic data).
>Data size information
M
The maximum/minimum/average size of the data or a range of size for the data (a pair of minimum and maximum data volumes) to be delivered/distributed.
>Time duration
M
The time duration (start and end time) expected for sending the volume of data.
QoS requirement
O
The QoS requirement, e.g. latency for data transmission.
Assistance information
O
The assistance information for deliver/distribute the data, e.g. time point/time window for the data transmission to the split AI/ML endpoints.
NOTE: This information element shall not be updated.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.13.3.2 SEALDD adaptive data transmission response
|
Table 9.13.3.2-1 describes the information from the SEALDD server to the consumer for responding to the adaptive data transmission request.
Table 9.13.3.2-1: SEALDD adaptive data transmission response
Information element
Status
Description
Result
M
The result of the request (positive or negative acknowledgement).
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.13.4 APIs
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.13.4.1 General
|
Table 9.13.4.1-1 illustrates the APIs exposed by SEALDD server for adaptive data transmission.
Table 9.13.4.1-1: List of SEALDD server APIs for adaptive data transmission
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_AdaptiveTransmission
Request
Request/Response
VAL server, SEALDD client
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
9.13.4.2 Sdd_AdaptiveTransmission Request operation
|
API operation name: Sdd_AdaptiveTransmission Request
Description: The consumer requests for adaptive data transmission service.
Inputs: See clause 9.13.3.1.
Outputs: See clause 9.13.3.2.
See clause 9.13.2 for details of usage of this operation.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10 SEALDD services over Satellite Access
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.1 General
|
This clause provides clarifications on the procedures and information flows for enabling SEALDD services using satellite access.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.2 SEALDD enabled transmission for S&F Satellite operation
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.2.1 General
|
This clause provides the services to support the transmission for delivery of delay-tolerant/non-real-time satellite services (i.e. CIoT/MTC, SMS) based on SEALDD capabilities including adapt the DL data delivery according to the S&F events from the 3GPP core network.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.2.2 Procedures
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.2.2.1 SEALDD enabled data transmission for delay-tolerant satellite services
|
Figure 10.2.2.1-1 illustrates the procedure for establishing S&F data transmission connection, and the SEALDD facilitates the delay-tolerant satellite services to transmit its data between the VAL client and VAL server.
Pre-condition:
- The VAL server discovers and select the SEALDD server by CAPIF functions.
Figure 10.2.2.1-1: SEALDD enabled data transmission for delay-tolerant satellite services
1. The VAL server decides to use SEALDD service for delay-tolerant traffic transfer and allocates address/port as SEALDD-S Data transmission connection information for receiving the data packets from SEALDD server. The VAL server sends Sdd_DTwithS&FTransmission request to the SEALDD server discovered by CAPIF. The service request includes UE ID/address, VAL server ID, VAL service ID, SEALDD-S Data transmission connection information of the VAL server side.
2. Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, SEALDD server allocates the SEALDD-S data transmission connection information (e.g., address/port) of SEALDD server side to receive the application data packets from the VAL server to be delivered to the VAL UE. The SEALDD server responds with a Sdd_DTwithS&FTransmission response.
NOTE 1: The SEALDD-S data transmission connection information of the SEALDD server side is optional, if the SEALDD server uses the downlink pull mode to fetch the application data from the address provided by the VAL server in step 1, and uses the uplink push mode to send the application data to the address provided by VAL server.
3. Same as step 3-9 of clause 9.2.2.2.
4. The SEALDD server subscribes the UE S&F status events from the 3GPP CN and is notified about the UE S&F status events information e.g., whether UE is registered in S&F Mode, the estimated delivery time indicating the DL estimated time to send data from the UE to gateway or from gateway to UE. The SEALDD server stores or the received UE S&F status events information for further control the downlink application data transmission.
5. The VAL server sends downlink application data to the SEALDD server which further delivers it to the VAL UE.
NOTE 2: The SEALDD server may receive the DLapplication data from the VAL server in step 10 before receiving the UE S&F status events notification from the 3GPP CN in step 9.
6. The SEALDD server controls the downlink application data delivery to the SEALDD client based on the UE S&F status events information, when the UE is in S&F mode:
- pending the DL data transmission when the Feeder Link is not available;
- (re-)transmitting the pending DL data when the Feeder Link is available.
- DL data volume to be transmitted is smaller than maximum S&F data storage quota per application per UE.
- If DL estimated delivery time is received from 3GPP CN, it may be used by the SEALDD server to estimate whether the transmitted DL application data is successfully delivered to the UE and its corresponding storage is available for new DL data. For each Feeder Link available period, the SEALDD server starts an estimated delivery timer based on the DL estimated delivery time which is corresponding to the current feeder link. The estimated delivery timer may be greater than or equal to the DL estimated delivery time. When in next Feeder Link available period, the SEALDD server checks the previous estimated delivery timer is expired or not before transmitting the DL data. Also, the maximum S&F data storage quota per application per UE is also considered.
a. If timer expires, the SEAL server calculates the new DL data volume (e.g., increasing the volume by certain data size (e.g., size of data previously delivered to the SEALDD client)).
b. If timer not expire, the SEALDD server also checks the available data volume within the maximum S&F data storage quota. The SEALDD server may send DL data limited within the available data volume. If no available data volume, the SEALDD server pends the DL data transmission until the timer expires.
Editor's note: whether the SEALDD server will consider the forwarding with higher priority policy for the DL data delivery is FFS.
7. The SEALDD server sends the DL data to the VAL UE via the 3GPP network as indicated in step 11.
8. Optionally, the SEALDD server may send Sdd_DTwithS&FTransmission notification to the VAL server to influence the DL application data transmission from VAL server if the VAL UE connection status changes or the DL data transmission from the VAL server needs to be adjusted.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.2.2.2 Client initiated data transmission for delay-tolerant satellite services
|
Figure 10.2.2.2-1 illustrates the procedure for establishing S&F data transmission connection, and the SEALDD facilitates the delay-tolerant satellite services to transmit data initiated by the VAL client to VAL server.
Pre-condition:
- The VAL client is aware of the availability of delay-tolerant satellite services to transmit data.
Figure 10.2.2.2-1: Client initiated data transmission for delay-tolerant satellite services
1. The VAL client decides to use SEALDD service for delay-tolerant traffic transfer.
2. Same as steps 2-4 of clause 9.2.2.7.
3. The SEALDD client provides the acknowledgment for the request made in step 1.
4. The SEALDD client sends the UL data to the SEALDD server via the 3GPP network.
5. The SEALDD server subscribes the recipient UE S&F status events from the 3GPP CN as specified in clause 5.6.3.10 of 3GPP TS 23.682 [24] and is notified about the recipient UE S&F status events information e.g., whether UE is registered in S&F Mode, the estimated delivery time indicating the DL estimated time to send data from the gateway to the recipient UE. The SEALDD server stores the received recipient UE S&F status events information for further control the downlink application data transmission.
Editor's note: How SEALDD server knows the recipient UE information is FFS.
6. The SEALDD server controls the downlink application data delivery to the SEALDD client based on the UE S&F status events information, when the recipient UE is in S&F mode and receives the DL estimated delivery time is received from 3GPP CN. If the recipient UE is not available or not registered to S&F mode, then the SEALDD server handles the DL data as per the service policy.
7. The SEALDD server sends the Sdd_S&FTransmission_notification to the SEALDD client and VAL client including the DL estimated delivery time of the recipient UE.
NOTE 1: VAL client can use the DL estimated delivery time of the recipient UE to control the UL application data delivery.
8. The SEALDD server sends the DL data to the VAL server.
NOTE 2: Details of step 1, step 3 and step 7 are out of scope of the current specification.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.2.3 Information flows
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.2.3.1 SEALDD enabled DTwithS&F transmission request
|
Table 10.2.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting the delay-tolerant with S&F application transmission service.
Table 10.2.3.1-1: SEALDD enabled DTwithS&F transmission request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
Identity of the VAL service
Identity
M
Identifier of specific UE or VAL user
SEALDD-S Data transmission connection information
M
Address/port and/or URL of the VAL server to receive the application packets from the SEALDD server.
VAL UE connection status subscription indication
O
Indicates the VAL server expected to receive the connection status notification
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.2.3.2 SEALDD enabled DTwithS&F transmission response
|
Table 10.2.3.2-1 describes the information flow from the SEALDD server to the VAL server for responding to the delay-tolerant with S&F application transmission.
Table 10.2.3.2-1: SEALDD enabled DTwithS&F transmission response
Information element
Status
Description
Result
M
Success or failure.
SEALDD-S information Data transmission connection information
O
Address/port and/or URL of the SEALDD server to receive the packets from the VAL server for application traffic transfer
Cause
O
(see NOTE)
Indicates the reason for the failure, e.g. SEALDD policy mismatch.
NOTE: The IE is only present if the Result is failure.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.2.3.3 SEALDD DTwithS&F transmission notification
|
Table 10.2.3.3-1 describes the information flow from the SEALDD server to the VAL server to notify S&F delivery related events.
Table 10.2.3.3-1: SEALDD connection status notification
Information element
Status
Description
Event ID
O
(see NOTE)
Identifies event SEALDD client connection status e.g., reachable, unreachable, sleeping.
DL data delivery instructions
O
(see NOTE)
Indicates the instructions to the VAL server regarding the DL data delivery
> Adjust DL data volume
O
Indicates adjusting DL data volume with suggested traffic volume
> Pending DL data delivery
O
Indicates pending DL data delivery due to e.g., feeder link is not available
> Resume DL data delivery
O
Indicates pending DL data delivery due to e.g., feeder link is available
Identity
M
Identifier of VAL UE or VAL user.
VAL service ID
O
Identity of the VAL service.
NOTE: Either Event ID IE or the DL data delivery instruction ID is present.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
10.2.3.4 Sdd_S&FTransmission_notification
|
Table 10.2.3.4-1 describes the information flow from the SEALDD server to the SEALDD Client to notify the DL estimated delivery time. Table 10.2.3.4-1: Sdd_S&FTransmission_notification Information element Status Description VAL server ID M Identity of the VAL server VAL service ID O Identity of the VAL service. Identity M Identifier of specific UE or VAL user Identity M Identifier of specific recipient UE or VAL user > DL estimated delivery time M DL estimated delivery time for a recipient UE Annex A (informative): Deployment models The SEALDD service can be deployed as a generic SEAL service and hence the deployment models for SEALDD service utilizes the deployment models specified in clause 8 of 3GPP TS 23.434 [4]. In the context of SEALDD service the following rules apply: - The SEAL server is the SEALDD server; - The SEAL-S reference point is the SEALDD-S reference point; and - The SEAL-E reference point is the SEALDD-E reference point. Annex B (Informative): Message delivery option: Utilizing MSGin5G B.1 General MSGin5G provides a data delivery messaging service in 5GS especially for enabling IoT device communications. It has been specified starting with Rel-17 in 3GPP TS 23.554 [9]. SEALDD is proposed as a generic data delivery enabler layer for all the verticals utilizing SEAL. It is beneficial to deploy one unified data delivery system suitable for all kinds of terminals to reduce the complexity of vertical applications. B.2 SEALDD utilizing MSGin5G MSGin5G functionalities described in 3GPP TS 23.554 [9] are integrated in SEALDD enabler layer. As shown in Figure B.2-1, MSGin5G client functionality is integrated in SEALDD client, and MSGin5G server functionality is integrated in SEALDD server. SEALDD server and SEALDD client can use MSGin5G functionalities to send SEALDD traffic in MSGin5G message format. Figure B.2-1 SEALDD utilizing MSGin5G Annex C (Informative): Overall lifecycle of SEALDD service Figure C-1: Overall lifecycle of SEALDD As shown in Figure C-1, the whole lifecycle of SEALDD to establish the SEALDD connection for the VAL client and VAL server includes two phases: 1. SEALDD server Service Preparation Phase (This Phase is used by the VAL server to get SEALDD server prepared for SEALDD client access): (1) When the VAL server decides to use the SEALDD service for data transmission enhancement, it discovers the SEALDD server (e.g. by CAPIF). (2) Then the VAL server triggers SEALDD service subscription procedure to the discovered SEALDD server, in that procedure, SEALDD server is associated with the VAL server, and specific SEALDD server resource (e.g. address/port of the SEALDD server for redundant transmission) is allocated for the VAL server's service to transfer SEALDD traffic. (3) For EDN scenario, the SEALDD server or VAL server will register the association information to the EES. 2. SEALDD client Service Consuming Phase (When SEALDD server is prepared in SEALDD server Service Preparation Phase, the VAL client(s) can trigger SEALDD client to connect to specific prepared SEALDD server for SEALDD service): (1) When VAL client request to use SEALDD service to transmit the VAL traffic to VAL server, the VAL client or SEALDD client can discover the proper SEALDD server associated with the VAL server (e.g. via EAS discovery, DNS query, pre-configuration or Application layer signalling). (2) Then SEALDD client can interact with SEALDD server to negotiate for SEALDD data transfer. If Address/Port is allocated in SEALDD service subscription phase, it will be notified to SEALDD client in this step. (3) Data transmission connection is established between the SEALDD client and SEALDD server for SEALDD traffic transfer. (5) The whole configuration is accomplished and the VAL traffic is transferred via the SEALDD connection. Annex D (Informative): Media data delivery in SEALDD D.1 General The SEALDD layer provides a general functionality to support data storage and data delivery by introducing 5G interaction (N5/N33 in control plane, N6 in user plane), including application data storage and management, application signalling and data transmission, E2E URLCC transmission, IoT message transmission (i.e. MSGin5G), etc. D.2 SEALDD deployment for media delivery For media delivery functionality in SEALDD, as shown in Figure D.2-1, the functionality/protocol defined in SA4 can be reused and further enhanced by SEALDD for supporting media type traffic, 5GMS/RTC AF and 5GMS RTC AS in 3GPP TS 26.501 [14] and 3GPP TS 26.506 [15] is utilized in SEALDD server to support the general media type delivery. The 5G transmission adaptation component is added in SEALDD, to facilitate the specific optimization for XR application provided by 5G network. NOTE: The functionality about 5G transmission adaptation component for media type will be further detailed based on the other progresses (e.g. application enabler for XR Services). Figure D.2-1: SEALDD deployment for media delivery When utilizing the SEALDD to deliver the media stream, the SEALDD server integrates the 5GMS/RTC AF and 5GMS/RTC AS, the SEALDD client integrates as the media session handler and the media player/framework, and follows the support the uplink media transmission and the downlink media transmission defined in 3GPP TS 26.501 [14] and 3GPP TS 26.506 [15]. The SEALDD-UU integrates the M4 and M5 interfaces of 5GMS according to 3GPP TS 26.501 [14], and the RTC-4 and RTC-5 interfaces of 5G RTC system according to 3GPP TS 26.506 [15]. The SEALDD-S integrates the M1 and M2 interfaces of 5GMS according to 3GPP TS 26.501 [14], and the RTC-1 interface of 5G RTC system according to 3GPP TS 26.506 [15]. Annex E (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2022-10 SA6#51-e TS skeleton (S6-222790) 0.0.0 2022-10 SA6#51-e Implementation of the following pCRs approved by SA6: S6-222984, S6-222986, S6-223040, S6-223041, S6-223042, S6-223043, S6-223044 0.1.0 2022-11 SA6#52 Implementation of the following pCRs approved by SA6: S6-223432, S6-223433, S6-223434, S6-223568 0.2.0 2022-12 SA#98-e SP-221218 Submitted to SA#98-e for information 1.0.0 2023-01 SA6#52-bis-e Implementation of the following pCRs approved by SA6: S6-230195, S6-230253, S6-230375, S6-230442, S6-230477, S6-230478, S6-230479, S6-230480, S6-230481 1.1.0 2023-03 SA6#53 Implementation of the following pCRs approved by SA6: S6-230611, S6-230725, S6-230868, S6-230869, S6-230870, S6-230871, S6-230872, S6-230873, S6-230877, S6-230879, S6-230880, S6-230881, S6-230882, S6-230883, S6-231045, S6-231046, S6-231047 1.2.0 2023-04 Moved clause 9.7.2.3 to clause 9.9.2.2 as per the approved pCR in S6-230880 1.2.1 2023-04 SA6#54-e Implementation of the following pCRs approved by SA6: S6-231297, S6-231298, S6-231300, S6-231330, S6-231365, S6-231485, S6-231554, S6-231558, S6-231559, S6-231560, S6-231561, S6-231562, S6-231564, S6-231565, S6-231637, S6-231638, S6-231639, S6-231640 1.3.0 2023-05 SA6#55 Implementation of the following pCRs approved by SA6: S6-231881, S6-231882, S6-232041, S6-232042, S6-232043, S6-232044, S6-232045, S6-232047, S6-232048, S6-232049, S6-232050, S6-232051, S6-232052, S6-232053, S6-232063, S6-232179, S6-232209 1.4.0 2023-06 SA#100 SP-230685 Submitted to SA#100 for approval 2.0.0 2023-06 SA#100 SP-230685 MCC Editorial update for publication after TSG SA approval (SA#100) 18.0.0 2023-09 SA#101 SP-231010 0001 1 F Introducing cause field and transfer of SEALDD server policy information in context transfer procedure 18.1.0 2023-09 SA#101 SP-231010 0002 1 F SEALDD client initiated connection release 18.1.0 2023-09 SA#101 SP-231010 0003 1 F Add the missing SEALDD policy delete procedure 18.1.0 2023-09 SA#101 SP-231010 0004 1 F Correct performance info in SEALDD server discovery 18.1.0 2023-09 SA#101 SP-231010 0005 2 F Update the SEALDD server discovery procedure 18.1.0 2023-09 SA#101 SP-231010 0006 F Correction for regular transmission procedure 18.1.0 2023-09 SA#101 SP-231010 0007 1 F Align the transmission quality report information 18.1.0 2023-09 SA#101 SP-231010 0009 1 F Adding the SEALDD overall lifecycle 18.1.0 2023-12 SA#102 SP-231567 0013 1 F Add missing information flow for transmission quality guarantee 18.2.0 2023-12 SA#102 SP-231567 0014 F Correct message name in policy driven connection management 18.2.0 2023-12 SA#102 SP-231567 0017 F Terminology alignment for transmission guarantee procedure 18.2.0 2023-12 SA#102 SP-231567 0018 F Correction for E2E redundant transmission procedure 18.2.0 2023-12 SA#102 SP-231567 0019 1 F Align the transmission quality analytics with ADAE server 18.2.0 2023-12 SA#102 SP-231567 0022 F Correction SEALDD context pull request 18.2.0 2023-12 SA#102 SP-231567 0025 2 F Complete information flow and API for transmission quality measurement procedure 18.2.0 2023-12 SA#102 SP-231567 0026 2 F Adding the consumer for data transmission quality query procedure 18.2.0 2023-12 SA#102 SP-231567 0027 1 F Clarification on SEALDD regular data transmission procedure 18.2.0 2023-12 SA#102 SP-231567 0028 2 F Correction for quality guarantee policy 18.2.0 2023-12 SA#102 SP-231568 0015 2 B SEALDD transmission quality guarantee with BAT and periodicity adaptation 19.0.0 2023-12 SA#102 SP-231568 0016 1 B Policy triggered redundant connection management 19.0.0 2023-12 SA#102 SP-231568 0020 2 F Clarification on media delivery functionality in SEALDD 19.0.0 2023-12 SA#102 SP-231568 0021 6 B Correction on SEALDD enabled congestion control for VAL application by supporting L4S mechanism 19.0.0 2023-12 SA#102 SP-231568 0023 2 B Provisioning a Geofence policy in the SEALDD server 19.0.0 2023-12 SA#102 SP-231568 0024 3 B Enhancements to the SEALDD connection status procedure 19.0.0 2024-03 SA#103 SP-240316 0029 1 F Clarification on content delivery in SEALDD-S interface 19.1.0 2024-03 SA#103 SP-240316 0030 2 F Clarification on media delivery functionality in SEALDD 19.1.0 2024-03 SA#103 SP-240316 0032 3 B Seamless SEALDD relocation enhancement 19.1.0 2024-03 SA#103 SP-240309 0034 A Alignment on VAL UE identity and VAL user identity 19.1.0 2024-03 SA#103 SP-240309 0036 2 A Complete API for regular data transmission procedure 19.1.0 2024-03 SA#103 SP-240309 0038 1 A Complete API for stored data transfer procedure 19.1.0 2024-03 SA#103 SP-240309 0042 1 A Add release operation for URLLC connection 19.1.0 2024-03 SA#103 SP-240309 0044 2 A Correct NRM and SEALDD interaction 19.1.0 2024-03 SA#103 SP-240309 0046 A Correct regular transmission procedure 19.1.0 2024-03 SA#103 SP-240309 0048 A Correct Sdd_TransmissionQualityMeasurement API 19.1.0 2024-03 SA#103 SP-240309 0050 A Correct URLLC transmission procedure 19.1.0 2024-03 SA#103 SP-240316 0051 3 B SEALDD Background data transfer 19.1.0 2024-03 SA#103 SP-240316 0052 F Correct IE presence condition 19.1.0 2024-06 SA#104 SP-240769 0055 3 F Functional model update to introduce the SEALDD UU-U and SEALDD S-U 19.2.0 2024-06 SA#104 SP-240769 0057 1 F Clarification on connection and flow in SEALDD 19.2.0 2024-06 SA#104 SP-240769 0059 1 F Clarification on the identifier of stored data from multiple SEALDD servers 19.2.0 2024-06 SA#104 SP-240769 0060 1 F Resolve Editor's notes about SEALDD query procedure 19.2.0 2024-06 SA#104 SP-240769 0061 1 F Update SEALDD connection status procedure 19.2.0 2024-06 SA#104 SP-240763 0063 1 A Alignment on data transmission connection establishment and release procedure re 19.2.0 2024-06 SA#104 SP-240763 0065 1 A Correction on E2E redundant transmission procedure 19.2.0 2024-06 SA#104 SP-240763 0067 1 A Correction on SEALDD server discovery and selection procedure 19.2.0 2024-06 SA#104 SP-240769 0068 1 F Correct SEALDD connection status event 19.2.0 2024-06 SA#104 SP-240763 0070 2 A Correct context IE table 19.2.0 2024-06 SA#104 SP-240769 0071 2 B Add client-initiated SEALDD connection establishment 19.2.0 2024-06 SA#104 SP-240769 0072 F Correct BDT IE table 19.2.0 2024-06 SA#104 SP-240769 0073 F Correct SEALDD quality measurement subscription response 19.2.0 2024-06 SA#104 SP-240769 0074 3 F Clarification about SEALDD enabled connection establishment based on policy 19.2.0 2024-09 SA#105 SP-241232 0075 1 B Support of QoS measurement for Multi-Modal traffic in SEALDD layer 19.3.0 2024-09 SA#105 SP-241227 0077 F Correction for SEALDD enabled L4S congestion control 19.3.0 2024-09 SA#105 SP-241216 0079 1 A Correction for SEALDD server discovery for SEALDD client 19.3.0 2024-09 SA#105 SP-241232 0080 2 B SEALDD policy configuration for multi-modal flows 19.3.0 2024-09 SA#105 SP-241232 0082 4 B PDU set handling 19.3.0 2024-09 SA#105 SP-241227 0083 1 F Correct API operation input output 19.3.0 2024-09 SA#105 SP-241227 0084 F Seamless SEALDD server relocation 19.3.0 2024-12 SA#106 SP-241733 0086 3 B Multi-modal SEALDD flow identifier 19.4.0 2024-12 SA#106 SP-241733 0087 2 B Architecture update to support the tethered UE based on PINAPP 19.4.0 2024-12 SA#106 SP-241733 0088 3 B Add new feature to support the tethered UE 19.4.0 2024-12 SA#106 SP-241733 0089 6 B Add new feature to support the Multi-modal flows alignment and monitoring 19.4.0 2024-12 SA#106 SP-241729 0090 F Correct BAT adaptation 19.4.0 2024-12 SA#106 SP-241729 0091 D Correct SEALDD-Uu 19.4.0 2024-12 SA#106 SP-241733 0092 1 B Support UE-to-UE communication 19.4.0 2024-12 SA#106 SP-241711 0095 1 A Correction to APIs exposed by SEALDD client side 19.4.0 2024-12 SA#106 SP-241729 0096 1 F Completion of SEALDD enabled URLLC transmission connection based on policy 19.4.0 2024-12 SA#106 SP-241729 0097 F Completion of SEALDD Background data transfer 19.4.0 2024-12 SA#106 SP-241729 0098 1 F Clarification on SEALDD server discovery and determination 19.4.0 2024-12 SA#106 SP-241729 0100 F Correction on NOTE in clause 9.2.2.1 19.4.0 2024-12 SA#106 SP-241729 0102 1 F Correction on SEALDD data transmission connection establishment message 19.4.0 2024-12 SA#106 SP-241729 0103 1 F Correction on SEALDD enabled regular data transmission connection establishment procedure 19.4.0 2024-12 SA#106 SP-241729 0104 1 F Fix the inconsistency on SEALDD enabled signalling transmission connection establishment procedure 19.4.0 2024-12 SA#106 SP-241733 0108 2 B XR architecture based on SEALDD architecture 19.4.0 2024-12 SA#106 SP-241717 0109 4 B SEALDD enabled S&F transmission 19.4.0 2024-12 SA#106 SP-241729 0110 1 B SEALDD enabled data transmission quality guarantee using a Non-3GPP RAT 19.4.0 2024-12 SA#106 SP-241729 0111 1 B XR Application Client Capability Information Request Procedure 19.4.0 2024-12 SA#106 SP-241733 0114 1 B SEALDD-UUc Cardinality rule 19.4.0 2024-12 SA#106 SP-241733 0115 1 B Support the user group level QoS guarantee 19.4.0 2024-12 SA#106 SP-241729 0117 F Correction the description on clause 9.2.2.1 19.4.0 2024-12 SA#106 SP-241729 0118 1 F Fix the inconsistency on SEALDD connection information in clause 9.3 19.4.0 2024-12 SA#106 SP-241729 0119 2 F Fix the inconsistency on SEALDD connection information in clause 9.3 19.4.0 2024-12 SA#106 SP-241733 0120 2 B Support for Multi-modal flows synchronization monitoring 19.4.0 2024-12 SA#106 SP-241733 0121 2 B Adding SEALDD Adaptive XR Data Transmission Service 19.4.0 2024-12 SA#106 SP-241729 0122 F Correction on SEALDD URLLC transmission connection establishment request 19.4.0 2024-12 SA#106 SP-241729 0123 1 F Correction on Mode of reporting 19.4.0 2025-03 SA#107 SP-250217 0125 2 B Address the EN in UE-to-UE communication 19.5.0 2025-03 SA#107 SP-250217 0127 1 F Remove the EN about multi-modal flow synchronization and crossflow measurement 19.5.0 2025-03 SA#107 SP-250217 0128 1 B Add update and delete service operation of SEALDD client policy configuration 19.5.0 2025-03 SA#107 SP-250215 0129 F Informative wording corrections 19.5.0 2025-03 SA#107 SP-250215 0130 1 D Corrections to 3GPP spec reference 19.5.0 2025-03 SA#107 SP-250215 0131 1 D NOTE number correction 19.5.0 2025-03 SA#107 SP-250215 0132 1 D Add missing figures to clause 9.12.2.3 19.5.0 2025-03 SA#107 SP-250215 0133 2 D Message name style alignment 19.5.0 2025-03 SA#107 SP-250217 0134 1 F Add service operation of Crossflow measurement and delay difference for XR application 19.5.0 2025-03 SA#107 SP-250217 0135 2 B Multi-Modal traffic indication in SEALDD layer 19.5.0 2025-03 SA#107 SP-250215 0136 F Correction on mode of reporting 19.5.0 2025-03 SA#107 SP-250215 0137 F Corrections to non-3GPP access measurements 19.5.0 2025-03 SA#107 SP-250217 0139 F Solving Editor’s Notes on PDU set an RTT 19.5.0 2025-03 SA#107 SP-250217 0140 2 B Completion of SEALDD-enabled flow Alignment procedure 19.5.0 2025-03 SA#107 SP-250205 0141 2 B Client initiated data transmission 19.5.0
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
1 Scope
|
The present document specifies the functional architecture for service enabler architecture layer (SEAL) and the procedures, information flows and APIs for each service within SEAL in order to support vertical applications over the 3GPP system. The present document is applicable to vertical applications using E-UTRAN or NR access based on the EPS or 5GS architecture defined in 3GPP TS 23.401 [9], 3GPP TS 23.246 [17], 3GPP TS 23.468 [16], 3GPP TS 23.501 [10], and 3GPP TS 23.247 [39]. To ensure efficient use and deployment of vertical applications over 3GPP systems this specification for SEAL services includes the group management, configuration management, location management, identity management, key management, network resource management, notification management, network slice capability enablement, data delivery and application data analytics enablement.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains".
[3] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[4] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[5] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[6] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[7] 3GPP TS 23.286: "Application layer support for V2X services; Functional architecture and information flows".
[8] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[9] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[10] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[11] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[12] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
[13] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[14] 3GPP TS 23.002: "Network Architecture".
[15] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[16] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[17] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[18] 3GPP TS 23.203: "Policy and charging control architecture".
[19] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[20] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[21] 3GPP TS 29.214: "Policy and charging control over Rx reference point".
[22] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[23] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[24] IETF RFC 6733 (October 2012): "Diameter Base Protocol".
[25] ETSI TS 102 894-2 (V1.2.1): "Intelligent Transport Systems (ITS); Users and applications requirements; Part 2: Applications and facilities layer common data dictionaryMultimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[26] ETSI TS 102 965 (V1.4.1): "Intelligent Transport Systems (ITS); Application Object Identifier (ITS-AID); Registration".
[27] ISO TS 17419: "Intelligent Transport Systems - Cooperative systems - Classification and management of ITS applications in a global context".
[28] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[29] 3GPP TS 33.434: "Service Enabler Architecture Layer (SEAL); Security aspects for Verticals".
[30] 3GPP TS 29.549: "Service Enabler Architecture Layer for Verticals (SEAL); Application Programming Interface (API) specification; Stage3".
[31] 3GPP TS 23.285: "Architecture enhancements for V2X services".
[32] IETF RFC 7252: "The Constrained Application Protocol (CoAP)".
[33] IETF RFC 8323: "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets".
[34] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[35] IEEE Std 802.1Qcc-2018: "Standard for Local and metropolitan area networks - Bridges and Bridged Networks - Amendment: Stream Reservation Protocol (SRP) Enhancements and Performance Improvements".
[36] IEEE 802.1Q-2018: "IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks".
[37] IEEE Std 802.1CB-2017: "Frame Replication and Elimination for Reliability".
[38] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[39] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2".
[40] 3GPP TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service".
[41] 3GPP TS 28.531: "Management and orchestration; Provisioning".
[42] 3GPP TS 28.533: "Management and orchestration; Architecture framework".
[43] 3GPP TS 28.530: "Management and orchestration; Concepts, use cases and requirements".
[44] 3GPP TS 28.532: "Management and orchestration; Generic management services".
[45] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[46] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[47] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics".
[48] 3GPP TS 23.433: "Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications".
[49] 3GPP TS 23.436: "Procedures for Application Data Analytics Enablement Service".
[50] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2"
[51] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3"
[52] 3GPP TS 23.256 "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
[53] 3GPP TS 37.355: "LTE Positioning Protocol (LPP)".
[54] 3GPP TS 29.122: "T8 reference point for Northbound APIs".
[55] Void
[56] 3GPP TS 23.482 "Functional architecture and information flows for AIML Enablement Service".
[57] 3GPP TS 23.586: "Architectural Enhancements to support Ranging based services and Sidelink Positioning".
[58] 3GPP TS 23.437: "Service Enabler Architecture Layer for Verticals (SEAL); Spatial map and Spatial anchors".
[59] 3GPP TS 23.438: "Service Enabler Architecture Layer for Verticals (SEAL); Digital Assets".
[60] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS) ".
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
3 Definitions, symbols and abbreviations
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions 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 user: An authorized user, who can use a VAL UE to participate in one or more VAL services.
VAL user ID: A generic name for the user ID of a VAL user within a specific VAL service.
VAL UE: A UE that can be used to participate in one or more VAL services.
VAL client: An entity that provides the client side functionalities corresponding to the vertical applications.
SEAL client: An entity that provides the client side functionalities corresponding to the specific SEAL service.
VAL service: A generic name for any service offered by the VAL service provider to their VAL users.
SEAL service: A generic name for a common service (e.g. group management, configuration management, location management) that can be utilized by multiple vertical applications.
SEAL provider: Provider of SEAL service(s).
VAL server: A generic name for the server application function of a specific VAL service.
SEAL server: An entity that provides the server side functionalities corresponding to the specific SEAL service.
VAL system: The collection of applications, services, and enabling capabilities required to support a VAL service.
Primary VAL system: VAL system where the VAL user profiles of a VAL user are defined.
Partner VAL system: A VAL system that has a business relationship with the primary VAL system such that service can be offered to primary VAL system users.
VAL group: A defined set of VAL UEs or VAL users configured for specific purpose in a VAL service.
NOTE: The set could be of either VAL UEs or VAL users depending on the specific VAL service.
VAL group home system: The VAL system where the VAL group is defined.
VAL group member: A VAL service user, whose VAL user ID is listed in a particular VAL group.
VAL stream: A time sensitive communication stream is used to transport a time sensitive data flow, and is defined by a stream specification (which identifies a source and destination of the data flow) and a traffic specification (which defines the characteristics of the data flow). VAL stream is identified by a VAL stream ID.
Vertical: See vertical domain.
Vertical application: An application catering to a specific vertical.
MBS session announcement: Mechanism to provide the necessary information to the NRM client to enable the reception of the VAL service data via the MBS session.
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.104 [2] apply:
Vertical domain
For the purpose of the present document, the following terms given in 3GPP TS 23.247 [39] apply:
MBS session
MBS service area
MB-SMF service area
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
5GS 5G System
5GVN 5G Virtual Network
CAPIF Common API Framework for northbound APIs
CNC Centralized Network Configuration
CRUDN Create, Retrieve, Update, Delete and Notify
EPC Evolved Packet Core
GPSI Generic Public Subscription Identifier
LWP Light-weight Protocol
NEF Network Exposure Function
NR New Radio
PCC Policy and Charging Control
SCEF Service Capability Exposure Function
SEAL Service Enabler Architecture Layer for Verticals
SEAL-UU Service Enabler Architecture Layer for Verticals, Universal UE-network interface
TSC Time Sensitive Communication
TSN Time Sensitive Networking
VAL Vertical Application Layer
NOP Network Operator
NSaaS Network Slice as a Service
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4 Architectural requirements
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.1 General
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.1.1 Description
|
This subclause specifies the general requirements for SEAL.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.1.2 Requirements
|
[AR-4.1.2-a] The SEAL shall support applications from one or more verticals.
[AR-4.1.2-b] The SEAL shall support multiple applications from the same vertical.
[AR-4.1.2-c] The SEAL shall offer SEAL services as APIs to the vertical applications.
[AR-4.1.2-d] The SEAL shall support notification mechanism for SEAL service events.
[AR-4.1.2-e] The API interactions between the vertical application server(s) and SEAL server(s) shall conform to CAPIF as specified in 3GPP TS 23.222 [8].
[AR-4.1.2-f] The SEAL server(s) shall provide a service API compliant with CAPIF as specified in 3GPP TS 23.222 [8].
[AR-4.1.2-g] The SEAL shall leverage the satellite connectivity.
[AR-4.1.2-h] The SEAL shall support discontinuous coverage of satellite connectivity.
[AR-4.1.2-i] The SEAL shall support managing S&F operations regarding satellite connectivity in EPS.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.2 Deployment models
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.2.1 Description
|
This subclause specifies the requirements for various deployment models.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.2.2 Requirements
|
[AR-4.2.2-a] The SEAL shall support deployments in which SEAL services are deployed only within PLMN network.
[AR-4.2.2-b] The SEAL shall support deployments in which SEAL services are deployed only outside of PLMN network.
[AR-4.2.2-c] The SEAL shall support deployments in which SEAL services are deployed both within and outside the PLMN domain at the same time.
[AR-4.2.2-d] The SEAL shall support SEAL capabilities for centralized deployment of vertical applications.
[AR-4.2.2-e] The SEAL shall support SEAL capabilities for distributed deployment of vertical applications.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.3 Location management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.3.1 Description
|
This subclause specifies the requirements for location management service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.3.2 On-network functional model requirements
|
[AR-4.3.2-a] The SEAL shall enable sharing location data between client and server for vertical applications usage.
[AR-4.3.2-b] The SEAL shall support different granularity of location data, as required by the vertical application.
[AR-4.3.2-c] The SEAL shall support requests for on-demand location reporting.
[AR-4.3.2-d] The SEAL shall support client location reporting based on triggers.
[AR-4.3.2-e] The SEAL shall enable vertical applications to receive updates to the location information.
[AR-4.3.2-f] The SEAL shall enable sharing the network location information obtained from the 3GPP network systems to the vertical applications.
[AR-4.3.2-g] The SEAL shall provide a mechanism to enable vertical applications to obtain a list of UE(s), and the location information of each UE, in the proximity to a designated/requested location.
[AR-4.3.2-h] The SEAL shall support the Geofencing.
[AR-4.3.2-i] The SEAL shall support the location history store and retrieve.
[AR-4.3.2-j] The SEAL shall support the UE location reporting with more information (e.g. velocity) to the vertical application.
[AR-4.3.2-k] The SEAL shall support the stored UE location information reusing.
[AR-4.3.2-l] The SEAL shall support the adaptive location reporting based on the UE moving trend.
[AR-4.3.2-m] The SEAL shall enable optimizing the location service operations when the multiple UEs are sharing the same location.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.3.3 Off-network functional model requirements
|
[AR-4.3.3-a] The SEAL shall support on-demand location reporting and event-triggered location reporting within PC5 communication.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.4 Group management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.4.1 Description
|
This subclause specifies the requirements for group management service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.4.2 Requirements
|
[AR-4.4.2-a] The SEAL shall enable group management operations (e.g. CRUDN) by the authorized users or VAL server.
[AR-4.4.2-b] The SEAL shall enable creation of group to be used by one or more vertical applications within the same VAL system.
[AR-4.4.2-c] The SEAL shall enable two or more groups to be merged (temporarily or permanently) into a single group by the authorized users or VAL server wherein all the group members of the constituent groups are designated as members of the merged group.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.5 Configuration management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.5.1 Description
|
This subclause specifies the requirements for configuration management service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.5.2 Requirements
|
[AR-4.5.2-a] The SEAL shall enable configuring service specific configuration data applicable to vertical applications.
[AR-4.5.2-b] The SEAL shall support configuring data applicable to different vertical applications.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.6 Key management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.6.1 Description
|
This subclause specifies the requirements for key management service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.6.2 Requirements
|
[AR-4.6.2-a] The SEAL shall support secure distribution of security related information (e.g. encryption keys).
[AR-4.6.2-b] The SEAL shall support all communications in SEAL ecosystem to be secured.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.7 Identity management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.7.1 Description
|
This subclause specifies the requirements for identity management service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.7.2 Requirements
|
[AR-4.7.2-a] The SEAL shall enable the access to SEAL services from the vertical application layer entities to be authorized.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.8 Network resource management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.8.1 Description
|
This subclause specifies the requirements for network resource management service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
4.8.2 Requirements
|
[AR-4.8.2-a] The SEAL shall enable support for unicast bearer establishment and modification to support service KPIs for VAL communications.
[AR-4.8.2-b] The SEAL shall enable support for multicast bearer establishment and modification to support service KPIs for VAL communications.
[AR-4.8.2-c] The SEAL shall support announcement of multicast bearers to the UEs.
[AR-4.8.2-d] The SEAL shall support switching of bearers between unicast and multicast.
[AR-4.8.2-e] The SEAL shall support multicast bearer quality detection.
[AR-4.8.2-f] The SEAL shall enable support for unicast PDU session establishment and modification to support service KPIs for VAL communications.
[AR-4.8.2-g] The SEAL shall enable support for MBS session (multicast or broadcast type) establishment and modification to support service KPIs for VAL communications.
[AR-4.8.2-h] The SEAL shall support announcement of MBS session (multicast or broadcast type) to the UEs.
[AR-4.8.2-i] The SEAL shall support switching of between unicast PDU session and MBS session (multicast or broadcast type).
[AR-4.8.2-j] The SEAL shall support MBS session (multicast or broadcast type) quality detection.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
5 Involved business relationships
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
5.1 Business relationships for VAL services
|
Figure 5.1-1 shows the business relationships that exist and that are needed to support a single VAL user.
Figure 5.1-1: Business relationships for VAL services
The VAL user belongs to a VAL service provider based on a VAL service agreement between the VAL user and the VAL service provider. The VAL service provider can have VAL service agreements with several VAL users. The VAL user can have VAL service agreements with several VAL service providers.
The VAL service provider and the home PLMN operator can be part of the same organization, in which case the business relationship between the two is internal to a single organization.
The VAL service provider can have SEAL provider arrangements with multiple SEAL providers and the SEAL provider can have PLMN operator service arrangements with multiple home PLMN operators. The SEAL provider and the VAL service provider or the home PLMN operator can be part of the same organization, in which case the business relationship between the two is internal to a single organization.
The home PLMN operator can have PLMN operator service arrangements with multiple VAL service providers and the VAL service provider can have PLMN operator service arrangements with multiple home PLMN operators. As part of the PLMN operator service arrangement between the VAL service provider and the home PLMN operator, PLMN subscription arrangements can be provided which allows the VAL UEs to register with home PLMN operator network.
The home PLMN operator can have PLMN roaming agreements with multiple visited PLMN operators and the visited PLMN operator can have PLMN roaming agreements with multiple home PLMN operators.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
5.2 Business relationships for VAL services with satellite connectivity
|
Figure 5.2-1 shows the business relationship for VAL services with satellite connectivity.
Figure 5.2-1: Business relationships for VAL services with satellite connectivity
The PLMN operator has satellite service agreement with the satellite service provider to offer his services e.g. to serve the unconnected areas.
The SEAL provider has satellite service agreement with the satellite service provider to enable SEAL to leverage satellite services to provide enhanced experience to end users of VAL services e.g. S&F, wider coverage.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6 Generic functional model for SEAL services
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.1 General
|
The functional model for SEAL is organized into generic SEAL service functional model and specific SEAL service functional models. The generic SEAL service functional model will be used as the reference model for the specific SEAL service functional models.
The following SEAL services are supported towards the vertical application layer:
- Location management;
- Group management;
- Configuration management;
- Identity management;
- Key management;
- Network resource management;
- Data delivery;
- Notification management;
- Network slice capability enablement; and
- Application data analytics enablement.
The generic functional model for the SEAL is organized into generic functional entities to describe a functional architecture which addresses the application layer support aspects for vertical applications. The on-network and off-network functional model is specified in this clause.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.2 On-network functional model description
|
Figure 6.2-1 illustrates the generic on-network functional model for SEAL.
Figure 6.2-1: Generic on-network functional model
In the vertical application layer, the VAL client communicates with the VAL server over VAL-UU reference point. VAL-UU supports both unicast and multicast delivery modes.
NOTE 1: The VAL-UU reference point is out of scope of the present document.
The SEAL functional entities on the UE and the server are grouped into SEAL client(s) and SEAL server(s) respectively. The SEAL consists of a common set of services (e.g. group management, location management) and reference points. The SEAL offers its services to the vertical application layer (VAL).
NOTE 2: The functionalities and reference points of the vertical application layer are out of scope of the present document.
NOTE 3: The vertical application layer may further consist of vertical application enabler layer functionalities (specified by 3GPP) and application specific functionalities, which is out of scope of the present document.
The SEAL client(s) communicates with the SEAL server(s) over the SEAL-UU reference points. SEAL-UU supports both unicast and multicast delivery modes. The SEAL client(s) provides the service enabler layer support functions to the VAL client(s) over SEAL-C reference points. The VAL server(s) communicate with the SEAL server(s) over the SEAL-S reference points. The SEAL server(s) may communicate with the underlying 3GPP network systems using the respective 3GPP interfaces specified by the 3GPP network system.
NOTE 4: Non-3GPP access used by the UE is out of scope of the present document.
The specific SEAL client(s) and the SEAL server(s) along with their specific SEAL-UU reference points and the specific network interfaces of 3GPP network system used are described in the respective on-network functional model for each SEAL service.
Figure 6.2-2 illustrates the functional model for interconnection between SEAL servers.
Figure 6.2-2: Interconnection between SEAL servers
To support distributed SEAL server deployments, the SEAL server interacts with another SEAL server for the same SEAL service over SEAL-E reference point.
Figure 6.2-3 illustrates the functional model for inter-service communication between SEAL servers.
Figure 6.2-3: Inter-service communication between SEAL servers
The SEAL server interacts with another SEAL server for inter-service communication over SEAL-X reference point.
Figure 6.2-4 illustrates the functional model for communication between SEAL server and VAL user database.
Figure 6.2-4: Communication between SEAL server and VAL user database
The SEAL server interacts with the VAL user database for storing and retrieving user profile over VAL-UDB reference point.
Figure 6.2-5 shows the functional model for the signalling control plane.
Figure 6.2-5: Functional model for signalling control plane
NOTE 5: The Light-weight Protocol (LWP) functional entities and reference points are a generic representation of protocol entities and reference points for use in constrained environments. Realizations of LWP by means of a particular transport protocol are defined in the annex of this specification. Realizations of LWP by means of transport protocols is not limited to those defined in the annex of this specification.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.3 Off-network functional model description
|
Figure 6.3-1 illustrates the generic off-network functional model for SEAL.
Figure 6.3-1: Generic off-network functional model
In the vertical application layer, the VAL client of UE1 communicates with VAL client of UE2 over VAL-PC5 reference point. A SEAL client of UE1 interacts with the corresponding SEAL client of UE2 over SEAL-PC5 reference points. The UE1, if connected to the network via Uu reference point, can also act as a UE-to-network relay, to enable UE2 to access the VAL server(s) over the VAL-UU reference point.
NOTE: The VAL-PC5 reference point is out of scope of the present document.
The specific SEAL client(s) along with their specific SEAL-PC5 reference points are described in the respective off‑network functional model for each SEAL service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4 Functional entities description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.1 General
|
Each subclause is a description of a functional entity corresponding to SEAL and does not imply a physical entity.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.2 Application plane
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.2.1 General
|
Entities within the application plane of a VAL system provide application control and media specific functions to support one or more VAL services.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.2.2 VAL client
|
The VAL client provides the client side functionalities corresponding to the vertical applications (e.g. V2X client). The VAL client supports interactions with the SEAL client(s).
NOTE: The details of the VAL client is specific to the vertical and out of scope of the present document.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.2.3 VAL server
|
The VAL server provides the server side functionalities corresponding to the vertical applications (e.g. V2X application servers). The VAL server acts as CAPIF's API invoker as specified in 3GPP TS 23.222 [8].
NOTE: The details of the VAL server is specific to the vertical and out of scope of the present document.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.2.4 SEAL client
|
The SEAL client provides the client side functionalities corresponding to the specific SEAL service. The SEAL client(s) supports interactions with the VAL client(s). The SEAL client also supports interactions with the corresponding SEAL client between the two UEs.
NOTE: It is up to each SEAL client to support the appropriate signalling plane entities.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.2.5 SEAL server
|
The SEAL server provides the server side functionalities corresponding to the specific SEAL service. The SEAL server supports interactions with the VAL server(s). The SEAL server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [8]. The SEAL server also supports interactions with the corresponding SEAL server in distributed SEAL deployments.
NOTE: It is up to each SEAL server to support the appropriate signalling plane entities.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.2.6 VAL user database
|
This functional entity contains information of the user profile associated with a VAL service that is served by the VAL service provider at the application plane.
Each VAL service may have a corresponding user database e.g. MCPTT user database as defined in 3GPP TS 23.379 [3], MCVideo user database as defined in 3GPP TS 23.281 [5] and MCData user database as defined in 3GPP TS 23.282 [6].
NOTE: It is up to each SEAL server to support the appropriate signalling plane entities.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3 Signalling control plane
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.1 SIP entities
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.1.1 Signalling user agent
|
This functional entity acts as the SIP user agent (both client and server) for all SIP transactions.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.1.2 SIP AS
|
The SIP AS functional entity supports the following functions on behalf of the VAL service:
- influencing and impacting the SIP session; and
- supporting event subscription and event notification.
NOTE: In the IM CN subsystem, this is provided by the Application Server as defined in 3GPP TS 23.002 [14].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.1.3 SIP core
|
6.4.3.1.3.1 General
The SIP core contains a number of sub-entities responsible for registration, service selection and routing in the signalling control plane.
The SIP core shall be either:
1. compliant with 3GPP TS 23.228 [15], i.e. the SIP core is a 3GPP IP multimedia core network subsystem; or
2. a SIP core, which internally need not comply with the architecture of 3GPP TS 23.228 [15], but with the reference points that are defined in subclause 6.5.3 (if exposed), compliant to the reference points defined in 3GPP TS 23.002 [14].
The data related to the functions of the SIP core, e.g. for data for application service selection, the identity of the serving registrar or authentication related information may be provided by the PLMN operator responsible for the bearer plane. In this case, the SIP database that is the source of the data may be part of the HSS. Alternatively, this data may be provided by the VAL service provider. In this case, the source of the data may be the VAL service provider's SIP database.
6.4.3.1.3.2 Local inbound / outbound proxy
The local inbound / outbound proxy functional entity acts as both an inbound proxy and an outbound proxy for all SIP transactions. This functional entity can provide the following functions:
- NAT traversal;
- Resource control;
- Route/forward requests and responses to the user agents;
- SIP signalling security; and
- Depending on the PLMN operator policy, discovery and address resolution, including E.164 numbers.
NOTE: In the IM CN subsystem, this functional entity is provided by the P-CSCF as defined in 3GPP TS 23.228 [15].
6.4.3.1.3.3 Registrar finder
The registrar finder functional entity is responsible for:
a) Identifying the serving registrar / application service selection functional entity. The serving registrar / application service selection functional entity is identified using information provided either by the PLMN operator's own SIP database or the VAL service provider's SIP database, and optionally using the PLMN operator's internal information e.g. network topology, registrar availability.
1) Registrar finder and registrar in the VAL service provider domain: registrar finder in the VAL service provider's domain uses the information from the VAL service provider's SIP database to identify the serving registrar in the VAL service provider domain.
2) Registrar finder and registrar in the PLMN operator domain: registrar finder uses information from PLMN operator's SIP database to identify the serving registrar in the PLMN operator domain.
3) Registrar finder in PLMN operator domain and registrar in VAL service provider domain: registrar finder uses information from the VAL service provider's SIP database to identify the serving registrar in the VAL service provider domain.
NOTE 1: The need for the registrar finder is deployment specific e.g. a deployment that has only one registrar does not need the registrar finder and the related SIP database information.
b) Providing discovery and address resolution, including E.164 numbers.
NOTE 2: In the IM CN subsystem, this is provided by the I-CSCF as defined in 3GPP TS 23.228 [15].
6.4.3.1.3.4 Registrar / application service selection
The registrar / application service selection functional entity provides the following functions:
- Registrar function (with integral provision of a location server) and also acts as an inbound proxy (with access to the integral location server), and outbound proxy for all SIP transactions where application service selection is required. It registers the user and maintains the association of the location and identity of the user in a location service. It provides notifications of the registration states.
- Supports authentication for identities provided within SIP signalling. Both the registrar (with integral location server) and authentication functions are supported by access either to the public network's own SIP database or the VAL service provider's SIP database.
- Can provide the application service selection for all SIP transactions, possibly based on application service selection information stored by either the public network's own SIP database or the VAL service provider's SIP database.
- Performs SIP signalling security.
NOTE: In the IM CN subsystem, this is provided by the S-CSCF as defined in 3GPP TS 23.228 [15].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.1.4 Diameter proxy
|
This functional entity acts as a proxy agent for Diameter messaging as specified in IETF RFC 6733 [24].
The Diameter proxy, when used on the AAA-2 interface, is collocated with the migration management server.
Other instances of the Diameter proxy may also be present in the SIP core / IMS.
NOTE: The number of instances of the Diameter proxy is deployment specific.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.2 SIP database
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.2.1 General
|
The SIP database contains information concerning the SIP subscriptions and corresponding identity and authentication information required by the SIP core, and such information as application service selection.
In deployment scenarios where the PLMN operator provides the SIP core, this database is provided by the HSS.
In deployment scenarios where the VAL service provider provides the SIP core, the SIP database may be provided by the VAL service provider.
Access to the data residing in the SIP database is restricted to the SIP core entities that are specifically serving the subscriber/user whose data are stored, i.e. registrars and registrar finders can access SIP databases only when they are part of the same trust domain for the data being provided.
NOTE: The SIP database can be in a different network than the registrar finder since the trust domain for the criteria for registrar selection can be different than the trust domain for the signalling plane user identities.
The SIP database is responsible for storing the following user related information:
- signalling plane user identities: Numbering and addressing information;
- signalling plane security information: SIP core access control information for authentication and authorization;
- VAL UE Location information at inter-system level: the SIP database supports the user registration, and stores inter-system location information, etc.; and
- signalling plane subscription profile (including initial filter criteria).
The SIP database also generates signalling plane security information for mutual authentication, communication integrity check and ciphering.
Based on this information, the SIP database is also responsible to support the call control and session management entities of the SIP core.
The SIP database consists of the following functionalities:
- support for control functions of the SIP core such as the Registrar and Registrar finder. This is needed to enable subscriber usage of the SIP core services. This functionality is independent of the access network used to access the SIP core; and
- authentication functionality required by the SIP core to authenticate the VAL UE.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.2.2 SIP database logical functions
|
The SIP database provides the following logical functions:
a) mobility management;
- provides the UE mobility through the SIP core.
b) registrar assignment support;
- provides to the registrar finder the required capabilities for VAL services based on VAL service provider requirements on a per-user basis, (e.g. whether a particular registrar within the PLMN operator's network (e.g. a registrar reserved for VAL service use or a registrar in a secure location) or a registrar within the VAL service provider network is assigned.
c) call and/or session establishment support;
- provides the call and/or session establishment procedures in the SIP core. For terminating traffic, it provides information on which registrar currently hosts the user.
d) user security information generation;
- provides generation of user authentication, integrity and ciphering data for the SIP core.
e) signalling plane security support;
- provides authentication procedures to access VAL services by storing the generated data for authentication, integrity and ciphering at the signalling plane and by providing these data to the appropriate registrar.
f) user identification handling;
- provides the appropriate relations among all the identifiers uniquely determining the signalling plane identities in the SIP core e.g. IMS public identities.
g) access authorisation; and
- provides authorisation of the user for mobile access when requested by the registrar e.g. by checking that the user is allowed to roam to that visited network.
h) service authorisation support.
- provides basic authorisation for terminating call/session establishment and service invocation. The SIP database may update the registrar with filter criteria to trigger the VAL server(s).
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.3 HTTP entities
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.3.1 HTTP client
|
This functional entity acts as the client for all hypertext transactions.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.3.2 HTTP proxy
|
This functional entity acts as a proxy for hypertext transactions between the HTTP client and one or more HTTP servers. The HTTP proxy terminates a TLS session on HTTP-1 with the HTTP client of the VAL UE allowing the HTTP client to establish a single TLS session for hypertext transactions with multiple HTTP servers that are reachable by the HTTP proxy.
The HTTP proxy terminates the HTTP-3 reference point that lies between different HTTP proxies. It may provide a topology hiding function from HTTP entities outside the trust domain of the VAL system.
The HTTP proxy shall be in the same trust domain as the HTTP clients and HTTP servers that are located within a VAL service provider's network. There can be multiple instances of an HTTP proxy e.g. one per trust domain.
NOTE: The number of instances of the HTTP proxy is deployment specific.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.3.3 HTTP server
|
This functional entity acts as the HTTP server for all hypertext transactions.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.4 LWP entities
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.4.1 LWP client
|
This functional entity acts as the light-weight protocol client for all transactions of the SEAL client executing in a constrained UE. A SEAL client executing in an unconstrained UE may choose to use the LWP client if it is available.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.4.2 LWP proxy
|
This functional entity acts as a proxy for transactions between the LWP client and one or more LWP servers. The LWP proxy typically terminates a secure transport protocol (e.g. DTLS, TLS or secure WebSocket) session on LWP-1 reference point with the LWP client of the VAL UE allowing the LWP client to establish a single secure session for transactions with multiple LWP servers that are reachable by the LWP proxy.
The LWP proxy can act as a cross-protocol LWP-HTTP proxy to enable LWP clients to access resources on HTTP servers via the LWP-HTTP-2 reference point.
The LWP proxy terminates LWP-3 reference point that lies between different LWP proxies. It may provide a topology hiding function from LWP entities outside the trust domain of the VAL system.
The LWP proxy can also terminate LWP-HTTP-3 reference point for interworking with another HTTP proxy. In this role it provides cross-protocol mapping and may provide a topology hiding function from HTTP entities outside the trust domain of the VAL system.
The LWP proxy shall be in the same trust domain as the LWP clients and LWP servers that are located within a VAL service provider's network. There can be multiple instances of a LWP proxy e.g. one per trust domain.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.4.3 LWP server
|
This functional entity acts as the LWP server for all LWP transactions of the SEAL server.
NOTE: A SEAL client can act as LWP server for certain transactions as required by the SEAL service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.4.3.5 LWP usage
|
LWP is a generic representation of a light-weight protocol for use in constrained environments. Realizations of the light-weight protocol (LWP) functional entities and reference points to a particular protocol are defined in the annexes of this specification.
LWP is a representation of a protocol to be used by the SEAL service enablers on their respective SEAL-UU reference points when the SEAL client is executing in a constrained UE. In this case the SEAL client should use the LWP-1 reference point with the LWP proxy and should use either the LWP-2 or the LWP-HTTP-2 reference point for transport and routing of the related signalling with the SEAL server.
A SEAL client executing in a non-constrained UE may choose to use the LWP-1 reference point with the LWP proxy and may use either the LWP-2 or the LWP-HTTP-2 reference point for transport and routing of the related signalling with the SEAL server.
LWP may be used for interactions between SEAL servers on their respective SEAL-E reference points. For this usage the SEAL-E reference point shall use the LWP-1 and either the LWP-2 or the LWP-3 reference point depending on the trust relationship between the interacting SEAL servers.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.