8.5 PIN Management
23.5423GPPApplication layer support for Personal IoT NetworkRelease 18TS
8.5.1 General
8.5.2 PIN Create
8.5.2.1 General
After the UE or PINE acquires the role of PEMC and receives the address of PIN server, the UE or PINE can trigger a creation of PIN towards PIN server.
Below are the possible scenarios when the PEMC request for the creation of PIN:
– No PIN elements or PEGC have established connection with PEMC;
– One or more PIN elements including PEGCs, PEMCs have established connection with PEMC via non-3GPP access. In this case the PEMC can trigger creation of PIN with these PIN elements in group.
After the creation of PIN is accepted by network, the PIN server responds to PEMC containing the details of the PIN including the PIN ID, the PEGC information, access control information configured in PEGC etc.
At the network side, a PIN server should be deployed. The PIN server is responsible for the authorization of the Creation request of PIN, and arranges the PEGC information about access control to PIN.
8.5.2.2 Procedure
8.5.2.2.1 PIN creation procedure
Figure 8.5.2.2.1-1 illustrates PIN creation procedure based on request/response model.
Pre-conditions:
1. The UE or PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
2. The UE Identifier or PIN client Identifier is available;
3. The UE or PINE has already been registered in PIN server;
4. The UE or PINE has been authorized to communicate with the PIN server;
5. PINE 1 is assigned the role of PEMC by PIN server and PINE-2 is the PEGC of the PIN;
Figure 8.5.2.2.1-1: PIN creation procedure
1. 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.
NOTE 1: For a certain PIN, only one PEMC at a time can be assigned with primary role and other PEMCs if any are assigned with secondary role.
2. 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.
Editor’s Note: Whether and how the 5GC involved in the PIN creation depends on the feedback from SA2.
3. 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.
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.
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.
4a-4c. [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.
5a-5c. [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.
After the procedure above, the PINE-1 (PEMC) creates a PIN with PEGC (PINE-2) and other accepted PIN elements in PIN.
8.5.2.3 Information flows
8.5.2.3.1 General
The following information flows are specified for PIN creation:
– PIN creation request and response;
– PIN creation notification request and response;
Editor’s note: A review and update of procedural text and IEs is necessary to ensure that multiple PEMC/PEGCs are supported.
8.5.2.3.2 PIN creation request
Table 8.5.2.3.2-1 describes information elements in the PIN creation request from the PINE/PEGC to the PIN server.
Table 8.5.2.3.2-1: PIN creation request
|
Information element |
Status |
Description |
|
UE Identifier |
M |
The identifier of the hosting UE (i.e. GPSI or identity token) or the PIN client ID of PINE/PEMC |
|
Security credentials |
M |
Security credentials resulting from a successful authorization for the PIN service. |
|
PIN client profile(s) |
O |
Profiles of PIN clients. The PIN client profiles are further described in Table 8.2.2.3. |
|
UE location |
O |
The location information of the UE. The UE location is described in clause 7.2.7. |
|
Lists of PINEs |
O |
The PINEs that has already communicated with PEMC directly, and intend to add these PINE into PIN. |
|
Additional PEMCs |
O |
Indicate additional PEMCs that are allowed to manage the PIN. |
8.5.2.3.3 PIN creation response
Table 8.5.2.3.3-1: PIN creation response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the PIN creation request was successful. |
|
> PIN ID |
M |
Identifier of the newly created PIN. |
|
> Expiration time |
M |
Indicates the expiration time of the PIN. |
|
> Lists of PINEs |
O |
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. |
|
> Identifier of PEGCs |
O |
Indicates the PINE identifier authorized to be the PEGCs of this PIN. |
|
>> PEGC address |
O |
Assigned IP address or port number of PEGC |
|
> PEGC information |
O |
Includes the PEGC information for example, |
|
>> Access control information |
O |
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 |
|
Failure response |
O |
Indicates that the PIN creation request failed. |
|
> Cause |
M |
Provides the cause for PIN creation request failure. |
8.5.2.3.4 PIN creation notification request
Table 8.5.2.3.4-1: PIN creation notification request
|
Information element |
Status |
Description |
|
PIN ID |
M |
Identifier of the newly created PIN. |
|
Indication |
O |
Indicates the PIN element is made the member of the newly created PIN. |
|
> Identifier of PEGCs |
O |
Indicates the PINE identifier that to be the PEGCs of this PIN. |
|
>> PEGC address |
O |
Assigned IP address or port number of PEGC |
|
> PEGC information |
O |
Includes the PEGC information for example, |
|
>> Access control information |
O |
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 |
8.5.2.3.5 PIN creation notification response
Table 8.5.2.3.5-1: PIN creation notification response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the PIN creation notification request was successful. |
|
Failure response |
O |
Indicates that the PIN creation notification request failed. |
|
> Cause |
O |
Indicates the cause of PIN creation notification request failure. |
8.5.3 PIN delete
8.5.3.1 General
The PIN which is in use can be deleted based on the decision by PEMC or PIN server as described below:
– Decided by PEMC. The PEMC of a PIN decides to delete the PIN and sends request to PIN server. The PIN server accepts the request and deletes the PIN.
– Decided by PIN server. If the PIN is configured to exist for a particular duration and if it continues to exist post the duration the PIN server can decide to delete the PIN and release the resources associated with the PIN.
Once the PIN is deleted, the PIN elements in PIN shall not be able to utilize the services by the PIN or 5GS anymore and cannot access the application server. The network resources allocated for this PIN will be released.
Since the configuration related to the duration of the PIN is available with PEMC and when the duration of the PIN expires, the PEMC can directly delete the PIN locally and without having to be authorized by the PIN server. After the PIN is deleted by PEMC, the PEMC can update the status of PIN to the PIN server.
8.5.3.2 Procedure
8.5.3.2.1 PIN delete procedure decided by PIN server
Figure 8.5.3.2.1-1 illustrates PIN delete procedure triggered by PEMC based on request/response model.
Pre-conditions:
1. PIN is successfully created and in use;
2. PEMC of the PIN decides to delete the PIN which could be based on the request from the authorized user or for any other reason which are implementation specific.
Figure 8.5.3.2.2-1: PIN delete procedure triggered by PEMC
1a. The PEMC sends a PIN delete request to the PIN server to request to delete the PIN. The PIN delete request includes the security credentials of the PIN client received during PIN client authorization procedure and PIN ID. The PIN ID identifies the PIN to be deleted.
1b. An event occurs at the PIN server that satisfies the trigger conditions for deleting the PIN. This event could the PIN continues to exist post the expiry of duration associated with it or the PIN server decides to not provide any PIN service in this PIN.
NOTE: The security credentials delivery and the authorization procedure happen at application layer.
2. Upon receiving the request, the PIN server validates the PIN delete request and verifies the security credentials.
3. Upon successful authorization, the PIN server sends a successful PIN delete response to PEMC.
After the PIN is deleted which is indicated by PIN ID, the access control information in PEGC is also disabled and the PIN elements in this PIN cannot access to 5GS via PEGC anymore.
4. When the PIN is deleted, the PEMC sends the PIN delete notification request to the PEGC containing the PIN ID of the deleted PIN.
5. PEMC sends the PIN delete notification request to the PIN elements containing the PIN ID of the deleted PIN.
6. The PEGC sends the PIN delete notification response to acknowledge the receipt of the notification and disables the 5GS connection permission and access control information for the PIN elements in this PIN.
7. The PIN elements in this PIN sends the PIN delete notification response to acknowledge the receipt of the notification. The PIN elements in this PIN can delete the information about this PIN, for example, the PIN profile.
8.5.3.2.2 PEMC decided PIN deletion
The PEMC can directly trigger the PIN delete procedure, for example, when the the duration assicated with the PIN expires, without having to be authorized from PIN server. After the PIN is deleted successfully, the PEMC updates the PIN status to PIN server.
Figure 8.5.3.2.2-1 illustrates PIN delete locally procedure triggered by PEMC based on request/response model.
Pre-conditions:
1. PIN is successfully created and in use;
2. PEMC of the PIN decides to delete the PIN.
Figure 8.5.3.2.2-1: PIN delete locally by PEMC
0. The duration associated with the PIN expires and PEMC decides to delete the PIN.
1. The PEMC deletes the PIN which indicated by PIN ID locally. The PEGC information and the information related to this PIN such as PIN profile, PIN dynamic profileare also deleted.
2-5. The same procedures as step 4-7 defined in Figure 8.5.2.2.1-1.
6. The PEMC sends the PIN delete notification request to the PIN server that the PIN is deleted locally and this notification request contains the PIN ID of the deleted PIN.
7. The PIN server sends the PIN delete notification response to acknowledge the receipt of the notification.
8.5.3.3 Information flows
8.5.3.3.1 General
The following information flows are specified for PIN creation:
– PIN delete request and response;
– PIN delete notification request and response;
8.5.3.3.2 PIN delete request
Table 8.5.3.3.2-1 describes information elements in the PIN delete request from the PEMC to the PIN server.
Table 8.5.3.3.2-1: PIN delete request
|
Information element |
Status |
Description |
|
PIN ID |
M |
Identifier of the deleted PIN. |
|
Security credentials |
M |
Security credentials resulting from a successful authorization for the PIN service. |
8.5.3.3.3 PIN delete response
Table 8.5.2.3.3-1: PIN delete response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the PIN delete request was successful. |
|
Failure response |
O |
Indicates that the PIN delete request failed. |
|
> Cause |
M |
Provides the cause for PIN delete request failure. |
8.5.3.3.4 PIN delete notification request
Table 8.5.3.3.4-1: PIN delete notification request
|
Information element |
Status |
Description |
|
PIN ID |
M |
Identifier of the deleted PIN. |
8.5.3.3.5 PIN delete notification response
Table 8.5.3.3.5-1: PIN delete notification response
|
Information element |
Status |
Description |
|
Successful response |
O |
Indicates that the PIN delete notification request was successful. |
|
Failure response |
O |
Indicates that the PIN delete notification request failed. |
|
> Cause |
O |
Indicates the cause of PIN delete notification request failure. |
8.5.4 Multiple PEMCs/PEGCs
8.5.4.1 General
This clause describes the procedures for the configuration and use of multiple PEMCs and PEGCs in a PIN.
For a PIN having a large number of PIN elements, covering a large area, and/or requiring extra reliability, multiple PIN Elements may be assigned the role of PEMC and/or PEGC.
8.5.4.2 Procedure
8.5.4.2.1 PIN configuration with default and backup PEGCs
Figure 8.5.4.2.1-1 illustrates a procedure for configuring a new PIN Element, when requesting to join, with a default PEGC and one or more backup PEGCs.
Pre-conditions:
- The PEMC is pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server.
- The PEMC is authorized to access the PIN server.
- The PEMC has registered to the PIN server.
- The PEMC has requested and has been authorized by the PIN server to create a PIN.
- The required KPIs of the PIN have been configured.
- PINE-1, PINE-2, PEGC-A and PEGC-B have registered to the PEMC and PIN server.
Figure 8.5.4.2.2-1: Multiple PEGC configuration for a PIN
- PEGCs (e.g., PEGC-A and PEGC-B) shall join the PIN by sending PIN management PINE join into PIN requests to the PEMC. The PIN Client Profile information (supported PIN roles, supported PEGC KPIs, Supported PEGC schedule, UE location) shall be included in the requests. The PEMC shall use this information to determine whether multiple PEGCs are needed to meet the required KPIs of the PIN and which PIN elements (e.g., PEGC-A and PEGC-B) are able to serve as PEGCs. The PEMC shall configure multiple PEGCs (e.g., PEGC-A and PEGC-B) with a role of PEGC if needed. The PEMC shall then send a PIN profile update to the PIN server informing the PIN server that of the multiple PEGCs.
2. When PINEs (e.g., PINE-1) send a PIN management PINE join into PIN request to the PEMC, PIN Client Profile information (application client KPIs, application client schedule, UE location) shall be included in the request. The PEMC shall use this information and the PEGC information the PEMC receives in step 1 to determine the optimal default and backup PEGCs for the PINE. For example, PEMC assigns PEGC-A as the default PEGC for PINE-1 and PEGC-B as the backup PEGC for PINE-1.
3 The PEMC shall notify a default PEGC (e.g., PEGC-A) to update its local PIN Profile information to reflect that a PINE (e.g., PINE-1) is authorized to relay PIN communications via the PEGC.
4. The PEMC shall notify any backup PEGCs (e.g., PEGC-B) to update their local PIN Profile information to reflect that a PINE (e.g., PINE-1) is authorized to relay PIN communications via the PEGC.
5. The PEMC shall return a PIN management PINE join into PIN response to PINE-1. The response shall include updated PIN client profile information informing the PINE that it shall use a specified PEGC (e.g., PEGC-A) as its default PEGC and a specified PEGC (e.g., PEGC-B) as its backup PEGC.
6. The PEMC shall send a PIN profile update to the PIN server informing the PIN server of a PEGC (e.g., PEGC-A) serving as the default PEGC for a PINE (e.g., PINE-1) and any PEGCs (e.g., PEGC-B) serving as backup PEGCs for a PINE.
7. Steps 2 to 6 may be repeated for any additional PINEs joining the PIN. For example, based on PIN client profile information provided by PINE-2, the PEMC configures PEGC-B to serve as the default PEGC for PINE-2 and PEGC-A to serve as the backup PEGC for PINE-2.
8.5.4.3 Information flows
8.5.4.3.1 General
8.5.4.3.2 PIN management PINE Join into PIN request enhancements.
Table 8.5.4.3.2-1 shows informational elements needed to be included in the PIN management PINE Join into PIN request to support this functionality, in addition to those captured in Table xx.
Table 8.5.4.3.2-1: PIN management PINE Join into PIN request enhancement
|
Information element |
Status |
Description |
|
PIN client profile |
M |
PIN client profile information of the PINE requesting to join the PIN (e.g., application client KPIs, application client schedule, UE location) |
|
NOTE: The Information Elements in this table are additional to those in Table xx. |
||
Editor’s Note: Table 8.5.4.3.2-1 is to be merged with the main table xx for PIN management PINE Join into PIN request, the enhancement is captured here only for the purpose of enabling agreement on the feature.
8.5.4.3.3 PIN management PINE Join into PIN response enhancements.
Table 8.5.4.3.3-1 shows information elements needed to be included in the PIN management PINE Join into PIN response message to support this functionality, in addition to those captured in Table yy.
Table 8.5.4.3.3-1: PIN management PINE Join into PIN response enhancement
|
Information element |
Status |
Description |
|
Updated PIN client profile |
M |
PIN client profile information updated by the PEMC (e.g., default and backup PEGCs assigned to PINE). |
|
NOTE: The Information Elements in this table are additional to those in Table yy |
||
Editor’s Note: Table 8.5.4.3.3-1 is to be merged with the main table yy for PIN management PINE Join into PIN response, the enhancement is captured here only for the purpose of enabling agreement on the feature.
8.5.4.3.4 PEGC_notification
Table 8.5.4.3.4-1 shows the information elements of the PEGC notification from PEMC to a PIN element.
Table 8.5.4.3.4-1: PEGC notification
|
Information element |
Status |
Description |
|
Updated PIN profile |
M |
Updated PIN profile information that includes identifiers of PIN clients authorized to use PEGC to relay PIN communications. |
8.5.5 PIN Profile Recovery
8.5.5.1 General
8.5.5.2 Procedure
8.5.5.3 Information flows
8.5.6 Credential Provision
8.5.6.1 General
8.5.6.2 Procedure
8.5.6.3 Information flows
8.5.7 PIN discovery
8.5.7.1 General
8.5.7.2 Procedure
8.5.7.3 Information flows
8.5.8 PINE management
8.5.8.1 General
After the PIN is created by the PEMC, the other PIN elements can be added into the PIN. For the PIN elements that have already added into the PIN, they can be removed from a certain PIN by the PEMC.
When a PIN element is added into a PIN, the PEMC should configure with the PIN elements with the necessary permission, for example, to be able to access to 5GS via the PEGC.
Before the PIN element to be added into a PIN, the PEMC should discover the PIN element first, or the PIN element receives the lists of PIN Profile first (for example, the list of PIN ID, PIN description information).
When a PIN element is added into a PIN, the PINE can indicate the service it can provide. The service includes both the service that PIN client in PINE can provide and the service that application client on PINE can provide.
8.5.8.2 Procedure
8.5.8.2.1 PIN client requests to join into a PIN
Figure 8.5.8.2.1-1 illustrates procedure of PIN client requests to join into a PIN, based on request/response model.
Pre-conditions:
1. The UE (PIN client) has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PEMC;
2. The UE Identifier or PIN client Identifier is available;
3. The PIN client has been authorized to communicate with the PEMC;
4. The PIN client has already received the list of PIN ID, corresponding PEMC IP address;
Figure 8.5.8.2.2-1: PIN client requests to join into a PIN
1. he PIN element already has an application layer connection with a PEMC which manages the PIN.
NOTE: If the PIN client communicates with PEMC via WiFi or Bluetooth provided by PEMC, the PEMC can identify the PIN elements by the account number and password that PEMC distributed and the PIN client ID, UE GPSI if available.
And the PEMC has already send the PIN profile 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) and the PEMC IP address.
2. The PIN client sends the PIN Management PINE join into PIN request to PEMC to join the PIN. The request includes the security credentials of the PIN client received during authorization procedure and may include the UE identifier such as GPSI, PIN client ID, UE location, PIN ID and PIN client profile(s) information as shown in Table xxx.
The request also includes service that PINE can provide. In the request, both the service that PIN client in PINE can provide and the service that application client on PINE can provide.
Editor’s note: The authorization procedure between PIN client and PEMC should be captured in SA3 scope.
3. Upon receiving the request, the PEMC performs an authorization check to verify whether the PIN client has authorization to join the PIN.
4. The PEMC sends a successful PIN Management PINE join into PIN response to PIN client. Also, the access control information for the PIN client is also included, for example, user name, account, SSID, BSSID. All the information is used by PIN elements in PIN to access 5G or access the network provided by PEGC. The PEMC also provides lifetime of the PIN, identity, address of PEGC and may also provide unique PIN client ID to identify the PIN element within a PIN.
5. The PEMC sends PIN status notification Request to the PIN server containing the details of the new PIN client that joined the PIN, including PIN client ID, GPSI and etc.
6. The PEMC sends PIN status notification Request to the PEGC and other PIN elements containing the details of the new PIN client that joined the PIN. And the PEGC decides to enables the PINE to access 5GS.
7-9. The PEMC/PEGC/PINE updates PIN profile with the details of the new PIN client that joined the PIN and the service that the PINE can provide.
10-11. The PIN server/PEGC sends PIN status notification Response to the PEMC to acknowledge the receipt of the notification.
8.5.8.2.2 Procedure of PIN elements decides to leave the PIN
The following procedure defines the PIN elements decides to leave the PIN.
Pre-conditions:
1. The PIN client has already been added into a PIN;
2. The UE Identifier or PIN client Identifier is available;
3. The PIN client has been authorized to communicate with the PEMC;
Figure 8.5.8.2.2-1: PIN client decides to leave a PIN
1. The PIN element already has an application layer connection with a PEMC which manages the PIN.
2. The PINE decides to leave a PIN, and sends the PIN Management PINE leave from PIN request to PEMC to leave the PIN. The request includes the security credentials of the UE or PIN client received during authorization procedure and may include the UE identifier such as GPSI, PIN client ID, UE location and PIN ID.
Editor’s note: The authorization procedure between PIN client and PEMC should be captured in SA3 scope.
3. The PEMC authorizes the request, and decides to remove a PIN client from a PIN which indicated by PIN client ID or UE GPSI.
4. The PEMC sends the PIN Management PINE leave from PIN response to PINE to notify that the PIN client may not be included in the PIN anymore.
5-6. The PEMC sends the PIN status notification Request to the PEGC/PIN server containing the details of the PIN client that requested to leave the PIN. The details of the PINE include PIN client ID, GPSI and etc.
7-9. The PEMC/PEGC/PIN server updates the PIN profile and remove the details of the PIN client that requested to leave the PIN. The PEGC disables the access control information for this PINE.
10-11. The PIN server/PEGC sends PIN status notification Response to the PEMC to acknowledge the receipt of the notification.
8.5.8.2.3 Procedure of PEMC removes the PIN elements from a PIN
The following procedure defines the PIN elements decides to leave the PIN.
Pre-conditions:
1. The PIN client has already been added into a PIN;
2. The UE Identifier or PIN client Identifier is available;
3. The PIN client has been authorized to communicate with the PEMC;
Figure 8.5.8.2.3-1: Remove a PIN element from a PIN by PEMC
1. The PIN element already has an application layer connection with a PEMC which manages the PIN.
2. The PEMC decides to remove the PINE (identified by GPSI, PIN client ID).
3. The PEMC sends the PIN status notification Request to PINE, to notify that the PINE has been removed from the PIN.
4. The PINE sends PIN status notification Response to the PEMC to acknowledge the receipt of the notification.
5-6. The PEMC sends the PIN status notification Request to the PEGC/PIN server containing the details of the PIN client that removed from the PIN. The details of the PINE include PIN client ID, GPSI and etc.
7-9. The PEMC/PEGC/PIN server updates the PIN profile and remove the details of the PIN client that requested to leave the PIN. The PEGC disables the access control information for this PINE.
10-11. The PIN server/PEGC sends PIN status notification Response to the PEMC to acknowledge the receipt of the notification.
8.5.8.3 Information flows
8.5.9 PIN join
8.5.9.1 General
The PINE may join the PIN via either the PEMC or the PEGC depends on the communication range, supported RATs, preference, or local configuration.
8.5.9.2 Procedure
8.5.9.2.1 PINE join via PEGC
The PINE joins the PIN via the PEGC is depicted in figure 8.5.9.2.1-1.
Pre-conditions:
1. The PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PEMC;
2. The PINE already establishes the connection with PEGC;
3. The PIN information to join is available at the PINE via e.g., PIN discovery procedure.
Figure 8.5.9.2.1-1: PINE registration to PIN server via PEGC before join
1. The PINE sends PIN join request to the PEGC. The PIN join request contains the PIN ID which identifies the PIN to join, PINE client ID and credentials if available, PEMC identify/PIN server address[optional].
2. The PEGC identifies the received message is the PIN join request and perform the authorization. If authorized, the PEGC determines to forward the PIN join request to the PEMC or the PIN server.
3. The PEGC forwards the PIN join request to the PEMC based on the PEMC identity in step 1 or by resolving the PIN ID. The PEMC authorized the PINE to join the PIN, and returns the PIN join response to the PEGC.
4. The PEGC forwards the PIN join request to the PIN server based on the PIN server address in step 1 or by resolving the PIN ID. The PIN server forwards the PIN join request to the PEMC, and the PEMC authorized the PINE to join the PIN, and returns the PIN join response to the PIN server. Further the PIN server return the PIN server to the PEGC.
5. After the join, the PEMC update the PIN and may notify other entities (e.g., existing joined members, PIN server).
6. The PEGC return the PIN join response to the PINE.
8.5.10 PIN modification
8.5.10.1 General
This clause describes PIN modification functionality.
8.5.10.2 Procedures
8.5.10.2.1 General
8.5.10.2.2 PIN modification after local PEMC failure
Figure 8.5.10.2.2-1 describes the PIN modification procedure to perform a PEMC role change due to the failure of the PEMC. An authorised administrator is the owner of the PIN and accesses PIN configuration using an application on a UE, which is one of the PEMC for the PIN. The authorised administrator can manage the PIN locally or through the 5G network. This procedure describes a PEMC (e.g. an authorized administrator on a UE) managing the PIN remotely via the 5G network.
The procedure may used e.g. when a PEMC is available on a UE for PIN management by an authorised administrator. When there is a local PEMC failure, the authorized administrator can be enabled to manage the PIN remotely, via the 5G network, using the following steps.
Pre-conditions:
1. The PIN server has authorised the creation of the PIN.
2. The authorised administrator is the owner of the PIN and has created the PIN.
3. The authorised administrator configures PEMC2 to provide PIN management for the PIN. PEMC2 becomes the active PEMC and UE/PEMC1 is the inactive PEMC.
4. PEMC2, PEGC, PINE-1, PINE-2, and the UE/PEMC1 are members of the PIN. PINE-1 has PEMC capability.
5. The authorised administrator leaves the local area of the PIN (e.g. in a home) and is able to access the PIN remotely through the 5G network. As a result, the authorised administrator is able to manage the PIN through the 5G network
Figure 8.5.10.2.2-1: PIN Modification after local PEMC failure
1. UE/PEMC1 receives a notification from PEGC that there is a communication failure with PEMC2.
2. An authorised administrator on UE/PEMC1 sends a PIN_configuration_request to the PIN server through the 5G network. The request includes the security credentials of the authorised administrator, the UE ID, the PIN ID, PIN member ID, authorization type indicating the role change, and a request that PINE-1 be assigned the new PEMC.
3. The PIN server processes the modification request and checks if the authorised administrator is allowed to modify the PIN. The PIN server verifies PINE-1 has the capability to serve as a PEMC using information in the PIN profile.
4. If the authorised administrator is allowed to perform PIN modification, the PIN server sends a PIN_management_request to PINE-1 to assign PINE-1 as the new PEMC and provides PIN profile and dynamic profile information to PINE-1.
Editor’s Note: Usage of PIN profile information and PIN dynamic profile information in the information flows, and the procedures where each of these IEs are applicable are FFS.
5. PINE-1 returns an accept response in the PIN_management_response to the PIN server.
6. The PIN server notifies the other members of the PIN that PINE-1 will be the new PEMC for the PIN and updates the PIN profile and dynamic profile information.
7. The PIN server sends a PIN_configuration_response to the PIN_configuration_request with updated information for the PIN profile and the dynamic profile information to the UE/PEMC1.
8. PIN communications resume with PINE-1 serving as the new PEMC.
8.5.10.2.3 PIN modification with PEGC role change
Figure 8.5.10.2.3-1 describes a PIN modification procedure to perform a PEGC role change due to the unavailability of the PEGC. This procedure describes a PEMC detecting the unavailability of a PEGC (e.g. PEGC leaves the local service area of the PIN) and performing a PIN modification with the PIN Server to assign a new PEGC. As part of PIN management, a PEMC subscribes to receive periodic notifications from PEGCs to ensure PIN routing is available for members of the PIN at all times. If a PEMC does not receive the periodic notifications from the PEGC, then the PEMC needs to assign a new PEGC or request the PIN server to assign the new PEGC.
Pre-conditions:
1. The PIN server has authorized the PEMC to create PINs.
2. The PEMC creates a local PIN with members: PEMC, UE serving as PEGC, PINE1, and PINE2.
3. The PEMC maintains a PIN profile with information on the capabilities of each PIN member.
4. PINE2 is a PIN member that also has gateway capability.
Figure 8.5.10.2.3-1: PIN Modification due to PEGC unavailability
1. PEMC subscribes to receive periodic notifications from PEGC to monitor the availability of PIN routing service provided by PEGC.
NOTE: The subscription/ notification is for further development.
Editor’s Note: How the PEMC detects the unavailability of PEGC is FFS.
2. PEGC leaves the local coverage area of the PIN, e.g., leaves the home, and is not available to route PIN communications.
3. PEMC does not receive a notification from PEGC at the configured interval and determines that PEGC is no longer providing PIN routing capability.
4. PEMC sends a PIN_configuration_request to the PIN server to select a new PEGC. The request includes the PIN ID, the PEMC ID, the PEGC ID, authorization type indicating the role change, the ID of a PIN member that can serve as the new PEGC (e.g., PINE2), and a timestamp.
5. The PIN server considers which member of the PIN can serve as the new PEGC, including the PIN member the PEMC provided, and selects a PIN member to serve as the new PEGC. The PIN server sends a PIN_management_request to PINE-2 with PIN profile and dynamic profile information. The dynamic profile information includes PIN traffic routing rules that PINE2 would need to make routing decisions.
6. PINE-2 sends a PIN_management_response accepting to serve as the new PEGC.
7. The PIN server sends a PIN_configuration_response with PIN profile and dynamic profile information to the PEMC with the status of the request, the ID of the new PEGC, and PIN traffic routing rules. The PIN server response triggers the PEMC to notify other PIN members of the PEGC role change.
8. PEMC notifies the other members of the PIN that PINE2 will serve as the new PEGC. The PEMC includes PIN profile and dynamic profile information that includes traffic routing rules applicable to each member.
8.5.10.3 Information flows.
8.5.10.3.1 General
8.5.10.3.2 PIN_configuration_request
Table 8.5.10.3.2-1 shows the informational elements of the PIN configuration request sent by a PIN Element to the PIN server to obtain authorization for the modification of a PIN.
Table 8.5.10.3.2-1: PIN configuration request
|
Information element |
Status |
Description |
|
PIN ID |
M |
The identifier of the PIN |
|
Requester PINE ID |
M |
The identifier of the PIN Element making the request |
|
Authorization type |
M |
Request for the authorization to modify the configuration of a PIN: PEMC role change, PEGC role change |
|
PINE ID of predecessor in the role |
M |
PINE ID of the element serving in the indicated role and needs to be changed e.g. due to being unavailable. |
|
PINE ID of proposed successor in the role |
O |
PINE ID of the element proposed to assume the role |
8.5.10.3.3 PIN_configuration_response
Table 8.5.10.3.3-1 shows the informational elements of the PIN configuration response provided by the PIN server to authorize the modification of a PIN.
Table 8.5.10.3.3-1: PIN configuration response
|
Information element |
Status |
Description |
|
Response |
M |
The response (authorize or not authorize) from the PIN Server. |
|
PIN profile information |
M |
The IEs from the PIN profile information that the PIN Server has updated for modifying the PIN |
|
Dynamic PIN profile information |
M |
The IEs from the dynamic PIN profile information that the PIN Server has authorized for modifying the PIN |
8.5.10.3.4 PIN_management_request
Table 8.5.10.3.4-1 shows the informational elements of the PIN management request sent to PIN elements to make changes to the configuration of the PIN.
Table 8.5.10.3.4-1: PIN management request
|
Information element |
Status |
Description |
|
PIN ID |
M |
The identifier of the PIN |
|
Requestor ID |
M |
The identifier of the PIN Server or PIN Element making the request |
|
Modification type |
M |
Request for the modification of the PIN: PEMC assignment, PEGC assignment |
|
Dynamic PIN profile information |
M |
IEs from the dynamic PIN profile information that the PINE needs to operate in the new role |
8.5.10.3.5 PIN_management_response
Table 8.5.3.3.5-1 shows the informational elements of the PIN management response received from the PIN element to the PIN modification request.
Table 8.5.10.3.5-1: PIN management response
|
Information element |
Status |
Description |
|
Response |
M |
The response (accept or deny) from the PIN Element to the PIN management request. |