Content for TS 23.437 Word version: 20.1.0
9.5 SM data source
9.5.1 General
9.5.2 SM data source registration
9.5.3 SM data source registration update
9.5.4 SM data source deregistration
9.5.5 SM data source discovery
9.5.6 SM data source subscription
...
...
9.5 SM data source p. 69
9.5.1 General p. 69
This clause provides registration related procedures for SM data source.
9.5.2 SM data source registration p. 69
9.5.2.1 General p. 69
The SM data source registration procedure registers the authorized SM information data source with SEAL SM server.
9.5.2.2 Procedure p. 69
Figure 9.5.2.2-1 depicts the procedure for an authorized VAL client, via a SEAL SM client, to register as a SM data source with the SEAL SM server.
Pre-conditions:
- The SEAL SM client has received information (e.g. URI, IP address) related to the SEAL SM server;
- The SEAL SM client has received security credentials authorizing it to communicate with the SEAL SM server.
Step 1.
The SEAL SM client sends a SM data source registration request to the SEAL SM server. The request includes a requestor ID, security credentials, SEAL SM client notification endpoint and a SM data source profile including SM information details (e.g., provider identifier, type, position, state). The request may include UE identifier, VAL client identifier, Proposed expiration time. The SM data source profile may also include data source update interval information to support the different needs for frequency of the data source and the mobility information (like fixed or low or high mobility). When real-time data is needed (such as autonomous driving, drones, etc.) a different update interval can be used than for the fixed cases (e.g., in industrial setting).
Step 2.
Upon receiving the request, the SEAL SM server validates if the requestor is authorized for the request. If the requestor is authorized, the SEAL SM server assigns a unique identifier for the registration and stores the SM data source profile provided in the request.
Step 3.
The SEAL SM server sends a SM data source registration response to the SEAL SM client. If the SEAL SM server successfully stored the SM data source profile, the response includes an indication of success, the registration identifier and may include an expiration time for the registration. Otherwise, the response includes an indication of failure and may include a reason for failure.
9.5.2.3 Information flows p. 70
9.5.2.3.1 SM data source registration request p. 70
Table 9.5.2.3.1-1 describes information elements in the SM data source registration request from the SEAL SM client to the SEAL SM server.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identifier of the requestor (e.g., VAL User or VAL UE). |
| Security credentials | M | The security credentials of the requestor. |
| Proposed expiration time | O | Proposed expiration time for the registration. |
| UE ID | O | The identifier of the hosting UE (i.e., GPSI). |
| VAL client ID | O | The identifier of the VAL client. |
| Notification endpoint | M | The endpoint for notifying the SM data source about a SM information request. |
| SM data source profile | M | The SM data source profile of the registering SM data source as described in Table 7.3.3.2-1. |
9.5.2.3.2 SM data source registration response p. 70
Table 9.5.2.3.2-1 describes information elements in the SM data source registration response from the SEAL SM server to the SEAL SM client.
| Information element | Status | Description |
|---|---|---|
| Successful response | O | Indicates that the registration request was successful. |
| > Registration ID | M | Identifier of the registration. |
| > Expiration time | O | Indicates the expiration time of the registration. To maintain an active registration status, a registration update is required before the expiration time. If the Expiration time IE is not included, it indicates that the registration never expires. |
| Failure response | O | Indicates that the registration request failed. |
| > Cause | O | Indicates the cause of registration request failure. |
9.5.3 SM data source registration update p. 71
9.5.3.1 General p. 71
The SM data source registration update procedure updates registration status of the authorized SM information data source to the SEAL SM server.
9.5.3.2 Procedure p. 71
Figure 9.5.3.2-1 depicts the procedure for an authorized VAL client, via a SEAL SM client, to update a registered SM data source information.
Pre-conditions:
- The SEAL SM client has successfully registered the SM data source with the SEAL SM server.
Step 1.
The SEAL SM client sends a SM data source registration update request to the SEAL SM server. The request includes a requestor ID, security credentials, a registration ID, and may include an updated SM data source profile and a proposed expiration time for the updated registration.
Step 2.
Upon receiving the request, the SEAL SM server validates if the requestor is authorized for the request. If the requestor is authorized, the SEAL SM server updates the SM data source profile based on the request information.
Step 3.
The SEAL SM server sends the SM data source registration update response to the SEAL SM client. If the SEAL SM server successfully updated the SM data source profile, the response includes an indication of success. Otherwise, the response includes an indication of failure and may include a reason for failure.
9.5.3.3 Information flows p. 72
9.5.3.3.1 SM data source registration update request p. 72
Table 9.5.3.3.1-1 describes information elements in the SM data source registration update request from the SEAL SM client to the SEAL SM server.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identifier of the requestor (e.g., VAL User or VAL UE). |
| Security credentials | M | The security credentials of the requestor. |
| Registration ID | M | Identifier of the registration. |
| Proposed expiration time (NOTE) | O | Proposed expiration time for the registration. |
| Updated SM data source profile (NOTE) | O | The SM data source profile, as described in Table 7.3.3.2-1, with updated SM information details. Included only if there is an update in SM information details. |
|
NOTE:
At least one of the IEs is included.
|
||
9.5.3.3.2 SM data source registration update response p. 72
Table 9.5.3.3.2-1 describes information elements in the SM data source registration update response from the SEAL SM server to the SEAL SM client.
| Information element | Status | Description |
|---|---|---|
| Successful response | O | Indicates that the registration update request was successful. |
| > Expiration time | O | Indicates the expiration time of the updated registration. To maintain an active registration status, a registration update is required before the expiration time. If the Expiration time IE is not included, it indicates that the updated registration never expires. |
| Failure response | O | Indicates that the request failed. |
| > Cause | O | Indicates the cause of the failure. |
9.5.4 SM data source deregistration p. 72
9.5.4.1 General p. 72
The SM data source deregistration procedure deregisters the authorized SM information data source from the SEAL SM server.
9.5.4.2 Procedure p. 72
Figure 9.5.4.2-1 depicts the procedure for an authorized SEAL SM client to deregister a SM data source.
Pre-conditions:
- The SEAL SM client has already registered the SM data source with the SEAL SM server.
Step 1.
The SEAL SM client sends a SM data source deregistration request to the SEAL SM server. The request includes a requestor ID, security credentials, and a registration ID.
Step 2.
Upon receiving the request, the SEAL SM server validates if the requestor is authorized for the request. If the requestor is authorized, the SEAL SM server ends the SM data source registration and removes the stored SM data source profile.
Step 3.
The SEAL SM server sends the SM data source deregistration response to the SEAL SM client. If the SEAL SM server successfully deregistered the SEAL SM client, the response includes an indication of success. Otherwise, the response includes an indication of failure and may include a reason for failure.
9.5.4.3 Information flows p. 73
9.5.4.3.1 SM data source deregistration request p. 73
Table 9.5.4.3.1-1 describes information elements in the SM data source deregistration request from the SEAL SM client to the SEAL SM server.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identifier of the requestor (e.g., VAL User or VAL UE). |
| Security credentials | M | The security credentials of the requestor. |
| Registration ID | M | Identifier of the registration. |
9.5.4.3.2 SM data source deregistration response p. 73
Table 9.5.4.3.2-1 describes information elements in the SM data source deregistration response from the SEAL SM server to the SEAL SM client.
| Information element | Status | Description |
|---|---|---|
| Successful response | O | Indicates that the deregistration request was successful. |
| Failure response | O | Indicates that the request failed. |
| > Cause | O | Indicates the cause of the failure. |
9.5.5 SM data source discovery p. 74
9.5.5.1 General p. 74
The SM data source discovery procedure allows VAL server to discover the authorized SM information data sources from the SEAL SM server.
9.5.5.2 Procedure p. 74
Figure 9.5.5.2-1 depicts the procedure for an authorized VAL server to discover SM data source(s).
Pre-conditions:
- The VAL server has received information (e.g. URI, IP address) related to the SEAL SM server;
- The VAL server has received security credentials authorizing it to communicate with the SEAL SM server.
Step 1.
The requestor (e.g, VAL server or SEAL server) sends a SM data source discovery request to the SEAL SM server. The request includes a requestor ID, security credentials, and may include discovery filters and endpoint information for receiving spatial mapping information from discovered SM data sources. Discovery filters inlcude the area of interest (e.g., three-dimensional area, localization information, availability, data source update interval, mobility information) and requirements on spatial mapping information as defined in clause 9.5.5.3.1.
Step 2.
The SEAL SM server authorizes the requestor and validates the request. If the request is authorized, the SEAL SM server determines one or more registered SM data source(s) according to the discovery filters.
The SEAL SM server evaluates if the SM data source location is in accordance with the area of interest included in the discovery request to determine the SM data source(s). The SEAL SM server can obtain UE location information and velocity information from the 3GPP core network by invoking the 3GPP Core Network Location Services exposed by the NEF as described in TS 23.273 and TS 23.502, or by invoking the SEAL Location Management APIs as described in TS 23.434.
Step 3.
The SEAL SM server sends a SM data source notification to trigger the determined SEAL SM client(s) to send spatial mapping information. The notification includes details about the requested spatial mapping information and endpoint information for sending the spatial mapping information to the requestor. The SEAL SM client provides the information included in the notification to the VAL client that will send the spatial mapping information.
Step 4.
The SEAL SM server sends a SM data source discovery response to the requestor. The response includes information about SM data source(s) when at least one SM data source has been determined. If no SM information provided was determined, the SEAL SM server sends a failure indication with a reason for failure.
9.5.5.3 Information flows p. 75
9.5.5.3.1 SM data source discovery request p. 75
Table 9.5.5.3.1-1 describes information elements in the SM data source discovery request from the VAL server to the SEAL SM server.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identifier of the requestor (e.g., VAL server). |
| M | The security credentials of the requestor. | |
| SM data reporting endpoint | O | The endpoint information where the triggered spatial mapping data source sends the SM data. |
| Discovery filters | O | Set of characteristics to determine SM data source(s) in the area of interest. |
| > Area of interest | O | Three-dimensional area of interest or localization information to discover SM data source(s) in the area. |
| > SM information details | O | The SM information details to match. |
| >> SM data identifier | O | The identifier of SM information. |
| >> SM data type (NOTE) | O | The type of SM information (e.g., LiDAR camera, RGB-D camera, high-resolution cameras, etc.) that is provided by the application layer. |
| >> SM data format | O | The format of a SM information (e.g., raw, processed, etc.). |
| >> Position information | O | Indicates the Three dimensional area of interest or location information of the SM data source. |
| >> Availability State information | O | Indicates the time period availability information of the SM data source. |
| >> Data source update interval information | O | Indicates the rate at which data source updates or generates the data. It describes how often the new data is captured or collected. e.g., every x milliseconds generates data. |
| >> Mobility information | O | Indicates the mobility information of the SM data source.e.g., fixed, low or high mobility. |
|
NOTE:
The definition of SM data types is application specific (e.g., VAL client) for the current release.
|
||
9.5.5.3.2 SM data source discovery response p. 75
Table 9.5.5.3.2-1 describes information elements in the SM data source discovery response from the SEAL SM server to the SM data source consumer (e.g., VAL server or SEAL server).
| Information element | Status | Description |
|---|---|---|
| Successful response | O | Indicates that the discovery request was successful. |
| > SM data source profiles | O | The list of SM data source profiles as described in Table 7.3.3.2-1. |
| Failure response | O | Indicates that the request failed. |
| > Cause | O | Indicates the cause of the failure. |
9.5.5.3.3 SM data source notification p. 75
Table 9.5.5.3.3-1 shows the notification sent by a SEAL SM server to a SEAL SM client for triggering a spatial mapping information session from a SM data source.
| Information element | Status | Description |
|---|---|---|
| Requestor identifier | M | The identifier of the requestor (e.g., SEAL SM server, VAL server). |
| Security credentials | M | The security credentials of the requestor. |
| SM data source ID | M | The identifier of the SM data source. |
| SM information reporting session | M | The characteristics of SM information reporting session. |
| > SM data identifier | M | The identifier of spatial SM data to report. |
| > SM data type (NOTE) | O | The type of SM information data to report. (e.g., LiDAR camera, RGB-D camera, high-resolution cameras, etc.) that is provided by the application layer. |
| > SM data format | O | The format of a SM information data to report. (e.g., raw, processed, etc.). |
| > SM duration | O | The duration for which the SM data is reported. |
| > SM frequency | O | The frequency at which the SM data is reported. |
| > SM endpoint | M | The endpoint where to report the SM data. |
|
NOTE:
The definition of SM data types is application specific (e.g., VAL client) for the current release.
|
||
9.5.6 SM data source subscription |R20| p. 76
9.5.6.1 General p. 76
SM data source subscription enables VAL server or SEAL server to subscribe to the SM server to get the updates related to changes in SM data sources and data source profiles.
9.5.6.2 Procedures p. 76
9.5.6.2.1 Subscribe SM data source p. 76
Figure 9.5.6.2.1-1 depicts the procedure for the authorized VAL server or SEAL server to subscribe to the SM server for the the SM data source specific event. VAL server or SEAL server can get notification information when the the SM server detects subscribed event.
Pre-conditions:
- The VAL server or SEAL server has received information (e.g. URI, IP address) related to the SEAL SM server;
- The VAL server or SEAL server has received security credentials authorizing it to communicate with the SEAL SM server.
- The VAL server or SEAL server has already discovered the SM data sources and obtained the SM data source information.
Step 1.
The requestor (e.g., VAL server or SEAL server) sends a SM data source subscription request to the SM server. The request includes requestor ID, security credentials, a notification endpoint, event to subscribe which triggers the notification etc as specified in Table 9.5.6.3.1-1.
Step 2.
Upon receiving the request from the requestor, the SM server validates if the requestor is authorized for the request. If the requestor is authorized, the SM server creates the subscription and stores the subscription information.
Step 3.
- If the subscribed event is for "changes in SM data source(s) profiles", the SM server monitors for updates to the elements of SM data source profile(s) described in Table 7.3.3.2-1 that are associated with the target SM data source(s) provided in the subscription request. The SM server also subscribes to the SEAL Location Management Server services in TS 23.434 or NEF services specified in TS 23.502 to monitor the location of the SM data source. The SM server also monitors updates to the SM data source profile done via the procedure defined in clause 9.5.3.
The SM server sends a SM data source subscription response to the requestor with the indication of success or failure as specified in Table 9.5.6.3.2-1.
9.5.6.2.2 Notify SM data source event p. 77
Figure 9.5.6.2.2-1 depicts the notify spatial map event operation between the authorized SM data source consumer (VAL server or SEAL server) and SEAL SM server.
Step 1.
The SEAL SM server detects an event that triggers the notification to the subscribers for the corresponding event. SM server determines whether the detected event matches triggering criteria and notifies subscribers accordingly.
Step 2.
- If the subscribed event is "changes in SM data source(s) profiles", the SM server detects changes to the SM data source like changes in to the SM data source profile, SM data type, SM data format, SM data area, changes in location, availability state, data source update interval.
The SEAL SM server notifies the VAL servers or SEAL servers which subscribed the corresponding event. The notification includes a subscription ID and event-specific information.
- If the event is "changes in SM data source(s) profiles", the notification message includes the list of all SM data sources identifiers that are updated and the updated elements (e.g. changes in SM data type, SM data format, SM data area, location, availability state, data source update interval).
9.5.6.3 Information flows p. 78
9.5.6.3.1 Subscribe SM data source request p. 78
Table 9.5.6.3.1-1 shows the subscribe SM data source request sent by VAL server or SEAL server to SEAL SM server to subscribe for SM data source event(s).
| Information element | Status | Description |
|---|---|---|
| Requestor identity | M | The identity of the requestor (e.g., VAL server or SEAL server). |
| Security credentials | M | The security credentials of the requestor. |
| Application service ID | M | ID of the requesting VAL application service. |
| Notification Target Address | O | Notification target address (e.g. URL) where the notifications should be sent. |
| Expiry time | O | Proposed subscription expiry time. |
| Target SM data source(s) | M | SM data source(s) to subscribe. |
| > List of SM data source IDs | O | ID(s) of the SM data source(s) to subscribe. |
| > Area of interest | O | Three-dimensional area information to discover SM data source(s) to subscribe. |
| List of events | M | Events to subscribe. Each element includes the information described below. |
| > Event type | O | List of events to subscribed. Possible values are:
|
| > Triggering criteria | O | Specifies the condition to determine whether the event is occurred and to notify the requestor. |
| >> Changes in SM data source profiles | O
(NOTE) | Triggers notification if any or specified element described in Table 7.3.3.2-1 change is detected. |
| > Notification intervals | O | Specifies when to notify the detected event,
Possible values are:
|
| > interval time | O | Time between consecutive notifications (applicable only if notification intervals is set to intervals. |
|
NOTE:
At least one of the sub-elements shall be provided.
|
||
9.5.6.3.2 Subscribe SM data source response p. 78
Table 9.5.6.3.2-1 shows the subscribe SM data source response sent by SEAL SM server to VAL server or SEAL server.
| Information element | Status | Description |
|---|---|---|
| Result | M | Result of the subscribe SM data source event request. |
| Subscription Id (NOTE) | O | Identity of the subscription. |
| Expire time | O | Subscription expire time. |
| Failure cause | O | Indicates reason for the failure. |
|
NOTE:
This IE is mandatory when Result IE indicates success.
|
||
9.5.6.3.3 Notify SM data source event p. 79
Table 9.5.6.3.3-1 shows the SM data source notification sent by SEAL SM server to VAL server or SEAL server to notify about SM data source event(s).
| Information element | Status | Description |
|---|---|---|
| Subscription ID | M | Identifier of the subscription request. |
| Notification information | M | Specifies what matches the triggering notification condition, including related information. |
| Event type | M | Type of event detected. One of the event as specified in Table 9.5.6.3.1-1. |
| Changes of SM data source(s) profile | O
(NOTE) | Indicates list of SM data source ID and information about changes in the SM data source. |
| > SM data source ID | O | Identifier of the SM data source. |
| > SM Data source profile | O | Updated data source profile of the SM data source as specified in clause 7.3.3.2. |
|
NOTE:
This IE includes the list of SM data source ID and the corresponding information if the changes are detected for more than one SM data source.
|
||
