WO2023091425A1 - Procédé et appareil permettant de créer et d'utiliser des microtranches dans un réseau de communication sans fil d'entreprise - Google Patents

Procédé et appareil permettant de créer et d'utiliser des microtranches dans un réseau de communication sans fil d'entreprise Download PDF

Info

Publication number
WO2023091425A1
WO2023091425A1 PCT/US2022/049984 US2022049984W WO2023091425A1 WO 2023091425 A1 WO2023091425 A1 WO 2023091425A1 US 2022049984 W US2022049984 W US 2022049984W WO 2023091425 A1 WO2023091425 A1 WO 2023091425A1
Authority
WO
WIPO (PCT)
Prior art keywords
microslice
network
instance
instances
enterprise
Prior art date
Application number
PCT/US2022/049984
Other languages
English (en)
Inventor
Mehmet Yavuz
Keshav Sai Srinivas Nanduri
Andrew Von Nagy
Vinay Anneboina
Rajeev Shah
Srinivasan Balasubramanian
Original Assignee
Celona, Inc.
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/687,546 external-priority patent/US20220255798A1/en
Priority claimed from US17/979,266 external-priority patent/US20230121880A1/en
Application filed by Celona, Inc. filed Critical Celona, Inc.
Publication of WO2023091425A1 publication Critical patent/WO2023091425A1/fr

