Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑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.9  PIN status subscriptionp. 63

8.5.9.1  Generalp. 63

The PIN status update is used by the PINE, PEGC and PIN server to be notified of PIN status information by the PEMC.
PIN status information includes the following information:
  • PINE add/remove into/from the PIN;
  • PEGC/PEMC relocation in the PIN;
  • PIN profile update;
  • PIN state changes;

8.5.9.2  Procedurep. 63

8.5.9.2.1  PIN status subscribep. 63
Figure 8.5.9.2.1-1 illustrates the PIN status subscribe procedure.
Pre-conditions:
  1. The PINE/PEGC/PIN server has already received the address of PEMC;
  2. The PINE/PEGC/PIN server has been authorized to communicate with PEMC.
Reproduction of 3GPP TS 23.542, Fig. 8.5.9.2.1-1: PIN status subscribe
Up
Step 1.
The PINE/PEGC/PIN server sends the PIN status subscribe request to the PEMC. The PIN status subscribe request includes the PIN client ID along with the security credentials, Event ID.
Step 2.
Upon receiving the request from the PINE/PEGC/PIN server, the PEMC checks if the PINE/PEGC/PIN server is authorized to subscribe for information of the requested PIN status information. The authorization check may apply to an individual PIN. If the request is authorized, the PEMC creates and stores the subscription for PIN.
Step 3.
If the processing of the request is successful, the PEMC sends a PIN status subscribe response to the PINE/PEGC/PIN server, which includes the subscription identifier and may include the expiration time, indicating when the subscription will automatically expire. To maintain the subscription, the PINE/PEGC/PIN server shall send a PIN status update request prior to the expiration time. If a new PIN status update request is not received prior to the expiration time, the PEMC shall treat the PINE/PEGC/PIN server as implicitly unsubscribed.
Up
8.5.9.2.2  PIN status notifyp. 63
Figure 8.5.9.2.2-1 illustrates the PIN status notify procedure.
Pre-conditions:
  1. The PINE/PEGC/PIN has subscribed with the PEMC for the PIN status as specified in clause 8.5.9.2.1.
Reproduction of 3GPP TS 23.542, Fig. 8.5.9.2.2-1: PIN status notify procedure
Up
Step 1.
When an event occurs at the PEMC that satisfies trigger conditions for notifying (e.g. to provide updated PIN status, for example when a PINE joins into the PIN) a PINE/PEGC/PIN server.
The status information of PIN is updated including the following cases:
  • PIN modification: The PIN modification includes the PEMC/PEGC relocation and the PINE joins into PIN or leaves the PIN;
  • PIN profile updates: The PIN profiles is referred to the clause 8.2.2, and the updated PIN profile may be coordinated to other PINEs;
  • PIN state changes: Whenever the PIN state is changed from activated to de-activated or vice-versa;
Step 2.
The PEMC sends an PIN status notify to the PINE/PEGC/PIN server with the updated PIN status information.
The PIN status information notification includes the following parameters:
  • PIN modification: If the PEMC decides the PEMC/PEGC relocation, the PEMC includes the parameters about the newly assigned PEMCs and PEGCs in the PIN status update request, for example, the PEMC/PEGC ID or address, the PEGC information in Table 8.5.2.3.3-1 about access control information and etc;
  • PINE management: If the PEMC decides the PINE to join or leave the PIN, the PEMC includes the parameters about the newly added/removed PINE in the PIN status update request, for example, the PIN client ID or address, the PIN client profile and etc. Also if the PINE is removed from the PIN, the parameters about the removed PINE should be included in the PIN status update request;
  • PIN profile update: If the PIN profile is updated, the PEMC includes the parameters about updated PIN profile in the PIN status update request;
  • PIN state changes: Whenever the PIN state is changed from activated to de-activated or vice-versa;
Step 3.
Upon receiving the notification, the PINE, PEGC or PIN server updates the PIN profile according to the information in the PIN status notify.
Up
8.5.9.2.3  PIN status updatep. 64
Figure 8.5.9.2.3-1 illustrates the PIN status update procedure.
Pre-conditions:
  1. The PINE/PEGC/PIN server has subscribed with the PEMC for PIN status information as specified in clause 8.5.9.2.1;
Reproduction of 3GPP TS 23.542, Fig. 8.5.9.2.3-1: PIN status update
Up
Step 1.
The PINE/PEGC/PIN server sends a PIN status update request to the PEMC. The PIN status update request includes the security credentials and the subscription identifier. It may also include subscribed events, notification target address and proposed expiration time.
Step 2.
Upon receiving the request from the PINE/PEGC/PIN server, the PEMC checks if the PINE/PEGC/PIN server is authorized to update the subscription information. If the request is authorized, the PEMC updates the stored subscription for PIN status information.
Step 3.
If the processing of the request is successful, the PEMC sends a PIN status update response to the PINE/PEGC/PIN server, which may include the expiration time, indicating when the subscription will automatically expire. To maintain the subscription, the PINE/PEGC/PIN server shall send an PIN status information subscription update request prior to the expiration time. If a PIN status update request is not received prior to the expiration time, the PEMC shall treat the PINE/PEGC/PIN server as implicitly unsubscribed.
Up
8.5.9.2.4  PIN status unsubscribep. 65
Figure 8.5.9.2.4-1 illustrates the PIN status unsubscribe procedure.
Pre-conditions:
  1. The PINE/PEGC/PIN server has subscribed with the PEMC for PIN status information as specified in clause8.5.9.2.1;
