Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑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.8 PINE management  8.5.8.1 General  8.5.8.2 Procedure  8.5.8.2.1 PIN client requests to join into a PIN  8.5.8.2.2 Procedure of PIN elements decides to leave the PIN  8.5.8.2.3 Procedure of PEMC removes the PIN elements from a PIN  8.5.8.2.4 PINE join into PIN via PEGC  8.5.8.2.5 PINE leave via PEGC  8.5.8.3 Information flows  8.5.8.3.1 General  8.5.8.3.2 PIN Management PINE join into PIN request  8.5.8.3.3 PIN Management PINE join into PIN response  8.5.8.3.4 PIN Management PINE leave from PIN request  8.5.8.3.5 PIN Management PINE leave from PIN response 
...

 

8.5.8  PINE management  p. 55

8.5.8.1  General  p. 55

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 example, to be able to access to 5GS via the PEGC.
When a PIN element is added into a PIN, the PINE can indicate the service it can provide. The service includes both the service that PIN client in PINE can provide and the service that application client on PINE can provide.
Up

8.5.8.2  Procedure  p. 55

8.5.8.2.1  PIN client requests to join into a PIN  p. 55
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. The PIN client has been authorized to communicate with the PEMC and already has application layer connection with PEMC;
  4. The PIN client has already received the list of PIN ID, corresponding PEMC IP address and configuration information related to each PIN;
