WO2023200881A1 - Fourniture de réseau à de multiples cœurs - Google Patents

Fourniture de réseau à de multiples cœurs Download PDF

Info

Publication number
WO2023200881A1
WO2023200881A1 PCT/US2023/018356 US2023018356W WO2023200881A1 WO 2023200881 A1 WO2023200881 A1 WO 2023200881A1 US 2023018356 W US2023018356 W US 2023018356W WO 2023200881 A1 WO2023200881 A1 WO 2023200881A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
order
cloud core
cloud
application programming
Prior art date
Application number
PCT/US2023/018356
Other languages
English (en)
Inventor
Jeffrey S. Wendeborn
Venkata Sai Pavan Nori
Original Assignee
Dish Wireless L.L.C.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US17/887,722 external-priority patent/US20230336954A1/en
Application filed by Dish Wireless L.L.C. filed Critical Dish Wireless L.L.C.
Publication of WO2023200881A1 publication Critical patent/WO2023200881A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1006—Server selection for load balancing with static server selection, e.g. the same server being selected for a specific client

Definitions

  • the present disclosure relates generally to network provisioning and, more particularly, to dynamically provisioning networking features to different cloud cores.
  • embodiments are directed toward systems and methods of provisioning multiple cloud cores for new wireless services.
  • An order for new wireless service for a customer is received.
  • the customer of the order is determined, and one or more networking services, such as a first service and a second service, are selected for that order based on the identification of the customer.
  • a first cloud core is then provisioned for the first service, and a different second cloud core is provisioned for the second service.
  • networking services for the second order are identified and additional cloud cores are provisioned for those services. In this way, separate cloud cores are provisioned for separate networking services.
  • Identifying the first service and the second service associated with the order may include selecting a first application programming interface end point that is associated with the first service and selecting a second application programming interface end point that is associated with the second service.
  • the first and second application programming interface end points can then be used to provision the cloud cores.
  • the first application programming interface end point can be employed to call the first cloud core with the order for the first service
  • the second application programming interface end point can be employed to call the second cloud core with the order for the second service.
  • a plurality of application programming interface end points can be grouped into a region of end points. Different cloud cores can then be assigned to each of the plurality of application programming interface end points and one or more customers can be assigned to the group of end points. In this way, the region or group of end points is selected from multiple regions based on the customer, and the first and second application programming interface end points are selected from the group of end points.
  • Figure 1 illustrates a context diagram of an environment for dynamically provisioning multiple cloud cores for new wireless network service in accordance with embodiments described herein;
  • Figure 2 is a context diagram of a non-limiting embodiment of systems that provide functionality to dynamically provision multiple cloud cores in accordance with embodiments described herein;
  • Figure 3 illustrates a logical flow diagram showing one embodiment of a process for dynamically provisioning multiple cloud cores for new wireless network service in accordance with embodiments described herein;
  • Figure 4 shows a system diagram that describe various implementations of computing systems for implementing embodiments described herein.
  • Figure 1 illustrates a context diagram of an environment 100 for dynamically provisioning multiple cloud cores for new wireless network service in accordance with embodiments described herein.
  • Environment 100 includes a plurality of cells 112a-112c, a plurality of customer or user devices 124a- 124b, a network-service-management computing device 102, a cloud computing environment 104, and a communication network 110.
  • the customer devices 124a-124c are computing devices that receive and transmit cellular communication messages with the cells 112a- 112c.
  • Examples of customer devices 124a-124c may include, but are not limited to, mobile devices, smartphones, tablets, cellular-enabled laptop computers, or other computing devices that can communication with a cellular network.
  • the cells 112a-112c are cellular towers that together provide the hardware infrastructure of a cellular communications network, e.g., a 5G cellular communications network.
  • the cells 112a-112c may include or be in communication with base stations, radio back haul equipment, antennas, or other devices, which are not illustrated for ease of discussion.
  • the cells 112a-112c may communicate with each other via communication network 110.
  • Communication network 110 includes one or more wired or wireless networks, which may include a series of smaller or private connected networks that carry information between the cells 112a-112c.
  • the cloud computing environment 104 is a collection of computing resources that can be utilized to form separate virtual computing environments for use by computing devices. These virtual computing environments can be provisioned as cloud-computing cores to perform functionality associated with a particular networking service.
  • the network-service-management computing device 102 is configured to manage orders for new wireless services for customer devices 124a-124b, such as when a new customer device 124 requests access to join the communication network or is setup to join the communication network.
  • the network-service-management computing device 102 determines which networking services are to be setup and initialized for that new customer device 124 based on the order received for that customer device 124.
  • the network- service-management computing device 102 communicates with the cloud computing environment 104 to provision separate cloud-computing cores for the separate networking services for that customer device 124.
  • the networking services may be specific network functions (e.g., management of data usage for the customer device, management of voice usage for the customer device, management of messaging usage for the customer device, etc.), test environments (e.g., device-specific testing, load balancing testing, etc.), or other functionality to facilitate and manage the communication network.
  • specific network functions e.g., management of data usage for the customer device, management of voice usage for the customer device, management of messaging usage for the customer device, etc.
  • test environments e.g., device-specific testing, load balancing testing, etc.
  • FIG 2 is a context diagram of a non-limiting embodiment of systems that provide functionality to dynamically provision multiple cloud cores in accordance with embodiments described herein.
  • Example 200 includes network-service-management computing device 102 and cloud computing environment 104, similar to the network-service-management computing device 102 and the cloud computing environment 104 shown in Figure 1.
  • the network-service-management computing device 102 is configured to manage new wireless service orders.
  • the network-service- management computing device 102 may include a cloud-core-provisioning module 204 and an order-management module 206.
  • the order-management module 206 is configured to receive orders for new wireless services. These orders may be received from a customer device that is being added to the wireless communication network, or they may be generated by the ordermanagement module 206 on behalf of a customer device.
  • the ordermanagement module 206 determines which networking services are to be used or initialized for each order.
  • the order-management module 206 communicates those networking services to the cloud-core-provisioning module 204.
  • the cloud-core-provisioning module 204 utilizes API end points that are associated with the networking services to provision cloud-computing cores in the cloud computing environment 104.
  • cloud-core-provisioning module 204 and the ordermanagement module 206 are illustrated as separate modules, embodiments are not so limited. Rather, functionality of the cloud-core-provisioning module 204 and the order-management module 206 may be performed by a single module or a plurality of modules.
  • the cloud computing environment 104 provisions and maintains cloud-computing cores for the different networking services being established for different customers.
  • the cloud computing environment 104 has provisioned cores 224a-224c for customer 220a and has provisioned cores 226a-226c for customer 220b. Each separate core is provisioned to perform the functionality of a different networking service.
  • Figure 3 illustrates a logical flow diagram showing one embodiment of a process 300 for dynamically provisioning multiple cloud cores for new wireless network service in accordance with embodiments described herein.
  • process 300 may be implemented by or executed via circuitry or on one or more computing devices, such as network-service-management computing device 102 in Figure 1.
  • Process 300 begins, after a start block, at block 302 where a plurality of networking services are assigned to a plurality of API end points.
  • each separate networking service is assigned to one API end point.
  • a networking service may be assigned to multiple API end points.
  • a cloud core associated with the networking service is also assigned to the same API end point as the networking service.
  • the networking services may include network functions, device test environments, network capacity test environments, network load test environments, or other computing environments associated with a wireless network.
  • Process 300 proceeds to block 304, where one or more groups of API end points are generated. These groups may be referred to a regions of networking services. Each group may include one or more API end points. Accordingly, one or more networking services are associated with each group. In some embodiments, a same API end point may be in two or more different groups. In other embodiments, each group includes a unique set of API end points.
  • Process 300 continues at block 306, where one or more customers are assigned to each group.
  • this assignment may be for specific customers, such as a list of customer identifiers.
  • a category or characteristic of customers may be used to assign customers to a group of API end points without assigning specific customers to the group.
  • Process 300 proceeds next to block 308, where an order for new wireless service is received for a customer device.
  • the order may be to establish networking services for a new customer.
  • the order may also be to change or modify networking services for an existing customer.
  • the order may be to change from a data networking service to a messaging networking service for an existing customer.
  • the order identifies the customer associated with the device and the new wireless service.
  • the order may also indicate which networking services are to be employed for that customer, such as data, voice, messaging, device management, subscription, roaming, etc.
  • Process 300 continues next at block 310, where a customer is determined for the order.
  • the order itself may include a customer identifier that is used to determine the customer.
  • a database that maps customer devices to customer identifiers or customer identification may be accessed using the customer device information in the order to determine the customer identifier or customer identification.
  • the customer may be defined using one or more characteristics or attributes of the customer, such as geographic area where the customer resides, types of networking services being requested, type of network request (e.g., private or public network access, or sub-network access), type of customer devices requesting access, or other demographic or network information.
  • Process 300 proceeds to block 312, where a region or group of API end points is selected based on the customer.
  • the specific customer identifier may be used to select the group of API end points.
  • characteristics of the customer may be used to select the group. For example, different groups may be associated with different metropolitan areas, and the group associated with the metropolitan area of the customer may be selected. This example is not to be limiting and other customer characteristics may be used to select a group of API end points from the plurality of groups of API end points.
  • a network service is identified for the order.
  • the order may itself identify the networking service.
  • the networking service may be a specific network function, such as data management, voice management, messaging management, etc.
  • the networking service may be associated with networking or device testing. For example, if the customer device is Model_A for Manufacturers, then the networking service may be testing various aspects of how that device operates in the network.
  • Process 300 proceeds next to block 316, where an API end point associated with the identified service is selected.
  • a configuration file may be used to indicate which networking services are associated with or map to which API end points.
  • Process 300 continues next at block 318, where the selected API end point is employed to provision a cloud-computing core for the identified service.
  • the selected API end point is used to call the cloud-computing infrastructure and request that a cloud-computing core be established to perform the functionality of the associated identified networking service.
  • a configuration file may be used to map the API end points to the provisioning of cloud-computing cores to perform the networking service functionality.
  • process 300 proceeds to decision block 320, where a determination is made whether another service is identified for the order.
  • the order may include a plurality of different networking services.
  • the group of API end points may include a plurality of API end points that are associated with a plurality of networking services. If another networking service is to be selected or identified for the order, then process 300 loops to block 314, where another networking service is identified and a corresponding API end point is selected and employed to provision a cloud-computing core for that networking service for the order. Accordingly, a separate cloud-computing core is provisioned for each separate networking service for the order. If another networking service is not selected or identified for the order, then process 300 flows to decision block 322.
  • process 300 loops to block 308 to process the other order and provision separate cloud-computing cores for each networking service associated with that other order; otherwise, process 300 terminates or returns to a calling process to perform other actions.
  • System 400 includes a network-service-management computing device 102 and a cloud computing environment 104.
  • the cloud computing environment 104 includes computing components and resources that can be utilizes as cloud-computing cores in a virtual computing environment
  • the network-service-management computing device 102 initializes the provisioning of multiple cloud-computing cores for separate networking services for customer devices, as described herein.
  • One or more special-purpose computing systems may be used to implement network- service-management computing device 102. Accordingly, various embodiments described herein may be implemented in software, hardware, firmware, or in some combination thereof.
  • the network-service-management computing device 102 may include memory 402, one or more central processing units (CPUs) 414, I/O interfaces 418, other computer-readable media 420, and network connections 422.
  • Memory 402 may include one or more various types of nonvolatile and/or volatile storage technologies.
  • Examples of memory 402 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 402 may be utilized to store information, including computer-readable instructions that are utilized by CPU 414 to perform actions, including embodiments described herein.
  • Memory 402 may have stored thereon cloud-core-provisioning module 204 and order-management module 206.
  • the cloud-core-provisioning module 204 is configured to utilize API end points to call on the cloud computing environment 104 to provision separate cloud-computing cores for separate networking services and to manage the use of those cores, as described herein.
  • the order-management module 206 is configured to manage the receipt of orders for new wireless services and to coordinate the provisioning of the cloud-computing cores for those services with the cloud- core-provisioning module 204, as described herein.
  • Memory 402 may also store other programs and data 410.
  • Network connections 422 are configured to communicate with other computing devices, such as the cloud computing environment 102, to facilitate the provisioning of cloud-computing cores in the cloud computing environment 104.
  • the network connections 422 include transmitters and receivers (not illustrated) to send and receive data as described herein.
  • I/O interfaces 418 may include a video interfaces, other data input or output interfaces, or the like.
  • Other computer-readable media 420 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 systèmes et un procédé selon l'invention concernent la fourniture de multiples cœurs en nuage pour de nouveaux services sans fil. Un ordre pour le nouveau service sans fil pour un dispositif client est reçu et un identifiant de client associé à l'ordre est déterminé. Un premier service et un second service sont identifiés pour l'ordre sur la base de l'identifiant de client. Le premier service est différent du second service. Un premier cœur en nuage est fourni pour le premier service. Et un second cœur en nuage est fourni pour le second service. Le second cœur en nuage s'exécute séparément du premier cœur en nuage.
