Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.437  Word version:  19.0.0

Top   Top   Up   Prev   Next
0…   7…   8…   8.3…   8.4…   8.5…   9…   9.3…   9.4…   9.5…   9.6…   9.7…

 

9.6  SM service capable application server (SMAS)p. 61

9.6.1  Generalp. 61

This clause enables VAL server with SM capability to register with SEAL SM server in order to provide SM services.

9.6.2  SMAS registrationp. 61

9.6.2.1  Generalp. 61

The SMAS registration procedure registers the authorized VAL server with SM capability with SEAL SM server.

9.6.2.2  Procedurep. 61

Figure 9.6.2.2-1 depicts the procedure for an authorized VAL server with SM capabilities to register a SMAS with the SEAL SM server.
Pre-conditions:
  1. The VAL server has received information (e.g. URI, IP address) related to the SEAL SM server;
  2. The VAL server has received security credentials authorizing it to communicate with the SEAL SM server.
Copy of original 3GPP image for 3GPP TS 23.437, Fig. 9.6.2.2-1: SMAS registration procedure
Figure 9.6.2.2-1: SMAS registration procedure
(⇒ copy of original 3GPP image)
Up
Step 1.
The VAL server sends a SMAS registration request to the SEAL SM server. The request includes a requestor ID, security credentials, and a SMAS profile including SM service information (e.g., endpoint, availability period, availability location) and spatial map information (e.g., identifier, coverage area, civic address, latest update time).
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 SMAS profile that was provided in the request.
Step 3.
The SEAL SM server sends a SMAS registration response to the VAL server. If the SEAL SM server successfully stored the SMAS profile, the response includes an indication of success, the registration identifier and may include a proposed expiration time for the registration. Otherwise, the response includes an indication of failure and may include a reason for failure.
Up

9.6.2.3  Information flowsp. 62

9.6.2.3.1  SMAS registration requestp. 62
Table 9.6.2.3.1-1 describes information elements in the SMAS registration request from the VAL server to the SEAL SM server.
Information element Status Description
Requestor IDMThe identifier of the requestor (e.g., VAL server).
Security credentialsMThe security credentials of the requestor.
Proposed expiration timeOProposed expiration time for the registration.
SMAS profileO The SMAS profile as described in Table 9.6.2.3.1-2.
Table 9.6.2.3.1-2 describes information elements in the SMAS profile.
Information element Status Description
SMAS informationMThe information about the SM service; each element includes the information described below.
> EndpointOThe endpoint information (e.g. URI, FQDN, IP address) used to communicate with the SM Service.
> Availability periodOThe time period when a service consumer can access the SM service.
> Availability locationOThe location where a service consumer can access the service from.
List of spatial map informationMThe information about spatial map(s) available at the SM service; each spatial map of the list includes the information described below.
> IdentifierMThe identifier of a spatial map.
> Coverage areaMThe spatial coverage area of a spatial map.
Up
9.6.2.3.2  SMAS registration responsep. 63
Table 9.6.2.3.2-1 describes information elements in the SMAS registration response from the SEAL SM server to the VAL server.
Information element Status Description
Successful responseOIndicates that the registration request was successful.
> Registration IDMIdentifier of the registration.
> Expiration timeOIndicates 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 responseOIndicates that the request failed.
> CauseOIndicates the cause of the failure.
Up

9.6.3  SMAS registration updatep. 63

9.6.3.1  Generalp. 63

The SMAS registration update procedure updates registration status of the authorized VAL server with SM capability to the SEAL SM server.

9.6.3.2  Procedurep. 63

Figure 9.6.3.2-1 depicts the procedure for an authorized VAL server to update SMAS information.
Pre-conditions:
  1. The VAL server has already registered the SM service with the SEAL SM server.
Copy of original 3GPP image for 3GPP TS 23.437, Fig. 9.6.3.2-1: SMAS registration update procedure
Figure 9.6.3.2-1: SMAS registration update procedure
(⇒ copy of original 3GPP image)
Up
Step 1.
The VAL server sends a SMAS registration update request to the SEAL SM server. The request includes a requestor ID, security credentials, a registration ID, and may include an updated SMAS profile and 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 SMAS profile based on the request information.
Step 3.
The SEAL SM server sends the SMAS registration update response to the VAL server. If the SEAL SM server successfully updated the SMAS profile, the response includes an indication of success and may include a proposed expiration time for the registration. Otherwise, the response includes an indication of failure and may include a reason for failure.
Up

9.6.3.3  Information flowsp. 64

9.6.3.3.1  SMAS registration update requestp. 64
Table 9.6.3.3.1-1 describes information elements in the SMAS registration update request from the VAL server to the SEAL SM server.
Information element Status Description
Requestor IDMThe identifier of the requestor (e.g., VAL server).
Security credentialsMThe security credentials of the requestor.
Registration IDMIdentifier of the registration.
Proposed expiration time (NOTE)OProposed expiration time for the registration.
SMAS profile (NOTE)O The SMAS profile as described in Table 9.6.2.3.1-2.
NOTE:
At least one of the IEs is included.
Up
9.6.3.3.2  SMAS registration update responsep. 64
Table 9.6.3.3.2-1 describes information elements in the SMAS registration update response from the SEAL SM server to the VAL server.
Information element Status Description
Successful responseOIndicates that the registration update request was successful.
> Expiration timeOIndicates 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 responseOIndicates that the request failed.
> CauseOIndicates the cause of the failure.
Up

9.6.4  SMAS deregistrationp. 65

9.6.4.1  Generalp. 65

The SMAS deregistration procedure deregisters the authorized VAL server with SM capability from the SEAL SM server.

9.6.4.2  Procedurep. 65

Figure 9.6.4.2-1 depicts the procedure for an authorized VAL server to deregister a SMAS.
Pre-conditions:
  1. The VAL server has already registered the SM service with the SEAL SM server.
Copy of original 3GPP image for 3GPP TS 23.437, Fig. 9.6.4.2-1: SMAS deregistration procedure
Figure 9.6.4.2-1: SMAS deregistration procedure
(⇒ copy of original 3GPP image)
Up
Step 1.
The VAL server sends a SMAS 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 SMAS registration and removes the stored SMAS profile.
Step 3.
The SEAL SM server sends the SMAS deregistration response to the VAL server. If the SEAL SM server successfully deregistered the SMAS, the response includes an indication of success. Otherwise, the response includes an indication of failure and may include a reason for failure.
Up

9.6.4.3  Information flowsp. 66

9.6.4.3.1  SMAS deregistration requestp. 66
Table 9.6.4.3.1-1 describes information elements in the SMAS deregistration request from the VAL server to the SEAL SM server.
Information element Status Description
Requestor IDMThe identifier of the requestor (e.g., VAL server).
Requestor security credentialsMThe security credentials of the requestor.
Registration IDMIdentifier of the registration.
Up
9.6.4.3.2  SMAS deregistration requestp. 66
Table 9.6.4.3.2-1 describes information elements in the SMAS deregistration response sent from the SEAL SM server to the VAL server.
Information element Status Description
Successful responseOIndicates that the deregistration request was successful.
Failure responseOIndicates that the request failed.
> CauseOIndicates the cause of the failure.
Up

9.6.5  SMAS discoveryp. 66


Up   Top   ToC