# US 2017/0289856 A1 · Method and system for handling a traffic flow between local service clouds

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

- Number: US 2017/0289856 A1
- Document ID: US20170289856A1
- Status: Published application
- Kind: A1
- Application number: 15/507,132
- Filed: 2014-09-02
- Published: 2017-10-05
- Earliest claimed: 2014-09-02
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Johan RUNE; Lars WESTBERG; Vinay YADHAV
- Web page: https://patentgrep.com/patent/US20170289856A1

## CPC

- H04W 36/0016: {Hand-off preparation specially adapted for end-to-end data sessions}
- H04L 61/2514: between local and global IP addresses
- H04L 61/5007: Internet protocol [IP] addresses
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04W 36/125: {involving different types of service backbones}
- H04L 61/5084: Providing for device mobility (network addressing or numbering for mobility support in wireless networks H04W8/26; mobile IP H04W80/04)
- H04L 2101/668: Internet protocol [IP] address subnets
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method in a network node for handling a traffic flow of a User Equipment, UE. The network node creates a unique Network Address Translated, NAT:ed, Internet Protocol, IP, address mapping to an IP address of the UE. The NAT:ed IP address includes a local IP address prefix assigned to a related first local service cloud. The NAT:ed IP address is usable for the traffic flow both before and after a handover of the UE from the first local service cloud to a neighbouring second local service cloud. The NAT:ed IP address is unique at least in all local service clouds neighbouring to the first local service cloud, including the second local service cloud. The network node assigns the NAT:ed IP address to the UE for local break out of the traffic flow of the application session to the first local service cloud.

## Claims

### Claim 1

A method in a network node for handling a traffic flow of a User Equipment, UE, the network node being related to a first local service cloud, and the traffic flow is related to an application session served by the first local service cloud, the method comprising:
creating a unique Network Address Translated, NAT:ed, Internet Protocol, IP, address mapping to a UE IP address of the UE, the unique NAT:ed IP address having a local IP address prefix assigned to the first local service cloud,
the unique NAT:ed IP address being usable for the traffic flow both before and after a handover of the UE from the first local service cloud to a neighbouring second local service cloud, the unique NAT:ed IP address is unique at least in all local service clouds neighboring to the first local service cloud, including the second local service cloud; and
assigning the unique NAT:ed IP address to the UE for local break out of the traffic flow of the application session to the first local service cloud.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the uniqueness of the unique NAT:ed IP address is created by NAT:ing the UE IP address to one of a public IPv6 address and a public IPv4 address.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising:
identifying a UE IP address of the UE.

### Claim 4 (depends on 1)

The method according to claim 1, further comprising:
identifying a UE IP address and a port number of the UE.

### Claim 5 (depends on 1)

The method according to claim 1, wherein the unique NAT:ed IP address mapping to the UE IP address of the UE is further mapped to at least one port number of the UE.

### Claim 6 (depends on 1)

The method according to claim 1, further comprising:
mapping, to a radio bearer, a downlink for the traffic flow of the application session to the first local service cloud, by using the unique NAT:ed IP address as an identifier.

### Claim 7 (depends on 1)

The method according to claim 1, wherein the assigned unique NAT:ed IP address is any one of:
assigned a maximum time-to-live and, when the maximum time-to-live expires, the NAT:ed IP address is reused; and
de-allocated when it has not been used for a certain time.

### Claim 8 (depends on 1)

The method according to claim 1, wherein the network node is arranged to be included in a base station.

### Claim 9

A method in a cloud orchestration server for handling Internet Protocol, IP, address prefixes for local service clouds in a set of local service clouds, the method comprising:
generating a unique local IP address prefix for each one of the respective local service clouds in the set of local service clouds, the unique local IP address prefix for creating unique Network Address Translated, NAT:ed, IP address mapping to an User Equipment, UE, IP address, the generating of the unique local IP address prefix to each of the respective local service cloud in the set of local service clouds comprises:
assigning an IP address prefix for all the local service clouds in the set of local service clouds;
dividing the assigned IP address prefix into a number of local IP address prefixes, the number of local IP address prefixes being equal to the number of local service clouds in the set of local service clouds; and
assigning each one out of the number of local IP address prefixes to each respective local service cloud in the set of local service clouds such that each local IP address prefix is unique among the local IP address prefixes of the local service clouds in the set of local service clouds, the local IP address prefixes are to be assigned to User Equipments, UEs, for local break out of traffic flows of application sessions to local service clouds in the set of local service clouds.

### Claim 10 (depends on 9)

The method according to claim 9, wherein the IP address prefix and the local IP address prefixes relate to one of IPv4 and IPv6.

### Claim 11 (depends on 9)

The method according to claim 9, wherein the IP address prefix and the local IP address prefixes relate to IPv4, wherein the set of local service clouds comprises a cluster of neighboring local service clouds, and wherein the generating of the unique local IP address prefix to each of the respective local service clouds in the set of local service clouds further comprises:
determining a distance between local service clouds for assigning local IP address prefix reuse, the distance being in terms of number of local service clouds; and
defining a size of the cluster of neighboring local service clouds in the set of local service clouds based on the determined local service cloud distance for local IP address prefix reuse;
wherein the dividing the assigned IP address prefix into a number of local IP address prefixes, is performed based on the size of the cluster; and
wherein assigning each one out of the number of local IP address prefixes to each respective local service cloud in the set of local service clouds, is performed to each respective local service cloud in the cluster.

### Claim 12 (depends on 11)

