Systems and methods for network slice traffic identification using dynamic network addressing

Patent metadata

Field	Value
Publication number	US-11903044-B2
Application number	US-202217657806-A
Country	US
Kind code	B2
Filing date	Apr 4, 2022
Priority date	Apr 4, 2022
Publication date	Feb 13, 2024
Grant date	Feb 13, 2024

Abstract

A network device may maintain a list of existing slice identifiers, associated with slices of a core network, that are in use in active UE sessions, and may receive a slice identifier associated with a slice of the core network and provided in a request to establish a session between a UE and the slice of the core network. The network device may determine whether the slice identifier matches an existing slice identifier included in the list, and may create a new network address, with an address of the network device and the slice identifier, based on the slice identifier failing to match an existing slice identifier included in the list. The network device may utilize the new network address to establish the session between the UE and the slice of the core network.

First claim

What is claimed is:

1. A method, comprising:
maintaining, by a network device, a list of existing slice identifiers, associated with slices of a core network, that are in use in active user equipment (UE) sessions;
receiving, by the network device, a slice identifier associated with a slice of the core network and provided in a request to establish a session between a UE and the slice of the core network;
determining, by the network device, whether the slice identifier matches an existing slice identifier included in the list;
creating, by the network device, a new network address, with an address of the network device and the slice identifier, based on the slice identifier failing to match an existing slice identifier included in the list; and
utilizing the new network address to establish the session between the UE and the slice of the core network.

2. The method of claim 1 , further comprising:
utilizing an existing network address, associated with the existing slice identifier included in the list, based on the slice identifier matching the existing slice identifier.

3. The method of claim 2 , further comprising:
utilizing the existing network address to establish the session between the UE and the slice of the core network.

4. The method of claim 1 , further comprising:
storing the new network address in the list of existing slice identifiers.

5. The method of claim 1 , further comprising:
deleting existing network addresses associated with existing slice identifiers included in the list and not being utilized in active UE sessions.

6. The method of claim 1 , wherein the new network address is an N3 interface Internet protocol version six address.

7. The method of claim 1 , wherein the slice identifier is single network slice selection assistance information.

8. A network device, comprising:
one or more processors configured to:
maintain a list of existing slice identifiers, associated with slices of a core network, that are in use in active user equipment (UE) sessions;
receive a slice identifier associated with a slice of the core network and provided in a request to establish a session between a UE and the slice of the core network;
determine whether the slice identifier matches an existing slice identifier included in the list;
create a new network address, with an address of the network device and the slice identifier, based on the slice identifier failing to match an existing slice identifier included in the list;
store the new network address in the list of existing slice identifiers; and
utilize the new network address to establish the session between the UE and the slice of the core network.

9. The network device of claim 8 , wherein the one or more processors, to create the new network address, with the address of the network device and the slice identifier, are configured to:
determine whether a quantity of bits associated with a header of the new network address satisfies a threshold quantity; and
provide the slice identifier in the header of the new network address based on the quantity of bits associated with the header of the new network address satisfying the threshold quantity.

10. The network device of claim 9 , wherein the one or more processors are further configured to:
determine a shortened version of the slice identifier based on the quantity of bits associated with the header of the new network address failing to satisfy the threshold quantity; and
provide the shortened version of the slice identifier in the header of the new network address.

11. The network device of claim 8 , wherein the network device is a user plane function.

12. The network device of claim 8 , wherein the one or more processors are further configured to:
cause a transport network, associated with the core network, to identify per slice traffic based on inspection of the new network address in a packet of the per slice traffic.

13. The network device of claim 8 , wherein the one or more processors are further configured to:
cause a transport network, associated with the core network, to perform traffic routing decisions based on inspection of the new network address in a packet of per slice traffic.

14. The network device of claim 8 , wherein the one or more processors, to receive the slice identifier associated with the slice of the core network, are configured to:
receive the slice identifier from a session management function during UE session establishment procedures.

15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a network device, cause the network device to:
maintain a list of existing slice identifiers, associated with slices of a core network, that are in use in active user equipment (UE) sessions;
receive a slice identifier associated with a slice of the core network and provided in a request to establish a session between a UE and the slice of the core network;
determine whether the slice identifier matches an existing slice identifier included in the list;
create a new network address, with an address of the network device and the slice identifier, based on the slice identifier failing to match an existing slice identifier included in the list;
utilize the new network address to establish the session between the UE and the slice of the core network; and
delete existing network addresses associated with existing slice identifiers included in the list and not being utilized in active UE sessions.

16. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the network device to:
utilize an existing network address, associated with an existing slice identifier included in the list, based on the slice identifier matching the existing slice identifier; and
utilize the existing network address to establish the session between the UE and the slice of the core network.

17. The non-transitory computer-readable medium of claim 15 , wherein the new network address is an N3 interface Internet protocol version six address, and the slice identifier is single network slice selection assistance information.

18. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the network device to create the new network address, with the address of the network device and the slice identifier, cause the network device to:
determine whether a quantity of bits associated with a header of the new network address satisfies a threshold quantity; and
provide the slice identifier in the header of the new network address based on the quantity of bits associated with the header of the new network address satisfying the threshold quantity.

19. The non-transitory computer-readable medium of claim 18 , wherein the one or more instructions further cause the network device to:
determine a shortened version of the slice identifier based on the quantity of bits associated with the header of the new network address failing to satisfy the threshold quantity; and
provide the shortened version of the slice identifier in the header of the new network address.

20. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the network device to:
cause a transport network, associated with the core network, to identify per slice traffic and to perform traffic routing decisions based on inspection of the new net

Assignees

• Verizon Patent & Licensing Inc

Inventors

• Hua Suzann
• PATIL Sudhakar Reddy
• Booker Parry Cornell
• Taft David
• So Raymond Waiman
• Tse Lap

Classifications

• H04W76/10 Primary

  Connection setup · CPC title

• H04L45/745

  Address table lookup; Address filtering · CPC title

• H04W40/248

  Connectivity information update · CPC title

• H04W48/18 Primary

  Selecting a network or a communication service · CPC title