8.7 Service Switch

23.5423GPPApplication layer support for Personal IoT NetworkRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.7.1 General

PIN service switch procedures enable an Application Client participating in a PIN or CPN to transfer its application session(s) to a different Application Client participating in the same PIN or CPN. For example, an Application Client located on a UE can transfer a video streaming session to an Application Client located on a television.

PIN service switch can be implemented following two defined scenarios: PIN service switch with PIN server support or PIN service switch without PIN Server support using only internal PIN communication.

8.7.2 Procedure

8.7.2.1 Service switch in a PIN with PIN server support

8.7.2.1.1 General

Following procedures are supported for service switch in a PIN with PIN server support:

– PIN Service Switch procedure;

– PIN Configure Service Switch procedure;

8.7.2.1.1 PIN Service Switch procedure

Pre-conditions:

1. The PIN Client established an application session with an Application Server;

2. The PIN Client joined a PIN.

Figure 8.7.2.1.1-1: PIN Service Switch procedure

1. The PIN Client sends a PIN Service Switch request to the PIN Server. The PIN Service Switch request includes the requestor identifier [PIN Client ID], security credential, a PIN identifier [PIN ID], an Application Client identifier [ACID], an Application Server identifier, an application session identifier, can include an IP 4 tuple that describes the traffic of the application session and can include a target PIN Client [PIN Client ID] if a target is known.

2. Upon receiving the request from the PIN Client, the PIN Server checks if the PIN Client is authorized to request service switching for the given Application Server and validates the request. If the request is authorized and valid, the PIN server can determine a target PIN Client if the target PIN Client was not included in the request. The PIN Server sends a PIN Configure Service Switch request to the PIN Management Client and the Application Server as in clause 8.7.2.1.2. The PIN Server can use the PIN ID to identify the PIN Management Client instance and the Application Server identifier, or IP 4 tuple, to identify the Application Server instance.

3. If the processing of the request was successful, the PIN Server sends a PIN Service Switch response to the PIN Client that indicates the Service Swich request was successfully processed and can include the target PIN Client information if it was decided by the PIN Server. Otherwise, the PIN Server sends a PIN Service Switch response to the PIN Client indicating that the request processing failed and can include appropriate reasons.

Upon reciving the PIN Service Switch response, the PIN Client validates if the request was succesful and can indicate the result to the Application Client; the PIN Client can transfer the application context to the target PIN Client. If the PIN Service Switch response indicated a failure, the PIN Client can attempt perform service switch again for the same or a different target PIN Client considering the failure reason.

8.7.2.1.2 PIN Service Switch Configure procedure

Pre-conditions:

1. The PIN Client successfully requested a service switch with the PIN Server

Figure 8.7.2.1.2-1: PIN Configure Service Switch procedure

1. The PIN Server sends the PIN Configuration Service Switch Configure request to the PIN Management Client or Application Server. The PIN Configuration Service Switch Configure request includes the requestor identifier, security credential, Application Client identifier, Application Server identifier, target PIN Client, application session identifier and can include IP 4 tuple that descibes the traffic of the application session.

NOTE 1: The PIN Server first performs PIN Configure Service Switch procedure with the PIN Management Client, then if successful, with the Application Server.

2. Upon receiving the request from the PIN Server, the PIN Management Client or the Application Server checks if the PIN Server is authorized to request service switch configuration and validates the request.

If the request was recevied at the Application Server, if the request is authorized and valid, the Application Server uses the information provided in the request to switch the application session to the target PIN client and proceeds to step 6 of the procedure.

If the request was recevied at the the PIN Management Client, if the request is authorized and valid, the PIN Management Client prepares for sending PIN Configure Service Switch request to the PIN Gateway Client or the target PIN Client. The PIN Management Client can use the PIN ID to identify the PIN Gateway Client instance and the target PIN Client identifier to identify the target PIN Client.

3. The PIN Management Client sends the PIN Management Service Switch Configure request to the PIN Gateway Client or the target PIN Client including the information defined in step 1.

NOTE 2: The PIN Management Client first performs PIN Configure Service Switch procedure with the PIN Gateway Client, then if successful, with the target PIN Client.

4. Upon receiving the request from the PIN Management Client, the PIN Gateway Client or the target PIN Client checks if the PIN Managment Client is authorized to request service switch configuration and validates the request. If the PIN Management Client is authorized and the request is valid, the PIN Gateway Client or the target PIN Client use the information provided in the request to switch the application session to the target PIN Client.

NOTE 3: The target Application Client needs to receive the application context prior to re-establishing a switched application session with the Application Server.

NOTE 4: How the target Application Client recovers the switched application session is out of scope of this specification.

5. If the processing of the request was successful, the PIN Gateway Client or the target PIN Client send a PIN management Service Switch Configure response to the PIN Management Client indicating the processing was successful. Otherwise, the PIN Gateway Client or target PIN Client send a PIN Management Service Switch Configure response to the PIN Management Client indicating that processing the request failed and can include appropriate reasons.

6. If the processing of the request was successful, the PIN Management Client or Application Server send a PIN Configuration Service Switch Configure response to the PIN Server that indicates the request was successfully processed. Otherwise, the PIN Management Client or Application Server send a PIN Configuration Service Switch Configure response to the PIN Server indicating the processing the request failed and can include appropriate reasons.