Content for  TS 23.542  Word version:  18.4.0

The PEMC sends a PIN creation request to the PIN server in order to create a PIN. The PIN creation request includes the security credentials of the UE or PINE-1 received during authorization procedure and may include the UE identifier such as GPSI, PIN client ID, UE location and PIN client profile(s) information. The PEMC can request to create a PIN including the details of other PIN elements (list of PINEs) that has already established connection with it. The details of the PIN elements could be for example, UE identifier such as GPSI, PIN client ID, UE location and PIN client profile(s) information. If there are no other PIN elements in the request, the PEMC requests to create a PIN including itself. In order to save the procedure of several PEMCs to be involved into the certain PIN as individual PEMC, the PEMC can have the additional PEMC GPSIs/PIN client ID in the PIN create request, to indicate additional PEMCs that are allowed to manage the PIN. This procedure doesn't have conflict with that other PEMC requests to join the certain PIN and becomes PEMC separately. The PEMC creates the PIN profile and delivers the PIN profile to PIN server. The PIN creation request also includes service that PINE can provide.

Upon receiving the request, the PIN server performs an authorization check to verify whether the PEMC (PINE 1) has authorization to perform the PIN creation operation.

The PIN server sends a successful PIN creation response to PEMC, which includes a newly assigned PIN ID to indicate the PIN. It also includes the list of PIN elements and their identifier which are authorized and made as member of the newly created PIN if the PIN creation request contains the list of PIN elements to be included in the PIN. If the PIN creation request fails, the PIN server should give the failure response indicating the cause of PIN creation request failure. The member of newly created PIN may include PEMC and (optional) the list of PIN elements which are authorized to be added into the PIN by PIN server. If there are no other PIN elements in the PIN creation request and the PIN creation is successful, the PIN server indicates the PEMC to be the PEGC. The PEMC who has already had the role of PEMC can also has the role of PEGC. The PIN server may determine the list of candidates PEGCs for this PIN according to the gateway capability provided by PINE during PINE registration procedure. Only the PINE that has the capability of gateway can be selected as the PEGCs for this PIN. If no PEGCs are available for this PIN, the PIN server initiates PIN create response with PIN creation failure to PEMC. If the one or more PEGCs are indicated in the PIN creation response, the PIN server indicates the PIN client ID/GPSI of one PINE to be the PEGC. Also, the assigned IP address or port number is delivered in the PIN creation response to PEMC. And, the PIN Server also sends the PEGC information about access control in the response, including:

• Access control information includes: user name, account, SSID, BSSID. All the information is used by PIN elements in PIN to access 5G or access other application outside of PIN;
  The PIN server or PEMC can decide the access control information in certain PEGC.
• If the access control information decided by PIN server, the PIN server sends the access control information to PEMC via PIN creation response. And the PEMC delivers the access control information to PEGC via PIN creation notification request.
• If the access control information decided by PEMC, the PEMC delivers the access control information to PEGC via PIN creation notification request.

It is possible for PIN server to indicate several devices as PEGCs in a PIN. And it is possible for PIN server to indicate the PEGC and PEMC is the same device in a PIN. The PIN server may update the PIN profile and delivers the updated PIN profile to PEMC.

[Optional] If the PIN creation response contains the list of PIN elements, the PEMC generates the PIN creation notification request to individual PINEs based on the list received in step 3. This notification request includes the PIN ID of the newly created PIN and also contains an indication that the PIN element is made the member of the newly created PIN. During this step, the PEMC may distribute the Access control information to PINE, to be used by PIN elements in PIN to access 5G or access other application outside of PIN. The updated the PIN profile may be synchronized to PEGC or PINEs.

[Optional] The individual PIN elements sends the PIN creation notification response to acknowledge the receipt of the notification. The PIN elements receiving the PIN creation notification request with joined indication shall not join the PIN by issuing the PIN join request since they are already made as the member of the PIN.