Systems, devices, and techniques for managing data sessions in a wireless network using a native blockchain platform

• US 10,491,376 B1
• Filed: 09/21/2018
• Issued: 11/26/2019
• Est. Priority Date: 06/08/2018
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Suthar, Om Prakash, Dodd-Noble, Aeneas Sean, Rayes, Ammar, Campbell, Ian McDowell, Geller, Michael David
• Primary Examiner(s): Lemma, Samson B
• Application Number:
  US16/138,524
• Publication Number:
  US 20190379530A1
• Time in Patent Office: 431 Days
• Field of Search: 713168
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1407 Policy-and-charging control [PCC] architecture
• CPC Class Codes: H04L 2209/80 Wireless
• CPC Class Codes: H04L 63/0892 by using authentication-authorization-accounting [AAA] servers or protocols
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 9/0637 Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/66 Policy and charging system
• CPC Class Codes: H04M 15/8038 Roaming or handoff
• CPC Class Codes: H04M 15/8228 Session based
• CPC Class Codes: H04M 15/854 Available credit
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 4/24 Accounting or billing
• CPC Class Codes: H04W 48/08 Access restriction or access information delivery, e.g. discovery data delivery signalling during connection H04W76/00
• CPC Class Codes: H04W 48/18 Selecting a network or a communication service
• CPC Class Codes: H04W 60/00 Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 84/042 Public Land Mobile systems, e.g. cellular systems
• CPC Class Codes: H04W 88/02 : Terminal devices

Abstract

A network function (NF) entity in a communication network receives session request data associated with a User Equipment (UE), which includes blockchain authentication data. The NF entity selects a Blockchain Authentication Function (BAF) entity based on the session request data, and exchanges at least a portion of the blockchain authentication data with the BAF entity over a blockchain network interface. The NF entity further receives authentication confirmation data from the BAF entity over the blockchain network interface, and establishes a data session associated with the UE based on the authentication confirmation data.

Claims

1. A method for managing a data session for User Equipment (UE) in a communication network, the method comprising:

receiving, by a Session Management Function (SMF) entity, session request data associated with User Equipment (UE), the session request data including blockchain authentication data;

selecting, by the SMF, a Blockchain Authentication Function (BAF) entity based on the session request data;

exchanging at least a portion of the blockchain authentication data between the SMF entity and the BAF entity over a blockchain network interface;

receiving, by the SMF, authentication confirmation data from the BAF entity over the blockchain network interface; and

establishing a data session associated with the UE based on the authentication confirmation data.

2. The method of claim 1, wherein the blockchain authentication data includes blockchain credentials associated with the UE, and

wherein exchanging the blockchain authentication data between the SMF and the BAF entity further comprises exchanging the blockchain credentials associated with the UE over the blockchain network interface.

3. The method of claim 1, further comprising:

applying a restricted access policy for the data session;

soliciting blockchain payment credits from the BAF entity over the blockchain network interface;

determining the blockchain payment credits satisfy a payment criteria for one or more network services as part of a blockchain charging event; and

updating the restricted access policy to permit the UE access to the one or more network services based on the blockchain charging event.

4. The method of claim 1, wherein exchanging the blockchain authentication data between the SMF and the BAF further comprises:

selecting, by the SMF, a Network Exposure Function (NEF) entity to communicate with the BAF over the blockchain network interface.

5. The method of claim 1, further comprising:

selecting the SMF entity based on the blockchain authentication data.

6. The method of claim 1, wherein the session request data comprises Single Network Slice Selection Assistance Information (N-SSAI) that includes the blockchain authentication data.

7. The method of claim 1, wherein the session request data comprises Single Network Slice Selection Assistance Information (N-SSAI) that includes at least a portion of the blockchain authentication data in a slice/service type (SST) value.

8. The method of claim 1, wherein the data session includes at least one of a Protocol Data Unit (PDU) session or a Packet Data Network (PDN) session.

9. The method of claim 1, wherein establishing the data session further comprises establishing the data session for a network slice associated with the UE.

10. The method of claim 1, wherein establishing the data session further comprises:

selecting a User Plane Function entity to serve the data session.

11. The method of claim 1, wherein the session request data includes a Service Management (SM) Data Network (DN) request container message.

12. A network function (NF) device, comprising:

one or more network interfaces to communicate within a communication network;

a processor coupled to the network interfaces; and

a memory configured to store a process executable by the processor, the process when executed operable to;

receive session request data associated with a User Equipment (UE), the session request data including blockchain authentication data;

select a Blockchain Authentication Function (BAF) entity based on the session request data;

exchange at least a portion of the blockchain authentication data with the BAF entity over a blockchain network interface;

receive authentication confirmation data from the BAF entity over the blockchain network interface; and

establish a data session associated with the UE based on the authentication confirmation data.

13. The NF device of claim 12, wherein the blockchain authentication data includes blockchain credentials associated with the UE, and

wherein the process to exchange the blockchain authentication data with the BAF entity is further operable to exchange the blockchain credentials associated with the UE over the blockchain network interface.

14. The NF device of claim 12, wherein the process, when executed, is further operable to:

apply a restricted access policy for the data session;

solicit blockchain payment credits from the BAF entity over the blockchain network interface;

determine the blockchain payment credits satisfy a payment criteria for one or more network services as part of a blockchain charging event; and

update the restricted access policy to permit the UE access to the one or more network services based on the blockchain charging event.

15. The NF device of claim 12, wherein the process to exchange the blockchain authentication data with the BAF, when executed, is further operable to:

select a Network Exposure Function (NEF) entity to communicate with the BAF over the blockchain network interface.

16. The NF device of claim 12, wherein the session request data comprises Single Network Slice Selection Assistance Information (N-SSAI) that includes the blockchain authentication data.

17. The NF device of claim 12, wherein the session request data comprises Single Network Slice Selection Assistance Information (N-SSAI) that includes at least a portion of the blockchain authentication data in a slice/service type (SST) value.

18. A tangible, non-transitory, computer-readable media having instructions encoded thereon, the instructions, when executed by a processor, are operable to perform operations comprising:

receive, by a Network Function (NF) entity, session request data associated with a User Equipment (UE), the session request data including blockchain authentication data;

select, by the NF entity, a Blockchain Authentication Function (BAF) entity based on the session request data;

exchange, by the NF entity, at least a portion of the blockchain authentication data with the BAF entity over a blockchain network interface;

receive, by the NF entity, authentication confirmation data from the BAF entity over the blockchain network interface; and

establish a data session associated with the UE based on the authentication confirmation data.

19. The tangible, non-transitory, computer-readable media of claim 18, wherein the instructions, when executed by the processor, are further operable to:

apply a restricted access policy for the data session;

solicit blockchain payment credits from the BAF entity over the blockchain network interface;

determine the blockchain payment credits satisfy a payment criteria for one or more network services as part of a blockchain charging event; and

update the restricted access policy to permit the UE access to the one or more network services based on the blockchain charging event.

20. The tangible, non-transitory, computer-readable media of claim 18, wherein the session request data comprises Single Network Slice Selection Assistance Information (N-SSAI) that includes at least a portion of the blockchain authentication data in a slice/service type (SST) value.