Secure remote access to a 5G private network through a private network slice
摘要
說明書
In some implementations, the network node may cause one or more values of a 5-tuple for the enterprise UP traffic to be provisioned in the forwarding entity for causing the UP traffic of the UE to be forwarded to the anchor UPF as described. In additional or alternative implementations, the network node may cause the session identifier or service path identifier to be provisioned in the forwarding entity for causing the UP traffic of the UE to be forwarded to the anchor UPF as described. Here, the network node may send to the UE a message which includes a session identifier or service path identifier. The session identifier or service path identifier may be provided to the UE for inclusion in a header of data packets associated with the UP traffic. The session identifier or service path identifier may be inserted by the UE in a header which is a NSH or the like.
Thus, traffic splitting functionality is made available in order to route enterprise UP traffic from the UE using a private network slice while routing remaining subscriber UP traffic from the same UE using a subscriber network slice of the subscriber. Such a mechanism may be considered or viewed as a Split VPN, where enterprise UP traffic is routed through a secure tunnel to the enterprise while remaining subscriber UP traffic is routed to the Internet or other public network.
