Content for &nbsp; TS 23.542 &nbsp; Word version:&nbsp; 18.4.0

The PINE sends an AS discovery request to the PEMC. The AS discovery request includes the requestor identifier, security credentials of the PINE and the AS service identifier of a service associated with an AS.

Upon receiving the request, the PEMC checks if the requestor is authorized to request AS discovery, and if the request is authorized, the PEMC verifies if it has information on an AS providing associated with the requested AS service identifier. If the PEMC identifies information about an AS providing the requested service, the PEMC proceeds to step 6.

Figure 8.8.2.3-1: AS registration procedure

If the PEMC has not identified an AS in step 2, the PEMC sends an AS discovery request to the PIN Server. The AS discovery request includes the requestor identifier, security credentials of the PEMC and the AS service identifier associated with an AS.

Step 4.

Upon receiving the request, the PJN Server checks if the requestor is authorized to request AS discovery, and if the request is authorized, the PIN Server verifies if it has information on an AS providing associated with the requested AS service identifier.

Step 5.

If the processing of the request was successful, the PIN Server sends an AS discovery response to the requestor indicating successful processing and includes connectivity information to the AS. If the request processing failed, the PIN Server indicates failure and may provide a failure reason.

Step 6.

If the processing of the request was successful in step 2 or the PEMC has received a successful response from the PIN Server in step 5, the PEMC sends an AS discovery response to the requestor indicating successful processing and includes connectivity information to the discovered AS. If the request processing failed, the PEMC indicates failure and may provide a failure reason.

Upon receiving the AS discovery response from the PEMC, if the response indicates success, the PINE (e.g., PIN Client) may provide the AS connectivity information to the AC so the AC can access the AS. If the response indicates failure, the PINE may retry AS discovery considering the failure reason.

8.8.2.3 AS registration p. 106

Figure 8.8.2.3-1 illustrates the AS registration procedure between the AS and the PEMC or PIN Server. This procedure enables the AS to provide AS connectivity information to the PEMC or the PIN Server.

Pre-conditions:

The AS is authorized to communicate with the PEMC or the PIN Server;

Reproduction of 3GPP TS 23.542, Fig. 8.8.2.3-1: AS registration procedure

The AS sends an AS registration request to the PEMC or PIN Server. The AS registration request includes the requestor identifier, security credentials of the AS, the AS service identifier of the service associated with the AS, the connectivity information of the AS.

Upon receiving the request, the PEMC or PIN Server checks if the requestor is authorized to request AS registration, and if the request is authorized, the PEMC or PIN Server stores information associated with AS service.

Figure 8.8.2.4-1: AS registration update procedure

If the processing of the request was successful, the PEMC or PIN Server sends an AS registration response to the requestor indicating successful processing and include the AS registration identifier; the response may include an expiration time to indicate to the AS when the registration will automatically expire. To maintain the registration, the AS shall send a registration update request prior to the expiration time. If a registration update request is not received prior to the expiration time, the PEMC or PIN Server shall treat the AS as implicitly de-registered. If the request processing failed, the PEMC or PIN Server indicates failure and may provide a failure reason.

Upon receiving the AS registration response from the PEMC, if the response indicates success, the AS stores the registration identifier and may reuse it to update or delete its registration to the PEMC or PIN Server. If the response indicates failure, the AS may retry AS registration considering the failure reason.

8.8.2.4 AS registration update p. 107

Pre-conditions:

The AS has registered with the PEMC or PIN Server;
The AS has determined that its existing registration needs to be updated;

Reproduction of 3GPP TS 23.542, Fig. 8.8.2.4-1: AS registration update procedure

The AS sends an AS registration update request to the PEMC or PIN Server where it registered. The request shall include the AS registration identifier and may include registration information such as the AS service identifier and AS connectivity information.

The PEMC or PIN Server performs an authorization check to verify whether the requestor is authorized to request AS registration update for the provided AS registration identifier; if the request is authorized and the AS registration identifier is valid, the PEMC or PIN Server update the registration information associated with the AS registration identifier.

Figure 8.8.2.5-1: AS de-registration procedure

If the request processing is successful, the PEMC or PIN Server replies to the AS with an AS registration update response and may include an updated expiration time to indicate to the AS when the updated registration will automatically expire. To maintain the registration, the AS shall send a registration update request prior to the expiration time. If a registration update request is not received prior to the expiration time, the PEMC or PIN Server shall treat the AS as implicitly de-registered. If the request processing failed, the PEMC or PIN Server indicates failure and may provide a failure reason.

8.8.2.5 AS de-registration p. 107

Pre-conditions:

The AS has registered with the PEMC or PIN Server;
The AS has determined that de-registration is required;

Reproduction of 3GPP TS 23.542, Fig. 8.8.2.5-1: AS de-registration procedure

The AS sends an AS de-registration request to the PEMC or PIN Server where it registered. The request shall include the AS registration identifier.

The PEMC or PIN Server performs an authorization check to verify whether the requestor is authorized to request AS de-registration for the provided AS registration identifier; if the request is authorized and the AS registration identifier is valid, the PEMC or PIN Server removes the registration information associated with the AS registration identifier.