Reproduction of 3GPP TS 23.542, Fig. 8.5.9.2.4-1: PIN status unsubscribe
Up
Step 1.
The PINE/PEGC/PIN server sends a PIN status unsubscribe request to the PEMC. The PIN status unsubscribe request includes the security credentials and the subscription identifier.
Step 2.
Upon receiving the request from the PINE/PEGC/PIN server, the PEMC checks if the PINE/PEGC/PIN server is authorized to unsubscribe. If the request is authorized, the PEMC cancels the subscription for PIN status information.
Step 3.
If the processing of the request is successful, the PEMC sends a PIN status unsubscribe response to the PINE/PEGC/PIN server.
Up

8.5.9.3  Information flowsp. 66

8.5.9.3.1  Generalp. 66
The following information flows are specified for PIN status:
  • PIN status subscribe;
  • PIN status notify;
  • PIN status update;
  • PIN status unsubscribe;
8.5.9.3.2  PIN status subscribe requestp. 66
Information element Status Description
PIN client IDMUnique identifier of the PINE/PEGC/PIN server.
Subscribed Events IDsM Identifies PIN status event for which the subscriber is notified, more than one PIN status event IDs can be provided.
Event IDs:
  • PIN modification
  • PINE management (PINE join/leave)
  • PIN profile update
  • PIN state
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
PIN IDMThe identifier of PIN.
Notification Target AddressOThe Notification target address (e.g. URL) where the notifications destined for the PINE/PEGC/PIN server should be sent to.
Proposed expiration timeOProposed expiration time for the subscription.
Up
8.5.9.3.3  PIN status subscribe responsep. 66
Information element Status Description
Successful responseOIndicates that the subscription request was successful.
> Subscription IDMSubscription identifier corresponding to the subscription.
> Expiration timeOIndicates the expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time.
> Successfully subscribed event IDsOIndicates the successfully subscribed event IDs.
Failure responseOIndicates that the subscription request failed.
> CauseOIndicates the cause of subscription request failure.
> Unsuccessfully subscribed event IDsOIndicates the unsuccessfully subscribed event IDs.
Up
8.5.9.3.4  PIN status notifyp. 67
Table 8.5.9.3.4-1 describes information elements in the PIN status notify from the PEMC to PEMC/PEGC/PINE/PIN server.
Information element Status Description
PIN Status event typeMIdentifies PIN status event types contained in the notification; more than one PIN status event type can be provided.
PIN status event types
  • PIN modification
  • PINE management (PINE join/leave)
  • PIN profile update
  • PIN state (Activated or de-activated)
PIN IDMIndicate identifier of the PIN that status event related to.
PINE managementOIndicates the PINE join/leave the PIN and PINE removed, this IE is present if the PIN status event type is PINE management.
PIN modificationOIndicates the modification of PIN as indicated in clause 8.5.10 for example the PEMC/PEGC relocation, this IE is present if the PIN status event type is PIN modification.
PIN profiles updateOIndicates a PIN profile update that indicated in clause 8.2.2, this IE is present if the PIN status event type are PIN modification, PINE management, and is PIN profile update.
PIN stateOIndicates the state of a PIN.
Up
8.5.9.3.5  PIN status update requestp. 67
Information element Status Description
Subscription IDMSubscription identifier corresponding to the subscription.
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
PIN IDMThe identifier of PIN.
Subscribed EventsO Identifies PIN status event types for which the subscriber is notified, more than one PIN status event type can be provided.
PIN status event types
  • PIN modification
  • PINE management (PINE join/leave)
  • PIN profile update
  • PIN state
Notification Target AddressOThe Notification target address (e.g. URL) where the notifications destined for the PINE/PEGC/PIN server should be sent to.
Proposed expiration timeOProposed expiration time for the subscription.
Up
8.5.9.3.6  PIN status update responsep. 68
Information element Status Description
Successful response (see NOTE)OIndicates that the subscription update request was successful.
> Expiration timeOIndicates the expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time.
Failure response (see NOTE)OIndicates that the subscription update request failed.
> CauseMIndicates the cause of subscription update request failure.
NOTE:
One IE is included in the response.
Up
8.5.9.3.7  PIN status unsubscribe requestp. 68
Information element Status Description
Subscription IDMSubscription identifier corresponding to the subscription.
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
Up
8.5.9.3.8  PIN status unsubscribe responsep. 68
Information element Status Description
Successful response (see NOTE)OIndicates that the unsubscribe request was successful.
Failure response (see NOTE)OIndicates that the unsubscribe request failed.
> CauseMIndicates the cause of unsubscribe request failure.
NOTE:
One IE is included in the response.
Up

Up   Top   ToC