8.9 Service Continuity

23.5423GPPApplication layer support for Personal IoT NetworkRelease 18TS

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

8.9.1 General

PIN service continuity procedures enable an Application Client participating in a PIN or CPN to maintain service when PIN Elements enter or leave the PIN. The following examples illustrate scenarios where PIN service continuity is needed; in a first scenario, an Application Client located in a UE needs to receive data from another PIN Element located in the home when the Ue leaves home; in a second scenario, an Application Clients communicating via a PIN Gateway Client needs to maintain communication when the PIN Gateway becomes unreacheable.

PIN service continuity can be implemented following two defined scenarios: PIN service continuity in PIN Gateway Client relocation and PIN service continuity in changing access to 5GS.

8.9.2 Procedure

8.9.2.1 Service continuity in PEGC relocation scenario

8.9.2.1.1 General

Following procedures are supported for service continuity in a PEGC relocation scenario:

– PIN Management PEGC Service Continuity procedure;

– PIN Management PEGC Configuration procedure;

– PIN Configuration Update procedure; and

8.9.2.1.2 PIN Management PEGC Service Continuity procedure

Pre-conditions:

1. PIN Element has an application session that goes through a PIN Gateway Client; and

2. PIN Gateway Client needs to be replaced (e.g., PEGC will become unavailable or PEGC is unreachable).

Figure 8.9.2.1.2-1: PIN PEGC Service Continuity procedure

1. The PIN Gateway Client or the PIN Client sends a PIN Management PEGC Service Continuity request to the PIN Management Client for a specific service. The PIN Management PEGC Service Continuity request includes security credentials, PIN Client identifier(s), PIN Gateway identifier, and Service identifier.

2 Upon receiving the request, the PIN Management Client validates the request and checks if the request is authorized for the given PIN Client(s), PIN Gateway Client and service. If the request is authorized and valid, the PIN Management Client determines if a target PIN Gateway Client meets the requirements for handling the application traffic for the provided service.

If the PIN Management Client identifes a target PIN Gateway Client that meets the requirements, the PIN Management Client sends PIN Management PEGC Configuration request to the target PIN Gateway Client to configure the target PIN Gateway for handling service traffic from the PIN Client(s) as in clause 8.9.2.1.3. If the service is provided by an Application Server, the PIN Management Client send a PIN Configuration Update request to the PIN Server if needed to inform of the service continuity changes in the PIN as in clause 8.9.2.1.4.

3. If the procesing of the request was successful, the PIN Management Client sends a PIN Management PEGC Service Continuity response to indicate that the request processing was successfull and includes target PIN Gateway Client information. Otherwise, the PIN Management Client sends a PIN PEGC Service Continuity response indicating that the request processing failed and can include appropriate reasons.

Upon receiving the PIN Management PEGC Service Continuity response, if the response was received by the PIN Client, the PIN Client validates if the request was successful and can inform the application client of the target PIN Gateway Client provided in the response to establish connectivity. If the response was received by the PIN Gateway Client, the PIN Gateway Client notifies each PIN Client included in the PIN Management PEGC Service Continuity request about the target PIN Gateway Client change as in clause 8.9.2.1.5.

8.9.2.1.3 PIN Management PEGC Configuration procedure

Pre-conditions:

1. The PIN Management Client has received a PIN Management PEGC Service Continuity request; and

2. The PIN Management client has identified a target PIN Gateway Client.

Figure 8.9.2.1.3-1: PIN Management PEGC Configuration procedure

1. The PIN Management Client sends a PIN Management PEGC Configuration request to the target PIN Gateway Client. The PIN Management PEGC Configuration request includes security credentials, PIN Client identifier(s), PIN Gateway identifier, and Service identifier.

2. Upon receiving the request, the PIN Gateway Client validates the request and checks if the PIN Management Client is authorized to request PEGC Configuration. If the request is authorized and the request is valid, the PIN Gateway Client creates a new configuration for the PIN Client(s) and service that are indicated in the request.

3. If the processing of the request was successful, the target PIN Gateway Client sends a PIN Management PEGC Configuration response to the PIN Management Client to indicate that the request was successful and can include connectivity information to be used by the PIN Client(s). Otherwise, the target PIN Gateway sends a PIN Management PEGC Configuration response indicating that the request failed and can include appropriate reasons.

Upon receiving the PIN Management PEGC Configuration response, the PIN Management Client uses the information provided in the response to inform the PIN Client(s) or the PIN Gateway Client from which the service continuity request originated as in clause 8.9.2.1.2.

8.9.2.1.4 PIN Configuration Update procedure

Pre-conditions:

1. PIN Element has an application session that goes through a PIN Gateway Client; and

2. PIN Gateway Client needs to be replaced (e.g., PEGC will become unavailable or PEGC is unreachable).

Figure 8.9.2.1.4-1: PIN Configuration Update procedure

1. The PIN Management Client sends a PIN Configuration Update request to the PIN Server. The PIN Configuration Update request includes security credentials, service continuity information, PIN Client identifier(s), PIN Gateway identifier, and Service identifier.