PCT/US2023/018356 2022-04-14 2023-04-12 Fourniture de réseau à de multiples cœurs WO2023200881A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202263331084P 2022-04-14 2022-04-14
US63/331,084 2022-04-14
US17/887,722 US20230336954A1 (en) 2022-04-14 2022-08-15 Network provisioning to multiple cores
US17/887,722 2022-08-15

Publications (1)

Publication Number Publication Date
WO2023200881A1 true WO2023200881A1 (fr) 2023-10-19

Family

ID=86329161

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/018356 WO2023200881A1 (fr) 2022-04-14 2023-04-12 Fourniture de réseau à de multiples cœurs

Country Status (1)

Country Link
WO (1) WO2023200881A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150326448A1 (en) * 2014-05-07 2015-11-12 Verizon Patent And Licensing Inc. Network-as-a-service product director
US20200244551A1 (en) * 2019-01-24 2020-07-30 Vmware, Inc. Dynamic inter-cloud placement of virtual network functions for a slice
US20210051070A1 (en) * 2019-08-15 2021-02-18 Netsia, Inc. Apparatus and method for a unified slice manager
WO2021181408A1 (fr) * 2020-03-07 2021-09-16 Sterlite Technologies Limited Système et procédé de création dynamique de tranches de réseau de bout en bout

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150326448A1 (en) * 2014-05-07 2015-11-12 Verizon Patent And Licensing Inc. Network-as-a-service product director
US20200244551A1 (en) * 2019-01-24 2020-07-30 Vmware, Inc. Dynamic inter-cloud placement of virtual network functions for a slice
US20210051070A1 (en) * 2019-08-15 2021-02-18 Netsia, Inc. Apparatus and method for a unified slice manager
WO2021181408A1 (fr) * 2020-03-07 2021-09-16 Sterlite Technologies Limited Système et procédé de création dynamique de tranches de réseau de bout en bout

