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.6 PIN enable 5GS communication  8.6.1 General  8.6.2 Procedure  8.6.2.1 AF trigger QoS establishment  8.6.2.2 Procedures of PIN communication via 5GS triggered by PEGC  8.6.3 Information flows  8.6.3.1 General  8.6.3.2 PIN Communication Create Request  8.6.3.3 PIN Communication Create Response  8.6.3.4 PIN Communication Update Request  8.6.3.5 PIN Communication Update Response  8.6.3.6 PIN Communication Delete Request  8.6.3.7 PIN Communication Delete Response 
...

 

8.6  PIN enable 5GS communication  p. 87

8.6.1  General  p. 87

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 can communicate with other devices, services and applications within the same PIN. Furthermore, PIN client can connect the 5G Network via a PEGC. Also, as a feature, some of the PIN client in PIN has the permissions that they can communicate with other UE or application outside of PIN with the help of 5GC.
  • There are two methods to enable the PIN with 5GS communication:
  • Establish QoS for PINE with AF support.
  • PEGC triggers PDU session establishment/modification for PINE.
For the AF related procedure, the AF trigger the QoS create/modification procedure with parameters of Packet filters, DN specific ID, to request the 5GS to arrange resource for PIN.
For PEGC related procedure, the PIN element sends PIN Communication Request to the PEMC and the PEMC checks whether to allow or forbid the PINEs to communicate with other PINEs via PEGC directly or communicate with other PINEs via PEGC by 5GS. If the alloewd, the PEMC sends Create/Update/Remove Communication Request (PIN ID, Packet filters, requested QoS) to the PEGC. Or,the PEMC directly send Create/Update/Remove Communication Request (PIN ID, Packet filters, requested QoS) to the PEGC. The PEGC configures the local rule accordingly, or according to the Packet filters, the PEGC may initiate PDU Session Modification with the Packet filters and requested QoS towards 5G system in order to make 5GC configure the N4 rules for UPF(s).
Up

8.6.2  Procedure  p. 87

8.6.2.1  AF trigger QoS establishment  p. 87

For the AF related procedure, the AF trigger the QoS create/modification procedure as defined in clause 4.15.6.6 of TS 23.502 with parameters of Packet filters (that related to the PINEs needs communication), DN specific ID, to request the 5GS to arrange resource for PIN.

8.6.2.2  Procedures of PIN communication via 5GS triggered by PEGC  p. 87

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 IP address of other PINE.
  6. The communication between PEMC and PEGC is available.
  7. The PIN is in the activated state.
Reproduction of 3GPP TS 23.542, Fig. 8.6.2.2-1: Procedures of PIN communication via 5GS triggered by PEGC
Figure 8.6.2.2-1: Procedures of PIN communication via 5GS triggered by PEGC
Up
The PINE may have the traffic to send via 5GS communication.
Step 1a-1b.
The PINE sends PIN Communication Create/Update/Remove Request (PIN ID, MAC address/IP address, Traffic descriptors, Packet filters, requested QoS) to the PEMC in step 1a, and the PEMC checks whether to allow or forbid the PINEs to communicate with other PINEs via PEGC directly or communicate with other PINEs via PEGC by 5GS. If permitted, PEMC sends PIN Communication Create/Update/Remove Request to PEGC in step 1b. If not permitted, PEMC directly performs step 3b to indicate failure in PIN Communication Create/Update/Remove response.
After the PEGC receives the PIN Communication Create/Update/Remove Request, the PEGC configures the local rule accordingly.
Step 2.
[Optional] According to the Packet filters, the PEGC may initiate PDU Session Modification with the Packet filters and requested QoS towards 5G system in order to make 5GC configure the N4 rules for UPF(s).
Step 3a.
The PEGC sends PIN Communication Create/Update/Remove Response to the PEMC.
Step 3b.
If the request is triggered by PINE, step 3b is performed. The PEMC sends PIN Communication Create/Update/Remove Response to PINE.
After receiving successful response, the PINE sends data through the PEGC to the 5GS using the PDU session modified in step 2.
Up