Reproduction of 3GPP TS 23.542, Fig. 8.5.8.2.1-1: PIN client requests to join into a PIN
Figure 8.5.8.2.1-1: PIN client requests to join into a PIN
Up
Step 1.
The PIN client sends the PIN Management PINE join into PIN request to PEMC to join the PIN. The request includes the security credentials of the PIN client received during authorization procedure and may include the UE identifier such as GPSI, PIN client ID, UE location, PIN ID and PIN client profile(s) information as defined in clause 8.5.8.3.2.
The request also includes service that PINE can provide. In the request, both the service that PIN client in PINE can provide and the service that application client on PINE can provide.
Step 2.
Upon receiving the request, the PEMC performs an authorization check to verify whether the PIN client has authorization to join the PIN. The authorization procedure is defined in clause 8.10.
Step 3.
The PEMC sends a successful PIN Management PINE join into PIN response to PIN client. Also, the access control information for the PIN client is also included, for example, user name, account, SSID, BSSID. All the information is used by PIN elements in PIN to access 5G or access the network provided by PEGC. The PEMC also provides lifetime of the PIN, identity, address of PEGC and may also provide unique PIN client ID to identify the PIN element within a PIN.
Step 4.
The PEMC sends PIN status notify to the PIN server containing the details of the new PIN client that joined the PIN, including PIN client ID, GPSI and etc.
Step 5.
The PEMC sends PIN status notify to the PEGC and other PIN elements that subscribed for PIN status notification which contains the details of the new PIN client that joined the PIN. And the PEGC decides to enables the PINE to access 5GS.
Step 6-8.
The PEMC/PEGC/PINE updates PIN profile with the details of the new PIN client that joined the PIN and the service that the PINE can provide.
Up
8.5.8.2.2  Procedure of PIN elements decides to leave the PIN  p. 56
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 connection with the PEMC;
Reproduction of 3GPP TS 23.542, Fig. 8.5.8.2.2-1: PIN client decides to leave a PIN
Figure 8.5.8.2.2-1: PIN client decides to leave a PIN
Up
Step 1.
The PINE decides to leave a PIN, and sends the PIN Management PINE leave from PIN request to PEMC to leave the PIN. The request includes the security credentials of the UE or PIN client received during authorization procedure and may include the UE identifier such as GPSI, PIN client ID, UE location and PIN ID.
Step 2.
The PEMC authorizes the request, and decides to remove a PIN client from a PIN which indicated by PIN client ID or UE GPSI. The authorization procedure is defined in clause 8.10.
Step 3.
The PEMC sends the PIN Management PINE leave from PIN response to PINE to notify that the PIN client is not the member of the PIN anymore.
Step 4-5.
The PEMC sends the PIN status notify Request to the PEGC, PIN server and PIN elements that subscribed for PIN status notification which contains the details of the PIN client that requested to leave the PIN. The details of the PINE include PIN client ID, GPSI and etc.
Step 6-8.
The PEMC/PEGC/PIN server updates the dynamic profile information of the PIN to remove the details of the PIN client that requested to leave the PIN. The PEGC disables the access control information for this PINE. The PEGC stops relaying traffic to the PINE.
Up
8.5.8.2.3  Procedure of PEMC removes the PIN elements from a PIN  p. 57
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 connection with PEMC;
Reproduction of 3GPP TS 23.542, Fig. 8.5.8.2.3-1: Remove a PIN element from a PIN by PEMC
Figure 8.5.8.2.3-1: Remove a PIN element from a PIN by PEMC
Up
Step 1.
The PEMC decides to remove the PINE (identified by GPSI, PIN client ID and in certain PIN identified by PIN ID).
Step 2.
The PEMC sends the PIN status notify to the PINE that this PINE has been removed from the PIN that identified by PIN ID.
Step 3-4.
The PEMC sends the PIN status notify to the PEGC, PIN elements subscribed for PIN status notification and PIN server containing the details of the PIN client that is removed from the PIN. The details of the PINE include PIN client ID, GPSI and etc.
Step 5-7.
The PEMC/PEGC/PIN server updates the dynamic profile information of the PIN to remove the details of the PIN client that is removed from the PIN. The PEGC disables the access control information for this PINE. The PEGC stops relaying traffic to the PINE.
Up
8.5.8.2.4  PINE join into PIN via PEGC  p. 58
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.g., PIN discovery procedure.
Reproduction of 3GPP TS 23.542, Fig. 8.5.8.2.4-1: PINE join into PIN via PEGC
Figure 8.5.8.2.4-1: PINE join into PIN via PEGC
Up
Step 1.
The PINE sends PIN Management PINE join into PIN request to the PEGC. The PIN Management PINE join into PIN request contains the PIN ID which identifies the PIN to join, PINE client ID and credentials if available, PEMC identity/PIN server address.
The request also includes service that PINE can provide.
Step 2.
The PEGC identifies the received message is the PIN Management PINE join into PIN request and perform the authorization. If authorized, the PEGC determines to forward the PIN Management PINE join into PIN request to the PEMC or the PIN server.
If authorization in PEGC is failed, directly skip to step 6.
The PEGC can decide to perform either Option 1 (from step 3a to step 3b) or Option 2 (from step 4a to step 4d). If direct communication between PEGC and PEMC always available, the PEGC performs Option 1.
Step 3.
(Option 1, step 3a and step 3b) The PEGC forwards the PIN Management PINE join into PIN request to the PEMC in step 3a, based on the PEMC identity in step 1 or by resolving the PIN ID. The PEMC authorized the PINE to join the PIN, and returns the PIN Management PINE join into PIN response to the PEGC in step 3b.
Step 4.
(Option 2, from step 4a to step 4d) The PEGC forwards the PIN Management PINE join into PIN request to the PIN server in step 4a based on the PIN server address in step 1 or by resolving the PIN ID. The PIN server forwards the PIN Management PINE join into PIN request to the PEMC in step 4b, and the PEMC authorized the PINE to join the PIN, and returns the PIN Management PINE join into PIN response to the PIN server in step 4c. Further the PIN server return the PIN server to the PEGC in step 4d.
Step 5.
After the join, the PEMC update the PIN and may notify other entities (e.g., existing joined members, PIN server). The PEMC triggers the PIN status notify to PEGC/PINE as indicated in step 5-6 of procedure Figure 8.5.8.2.2-1.
Step 6.
The PEGC return the PIN Management PINE join into PIN response to the PINE.
If authorization in PEGC is failed, PEGC generates the PIN Management PINE join into PIN response to the PINE for the authorization failure.
Up
8.5.8.2.5  PINE leave via PEGC  p. 59
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 as defined in 6.3.4
Reproduction of 3GPP TS 23.542, Fig. 8.5.8.2.5-1: PINE leave via the PEGC
Figure 8.5.8.2.5-1: PINE leave via the PEGC
Up
Step 1.
The PINE determines to leave the PIN and sends PIN Management PINE leave from PIN request to the PEGC. The PIN Management PINE leave from PIN request contains the PIN ID which identifies the PIN to leave, PINE client ID and credentials if available, PEMC identify/PIN server address[optional].
Step 2.
The PEGC identifies the received message is the PIN Management PINE leave from PIN request and perform the authorization. If authorized, the PEGC determines to forward the PIN leave request to the PEMC or the PIN server.
If authorization in PEGC is failed, directly skip to step 6.
The PEGC can decide to perform either Option 1 (from step 3a to step 3b) or Option 2 (from step 4a to step 4d). If direct communication between PEGC and PEMC always available, the PEGC performs Option 1.
Step 3.
(Option 1, step 3a and step 3b) If PEGC determine to forward the PIN Management PINE leave from PIN request to the PEMC in step 2, PEGC forwards the PIN Management PINE leave from PIN request to the PEMC based on the PEMC identity in step 1 or by resolving the PIN ID.
The PEMC authorized the PINE to leave the PIN, and returns the PIN Management PINE leave from PIN response to the PEGC.
Step 4.
(Option 2, step 4a and step 4d) If PEGC determine to forward the PIN Management PINE leave from PIN request to the PIN Sever in step2, the PEGC forwards the PIN Management PINE leave from PIN request to the PIN server based on the PIN server address in step 1 or by resolving the PIN ID. The PIN server forwards the PIN Management PINE leave from PIN request to the PEMC, and the PEMC authorized the PINE to leave the PIN, and returns the PIN Management PINE leave from PIN response to the PIN server. Further the PIN server return the PIN Management PINE leave from PIN response to the PEGC.
Step 5.
Further, the PEMC updates the PIN and may notify other entities (e.g., existing joined members, PIN server).
Step 6.
The PEGC returns the PIN Management PINE leave from PIN response to the PINE. The PEGC disables the access control information for this PINE. The PEGC stops relaying traffic to the PINE.
If authorization in PEGC is failed, PEGC generates the PIN Management PINE leave from PIN response to the PINE for the authorization failure.
Up

