IP Library Granted Patent US 12,563,374
Granted Patent B2
US 12,563,374 · App. 17/544,825 · Granted Feb 24, 2026

Locality-based network slicing in radio-based networks

Inventors: Alexey Gadalin (Kirkland, WA); Diwakar Gupta (Seattle, WA); Rudresh Amin (Danville, CA); Yatin Patil (Redmond, WA); Kaixiang Hu (Fremont, CA); Dimitrios Elissaios (Seattle, WA)
Assignee: Amazon Technologies, Inc.
H04W4/50H04W4/021H04W28/16H04W40/34H04W48/04
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,563,374
App. No.
17/544,825
Filed
Dec 7, 2021
Granted
Feb 24, 2026
Kind
B2
Examiner
LAM, DUNG LE
Art Unit
2646
USPC
455/418
Abstract

Disclosed are various embodiments for locality-based network slicing in radio-based networks. In one embodiment, network traffic is received via a network slice in a radio-based network. The radio-based network includes a radio access network and an associated core network. The network slice is associated with at least one locality rule requiring that the network traffic remain within a particular geographic area. It is determined that the radio-based network has resources to comply with the locality rule(s). The network traffic in the radio-based network is acted upon in order to comply with the locality rule(s).

Claims (33)

1 . A computer-implemented method, comprising:

receiving network traffic via a network slice in a radio-based network, the radio-based network including a radio access network and an associated core network, the network slice being associated with at least one locality rule requiring that the network traffic remain within a particular geographic area;

determining that the radio-based network has resources to comply with the at least one locality rule;

acting upon a first portion of the network traffic in the radio-based network in order to comply with the at least one locality rule;

blocking communication of a second portion of the network traffic, received via the network slice, that violates the at least one locality rule;

receiving other network traffic via the network slice in the radio-based network;

determining that the radio-based network does not have the resources to comply with the at least one locality rule with respect to routing the other network traffic; and

sending a notification to a user device indicating that an exception to the at least one locality rule is necessary to route the other network traffic.

2 . The computer-implemented method of claim 1 , further comprising storing data records associated with the network traffic within the particular geographic area in order to comply with the at least one locality rule.

3 . The computer-implemented method of claim 1 , further comprising:

receiving other network traffic via a different network slice in the radio-based network, the different network slice being unassociated with the at least one locality rule; and

selecting a different route for the other network traffic received via the different network slice in the radio-based network in which the other network traffic received via the different network slice exits the particular geographic area.

4 . The computer-implemented method of claim 1 , further comprising determining that the network traffic is sent via the network slice based at least in part on at least one of: a source application of the network traffic, a source client device of the network traffic, or a tag in the network traffic.

5 . The computer-implemented method of claim 1 , wherein determining that the radio-based network has the resources to comply with the at least one locality rule further comprises allocating one or more additional resources to the radio-based network in the particular geographic area in order to comply with the at least one locality rule.

6 . The computer-implemented method of claim 1 , wherein acting upon the first portion of the network traffic in the radio-based network in order to comply with the at least one locality rule further comprises selecting for a route a particular communication link between the radio access network and the associated core network, wherein an entirety of the particular communication link is within the particular geographic area.

7 . The computer-implemented method of claim 1 , wherein acting upon the first portion of the network traffic in the radio-based network in order to comply with the at least one locality rule further comprises selecting a particular instance of a network function to process the network traffic, the particular instance being selected from a plurality of instances of the network function in the radio-based network based at least in part on the particular instance being within the particular geographic area.

8 . The computer-implemented method of claim 7 , wherein at least one other instance of the plurality of instances of the network function in the radio-based network are outside of the particular geographic area.

9 . A system, comprising:

a radio-based network comprising a radio access network and an associated core network; and

at least one computing device configured to at least:

receive network traffic via a network slice in the radio-based network, the network slice being associated with at least one locality rule requiring that the network traffic remain within a particular geographic area;

determine that the radio-based network has resources to comply with the at least one locality rule;

act upon the a first portion of the network traffic in the radio-based network in order to comply with the at least one locality rule;

block communication of a second portion of the network traffic, received via the network slice, that violates the at least one locality rule;

