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.14  PIN connectivity subscriptionp. 82

8.5.14.1  Generalp. 82

The PIN connectivity subscription is used by the PINE/PEMC/PIN Server to be notified of PIN connectivity events by the PEGC.
PIN connectivity notification includes PIN connectivity information.

8.5.14.2  Procedurep. 82

8.5.14.2.1  PIN connectivity subscribep. 82
Figure 8.5.14.2.1-1 illustrates the PIN connectivity subscribe procedure.
Pre-conditions:
  1. The PINE/PEMC/PIN Server (e.g., subscriber) has already received the address of PEGC;
  2. The subscriber has been authorized to communicate with PEGC;
Reproduction of 3GPP TS 23.542, Fig. 8.5.14.2.1-1: PIN connectivity subscribe
Up
Step 1.
The subscriber sends the PIN connectivity subscribe request to the PEGC. The PIN connectivity subscribe request includes the subscriber identifier along with the security credentials and the event identifier.
Step 2.
Upon receiving the request from the subscriber, the PEGC checks if the subscriber is authorized to subscribe for PIN connectivity information. The authorization check may apply to an individual PIN. If the request is authorized, the PEGC creates and stores the subscription for PIN.
Step 3.
If the processing of the request is successful, the PEGC sends a PIN connectivity subscribe response to the subscriber, which includes the subscription identifier and may include the expiration time, indicating when the subscription will automatically expire. To maintain the subscription, the subscriber shall send a PIN connectivity update request prior to the expiration time. If a new PIN connectivity update request is not received prior to the expiration time, the PEGC shall treat the subscriber as implicitly unsubscribed.
Up
8.5.14.2.2  PIN connectivity notifyp. 83
Figure 8.5.14.2.2-1 illustrates the PIN connectivity notify procedure.
Pre-conditions:
  1. The PINE/PEMC/PIN Server (e.g., subscriber) has successfully subscribed with the PEGC for the PIN connectivity as specified in clause 8.5.14.2.1.
Reproduction of 3GPP TS 23.542, Fig. 8.5.14.2.2-1: PIN connectivity notify procedure
Up
Step 1.
When an event occurs at the PEGC that satisfies triggering conditions, the PEGC notifies the subscriber(s).
Step 2.
The PEGC sends an PIN connectivity notification to the subscribers related to the connectivity event and includes the PIN connectivity information.
The PIN connectivity information includes the PEGC identifier, the PIN identifier, the PIN client identifier, and the event type (e.g., connectivity).
Step 3.
Upon receiving the notification, the subscriber processes the connectivity changes according to the information in the PIN connectivity notification.
Up
8.5.14.2.3  PIN connectivity updatep. 84
Figure 8.5.14.2.3-1 illustrates the PIN connectivity update procedure.
Pre-conditions:
  1. The PINE/PEMC/PIN Server (e.g., subscriber) has subscribed with the PEGC for PIN connectivity information as specified in 8.5.14.2.1;
Reproduction of 3GPP TS 23.542, Fig. 8.5.14.2.3-1: PIN connectivity update
Up
Step 1.
The subscriber sends a PIN connectivity update request to the PEGC. The PIN connectivity update request includes the security credentials and the subscription identifier. It may also include notification target address and proposed expiration time.
Step 2.
Upon receiving the request from the requestor, the PEGC checks if the subscriber is authorized to update the subscription information. If the request is authorized, the PEGC updates the stored subscription for PIN connectivity information.
Step 3.
If the processing of the request is successful, the PEGC sends a PIN connectivity update response to the subscriber, which may include the expiration time, indicating when the subscription will automatically expire. To maintain the subscription, the subscriber shall send an PIN connectivity update request prior to the expiration time. If a PIN connectivity update request is not received prior to the expiration time, the PEGC shall treat the subscriber as implicitly unsubscribed.
Up
8.5.14.2.4  PIN connectivity unsubscribep. 84
Figure 8.5.14.2.4-1 illustrates the PIN connectivity unsubscribe procedure.
Pre-conditions:
  1. The PINE/PEMC/PIN Server (e.g., subscriber) has subscribed with the PEGC for PIN connectivity information as specified in 8.5.14.2.1;
Reproduction of 3GPP TS 23.542, Fig. 8.5.14.2.4-1: PIN connectivity update
Up
Step 1.
The subscriber sends a PIN connectivity unsubscribe request to the PEGC. The PIN connectivity unsubscribe request includes the security credentials and the subscription identifier.
Step 2.
Upon receiving the request from the subscriber, the PEGC checks if the requestor is authorized to unsubscribe. If the request is authorized, the PEGC cancels the subscription for PIN connectivity information.
Step 3.
If the processing of the request is successful, the PEGC sends a PIN connectivity unsubscribe response to the subscriber.
Up

8.5.14.3  Information flowsp. 85

8.5.14.3.1  Generalp. 85
The following information flows are specified for PIN connectivity subscription:
  • PIN connectivity subscribe
  • PIN connectivity notify
  • PIN connectivity update
  • PIN connectivity unsubscribe
8.5.14.3.2  PIN connectivity subscribe requestp. 85
Information element Status Description
Subscriber identifierMUnique identifier of the PINE/PEMC/PIN server.
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
PIN IDMThe identifier of PIN.
Notification Target AddressMThe Notification target address (e.g. URL) where the notifications destined for the subscriber should be sent to.
Proposed expiration timeOProposed expiration time for the subscription.
Up
8.5.14.3.3  PIN connectivity subscribe responsep. 85
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.
Failure responseOIndicates that the subscription request failed.
> CauseOIndicates the cause of subscription request failure.
Up
8.5.14.3.4  PIN connectivity notifyp. 85
Table 8.5.14.3.4-1 describes information elements in the PIN connectivity notification from the PEGC.
Information element Status Description
PEGC identifierMIdentifier of the PEGC.
PIN identifierMIdentifier of the PIN.
PIN client identifierMUnique identifier of the PINE/PEMC/PIN server related to the connectivity change.
Event typeMType of event (e.g., connectivity).
Up
8.5.14.3.5  PIN connectivity update requestp. 86
Information element Status Description
Subscription IDMSubscription identifier corresponding to the subscription.
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
Notification Target AddressOThe Notification target address (e.g. URL) where the notifications destined for the subscriber should be sent to.
Proposed expiration timeOProposed expiration time for the subscription.
Up
8.5.14.3.6  PIN connectivity update responsep. 86
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.14.3.7  PIN connectivity unsubscribe requestp. 86
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.14.3.8  PIN connectivity unsubscribe responsep. 87
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