hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.12.3.1 General
| The PIN heartbeat information flow is specified for the PIN heartbeat.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.12.3.2 PIN heartbeat
| Table 8.5.12.3.2-1: PIN heartbeat
Information element
Status
Description
PIN client ID
M
Unique identifier of the PINE/PEGC/PEMC.
PIN ID
M
Identifier of the PIN.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.13 PIN activation and deactivation
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.13.1 General
| The procedures in this clause describes how a PEMC can activate and deactivate the PIN. PEMC being an authorized entity to manage the PIN can request to activate and deactivate the PIN. When the PIN is in deactivated state, services offered by the PIN are inaccessible and no PIN elements can join the PIN. Also PEGC clo... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.13.2 Procedure
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.13.2.1 PIN activation
| Figure 8.5.13.2.1-1 illustrates a procedure for activating the PIN by PEMC.
Pre-conditions:
1. PEMC(PINE-3), PEGC, PINE-1 and PINE-2 all are part of same PIN
2. The PIN being activated has already been created earlier and is in the deactivated state.
3. The PINE-3 is authorized as PEMC of the PIN.
4. PIN server, ... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.13.2.2 PIN de-activation
| Figure 8.5.13.2.2-1 illustrates a procedure for de-activating the PIN by PEMC.
Pre-conditions:
1. PEGC, PINE-1, PINE-2 and PINE-3 are part of same PIN, which is created earlier and is now in activated state.
2. The PINE-3 is authorized as PEMC.
3. PEMC (PINE-3) decides to de-activate the PIN.
4. PIN server, PEGC a... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14 PIN connectivity subscription
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.1 General
| 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.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.2 Procedure
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.2.1 PIN connectivity subscribe
| 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;
Figure 8.5.14.2.1-1: PIN connectivity subscribe
1. The subscriber sen... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.2.2 PIN connectivity notify
| 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.
Figure 8.5.14.2.2-1: PIN connectivity notify procedure
1. When an event occur... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.2.3 PIN connectivity update
| 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;
Figure 8.5.14.2.3-1: PIN connectivity update
1. The subscriber sends a PIN connectivity up... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.2.4 PIN connectivity unsubscribe
| 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;
Figure 8.5.14.2.4-1: PIN connectivity update
1. The subscriber sends a PIN connectivi... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.3 Information flows
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.3.1 General
| The following information flows are specified for PIN connectivity subscription:
- PIN connectivity subscribe
- PIN connectivity notify
- PIN connectivity update
- PIN connectivity unsubscribe
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.3.2 PIN connectivity subscribe request
| Table 8.5.14.3.2-1: PIN connectivity subscribe request
Information element
Status
Description
Subscriber identifier
M
Unique identifier of the PINE/PEMC/PIN server.
Security credentials
M
Security credentials resulting from a successful authorization for the PIN service.
PIN ID
M
The identifier of PIN.
No... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.3.3 PIN connectivity subscribe response
| Table 8.5.14.3.3-1: PIN connectivity 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 th... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.3.4 PIN connectivity notify
| Table 8.5.14.3.4-1 describes information elements in the PIN connectivity notification from the PEGC.
Table 8.5.14.3.4-1: PIN connectivity notification
Information element
Status
Description
PEGC identifier
M
Identifier of the PEGC
PIN identifier
M
Identifier of the PIN.
PIN client identifier
M
Unique ide... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.3.5 PIN connectivity update request
| Table 8.5.14.3.5-1: PIN connectivity 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.
Notification Target Address
O
Th... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.3.6 PIN connectivity update response
| Table 8.5.14.3.6-1: PIN connectivity 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 u... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.3.7 PIN connectivity unsubscribe request
| Table 8.5.14.3.7-1: PIN connectivity 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.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.5.14.3.8 PIN connectivity unsubscribe response
| Table 8.5.14.3.8-1: PIN connectivity 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 r... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6 PIN enable 5GS communication
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.1 General
| For a certain PINE in PIN, the PEMC controls whether to allow or forbid the PINEs to communicate with other PINEs via PEGC directly or communicate with other PINEs via PEGC by 5GS. Also, the PEMC controls whether to allow or forbid the traffic from network sides to deliver to certain PINE.
The PIN client within a PIN... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.2 Procedure
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.2.1 AF trigger QoS establishment
| For the AF related procedure, the AF trigger the QoS create/modification procedure as defined in Section 4.15.6.6 of TS 23.502[5] with parameters of Packet filters (that related to the PINEs needs communication), DN specific ID, to request the 5GS to arrange resource for PIN.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.2.2 Procedures of PIN communication via 5GS triggered by PEGC
| Pre-conditions:
1. The PINE already has application layer connection with PEGC;
2. The UE Identifier or PIN client Identifier is available for PINE;
3. The PIN client has been authorized to communicate with PEMC;
4. The PINE has the subscription that it can communicate via 5GS;
5. The PINE has already received the... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.3 Information flows
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.3.1 General
| The following information flows are specified for PIN communication:
- PIN Communication Create/Update/Remove Request and response;
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.3.2 PIN Communication Create Request
| Table 8.6.3.2-1 shows the informational elements of the PIN Communication Create request sent by a PIN Element/PEMC to the PEGC to provide the PIN communication information.
Table 8.6.3.2-1: PIN Communication Create request
Information element
Status
Description
PIN ID
M
The identifier of the PIN
Requester PINE... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.3.3 PIN Communication Create Response
| Table 8.6.3.3-1 shows the informational elements of the PIN Communication Create response sent by a PEGC to the PINE/PEMC.
Table 8.6.3.3-1: PIN Communication Create response
Information element
Status
Description
Successful response
O
(see NOTE)
Indicates that the PIN communication creation request was successf... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.3.4 PIN Communication Update Request
| Table 8.6.3.4-1 shows the informational elements of the PIN Communication Update request sent by a PIN Element/PEMC to the PEGC to provide the updated PIN communication information.
Table 8.6.3.4-1: PIN Communication Update request
Information element
Status
Description
PIN ID
M
The identifier of the PIN
Reques... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.3.5 PIN Communication Update Response
| Table 8.6.3.5-1 shows the informational elements of the PIN Communication Update response sent by a PEGC to the PINE/PEMC.
Table 8.6.3.5-1: PIN Communication Create response
Information element
Status
Description
Successful response
O
(see NOTE)
Indicates that the PIN communication update request was successful... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.3.6 PIN Communication Delete Request
| Table 8.6.3.6-1 shows the informational elements of the PIN Communication Delete request sent by a PIN Element/PEMC to the PEGC to delete the PIN communication.
Table 8.6.3.4-1: PIN Communication Delete request
Information element
Status
Description
PIN ID
M
The identifier of the PIN
Requester PINE ID/PEMC
M
... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.6.3.7 PIN Communication Delete Response
| Table 8.6.3.7-1 shows the informational elements of the PIN Communication Delete response sent by a PEGC to the PINE/PEMC.
Table 8.6.3.7-1: PIN Communication Delete response
Information element
Status
Description
Successful response
O
(see NOTE)
Indicates that the PIN communication delete was successful.
Failu... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7 Service Switch
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.1 General
| PIN service switch procedures enable a PIN Element participating in a PIN to transfer application session(s) to a different PIN Element participating in the same PIN. For example, a first PIN Element (e.g. a UE) can transfer a video streaming session to a second PIN Element (e.g. a television). PIN service switch can b... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2 Procedure
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1 Service switch in a PIN with PIN server support
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1.1 General
| Following procedures are supported for service switch in a PIN with PIN server support:
- PIN Service Switch procedure;
- PIN Service Switch Configure procedure;
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1.2 PIN Service Switch procedure
| Pre-conditions:
1. The PIN Client established an application session with an Application Server;
2. The PIN Client joined a PIN.
Figure 8.7.2.1.2-1: PIN Service Switch procedure
1. The PIN Client sends a PIN Service Switch request to the PIN Server. The PIN Service Switch request includes the requestor identifier... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1.3 PIN Service Switch Configure procedure
| Pre-conditions:
1. The PIN Client successfully requested a service switch with the PIN Server
2. The AS is successfully subscribed for PIN service switch notifications with the PIN server.
Figure 8.7.2.1.3-1: PIN Service Switch Configure procedure
1. The PIN Server sends the PIN Configuration Service Switch Con... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1.4 PIN Service Switch subscription
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1.4.1 General
| The PIN service switch subscription is used by the Application Server to be notified of PIN service switch events by the PIN Server.
The PIN service switch notification events includes PIN service switch configuration information.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1.4.2 Procedure
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1.4.2.1 PIN service switch subscribe
| Figure 8.7.2.1.4.2.1-1 illustrates the PIN service switch subscribe procedure.
Pre-conditions:
1. The application server has already received the address of the PIN server;
2. The application server is authorized to communicate with PIN server;
Figure 8.7.2.1.4.2.1-1: PIN service switch subscribe
1. The applica... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1.4.2.2 PIN service switch notify
| Figure 8.7.2.1.4.2.2-1 illustrates the PIN service switch notify procedure.
Pre-conditions:
1. The application server has subscribed with the PIN server as specified in clause 8.7.2.1.4.2.1.
Figure 8.7.2.1.4.2.2-1: PIN service switch notify procedure
1. When a service switch event occurs at the PIN server that s... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1.4.2.3 PIN service switch update
| Figure 8.7.2.1.4.2.3-1 illustrates the PIN service switch update procedure.
Pre-conditions:
1. The application server has subscribed with the PIN server as specified in clause 8.7.2.1.4.2.1.
Figure 8.7.2.1.4.2.3-1: PIN service switch update
1. The application server sends a PIN service switch update request to th... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.1.4.2.4 PIN service switch unsubscribe
| Figure 8.7.2.1.4.2.4-1 illustrates the PIN service switch unsubscribe procedure.
Pre-conditions:
1. The application server has subscribed with the PIN server as specified in clause 8.7.2.1.4.2.1.
Figure 8.7.2.1.4.2.4-1: PIN service switch unsubscribe
1. The application server sends a PIN service switch unsubscrib... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.2.2 Service switch in a PIN without PIN server support
|
Figure 8.7.2.2-1: PIN Service Switch internal PIN
In Figure 8.7.2.2-1, it describes the service switch scenario supported internal PIN.
The PINE A has the application communication with application server. And when the PINE A decides to select other alternative PINE B to apply the traffic flow, the PINE A firstly ... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3 Information flows
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.1 General
| The following information flows are specified for Service Switch:
- PIN service switch request and response
- PIN configuration service switch configure request and response
- PIN management service switch configure request and response
- PIN service discovery request and response
- PIN service switch subscribe
-... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.2 PIN service switch request
| Table 8.7.3.2-1 describes information elements for the PIN service switch request that is sent from the PIN client to the PIN server.
Table 8.7.3.2-1: PIN service switch request
Information element
Status
Description
PIN client identifier
M
Requestor identifier.
Security credentials
M
Security credentials of ... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.4 PIN configuration service switch configure request
| Table 8.7.3.4-1 describes information elements for the PIN configuration service switch configure request that is sent from the PIN server to the PIN management client.
Table 8.7.3.4-1: PIN configuration service switch configure request
Information element
Status
Description
PIN server identifier
M
Requestor ide... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.5 PIN configuration service switch configure response
| Table 8.7.3.5-1 describes information elements for the PIN configuration service switch configure response.
Table 8.7.3.5-1: PIN configuration service switch configure response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the request was successful.
Failure response (se... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.7 PIN management service switch configure response
| Table 8.7.3.7-1 describes information elements for the PIN management service switch configure response.
Table 8.7.3.7-1: PIN management service switch configure response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the request was successful.
Failure response (see NOTE... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.8 PIN Service Discovery Request
| Table 8.7.3.8-1 shows the informational elements of the PIN Service Discovery Request sent by a PIN Element to the PEMC to discover the candidate PINEs that can provide the certain PIN service.
Table 8.7.3.8-1: PIN Service Discovery Request
Information element
Status
Description
PIN ID
M
The identifier of the PI... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.9 PIN Service Discovery Response
| Table 8.7.3.9-1 shows the informational elements of the PIN Service Discovery Response sent by a PEMC to the PINE to list the candidate PINEs that can provide the target PIN service. The candidate PINEs that can provide the target PIN service may be multiple.
Table 8.7.3.9-1: PIN Service Discovery Response
Informati... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.10 PIN service switch subscribe request
| Table 8.7.3.10-1: PIN service switch subscribe request
Information element
Status
Description
Application server ID
M
Unique identifier of the application server.
Security credentials
M
Security credentials resulting from a successful authorization for the PIN service.
PIN ID
M
The identifier of PIN.
Subs... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.11 PIN service switch subscribe response
| Table 8.7.3.11-1: PIN service switch subscribe response
Information element
Status
Description
Successful response
(see NOTE)
O
Indicates that the subscription request was successful.
> Subscription ID
M
Subscription identifier corresponding to the subscription.
> Expiration time
O
Indicates the expiratio... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.12 PIN service switch notify
| Table 8.7.3.12-1 describes information elements in the PIN service switch notification from the PIN server to application server.
Table 8.7.3.12-1: PIN service switch notification
Information element
Status
Description
PIN subscription identifier
M
Identifier of the subscription
Subscribed event
M
Identifies... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.13 PIN service switch update request
| Table 8.7.3.13-1: PIN service switch 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
O
PIN identifier
Subscri... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.14 PIN service switch update response
| Table 8.7.3.14-1: PIN service switch 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 u... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.15 PIN service switch unsubscribe request
| Table 8.7.3.15-1: PIN service switch 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.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.3.16 PIN service switch unsubscribe response
| Table 8.7.3.16-1: PIN service switch 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 r... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.4 APIs
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.4.1 General
| Table 8.7.4.1-1 illustrates the API for AS service switch subscription.
Table 8.7.4.1-1: Ppinserver_ASServiceSwitchSubscription API
API Name
API Operations
Operation
Semantics
Consumer(s)
Ppinserver_ASServiceSwitch
Subscribe
Subscribe/Notify
AS
Notify
Update
Unsubscribe
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.4.2 Ppinserver_ ASServiceSwitch_Subscribe operation
| API operation name: Ppinserver_ASServiceSwitch_Subscribe
Description: The consumer subscribes for service switch information.
Inputs: See clause 8.7.3.10.
Outputs: See clause 8.7.3.11.
See clause 8.7.2.1.4.2.1 for details of usage of this operation.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.4.3 Ppinserver_ ASServiceSwitch_Notify operation
| API operation name: Ppinserver_ASServiceSwitch_Notify
Description: The consumer is notified with service switch information.
Inputs: See clause 8.7.3.12.
Outputs: None.
See clause 8.7.2.1.4.2.2 for details of usage of this operation.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.4.4 Ppinserver_ ASServiceSwitch_ Update operation
| API operation name: Ppinserver_ASServiceSwitch_Update
Description: The consumer updates an existing subscription for service switch information.
Inputs: See clause 8.7.3.13.
Outputs: See clause 8.7.3.14.
See clause 8.7.2.1.4.2.3 for details of usage of this operation.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.7.4.5 Ppinserver_ ASServiceSwitch_ Unsubscribe operation
| API operation name: Ppinserver_ASServiceSwitch_Unsubscribe
Description: The consumer cancels an existing subscription for service switch information.
Inputs: See clause 8.7.3.15.
Outputs: See clause 8.7.3.16.
See clause 8.7.2.1.4.2.4 for details of usage of this operation.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.8 Application server discovery and registration in PIN
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.1 General
| The PEMC and PIN Server have capabilities for maintaining information related to application servers that may be available to the PINE(s) within a PIN. Application server information may be pre-provisioned in the PIN Server or the PEMC; the application server may also register with the PEMC or the PIN Server if it has ... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.2 Procedure
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.2.1 General
| The follosing procedures are specified for AS discovery in PIN:
- AS discovery;
- AS registration;
- AS registration update;
- AS de-registration;
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.2.2 AS discovery
| Figure 8.8.2.2-1 illustrates the AS discovery procedure between the PINE and the PEMC and between the PEMC and the PIN Server. This procedure enables the PEMC to provide AS connectivity information to the PINE when requested by the PINE.
Pre-conditions:
1. The PINE has joined the PIN and is authorized to communicate ... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.2.3 AS registration
| Figure 8.8.2.3-1 illustrates the AS registration procedure between the AS and the PEMC or PIN Server. This procedure enables the AS to provide AS connectivity information to the PEMC or the PIN Server.
Pre-conditions:
1. The AS is authorized to communicate with the PEMC or the PIN Server;
Figure 8.8.2.3-1: AS regi... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.2.4 AS registration update
| Pre-conditions:
1. The AS has registered with the PEMC or PIN Server;
2. The AS has determined that its existing registration needs to be updated;
Figure 8.8.2.4-1: AS registration update procedure
1. The AS sends an AS registration update request to the PEMC or PIN Server where it registered. The request shall ... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.2.5 AS de-registration
| Pre-conditions:
1. The AS has registered with the PEMC or PIN Server;
2. The AS has determined that de-registration is required;
Figure 8.8.2.5-1: AS de-registration procedure
1. The AS sends an AS de-registration request to the PEMC or PIN Server where it registered. The request shall include the AS registratio... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.3 Information flows
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.3.1 General
| The following information flows are specified for AS discovery:
- AS discovery request and response;
- AS registration request and response;
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.3.2 AS discovery request
| Table 8.8.3.2-1 describes information elements for the AS discovery request from the PINE to the PEMC or from the PEMC to the PIN Server.
Table 8.8.3.2-1: AS discovery request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor instance (e.g., PINE ID)
Security credenti... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.3.3 AS discovery response
| Table 8.8.3.3-1 describes information elements for the AS discovery response from the PEMC to the PINE or from the PIN Server to the PEMC.
Table 8.8.3.3-1: AS discovery response
Information element
Status
Description
Successful response
O
Indicates that the AS discovery request was successful.
> AS connectivity... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.3.4 AS registration request
| Table 8.8.3.4-1 describes information elements for the AS registration request from the AS to the PEMC or the PIN Server.
Table 8.8.3.4-1: AS registration request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor instance (e.g., AS ID)
Security credentials
M
Securit... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.3.5 AS registration response
| Table 8.8.3.5-1 describes information elements for the AS registration response from the PEMC or PIN Server to the AS.
Table 8.8.3.5-1: AS registration response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the AS registration request was successful.
> AS registration id... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.3.6 AS registration update request
| Table 8.8.3.6-1 describes information elements for the AS registration update request from the AS to the PEMC or the PIN Server.
Table 8.8.3.6-1: AS registration update request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor instance (e.g., AS ID)
AS registration id... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.3.7 AS registration update response
| Table 8.8.3.7-1 describes information elements for the AS registration update response from the PEMC or PIN Server to the AS.
Table 8.8.3.7-1: AS registration update response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the AS registration update request was successful.
... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.3.8 AS de-registration request
| Table 8.8.3.8-1 describes information elements for the AS de-registration request from the AS to the PEMC or the PIN Server.
Table 8.8.3.8-1: AS de-registration request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor instance (e.g., AS ID)
AS registration identifier... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.3.9 AS de-registration response
| Table 8.8.3.9-1 describes information elements for the AS de-registration response from the PEMC or PIN Server to the AS.
Table 8.8.3.9-1: AS de-registration response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the AS de-registration request was successful.
Failure res... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.4 APIs
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.8.4.1 General
| Table 8.8.4.1-1 illustrates the API for AS registration.
Table 8.8.4.1-1: Ppinserver_ASRegistration API
API Name
API Operations
Operation
Semantics
Consumer(s)
Ppinserver_ASRegistration
Request
Request/Response
AS
Update
Deregister
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.4.4.2 Ppinserver_ASRegistration_Request operation
| API operation name: Ppinserver_ASRegistration_Request
Description: The consumer requests to register the AS on the PIN server.
Inputs: See clause 8.8.3.4.
Outputs: See clause 8.8.3.5.
See clause 8.8.2.3 for details of usage of this operation.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.4.4.3 Ppinserver_ASRegistration_Update operation
| API operation name: Ppinserver_ASRegistration_Update
Description: The consumer requests to update the registered information of the AS on the PIN server.
Inputs: See clause 8.8.3.6.
Outputs: See clause 8.8.3.7.
See clause 8.8.2.4 for details of usage of this operation.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.4.4.4 Ppinserver_ASRegistration_Deregister operation
| API operation name: Ppinserver_ASRegistration_Deregister
Description: The consumer requests to deregister the AS from the PIN server.
Inputs: See clause 8.8.3.8.
Outputs: See clause 8.8.3.9.
See clause 8.8.2.5 for details of usage of this operation.
|
06253d02247591cc2149faea837cc737 | 23.542 | 8.9 Service Continuity
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.9.1 General
| PIN service continuity procedures enable an Application Client participating in a PIN to maintain service when PIN Elements enter or leave the PIN. The following examples illustrate scenarios where PIN service continuity is needed.
In a first scenario, a first PIN Element (e.g. a UE) receives data from a second PIN E... |
06253d02247591cc2149faea837cc737 | 23.542 | 8.9.2 Procedure
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.9.2.1 Service continuity in PEGC relocation scenario
| |
06253d02247591cc2149faea837cc737 | 23.542 | 8.9.2.1.1 General
| Following procedures are supported for service continuity in a PEGC relocation scenario:
- PIN Management PEGC Service Continuity procedure;
- PIN Management PEGC Configuration procedure;
- PIN Configuration Service Continuity Update procedure;
- PIN Management PEGC Discovery procedure;
- PIN Service Continuity s... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.