Figure 8.5.9.2.1-1 illustrates the PIN status subscribe procedure.
Pre-conditions:
-
The PINE/PEGC/PIN server has already received the address of PEMC;
-
The PINE/PEGC/PIN server has been authorized to communicate with PEMC.
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.
Figure 8.5.9.2.2-1 illustrates the PIN status notify procedure.
Pre-conditions:
-
The PINE/PEGC/PIN has subscribed with the PEMC for the PIN status as specified in clause 8.5.9.2.1.
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.
Figure 8.5.9.2.3-1 illustrates the PIN status update procedure.
Pre-conditions:
-
The PINE/PEGC/PIN server has subscribed with the PEMC for PIN status information as specified in clause 8.5.9.2.1;
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.
Figure 8.5.9.2.4-1 illustrates the PIN status unsubscribe procedure.
Pre-conditions:
-
The PINE/PEGC/PIN server has subscribed with the PEMC for PIN status information as specified in clause8.5.9.2.1;
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.