IP Library Granted Patent US 12,615,232
Granted Patent B2
US 12,615,232 · App. 18/037,822 · Granted Apr 28, 2026

Network traffic management

Inventors: András Kern (Budapest, HU); Balázs Peter Gerö (Budapest, HU)
Assignee: Telefonaktiebolaget LM Ericsson (Publ)
H04L61/5076H04L61/4511
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,615,232
App. No.
18/037,822
Granted
Apr 28, 2026
Kind
B2
Abstract

There is provided a method performed by an entity for managing traffic between a network gateway and an application server. In response to a user equipment (UE) connecting to or disconnecting from the network gateway, a network prefix assigned to a DNS view is updated ( 102 ). The network prefix comprises one or more internet protocol (IP) addresses that each identify a UE that is connected to the network gateway and to which the DNS view is accessible. Traffic between the network gateway and the application server is steered according to the DNS view to which the updated network prefix is assigned.

Claims (55)

1 . A method performed by a computing device for managing traffic between a network gateway and an application server, the method comprising:

collecting one or more policies;

receiving a notification that a user equipment (UE) has connected to or disconnected from the network gateway, the notification comprising an identifier of the UE;

updating a network prefix that is currently assigned to a domain name service (DNS) view in response to receiving the notification and based on the one or more policies that are applicable to the UE, the updating comprising:

calculating a second network prefix;

assigning the calculated second network prefix to the DNS view at one or more DNS servers that comprise the DNS view, the second network prefix being different from the first network prefix; and

unassigning the first network prefix from the DNS view at the one or more DNS servers that comprise the DNS view;

the first network prefix that is currently assigned to the DNS view comprising two or more internet protocol (IP) addresses that each identify a UE that is connected to the network gateway; and

traffic between the network gateway and the application server being steered according to the DNS view when the traffic originates from a UE having an IP address that falls within the network prefix currently assigned to the DNS view.

2 . The method of claim 1 , wherein updating the first network prefix assigned to the DNS view comprises:

deleting the first network prefix that is currently assigned to the DNS view.

3 . The method of claim 2 , wherein:

deleting the first network prefix that is currently assigned to the DNS view is performed in response to the UE disconnecting from the network gateway; and/or

assigning the second network prefix to the DNS view is performed in response to the UE connecting to the network gateway.

4 . The method of claim 2 , wherein:

deleting the first network prefix that is currently assigned to the DNS view comprises deleting the first network prefix at one or more DNS servers that comprise the DNS view; and/or

assigning the second network prefix to the DNS view comprises assigning the second network prefix at the one or more DNS servers that comprise the DNS view.

5 . The method of claim 4 , further comprising identifying the one or more DNS servers that comprise the DNS view to which the first network prefix is assigned.

6 . The method of claim 1 , wherein the notification comprises an identifier that identifies:

the UE that is connecting to or disconnecting from the network gateway; and/or

the network gateway.

7 . The method of claim 1 , wherein the notification comprises the second network prefix.

8 . The method of claim 1 , wherein the one or more policies are associated with the UE only or a group of UEs that comprises the UE.

9 . A computing device comprising:

processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the computing device is configured to:

collect one or more policies;

receive a notification that a user equipment (UE) has connected to or disconnected from a network gateway, the notification comprising an identifier of the UE;

update a first network prefix that is currently assigned to a domain name service (DNS) view in response to receiving the notification and based on the one or more policies that are applicable to the UE, the updating comprising:

calculate a second network prefix;

assign the calculated second network prefix to the DNS view at one or more DNS servers that comprise the DNS view, the second network prefix being different from the first network prefix; and

unassign the first network prefix from the DNS view at the one or more DNS servers that comprise the DNS view;

the first network prefix that is currently assigned to the DNS view comprising two or more internet protocol (IP) addresses that each identify a UE that is connected to the network gateway; and

traffic between the network gateway and an application server being steered according to the DNS view when the traffic originates from a UE having an IP address that falls within the network prefix currently assigned to the DNS view.

