8.3 PIN server discovery

23.5423GPPApplication layer support for Personal IoT NetworkRelease 18TS

8.3.1 General

Some of the PIN management procedures needs the PIN server to help. So, the PINE should receive the PIN server endpoint address first and then trigger the other following procedure, for example, the PIN creation procedure.

Due to the PIN server in a PLMN can be multiple, so it is important to PIN elements to discover the appropriate PIN server to connect.

8.3.2 Procedure

8.3.2.1 Static PIN server discovery

The aim of PIN server discovery procedure is to receive one or more endpoint information (e.g. URI(s), FQDN(s), IP address(es)) of PIN server. And the PEMC, PEGC, PIN elements are all able to receive the PIN server endpoint information.

The PIN server can be discovered by the following method:

– pre-configured in the PIN elements or PIN clients;

– configured by the user;

– derived from HPLMN identifier for non-roaming scenario or from VPLMN identifier for roaming scenario.

8.3.2.2 Procedures of PIN server discovery via PEGC

Due to for some of the PIN elements can have the application interaction towards the PEGC, for example, via WiFi or Bluetooth pairing, so the PEGC can provide the PIN server end point information to PIN elements.

For some of the PEGC, it has the open access capability to accept the application layer connection from the PIN elements.

Pre-conditions:

1. The PIN elements or PIN client has application layer connection with PEGC;

2. The UE Identifier or PIN client Identifier is available;

3. The PEGC supports the open access and can reroute the request from PINE to PEMC behind the PEGC;

Figure 8.3.2.2-1: Procedures of PIN server discovery via PEGC

0. The PINE has already had the application layer connection towards PEGC. For example, the PIN elements can communicate with PEGC via WiFi or Bluetooth.

The PINE can also have the open access to PEGC that with no user name or password. For this situation, the PINE can’t consume the communication service that provided by PEGC, but can have communication with the PEMC behind the PEGC.

1. The PINE sends PIN server discovery request to PEGC. The requests include the GPSI, MAC address, if has, UE location.

2. (Optional) The PEGC can directly deliver the PIN server discovery response to PINE, including PIN server end point information to PIN elements. The end point information of PIN server includes URI(s), FQDN(s), IP address(es)) of PIN server.

3. If the PINE has open access to PEGC, that the PEGC should route the PIN server discovery request to PEMC that behind the PEGC.

4-5. The PEMC delivers the PIN server discovery response to PEGC and the PEGC routes the response to PINE, including PIN server end point information to PIN elements. The end point information of PIN server includes URI(s), FQDN(s), IP address(es)) of PIN server.

8.3.3 Information flows

8.3.3.1 General

The following information flows are specified for PIN creation:

– PIN server discovery request and response;

8.3.3.2 PIN server discovery request

Table 8.3.3.2-1 describes information elements in the PIN discovery request from the PINE to the PEGC/PEMC.

Table 8.3.3.2-1: PIN server discovery request

Information element	Status	Description
UE Identifier	M	The identifier of the hosting UE (i.e. GPSI or identity token) or PINE.
MAC address	O	MAC address of the device.
UE location	O	The location information of the UE. The UE location is described in clause x.x.x.

8.3.3.3 PIN server discovery response

Table 8.3.3.3-1: PIN server discovery response

Information element	Status	Description
Successful response	O	Indicates that the PIN creation request was successful.
> PIN server endpoint information	M	Includes URI(s), FQDN(s), IP address(es)) of PIN server.
Failure response	O	Indicates that the PIN creation request failed.
> Cause	M	Provides the cause for PIN creation request failure.