hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.2.3.5 PIN creation notification response
| Table 8.5.2.3.5-1 describes information elements in the PIN creation notification response from the PEGC, PIN elements to the PEMC.
Table 8.5.2.3.5-1: PIN creation notification response
Information element
Status
Description
Successful response
O (see NOTE)
Indicates that the PIN creation notification request w... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3 PIN delete
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.1 General
| 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... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.2.1 PIN delete procedure involving PIN server
| 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 ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.2.2 PEMC decided PIN deletion
| 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 trig... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.2.3 PIN delete procedure triggered by PIN server
| 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.
Figure 8.5.3.2.3-1: PIN delete procedure triggered by PEMC
1. An event occurs at the PIN server that s... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.3 Information flows
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.3.1 General
| The following information flows are specified for PIN creation:
- PIN delete request and response;
- PIN delete notification request and response;
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.3.2 PIN delete request
| Table 8.5.3.3.2-1 describes information elements in the PIN delete request from the PEMC to the PIN server.
Table 8.5.3.3.2-1: PIN delete request
Information element
Status
Description
PIN ID
M
Identifier of the deleted PIN.
Security credentials
M
Security credentials resulting from a successful authorizatio... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.3.3 PIN delete response
| Table 8.5.3.3.3-1: PIN delete response
Information element
Status
Description
Successful response
O
Indicates that the PIN delete request was successful.
Failure response
O
Indicates that the PIN delete request failed.
> Cause
M
Provides the cause for PIN delete request failure.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.3.4 PIN delete notification request
| Table 8.5.3.3.4-1: PIN delete notification request
Information element
Status
Description
PIN ID
M
Identifier of the deleted PIN.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.3.3.5 PIN delete notification response
| Table 8.5.3.3.5-1: PIN delete notification response
Information element
Status
Description
Successful response
O
Indicates that the PIN delete notification request was successful.
Failure response
O
Indicates that the PIN delete notification request failed.
> Cause
O
Indicates the cause of PIN delete notifi... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.4 Multiple PEMCs/PEGCs
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.4.1 General
| This clause describes the procedures for the configuration and use of multiple PEMCs and PEGCs in a PIN.
For a PIN having a large number of PIN elements, covering a large area, and/or requiring extra reliability, multiple PIN Elements may be assigned the role of PEMC and/or PEGC.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.4.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.4.2.1 PIN configuration with default and backup PEGCs
| Figure 8.5.4.2.1-1 illustrates a procedure for configuring a new PIN Element, when requesting to join, with a default PEGC and one or more backup PEGCs.
Pre-conditions:
1. The PEMC is pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server.
2. The PEMC is authorized to access the... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.4.2.2 PIN management with multiple PEMCs
| Figure 8.5.4.2.2-1 illustrates a procedure for managing the PIN with multiple PEMCs. PIN elements when registering with the PIN indicates that they have the capability to act as PEMC and are assigned with primary or secondary PEMC role as described in the subclause 8.4.2.2.1.
Pre-conditions:
1. A PIN owner or admin c... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.4.2.3 Notifying the PIN elements of PEGC details
| Figure 8.5.4.2.3-1 illustrates a procedure for notifying the PIN elements about the change in default or backup PEGC when multiple PIN elements have the PEGC capability.
Pre-conditions:
1. The PIN is configured and PEGC-1 is the designed PEGC.
2. PIN elements have subscribed for PIN status as specified in clause 8.5... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.4.3 Void
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.4.3.1 Void
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.5 PIN Profile Recovery
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.5.1 General
| The PIN profile recovery procedure describes how the PEMC retrieves a PIN profile from a PIN server.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.5.2 Procedure
| Pre-conditions:
1. The PEMC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
2. The PIN has already been created and a PIN ID is distributed by PIN server;
3. The PEMC has been authorized to communicate with the PIN server;
4. A PIN client has already re... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.5.3 Information flows
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.5.3.1 General
| The following information flows are specified for PIN profile retrieval:
- PIN Profile Query request and response;
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.5.3.2 PIN Profile Query request
| Table 8.5.5.3.2-1 describes information elements in the PIN Profile Query request from the PEMC to the PIN server.
Table 8.5.5.3.2-1: PIN Profile Query request
Information element
Status
Description
PIN ID
M
Identifier of the deleted PIN.
Security credentials
M
Security credentials resulting from a successfu... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.5.3.3 PIN Profile Query Response
| Table 8.5.5.3.3-1 describes information elements in the PIN Profile Query response from the PIN server to PEMC.
Table 8.5.5.3.3-1: PIN Profile Query Response
Information element
Status
Description
Successful response
O
Indicates that the PIN Profile Query request was successful.
> PIN profile
M
The PIN profi... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.6 Credential Provision
| NOTE: In the current release, PIN client authentication (e.g.: PINE, PEMC or PEGC) relies on pre-provisioned information and no dynamic credential provision procedure is defined, and authorization within the PIN is defined in clause 8.10.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.7 PIN discovery
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.7.1 General
| Before the PINE trigger the PINE join into the PIN, the PINE should discover the available PIN.
For a certain PIN element, the PIN should be discovered and the PIN element can decide whether to join in the PIN. There are two situations that the PIN elements can discover the PIN as following:
- If the PIN elements c... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.7.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.7.2.1 Procedures of PIN discovery based on PEMC
| Pre-conditions:
1. The UE Identifier or PIN client Identifier is available;
2. The PIN client has been authorized to communicate with the PEMC;
3. The UE or PIN client has already received the role of PEMC from PIN server;
4. The PIN element has already had an application layer connection with a PEMC which manages ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.7.2.2 Procedures of PIN discovery with assistance of PIN server via PEGC
| Some of the PIN elements can have the application layer connection with the PEGC, for example, via WiFi or Bluetooth, and the PIN element can have the communication with PIN server to receive the lists of PIN ID and corresponding PIN description information. And the PIN elements can decide whether to join in the PIN.
... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.7.3 Information flows
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.7.3.1 General
| The following information flows are specified for PIN discovery:
- PIN discovery request and response;
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.7.3.2 PIN discovery request
| Table 8.5.7.3.2-1 describes information elements in the PIN discovery request from the PINE to the PEMC/PIN server.
Table 8.5.7.3.2-1: PIN discovery request
Information element
Status
Description
UE identifier
M
The identifier of the hosting UE (i.e. GPSI or identity token) of PINE
Security credentials
M
Sec... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.7.3.3 PIN discovery response
| Table 8.5.7.3.3-1 describes information elements in the PIN discovery response from the PEMC/PIN server to PINE.
Table 8.5.7.3.3-1: PIN discovery response
Information element
Status
Description
Successful response
O
(see NOTE)
Indicates that the PIN discovery request was successful.
> PIN IDs
M
Identifier o... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8 PINE management
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.1 General
| After the PIN is created by the PEMC, the other PIN elements can be added into the PIN. For the PIN elements that have already added into the PIN, they can be removed from a certain PIN by the PEMC.
When a PIN element is added into a PIN, the PEMC should configure the PIN elements with the necessary permission, for e... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.2.1 PIN client requests to join into a PIN
| Figure 8.5.8.2.1-1 illustrates procedure of PIN client requests to join into a PIN, based on request/response model.
Pre-conditions:
1. The UE (PIN client) has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PEMC;
2. The UE Identifier or PIN client Identifier is available;
3. T... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.2.2 Procedure of PIN elements decides to leave the PIN
| The following procedure defines the PIN elements decides to leave the PIN.
Pre-conditions:
1. The PIN client has already been added into a PIN;
2. The UE Identifier or PIN client Identifier is available;
3. The PIN client has been authorized to communicate with the PEMC and already has the application layer connec... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.2.3 Procedure of PEMC removes the PIN elements from a PIN
| The following procedure defines the PIN elements decides to leave the PIN.
Pre-conditions:
1. The PIN client has already been added into a PIN;
2. The UE Identifier or PIN client Identifier is available;
3. The PIN client has been authorized to communicate with the PEMC and already has the application layer connec... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.2.4 PINE join into PIN via PEGC
| The PINE joins the PIN via the PEGC is depicted in Figure 8.5.8.2.4-1.
Pre-conditions:
1. The PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PEMC;
2. The PINE already establishes the connection with PEGC;
3. The PIN information to join is available at the PINE via e.... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.2.5 PINE leave via PEGC
| The PINE leaves the PIN via the PEGC is depicted in figure 8.5.8.2.5-1.
Pre-conditions:
1. The PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PEMC or PIN server;
2. The PINE already establishes the connection with PEGC;
3. The PEGC acts as the application layer relay... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.2.6 PINE discovery within PIN
| Figure 8.5.8.2.6-1 illustrates procedure of PIN client requests to discover another PIN element, based on request/response model.
Pre-conditions:
1. The UE (PIN client) has already discovered PIN as specified in clause 8.5.7;
2. The UE (PIN client) has already joined the PIN as specified in clause 8.5.8.2.
3. The P... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.2.7 PINE Profile update within PIN
| Figure 8.5.8.2.7-1 illustrates procedure of PIN Element (PINE) to update its profile with the PEMC to indicate its willingness to support in PINE discovery procedure by another PINE.
Pre-conditions:
1. The UE (PINE) has already joined the PIN as specified in clause 8.5.8.2.
3. The PINE has been authorized to communi... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.3 Information flows
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.3.1 General
| The following information flows are specified for PIN creation:
- PIN Management PINE join into PIN request and response;
- PIN Management PINE leave from PIN request and response;
- PIN Management PINE discovery request and response;
- PIN Management PINE Profile update request and response;
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.3.2 PIN Management PINE join into PIN request
| Table 8.5.8.3.2-1 describes information elements in the PIN Management PINE join into PIN request from the PINE to PEMC, from PINE to PEGC, from PEGC to PEMC, from PIN server to PEMC.
Table 8.5.8.3.2-1: PIN Management PINE join into PIN request
Information element
Status
Description
PIN ID
M
Identifier of the P... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.3.3 PIN Management PINE join into PIN response
| Table 8.5.8.3.3-1 describes information elements in the PIN Management PINE join into PIN response from the PEMC to PINE, from PEGC to PINE, from PEMC to PEGC, from PEMC to PIN server.
Table 8.5.8.3.3-1: PIN Management PINE join into PIN response
Information element
Status
Description
Successful response
O
(see... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.3.4 PIN Management PINE leave from PIN request
| Table 8.5.8.3.4-1 describes information elements in the PIN Management PINE leave from PIN request from the PINE to PEMC.
Table 8.5.8.3.4-1: PIN Management PINE leave from PIN request
Information element
Status
Description
PIN ID
M
Identifier of the PIN that wants to leave from.
Security credentials
M
Securi... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.3.5 PIN Management PINE leave from PIN response
| Table 8.5.8.3.5-1 describes information elements in the PIN Management PINE leave from PIN response from the PEMC to PINE.
Table 8.5.8.3.5-1: PIN Management PINE leave from PIN response
Information element
Status
Description
Successful response
O
(see NOTE)
Indicates that the PIN Management PINE leave from PIN... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.3.6 PIN Management PINE discovery request
| Table 8.5.8.3.6-1 shows the request sent by a PIN client of a PIN element to a PEMC for the PIN element discovery request.
Table 8.5.8.3.6-1: PIN Management PINE discovery request
Information element
Status
Description
PIN ID
M
Identifier of the PIN that wants to join in.
Security credentials
M
Security cred... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.3.7 PIN Management PINE discovery response
| Table 8.5.8.3.7-1 shows the response sent by the PEMC to the requester for a PIN element discovery response.
Table 8.5.8.3.7-1: PIN Management PINE discovery response
Information element
Status
Description
Status
M
The status for the request (e.g., success or fail), including failure reason if needed.
Discover... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.3.8 PIN Management PINE Profile update request
| Table 8.5.8.3.8-1 shows the request sent by a PINE client to a PEMC client for the PINE profile update.
Table 8.5.8.3.8-1: PIN Management PINE Profile update request
Parameter Name
Status
Parameter Description
PIN ID
M
The identifier of the PIN to which the PIN element wants to join
UE identifier
O
PIN Eleme... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.8.3.9 PIN Management PINE Profile update response
| Table 8.5.8.3.9-1 shows the response sent by the PEMC to the PINE.
Table 8.5.8.3.9-1: PIN Management PINE Profile update response
Information element
Status
Description
Status
M
The status for the request (e.g., success or fail), including failure reason if needed.
> PIN client profile
O
Updated PIN client p... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9 PIN status subscription
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.1 General
| 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;
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.2.1 PIN status subscribe
| 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;
Figure 8.5.9.2.1-1: PIN status subscribe
1. The PINE/PEGC/PIN server sends the PIN st... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.2.2 PIN status notify
| 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.
Figure 8.5.9.2.2-1: PIN status notify procedure
1. When an event occurs at the PEMC that satisfies trigger conditions for notifyin... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.2.3 PIN status update
| 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 8.5.9.2.1;
Figure 8.5.9.2.3-1: PIN status update
1. The PINE/PEGC/PIN server sends a PIN status update request to the PEMC. The PIN st... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.2.4 PIN status unsubscribe
| 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 8.5.9.2.1;
Figure 8.5.9.2.4-1: PIN status unsubscribe
1. The PINE/PEGC/PIN server sends a PIN status unsubscribe request to the P... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.3 Information flows
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.3.1 General
| The following information flows are specified for PIN status:
- PIN status subscribe;
- PIN status notify;
- PIN status update;
- PIN status unsubscribe;
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.3.2 PIN status subscribe request
| Table 8.5.9.3.2-1: PIN status subscribe request
Information element
Status
Description
PIN client ID
M
Unique identifier of the PINE/PEGC/PIN server.
Subscribed Events IDs
M
Identifies PIN status event for which the subscriber is notified, more than one PIN status event IDs can be provided.
Event IDs:
- PI... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.3.3 PIN status subscribe response
| Table 8.5.9.3.3-1: PIN status subscribe response
Information element
Status
Description
Successful response
O
Indicates that the subscription request was successful.
> Subscription ID
M
Subscription identifier corresponding to the subscription.
> Expiration time
O
Indicates the expiration time of the subsc... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.3.4 PIN status notify
| Table 8.5.9.3.4-1 describes information elements in the PIN status notify from the PEMC to PEMC/PEGC/PINE/PIN server.
Table 8.5.9.3.4-1: PIN status notify
Information element
Status
Description
PIN Status event type
M
Identifies PIN status event types contained in the notification; more than one PIN status even... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.3.5 PIN status update request
| Table 8.5.9.3.5-1: PIN status update request
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription.
Security credentials
M
Security credentials resulting from a successful authorization for the PIN service.
PIN ID
M
The identifier of PIN.
Subscr... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.3.6 PIN status update response
| Table 8.5.9.3.6-1: PIN status update response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the subscription update request was successful.
> Expiration time
O
Indicates the expiration time of the subscription. To maintain an active subscription, a subscription update i... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.3.7 PIN status unsubscribe request
| Table 8.5.9.3.7-1: PIN status unsubscribe request
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription.
Security credentials
M
Security credentials resulting from a successful authorization for the PIN service.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.9.3.8 PIN status unsubscribe response
| Table 8.5.9.3.8-1: PIN status unsubscribe response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the unsubscribe request was successful.
Failure response (see NOTE)
O
Indicates that the unsubscribe request failed.
> Cause
M
Indicates the cause of unsubscribe request ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10 PIN modification
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.1 General
| This clause describes PIN modification functionality.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.2 Procedures
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.2.1 General
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.2.2 PIN modification after local PEMC failure
| Figure 8.5.10.2.2-1 describes the PIN modification procedure to perform a PEMC role change due to the failure of the PEMC. An authorised administrator is the owner of the PIN and accesses PIN configuration using an application on a UE, which is one of the PEMC for the PIN. The authorised administrator can manage the PI... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.2.3 PIN modification with PEGC role change
| Figure 8.5.10.2.3-1 describes a PIN modification procedure to perform a PEGC role change due to the unavailability of the PEGC. This procedure describes a PEMC detecting the unavailability of a PEGC (e.g. PEGC leaves the local service area of the PIN) and performing a PIN modification with the PIN Server to assign a ne... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.2.4 PEMC replacement triggered internally within the PIN
| A PIN element could have been authorized to act as PEMC for a certain duration after which it is either removed from the PIN or de-authorized to act as PEMC. Another PIN element in the PIN takes over the role of PEMC.
When the duration of its role as PEMC is expiring or for some other reasons (implementation specific)... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.2.5 PEGC replacement triggered by PEMC
| In some scenarios, like hardware failure, crash or power drain, the current PEGC may not be in a position to indicate to the PIN server or request the PIN server to assign the role of PEGC to another PIN element. In these cases, the PEMC on detecting the unavailability of the PIN element acting as PEGC, need to assign ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.3 Information flows.
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.3.1 General
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.3.2 PIN configuration request
| Table 8.5.10.3.2-1 shows the informational elements of the PIN configuration request sent by a PIN Element to the PIN server to obtain authorization for the modification of a PIN.
Table 8.5.10.3.2-1: PIN configuration request
Information element
Status
Description
PIN ID
M
The identifier of the PIN
Requester PI... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.3.3 PIN configuration response
| Table 8.5.10.3.3-1 shows the informational elements of the PIN configuration response provided by the PIN server to authorize the modification of a PIN.
Table 8.5.10.3.3-1: PIN configuration response
Information element
Status
Description
Response
M
The response (authorize or not authorize) from the PIN Server.
... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.3.4 PIN management request
| Table 8.5.10.3.4-1 shows the informational elements of the PIN management request sent to PIN elements to make changes to the configuration of the PIN.
Table 8.5.10.3.4-1: PIN management request
Information element
Status
Description
PIN ID
M
The identifier of the PIN
Requestor ID
M
The identifier of the PIN... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.3.5 PIN management response
| Table 8.5.10.3.5-1 shows the informational elements of the PIN management response received from the PIN element to the PIN modification request.
Table 8.5.10.3.5-1: PIN management response
Information element
Status
Description
Response
M
The response (accept or deny) from the PIN Element to the PIN management ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.3.6 PIN PEMC role takeover request
| Table 8.5.10.3.6-1 shows the informational elements of the PIN PEMC role takeover request sent from current PEMC of the PIN to another PIN element with PEMC capability.
Table 8.5.10.3.6-1: PIN PEMC role takeover request
Information element
Status
Description
PIN ID
M
The identifier of the PIN
Current PEMC ident... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.3.7 PIN PEMC role takeover response
| Table 8.5.10.3.7-1 shows the informational elements of the PIN PEMC role takeover response sent from requested PIN element to the current PEMC.
Table 8.5.10.3.7-1: PIN PEMC role takeover response
Information element
Status
Description
PIN ID
M
The identifier of the PIN
Success response (see NOTE)
O
Indicates ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.3.8 PIN PEGC role takeover request
| Table 8.5.10.3.8-1 shows the informational elements of the PIN PEGC role takeover request sent from current PEMC of the PIN to another PIN element with PEGC capability.
Table 8.5.10.3.8-1: PIN PEGC role takeover request
Information element
Status
Description
PIN ID
M
The identifier of the PIN
Current PEMC ident... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.10.3.9 PIN PEGC role takeover response
| Table 8.5.10.3.9-1 shows the informational elements of the PIN PEGC role takeover response sent from requested PIN element to the current PEMC.
Table 8.5.10.3.9-1: PIN PEGC role takeover response
Information element
Status
Description
PIN ID
M
The identifier of the PIN
Success response (see NOTE)
O
Indicates ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.11 PIN services management
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.11.1 General
| PIN elements can indicate the list of services it is offering at the time of joining the PIN by listing them as part of the PIN client profile. here could be scenarios wherein the PIN element may not be able to continue to provide the service(s) it indicated while joining or there could be scenarios where the PIN eleme... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.11.2 Procedures
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.11.2.1 PINE registering the services
| Figure 8.5.11.2.1-1 illustrates procedure of PIN element registering the new service(s).
Pre-conditions:
1. PIN is already created and the PIN entities PEGC, PINE-1, PINE-2, PINE-3 and PINE-4 are all part of the same PIN;
2. The PINE-4 is the PEMC of the PIN;
Figure 8.5.11.2.1-1: PINE registering the service(s)
... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.11.2.2 PINE de-registering the services
| Figure 8.5.11.2.2-1 illustrates procedure of PIN element de-registering the service(s).
Pre-conditions:
1. PIN is already created and the PIN entities PEGC, PINE-1, PINE-2, PINE-3 and PINE-4 are all part of the same PIN;
2. The PINE-4 is the PEMC of the PIN;
Figure 8.5.11.2.2-1: PINE de-registering the service(... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.11.3 Information flows.
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.11.3.1 General
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.11.3.2 PIN services registration request
| Table 8.5.11.3.2-1 shows the informational elements of the PIN services registration request sent by a PIN Element to the PEMC to register for new services it is offering.
Table 8.5.11.3.2-1: PIN services registration request
Information element
Status
Description
PIN ID
M
The identifier of the PIN
Requester PI... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.