WO2023200885A1 - Fournisseur de services de télécommunication contrôlant un réseau sous-jacent dans un environnement de fournisseur de services en nuage - Google Patents
Fournisseur de services de télécommunication contrôlant un réseau sous-jacent dans un environnement de fournisseur de services en nuage Download PDFInfo
- Publication number
- WO2023200885A1 WO2023200885A1 PCT/US2023/018360 US2023018360W WO2023200885A1 WO 2023200885 A1 WO2023200885 A1 WO 2023200885A1 US 2023018360 W US2023018360 W US 2023018360W WO 2023200885 A1 WO2023200885 A1 WO 2023200885A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service provider
- cloud
- primary
- network
- telecommunication service
- Prior art date
Links
- 238000013461 design Methods 0.000 claims abstract description 21
- 238000000034 method Methods 0.000 claims abstract description 18
- 230000001413 cellular effect Effects 0.000 claims description 15
- 238000004891 communication Methods 0.000 claims description 8
- 238000003860 storage Methods 0.000 claims description 8
- 241000256836 Apis Species 0.000 claims 2
- 239000008186 active pharmaceutical agent Substances 0.000 claims 2
- 230000006870 function Effects 0.000 description 30
- 238000010586 diagram Methods 0.000 description 13
- 230000006855 networking Effects 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 7
- 230000008901 benefit Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 230000001276 controlling effect Effects 0.000 description 3
- 238000002955 isolation Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000001427 coherent effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
Definitions
- the present disclosure relates generally to telecommunication networks, more particularly, to controlling an underlay networks.
- 5G provides a broad range of wireless services delivered to the end user across multiple access platforms and multi-layer networks.
- 5G is a dynamic, coherent and flexible framework of multiple advanced technologies supporting a variety of applications.
- 5G utilizes an intelligent architecture, with Radio Access Networks (RANs) not constrained by base station proximity or complex infrastructure.
- RANs Radio Access Networks
- 5G enables a disaggregated, flexible, and virtual RAN with interfaces creating additional data access points.
- 5G network functions may be completely software-based and designed as cloudnative, meaning that they’re agnostic to the underlying cloud infrastructure, allowing higher deployment agility and flexibility.
- MEC Multi-Access Edge Computing
- This MEC technology is not exclusive to 5G but is certainly important to its efficiency. Characteristics of the MEC include the low latency, high bandwidth and real time access to RAN information that distinguishes 5G architecture from its predecessors. This convergence of the RAN and core networks enables operators to leverage new approaches to network testing and validation. 5G networks based on the 3GPP 5G specifications provide an environment for MEC deployment. The 5G specifications define the enablers for edge computing, allowing MEC and 5G to collaboratively route traffic. In addition to the latency and bandwidth benefits of the MEC architecture, the distribution of computing power better enables the high volume of connected devices inherent to 5G deployment and the rise of loT.
- the 3rd Generation Partnership Project (3GPP) develops protocols for mobile telecommunications and has developed a standard for 5G.
- the 5G architecture is based on what is called a Service-Based Architecture (SBA), which leverages IT development principles and a cloud-native design approach.
- SBA Service-Based Architecture
- each network function (NF) offers one or more services to other NFs via Application Programming Interfaces (API).
- API Application Programming Interfaces
- NFV Network function virtualization decouples software from hardware by replacing various network functions such as firewalls, load balancers and routers with virtualized instances running as software. This eliminates the need to invest in many expensive hardware elements and can also accelerate installation times, thereby providing revenue generating services to the customer faster.
- NFV enables the 5G infrastructure by virtualizing appliances within the 5G network. This includes the network slicing technology that enables multiple virtual networks to run simultaneously. NFV may address other 5G challenges through virtualized computing, storage, and network resources that are customized based on the applications and customer segments.
- the concept of NFV extends to the RAN through, for example, network disaggregation promoted by alliances such as 0-RAN. This enables flexibility, provides open interfaces and open-source development, ultimately to ease the deployment of new features and technology with scale.
- the 0-RAN ALLIANCE objective is to allow multi-vendor deployment with off-the shelf hardware for the purposes of easier and faster inter-operability.
- Network disaggregation also allows components of the network to be virtualized, providing a means to scale and improve user experience as capacity grows.
- the benefits of virtualizing components of the RAN provide a means to be more cost effective from a hardware and software viewpoint especially for loT applications where the number of devices is in the millions.
- the 5G New Radio (5GNR) RAN comprises of a set of radio base stations (each known as Next Generation Node B (gNB)) connected to the 5G core (5GC) and to each other.
- the gNB incorporates three main functional modules: the Centralized Unit (CU), the distributed Unit (DU), and the Radio Unit (RU), which can be deployed in multiple combinations.
- the primary interface is referred to as the Fl interface between DU and CU and are interoperable across vendors.
- the CU may be further disaggregated into the CU user plane (CU-UP) and CU control plane (CU-CP), both of which connect to the DU over Fl -U and Fl-C interfaces respectively.
- This 5G RAN architecture is described in 3GPP TS 38.401 V16.8.0 (2021-12).
- Each network function (NF) is formed by a combination of small pieces of software code called as microservices.
- one or more methods for enabling a telecommunication service provider to control an underlay network in cloud service provider environment include: providing, by a mobile network operator, a distributed unit (DU) of a fifth-generation New Radio (5GNR) cellular telecommunication network radio access network (RAN) that is served by a particular 5G NR cellular site base station, wherein the DU: is associated with a primary 5G NR Next Generation Node B (gNB) identified by a primary identifier (ID); and is in operable communication with a corresponding primary central unit control plane (CU-CP) of a 5G NR primary centralized unit (CU) that is hosted on a cloud-native virtualized compute instance in a primary cloud availability zone and is also associated with the primary gNB identified by the primary ID; dictating control of the underlay network to a telecommunication service provider in the cloud service provider environment; enabling control of a number of virtual routers to be deployed by the telecommunication service provider in the cloud service provider
- the Virtual Private Cloud design is configured to be similar to a design of the on-prem architecture of the telecommunication service provider.
- the each Passthrough Edge Data Center has two connections to its closest Direct Connect location.
- the each Passthrough Edge Data Center has two connections to its second closest Direct Connect location for diversity.
- the on-prem architecture of the telecommunication service provider has two connections to its closest Direct Connect location.
- the on-prem architecture of the telecommunication service provider has a dedicated circuit for Lab.
- the system uses 5G components for services in multiple target environments with full automation.
- the system uses native automation constructs instead of building overlay automation.
- the system uses a mix of cloud native APIs and existing telecom protocols.
- one or more systems for enabling a telecommunication service provider to control an underlay network in cloud service provider environment include: at least one memory that stores computer executable instructions; and at least one processor that executes the computer executable instructions to cause actions to be performed.
- Such actions include: provide, by a mobile network operator, a distributed unit (DU) of a fifth-generation New Radio (5G NR) cellular telecommunication network radio access network (RAN) that is served by a particular 5G NR cellular site base station, wherein the DU: is associated with a primary 5G NR Next Generation Node B (gNB) identified by a primary identifier (ID); and is in operable communication with a corresponding primary central unit control plane (CU-CP) of a 5G NR primary centralized unit (CU) that is hosted on a cloud-native virtualized compute instance in a primary cloud availability zone and is also associated with the primary gNB identified by the primary ID; dictate control of the underlay network to a telecommunication service provider in the cloud service provider environment; enable control of a number of virtual routers to be deployed by the telecommunication service provider in the cloud service provider environment; and manage route tables for the virtual routers deployed by the telecommunication service provider in the cloud service provider environment.
- the Virtual Private Cloud design is configured
- one or more non-transitory computer- readable storage mediums have computer-executable instructions stored thereon that, when executed by at least one processor, cause the at least one processor to: provide, by a mobile network operator, a distributed unit (DU) of a fifth-generation New Radio (5G NR) cellular telecommunication network radio access network (RAN) that is served by a particular 5G NR cellular site base station, wherein the DU: is associated with a primary 5G NR Next Generation Node B (gNB) identified by a primary identifier (ID); and is in operable communication with a corresponding primary central unit control plane (CU-CP) of a 5G NR primary centralized unit (CU) that is hosted on a cloud-native virtualized compute instance in a primary cloud availability zone and is also associated with the primary gNB identified by the primary ID; dictate control of the underlay network to a telecommunication service provider in the
- DU distributed unit
- 5G NR fifth-generation New Radio
- RAN telecommunication network radio access network
- Figure 1 illustrates a context diagram of a system that enables a telecommunication service provider to control an underlay network in cloud service provider environment may be implemented in accordance with embodiments described herein.
- Figure 2 illustrates a diagram of an example system architecture overview of a system in which the environment of Figure 1 may be implemented in accordance with embodiments described herein.
- Figure 3 illustrates a diagram showing connectivity between certain telecommunication network components during cellular telecommunication.
- Figure 4 illustrates a diagram of networking underlay with a Virtual Private Cloud design in a system that enables a telecommunication service provider to control an underlay network in cloud service provider environment.
- Figure 5 illustrates a diagram of networking underlay with a Breakout Edge Data Center in a system that enables a telecommunication service provider to control an underlay network in cloud service provider environment.
- Figure 6A illustrates a diagram of a 5G cloud computing network architecture in a system that enables a telecommunication service provider to control an underlay network in cloud service provider environment.
- Figure 6B is a logic diagram showing a telecommunication service provider controlling an underlay network in cloud service provider environment.
- Figure 7 shows a system diagram that describes an example implementation of a computing system(s) for implementing embodiments described herein.
- Figure 1 illustrates a context diagram of a system that enables a telecommunication service provider to control an underlay network in cloud service provider environment implemented, in accordance with embodiments described herein.
- a given area 100 will mostly be covered by two or more mobile network operators’ wireless networks.
- mobile network operators have some roaming agreements that allow users to roam from home network to partner network under certain conditions, shown in Figure 1 as home coverage area 102 and roaming partner coverage area 104.
- Operators may configure the mobile user’s device, referred to herein as user equipment (UE), such as UE 106, with priority and a timer to stay on the home network coverage area 102 versus the roaming partner network coverage area 104. If a UE (e.g., UE 106) cannot find the home network coverage area 102, the UE will scan for a roaming network after a timer expiration (6 minutes, for example).
- UE user equipment
- a 5G RAN is split into DUs (e.g., DU 108) that manage scheduling of all the users and a CU that manages the mobility and radio resource control (RRC) state for all the UEs.
- the RRC is a layer within the 5G NR protocol stack. It exists only in the control plane, in the UE and in the gNB. The behavior and functions of RRC are governed by the current state of RRC. In 5GNR, RRC has three distinct states: RRC IDLE, RRC CONNECTED and RRC INACTIVE.
- Figure 2 illustrates a diagram of an example system architecture overview of a system 200 in which the environment of Figure 1 may be implemented in accordance with embodiments described herein.
- the radio unit (RU) 206 converts radio signals sent to and from the antenna into a digital signal for transmission over packet networks. It handles the digital front end (DFE) and the lower physical (PHY) layer, as well as the digital beamforming functionality.
- DFE digital front end
- PHY physical
- the DU 204 may sit close to the RU 206 and runs the radio link control (RLC), the Medium Access Control (MAC) sublayer of the 5G NR protocol stack, and parts of the PHY layer.
- the MAC sublayer interfaces to the RLC sublayer from above and to the PHY layer from below.
- the MAC sublayer maps information between logical and transport channels. Logical channels are about the type of information carried whereas transport channels are about how such information is carried.
- This logical node includes a subset of the gNB functions, depending on the functional split option, and its operation is controlled by the CU 202.
- the CU 202 is the centralized unit that runs the RRC and Packet Data Convergence Protocol (PDCP) layers.
- a gNB may comprise a CU and one DU connected to the CU via Fs-C and Fs-U interfaces for control plane (CP) and user plane (UP) respectively.
- CP control plane
- UP user plane
- a CU with multiple DUs will support multiple gNBs.
- the split architecture enables a 5G network to utilize different distribution of protocol stacks between CU 202 and DU 204 depending on midhaul availability and network design.
- the CU 202 is a logical node that includes the gNB functions like transfer of user data, mobility control, RAN sharing, positioning, session management etc., with the exception of functions that may be allocated exclusively to the DU 204.
- the CU 202 controls the operation of several DUs 204 over the mid-haul interface.
- 5G network functionality is split into two functional units: the DU 204, responsible for real time 5G layer 1 (LI) and 5G layer 2 (L2) scheduling functions, and the CU 202 responsible for non-real time, higher L2 and 5G layer 3 (L3).
- the DU’s server and relevant software may be hosted on a cell site 216 itself or can be hosted in an edge cloud (local data center (LDC) 218 or central office) depending on transport availability and fronthaul interface.
- LDC local data center
- the CU’s server and relevant software may be hosted in a regional cloud data center or, as shown in Figure 2, in a breakout edge data center (B-EDC) 214.
- B-EDC breakout edge data center
- the DU 204 may be provisioned to communicate via a pass-through edge data center (P-EDC) 208.
- the P-EDC 208 may provide a direct circuit fiber connection from the DU directly to the primary cloud availability zone (e.g., B-EDC 214) hosting the CU 202.
- the LDC 218 and P-EDC 208 may be co-located or in a single location.
- the CU 202 may be connected to a regional cloud data center (RDC) 210, which in turn may be connected to a national cloud data center (NDC) 212.
- RDC regional cloud data center
- NDC national cloud data center
- the P-EDC 208, the LDC 218, the cell site 216 and the RU 206 may all be managed by the mobile network operator and the B-EDC 214, the RDC 210 and the NDC 212 may all be managed by a cloud computing service provider.
- the actual split between DU and RU may be different depending on the specific use-case and implementation.
- Figure 3 is a diagram showing connectivity between certain telecommunication network components during cellular telecommunication in accordance with embodiments described herein.
- the central unit control plane for example of CU 110 of Figure 1 or CU 202 of Figure 2, primarily manages control processing of DUs, such as DU 308, and UEs, such as UE 302.
- the CU-CP 302 hosts RRC and the control-plane part of the PDCP protocol.
- CU-CP 302 manages the mobility and radio resource control (RRC) state for all the UEs.
- RRC radio resource control
- the RRC is a layer within the 5G NR protocol stack and manages context and mobility for all UEs. The behavior and functions of RRC are governed by the current state of RRC. In 5G NR, RRC has three distinct states: RRC IDLE, RRC CONNECTED and RRC INACTIVE.
- the CU-CP 302 terminates the El interface connected with the central unit user plane (CU-UP) 304 and the Fl-C interface connected with the DU 308.
- the DU 308 maintains a constant heartbeat with CU 302.
- the CU-UP 304 manages the data sessions for all UEs 306 and hosts the user plane part of the PDCP protocol.
- the CU-UP 304 terminates the El interface connected with the CU-CP and the Fl-U interface connected with the DU 308.
- FIG. 4 a Networking Underlay architecture is shown for a Virtual Private Cloud (VPC) design in a system that enables a telecommunication service provider to control an underlay network in cloud service provider environment.
- An underlay network is the physical network responsible for the delivery of packets such as IP packets.
- a virtual private cloud is a configurable pool of shared resources allocated within a public cloud environment.
- the VPC provides isolation between one VPC user and all other users of the same cloud, for example, by allocation of a private IP subnet and a virtual communication construct (e.g., a VLAN or a set of encrypted communication channel) per user.
- a virtual communication construct e.g., a VLAN or a set of encrypted communication channel
- FIG. 4 displays one embodiment of VPCs used by the system that enables a telecommunication service provider to control an underlay network in cloud service provider environment.
- this 5G network leverages the distributed nature of 5G cloud-native network functions and Cloud flexibility, which optimizes the placement of 5G network functions for optimal performance based on latency, throughput and processing requirements.
- the network architecture utilizes a logical hierarchical architecture consisting of National Data Centers (NDCs), Regional Data Centers (RDCs) and Breakout Edge Data Centers (BEDCs), as shown in Figure 4, to accommodate the distributed nature of 5G functions and the varying requirements for service layer integration.
- BEDCs are deployed in Local Zones hosting 5G NFs that have strict latency budgets. They are connected with Passthrough Edge Data Centers (PEDC), which serve as an aggregation point for all Local Data Centers (LDCs) and cell sites in a particular market.
- PEDC Passthrough Edge Data Centers
- LDCs Local Data Centers
- BEDCs also provide internet peering for 5G data service.
- the NDCs host a nationwide global service such as OSS (Operating Support System) and BSS (Billing Support System).
- NDC is hosted in the Region and spans multiple AZs for high availability.
- NDCs are mapped to Regions where three NDCs are built in three U.S. Regions (Region A, Region B, and Region C).
- An NDC is built to span across two AZs for high availability.
- DirectConnect Gateways Also shown in the network architecture displayed in Figure 4 are DirectConnect Gateways, Transit Gateways, DirectConnect Routers, Internet Gateways, NAT Gateways, system routers, and virtual routers.
- an O-RAN network may be implemented that includes an RU (Radio Unit), which is deployed on towers and a DU (Distributed Unit), which controls the RU. These units interface with the Centralized Unit (CU), which is hosted in the BEDC at the Local Zone. These combined pieces provide a full RAN solution that handles all radio level control and subscriber data traffic.
- RU Radio Unit
- DU Distributed Unit
- CU Centralized Unit
- the User Plane Function (Data Network Name (DNN)) is collocated in the BEDC, which anchors user data sessions and routes to the internet.
- the BEDCs leverage local internet access available in Local Zones, which allows for a better user experience while optimizing network traffic utilization.
- the Regional Data Centers are hosted in the Region across multiple availability zones.
- the RDCs host 5G subscribers’ signaling processes such as authentication and session management as well as voice for 5G subscribers. These workloads can operate with relatively high latencies, which allows for a centralized deployment throughout a region, resulting in cost efficiency and resiliency.
- 3 RDCs are deployed in a region, each in a separate Availability Zone (AZ) to ensure application resiliency and high availability.
- AZ Availability Zone
- an AZ is one or more discrete data centers with redundant power, networking, and connectivity in a Region.
- AZs in a Region are interconnected with high-bandwidth and low-latency networking over a fully redundant, dedicated metro fiber, which provides high-throughput, low-latency networking between AZs.
- Cloud Native Functions deployed in the RDC utilizes a high speed backbone to failover between AZs for application resiliency.
- CNFs like AMF and SMF, which are deployed in RDC, continue to be accessible from the BEDC in the Local Zone in case of an AZ failure. They serve as the backup CNF in the neighboring AZ and would take over and service the requests from the BEDC.
- VPCs are implemented for each Data Center type (e.g., local data center, breakout edge data center, regional data center, national data center, and the like).
- Data Center type e.g., local data center, breakout edge data center, regional data center, national data center, and the like.
- the national data center VPC stretches across multiple Availability Zones (AZs).
- two or more AZs are implemented per region of the cloud computing service provider.
- the regional data center VPCs are confined into a single AZ per region.
- the breakout edge data center includes two of more VPCs. These two of more VPCs may include Direct Connect (DX) Virtual Private Clouds and Internet Virtual Private Clouds.
- DX Direct Connect
- the system architecture includes one dedicated Virtual Private Cloud per region.
- Software-Defined Data Center software may be implemented to the Cloud Infrastructure, which enables customers to run production applications across private cloud environments.
- a transit gateway is dedicated to each environment.
- a transit gateway is a network transit hub that may be used to interconnect virtual private clouds (VPCs) with on-premises networks.
- VPCs virtual private clouds
- the transit gateway enables peering between regions.
- VPC Peering enables VPC resources like EC2 instances (e.g., virtual servers in an Elastic Compute Cloud (EC2) for running applications), Relational Database Service (RDS) databases and Lambda functions (e.g., server-less compute services that run code in response to events and automatically manage underlying compute resources) running in different regions to communicate with each other using private IP addresses, without requiring gateways, VPN connections, or separate network appliances.
- EC2 instances e.g., virtual servers in an Elastic Compute Cloud (EC2) for running applications
- RDS Relational Database Service
- Lambda functions e.g., server-less compute services that run code in response to events and automatically manage underlying compute resources
- each traffic from virtual routers is encapsulated using Generic Routing Encapsulation (GRE) tunnels, creating an Overlay Network.
- GRE Generic Routing Encapsulation
- the Overlay network uses Intermediate Systems to Intermediate Systems (IS-IS) routing protocol in conjunction with Segment Routing Multi -Protocol Label Switching (SR-MPLS) to distribute routing information and establish network reachability between the virtual routers.
- IS-IS Intermediate Systems to Intermediate Systems
- SR-MPLS Segment Routing Multi -Protocol Label Switching
- MP-BGP Multi -Protocol Border Gateway Protocol
- the combined solution provides the ability to honor requirements, such as traffic isolation and efficiently route traffic between on- prem, and 3rd parties (e.g., voice aggregators, regulatory entities, and the like).
- the VPC enables the launch of CNF resources on a virtual network.
- This virtual network is intended to closely resemble an on-premises network, but also contains all the resources needed for Data Center functions.
- the VPCs hosting each of the DCs are interconnected utilizing global network and Transit Gateway.
- the Transit Gateway is used in Regions to provide connectivity between VPCs deployed in the NDCs, RDCs, and BEDCs with scalability and resilience.
- the Direct Connect location provides connectivity from RAN DUs (on-prem) to Local Zones where cell sites are homed. Cell sites are mapped to a particular Local Zone based on proximity to meet 5G RAN mid-haul latency expected between DU and CU.
- each Region hosts one NDC and three RDCs.
- the NDC functions communicate to each other through the Transit Gateway, where each VPC has an attachment to the specific regional Transit Gateway.
- EC2 and native networking is referred to as “Underlay Network” in this network architecture. Provisioning of Transit Gateway and required attachments are automated using CI/CD pipelines with AWS APIs. Transit Gateway routing tables are utilized to maintain isolation of traffic between functions.
- some of the 5G core network functions require support for advanced routing capabilities inside VPC and across VPCs (e.g., UPF, SMF and ePDG). These functions reply on routing protocols such as BGP for route exchange and fast failover (both stateful and stateless).
- routing protocols such as BGP for route exchange and fast failover (both stateful and stateless).
- virtual routers are deployed on EC2 to provide connectivity within and across VPCs, as well as back to the on-prem network.
- telco-grade networks resiliency drives the design configuration. Redundancy and resiliency are addressed at various layers of the 5G stack. Transport availability in failure scenarios is also discussed herein. High availability and georedundancy are NF dependent, while some NFs are required to maintain state.
- High availability and georedundancy are required.
- High availability is achieved by deploying two redundant NFs in two separate availability zones within a single VPC. Failover within an AZ can be recovered within the region without the need to route traffic to other regions.
- the in-region networking uses the underlay and overlay constructs, which enable on-prem traffic to seamlessly flow to the standby NF in the secondary AZ if the active NF becomes unavailable.
- Geo-Redundancy is achieved by deploying two redundant NFs in two separate availability zones in more than one region. This is achieved by interconnecting all VPCs via inter-region Transit Gateway and leveraging v-router for overlay networking.
- the overlay network is built as a full-mesh enabling service continuity using the NFs deployed across NDCs in other regions (e.g., Markets, B-EDCs, RDCs, in Region A can continue to function using the NDC in Region B).
- RDCs high availability and geo-redundancy are achieved by NFs failover between VPCs (multiple Availability zones) within one region.
- VPCs multiple Availability zones
- These RDCs are interconnected via Transit Gateway with the v-router-based overlay network. This provides on-premise and B-EDC reachability to the NFs deployed in each RDC with route policies in place to ensure traffic only flows to the backup RDCs, if the primary RDC becomes unreachable.
- a RAN network is connected, through PEDC, to two different direct connect locations for reachability into the region and local zone This allows for DU traffic to be rerouted from an active BEDC to backup BEDC in the event a local zone fails.
- each Passthrough Edge Data Center has two connections to its closest Direct Connect location.
- each Passthrough Edge Data Center has two connections to its second closest Direct Connect location for diversity.
- the on-prem architecture of the telecommunication service provider has two connections to its closest Direct Connect location.
- the on-prem architecture of the telecommunication service provider has a dedicated circuit for Lab.
- the network architecture uses 5G components for services in multiple target environments with full automation.
- the network architecture uses native automation constructs instead of building overlay automation.
- the network architecture uses a mix of cloud native APIs and existing telecom protocols.
- route tables are managed for the virtual routers deployed by the telecommunication service provider in the cloud service provider environment.
- optional operation 680 is included, in which the Virtual Private Cloud design is configured to be similar to a design of the on-prem architecture of the telecommunication service provider.
- Figure 7 shows a system diagram that describes an example implementation of a computing system(s) for implementing embodiments described herein.
- the functionality described herein for a system that enables a telecommunication service provider to control an underlay network in cloud service provider environment can be implemented either on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.
- such functionality may be completely software-based and designed as cloud-native, meaning that they’re agnostic to the underlying cloud infrastructure, allowing higher deployment agility and flexibility.
- such computer system(s) 701 may represent those in various data centers and cell sites shown and/or described herein that host the functions, components, microservices and other aspects described herein to implement a system that enables a telecommunication service provider to control an underlay network in cloud service provider environment.
- one or more special-purpose computing systems may be used to implement the functionality described herein.
- various embodiments described herein may be implemented in software, hardware, firmware, or in some combination thereof.
- Host computer system(s) 701 may include memory 702, one or more central processing units (CPUs) 714, I/O interfaces 718, other computer- readable media 720, and network connections 722.
- CPUs central processing units
- Memory 702 may include one or more various types of non-volatile and/or volatile storage technologies. Examples of memory 702 may include, but are not limited to, flash memory, hard disk drives, optical drives, solid-state drives, various types of random-access memory (RAM), various types of read-only memory (ROM), other computer-readable storage media (also referred to as processor-readable storage media), or the like, or any combination thereof. Memory 702 may be utilized to store information, including computer-readable instructions that are utilized by CPU 714 to perform actions, including those of embodiments described herein.
- Memory 702 may have stored thereon control module(s) 704.
- the control module(s) 704 may be configured to implement and/or perform some or all of the functions of the systems, components and modules described herein for a system that enables a telecommunication service provider to control an underlay network in cloud service provider environment.
- Memory 702 may also store other programs and data 710, which may include rules, databases, application programming interfaces (APIs), software platforms, cloud computing service software, network management software, network orchestrator software, network functions (NF), Al or ML programs or models to perform the functionality described herein, user interfaces, operating systems, other network management functions, other NFs, etc.
- APIs application programming interfaces
- NF network functions
- Al or ML programs or models to perform the functionality described herein, user interfaces, operating systems, other network management functions, other NFs, etc.
- Network connections 722 are configured to communicate with other computing devices to facilitate the functionality described herein.
- the network connections 722 include transmitters and receivers (not illustrated), cellular telecommunication network equipment and interfaces, and/or other computer network equipment and interfaces to send and receive data as described herein, such as to send and receive instructions, commands and data to implement the processes described herein.
- I/O interfaces 718 may include a video interfaces, other data input or output interfaces, or the like.
- Other computer-readable media 720 may include other types of stationary or removable computer-readable media, such as removable flash drives, external hard drives, or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Des modes de réalisation concernent des systèmes et des procédés pour permettre à un fournisseur de services de télécommunication de contrôler un réseau sous-jacent dans un environnement de fournisseur de services en nuage. Un tel procédé consiste à : dicter le contrôle du réseau sous-jacent à un fournisseur de services de télécommunication dans l'environnement de fournisseur de services en nuage ; permettre le contrôle d'un nombre de routeurs virtuels devant être déployés par le fournisseur de services de télécommunication dans l'environnement de fournisseur de services en nuage ; et gérer des tables de routage pour les routeurs virtuels déployés par le fournisseur de services de télécommunication dans l'environnement de fournisseur de services en nuage. Dans certains modes de réalisation, le modèle de nuage privé virtuel est configuré pour être similaire à un modèle de l'architecture sur site du fournisseur de services de télécommunication.
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202263331121P | 2022-04-14 | 2022-04-14 | |
US63/331,121 | 2022-04-14 | ||
US18/101,067 US11843537B2 (en) | 2022-04-14 | 2023-01-24 | Telecommunication service provider controlling an underlay network in cloud service provider environment |
US18/101,067 | 2023-01-24 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023200885A1 true WO2023200885A1 (fr) | 2023-10-19 |
Family
ID=86331895
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2023/018360 WO2023200885A1 (fr) | 2022-04-14 | 2023-04-12 | Fournisseur de services de télécommunication contrôlant un réseau sous-jacent dans un environnement de fournisseur de services en nuage |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2023200885A1 (fr) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200068639A1 (en) * | 2018-08-27 | 2020-02-27 | Samsung Electronics Co., Ltd | Method and apparatus for performing dual connectivity in heterogeneous network |
US20220014963A1 (en) * | 2021-03-22 | 2022-01-13 | Shu-Ping Yeh | Reinforcement learning for multi-access traffic management |
US20220109622A1 (en) * | 2021-12-14 | 2022-04-07 | Intel Corporation | Reliability enhancements for multi-access traffic management |
-
2023
- 2023-04-12 WO PCT/US2023/018360 patent/WO2023200885A1/fr unknown
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200068639A1 (en) * | 2018-08-27 | 2020-02-27 | Samsung Electronics Co., Ltd | Method and apparatus for performing dual connectivity in heterogeneous network |
US20220014963A1 (en) * | 2021-03-22 | 2022-01-13 | Shu-Ping Yeh | Reinforcement learning for multi-access traffic management |
US20220109622A1 (en) * | 2021-12-14 | 2022-04-07 | Intel Corporation | Reliability enhancements for multi-access traffic management |
Non-Patent Citations (2)
Title |
---|
3GPP TS 38.401, December 2021 (2021-12-01) |
SHINDE SWAPNIL SADASHIV ET AL: "A network operator-biased approach for multi-service network function placement in a 5G network slicing architecture", COMPUTER NETWORKS, ELSEVIER, AMSTERDAM, NL, vol. 201, 9 November 2021 (2021-11-09), XP086877947, ISSN: 1389-1286, [retrieved on 20211109], DOI: 10.1016/J.COMNET.2021.108598 * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN113452547B (zh) | 实现容错多nrf网络拓扑 | |
US20240107333A1 (en) | Geographically redundant and high availability system architecture for a hybrid cloud cellular network | |
US20230337047A1 (en) | Utilization of replicated pods with distributed unit applications | |
US11843537B2 (en) | Telecommunication service provider controlling an underlay network in cloud service provider environment | |
US11838150B2 (en) | Leveraging a virtual router to bridge between an underlay and an overlay | |
US20240064042A1 (en) | Leveraging a virtual router to bridge between an underlay and an overlay | |
US20230336476A1 (en) | Use of an overlay network to interconnect between a first public cloud and second public cloud | |
WO2023200885A1 (fr) | Fournisseur de services de télécommunication contrôlant un réseau sous-jacent dans un environnement de fournisseur de services en nuage | |
US20230336996A1 (en) | Universal unlock microservice system and method | |
WO2023200878A1 (fr) | Utilisation d'un réseau de recouvrement pour assurer une interconnexion entre un premier nuage public et un second nuage public | |
US20230337022A1 (en) | System and method for alerts collection from 5g network | |
US20230328590A1 (en) | Systems and methods for a pass-through edge data center (p-edc) in a wireless telecommunication network | |
US20240057144A1 (en) | 5g prb blanking system with 5g phone to prevent interference between signal transmissions from different networks | |
US20240048963A1 (en) | Blockchain-based system that records the states of 5g end user mobile devices using the distributed ledger | |
US20230327987A1 (en) | Concurrently supporting internet protocol version 6 (ipv6) and internet protocol version 4 (ipv4) in a cloud-managed wireless telecommunication network | |
US20230337113A1 (en) | Managing multiple transit gateway routing tables to implement virtual routing and forwarding functionality | |
US20230336473A1 (en) | Overlay from on-premises router to cloud service provider environment for telecommunication network functions (nfs) to handle multiple virtual routing and forwarding (vrf) protocols | |
US20240056934A1 (en) | System and method for predictive inter-carrier hand-off to mitigate problematic coverage areas | |
US20230336405A1 (en) | Failover of cloud-native network functions within node groups for high availability in a wireless telecommunication network | |
US20230276271A1 (en) | Managing user experiences during cellular telecommunication network outage utilizing a backup data center | |
US20230337018A1 (en) | Centralized unit user plane (cu-up) and centralized unit control plane (cu-cp) standby pods in a cloud-native fifth generation (5g) wireless telecommunication network | |
US20230337055A1 (en) | Usage of wireless telecommunication service provider autonomous system number (asn) in a cloud-native wireless telecommunication network | |
US20240048961A1 (en) | Blockchain-based system for reestablishing sequencing after connection loss between distributed subscriber database and a 5g core | |
US20230337019A1 (en) | Microservices for centralized unit user plane (cu-up) and centralized unit control plane (cu-cp) standby pods in a cloud-native fifth generation (5g) wireless telecommunication network | |
US20230336482A1 (en) | Overcoming limitations of a virtual private cloud (vpc) implemented on a public cloud in a cloud-native fifth generation (5g) wireless telecommunication network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23723292 Country of ref document: EP Kind code of ref document: A1 |