10 . The computing device of claim 9 , wherein to update the first network prefix assigned to the DNS view, the computing device is configured to:

delete the first network prefix that is currently assigned to the DNS view.

11 . The computing device of claim 10 , wherein the computing device is configured to:

delete the first network prefix that is currently assigned to the DNS view in response to the UE disconnecting from the network gateway; and/or

assign the second network prefix to the DNS view in response to the UE connecting to the network gateway.

12 . The computing device of claim 10 , wherein the computing device is configured to:

delete the first network prefix that is currently assigned to the DNS view at one or more DNS servers that comprise the DNS view; and/or

assign the second network prefix to the DNS view at the one or more DNS servers that comprise the DNS view.

13 . The computing device of claim 12 , wherein the computing device is further configured to identify the one or more DNS servers that comprise the DNS view to which the first network prefix is assigned.

14 . The computing device of claim 9 , wherein the notification comprises an identifier that identifies:

the UE that is connecting to or disconnecting from the network gateway; and/or

the network gateway.

15 . The computing device of claim 9 , wherein the notification comprises the second network prefix.

16 . A non-transitory computer readable medium storing a computer program product comprising instructions which, when executed on processing circuitry of a computing device, cause the processing circuitry to:

collect one or more policies;

receive a notification that a user equipment (UE) has connected to or disconnected from a network gateway, the notification comprising an identifier of the UE;

update a first network prefix that is currently assigned to a domain name service (DNS) view in response to receiving the notification and based on the one or more policies that are applicable to the UE, the updating comprising:

calculate a second network prefix;

assign the calculated second network prefix to the DNS view at one or more DNS servers that comprise the DNS view, the second network prefix being different from the first network prefix; and

unassign the first network prefix from the DNS view at the one or more DNS servers that comprise the DNS view;

the first network prefix that is currently assigned to the DNS view comprising two or more internet protocol (IP) addresses that each identify a UE that is connected to the network gateway; and

traffic between the network gateway and an application server being steered according to the DNS view when the traffic originates from a UE having an IP address that falls within the network prefix currently assigned to the DNS view.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2023
From: KERN, ANDRÁS; GERÖ, BALÁZS PETER
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 063699/0028 →
Continuity (1)
Related Publication 20230421533A1 · Dec 28, 2023
References Cited (10)
US 10972426B1 · Sinha · 2021 [cited by examiner]
US 20050286510A1 · Nakajima · 2005 [cited by examiner]
US 20100131646A1 · Drako · 2010 [cited by examiner]
US 20180063075A1 · Eckert · 2018 [cited by examiner]
3rd Generation Partnership Project, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of support for Edge Computing in 5G Core network (5GC) (Release 17… [cited by applicant]
3rd Generation Partnership Project, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on application architecture for enabling Edge Applications; (Release 17)”, Techni… [cited by applicant]
ETSI, “Multi-access Edge Computing (MEC); MEC Management; Part 2: Application lifecycle, rules and requirements management”, Group Specification, ETSI GS MEC 010-2 V2.1.1, Nov. 2019, pp. 1-134, ETSI. [cited by applicant]
Waldner, “Geolocation-aware DNS with Bind”, Feb. 1, 2010, pp. 1-9, retrieved on May 12, 2023, retrieved from internet: https://backreference.org/2010/02/01/geolocation-aware-dns-with-bind/. [cited by applicant]
Microsoft Learn, “Use DNS Policy for Geo-Location Based Traffic Management with Primary Servers”, Sep. 20, 2021, pp. 1-6, retrieved on May 12, 2023, retrieved from internet: https://docs.microsoft.com/en-us/windows-serv… [cited by applicant]
ETSI, “Multi-access Edge Computing (MEC); MEC Management; Part 2: Application lifecycle, rules and requirements management”, Group Specification, ETSI GS MEC 010-2 V2.1.6, Sep. 2020, pp. 1-148, ETSI. [cited by applicant]