receive other network traffic sent via the network slice to a destination outside of the particular geographic area; and

block communicating the other network traffic to the destination pending an approval of an exception to the at least one locality rule.

10 . The system of claim 9 , wherein at least a portion of the associated core network is provisioned in a cloud provider network, and the at least one computing device is in the cloud provider network.

11 . The system of claim 9 , wherein the at least one computing device is further configured to at least:

receive a request to provision the network slice; and

provision the network slice in the radio-based network in compliance with the at least one locality rule by using physical hardware located within the particular geographic area.

12 . The system of claim 11 , wherein provisioning the network slice in the radio-based network further comprises deploying at least one provider substrate extension within the particular geographic area in response to the request.

13 . The system of claim 9 , wherein the at least one computing device is further configured to at least scale computing resources allocated to the network slice within the particular geographic area based at least in part on a utilization of the network slice.

14 . The system of claim 9 , wherein the at least one computing device is further configured to at least store data records relating to the network traffic in a data storage service within the particular geographic area.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 10, 2021
From: GADALIN, ALEXEY; GUPTA, DIWAKAR; AMIN, RUDRESH; PATIL, YATIN; HU, KAIXIANG; ELISSAIOS, DIMITRIOS
To: AMAZON TECHNOLOGIES, INC.
Reel/Frame 058355/0945 →
Continuity (1)
Related Publication 20230179974A1 · Jun 8, 2023
References Cited (30)
US 9098344B2 · Chandramouli et al. · 2015 [cited by applicant]
US 11716246B2 · Lee et al. · 2023 [cited by applicant]
US 11917483B2 · Matray et al. · 2024 [cited by applicant]
US 20160337179A1 · Rao et al. · 2016 [cited by applicant]
US 20180077023A1 · Zhang et al. · 2018 [cited by applicant]
US 20180123878A1 · Li et al. · 2018 [cited by applicant]
US 20210144517A1 · Guim Bernat et al. · 2021 [cited by applicant]
US 20210157848A1 · Doshi et al. · 2021 [cited by applicant]
US 20210345357A1 · Ijntema · 2021 [cited by examiner]
US 20210360447A1 · Bor-Yaliniz · 2021 [cited by examiner]
US 20220078081A1 · Mahdi et al. · 2022 [cited by applicant]
US 20220150125A1 · Kumar et al. · 2022 [cited by applicant]
US 20220217610A1 · Zheng · 2022 [cited by examiner]
US 20220225094A1 · Chong et al. · 2022 [cited by applicant]
US 20220264444A1 · Ryu · 2022 [cited by examiner]
US 20220264525A1 · Simon et al. · 2022 [cited by applicant]
US 20220294709A1 · Mannweiler · 2022 [cited by examiner]
US 20220400425A1 · Cakulev · 2022 [cited by examiner]
US 20230007483A1 · Mueck et al. · 2023 [cited by applicant]
US 20230027736A1 · McLachlan et al. · 2023 [cited by applicant]
US 20230075276A1 · Zhu · 2023 [cited by examiner]
US 20230276199A1 · Ryu · 2023 [cited by examiner]
US 20230370330A1 · Lee et al. · 2023 [cited by applicant]
US 20230403543A1 · Pateromichelakis · 2023 [cited by examiner]
US 20240028766A1 · McLachlan et al. · 2024 [cited by applicant]
US 20240045851A1 · Li et al. · 2024 [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/544,817 mailed Apr. 30, 2024. [cited by applicant]
International Search Report and Written Opinion for PCT/US22/80988 mailed Feb. 28, 2024. [cited by applicant]
Simone Redana et al: “5G PPP Architecture Working Group—View on 5G Architecture, Version 3.0”, Jun. 19, 2019 (Jun. 19, 2019), pp. 1-166, XP055736939, DOI: 10.5281/zenodo.3265031 Retrieved from the Internet: URL: https:/… [cited by applicant]
Yoshinori Goto Nippon Telegraph and Telephone Corporation Japan: “Draft Supplement 44 to Y.3100-series (formerly Suppl. To Y.IMT2020 series);TD092/WP1”, ITU-T Draft; Study Period 2017-2020; Study Group 13; Series TD092/… [cited by applicant]