Similar Documents

Publication Publication Date Title
US11432366B2 (en) Session management method, device, and system
CN109429295B (zh) 一种选择amf的方法、amf、系统及存储介质
US12004264B2 (en) Session management method, device, and system
EP3457733B1 (fr) Orchestrateur mobile edge et système de migration d'application
KR20180134685A (ko) 통신 시스템에서 PDU(Protocol Data Unit) 세션을 설립하는 방법
US20240349265A1 (en) Communication method and apparatus
US11528593B2 (en) Network slicing using dedicated network node
US12096218B2 (en) Security for network slicing in a communication system
US11490322B2 (en) Provisioning of network slicing in a communication system
US20230336441A1 (en) Flexible model to provision wireless communication services directly to network function or network support system
KR20160036947A (ko) 기지국장치 및 기지국장치의 동작 방법
CN112398675B (zh) 网元分配方法及装置
WO2023059821A1 (fr) Transfert sélectif de dispositif cellulaire sur la base d'un découpage de réseau
US20220141762A1 (en) Network slice selection in a wireless telecommunications network
CN107426109B (zh) 一种流量调度方法、vnf模块及流量调度服务器
US20230336954A1 (en) Network provisioning to multiple cores
WO2023200881A1 (fr) Fourniture de réseau à de multiples cœurs
WO2023200883A1 (fr) Modèle flexible pour fournir des services de communication sans fil directement à une fonction de réseau ou à un système de support de réseau
US20230189311A1 (en) Data transmission method, network device and system in multi-connectivity network
CN113886072A (zh) 负载均衡系统、方法及设备
CN117121560A (zh) 动态网络切片管理
CN102550056B (zh) 一种策略控制的方法、设备及系统
CN108141761B (zh) 无线资源确定方法、装置及业务服务器
WO2020006651A1 (fr) Procédé et dispositif d'attribution de services
CN114189920B (zh) 网络切片的载波隔离方法、装置、设备和介质

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: 23722159

Country of ref document: EP

Kind code of ref document: A1