Systems, devices, and techniques for registering user equipment (UE) in wireless networks using a native blockchain platform

• US 10,505,718 B1
• Filed: 09/18/2018
• Issued: 12/10/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): Ho, Dao Q
• Application Number:
  US16/134,887
• Publication Number:
  US 20190380030A1
• Time in Patent Office: 448 Days
• 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 network architectures or network communication protocols for wireless network security H04W12/00
• 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 determines a User Equipment (UE) supports a blockchain authentication procedure, exchanges authentication messages with a Blockchain Authentication Function (BAF) entity over a blockchain network interface (e.g., based on the blockchain authentication procedure), receives a blockchain authentication confirmation from the BAF entity, and registers the UE based on the blockchain authentication confirmation.

Claims

1. A method for registering User Equipment in a communication network, the method comprising:

determining, by an Access and Mobility Management Function (AMF) entity, a User Equipment (UE) supports a blockchain authentication procedure;

first receiving, by the AMF entity, blockchain credentials from the UE;

determining, by the AMF entity, the blockchain credentials include a blockchain entity identifier (ID);

selecting, by the AMF, from amongst a plurality of available Blockchain Authentication Function (BAF) entities a particular BAF entity based on the blockchain entity ID;

exchanging, after the selecting, authentication messages between the AMF entity and the selected BAF entity over a blockchain network interface, based on the blockchain authentication procedure;

second receiving, by the AMF entity, a blockchain authentication confirmation from the BAF entity; and

registering, by the AMF entity, the UE based on the blockchain authentication confirmation.

2. The method of claim 1, wherein exchanging authentication messages between the AMF entity and the BAF entity further comprises:

selecting an Authentication Server Function (AUSF) entity to perform the blockchain authentication procedure; and

sending a blockchain authentication request to the AUSF entity to cause the AUSF entity to authenticate the UE with the BAF entity over a blockchain network interface, and

wherein receiving the authentication confirmation further comprises receiving the authentication confirmation from the AUSF entity.

3. The method of claim 1, further comprising:

receiving, by the AMF entity, blockchain credentials in a Non-Access Stratum (NAS) message from the UE, and

wherein exchanging the authentication messages further comprises exchanging the blockchain credentials between the AMF entity and the BAF entity.

4. The method of claim 3, wherein the blockchain network interface is a first blockchain network interface, wherein the UE receives the blockchain credentials from the BAF entity over a second blockchain network interface.

5. The method of claim 1, further comprising between the second receiving and the registering:

performing a credit authorization procedure for a user associated with the UE; and

providing the UE access to one or more network resources based on the credit authorization procedure.

6. The method of claim 5, wherein performing the credit authorization procedure further comprises invoking, by the AMF, a Policy Control Function entity to perform the credit authorization procedure.

7. The method of claim 1, wherein determining the UE supports the blockchain authentication procedure further comprises:

receiving, by the AMF entity, a registration request message associated with the UE over at least one of a Radio Access Network (RAN) interface or an Access Network (AN) interface; and

determining the registration request message indicates the UE supports blockchain authentication in an access category.

8. The method of claim 1, wherein determining the UE supports the blockchain authentication procedure further comprises:

receiving, by the AMF entity, a Non-Access Stratum (NAS) message associated with the UE; and

determining the NAS message indicates the UE supports the blockchain authentication procedure based on at least one of registration type data or follow-on request data.

9. The method of claim 1, wherein exchanging authentication messages between the AMF entity and the BAF entity further comprises exchanging one or more REST Application Program Interface (API) messages between the AMF entity and the BAF entity.

10. 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 adapted to execute one or more processes; and

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

determine a User Equipment (UE) supports a blockchain authentication procedure;

first receive, by the AMF entity, blockchain credentials from the UE;

determine, by the AMF entity, the blockchain credentials include a blockchain entity identifier (ID);

select, by the AMF, from amongst a plurality of available Blockchain Authentication Function (BAF) entities a particular BAF entity based on the blockchain entity ID;

exchange, after the select, authentication messages with the selected BAF entity over a blockchain network interface, based on the blockchain authentication procedure;

second receive a blockchain authentication confirmation from the BAF entity; and

register the UE based on the blockchain authentication confirmation.

11. The NF device of claim 10, wherein the instructions to exchange authentication messages with the BAF entity are further operable to:

select an Authentication Server Function (AUSF) entity to perform the blockchain authentication procedure; and

send a blockchain authentication request to the AUSF entity to cause the AUSF entity to authenticate the UE with the BAF entity over a blockchain network interface, and

wherein the instructions to receive the authentication confirmation message are further operable to receive the authentication confirmation message from the AUSF entity.

12. The NF device of claim 10, wherein the instructions, when executed, are further operable to:

receive blockchain credentials in a Non-Access Stratum (NAS) message from the UE, and

wherein the instructions to exchange the authentication messages are further operable to send the blockchain credentials to the BAF entity.

13. The NF device of claim 10, wherein the instructions, when executed, are further operable to between the second receive and the register:

perform a credit authorization procedure for a user associated with the UE; and

provide the UE access to one or more network resources based on the credit authorization procedure.

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

determine a User Equipment (UE) supports a blockchain authentication procedure;

first receive, by the AMF entity, blockchain credentials from the UE;

determine, by the AMF entity, the blockchain credentials include a blockchain entity identifier (ID);

select, by the AMF, from amongst a plurality of available Blockchain Authentication Function (BAF) entities a particular BAF entity based on the blockchain entity ID;

exchange, after the select, authentication messages with the selected BAF entity over a blockchain network interface, based on the blockchain authentication procedure;

second receive a blockchain authentication confirmation from the BAF entity; and

register the UE based on the blockchain authentication confirmation.

15. The tangible, non-transitory, computer-readable media of claim 14, wherein the instructions, when executed by the processor to exchange authentication messages with the BAF entity, are further operable to:

select an Authentication Server Function (AUSF) entity to perform the blockchain authentication procedure; and

send a blockchain authentication request to the AUSF entity to cause the AUSF entity to authenticate the UE with the BAF entity over a blockchain network interface, and

wherein the instructions, when executed by the processor to receive the authentication confirmation message are further operable to receive the authentication confirmation from the AUSF entity.

16. The tangible, non-transitory, computer-readable media of claim 14, wherein the instructions, when executed by the processor, are further operable between the second receive and the register to:

perform a credit authorization procedure for a user associated with the UE; and

provide the UE access to one or more network resources based on the credit authorization procedure.