Links

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/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/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the disclosed method and apparatus relate generally to wireless communication networks and more particularly to methods and apparatus for slicing the network to allow network administrators and businesses and other enterprises to more closely tailor network access with communication needs, and provide a way to use network resources more efficiently.
  • FIG. 1 is an illustration of a basic configuration for a communication network, such as a “4G LTE” (fourth generation Long-Term Evolution) or “5G NR” (fifth generation New Radio) network.
  • a communication network such as a “4G LTE” (fourth generation Long-Term Evolution) or “5G NR” (fifth generation New Radio) network.
  • UE user equipment
  • PDNs External Packet Data Networks
  • the UEs 101a and 101b connect wirelessly over respective communication links 105a and 105b to a Radio Access Network (RAN) 107 that includes a base station/access point (BS/AP) 109.
  • RAN Radio Access Network
  • BS/AP base station/access point
  • One of the advantages of such networks is their ability to provide communications to and from multiple wireless devices and provide these wireless devices with access to a large number of other devices and services even though the devices may be mobile and moving from location to location.
  • the term “UE’ refers to a wide range of user_devices having wireless connectivity, such as a cellular mobile phone, an Internet of Things (IOT) device, virtual reality goggles, robotic devices, autonomous driving machines, smart barcode scanners, and communications equipment including for example cell phones, desktop computers, laptop computers, tablets and other types of personal communications devices.
  • the UEs may be mobile; in other cases, they may be installed at a fixed location.
  • a factory sensor may be installed at a fixed location from which it can remotely monitor an assembly line or a robotic arm’s movement.
  • BS/AP is used broadly herein to include base stations and access points, including at least an evolved NodeB (eNB) of an LTE network or gNodeB of a 5G network, a cellular base station (BS), a Citizens Broadband Radio Service Device (CBSD) (which e.g. may be an LTE or 5G device), a WiFi access node, a Local Area Network (LAN) access point, a Wide Area Network (WAN) access point, and should also be understood to include other network receiving hubs that provide access to a network of a plurality of wireless transceivers within range of the BS/AP.
  • eNB evolved NodeB
  • CBSD Citizens Broadband Radio Service Device
  • WiFi Wireless Fidelity
  • LAN Local Area Network
  • WAN Wide Area Network
  • the BS/APs are used as transceiver hubs, whereas the UEs are used for point-to-point communication and are not used as hubs. Therefore, the BS/APs transmit at a relatively higher power than the UEs.
  • the RAN 107 connects the UEs 101 with the Core Network 111.
  • One function of the Core Network 111 is to provide control of wireless signaling between the UEs 101 and the RAN 107.
  • Another function of the Core Network 111 is to provide access to other devices and services either within its network, or on other networks such as the External PDNs 103.
  • the BS/AP 109 can receive wireless signals from, and send wireless signals to, the UEs 101.
  • the RAN 107 is coupled to the core network 111; therefore, the RAN 107 and the Core Network 111 provide a system that allows information to flow between a UE in the cellular or private network and other networks, such as the Public Switched Telephone Network (PSTN) or the Internet.
  • PSTN Public Switched Telephone Network
  • Wireless data transmission between a UE 101 and the BS/AP 109 occurs on an assigned channel, such as a specific frequency.
  • Data transmission between the BS/AP 109 and the Core Network 111 utilizes any appropriate communication means, such as wireless, cable, and fiber optic.
  • the Core Network 111 In addition to providing access to remote networks and allowing information to flow between the cellular network and the external PDNs 103, the Core Network 111 provides control of the air interface between the BS/AP 119 and the UEs 101. The Core Network 111 may also coordinate the BS/APs 109 to minimize interference within the network.
  • LTE Long Term Evolution
  • 5G NR 5G NR
  • network slicing was introduced for LTE/5G networks.
  • network slicing is a network architecture that enables the multiplexing of virtualized and independent logical networks on the same physical network infrastructure. Each network slice is an isolated end-to-end network tailored to fulfil diverse requirements requested by a particular application.
  • the GSM Association (GSMA) is a telecommunications industry group involved in 5G.
  • the technology that enables network slicing is transparent to business customers for whom LTE/5G networks, and in combination with network slicing, allows connectivity and data processing tailored to specific business requirements.
  • the customizable network capabilities include data speed, quality, latency, reliability, security, and services. These capabilities may be provided based on a Service Level Agreement (SLA) between the mobile operator and the business customer.
  • SLA Service Level Agreement
  • a network slice may span across multiple parts of the network (e.g., access network, core network and transport network) and could be deployed across multiple operators.
  • a network slice may utilize dedicated and/or shared resources, (e.g., in terms of processing power, storage, and bandwidth), and each network slice is effectively isolated from the other network slices.
  • a network slice is a logical network that provides specific network capabilities and network characteristics in order to serve a defined business purpose of a customer.
  • Network slicing allows multiple virtual networks to be created on top of a common shared physical infrastructure.
  • a network slice consists of different subnets, example: Radio Access Network (RAN) subnet, Core Network (CN) subnet, Transport network subnet.
  • RAN Radio Access Network
  • CN Core Network
  • Transport network subnet Transport network subnet
  • a Network Slicing Provider is typically a telecommunication service provider who is the owner or tenant of the network infrastructures from which network slices are created.
  • the Network Slicing provider takes the responsibilities of managing and orchestrating corresponding resources that the Network Slicing consists of.
  • a Business Customer tenants the network slice, e.g., customers from vertical industries. For instance, business customers could be enterprise or specialized industry customers (often referred to as “verticals”).
  • SDO Standards Developing Organizations
  • RAN Radio Access Network
  • CN Core Network
  • TN Transport Network
  • BBF BBF
  • IETF IETF
  • ITUT GSTR TN5G
  • IEEE NGFI 1914
  • MEF MEF and other SDOs are working on this topic as well.
  • the 3GPP (3 rd Generation Partnership Project) TS 23.501 Release 16, vl6.2.0 (2019-09) specification includes particular aspects of network slicing. Details are specified in 3GPP 23.501 section 5.15.
  • the UE device may provide Network Slice Selection Assistance Information (NSSAI) parameters to the network to help the network select a RAN and a Core Network part of a Network Slice Instance (NSI) for the device.
  • NSSAI Network Slice Selection Assistance Information
  • a single NSSAI may lead to the selection of several slices.
  • the network may also use device capabilities, subscription information and local operator policies to do the selection.
  • Network slices may differ for supported features and network functions optimizations, in which case such Network Slices may have e.g., different S-NSSAIs with different Slice/Service Types (SSTs) (see 3GPP TS 23.501 section 5.15.2.1).
  • SSTs Slice/Service Types
  • the operator can deploy multiple network slices delivering exactly the same features but for different groups of UEs, e.g., as they deliver a different committed service and/or because they are dedicated to a customer, in which case such Network Slices may have e.g., different S- NSSAIs with the same Slice/Service Type but different Slice Differentiators (see TS 23.501 section 5.15.2.1).
  • the network may serve a single UE with one or more Network Slice instances simultaneously via a 5G Access Network (5G-AN) regardless of the access type(s) over which the UE is registered (e.g., 3GPP Access and/or Non-3Gpp (N3GPP Access).
  • the Access and Mobility management Function (AMF) instance serving the UE logically belongs to each of the network slice instances serving the UE, i.e., this AMF instance is common to the Network Slice instances serving a UE.
  • microslices described herein can provide an end-to-end logical network through multiple networks that can be flexibly created and managed by IT professionals.
  • the microslices can be monitored and dynamically adjusted to ensure that certain Quality of Service (QoS) and Service Level Objective (SLO) requirements are met for different service types or applications.
  • QoS Quality of Service
  • SLO Service Level Objective
  • microslicing as described herein take a more granular approach to network slicing for enterprise LTE/5G deployments than the standard-based network slicing approach, which allows greater customization of services, faster updates, and simplifies administration, and provides users and the enterprise with more efficient use of bandwidth and better service for the UEs; generally the microslices and methods described herein provide a more efficient wireless network for enterprises.
  • the network administrator can specify one or more applications, devices, and/or users that are allowed to use one or more microslices.
  • the device may be associated with a device group, and the microslice profile may be selected and/or set-up responsive to device group associated with the device.
  • the network administrator may define one or more groups of UEs; and associate one or more microslices to each of those groups.
  • the network administrator may also define a plurality of service types, and associate one or more microslices to those service types.
  • a method for implementing a microslice includes receiving device information, microslice profiles and resource availability information from the enterprise network, responsive to the device information and microslice profiles, selecting a microslice profile, responsive to the selected microslice profile and the resource availability information, determining a network configuration that defines a microslice instance, including defining functional blocks and communication links between the functional blocks in the enterprise network, and responsive to the network configuration, setting up and managing the functional blocks and the communication links between the functional blocks, to implement the microslice instance for the wireless device.
  • Resources may be allocated to the microslice configuration in a Network Resource Allocation Module responsive to the resource availability information provided by the enterprise network.
  • a microslice orchestration module for implementing a microslice that provides a communication path for a wireless device connected to a network, including a receiving unit for receiving device information, microslice profiles and resource availability information, a microslice orchestrating unit for determining a network configuration that defines a microslice instance responsive to the device information, microslice profiles and the resource availability information, the network configuration of the microslice instance defining functional blocks and communication links between the functional blocks, and a configuration control unit for setting up and controlling the functional blocks and the communication links between the functional blocks responsive to the network configuration, to implement the microslice instance for the wireless device.
  • a method of monitoring and managing data flows in an enterprise wireless communication network includes a plurality of UEs wirelessly connected with a RAN and a Core Network.
  • a plurality of microslice instances are created that define data flows, each microslice instance including a plurality of network components that span a plurality of functional blocks and communication nodes.
  • Each microslice instance has at least one associated Service Level Objective (SLO), which provides performance objectives for the microslices.
  • SLO Service Level Objective
  • Each of the microslice instances is monitored, which includes measuring at least one Key Performance Indicator (KPI) of each microslice instance.
  • KPI Key Performance Indicator
  • the KPIs may be measured end-to-end across the microslice instance, at a communication node of the microslice instance, and at a functional block of the microslice instance.
  • the measured KPIs are compared with the SLOs for the associated microslice instances, and if the SLOs have been met for the microslice instances, then monitoring continues.
  • the KPIs may be measured as end-to-end performance apart from monitoring the performance within the network components directly managed by the microslice.
  • At least one microslice instance may be dynamically adjusted by for example reconfiguring.
  • the QoS settings may be adjusted.
  • the reconfigured microslice instance is monitored, and reconfiguration may be repeated to dynamically adjust the microslice until the SLOs for the adjusted microslice instance have been met.
  • the microslice configuration may be reconfigured responsive to the KPIs and the microslice profile.
  • the microslice instances can be dynamically adjusted responsive the revised microslice configurations, so that communication is not significantly interrupted.
  • the microslice instance may be modified for all UEs, in other embodiment the microslice instance may be modified for a finite subset of users I user groups that use that microslice instance.
  • Reconfiguration and dynamically adjusting the microslice instances may be performed in a microslice orchestration module connected to the enterprise network.
  • the microslice instance may be configured to include a functional block in an external network; in some embodiments the microslice instance may include a functional block in at least one of a VLAN and a VxLAN, which may be reconfigured.
  • the enterprise network is configured as a CBRS network, the RAN includes CBSDs, and the microslice instances communicate to the Core Network through the CBSDs.
  • a method of managing and controlling network load includes monitoring the microslice instances, including measuring at least one KPI at a communication node of each microslice instance, comparing the measured KPIs with the SLOs for the associated microslice instances, and determining a network load including a load for network components. If the network load exceeds a performance threshold, then the priority of the microslice instances is evaluated. At least one of the following is performed:
  • the lower priority microslice instances are dynamically adjusted, which may include reconfiguring the microslices instance, monitoring the network load, and repeating until the load meets the performance threshold.
  • a load control apparatus for managing and controlling network load in a wireless communication network includes a microslice orchestration module for creating the microslice instances that define data paths for the UEs.
  • a monitoring unit is provided for monitoring each of the plurality of microslice instances, including measuring at least one KPI at a communication node of each microslice instance.
  • a load control unit is provided that receives the measured KPIs and compares them with the SLOs for the associated microslice instances, determines network load including a load for network components responsive thereto, and determines if the network load exceeds a performance threshold responsive to the SLOs.
  • a performance management unit evaluates priority of the microslice instances, and performs at least one of the following: 1) drops lowest priority microslices until the load meets the performance threshold, 2) dynamically adjusts the lower priority microslice instances until the network load meets the performance threshold.
  • the microslice orchestration module may be part of a cloud-based network orchestration module that is remotely located from the enterprise network.
  • the microslice orchestration module may include a configuration control unit for reconfiguring microslice instances.
  • the enterprise network is configured as a CBRS network
  • the RAN includes CBSDs
  • the microslice orchestration module creates microslice instances to communicate through the CBRS network.
  • FIG. 1 is an illustration of a basic configuration for a communication network, such as a “4G LTE” (fourth generation Long-Term Evolution) or “5G NR” (fifth generation New Radio) network.
  • 4G LTE fourth generation Long-Term Evolution
  • 5G NR fifth generation New Radio
  • FIG. 2A is a block diagram illustrating microslice instances across multiple networks including a wireless network.
  • FIG. 2B is a block diagram illustrating microslice instances across multiple networks, including a wireless network, a LAN, and an external WAN.
  • FIG. 3A is a high-level flow chart of a method for defining microslice profiles, selecting a profile for a communication, setting up the microslice instance, and managing and monitoring the microslice instance.
  • FIG. 3B is a flow chart of operations to define a microslice profile.
  • FIG. 3C is a flow chart of operations to select a microslice profile for a communication session with a UE.
  • FIG. 3D is a flow chart that shows the inputs and operations to set up a microslice instance.
  • FIG. 3E is a flow chart of operations to manage and monitor microslices during operation.
  • FIG. 4 is a table showing an example microslice profile.
  • FIG. 5 is a table showing an example of allowed application definitions for a microslice.
  • FIG. 6 is a flow chart of a method for assigning a microslice to devices.
  • FIG. 7 is a table showing an example of a device group definition.
  • FIG. 8 is a table showing an example of microslice assignments to device groups.
  • FIG. 9 is a block diagram of a 4G wireless communication network.
  • FIG. 10 is a block diagram of a 5G wireless communication network.
  • FIG. 11 is a table showing an example of service types that can be associated with microslice profiles.
  • FIG. 12 is a flow chart of operations to provide load control in a system utilizing microslices.
  • FIG. 13 is a flow chart of operations to provide admission control in a system utilizing microslices.
  • FIG. 14 is a flow chart of alarm operations that may be triggered under some circumstances, also showing a control procedure that may be run in response to triggering an alarm.
  • FIG. 15 is a block diagram of an implementation of an enterprise network including a cloud-based orchestration module.
  • FIG. 16 is a block diagram of a wireless communication system including an enterprise network and a microslice orchestration module, illustrating microslices implemented in the enterprise network.
  • FIG. 17 is a block diagram of a wireless communication system including an enterprise network and a microslice orchestration module, illustrating microslices implemented across the enterprise network and external networks.
  • a functional block is a computing element that performs any activity required to implement a set of logical operations.
  • the functional block may include a dedicated processing circuit that performs an intended function, or it may be a software- implemented process across circuits that performs the intended function.
  • the functional blocks may reside inside or outside an enterprise network, and the functional block may include a LAN, a VLAN or a VxLAN or another network or network element, and it may reside in an internal network, or an external network.
  • the activity required to implement a set of logical operations is performed for the purpose of facilitating end-to-end communication (e.g., between a UE and an external server).
  • the functional block may be in the control plane or the user plane.
  • control information is exchanged between the block and the orchestrator. For example, the orchestrator may make a query, and the functional block may respond.
  • a communication link is a connection between two functional blocks that provides communication between the two functional blocks.
  • the communication link may include any appropriate connection type, such as wireless or wired, and utilize any suitable protocol.
  • the link and/or protocol may be secure or otherwise.
  • a communication link may be monitored at any point in the link, for example it may be monitored at its entry point and/or its exit point to provide performance data.
  • Communication networks and system components are described herein using terminology and components common to 4G (LTE) communication systems, and/or 5G NR communication systems. However, the principles of the communication network and microslices described herein more widely apply to other communication systems, not only to 4G or 5G systems.
  • An enterprise network is one type of private network. Private networks are operated for use within a limited area by a limited group of authorized users, whereas public networks generally cover a larger area and are open for use by anyone that subscribes to the service by the network operator.
  • An enterprise network is created at an enterprise location such as a warehouse, factory, research center or other building, and is usually operated by an organization for its own use. Other types of private networks may be operated by a private network manager for use by more than one organization.
  • FIG. 2A is a block diagram illustrating microslice instances in a wireless network 200.
  • a mobile phone UE 201a is connected via a wireless link 205 a to a RAN 207, which is connected to a Core Network 211.
  • a vehicle 201b is connected via a wireless link 205b to the RAN 207.
  • the mobile phone UE 201a may have a need for voice communication.
  • the vehicle 201b may need a highly reliable link for navigation, and another for data communication. To address these needs, microslices are described herein.
  • a microslice instance provides a path for data flow to and from a device.
  • a device may be a UE or other device such as an Access Point (AP), a router, or other component in the communication network.
  • AP Access Point
  • the microslice’s data flow will travel end-to-end (i.e., from the UE to the edge of the external PDN), the data flow may travel through all or parts of the RAN, Core Network, and service platforms.
  • a microslice instance typically spans multiple functional blocks, and multiple communication nodes.
  • a microslice instance is set up using a microslice profile, described herein.
  • a microslice profile can be defined in any of a number of ways; for example, in some embodiments, a microslice profile may be defined to meet requirements of a service type, in other embodiments, a microslice may be associated with a user application, for example YouTube or Netflix, or a group of similar applications.
  • microslice profiles can be defined by a network administrator operating one or more networks in an enterprise location, and the microslice profiles can then be applied to communications within the enterprise location’s networks.
  • each microslice is instantiated (i.e., established within a “microslice instance”) in a manner that forms a complete logical network.
  • a logical network is a virtual representation of a network that appears to the user as an entirely separate and self-contained network even though it might physically be only a portion of a larger network or a local area network.
  • a first microslice instance 221 is shown from the mobile phone UE 201a through the RAN 207 and to the Core Network 211.
  • a second microslice instance 222 and a third microslice instance 223 are provided from the vehicle 201b through the RAN 207 and to the Core Network 211.
  • An instance may also be established between other components of the communication network, such as in parts of the RAN and/or the Core Network, or between other components of the communication network. For example, an instance may be established between the UE 201a and the RAN 207, between the vehicle 201b and the RAN 207, or between the RAN 207 and the Core Network 211, or along any communication link that may be available.
  • Each microslice instance 221, 222, 223 is implemented using a set of functional blocks and communication links in the RAN 207, Core Network 211, or any other network or component that communicates with the enterprise network, such as other servers, WANs, LANs, and VLANs.
  • a Core Network is an Evolved Packet Core (EPC) in an LTE/5G network.
  • EPC Evolved Packet Core
  • the LTE/5G network may be part of an enterprise IT network, or other network.
  • FIG. 2A shows the microslice instances 221, 222, and 223 implemented across the UE 201a, the vehicle 201b, RAN 207, and Core Network 211.
  • Microslices can be implemented across multiple networks, for example, as LTE/5G networks are deployed in enterprises, the newly-deployed networks need to be integrated into Local Area Networks (LANs), and Wide Area Networks (WANs), and microslices can be utilized for this purpose.
  • LANs Local Area Networks
  • WANs Wide Area Networks
  • the microslice architecture enables customizable network capabilities and the ability to select QoS parameters for different service types.
  • each of several service types can be associated with a unique microslice profile that has a defined data throughput, quality, packet error rate (PER), packet latency, reliability, isolation and set of security services.
  • PER packet error rate
  • FIG. 2B is a block diagram illustrating microslice instances across additional networks, including a Local Area LAN 231 and a WAN 232.
  • the plurality of UEs 201a and 201c are wirelessly connected to the RAN 207.
  • the LAN 231 connects the RAN 207 with the Core Network 211.
  • the WAN 232 is connected to the Core Network 211, and connects to a wide variety of external PDNs 103 and other services.
  • These LANs and WANs may be external PDNs outside the Core Network 211, or may be internal.
  • firewalls e.g., next-gen firewalls
  • These firewalls would also be outside the Core Network 211.
  • the microslice instances extend from the UE, through the networks, and into the WAN 232.
  • a first microslice instance 241 extends from the UE (mobile phone) 201a, through the RAN 207, LAN 231, Core Network 211, and extend into the WAN 232.
  • the QoS parameters of each the microslices can be extended to these LANs, WANs, and firewalls through standard mechanisms such as QoS markings and DiffServ differentiated services code point (DSCP).
  • second and third microslices 242 and 243 extend from the auto UE 201b, through the RAN 207, LAN 231, Core Network 211, and extend into the WAN 232.
  • This provides the ability to integrate a microslice with the “remaining” network components via tagging flows to enable end-to-end QoS.
  • DSCP markings for certain IP flows used by LAN switches, SDWAN routers and backhaul can be extended and combined with microslices.
  • IP flows with specific DHCP markings can be assigned to a specific microslice.
  • an enterprise network 250 shown within a block with dashed lines, includes the UEs 201, the RAN 207, LAN 231, and Core Network 211. Typically, these will be at a common location, such as a building or other defined area, however some components may be outside the defined area.
  • a network administrator 252 may, with appropriate security, remotely administer the enterprise network 250 via the WAN and set up microslices. Alternatively, the network administrator 252 may connect directly to the enterprise network, to administer the networks and set up microslices.
  • microslice profiles can be defined using any of a number of parameters associated with the microslice, for example service type, user application, and groups of applications. These parameters may, for example be stored in a Home Subscription Server (HSS) in a 4G system (FIG. 9), or a User Data Management (UDM) in a 5G system (FIG. 10).
  • HSS Home Subscription Server
  • UDM User Data Management
  • a microslice profile may include a series of parameter levels, each level designated by an index “k”; i.e., each microslice index “k” (MSk) may be associated with a particular level of QoS parameters such as one QoS Class Indicator (QCI) value, a Guaranteed Bit Rate (GBR) value, a Maximum Bit Rate (MBR) value, and an Allocation and Retention Priority (ARP) value.
  • QCI QoS Class Indicator
  • GRR Guaranteed Bit Rate
  • MRR Maximum Bit Rate
  • ARP Allocation and Retention Priority
  • FIGs. 3A-3E are flow charts that disclose methods to define and utilize microslices. Particularly, FIG. 3A discloses a general method to define, select, set-up and operate microslices.
  • FIG. 3B discloses a method to define microslice profiles.
  • FIG. 3C discloses a method to select a microslice profile responsive to a communication request.
  • FIG. 3D discloses a method to set up a microslice for a particular communication.
  • FIG. 3E discloses a method to manage and monitor the microslice after it has been set-up.
  • FIG. 3A is a high-level flow chart that summarizes operations to define, set-up and operate microslices (STEP 300).
  • microslices are defined (e.g., by a network administrator) utilizing a plurality of inputs such as the Service Level Agreements (SLAs) 312, Service Types 342, Applications and App Groups 344, and Users/UEs and User Groups 346. Responsive to any one or more of these inputs, one or more microslice profiles 304 are defined for use in the network.
  • Service Level Objectives (SLOs) 306 may be defined, which may be used to monitor a microslice instance operating in the network. Microslice profiles 304 and SLOs 306 are discussed in more detail elsewhere herein, for example with reference to FIG. 3B.
  • the available microslice profiles 304 are compared with the communication request 308, and a microslice profile appropriate for the communication is selected (STEP 310), responsive to information provided by the device or other available information such as a device group 348 to which the device belongs, and other information that may be provided by the network. Selecting the microslice profile (STEP 310) is described in more detail elsewhere herein, for example with reference to FIG. 3C.
  • the selected microslice profile 314 is then supplied to the network or appropriate functional unit, which sets up the microslice instance (STEP 316) using available network resources to provide an instance configuration 317 in the network.
  • Information regarding the device group 348 to which the device belongs may also be used to set up the instance, for example the device group information may indicate a particular network (e.g., VxLAN) for the device. Setting up the microslice instance (STEP 316) is described in more detail elsewhere herein, for example with reference to FIG. 3D.
  • the microslice instance configuration 317 can then be utilized for communication by the UE (STEP 318).
  • the network manages, and monitors the microslice instance during operation. Operating, managing, and monitoring the microslice is described in more detail elsewhere herein, for example with reference to FIG. 3E. Operation ends (STEP 319) when the communication is no longer desired, and then the microslice configuration can be dismantled.
  • FIG. 3B is a flow chart of operations to define a microslice profile.
  • a microslice profile can be defined in many different ways to meet the purpose of outlining a communication path and QoS requirements for the communication path.
  • a microslice profile defines the parameters of data flows to ensure that certain Quality of Service (QoS) requirements and Service Level Objectives (SLOs) are met, and can also define the path of data flows to some extent.
  • microslice profiles can be utilized to quickly and efficiently set up a microslice instance, which is a communication link with a wireless UE, that meets service requirements for the UE, allow the network to utilize its resources more efficiently, simplify network administration, and enhance services provided by the network.
  • microslice profiles 304 can be defined using any of a number of communication aspects associated with the microslice, for example service type, user application, and groups of applications.
  • a microslice profile is defined by parameters that reside within fields in a microslice profile database.
  • the parameters may, for example, include name, user applications, minimum guaranteed throughput, maximum allowed throughput, maximum packet delay bound, maximum packet loss rate and priority. These parameters may, for example be stored in a Home Subscription Server (HSS) in a 4G system (FIG. 9), or a User Data Management (UDM) in a 5G system (FIG. 10).
  • HSS Home Subscription Server
  • UDM User Data Management
  • a microslice profile may include a series of parameter levels, each level designated by an index “k”; i.e., each microslice index “k” (MSk) may be associated with a particular level of QoS parameters such as one QoS Class Indicator (QCI) value, a Guaranteed Bit Rate (GBR) value, a Maximum Bit Rate (MBR) value, and an Allocation and Retention Priority (ARP) value.
  • QCI QoS Class Indicator
  • GRR Guaranteed Bit Rate
  • MRR Maximum Bit Rate
  • ARP Allocation and Retention Priority
  • a number of inputs may be used together to create and define (STEP 302) the parameters of the microslice profiles 304.
  • One of more of these inputs may be provided to define the microslices (STEP 302).
  • These inputs may include SLOs 324, QoS parameters 328, Service Types 342, App Groups 344, User Groups 346, and Device Groups 348.
  • Service Level Objectives (SLOs) 324 are defined (STEP 322) for each microslice. SLOs 324 may be derived responsive to Service Level Agreements (SLAs) 312 of providers, QoS parameters 328, and other values, and provide different levels of service for the device.
  • SLAs Service Level Agreements
  • SLOs may be defined (STEP 326) by the administrator, device requirements, or other sources. Generally, the SLOs for each microslice are utilized to monitor a microslice instance, and provide a means for evaluating the performance of the services running over a microslice instance. The performance defined by the SLOs may be tracked across the microslice instance; particularly, performance may be monitored at multiple network locations along the microslice instance, e.g., at multiple functional blocks and multiple communication nodes.
  • FIG. 11 is a table 1100 of examples of service types.
  • Service types 342 are defined (STEP 332) depending upon the services 331 that the network is expected to provide for the UE.
  • the profile parameters of the microslices may be selected together (in STEP 302) to ensure certain Quality of Service (QoS) requirements and Service Level Objectives (SLOs) are met for different service types or applications such as:
  • QoS Quality of Service
  • SLOs Service Level Objectives
  • VT video telephone
  • teleconferencing e.g., zoom, Skype for business
  • a microslice profile may include a service type.
  • a Service Type may refer to communication for specific activities (e.g., videoconferencing, internet download, voice calls, music, loT, Industrial loT (IIoT), etc.) or more general activities.
  • the Service Type may be specifically defined a number of ways, for example it may be defined by a 5-tuple (server IP address, destination IP address, port number, transport protocol, DSCP/TOS marking).
  • QoS Quality of Service
  • Another input to define a microslice profile may be an application group.
  • Application groups 344 are defined (STEP 334) depending upon the services 333 that the network is expected to provide for the UE.
  • the microslice profile may also be associated with one or more applications, or it may be associated with one or more groups of applications, and they may be specified as part of the profile.
  • Al may be utilized to automatically classify application into groups and/or microslices.
  • Al option and other automated techniques to associate applications with microslices and/or applications can provide automated classification of applications into groups and automatic association with a microslice, providing greater efficiency and avoiding manual interaction. For example, when a new application like Disney+ arrives, it can automatically get assigned to a Streaming Microslice, together with other streaming apps like YouTube, NetFlix, Amazon Prime, etc.
  • Another input to define a microslice profile may be the user or user group.
  • User groups 346 are defined (STEP 336) depending upon the user 335 that the network is expected to provide for the users. User groups may be set up by the network administrator, for ease of administration, or to provide preferred service to a particular group.
  • the microslice profile may be associated with one or more users, or it may be associated with one or more groups of users, and the users or user groups may be specified as part of the profile.
  • Another input to define a microslice profile 304 may be device groups.
  • Device groups 348 are defined (STEP 334) depending upon the user 333 that the network is expected to provide for the UE. Device groups may be set up by the network administrator, for ease of administration, or to provide preferred service to a particular group of devices.
  • the microslice profile may be associated with one or more devices, or it may be associated with one or more groups of devices, and the devices or device groups may be specified as part of the profile.
  • Devices groups 348 are particularly useful for enterprise networks, and are described elsewhere in more detail.
  • FIG. 4 is an example of a microslice profile 400.
  • the microslice is defined by parameters that reside within fields. The parameters may, for example, include name, allowed application definitions, minimum guaranteed throughput, maximum allowed throughput, maximum packet delay bound, maximum packet loss rate and priority.
  • FIG. 3C is a flow chart of operations to select a microslice profile (STEP 310, FIG. 3A) for a communication session with a UE.
  • the wireless network is monitored (STEP 360) to detect a request 362 for communication, and when a communication is detected (STEP 364), then information from the request 362 or other available information may be utilized to identify (STEP 366) data and other information relating to the communication, such as the user, application, service type, and UE (device). Utilizing this information and other information, a microslice is selected (STEP 370) from the microslice profiles 304 to provide a selected microslice profile 314.
  • Other information that may be used to select a microslice profile includes the network architecture 372, network operational patterns 374, and available network resources 376. And if the UE is in a device group 348 that is associated with one or more microslices, then the device groups 348 may be used to select a microslice profile. Similarly, if the identified application is in a group 344 associated with one or more microslices, then app group 344 may be used to select the microslice profile.
  • Transport protocol used e.g., TCP, QUIC, or UDP.
  • FIG. 5 shows an example of definitions that indicate which applications are associated with a particular microslice.
  • a microslice may be associated with applications that meet the criteria of the first entry, which allows the microslice to be used by any application.
  • Microslices associated with applications that comply with a second entry can only be used by applications defined in accordance with definition of “Application 1” (i.e., having a destination IP address of 1.1.1.1, destination Port 123, etc.).
  • DPI Deep Packet Inspection
  • NSSAI Network Slice Selection Assistance Information
  • FIG. 3D is a flow chart that shows the inputs and operations to set up a microslice instance, starting at 380.
  • Inputs to set up a microslice instance include the selected microslice profile 314, network architecture 372, network operational patterns 374, and available network resources 376.
  • the device groups 348 and the app groups 344 may also be utilized. These inputs may be utilized to select a microslice instance (STEP 382) using functional blocks and communication links in an enterprise network and optionally external networks.
  • the result of setting up a microslice instance (STEP 382) is the microslice instance configuration 317.
  • FIG. 16 and 17 are block diagrams that illustrate microslice instances implemented with functional blocks and communication links.
  • a data flow may be set up to and from the UE, through the RAN, Core Network, and other possibly other servers or networks, to an external server.
  • the microslice is orchestrated by a Network Orchestrator. Note that there can be “N” microslices (MSI, MS2, ..., MSN) defined in any particular implementation.
  • traffic can be routed through multiple functional blocks that are inter-connected by communication links.
  • One or more of the functional blocks may be a pre-existing corporate LAN (e.g., via VLAN or VxLAN).
  • the choice of the functional blocks may be made for the purpose of ensuring specific security and access control rules are met, and/or ensuring that specific QoS and Service Level Objective (SLO) specifications are met.
  • the routing, and/or the specific security and access control rules can be specified by the administrator as part of the microslice profile, or may be orchestrated when the microslice instance is configured.
  • FIG. 3E is a flow chart of operations to manage and monitor microslices during operation. Operation starts (STEP 390), and the microslice instance configuration 317 is then managed and operated (STEP 391) using network components and management techniques, such as described with reference to FIGs. 15, 16, and 17. Operation continues until terminated (STEP 392) by the network, which may happen for a number of reasons, such as the end of the communication session, which ends (STEP 399) operations.
  • the microslice instance is monitored (STEP 393) at one or more of the functional blocks and communication links (described e.g., with reference to FIGs. 15, 16, and 17), to provide Key Performance Indicators (KPIs) 394.
  • KPIs Key Performance Indicators
  • the microslice instance may be monitored at any or all of the functional blocks, end-to-end, and communication links.
  • the instance may be monitored end-to-end or between nodes; for example, the KPIs may be measured as end-to-end performance apart from monitoring the performance within the network components directly managed by the microslice.
  • the end-to-end performance metric includes any appropriate measure such as TCP round-trip-delay, and RTP (realtime protocol) PER I one-way-delay as reported through RTCP (Realtime Control Protocol)
  • the KPIs 394 are compared (STEP 395) with the SLOs 324 defined in the selected microslice profile. If the SLOs 324 are met (STEP 396) then operation returns to STEP 391, to continue to operate and manage the microslice instance. However, if one or more of the SLOs are not met, than the network decides whether or not to take action (STEP 397) based upon the results of the comparison (STEP 395) and any other information that may be useful. If the network decides not to take action (STEP 397), then operation returns to STEP 391, to continue to operate and manage the microslice instance. However, if the network decides to take action (at STEP 397), then corrective action is taken (STEP 398).
  • the microslice instance may be dynamically adjusted, such as by re-configuration in some way.
  • the microslice configuration can be re-configured responsive to the KPIs and the microslice profile (e.g., the SLOs in the microslice profile) and the microslice instance is dynamically adjusted responsive to the revised microslice configuration, so that communication is not significantly interrupted.
  • the microslice instance may be dropped (i.e., terminated). At later time, another microslice instance could be set-up to provide communication with the UE that had been utilizing the dropped microslice.
  • FIG. 3E shows operations on a single microslice, in an operating network it should be clear that multiple microslice instances are operating simultaneously. Accordingly, the operations in FIG. 3E may be performed for each of the operating microslice instances. These monitoring operations may be utilized, optionally with other network data, to provide information relating to network and component loading and other network performance aspects. For example, in an operating network in which multiple microslice instances are operating at the same time, one or more of the components or functional blocks in the enterprise may become slow, overloaded, or otherwise poorly performing.
  • FIGs. 12-14 are flow charts that show some examples of operations that may be performed in this situation, for example load control or admission control may be performed, and alarms may be used. One or more of the microslice instances may be dropped, and/or one or more of the microslice instances may be reconfigured and dynamically adjusted to improve network performance.
  • FIG. 6 is a flow chart of operations (STEP 600) to associate devices with a microslice profile, in one example.
  • the term “devices” includes UEs and other devices or components of the communication network such as routers or APs.
  • Microslice profiles are defined and stored in an accessible server (STEP 602), as described herein. Many different microslice profiles may be defined in any particular embodiment, some embodiments of which may be part of an ETE/5G implementation.
  • the devices are assigned to one or more microslices (STEP 606).
  • the microslice(s) that best matches the needs of the device should be assigned to provide service to the device. Assignment can be made in a number of ways, for example by matching the device’s requested service type with appropriate microslices.
  • one or more other parameters associated with the microslice can be compared with the requested service type or other parameters associated with the device to determine which microslice(s) would be best suited to carry data to and from the device.
  • a default microslice profile called ‘Default’ is included in the product shipment, and therefore is defined “out of the box” (i.e., predefined in the product).
  • This Default microslice profile may, for example, be without any QoS guarantees, commonly known as best effort (BE).
  • BE best effort
  • Device groups 348 are discussed briefly above with reference to FIG. 3B, the following provides additional disclosure. To simplify administration and implementation of microslices, some embodiments may include device groups that may be utilized by a network administrator to associate with one or multiple microslices. Examples of devices that might be assigned to one or more different device groups can include devices such as:
  • a default device group is set up prior to installation (i.e., available “out of the box”), and therefore will be available during installation.
  • This default device group may be called “Default” and unless otherwise specified, each device can automatically be assigned to the “Default” device group to facilitate initial installation and administration.
  • a device group is a flexible grouping of devices. Using device groups, enterprises can, for example, flexibly create categories for their users/devices that have similar usage, service, coverage, and capacity needs in the network. Since this is a flexible grouping, enterprises are at liberty to define these groups to match their current profiling and more efficiently manage devices and network resources.
  • a device group can be defined with specific information such as device group name, administrator name, a trusted/untrusted field, VLAN or VxLAN ID and DHCP server address.
  • FIG. 7 shows an example device group definition, including Field Name, a Value Example for that field, and a Field Description for that field.
  • the Field Names specific to this example include: Device group name, Admin, Trusted, VLAN or VxLAN ID, and DHCP.
  • Mobile devices (UEs) in an enterprise can be associated with a device group, which may include many mobile UEs. In some embodiments, a particular UE can be associated with only one group.
  • the device may be associated with a group by an administrator, for example, or may be associated in response to information provided by the device, or may be associated by default.
  • the association can be implemented as a containerized application running in the Core Network, on Kubernetes or any other such system.
  • Kubernetes is an open-source container-orchestration system for automating application deployment, scaling and management.
  • Containers have become popular as enterprises use DevOps for faster development and deployment of applications.
  • Containers include everything needed to run software, including files and libraries.
  • Containers combine the libraries of an application or microservice into one deployable unit that does not deplete the CPU or memory resources of the host operating system and provide isolation for different services running on the same CPU.
  • EPC core network
  • the microservices architecture provides the ability to spin up the resources on the cloud and on demand so technically all of the network infrastructure can be provided as a cloud native application.
  • Microslices can be seamlessly integrated with existing enterprise local area networks (LANs) and enterprise backhaul wide area networks (WAN).
  • LANs enterprise local area networks
  • WAN wide area networks
  • FIG. 8 is a table showing an example of how microslices can be associated with different device groups.
  • Device Group 1 is assigned to the microslice called “Streaming”, to the microslice called “Video Conf’ and to the “Default” microslice.
  • Streaming the microslice
  • Video Conf the microslice
  • Default the microslice
  • some or all of the applications running on a device within the device group may be associated with a particular one of the enabled microslices.
  • a default microslice can be used for any application or services that are not associated with any other microslices.
  • a decision mechanism may be provided to select between multiple microslices.
  • microslices described herein will typically be implemented in LTE and/or 5G wireless communication networks; that is, communication networks that are constructed according to the specifications of Standard Development Organizations (SDOs) such as 3GPP. They can also be implemented in WiFi networks, or any suitable network. In some embodiments that implement two or more of these networks, the packets in a communication stream can be divided between these networks.
  • SDOs Standard Development Organizations
  • 3GPP Third Generation Partnership Project
  • FIG. 9 is a network diagram showing an architecture of an LTE (4G) wireless communication system.
  • the 4G network in FIG. 9 has a flat, all-IP architecture with separation of control plane and user plane traffic. Acronyms are shown in the network blocks. The following is a list of acronyms shown in the network blocks and other acronyms used in 4G systems:
  • APN Access Point Name
  • ARP Allocation and Retention Priority
  • AMBR Aggregate Maximum Bit Rate
  • ePDG Evolved Packet Data Gateway
  • EPC Evolved Packet Core
  • EPS Evolved Packet switched System
  • HSS Home Subscription Server
  • MME Mobility Management Entity
  • PCC Policy Control and Charging
  • PCRF Policy and Charging Rules Function
  • PDN Packet Data Network
  • PELR Packet Error Loss Rate
  • P-GW Packet Gateway
  • RAB Radio Access Bearer
  • RRC Radio Resource Control
  • S-GW Serving Gateway
  • TFT Traffic Flow Template
  • VoIP Voice over IP
  • Wi-Fi AP WiFi Access Point
  • EPC Evolved Packet Core
  • MME Mobility Management Entity
  • the MME is the key control-node for the LTE access-network. It is responsible for idle mode UE (User Equipment) paging and tagging procedure including retransmissions. It is involved in the bearer activation/deactivation process and is also responsible for choosing the SGW for a UE at the initial attach and at time of intra- LTE handover involving Core Network node relocation. It is responsible for authenticating the user (by interacting with the HSS).
  • NAS Non-Access Stratum
  • the MME is the termination point in the network for ciphering/integrity protection for NAS signaling and handles the security key management. Lawful interception of signaling is also supported by the MME.
  • the MME also provides the control plane function for mobility between LTE and 2G/3G access networks with the S3 interface terminating at the MME from the SGSN. The MME also terminates the S6a interface towards the HSS for roaming UEs.
  • SGW Serving Gateway
  • the SGW routes and forwards user data packets, while also acting as the mobility anchor for the user plane during inter-eNodeB handovers and as the anchor for mobility between LTE and other 3 GPP technologies (terminating S4 interface and relaying the traffic between 2G/3G systems and PGW).
  • the SGW terminates the downlink data path and triggers paging when downlink data arrives for the UE. It manages and stores UE contexts, e.g., parameters of the IP bearer service, network internal routing information. It also performs replication of the user traffic in case of lawful interception.
  • PGW Packet Data Network Gateway
  • the PDN Gateway provides connectivity from the UE to external packet data networks by being the point of exit and entry of traffic for the UE.
  • a UE may have simultaneous connectivity with more than one PGW for accessing multiple PDNs.
  • the PGW performs policy enforcement, packet filtering for each user, charging support, lawful interception, and packet screening.
  • Another key role of the PGW is to act as the anchor for mobility between 3 GPP and non-3GPP technologies such as WiMAX and 3GPP2 (CDMA IX and EVDO).
  • HSS Home Subscriber Server
  • the HSS is a central database that contains user- related and subscription-related information.
  • the functions of the HSS include functionalities such as mobility management, call and session establishment support, user authentication and access authorization.
  • the HSS is based on the pre-Release-4 Home Location Register (HLR) and Authentication Center (AuC).
  • HLR pre-Release-4 Home Location Register
  • AuC Authentication Center
  • ANDSF Access Network Discovery and Selection Function
  • the ANDSF provides information to the UE about connectivity to 3GPP and non-3GPP access networks (such as WiFi).
  • the purpose of the ANDSF is to assist the UE to discover the access networks in their vicinity and to provide rules (policies) to prioritize and manage connections to these networks.
  • ePDG Evolved Packet Data Gateway
  • the main function of the ePDG is to secure the data transmission with a UE connected to the EPC over untrusted non-3GPP access, e.g., VoWi-Fi.
  • the ePDG acts as a termination node of IPsec tunnels established with the UE.
  • An Administrative PDN is provided and shown at 930 in FIG. 9, connected to the EPC, that allows administrative access to the components. Alternatively, there may be administrative access 940 via a direct (non-PDN) connection to the EPC. In one microslice implementation, administrative operations to define and setup the microslice in the EPC, and monitor and operate the microslice instance in the communication network, can be performed via the Administrative PDN 930 or Administrative Access 940.
  • FIG. 10 is a network diagram of an LTE (4G) wireless communication system.
  • 5G Core 5G Core
  • acronyms are shown in the network blocks. Following is a list of acronyms shown in the network blocks and other acronyms used in 5G systems:
  • AMF Access and Mobility Management Function
  • AUSF Authentication Server Function
  • NEF Network Exposure Function
  • NRF Network Repository Function
  • NSSF Network Slice Selection Function
  • PCF Policy Control Function
  • PCEF Policy and Charging Enforcement Function
  • SD Slice Differentiator
  • SMF Session Management Function
  • SMSF Short Message Service
  • UDM User Data Management
  • UPF User Plane Function
  • Administrative access 1030 is provided to the 5GC, such as via a PDN connected securely to the 5GC, which allows administrative access to the components such as the UDM in the 5GC.
  • administrative operations in the EPC to define and setup the microslice, and to monitor and operate the microslice instance throughout the communication network can be performed via this Administrative access.
  • the User Data Management (UDM) function 1050 may be utilized to set up and store the data fields relating the microslices, service types, device groups, applications and other useful information. (12) Monitoring and adjusting the microslice instances
  • FIG. 3E a method is shown and described to manage and monitor microslice instances during network operation. While operation is continuing, the microslice instances are monitored at one or more of the functional blocks, end-to-end, and at communication links (described e.g., with reference to FIGs. 9. 10, 15, 16, and 17), to provide Key Performance Indicators (KPIs) 394 (and optionally other values), which are compared with the SLOs 324 defined in the selected microslice profile.
  • KPIs Key Performance Indicators
  • microslice operation can continue unchanged; however, if one or more of the SLOs are not met, then the network decides whether or not to take action based upon the results of the comparison and any other information that may be useful. If the network decides not to take action, then operation can continue unchanged; however, if the network decides to take action, then corrective action is taken.
  • FIGs. 12-14 are flow charts that show some examples of operations that may be performed if the network decides to take corrective action, for example load control or admission control may be performed, and alarms may be used.
  • One or more of the microslice instances may be dropped.
  • One or more of the microslice instances may be adjusted or adjusted, such as by re-configuration in some way.
  • the microslice configuration can be re-configured responsive to the KPIs and the microslice profile (e.g., the SLOs in the microslice profile) and the microslice instance is dynamically adjusted responsive to the revised microslice configuration.
  • a microslice instance is monitored.
  • the microslice instance may be monitored at all of the functional blocks and communication links, in other embodiments particular functional blocks and communication links may be selected based, e.g., upon the usefulness of the information that can be provided by the selected block or link.
  • the instance may be monitored end-to-end or between nodes.
  • KPIs Key Performance Indicators
  • the KPIs that will be compared with the SLOs may include the following in one example:
  • IP layer Packet Throughput
  • the KPIs can be monitored by the RAN, Core Network and/or devices, in combination or individually.
  • a preferred method is to utilize only the Core Network to measure these KPIs directly using a Performance Monitoring Engine (PME), shown at 1040 in FIG. 10.
  • PME Performance Monitoring Engine
  • the EPC generates diagnostic traffic to measure packet latency, loss rate and jitter between the EPC and the device.
  • the measurements can be achieved by using ICMP protocol, and monitoring round trip characteristics of IP packets generated by the ICMP applications.
  • the Internet Control Message Protocol (ICMP) is a supporting protocol in the Internet protocol suite as defined.
  • ICMP is used by network devices, including routers, to send error messages and operational information indicating success or failure when communicating with another IP address; for example, an error will be indicated when a requested service is not available or if a host or router could not be reached.
  • ICMP differs from transport protocols such as TCP and UDP in that ICMP is not typically used to exchange data between systems, nor is it typically employed by end-user network applications.
  • inspection of the TCP/IP packet headers of the ongoing data traffic can be used to measure the KPIs.
  • TCP ACK packet header indicates which specific TCP packet (sequence number field) is being acknowledged.
  • TCP/IP header files such as (“TSval” ad TSecor”) can be used to identify which specific TCP packet is acknowledged.
  • round-trip delay can be measured between the corresponding TCP packet and TCP ACK packet at EPC (by comparing the time stamp recorded from the original TCP packet with the corresponding ACK packet reception time). This operation can be performed both for downlink and uplink directions, giving a measurement of RTT between the EPC and UE, and between the EPC and application server.
  • Packet retransmission rate TCP headers (sequence number field) can be used to get a measure of packet retransmission rate via detection of repeated sequence numbers. Also, TCP ACK packet headers (acknowledgment number field) can be utilized for same purpose. The operation can be done both for the downlink and uplink direction giving a measurement of packet retransmission rate between EPC and UE, and between EPC and application server.
  • Artificial Intelligence (Al) techniques can be used to learn traffic patterns and associated KPIs such as packet latency, loss rate and jitter. For example, different multimedia applications may adjust traffic rate and packet sizes based on available throughput and packet error rate, or control the traffic associated with the application so that it has a certain behavior correlated with some of the network KPIs.
  • a PME 1040 (FIG. 10) is implemented, it may utilize any additional information that can be provided by the RAN and UE.
  • BS/AP (RAN)-provided performance metrics can include: 1) the achieved Packet Error Rate (PER) (MAC and RLC layer) for each QoS flow; and 2) PRB resource utilization for each QoS flow.
  • UE-provided performance metrics can include achieved PER (MAC, RLC and IP layer) for each QoS flow; and channel quality (SNR). Any of this information can be useful to help determine if the SLOs are being met.
  • the Performance Monitoring Engine (PME) 1040 preferably can update the current KPIs in real time, and provide the updated KPI values to an admission control function and a load control function for the RAN and EPC network, so that the current KPIs are available if and when needed.
  • the current KPIs may include, or be sent with, an indication of a specific QoS flow, microslice, BS/AP, functional component in the RAN or Core Network associated with the particular KPI.
  • FIGS. 12, 13, and 14 are flow charts that show examples of operations that may be taken to improve system performance. Particularly, FIG.
  • FIG. 12 shows an example of load control
  • FIG. 13 shows an example of admission control
  • FIG. 14 shows an example of alarm and control operations.
  • FIG. 3E shows taking corrective action such as reconfiguring a microslice instance and/or dynamically adjusting it to re-allocate network resources if the KPIs of a microslice are not met.
  • one or more of the components or functional blocks in the enterprise may become slow, overloaded, or otherwise poorly performing. If, during network operation, the load on the enterprise network, one or more of its network components, or functional blocks becomes too great (performance has degraded to a certain level), then one option is to perform load control operations. In one embodiment, lower priority microslices can be dropped (e.g., by the EPC) to accommodate higher priority traffic. As another example, one or more microslice instances can be re-configured, downgraded, and/or dynamically adapted to redistribute the load to different components or functional blocks that have more available resources. Then, the load can be monitored and if necessary, another round of load control operations can be performed until acceptable network performance levels are achieved.
  • FIG. 12 is flow chart that shows an example of network load control operations (STEP 1200) in an operating network that has instantiated microslices for communication with and/or through the enterprise network.
  • Network performance is measured at one or more functional blocks and communication nodes, and/or end-to-end; e.g., the KPIs for each microslice instance, and/or end-to-end performance can be measured (STEP 1202).
  • the KPIs may be measured continuously, periodically, or intermittently.
  • the KPIs are compared (STEP 1203) with predetermined network and microslice performance objectives 1205 such as the SLOs 324.
  • predetermined network and microslice performance objectives 1205 such as the SLOs 324.
  • these performance objectives 1205 are not met (i.e., the load threshold has been exceeded, this may indicate an overload condition that may require some action.
  • action should be taken.
  • KPIs exceeds threshold (STEP 1204) (e.g., if any specific KPI having index j (KPIj) passes a KPIj_load_control threshold (which may predetermined responsive to the respective SLOs) for a specified period of time (which means that the load may have become too high), the specific components (functional blocks and/or communication links) in the service under load (e.g., BS/APs and other components of the enterprise network) should be identified (STEP 1206).
  • KPI information may be collected from all the operating microslices and compared with objectives. Using this information, all the microslice instances that utilize the specific component or functional block in the enterprise network may be evaluated and sorted (STEP 1208) according to their priority, such as defined by their QCI, and the lowest priority microslices are identified.
  • the network then develops a load mitigation plan (STEP 1209), which may take into account the identified microslices, components, performance objectives, the extent to which the network is loaded, where there is available capacity in the network, and any other relevant data.
  • This step 1209 may utilize artificial intelligence (AI)/machine learning techniques to learn and select an approach.
  • AI artificial intelligence
  • the load mitigation plan may include techniques such as dropping (i.e., terminating) one or more of the identified microslices (STEP 1210).
  • microslice priority may be chosen in accordance with Allocation and Retention Priority characteristics, and the lowest priority microslice instances may be dropped beginning with the lowest priority, and continuing until performance improves.
  • the results may be monitored in real time, and when performance improves, a decision may be made (STEP 1212) that the KPIs, and particularly the specific KPIj’s under evaluation, satisfy the KPIj_load_control or SLO values.
  • the load mitigation plan may include modifying one or more of the lower priority microslice instances in some way to release their resources for higher priority traffic.
  • one or more of the identified microslice(s) may be reconfigured, downgraded, and/or dynamically adjusted to re-distribute the load to different components or functional blocks that have more resources available, in order to improve network performance and/or provide appropriate service to higher priority microslices or other network functions.
  • the load mitigation plan may include modifying a microslice instance for all UEs or modifying for a finite subset of users I user groups that use that microslice instance.
  • FIG. 13 is a flow chart that illustrates network admission operations (STEP 1300).
  • STEP 1300 network admission operations
  • Admission control operations may include denying UE’s admission for new calls and/or requests for services, in order to keep the KPIs at the desired levels for all other UEs and other devices in the system, and stay within reasonable bounds set by the SLOs of the microslices and the network.
  • Operation remains in a waiting state (STEP 1302) until a request for new services (e.g., a new call or new microslice setup request) is received.
  • a request for new services e.g., a new call or new microslice setup request
  • the system estimates the resources needed for the new services, and then determines KPI admission control values (STEP 1304).
  • the amount of resources needed for the incoming call can be estimated based on microslice requirements and other sources, such as analysis of ongoing flows utilizing AI/ML (Artificial Intelligence/Machine Learning) techniques, and can be performed in the Al Module 1540 (FIG. 15). This estimate of resources, and any other useful information, can be used to determine KPI admission control values.
  • AI/ML Artificial Intelligence/Machine Learning
  • ARP Allocation and Retention Priority
  • the request for new services may be denied (STEP 1318), and operation ends (STEP 1312).
  • the flows are sorted according to priority (STEP 1320) and lower priority flow(s) may be terminated (dropped similar to load control discussed above with reference to FIG. 12) (STEP 1322) to create enough resources for the incoming services request.
  • the new services request is then admitted (STEP 1324), and the admission control operation is complete (STEP 1312).
  • a BS/AP may have other metrics available to monitor and control load, such as the maximum number of RRC-Connected users allowed. These other metrics can also be used to perform admission control at the RAN and BS/AP level.
  • an alarm may be triggered, and/or a control procedure may be utilized.
  • the alarm procedure may be used for any purpose, for example it may be used to alert a user or a system component of a current or impending problem, or it may be used to notify and trigger load control and/or admission control as described above.
  • FIG. 14 describes Alarm and Control Operations (STEP 1400).
  • a specific threshold for a particular alarm is set at a desired level (STEP 1402).
  • these thresholds can be set to a certain value with respect to the maximum limit allowed by the SLOs. For example, a KPIj_admission_control may trigger an alarm at 80% of the maximum allowed value and the KPIj_load_control may trigger an alarm at 90% of the maximum allowed value for the KPIj, consistent with the SLOs.
  • the KPIs relevant to that alarm are monitored (STEP 1404). While KPIs remain below threshold, monitoring continues. (STEP 1406). However, if any of the KPIs is exceeded, an alarm is triggered (STEP 1408) (a KPIj_alarm).
  • the alarm may be provided to any interested entity, such as a network administrator, a system component in the enterprise network 1500, the cloud-based network orchestration module 1530, the UE, the RAN, the EPC, or any other entity that has an interest in knowing that a particular QoS flow or system component or microslice instance is nearing its maximum allowed value.
  • a specific threshold may be set to trigger load control (a KPIj_load_control) procedure such as shown and described with reference to FIG. 12, and a specific threshold may be set to trigger an admission control (a KPIj_admission_control) procedure such as shown and described with reference to FIG. 13.
  • FIG. 15 is a block diagram of an implementation of an enterprise network 1500 that implements the techniques described herein.
  • the enterprise network 1500 includes a radio access network (RAN) 1510 that includes a plurality of BS/APs 1511 that wirelessly communicate with a plurality of UEs 1512 over a wireless link 1514.
  • the BS/APs 1511 are installed in a campus 1516, and the UEs 1512 are present in or around the campus 1516 to wirelessly communicate with one or more of the BS/APs 1511.
  • the enterprise network 1500 includes a core network 1520 (also called a Programmable Service Edge or “PSE”) that provides a variety of services for the network.
  • An administrative interface 1518 allows a network administrator to access the enterprise network.
  • a cloud-based network orchestration module 1530 connected to the core network 1520, provides administrative services 1532, databases 1534, and other functional units that may provide machine learning and artificial intelligence.
  • the core network 1520 includes a plurality of components that provide services for the network, including an MMF (Mobility Management Function) unit 1521, a SON (Self Organizing Network) service unit 1522, a monitoring service unit 1523, an SGW/PGW (Serving Gateway/Packet Data Network Gateway) unit 1524, a domain proxy 1525, a TR069 unit 1526, and a KPI (Key Performance Indicator) service unit 1527.
  • the core network 1520 may also include microslice profiles database 1528, device groups database 1529, and other units for additional network services 1531 as required or useful.
  • the Al module 1540 may be implemented as part of the core network module 1520, and be connected to any of the functional units therein.
  • the core network 1520 is connected to a cloud-based network orchestration module
  • the core network 1520 and the orchestration module 1530 may be connected via a Packet Data Network (PDN) 1550.
  • PDN Packet Data Network
  • the cloud-based orchestration components 1530 include an Administrative Service Unit 1532 for remote administration of the enterprise network, databases 1534, a Microslice Orchestration Module 1560 (described in more detail with reference to FIG. 16), and other components as may be necessary or useful.
  • the Microslice Orchestration Module 1560 may be implemented as part of the enterprise network 1500.
  • the Al module 1540 may be implemented as part of the orchestration module 1530 or the enterprise network 1500.
  • Data collected from the BS/APs 1511 may be supplied to an Artificial Intelligence (Al) Module 1540 that includes an Application Association Unit 1542 and Request Detection Unit 1544.
  • the data supplied to the Al Module 1540 may include UE data, RAN data, and may be indicative of the load being experienced by the BS/APs 1511.
  • Data can be collected in batches and history-based learning and/or ML techniques performed on the batch of data, and then implemented. Alternatively, or after initial learning using batches of data, data can be collected periodically or nearly continuously in real time, and learning and ML can be implemented automatically (e.g., 5-minute intervals) to continually improve the models and thereby continually improve network performance.
  • the Al module 1540, the Application Association Unit 1542, and the Request Detection Unit 1544 include appropriate circuitry to perform their functions.
  • Al systems in the Al module 1540 may be implemented based upon any or all of heatmaps, the estimated ability to defuse congestion by offloading traffic, and preemptive steps to prevent users from attaching to the enterprise network.
  • the Al systems may be implemented to monitor and anticipate congestion in the enterprise network.
  • the Al module 1540 is connected to the core network 1520, and supplies the results of its learning and other information to the core network 1520 and/or the network orchestration module 1530.
  • the Al Module 1540 may also receive feedback from the BS/APs 1511. Particularly, network performance and congestion may be monitored to provide feedback to the Al system. For example, new performance data can be compared and/or combined with the previous data and new learning can be performed. Also, reinforcement learning techniques can be implemented using the new data and historical data to improve the Al system and thereby improve network performance. (19) Microslice Instance Block Diagram
  • FIG. 16 is a block diagram of a wireless communication system including the enterprise network 1500 and the cloud-based network orchestration module 1530 that includes the microslice orchestration module 1560.
  • the microslice orchestration module 1560 includes a receiving unit 1662 and a microslice orchestrating unit 1664.
  • the receiving unit 1662 is connected to receive resource availability information 1602, microslice profiles from the microslice profiles database 1528, and device groups from the device group database 1529.
  • the resource availability information 1602 may be supplied by appropriate functional units in the Core Network 1520 responsive to information that may be provided by the RAN, other functional units in the Core Network, and the UEs.
  • the resource availability information 1602 may include data indicative of the resources available in the enterprise network, and current resource usage.
  • the microslice orchestrating unit 1664 determines a network configuration that defines a microslice instance responsive to the microslice profile, the resource availability information 1602, and in some embodiments, the device groups. Particularly, responsive to these inputs, the network configuration defines the configuration for the microslice using functional blocks and the communication links between the functional blocks.
  • the microslice orchestration module 1560 also includes a configuration control unit 1566 for setting up and controlling the functional blocks and the communication links between the functional blocks responsive to the network configuration, to implement a microslice instance.
  • a functional block is a computing element that performs any activity required to implement a set of logical operations.
  • the functional block may include a dedicated processing circuit that performs an intended function, or it may be a software-implemented process across circuits that performs the intended function.
  • the activity required to implement a set of logical operations is performed for the purpose of facilitating end to end communication (e.g., between a UE and an external server).
  • a functional block may be in the control plane or the user plane.
  • control information is exchanged between the block and the orchestrator; for example, the orchestrator may make a query, and the functional block may respond.
  • a communication link is a connection between two functional blocks that provides communication between the two functional blocks.
  • the communication link may be implemented in any appropriate connection type, such as wireless or wired, and utilize any suitable protocol.
  • the link and/or protocol may be secure or otherwise.
  • a communication link may be monitored at any point in the link, for example it may be monitored at its entry point and/or its exit point to provide performance data.
  • FIG. 16 shows two examples of microslice instances, including a first instance 1610 and a second instance 1620.
  • the first instance 1610 shows a simple configuration in which a series of interconnected functional blocks 1612 and links 1614 connect a UE with the microslice orchestration module 1560 in the network orchestration module 1530.
  • the second instance 1620 shows a configuration including a control plane 1630 and a user plane 1640, and there are functional blocks and communication links in both the control plane 1630 and the user plane 1640, all of which are connected to the UE and the microslice orchestration module 1560. It should be clear that within the second microslice instance 1620, there are interconnections between the functional units, the UE, and the orchestration module 1530.
  • control plane 1630 includes a plurality of interconnected functional blocks 1632 and communication links 1634
  • user plane 1640 includes a plurality of interconnected functional blocks 1642 and communication links 1644.
  • the microslice orchestration module 1560 is connected to the enterprise network 1500, the receiving unit 1662 receives the microslice profiles, the resource availability information (and optionally the device groups) from the enterprise network, the microslice orchestrating unit determines a network configuration that defines a microslice instance in the enterprise network, and the configuration control unit 1666 sets up and controls the functional blocks and the communication links in the enterprise network to implement the microslice instance.
  • the orchestrating unit 1664 includes circuitry to set up and configure functional blocks that may be within an enterprise network (i.e., within the enterprise network’s control), or the functional blocks may be outside the enterprise network (i.e., the functional block(s) may be outside the enterprise network’s control, e.g., in a non-enterprise communication platform).
  • a non-enterprise communication platform is external network 1680, which includes at least one functional block 1682, and is connected to the network orchestration module 1530 and the enterprise network 1500 via an external PDN 103.
  • the external network 1680 may be a private network, for example.
  • the configuration control unit 1666 is connected to set up and control the functional blocks either inside the enterprise network or outside the enterprise network.
  • one of the functional blocks that may be either inside or outside the enterprise network may be a LAN, a VLAN or a VxLAN.
  • a functional block may comprise an internal or external network or network element that can be controlled directly, or indirectly, and/or its communications can be managed, by the configuration control unit 1666.
  • the enterprise network 1500, or any other network connected to the microslice orchestration module 1560 may provide resource availability information 1602.
  • Resource availability information may include data or other information relevant to any or all of the available network resources, such as available communication resources, computing resources (e.g., hardware like processors, state machines, dedicated circuitry, virtual machines), available spectrum, and the current extent of loading of the functional units, and other network operational parameters such as the KPIs.
  • the microslice orchestration module 1560 may include a Network Resource Allocation Module 1668 that allocates network resources to the microslice configuration responsive to the resource availability information.
  • the allocated network resources may include communication resources, computing resources (e.g., hardware-like processors, state machines, and dedicated circuitry virtual machines) available spectrum, and the current extent of loading of the functional units and other network operation parameters). These quantities may be measured and supplied to the microslice orchestration module 1560 in any appropriate format, e.g., by KPIs.
  • computing resources e.g., hardware-like processors, state machines, and dedicated circuitry virtual machines
  • the microslice orchestration module 1560 includes a monitoring unit 1670 that is connected to the functional units and communication links to separately monitor the performance of the functional units, the communication links between the functional units, and the end-to-end performance to provide Key Performance Indicators (KPIs) for each.
  • KPIs Key Performance Indicators
  • the microslice orchestration module 1560 further includes a performance managing unit 1672 that can revise the microslice configuration responsive to the KPIs and the microslice profile (e.g., the SLOs in the microslice profile) and dynamically adjusts the microslice instance responsive to the revised microslice configuration. For example, if the KPIs show that the microslice instance is not meeting its SLOs, the microslice instance can be re-configured using other available network resources, to improve performance. As another example, if the microslice instance’s network resources are being under-utilized, then the microslice instance can be re-configured to re- allocate the unneeded resources to other microslice instances.
  • a performance managing unit 1672 can revise the microslice configuration responsive to the KPIs and the microslice profile (e.g., the SLOs in the microslice profile) and dynamically adjusts the microslice instance responsive to the revised microslice configuration
  • the enterprise network 1500 includes a load control unit 1674 that implements load control operations, such as shown in FIG. 12, responsive to inputs such as the KPIs and instructions from any of the functional blocks in the microslice orchestration module 1560.
  • the load control unit 1674 is connected to functional blocks in the enterprise networks 1500 and the network orchestration module 1530 as appropriate to perform its operations, and may be implemented partly or wholly in those functional blocks.
  • the load control unit 1674 can receive KPI inputs 394 and other network metrics and compare them with SLOs 324 and other performance objectives.
  • the enterprise network 1500 also includes an admission unit 1676 that implements admission operations, such as shown in FIG. 13, responsive to inputs such as the KPIs and instructions from any of the functional blocks in the microslice orchestration module 1560.
  • the admission unit 1676 is connected to functional blocks in the enterprise networks 1500 and the network orchestration module 1530 as appropriate to perform its operations, and may be implemented partly or wholly in those functional blocks.
  • the enterprise network 1500 also includes an alarm unit 1678 that implements alarm operations, such as shown in FIG. 14, responsive to inputs such as the KPIs and instructions from any of the functional blocks in the microslice orchestration module 1560.
  • the alert unit 1678 is connected to functional blocks in the enterprise networks 1500 and the network orchestration module 1530 as appropriate to perform its operations, and may be implemented partly or wholly in those functional blocks.
  • FIG. 17 illustrates microslice instances 1710 and 1720 that extend outside the enterprise network 1500.
  • FIG. 17 is a block diagram of a wireless communication system that comprises the enterprise network 1500, the cloud-based network orchestration module 1530, and external networks 1780.
  • a first microslice instance 1710 connects one of the UEs 1512 with a first external network 1780a via functional blocks and links in the enterprise network 1500 that connect to a functional block 1782a in the first external network 1780a.
  • a second microslice instance 1720 connects one of the UEs 1512 with a second external network 1780b via functional blocks and links in the enterprise network 1500 that connect to a functional block 1782b in the second external network 1780b.
  • Some or all aspects of the invention may be implemented in hardware or software, or a combination of both (e.g., programmable logic arrays). Unless otherwise specified, the algorithms included as part of the invention are not inherently related to any particular computer or other apparatus. In particular, various general purpose computing machines may be used with programs written in accordance with the teachings herein, or it may be more convenient to use a special purpose computer or special-purpose hardware (such as integrated circuits) to perform particular functions.
  • embodiments of the invention may be implemented in one or more computer programs (i.e., a set of instructions or codes) executing on one or more programmed or programmable computer systems (which may be of various architectures, such as distributed, client/server, or grid) each comprising at least one processor, at least one data storage system (which may include volatile and non-volatile memory and/or storage elements), at least one input device or port, and at least one output device or port.
  • Program instructions or code may be applied to input data to perform the functions described in this disclosure and generate output information.
  • the output information may be applied to one or more output devices in known fashion.
  • Each such computer program may be implemented in any desired computer language (including machine, assembly, or high-level procedural, logical, or object-oriented programming languages) to communicate with a computer system, and may be implemented in a distributed manner in which different parts of the computation specified by the software are performed by different computers or processors.
  • the computer language may be a compiled or interpreted language.
  • Computer programs implementing some or all of the invention may form one or more modules of a larger program or system of programs.
  • Some or all of the elements of the computer program can be implemented as data structures stored in a computer readable medium or other organized data conforming to a data model stored in a data repository.
  • Each such computer program may be stored on or downloaded to (for example, by being encoded in a propagated signal and delivered over a communication medium such as a network) a tangible, non-transitory storage media or device (e.g., solid state memory media or devices, or magnetic or optical media) for a period of time (e.g., the time between refresh periods of a dynamic memory device, such as a dynamic RAM, or semi-permanently or permanently), the storage media or device being readable by a general or special purpose programmable computer or processor for configuring and operating the computer or processor when the storage media or device is read by the computer or processor to perform the procedures described above.
  • the inventive system may also be considered to be implemented as a non-transitory computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer or processor to operate in a specific or predefined manner to perform the functions described in this disclosure.
  • a group of items linked with the conjunction “and” should not be read as requiring that each and every one of those items be present in the grouping, but rather should be read as “and/or” unless expressly stated otherwise.
  • a group of items linked with the conjunction “or” should not be read as requiring mutual exclusivity among that group, but rather should also be read as “and/or” unless expressly stated otherwise.
  • items, elements or components of the disclosed method and apparatus may be described or claimed in the singular, the plural is contemplated to be within the scope thereof unless limitation to the singular is explicitly stated.
  • module does not imply that the components or functionality described or claimed as part of the module are all configured in a common package. Indeed, any or all of the various components of a module, whether control logic or other components, can be combined in a single package or separately maintained and can further be distributed in multiple groupings or packages or across multiple locations.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

[0001] L'invention concerne un procédé et un appareil permettant de définir, de configurer, d'exploiter, de surveiller et de modifier des microtranches dans un réseau de communication sans fil d'entreprise. Divers modes de réalisation d'un système permettant à un administrateur du réseau sans fil de créer et de mettre en œuvre des exemples de microtranches sont décrits. L'administrateur peut définir des objectifs de niveau de service (SLO), des groupes de dispositifs, des types de services et des groupes d'applications d'utilisateurs, et les associer à une ou plusieurs microtranches. Un exemple de microtranche peut relier un UE dans le réseau d'entreprise à un serveur externe. Un procédé et un appareil d'utilisation de microtranches pour gérer et contrôler les performances d'un réseau sont également décrits. Les exemples de microtranches sont surveillés pendant le fonctionnement du réseau au niveau de nœuds de communication, de blocs fonctionnels et de bout en bout pour fournir des indicateurs de performance clé (KPI) qui sont comparés à des objectifs de performance, qui peuvent être des SLO. Si les objectifs de performance ne sont pas satisfaits, alors les exemples de microtranches peuvent être ajustés de manière dynamique jusqu'à ce que les objectifs de performance soient suffisamment satisfaits.
PCT/US2022/049984 2021-11-16 2022-11-15 Procédé et appareil permettant de créer et d'utiliser des microtranches dans un réseau de communication sans fil d'entreprise WO2023091425A1 (fr)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US202163280060P 2021-11-16 2021-11-16
US63/280,060 2021-11-16
US202163283211P 2021-11-24 2021-11-24
US63/283,211 2021-11-24
US17/687,546 2022-03-04
US17/687,546 US20220255798A1 (en) 2019-12-31 2022-03-04 Method and Apparatus for Microslicing Wireless Enterprise Communication Networks Using Microslice Profiles
US17/979,266 2022-11-02
US17/979,266 US20230121880A1 (en) 2019-12-31 2022-11-02 Method and Apparatus for using Microslices to Control Network Performance of an Enterprise Wireless Communication Network

Publications (1)

Publication Number Publication Date
WO2023091425A1 true WO2023091425A1 (fr) 2023-05-25

Family

ID=86397686

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/049984 WO2023091425A1 (fr) 2021-11-16 2022-11-15 Procédé et appareil permettant de créer et d'utiliser des microtranches dans un réseau de communication sans fil d'entreprise

Country Status (1)

Country Link
WO (1) WO2023091425A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180152958A1 (en) * 2016-11-28 2018-05-31 Deutsche Telekom Ag Radio communication network with multi threshold based sla monitoring for radio resource management
US20200313985A1 (en) * 2019-03-30 2020-10-01 Wipro Limited Method and system for effective data collection, aggregation, and analysis in distributed heterogeneous communication network
US20210160153A1 (en) * 2019-11-27 2021-05-27 Netsia, Inc. Slice assurance within a mobile network
US20210204164A1 (en) * 2019-12-31 2021-07-01 Celona, Inc. Method and apparatus for microslicing wireless communication networks with device groups, service level objectives, and load/admission control

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180152958A1 (en) * 2016-11-28 2018-05-31 Deutsche Telekom Ag Radio communication network with multi threshold based sla monitoring for radio resource management
US20200313985A1 (en) * 2019-03-30 2020-10-01 Wipro Limited Method and system for effective data collection, aggregation, and analysis in distributed heterogeneous communication network
US20210160153A1 (en) * 2019-11-27 2021-05-27 Netsia, Inc. Slice assurance within a mobile network
US20210204164A1 (en) * 2019-12-31 2021-07-01 Celona, Inc. Method and apparatus for microslicing wireless communication networks with device groups, service level objectives, and load/admission control

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
BOUSSARD MATHIEU; SAUZE NICOLAS LE; PAPILLON SERGE; PELOSO PIERRE; VARLOOT REMI: "Secure Application-Oriented Network Micro-Slicing", 2019 IEEE CONFERENCE ON NETWORK SOFTWARIZATION (NETSOFT), IEEE, 24 June 2019 (2019-06-24), pages 248 - 250, XP033601981, DOI: 10.1109/NETSOFT.2019.8806629 *

Similar Documents

Publication Publication Date Title
US11284288B2 (en) Method and apparatus for microslicing wireless communication networks with device groups, service level objectives, and load/admission control
US10506492B2 (en) System and method to facilitate link aggregation using network-based internet protocol (IP) flow mobility in a network environment
JP6701196B2 (ja) 通信における体感品質（ＱｏＥ）の強化
EP2441211B1 (fr) Contrôle des performances dans un réseau de communication
EP1654625B1 (fr) Optimisation de trafic autoip dans des systemes de telecommunications mobiles
US11558924B2 (en) Method and apparatus for selectively releasing user equipment devices to efficiently operate an enterprise wireless communication network
CN104904263B (zh) 用于控制wlan系统中的过载的装置和方法
US11540176B2 (en) Method and apparatus for load control of an enterprise network on a campus based upon observations of busy times and service type
US20220255798A1 (en) Method and Apparatus for Microslicing Wireless Enterprise Communication Networks Using Microslice Profiles
WO2016091298A1 (fr) Mise à jour de politiques de qualité de service (qos) spécifiques à un flux sur la base d'informations rapportées à partir d'une station de base
CN114097267A (zh) 用于具有wi-fi和蜂窝数据的用户偏好的组合管理的系统和方法
Moura et al. Ethanol: A software-defined wireless networking architecture for IEEE 802.11 networks
WO2022098561A1 (fr) Procédé et appareil de libération sélective de dispositifs d'équipement d'utilisateur pour faire fonctionner efficacement un réseau de communication sans fil d'entreprise
CN115462174A (zh) 用于处理卸载的会话管理
US10959130B2 (en) Quality of service class indicator structure and corresponding controllers and control methods
CN112953748B (zh) 一种通信方法及装置
US20230156479A1 (en) Multilink uplink grant management method
US20230121880A1 (en) Method and Apparatus for using Microslices to Control Network Performance of an Enterprise Wireless Communication Network
WO2023091425A1 (fr) Procédé et appareil permettant de créer et d'utiliser des microtranches dans un réseau de communication sans fil d'entreprise
Luengo An openflow-based wireless user management system
US20210297864A1 (en) Backhaul Estimation Scheduling
US20240107367A1 (en) Intelligent connectivity and data usage management for mobile devices in a converged network
KR20200081353A (ko) 서비스 품질 정보 갱신 방법
Al-Shammari Assurance, Provision, Management and Enhancement of QoS in 5G Communication Networks
Main et al. Document Title: Intermediate Design of the MEVICO Traffic Engineering Architecture

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

Country of ref document: EP

Kind code of ref document: A1