Figure 8.5.14.2.1-1 illustrates the PIN connectivity subscribe procedure.
Pre-conditions:
-
The PINE/PEMC/PIN Server (e.g., subscriber) has already received the address of PEGC;
-
The subscriber has been authorized to communicate with PEGC;
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.
Figure 8.5.14.2.2-1 illustrates the PIN connectivity notify procedure.
Pre-conditions:
-
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.
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.
Figure 8.5.14.2.3-1 illustrates the PIN connectivity update procedure.
Pre-conditions:
-
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;
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.
Figure 8.5.14.2.4-1 illustrates the PIN connectivity unsubscribe procedure.
Pre-conditions:
-
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;
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.