8.6.3  Information flows  p. 88

8.6.3.1  General  p. 88

The following information flows are specified for PIN communication:
  • PIN Communication Create/Update/Remove Request and response;

8.6.3.2  PIN Communication Create Request  p. 89

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.
Information element Status Description
PIN IDMThe identifier of the PIN.
Requester PINE ID/PEMCMThe identifier of the PIN Element/PEMC making the request.
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
MAC address/IP addressOMAC address/IP address of PINE/PEMC.
Traffic descriptorsMIdentify the target traffic to/from application server or to/from PINE, e.g.: IP 5 Tuple.
Packet filtersMThe Packet Filter is used in PEGC to identify one or more packet flow(s), and the PEGC can route the traffic to the target application server/PINEs.
Request QoSOThe QoS (e.g.: packet delay or AMBR) of packet flow that requested by PINE.
Up

8.6.3.3  PIN Communication Create Response  p. 89

Table 8.6.3.3-1 shows the informational elements of the PIN Communication Create response sent by a PEGC to the PINE/PEMC.
Information element Status Description
Successful responseO
(see NOTE)		Indicates that the PIN communication creation request was successful.
> QoS informationMIncludes QoS information that agreed for this information flow.
> PIN communication flow IDMIncludes the communication flow that successfully established by PEGC.
Failure responseO
(see NOTE)		Indicates that the PIN communication creation request failed.
> CauseMProvides the cause for PIN communication creation request failure.
NOTE:
At least one of the IE shall be present.
Up

8.6.3.4  PIN Communication Update Request  p. 89

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.
Information element Status Description
PIN IDMThe identifier of the PIN.
Requester PINE ID/PEMCMThe identifier of the PIN Element/PEMC making the request.
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
MAC address/IP addressOMAC address/IP address of PINE/PEMC.
Traffic descriptorsMIdentify the updated target traffic to/from application server or to/from PINE, e.g.: IP 5 Tuple.
Packet filtersMUpdated packet filters that is used in PEGC to identify one or more packet flow(s), and the PEGC can route the traffic to the target application server/PINEs.
PIN communication flow IDMIncludes the communication flow that has been successfully established by PEGC.
Request QoSOThe updated QoS (e.g.: packet delay or AMBR) of packet flow that requested by PINE.
Up

8.6.3.5  PIN Communication Update Response  p. 90

Table 8.6.3.5-1 shows the informational elements of the PIN Communication Update response sent by a PEGC to the PINE/PEMC.
Information element Status Description
Successful responseO
(see NOTE)		Indicates that the PIN communication update request was successful.
> QoS informationMIncludes updated QoS information that agreed for this information flow.
> PIN communication flow IDMIncludes the communication flow that successfully established by PEGC.
Failure responseO
(see NOTE)		Indicates that the PIN communication update request failed.
> CauseMProvides the cause for PIN communication update request failure.
NOTE:
At least one of the IE shall be present.
Up

8.6.3.6  PIN Communication Delete Request  p. 90

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.
Information element Status Description
PIN IDMThe identifier of the PIN.
Requester PINE ID/PEMCMThe identifier of the PIN Element/PEMC making the request.
Security credentialsMSecurity credentials resulting from a successful authorization for the PIN service.
PIN communication flow IDMIncludes the communication flow that has been successfully established by PEGC.
Up

8.6.3.7  PIN Communication Delete Response  p. 90

Table 8.6.3.7-1 shows the informational elements of the PIN Communication Delete response sent by a PEGC to the PINE/PEMC.
Information element Status Description
Successful responseO
(see NOTE)		Indicates that the PIN communication delete was successful.
Failure responseO
(see NOTE)		Indicates that the PIN communication delete request failed.
> CauseMProvides the cause for PIN communication delete request failure.
NOTE:
At least one of the IE shall be present.
Up

Up   Top   ToC