Content for TS 23.542 Word version: 18.4.0

0… 5… 8… 8.3… 8.4… 8.5… 8.5.3… 8.5.4… 8.5.7… 8.5.8… 8.5.9… 8.5.10… 8.5.11… 8.5.12… 8.5.13… 8.5.14… 8.6… 8.7… 8.8… 8.9… 8.10… A…

8.5.7 PIN discovery 8.5.7.1 General 8.5.7.2 Procedure 8.5.7.2.1 Procedures of PIN discovery based on PEMC 8.5.7.2.2 Procedures of PIN discovery with assistance of PIN server via PEGC 8.5.7.3 Information flows 8.5.7.3.1 General 8.5.7.3.2 PIN discovery request 8.5.7.3.3 PIN discovery response
...

8.5.7 PIN discovery p. 52

8.5.7.1 General p. 52

Before the PINE trigger the PINE join into the PIN, the PINE should discover the available PIN.

For a certain PIN element, the PIN should be discovered and the PIN element can decide whether to join in the PIN. There are two situations that the PIN elements can discover the PIN as following:

If the PIN elements can have an application layer communication with the PEMC which manages a PIN, the PIN elements can receive the PIN ID, PIN description and the PIN service that a PIN can provide, and decides whether to join the PIN;
The PEGC can be set as open access and the PIN element can communicate with PIN server to receive the PIN ID, PIN description and the PIN service that a PIN can provide from PIN server via the PEGC.

8.5.7.2 Procedure p. 52

8.5.7.2.1 Procedures of PIN discovery based on PEMC p. 52

Pre-conditions:

The UE Identifier or PIN client Identifier is available;
The PIN client has been authorized to communicate with the PEMC;
The UE or PIN client has already received the role of PEMC from PIN server;
The PIN element has already had an application layer connection with a PEMC which manages a PIN.

Reproduction of 3GPP TS 23.542, Fig. 8.5.7.2.1-1: Procedures of PIN discovery based on PEMC

Figure 8.5.7.2.1-1: Procedures of PIN discovery based on PEMC

Step 1.

The PIN client sends the PIN discovery request to PEMC. The PIN discovery request includes the security credentials of the UE or PIN client and may include the UE identifier such as GPSI if available, PIN client ID, UE location, Security credentials, the service that PINE wants to consume.

Step 2.

The PEMC performs an authorization check to verify whether PINE is allowed to perform the operation.

Step 3.

The PEMC sends the PIN discovery response to PIN element including the configuration information of the PIN(s), which are offering the services requested by the PINE in the PIN discovery request. The configuration information includes PIN ID, PIN description (Human-readable description of the PIN, for example, the company name, location or the type of service), services that each PIN can provide and the PEMC IP address.

The PIN client receives the configuration information and decides whether to join in the PIN.

If the PIN element has already had a communication connection with the PEMC, which managements of a PIN, the PIN element can receive the PIN ID, PIN description information and IP address of PEMC and decides whether to join the PIN.

8.5.7.2.2 Procedures of PIN discovery with assistance of PIN server via PEGC p. 53

Some of the PIN elements can have the application layer connection with the PEGC, for example, via WiFi or Bluetooth, and the PIN element can have the communication with PIN server to receive the lists of PIN ID and corresponding PIN description information. And the PIN elements can decide whether to join in the PIN.

Figure 8.5.7.2.2-1 illustrates PIN server discovery via PEGC based on request/response model.

Pre-conditions:

The PIN elements or PIN client has application layer connection with PEGC;
The UE Identifier or PIN client Identifier is available;
The PEGC has been authorized to communicate with the PIN server;
The PIN element has already had an application layer connection with a PEGC, and the PEGC can route the PIN discovery request to PIN server.
The PINE has already received the PIN server IP address.

Reproduction of 3GPP TS 23.542, Fig. 8.5.7.2.2-1: PIN discovery based on PIN server

Figure 8.5.7.2.2-1: PIN discovery based on PIN server

Step 1.

The PIN client sends the PIN discovery request to PIN server via PEGC. The PEGC routes the PIN discovery request to PIN server. The PIN discovery request includes the security credentials of the UE or PIN client and may include the UE identifier such as GPSI, PIN client ID, UE location, Security credentials, the service that PINE wants to consume.

The PIN client can have the filter information in the PIN discovery request for example, the interesting area, the interesting type of PIN and etc.

Step 2.

Upon receiving the request, the PIN server performs an authorization check to verify whether the PIN client has authorization to perform the operation.

The PIN server can decide the candidate PINs according to the filter information from PIN discovery request and the PIN Profile. The PIN server may determine the PIN which the PIN profile accords with the filter information in PIN discovery request. The candidate PINs can be multiple.

Step 3.

The PIN server sends a successful PIN discovery response to PIN client via PEGC, which includes the configuration information to PIN elements. The configuration includes PIN ID, PIN description (Human-readable description of the PIN, for example, the company name, location or the type of service), services that each PIN can provide and the corresponding PEMC IP address.

8.5.7.3 Information flows p. 54

8.5.7.3.1 General p. 54

The following information flows are specified for PIN discovery:

PIN discovery request and response;

8.5.7.3.2 PIN discovery request p. 54

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

Table 8.5.7.3.2-1: PIN discovery request

Information element	Status	Description
UE identifier	M	The identifier of the hosting UE (i.e. GPSI or identity token) of PINE.
Security credentials	M	Security credentials resulting from a successful authorization for the PIN service.
UE location	O	The location information of the UE. The UE location is described in clause 7.2.7.
Filter information	O	Set of characteristics to determine required PIN.
> Requested PIN service	O	Indicate the service that PINE wants to consume in the PIN.
> Service area	O	Indicate the service area of a PIN.

8.5.7.3.3 PIN discovery response p. 55

Table 8.5.7.3.3-1 describes information elements in the PIN discovery response from the PEMC/PIN server to PINE.

Table 8.5.7.3.3-1: PIN discovery response

Information element	Status	Description
Successful response	O (see NOTE)	Indicates that the PIN discovery request was successful.
> PIN IDs	M	Identifier of the candidate PIN.
>> PIN Description	O	Human-readable description of the PIN, for example, the company name, location or the type of service.
>> PIN service	O	List of service that a PIN can provide, including the services provided by PINE or the service that can provided by application client on PINE: > PIN service Provider Identifier > PIN service type > PIN service Feature
>> PEMC information	O	Including the address or identifier of PEMC.
Failure response	O (see NOTE)	Indicates that the PIN discovery request failed.
> Cause	M	Provides the cause for PIN discovery request failure.
NOTE: At least one of the IE shall be present.