8.5.8.3  Information flows  p. 61

8.5.8.3.1  General  p. 61
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;
8.5.8.3.2  PIN Management PINE join into PIN request  p. 61
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.
Information element Status Description
PIN IDMIdentifier of the PIN that wants to join in.
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
PIN client IDMThe PIN client ID of PINE.
PEMC IDOIdentifier of the PEMC that PEGC should send request to.
UE IdentifierMThe identifier of the hosting UE (i.e. GPSI or identity token) or the PIN client ID of PEMC.
PIN client profile(s)O Profiles of PIN clients. The PIN client profiles are further described in Table 8.2.2.3-1.
PIN server endpoint informationOIncludes URI(s), FQDN(s), IP address(es)) of PIN server.
UE locationOThe location information of the UE. The UE location is described in clause 7.2.7.
Services that PINE provideOIndicate the service that PINE can provide.
Up
8.5.8.3.3  PIN Management PINE join into PIN response  p. 61
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.
Information element Status Description
Successful responseO
(see NOTE)		Indicates that the PIN Management PINE join into PIN request was successful.
> Updated PIN client profileOPIN client profile information updated by the PEMC (e.g., default and backup PEGCs assigned to PINE).
> Heartbeat TimerMHeartbeat timer value assigned to PINE
> Lifetime of the PINMIndicates the lifetime of PIN.
> Identifier of PEGCsOIndicates the PINE identifier authorized to be the PEGCs of this PIN.
>> PEGC addressOAssigned IP address or port number of PEGC.
> PEGC informationOIncludes the PEGC information for example.
>> Access control informationOIncludes: user name, account, SSID, BSSID. All the information is used by PIN elements in PIN to access 5G or access other application outside of PIN.
Failure responseO
(see NOTE)		Indicates that the PIN Management PINE join into PIN request failed.
> CauseMProvides the cause for PIN Management PINE join into PIN request failure.
NOTE:
At least one of the IE shall be present.
Up
8.5.8.3.4  PIN Management PINE leave from PIN request  p. 62
Table 8.5.8.3.4-1 describes information elements in the PIN Management PINE leave from PIN request from the PINE to PEMC.
Information element Status Description
PIN IDMIdentifier of the PIN that wants to leave from.
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
PIN client IDMThe PIN client ID of PINE.
UE IdentifierMThe identifier of the hosting UE (i.e. GPSI or identity token) or the PIN client ID of PEMC.
Up
8.5.8.3.5  PIN Management PINE leave from PIN response  p. 62
Table 8.5.8.3.5-1 describes information elements in the PIN Management PINE leave from PIN response from the PEMC to PINE.
Information element Status Description
Successful responseO
(see NOTE)		Indicates that the PIN Management PINE leave from PIN request was successful.
Failure responseOIndicates that the PIN Management PINE leave from PIN request failed.
> CauseM
(see NOTE)		Provides the cause for PIN Management PINE leave from PIN request failure.
NOTE:
At least one of the IE shall be present.
Up

Up   Top   ToC