Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.542  Word version:  18.4.0

Top   Top   Up   Prev   Next
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.3 PIN delete  8.5.3.1 General  8.5.3.2 Procedure  8.5.3.2.1 PIN delete procedure involving PIN server  8.5.3.2.2 PEMC decided PIN deletion  8.5.3.2.3 PIN delete procedure triggered by PIN server  8.5.3.3 Information flows  8.5.3.3.1 General  8.5.3.3.2 PIN delete request  8.5.3.3.3 PIN delete response  8.5.3.3.4 PIN delete notification request  8.5.3.3.5 PIN delete notification response 
...

 

8.5.3  PIN delete  p. 44

8.5.3.1  General  p. 44

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.
Up

8.5.3.2  Procedure  p. 44

8.5.3.2.1  PIN delete procedure involving PIN server  p. 44
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.
Reproduction of 3GPP TS 23.542, Fig. 8.5.3.2.1-1: PIN delete procedure involving PIN server
Figure 8.5.3.2.1-1: PIN delete procedure involving PIN server
Up
Step 1.
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.
Step 2.
Upon receiving the request, the PIN server validates the PIN delete request and verifies the security credentials.
Step 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.
Step 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.
Step 5.
PEMC sends the PIN delete notification request to the PIN elements containing the PIN ID of the deleted PIN.
Step 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.
Step 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.
Up
8.5.3.2.2  PEMC decided PIN deletion  p. 45
The PEMC can directly trigger the PIN delete procedure, for example, when the duration associated 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.
Reproduction of 3GPP TS 23.542, Fig. 8.5.3.2.2-1: PIN delete locally by PEMC
Figure 8.5.3.2.2-1: PIN delete locally by PEMC
Up
Step 0.
The duration associated with the PIN expires and PEMC decides to delete the PIN.
Step 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 profile are also deleted.
Step 2-5.
The same procedures as step 4-7 defined in Figure 8.5.2.2.1-1.
Step 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.
Step 7.
The PIN server sends the PIN delete notification response to acknowledge the receipt of the notification.
Up
8.5.3.2.3  PIN delete procedure triggered by PIN server  p. 46
Figure 8.5.3.2.3-1 illustrates PIN delete procedure triggered by PIN server based on request/response model.
Pre-conditions:
  1. PIN is successfully created and in use;
  2. The PIN server decides to delete a PIN.
Reproduction of 3GPP TS 23.542, Fig. 8.5.3.2.3-1: PIN delete procedure triggered by PEMC
Figure 8.5.3.2.3-1: PIN delete procedure triggered by PEMC
Up
Step 1.
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.
Step 2.
If the PIN server decides to delete the PIN, the PIN server sends a PIN delete notification request to PEMC.
Step 3.
The PEMC sends the PIN delete notification response to the PIN server to acknowledge the receipt of the notification.
Step 4-7.
The same as step 4 - 7 in Figure 8.5.3.2.2-1.
Up

8.5.3.3  Information flows  p. 46

8.5.3.3.1  General  p. 46
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  p. 47
Table 8.5.3.3.2-1 describes information elements in the PIN delete request from the PEMC to the PIN server.
Information element Status Description
PIN IDMIdentifier of the deleted PIN.
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
Up
8.5.3.3.3  PIN delete response  p. 47
Information element Status Description
Successful responseOIndicates that the PIN delete request was successful.
Failure responseOIndicates that the PIN delete request failed.
> CauseMProvides the cause for PIN delete request failure.
Up
8.5.3.3.4  PIN delete notification request  p. 47
Information element Status Description
PIN IDMIdentifier of the deleted PIN.
8.5.3.3.5  PIN delete notification response  p. 47
Information element Status Description
Successful responseOIndicates that the PIN delete notification request was successful.
Failure responseOIndicates that the PIN delete notification request failed.
> CauseOIndicates the cause of PIN delete notification request failure.
Up

Up   Top   ToC