2. Upon receiving the request, the PIN Server validates the request and checks if the PIN Management Client is authorized to request service continuity update. If the request is authorized and valid, the PIN Server updates the configuration for the PIN Client(s) and service indicated in the request. The PIN Server can update the Application Server accordingly if needed.

3. If the processing of the request was successful, the target PIN Server sends a PIN Configuration Update response to indicate that the request processing was successful. Otherwise, the PIN Server sends a PIN Configuration Update response indicating that the request processing failed and can include appropriate reasons.

Upon receiving the PIN Configuration Update response, the PIN Management Client uses the information provided in the response to inform the PIN Client(s) or the PIN Gateway Client from which the service continuity request originated as in clause 8.9.2.1.2.

8.9.2.2 Service continuity in changing access to 5GS

8.9.3 Information flows

Editor’s note: Information flows definition for Service Continuity is FFS

8.9.4 APIs

Editor’s note: API definition for Service Continuity is FFS

Annex A (informative):
Change history

Change history
Date	Meeting	TDoc	CR	Rev	Cat	Subject/Comment	New version
2023-01	SA6#52bis-e					TS skeleton (version 0.0.0) approved in S6-230388.	0.0.0
2023-01	SA6#52bis-e					Implementation of the following pCRs approved by SA6: S6-230081, S6-230082, S6-230083, S6-230118, S6-230121, S6-230124, S6-230126, S6-230184, S6-230185, S6-230300, S6-230369, S6-230370, S6-230381, S6-230384, S6-230386, S6-230387, S6-230388, S6-230487, S6-230488, S6-230489, S6-230490, S6-230491, S6-230492,	0.1.0

3GPP TS 23.542 V0.1.0 (2023-01)

Technical Specification

3^rd Generation Partnership Project;

Technical Specification Group Services and System Aspects;

Application layer support for Personal IoT Network;

(Release 18)