The method according to claim 11, wherein the local service cloud distance for local IP address prefix reuse comprises local IP address prefix reuse of any one of: geographic distance, number of inter cell handover hops, number of inter local service clouds handover hops, and inter base station handover hops.

### Claim 13 (depends on 11)

The method according to claim 11, wherein the local IP address prefixes assigned to each respective local service cloud in the cluster define a local IP address prefix pattern of assigned local IP address prefixes of the local service clouds in the cluster, the method further comprising:
repeating the local IP address prefix pattern of assigned local IP address prefixes of the local service clouds in the cluster over other local service clouds outside the cluster of service clouds such that local service clouds assigned with the same local IP address prefixes have the determined distance between each other.

### Claim 14

A network node for handling a traffic flow of a User Equipment, UE, the network node configured to be related to a first local service cloud, and the traffic flow is to be related to an application session served by the first local service cloud, the network node being configured to:
create a unique Network Address Translated, NAT:ed, Internet Protocol, IP, address mapping to an UE IP address of the UE, the unique NAT:ed IP address having a local IP address prefix assigned to the first local service cloud, the unique NAT:ed IP address being usable for the traffic flow both before and after a handover of the UE from the first local service cloud to a neighbouring second local service cloud, and the unique NAT:ed IP address is unique at least in all local service clouds neighboring to the first local service cloud, including the second local service cloud; and
assign the unique NAT:ed IP address to the UE for local break out of the traffic flow of the application session to the first local service cloud.

### Claim 15 (depends on 14)

The network node according to claim 14, wherein the uniqueness of the unique NAT:ed IP address is to be created by NAT:ing the UE IP address one of a public IPv6 address and a public IPv4 address.

### Claim 16 (depends on 14)

The network node according to claim 14, wherein the network node is further configured to identify a UE IP address of the UE.

### Claim 17 (depends on 14)

The network node according to claim 14, wherein the network node is further is configured to identify a UE IP address and a port number of the UE.

### Claim 18 (depends on 14)

The network node according to claim 14, wherein the unique NAT:ed IP address to be mapped to the UE IP address of the UE, is further to be mapped to at least one port number of the UE.

### Claim 19 (depends on 14)

The network node according to claim 14, wherein the network node is further configured to map to a radio bearer, a downlink for the traffic flow of the application session to the first local service cloud by using the unique NAT:ed IP address as an identifier.

### Claim 20 (depends on 14)

The network node according to claim 14, wherein the assigned unique NAT:ed IP address is one of:
assigned a maximum time-to-live and, when the maximum time-to-live expires, the NAT:ed IP address is reused; and
de-allocated when it has not been used for a certain time.

### Claim 21 (depends on 15)

The network node according to claim 15, wherein the network node is configured to be comprised in a base station.

### Claim 22

A cloud orchestration server for handling Internet Protocol, IP, address prefixes for local service clouds in a set of local service clouds, the cloud orchestration server being configured to:
generate a unique local IP address prefix for each one of the respective local service clouds in the set of local service clouds, the unique local IP address prefix for creating unique Network Address Translated, NAT:ed, IP address mapping to a User Equipment, UE, IP address, the cloud orchestration server being configured to generate the unique local IP address prefix to each of the respective local service cloud in the set of local service clouds by:
assigning an IP address prefix for all the local service clouds in the set of local service clouds;
dividing the assigned IP address prefix into a number of local IP address prefixes, the number of local IP address prefixes being equal to the number of local service clouds in the set of local service clouds; and
assigning each one out of the number of local IP address prefixes to each respective local service cloud in the set of local service clouds, such that each local IP address prefix is unique among the local IP address prefixes of the local service clouds in the set of local service clouds, the local IP address prefixes are to be assigned to User Equipments, UEs, for local break out of traffic flows of application sessions to local service clouds in the set of local service clouds.

### Claim 23 (depends on 22)

The cloud orchestration server according to claim 22, wherein the IP address prefix and the local IP address prefixes relate to one of IPv4 and IPv6.

### Claim 24 (depends on 22)

The cloud orchestration server according to claim 22, wherein the IP address prefix and the local IP address prefixes relate to IPv4, wherein the set of local service clouds is arranged to comprise a cluster of neighboring local service clouds, and wherein the cloud orchestration server is configured to generate the unique local IP address prefix to each of the respective local service clouds in the set of local service clouds by:
determining a distance between local service clouds for assigning local IP address prefix reuse, which distance is in terms of number of local service clouds; and
defining a size of the cluster of neighboring local service clouds in the set of local service clouds, based on the determined local service cloud distance for local IP address prefix reuse;
wherein the cloud orchestration server is further configured to divide the assigned IP address prefix into a number of local IP address prefixes, based on the size of the cluster; and
wherein the cloud orchestration server is further configured to assign each one out of the number of local IP address prefixes to each respective local service cloud in the set of local service clouds to each respective local service cloud in the cluster.

### Claim 25 (depends on 22)

The cloud orchestration server according to claim 22, wherein the local service cloud distance for local IP address prefix reuse comprises local IP address prefix reuse of any one out of: geographic distance, number of inter cell handover hops, number of inter local service clouds handover hops, and inter base station handover hops.

### Claim 26 (depends on 22)

The cloud orchestration server according to claim 22, wherein the local IP address prefixes to be assigned to each respective local service cloud in the cluster define a local IP address prefix pattern of assigned local IP address prefixes of the local service clouds in the cluster, and wherein the cloud orchestration server is further configured to repeat the local IP address prefix pattern of assigned local IP address prefixes of the local service clouds in the cluster over other local service clouds outside the cluster of service clouds such that local service clouds assigned with the same local IP address prefixes have the determined distance between each other.
