6 Application layer architecture
23.5423GPPApplication layer support for Personal IoT NetworkRelease 18TS
6.1 General
6.2 Architecture
6.2.1 General Architecture
Figure 6.2.1-1 illustrates the reference point representation of the architecture for PINAPP.
Figure 6.2.1-1: PINAPP architecture
The PIN elements contains PIN client and/or application clients. The PIN Element with gateway capability (PEGC) performs the role of an entity supporting gateway capability for PIN. The PIN Element with management capability (PEMC) performs the role of an entity supporting management capability for PIN.
NOTE 1: It is possible that an application client on PIN elements can communicate with application server directly via 5GS or indirectly via PEGC.
NOTE 2: It is possible that an application client can communicate with other application client in the same PIN directly or via PEGC.
NOTE 3: It is possible that an application client can communicate with other application client in another PIN via PEGC.
NOTE 4: There is no restrict that only one PEMC/PEGC deployed in PIN. It is possible that in a PIN, multiple PEMCs/PEGCs are deployed.
Editor’s note: Whether PIN-5 is in the scope of PINAPP is FFS.
6.2.2 Architecture of user accessing services provided by PIN Element from outside the PIN
The Figure 6.2.2-1 shows the application architecture to enable authorized user to access services provided by PIN element behind the PEGC. For simplicity, not all functional elements of Figure 6.2.2-1 are shown in below Figure 6.2.2-1.
Figure 6.2.2-1: PINAPP architecture of User accessing services provided by PIN Element from outside the PIN
The interactions between PEGC and PIN client of the authorized user are supported over interface PIN-11. The interactions between PEMC and PIN client of the authorized user are supported over interface PIN-12. The authorized user uses PIN-12 to configure the policies in a PIN.
NOTE1: The authorized user is allowed to manage a PIN due to authorized user has PIN-12 interface to communicate with PEMC.
6.3 Functional entities
6.3.1 General
6.3.2 PIN client
The PIN enabler layer entity residing in the PIN elements that provides the client side functionalities required for application clients in order to consume the services offered by the PIN or to offer services for other PIN elements to consume.
It provides the following functionalities:
– Registration of the available service and capabilities;
– Service discovery of other PIN elements and application server;
– Communication with PIN clients of other PIN elements;
– Selection of relay for direct communication;
– Maintaining the PIN profile;
– Perform to join/leave a PIN;
– Support to discover the available PIN; and
– Support to receive the information to access the 5G core network via PEGC.
– Support service switch internal PIN.
– Support PIN service continuity of PEGC relocation or changing to 5GS communication.
6.3.3 PIN Management Client
A PIN Element with Management Capability is a PIN Element that provides a means for an authorised administrator to configure and manage a PIN.
It provides following functionalities:
– For a network operator or authorized user to configure the policies of the PIN;
– Provide life span information of the PIN to the authorized user or the PIN elements;
– Maintain the list of PIN elements who joined the PIN. Maintaining available PIN services;
– Maintain the PIN profile for each PIN and PINE in PIN;
– To configure and manage a PIN, including:
– authorizing the PIN elements requesting to join the PIN;
– authorizing the PEGC and configure the parameters in PEGC to support PINE communication (via 5GS or direct communication);
– configuring PIN elements to enable discovery of services offered by other PIN Elements;
– add PIN elements to the PIN;
– configure PIN elements to enable direct communications;
– configure PIN elements to communicate with each other when gateway device is unavailable.
– support the PIN server endpoint address delivery to PIN elements;
– support the credentials delivery to PIN elements;
NOTE: When gateway device is unavailable, the configurations are required to enable direct communication.
– Support service switch internal PIN.
– Support PIN service continuity of PEGC relocation or changing to 5GS communication.
6.3.4 PIN Gateway Client
A PIN Element with Gateway Capability is a PIN Element PIN Element that has the ability to provide connectivity to and from the 5G network for other PIN Elements.
It provides the following functionalities:
– Maintain the PIN profile for each PIN and PINE in PIN;
– Maintain the access control information for each PIN and each PINE in PIN;
– Support to trigger the PDU session modification towards 5GS to request the resource for PIN;
– Enable the 5GS communication or direct communication;
– Support to PIN server address delivery;
– Support to deliver the credentials to PINE;
– Support PIN discovery function
– Support service switch internal PIN.
– Support PIN service continuity of PEGC relocation or changing to 5GS communication.
– Relay functionality for other PIN elements;
6.3.5 PIN server
A PIN server is deployed at network that provides server side functionalities required for managing the PIN.
It provides the following functionalities:
– Provisioning of configuration information to the PIN elements;
– Maintain the PIN profile for each PIN and PINE in PIN;
– PIN Management (Creation, modification and deletion) of PIN;
– Determine the access control information of PEGC/PINE in PIN;
– Authorization of the PINE to be added/removed into/from the PIN
– Support PIN discovery and application server discovery
– Support service switch internal PIN.
– Support PIN service continuity of PEGC relocation or changing to 5GS communication.
6.3.6 Application Client
An application client is the application resident in the PIN elements.
6.4 Reference Points
6.4.1 General
Editor’s note: Some of the reference points should be coordinated with the related PIN procedure, and will be supplied the details of interface function in the following meeting.
6.4.2 PIN-1
The interactions related to enabling PINAPP, between the Application client and the PIN client.
6.4.3 PIN-2
This reference point exists between PIN client and PEGC which connects PIN client of UE to PEGC. The PIN client uses this interface to communicate with other PIN clients within PIN or to access 3GPP network.
6.4.4 PIN-3
This reference point exists between the PIN client and PEMC and following functionalities are supported over this reference point:
– Authorizing PIN clients to access PIN;
– Discovery of services offered byother PIN elements;
– Discovery and selection of relay PIN elements;
– Notifying the PIN information modification details (e.g. PEMC change, PEGC change, PIN capabilities change).
6.4.5 PIN-4
This reference point exists between the PEGC and PEMC and following functionalities are supported over this reference point:
– Authorizing PEGC for PIN access;
– Notification of PIN elements joining or leaving the PIN by PEMC to PEGC;
– Delivery of PIN dynamic profile information by PEMC to PEGC whenever it changes;
6.4.6 PIN-5
This reference point exists between the one PIN client and another PIN client and it supports direct connection over 3GPP or non-3GPP RAT. It also connects to PIN client of a PIN element to the PIN client of another PIN element acting as a relay.
Editor’s note: It is FFS that whether the PIN-5 should be standardized in PINAPP.
6.4.7 PIN-6
This reference point exists between the PEMC and PIN server and supports the following functionalities:
– Authorization of PEMC;
– Notifying PIN server whenever a PIN element joins or leaves the PIN, whenever a PIN client updates its capabilities;
– Notifying PIN server of PEGC replacement;
– Delivery of PIN dynamic profile information;
6.4.8 PIN-7
This reference point exists between the PEGC and PIN server for the interactions related to enabling PINAPP
6.4.9 PIN-8
This reference point exists between the PIN server and 3GPP core network for the interactions related to enabling PINAPP
6.4.10 PIN-9
This reference point exists between the application server and PIN server for the interactions related to enabling PINAPP.
6.4.11 PIN-10
This reference point exists between the PIN client in PIN element and PIN server for the interactions related to enabling PINAPP.
6.4.12 PIN-11
This reference point exists between the PEGC and PIN client from outside the PIN to access the services provided by PIN elements within the PIN.
PIN-11 utilizes Uu reference point as described in 3GPP TS 23.501[4].
6.4.13 PIN-12
This reference point exists between the PEMC and PIN client for configuring and managing the PIN from outside the PIN.
PIN-12 utilizes Uu reference point as described in 3GPP TS 23.501[5].