# US 2019/0379530 A1 · Systems, devices, and techniques for managing data sessions in a wireless network using a native blockchain platform

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0379530 A1
- Document ID: US20190379530A1
- Status: Published application
- Kind: A1
- Application number: 16/138,524
- Filed: 2018-09-21
- Published: 2019-12-12
- Earliest claimed: 2018-06-08
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Om Prakash Suthar; Aeneas Sean Dodd-Noble; Ammar Rayes; Ian McDowell Campbell; Michael David Geller
- Web page: https://patentgrep.com/patent/US20190379530A1

## CPC

- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- H04L 63/0892: {by using authentication-authorization-accounting [AAA] servers or protocols}
- H04L 63/102: {Entity profiles}
- 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}
- H04M 15/66: {Policy and charging system}
- H04M 15/8038: {Roaming or handoff}
- H04M 15/8228: {Session based}
- H04M 15/854: {Available credit}
- H04W 12/08: Access security
- H04W 48/08: Access restriction or access information delivery, e.g. discovery data delivery (signalling during connection H04W76/00)
- H04W 48/18: Selecting a network or a communication service
- H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W 60/002: {Registration for requesting network slices}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2209/80: Wireless
- H04W 4/24: Accounting or billing
- H04W 12/06: Authentication
- H04W 84/042: {Public Land Mobile systems, e.g. cellular systems}
- H04W 88/02: Terminal devices
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## 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

### Claim 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.

### Claim 2 (depends on 1)

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.

### Claim 3 (depends on 1)

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.

### Claim 4 (depends on 1)

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.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
selecting the SMF entity based on the blockchain authentication data.

### Claim 6 (depends on 1)

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.

### Claim 7 (depends on 1)

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.

### Claim 8 (depends on 1)

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.

### Claim 9 (depends on 1)

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

### Claim 10 (depends on 1)

The method of claim 1, wherein establishing the data session further comprises:
selecting a User Plane Function entity to serve the data session.

### Claim 11 (depends on 1)

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

### Claim 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.

### Claim 13 (depends on 12)

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.

### Claim 14 (depends on 12)

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.

### Claim 15 (depends on 12)

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.

### Claim 16 (depends on 12)

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.

### Claim 17 (depends on 12)

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.

### Claim 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.

### Claim 19 (depends on 18)

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.

### Claim 20 (depends on 18)

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.