The present document has been developed within the 3rd Generation Partnership Project (3GPP^TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPPOrganizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPPonly. The Organizational Partners accept no liability for any use of this Specification.
Specifications and Reports for implementation of the 3GPP^TM system should be obtained via the 3GPP Organizational Partners’ Publications Offices.

3GPP

Postal address

3GPP support office address

650 Route des Lucioles – Sophia Antipolis

Valbonne – FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Intpp.org

Copyright Notification

No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

UMTS™ is a Trade Mark of ETSI registered for the benefit of its members

3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners

GSM® and the GSM logo are registered and owned by the GSM Association

Contents

Foreword 7

Introduction 7

1 Scope 8

2 References 8

3 Definitions of terms, symbols and abbreviations 8

3.1 Terms 8

3.2 Symbols 9

3.3 Abbreviations 9

4 Overview 9

4.1 General 9

5 Architectural requirements 9

5.1 General 9

5.2 Architectural requirements 9

5.2.1 General requirements 9

5.2.1.1 General 9

5.2.1.2 Requirements 9

5.2.2 PIN Management 10

5.2.2.1 General 10

5.2.2.2 Requirements 10

5.2.3 PIN enable 5GS communication 10

5.2.3.1 General 10

5.2.3.2 Requirements 10

5.2.4 Service Switch 10

5.2.4.1 General 10

5.2.4.2 Requirements 10

5.2.5 Application server discovery 11

5.2.5.1 General 11

5.2.5.2 Requirements 11

5.2.6 Service continuity 11

5.2.6.1 General 11

5.2.6.2 Requirements 11

5.2.7 Security 11

5.2.7.1 General 11

5.2.7.2 Requirements 11

5.2.7 Subscription service 11

5.2.7.1 General 11

5.2.7.2 Requirements 11

5.2.8 PIN application KPIs 11

5.2.8.1 General 11

5.2.8.2 Requirements 11

6 Application layer architecture 12

6.1 General 12

6.2 Architecture 12

6.2.1 General Architecture 12

6.2.2 Architecture of user accessing services provided by PIN Element from outside the PIN 12

6.3 Functional entities 13

6.3.1 General 13

6.3.2 PIN client 13

6.3.3 PIN Management Client 14

6.3.4 PIN Gateway Client 14

6.3.5 PIN server 15

6.3.6 Application Client 15

6.4 Reference Points 15

6.4.1 General 15

6.4.2 PIN-1 15

6.4.3 PIN-2 15

6.4.4 PIN-3 15

6.4.5 PIN-4 16

6.4.6 PIN-5 16

6.4.7 PIN-6 16

6.4.8 PIN-7 16

6.4.9 PIN-8 16

6.4.10 PIN-9 16

6.4.11 PIN-10 16

6.4.12 PIN-11 16

6.4.13 PIN-12 17

6.5 Cardinality rules 17

6.5.1 Application Client (AC) 17

6.5.2 PEMC 17

6.5.3 PEGC 17

6.5.4 PIN server 17

6.5.5 PIN client 17

7 Identities and commonly used values 17

7.1 General 17

7.2 Identities 17

7.2.1 General 17

7.2.2 PIN ID 17

7.2.3 PIN server ID 17

7.2.4 PIN client ID 18

7.2.5 Application Client ID (ACID) 18

7.2.6 UE ID 18

7.2.7 UE Location 18

8 Procedures and information flows 18

8.1 General 18

8.2 Common Information Elements 18

8.2.1 General 18

8.2.2 PIN Profile 18

8.2.2.1 PIN Profile in a PIN 18

8.2.2.2 Dynamic profile information of a PIN 19

8.2.2.3 PIN client profile 21

8.2.3 PIN Application KPIs 21

8.3 PIN server discovery 21

8.3.1 General 21

8.3.2 Procedure 22

8.3.2.1 Static PIN server discovery 22

8.3.2.2 Procedures of PIN server discovery via PEGC 22

8.3.3 Information flows 23

8.3.3.1 General 23

8.3.3.2 PIN server discovery request 23

8.3.3.3 PIN server discovery response 23

8.4 Registration 23

8.4.1 General 23

8.4.2 Registration Procedure 24

8.4.2.1 General 24

8.4.2.2 Procedure 24

8.4.2.2.1 PINE registration directly to PIN server 24

8.4.2.2.2 PINE registration indirectly to PIN server 25

8.4.2.2.3 PINE registration via PEGC before join 26

8.4.2.2.4 PINE registration during the PIN join via the PEGC 26

8.4.2.3 Information flow/elements 27

8.4.2.3.1 General 27

8.4.2.3.2 PINE Registration request 27

8.4.2.3.3 PINE Registration response 28

8.5 PIN Management 28

8.5.1 General 28

8.5.2 PIN Create 28

8.5.2.1 General 28

8.5.2.2 Procedure 28

8.5.2.3 Information flows 30

8.5.3 PIN delete 32

8.5.3.1 General 32

8.5.3.2 Procedure 32

8.5.3.2.1 PIN delete procedure decided by PIN server 32

8.5.3.2.2 PEMC decided PIN deletion 33

8.5.3.3 Information flows 34

8.5.3.3.1 General 34

8.5.3.3.2 PIN delete request 34

8.5.3.3.3 PIN delete response 35

8.5.3.3.4 PIN delete notification request 35

8.5.3.3.5 PIN delete notification response 35

8.5.4 Multiple PEMCs/PEGCs 35

8.5.4.1 General 35

8.5.4.2 Procedure 35

8.5.4.3 Information flows 37

8.5.4.3.1 General 37

8.5.4.3.2 PIN management PINE Join into PIN request enhancements. 37

8.5.4.3.3 PIN management PINE Join into PIN response enhancements. 37

8.5.4.3.4 PEGC_notification 37

8.5.5 PIN Profile Recovery 38

8.5.5.1 General 38

8.5.5.2 Procedure 38

8.5.5.3 Information flows 38

8.5.6 Credential Provision 38

8.5.6.1 General 38

8.5.6.2 Procedure 38

8.5.6.3 Information flows 38

8.5.7 PIN discovery 38

8.5.7.1 General 38

8.5.7.2 Procedure 38

8.5.7.3 Information flows 38

8.5.8 PINE management 38

8.5.8.1 General 38

8.5.8.2 Procedure 39

8.5.8.2.1 PIN client requests to join into a PIN 39

8.5.8.2.2 Procedure of PIN elements decides to leave the PIN 40

8.5.8.2.3 Procedure of PEMC removes the PIN elements from a PIN 41

8.5.8.3 Information flows 42

8.5.9 PIN join 42

8.5.9.1 General 42

8.5.9.2 Procedure 42

8.5.9.2.1 PINE join via PEGC 42

8.5.10 PIN modification 43

8.5.10.1 General 43

8.5.10.2 Procedures 43

8.5.10.2.1 General 43

8.5.10.2.2 PIN modification after local PEMC failure 43

8.5.10.2.3 PIN modification with PEGC role change 44

8.6 PIN enable 5GS communication 47

8.6.1 General 47

8.6.2 Procedure 47

8.6.2.1 AF trigger QoS establishment 47

8.6.2.2 Procedures of PIN communication via 5GS triggered by PEGC 47

8.6.3 Information flows 47

8.7 Service Switch 47

8.7.1 General 47

8.7.2 Procedure 47

8.7.2.1 Service switch in a PIN with PIN server support 47

8.7.2.1.1 General 47

8.7.2.1.1 PIN Service Switch procedure 47

8.7.2.1.2 PIN Service Switch Configure procedure 48

8.7.2.2 Service switch in a PIN without PIN server support 50

8.7.3 Information flows 50

8.7.4 APIs 50

8.8 Application server discovery in PIN 50

8.8.1 General 50

8.8.2 Procedure 50

8.8.3 Information flows 50

8.9 Service Continuity 50

8.9.1 General 50

8.9.2 Procedure 51

8.9.2.1 Service continuity in PEGC relocation scenario 51

8.9.2.1.1 General 51

8.9.2.1.2 PIN Management PEGC Service Continuity procedure 51

8.9.2.1.3 PIN Management PEGC Configuration procedure 52

8.9.2.1.4 PIN Configuration Update procedure 52

8.9.2.2 Service continuity in changing access to 5GS 53

8.9.3 Information flows 53

8.9.4 APIs 53

Annex A: Change history 54