5 Architectural requirements

23.5423GPPApplication layer support for Personal IoT NetworkRelease 18TS

5.1 General

5.2 Architectural requirements

5.2.1 General requirements

5.2.1.1 General

This clause specifies general requirements for the architecture.

5.2.1.2 Requirements

[AR-5.2.1.2-a] The application layer architecture shall support deployment of personal IoT network.

[AR-5.2.1.2-b] The application layer architecture shall support different deployment models in conjunction with an operator’s 3GPP network.

[AR-5.2.1.2-c] The application layer architecture shall be compatible with the 3GPP network system.

5.2.2 PIN Management

5.2.2.1 General

This clause specifies PIN management requirements for the architecture.

5.2.2.2 Requirements

[AR-5.2.2.2-a] The application layer architecture shall provide mechanisms to create PIN for UE or PIN elements.

[AR-5.2.2.2-b] The application layer architecture shall provide mechanisms to delete PIN, either triggered by PINEs or by PIN server.

[AR-5.2.2.2-c] The application layer architecture shall support the mechanisms of PIN modification procdure, for example, PEMC/PEGC relocation.

[AR-5.2.2.2-d] The application layer architecture shall support the deployment and mechanism of multiple PEMCs/PEGCs.

[AR-5.2.2.2-e] The application layer architecture shall support mechanisms to obtain PIN server endpoint address.

[AR-5.2.2.2-f] The application layer architecture shall support the mechanisms to perform PIN discovery, and enable the PINEs to join/leave the PIN.

[AR-5.2.2.2-g] The application layer architecture shall support the mechanisms of PINE registration to PIN server.

[AR-5.2.2.2-h] The application layer architecture shall support mechanisms to maintain, configure, update the PIN profile/PIN client profile.

5.2.3 PIN enable 5GS communication

5.2.3.1 General

This clause specifies PIN communication requirements for the architecture.

5.2.3.2 Requirements

[AR-5.2.3.2-a] The application layer architecture shall provide mechanisms to configure routing information in PEGC to enable the PINE to access the network provided by PEGC.

[AR-5.2.3.2-b] The application layer architecture shall provide mechanisms to support the PIN and the PINEs in PIN to consume the 5GS communication.

[AR-5.2.3.2-c] The application layer architecture shall provide mechanisms to support the PEMC/PEGC to request the 5GS resource for PIN.

5.2.4 Service Switch

5.2.4.1 General

This clause specifies service switch requirements for the architecture.

5.2.4.2 Requirements

[AR-5.2.4.2-a] The application layer architecture shall provide mechanisms to support the service switching in a PIN between different PINE for achieving better service experience.

5.2.5 Application server discovery

5.2.5.1 General

This clause specifies application server discovery requirements for the architecture.

5.2.5.2 Requirements

[AR-5.2.5.2-a] The application layer architecture shall provide mechanisms to support the application server discovery for PIN.

5.2.6 Service continuity

5.2.6.1 General

This clause specifies service continuity requirements for the architecture.

5.2.6.2 Requirements

[AR-5.2.6.2-a] The application layer architecture shall provide mechanisms to support the PEGC relocation procedure to enable service continuity.

[AR-5.2.6.2-b] The application layer architecture shall provide mechanisms to change the communication from via PEGC to via 5GS, and enable the service continuity.

5.2.7 Security

5.2.7.1 General

5.2.7.2 Requirements

5.2.7 Subscription service

5.2.7.1 General

5.2.7.2 Requirements

5.2.8 PIN application KPIs

5.2.8.1 General

5.2.8.2 Requirements