Proposal for PEMC Communicating with PEGC via 5GC Local Switch
Solution proposal for PEMC
communicating PEGC via 5GC
local switch to enable PEMC
managing PIN without AF
vivo
Why PEMC needs to communicate with PEGC via 5GC local switch
•
PEMC APP can be installed on any UE as well as on
devices
•
The UE with PEMC APP (called PEMC UE) may not have
direct connection with any PEGC
•
The communication of a PIN is fully controlled by
PEMC/AF, in case AF is not deployed, the PEMC UE
shall be able to communicate with PEGC to enable the
management of the PIN via 5GC local switch
•
When AF is deployed, the PEMC can register and
communicate with the AF, but the PEMC may still not
allow PEGCs to communicate with the AF for the sake
of privacy concern
The principle for PEMC communicating with PEGC via 5GC local switch
•
Anchor the PDU Sessions of PEGCs and PEMC UE at same SMF
•
The anchoring method could be according to same <DNN, S-NSSAI> combination, which does
not have impact on SMF selection
•
Different PIN
may use
same
<DNN, S-NSSAI> combination
, the
SMF sets
Network Instance
in
PDRs and FARs according to the PIN ID to isolate traffic data between different PINs
, which has
less impact on SMF functionality (SMF functionality anyway needs to be enhanced to support
the new feature -
PIN
)
•
The PEMC can be provisioned with URSP rule with same <DNN, S-NSSAI> combination for
anchoring the corresponding PDU Session at the
same SMF
, and
SMF sets
Packet Filter Set
in
PDRs
for the PDU Sessions
to isolate management data between different PINs
•
The Internal Group ID corresponding to the PIN ID that the PEMC UE is able to be managed can
be configured in Internal-Group-ID-list in AM and SM subscription, which does not have 5GC
impact (e.g., pre-configured, or using 5G VN procedure that the
External GID=PIN ID and
membership only includes PEMC UE(s)
)
•
The conclusion that “PEMC UE does not have PIN subscription” does not mean “5GC is not
aware of PEMC UE”, any UE can act as PEMC but only PEGC-capable UE with PIN subscription
can act as PEGC,
the above principle
does not require PEMC UE has PIN subscription
An example that is aligned with the principle –
PEMC UE is able to manage PIN#1 and PIN#2
•
The management data and traffic data may be over different
PDU Sessions of PEGC, but this will cause more PDU Session
establishment by PEGC, and need more procedure for
establishing the PDU Session for management by PEGC
•
The management is only between PEMC UE and PEGC, not
between PEGCs, so 5G VN can not be applied for
management data transferring
The proposal suggests enabling PEMC to manage Personal Information Network (PIN) without AF vivo by communicating with PEGC via a 5GC local switch. This method allows for PIN management even when AF is not deployed, ensuring privacy concerns are addressed. The principle involves anchoring PDU Sessions of PEGCs and PEMC UE at the same SMF without impacting SMF selection, thus isolating traffic data between different PINs. Through URSP rule provisioning and Internal Group ID configuration, the management data between different PINs is effectively managed.
Uploaded on May 10, 2024 | 0 Views
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
Solution proposal for PEMC communicating PEGC via 5GC local switch to enable PEMC managing PIN without AF vivo
Why PEMC needs to communicate with PEGC via 5GC local switch PEMC APP can be installed on any UE as well as on devices The UE with PEMC APP (called PEMC UE) may not have direct connection with any PEGC The communication of a PIN is fully controlled by PEMC/AF, in case AF is not deployed, the PEMC UE shall be able to communicate with PEGC to enable the management of the PIN via 5GC local switch When AF is deployed, the PEMC can register and communicate with the AF, but the PEMC may still not allow PEGCs to communicate with the AF for the sake of privacy concern PIN 5G network PEMC UE PEGC 1 PEGC 2 PINE 1 PINE 2 ... PINE a PINE b PINE c ... PINE m Legend: Direct connection PIN control signaling over application layer
The principle for PEMC communicating with PEGC via 5GC local switch Anchor the PDU Sessions of PEGCs and PEMC UE at same SMF The anchoring method could be according to same <DNN, S-NSSAI> combination, which does not have impact on SMF selection Different PIN may use same <DNN, S-NSSAI> combination, the SMF sets Network Instance in PDRs and FARs according to the PIN ID to isolate traffic data between different PINs, which has less impact on SMF functionality (SMF functionality anyway needs to be enhanced to support the new feature - PIN) The PEMC can be provisioned with URSP rule with same <DNN, S-NSSAI> combination for anchoring the corresponding PDU Session at the same SMF, and SMF sets Packet Filter Set in PDRs for the PDU Sessions to isolate management data between different PINs The Internal Group ID corresponding to the PIN ID that the PEMC UE is able to be managed can be configured in Internal-Group-ID-list in AM and SM subscription, which does not have 5GC impact (e.g., pre-configured, or using 5G VN procedure that the External GID=PIN ID and membership only includes PEMC UE(s)) The conclusion that PEMC UE does not have PIN subscription does not mean 5GC is not aware of PEMC UE , any UE can act as PEMC but only PEGC-capable UE with PIN subscription can act as PEGC, the above principle does not require PEMC UE has PIN subscription
PDRs and FARs for PDU Session#1 (PEGC#1) PDR#01 for management UL Source interface CN tunnel info PDRs and FARs for PDU Session#3 (PEGC#3) PDR#03 for management UL Source interface CN tunnel info PDRs and FARs for PDU Session#0 (PEMC UE) PDR#05 for management UL Source interface CN tunnel info An example that is aligned with the principle PEMC UE is able to manage PIN#1 and PIN#2 "access side" N3 TEID for PDU Session#1 src: PEGC IP#1 dst: PEMC IP#0 FAR#01 "access side" N3 TEID for PDU Session#3 src: PEGC IP#3 dst: PEMC IP#0 FAR#03 "access side" N3 TEID for PDU Session#0 src: IP#0, dst: IP#1 || IP#2 || IP#3 || IP#4 FAR#05 Packet Filter Set Packet Filter Set Packet Filter Set PINE#31 PINE#41 IP#41 IP#31 FAR ID FAR#01 for management UL Destination interface FAR ID FAR#03 for management UL Destination interface FAR ID FAR#05 for management UL Destination interface URSP rule: PIN ID#2: DNN#1+Slice#1 "5G VN internal" "5G VN internal" "5G VN internal" IP#3 IP#4 PIN subscription: Internal GID#2 PEGC 3 PEGC 4 PIN#2 PDR#02 for management DL Source interface PDR#04 for management DL Source interface PDR#06 for management DL Source interface "5G VN internal" "5G VN internal" "5G VN internal" src: PEMC IP#0 dst: PEGC IP#1 FAR#02 src: PEMC IP#0 dst: PEGC IP#3 FAR#04 src: IP#1 || IP#2 || IP#3 || IP#4, dst: IP#0 FAR#06 Packet Filter Set Packet Filter Set Packet Filter Set URSP rule: PEMC APP and/or IP descriptors: DNN#1+Slice#1 FAR ID FAR#02 for management DL Destination interface FAR ID FAR#04 for management DL Destination interface FAR ID FAR#06 for management DL Destination interface "access side" "access side" "access side" PDU Session#0 5G network IP#0 PEMC UE Outer header creation PDR#11 for traffic UL Source interface N3 TEID for PDU Session#1 N3 TEID for PDU Session#3 N3 TEID for PDU Session#0 Outer header creation Outer header creation AM&SM subscription: Internal GID#1 PDR#13 for traffic UL Source interface N/A Internal GID#2 "access side" "access side" N3 TEID for PDU Session#1 src: PINE IP#11 dst: PINE IP#21 N3 TEID for PDU Session#3 src: PINE IP#31, dst: PINE IP#41 CN tunnel info CN tunnel info PEGC 1 PEGC 2 IP#1 PIN subscription: Internal GID#1 IP#2 PIN#1 Packet Filter Set Packet Filter Set URSP rule: PIN ID#1: DNN#1+Slice#1 FAR ID FAR#11 FAR ID FAR#13 for traffic UL Network instance Destination interface FAR#13 FAR#11 for traffic UL N/A PIN#1 PIN#2 Network instance Destination interface PINE#11 PINE#21 IP#21 IP#11 "5G VN internal" "5G VN internal" PDR#12 for traffic DL Source interface PDR#14 for traffic DL Source interface N/A "5G VN internal" "5G VN internal" The management data and traffic data may be over different PDU Sessions of PEGC, but this will cause more PDU Session establishment by PEGC, and need more procedure for establishing the PDU Session for management by PEGC PIN#1 PIN#2 Network instance Network instance src: PINE IP#21 dst: PINE IP#11 FAR#12 src: PINE IP#41 dst: PINE IP#31 FAR#14 Packet Filter Set Packet Filter Set FAR ID FAR ID FAR#14 for traffic DL Destination interface FAR#12 for traffic DL N/A The management is only between PEMC UE and PEGC, not between PEGCs, so 5G VN can not be applied for management data transferring "access side" Destination interface "access side" Outer header creation N3 TEID for PDU Session#1 N3 TEID for PDU Session#2 Outer header creation
