US20200106714A1 - System and method for managing network resources - Google Patents
System and method for managing network resources Download PDFInfo
- Publication number
- US20200106714A1 US20200106714A1 US16/585,585 US201916585585A US2020106714A1 US 20200106714 A1 US20200106714 A1 US 20200106714A1 US 201916585585 A US201916585585 A US 201916585585A US 2020106714 A1 US2020106714 A1 US 2020106714A1
- Authority
- US
- United States
- Prior art keywords
- network
- data
- resources
- network resources
- internal data
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/78—Architectures of resource allocation
- H04L47/781—Centralised allocation of resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- 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/14—Network analysis or design
- H04L41/147—Network analysis or design for predicting network behaviour
-
- 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/16—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence
-
- 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/5019—Ensuring fulfilment of SLA
- H04L41/5025—Ensuring fulfilment of SLA by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/801—Real time traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/808—User-type aware
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
- H04L47/822—Collecting or measuring resource availability data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
- H04L47/823—Prediction of resource usage
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/83—Admission control; Resource allocation based on usage prediction
Definitions
- the present technology relates to systems and methods for managing network resources.
- the systems and methods allow network resource orchestration and/or network resource maintenance.
- Network service providers typically implement and manage physical network architecture components (i.e., network hardware resources) to deploy network functions.
- network hardware resources may comprise, without being limitative, antennas, routers, storages, switches, servers, gateways.
- the network hardware resources typically operate in accordance with one or more protocols so as to ensure proper communication amongst the network hardware resources.
- Network functions are traditionally deployed as physical devices running software components that are tightly coupled to the physical devices. Such approach to network functions creates operational challenges as manual interventions are often required to upscale or downscale network resources thereby preventing fast deployment of new network functions.
- network service providers have turned to network virtual resources allowing operating virtualized network functions decoupled for the underlying hardware.
- the network virtual resources may rely on one or more virtual machines running software on top the physical network architecture as opposed to requiring dedicated network hardware devices for each network functions.
- an orchestration layer may deploy one or more virtual machines to add capacity to the network.
- Increase and/or decrease in network resource capacity is often reactive in nature and contingent upon arriving at some trigger point (e.g., a measurement that a network resource operates beyond its limits, loss of network functionality in part or whole).
- Such reactive increase and/or decrease in network resource capacity may present challenges in rendering optimal network service delivery, in particular in contexts wherein the network resources support a plurality of network applications (e.g., high throughput data consumer communications, low latency automotive connectivity, multiple heterogeneous connected devices) in dynamic time varying environments.
- Embodiments of the present technology have been developed based on developers' appreciation of shortcomings associated with the prior art.
- such shortcomings may comprise (1) a reactive approach to increase and/or decrease in network resource capacity deployment, as opposed to a proactive approach; and (2) silos between various data sources based on which increase and/or decrease in network resource capacity deployment may be determined, thereby limiting an ability to implement a proactive approach.
- various implementations of the present technology provide a method for managing network resources enabling network services over a network, the method comprising:
- various implementations of the present technology provide a method for managing maintenance of network resources, the method comprising:
- various implementations of the present technology provide a non-transitory computer-readable medium storing program instructions for executing methods of managing network resources, the program instructions being executable by a processor of a computer-based system to carry out one or more of the above-recited methods.
- various implementations of the present technology provide a computer-based system, such as, for example, but without being limitative, an electronic device comprising at least one processor and a memory storing program instructions for executing methods of managing network resources, the program instructions being executable by the at least one processor of the electronic device to carry out one or more of the above-recited methods.
- a computer system may refer, but is not limited to, an “electronic device”, an “operation system”, a “system”, a “computer-based system”, a “network system”, a “network device”, a “controller unit”, a “monitoring device”, a “control device” and/or any combination thereof appropriate to the relevant task at hand.
- computer-readable medium and “memory” are intended to include media of any nature and kind whatsoever, non-limiting examples of which include RAM, ROM, disks (CD-ROMs, DVDs, floppy disks, hard disk drives, etc.), USB keys, flash memory cards, solid state-drives, and tape drives. Still in the context of the present specification, “a” computer-readable medium and “the” computer-readable medium should not be construed as being the same computer-readable medium. To the contrary, and whenever appropriate, “a” computer-readable medium and “the” computer-readable medium may also be construed as a first computer-readable medium and a second computer-readable medium.
- Implementations of the present technology each have at least one of the above-mentioned objects and/or aspects, but do not necessarily have all of them. It should be understood that some aspects of the present technology that have resulted from attempting to attain the above-mentioned object may not satisfy this object and/or may satisfy other objects not specifically recited herein.
- FIG. 1 is a diagram of a computing environment in accordance with an embodiment of the present technology
- FIG. 2 is a diagram of a network service provider environment in accordance with an embodiment of the present technology
- FIG. 3 is a diagram illustrating a network management and orchestration module in accordance with an embodiment of the present technology
- FIG. 4 is a diagram illustrating a network maintenance module in accordance with an embodiment of the present technology
- FIG. 6 is a diagram illustrating a first flowchart illustrating a computer-implemented method implementing embodiments of the present technology.
- FIG. 7 is a diagram illustrating a second flowchart illustrating a computer-implemented method implementing embodiments of the present technology.
- processor may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software.
- the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared.
- the processor may be a general purpose processor, such as a central processing unit (CPU) or a processor dedicated to a specific purpose, such as a digital signal processor (DSP).
- CPU central processing unit
- DSP digital signal processor
- processor should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read-only memory (ROM) for storing software, random access memory (RAM), and non-volatile storage. Other hardware, conventional and/or custom, may also be included.
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- ROM read-only memory
- RAM random access memory
- non-volatile storage non-volatile storage.
- Other hardware conventional and/or custom, may also be included.
- modules may be represented herein as any combination of flowchart elements or other elements indicating performance of process steps and/or textual description. Such modules may be executed by hardware that is expressly or implicitly shown. Moreover, it should be understood that module may include for example, but without being limitative, computer program logic, computer program instructions, software, stack, firmware, hardware circuitry or a combination thereof which provides the required capabilities.
- FIG. 1 illustrates a diagram of a computing environment 100 in accordance with an embodiment of the present technology is shown.
- the computing environment 100 may be implemented by any of a conventional personal computer, a computer dedicated to managing network resources, a network device and/or an electronic device (such as, but not limited to, a mobile device, a tablet device, a server, a controller unit, a control device, etc.) and/or any combination thereof appropriate to the relevant task at hand.
- the computing environment 100 comprises various hardware components including one or more single or multi-core processors collectively represented by a processor 110 , a solid-state drive 120 , a random access memory 130 and an input/output interface 150 .
- the computing environment 100 may be a computer specifically designed for managing network resources.
- the computing environment 100 may be a generic computer system.
- the computing environment 100 may also be a sub-system of one of the above-listed systems. In some other embodiments, the computing environment 100 may be an “off the shelf” generic computer system. In some embodiments, the computing environment 100 may also be distributed amongst multiple systems. The computing environment 100 may also be specifically dedicated to the implementation of the present technology. As a person in the art of the present technology may appreciate, multiple variations as to how the computing environment 100 is implemented may be envisioned without departing from the scope of the present technology.
- Communication between the various components of the computing environment 100 may be enabled by one or more internal and/or external buses 160 (e.g. a PCI bus, universal serial bus, IEEE 1394 “Firewire” bus, SCSI bus, Serial-ATA bus, ARINC bus, etc.), to which the various hardware components are electronically coupled.
- internal and/or external buses 160 e.g. a PCI bus, universal serial bus, IEEE 1394 “Firewire” bus, SCSI bus, Serial-ATA bus, ARINC bus, etc.
- the input/output interface 150 may allow enabling networking capabilities such as wire or wireless access.
- the input/output interface 150 may comprise a networking interface such as, but not limited to, a network port, a network socket, a network interface controller and the like. Multiple examples of how the networking interface may be implemented will become apparent to the person skilled in the art of the present technology.
- the networking interface may implement specific physical layer and data link layer standard such as Ethernet, Fibre Channel, Wi-Fi, Token Ring or Serial communication protocols.
- the specific physical layer and the data link layer may provide a base for a full network protocol stack, allowing communication among small groups of computers on the same local area network (LAN) and large-scale network communications through routable protocols, such as Internet Protocol (IP).
- IP Internet Protocol
- the solid-state drive 120 stores program instructions suitable for being loaded into the random access memory 130 and executed by the processor 110 for executing managing network resources.
- the program instructions may be part of a library or an application.
- the network service provider environment 200 comprises network resources 210 and a network resource management tool 220 .
- the network resource management tool 220 may monitor and/or control the network resources 210 via a communication channel, such as, the Internet and/or via an intranet implemented as part of the network architecture.
- the network resource management tool 220 may also access internal data and external data via the Internet and/or an intranet.
- the network resources 210 comprise network hardware resources 212 which may comprise, without being limitative, antennas, routers, storages, switches, servers, gateways and/or physical cabling (e.g., optic fiber lines, copper cables).
- the physical cabling may embody multi-frequency cables allowing additional wavelengths to be enabled as communication channels using specific paths to optimize capacity and/or resources in the “backhaul” network.
- the network resources 210 may also comprise a virtualization layer which is enabled by network virtual resources 212 .
- the network virtual resources 212 operate virtualized network functions such as, but not limited to, virtual compute resources, virtual storage resources and/or virtual communication channels.
- the virtualized network functions may comprise one or more virtual machines running different software and processes on top of the network hardware resources 214 .
- a virtual machine may be an operating system or application environment that is installed on software which imitates dedicated hardware.
- Specialized software also referred to as hypervisor may emulate a CPU, memory, hard disk, network and/or other hardware resources which allows the virtual machines to share the network hardware resources 214 .
- the virtualized network functions may be pre-defined functional behavior within a network, such as, but without being limitative, firewalling, domain name service (DNS), caching, network address translation (NAT), operating a proxy interface that may convert cellular packets (e.g., Access Point Name (APN) protocol) into IP packets, etc.
- DNS domain name service
- NAT network address translation
- Individual virtualized network functions may be linked or chained in a way similar to building blocks to offer a full-scale networking communication services (also referred to as network applications).
- the network resources 210 may support a plurality of network services which needs for network resources may vary in time and/or geography.
- the networking services may happen to be competing amongst one another for network resources.
- the network services may comprise services with different priority needs, such as, but without being limitative, speed, timeliness, accuracy and/or a combination thereof.
- network services may include, without being limitative, high throughput data consumer communications, low latency automotive connectivity (i.e., near real time connectivity), multiple heterogeneous connected devices. Other examples will become apparent to the person skilled in the art of the present technology.
- Each one of the network services may be associated with one or more Service Level Agreements (SLA) and service metrics.
- SLA Service Level Agreements
- SLA may be interpreted as a commitment between a network service provider and a service user.
- Particular aspects of the service—quality, service level, availability and/or responsibilities may be agreed upon between the network service provider and the service user.
- service metrics may be defined and monitored so as to measure one or more performances parameters of the network services and take measures regarding allocation of network resources.
- Such service metrics may comprise, without being limitative, a latency, available upload/download bandwidths, network uptimes, number of devices connected at a same time, etc. The service metrics therefore allows defining and monitoring a service level for a given network.
- the network resource management tool 220 may comprise a network management and orchestration module 222 , a network maintenance module 224 and a machine-learning module 226 associated with a training model database 228 .
- the network management and orchestration module 222 enables automation and provisional tasks relating to the network resources 210 .
- the tasks of orchestration may include configuration and execution of virtualized network functions so as to adapt the network hardware resources 214 and/or the network virtual resources 212 so as to properly support one or more network services (for example, so as to ensure that a given network service meets requirements of an associated SLA).
- the tasks of orchestration may include provisioning of virtual machines and application instances, security and compliance assessment, monitoring and/or reporting.
- the network management and orchestration module 222 may operate predictive auto-scaling to scale-up or scale-down the network resources 210 . In some embodiments, this may comprise scaling-up or scaling-down virtualized network functions enabling the network virtual resources 212 .
- the network management and orchestration module 222 may complement an existing management and orchestration tool operated by a network service provider so as to optimize, improve and/or adjust service delivery to customers. In some embodiments, such a balance may be determined in line with SLA and/or overall demand. As an example, but without being limitative, a network service may be scaled down to a minimum acceptable service on one end in order to supply acceptable network service on another end. The network management and orchestration module 222 may proactively (as opposed to reactively) adapt and shape capabilities of the network resources 210 (the network hardware resources 214 and/or the network virtual resources 212 ).
- the network management and orchestration module 222 may further allow delivering contextual, tailored network service levels by leveraging existing or future network infrastructures such as the network virtual resources 212 and/or the network hardware resources 214 .
- the network management and orchestration module 222 may operate as a supervision layer on top of existing network management tools.
- the network management and orchestration module 222 may monitor the one or more network services enabled by the network resource 210 .
- the network management and orchestration module 222 may predict network service degradation, for example, but without being limitative, due to external events (e.g., entertainment events, disaster, road traffic, weather conditions) and may adapt the network resources 210 accordingly.
- predictions of network service degradation may be based on external data processed by the machine-learning module 226 , as it will be further detailed in the subsequent paragraphs.
- Tasks executed by the network management and orchestration module 222 may be based on a pro-active and predictive basis resulting in a preventive (as opposed to curative) approach to management of network resources.
- the network management and orchestration module 222 may also be combined with self-healing, configuration and optimization solutions so as to create new instances of virtual devices or services to handle expected increases in network traffic, or disable a specific virtual or physical network resource, when imminent failure is expected. Operations of the network management and orchestration module 222 may allow improving network service customer experience while improving efficiency of the network resource usage by providing network resource usage optimization, anomaly detection, network operations management, detection of irregular operations and/or disaster recovery.
- the network maintenance module 224 may rely on the machine-learning module 226 and the internal data and/or external data to, at least partially, automate routing, planning, scheduling and/or execution of tasks to support operations of the network resources 210 .
- the network maintenance module 224 may execute maintenance operations in real-time.
- the network maintenance module 224 may leverage multiple data sources (e.g., internal data and/or external data) and/or manual processes (e.g., in person verification, scanning or photography of physical integrity of hardware infrastructure by maintenance staff) to enable systemic business operations and/or decision-making agent such as, but not limited to, predictive maintenance of the network resources 210 (e.g., so as to determine proactively if specific maintenance operations are required on certain network resources).
- the network maintenance module 224 comprise an image recognition module allowing to detect and/or predict cell tower and equipment corrosion rust or physical degradation.
- the network maintenance module 224 may adaptively and/or nimbly impact field operation maintenance activities by improving workforce scheduling, planning and/or dispatching fleets, at least partially, automatically based on internal data and/or external data (e.g., aggregated contextual customer complaints in a geographic area).
- the network maintenance module 224 may therefore allow improved management of assets such as, the network hardware resources 214 and improve their longevity. Further benefits may comprise improving network customer satisfaction, improved experience by accelerating ticket resolution, decreasing operational costs and/or time to repair network resources.
- the network maintenance module 224 may enable monitoring physical hardware components for failure, identifying quality of service or performance degradations, notifying system support teams of existing problems, scheduling reactive or proactive network maintenance, field workforce scheduling, disaster recovery (improved maintenance dispatching) and/or field troubleshooting support (contextual and/or dynamic). In some embodiments, the network maintenance module 224 may also enable management of activity related to irregular operation situations (IROPS).
- IOPS irregular operation situations
- the machine-learning module 226 may access, use and/or process external data, internal data and/or a training model database 228 as factors in a decision and/or inference process.
- the machine-learning module 226 may be part of the network management and orchestration module 222 and/or the network maintenance module 224 .
- the machine-learning module 226 may be a distinct and/or autonomous software component exchanging data with the network management and orchestration module 222 and/or the network maintenance module 224 via an interface, e.g., an Application Programming Interface (API).
- API Application Programming Interface
- the machine-learning module 226 may implement one or more machine-learning algorithm so as to leverage internal data and/or external data with existing training models from the training model database 228 .
- machine-learning algorithms implemented by the machine-learning module 228 may comprise, without being limitative, non-linear algorithm, linear regression, logistic regression, decision tree, support vector machine, na ⁇ ve bayes, K-nearest neighbors, K-means, random forest, dimensionality reduction, neural network, gradient boosting, adaboost, lasso, elastic net, ridge, bayesian ridge, Automatic Relevance Determination (ARD) regression, Stochastic Gradient Descent (SGD) regressor, passive aggressive regressor, k-neighbors regressor and/or Support Vector Regression (SVR).
- SGD Stochastic Gradient Descent
- SVR Support Vector Regression
- the training model database 228 may be implemented through database services such as, without being limitative, MySQL, PostgreSQL, MongoDB, MariaDB, Microsoft SQL Server, Oracle, Sybase, SAP HANA, MemSQL and/or IBM DB2.
- machine-learning module 226 may continuously run algorithm training instances so as to improve efficiency of algorithms for a given set of network resources.
- the network resource management tool 220 , the network management and orchestration module 222 , the network maintenance module 224 and/or the machine-learning module 226 may access internal data and/or external data.
- internal data may comprise data only accessible by the network service provider, created and compiled by the network service provider as a result of operating the network.
- external data may comprise data accessible from sources external to the network service provider and may exclude data relating to the operations of the network. Such external data are not directly related to the operations of the network. Both the internal data and the external data may be in structured or unstructured formats.
- Both the internal data and the external data may be stored in one or more databases and/or directly collected from various sources (either in real-time or at predefined intervals) such as, without being limitative, sensors, collectors and/or data feeds.
- internal data may be collected from central network resources and/or from resources distributed across the network (e.g., data collected at edges and/or nodes of the network).
- processing of the internal data may be centralised and/or decentralised (i.e., edge computing).
- the internal data may also relate to performances and/or configuration of network resources. Multiple approaches may therefore be envisioned as to how internal data an external data may be collected and/or compiled without departing from the scope of the present technology.
- the internal data may comprise, for example, but without being limitative, network data 232 , operations data 234 , customers data 236 and product data 238 .
- the network data 232 may comprise data generated as a result of operating the network, for example, but without being limitative, data collected from network probes (radio and core, transport and access), field measurements, geocoded live data from network devices and/or other data sources.
- the network data 232 may also comprise data collected from quality assurance tools, country-wide, regional and local supervision platforms and/or network management and monitoring tools available from vendors of network equipment.
- the operations data 234 may comprise business data resulting from business operations associated with the network, for example, but without being limitative, financial quarterly earnings, Capital Expenditure (CAPEX), market trends and/or other data sources.
- CRM Capital Expenditure
- the customers data 236 may comprise data relating to customer usage of the service. Such data may be anonymized before being further process by the network management tool 220 to ensure compliance with existing and future regulations relating to data privacy.
- the customers data 236 may comprise historical interactions, account details, social media and news feeds and/or other data sources.
- the customers data 236 may also comprise subscriber data and customer care/call center data.
- the customers data 236 may also comprise customer experience systems of records, such as, but without being limitative, Customer Relationship Management (CRM) tools, SLA compliance tools and/or contextual data (e.g., subscriber/customer historical experience profile).
- CRM Customer Relationship Management
- the subscriber data may comprise account details (plan, statements, payments, fees, roaming, customer segment, services), demographic and/or location.
- the customer care/call center data may comprise historical interactions, sentiment and/or device details and issues.
- collected data may be geotagged with a customer location at time of request for geographic optimization purposes. Collected data may be anonymized and/or aggregated so as to obfuscate individual information and ensure compliance with privacy regulations.
- the product data 238 may comprise, without being limitative, Product Offering Services (POS) data, device details and issues, location and/or other data sources.
- POS Product Offering Services
- the external data may comprise, for example, but without being limitative, environmental data 242 , regional data 244 , industry data 246 and/or financial data 248 .
- Environmental data 242 may comprise, as an example, but without being limitative, weather data, natural disaster information, geo-political information and/or seasonal trend information.
- Regional data 244 may comprise, as an example, but without being limitative data relating to traffic, local events (music, sports, festivals), public transportation and/or ad placement.
- the industry data 246 and the financial data 248 may comprise, as an example, but without being limitative, data relating to competitor information, partner information (e.g., roaming partnership and/or terms thereof), promotional, related product trends and information and/or cross-currency.
- FIG. 3 An exemplary embodiment of the network management and orchestration module 222 is exemplified in FIG. 3 .
- the network management and orchestration module 222 is configured to execute various steps of a method 300 allowing an improved delivery of network services while improving usage of network resources.
- the network management and orchestration module 222 causes to execute the machine-learning module 226 which may be part of the network management and orchestration module 222 or operate as a distinct software component (e.g., so as to operate for both the network management and orchestration module 222 and the network maintenance module 224 ).
- Multiple variations as to how and where the machine-learning module 226 may be implemented may therefore be envisioned without departing from the scope of the present technology.
- the network management and orchestration module 222 may determine an expected level of network services for the network or a portion of the network. As an example, determination may be made that multiple network services have to operate on the network and therefore share the network resources 210 . Each one of the network services may be associated with certain service metrics that establish network performances to be matched to ensure SLA compliance of each one of the network services. In some embodiments, the network management and orchestration module 222 may detect that a network service operate outside of normal reasonable historical parameters without a significant observable change in the overall architecture of the network.
- the network management and orchestration module 222 may access internal data and external data.
- a distinct software module may undertake to access the internal data and the external data.
- network service patterns are extracted based on the internal data, the external data and the expected level of network services.
- the step 330 may comprise determining a physical and/or organization of a network into groups (e.g., cells) where radio communication of a given cell is managed exclusively by one or multiple radio base stations.
- the network service pattern may be associated with one or more of a local area, a regional area and/or a country-wide area.
- the step 330 also comprises characterizing the network service patterns.
- characterizing the network service pattern allows augmenting the network service organization data with information relating to, for example, but without being limitative, performance and utilization of each cell and radio tower, and/or how such performance and utilization evolve over time.
- predictions of network service patterns and/or associated service level metrics may be generated, for example, by the machine-learning module 226 .
- the machine-learning module 226 may be trained with historical network service pattern data which enables prediction of imminent system or component failures (or degradation without failure) based on current network service pattern data.
- decision scenarios are established for network resources orchestration and one or more decision scenarios are selected.
- establishment and/or selection of decision scenarios may be based on correlations of the predicted network service patterns and availability of network resources.
- the correlations are identified and mapped on a graph.
- the availability of network resources may relate to computing power at the core and/or at the edge of the network, storage at a local base station/node, storage at a central network equipment and/or availability of frequency bands, channels and/or a number of active nodes per channel/band (i.e., concentration).
- step 360 network resources are allocated in accordance with the one or more selected decision scenarios, for example, by conducting orchestration tasks resulting in scaling-up certain virtual network functions and/or scaling down other virtual network functions.
- the selected decision scenarios is not limited to adapting the network to one network service in particular but rather establish an holistic decision scenario allowing to implement appropriate arbitration between network services running in parallel and competing to share the same network resources.
- step 360 may comprise re-arranging a layout of the network. As an example, in a wireless network wherein overlaps exist, it may be envisioned to tune down a tower and tune up another tower thereby changing a covered area/population on the fly so as to distribute resources more evenly.
- a loop back mechanism may execute monitoring customer experience, network performance and/or network service level and influence modifications of a decision scenario which in turn results in further adapting the network resources so as to base orchestration of the network resources both on predictions and actual/real-life feedback.
- the step 370 may further comprise monitoring customer experience, network performance and/or network service level so as to detect abnormal or unusual network behaviour and customer experience.
- the monitored customer experience, network performance and/or network service level are fed to the machine-learning module 226 so as to reinforce the one or more trained models based on actual/real-life responses to network resources rebalancing operations.
- the method 300 may also be used to anticipate network service disruptions (or significant changes in concentration distribution across the network resources) and adapt the network resources accordingly.
- FIG. 4 An exemplary embodiment of the network maintenance module 224 is exemplified in FIG. 4 .
- the network maintenance module 224 is configured to execute various steps of a method 400 allowing automating, at least partially, routing, planning, scheduling and/or execution of tasks to support operations of network resources.
- the network maintenance module 224 causes to execute the machine-learning module 226 which may be part of the network maintenance module 224 or operate as a distinct software component (e.g., so as to operate for both the network management and orchestration module 222 and the network maintenance module 224 ). Multiple variations as to how and where the machine-learning module 226 may be therefore envisioned without departing from the scope of the present technology.
- the network maintenance module 224 may access internal data and external data. In some embodiments, a distinct software module may undertake to access the internal data and the external data.
- the network maintenance module 224 based on the internal data and the external data, generate maintenance actions relating to the network resources.
- the maintenance workforce scheduling and planning of maintenance actions may be generated and executed.
- the machine-learning module 226 is configured to execute various steps of a method 500 allowing generating network service patterns. As internal data and external data are being collected and processed by the machine-learning module 226 , the machine-learning module 226 may start generating one or more predictions of network service patterns. In some embodiments, the machine-learning module 226 may take the form of an API. The API may be hosted by a system operating the network resource management tool 220 or may be hosted by a dedicated service platform accessible by the network resource management tool 220 . At a step 510 , the machine-learning module 226 may execute profiling of network service patterns which may be used to reinforce algorithm training instances stored in the training model database 228 .
- FIG. 6 a flowchart illustrating a computer-implemented method 600 of executing a method for managing network resources enabling network services over a network is illustrated.
- the computer-implemented method 600 may be (completely or partially) implemented on a computing environment similar to the computing environment 100 , such as, but not limited to, a system operating the network management and orchestration module 222 .
- the method 600 comprises executing, at a step 602 , generating an expected performance level of the network services. Then, at a step 604 , the method 600 executes accessing internal data relating to operations of the network and external data not relating to operations of the network.
- the method 600 executes generating a prediction of a network service pattern based on the expected performance level of the network services, the internal data and the external data. Then, at a step 608 , the method 600 executes identifying a decision scenario for orchestration of the network resources, the decision scenario establishing a configuration of the network resources, the decision scenario being generated based on a correlation of the prediction of the network service pattern and availability of the network resources. At a step 610 , the method 600 then executes causing to adapt the network resources based on the decision scenario.
- the method 600 may further execute monitoring at least one of a customer experience, a network performance and/or the performance level of the network services and causing to modify the decision scenario based on the at least one of the customer experience, the network performance and/or the performance level of the network services.
- FIG. 7 a flowchart illustrating a computer-implemented method 700 of executing a method for managing maintenance of network resources is illustrated.
- the computer-implemented method 700 may be (completely or partially) implemented on a computing environment similar to the computing environment 100 , such as, but not limited to, a system operating the network maintenance module 224 .
- the method 700 comprises executing, at a step 702 , accessing internal data relating to operations of the network and external data not relating to operations of the network. Then, at a step 704 , the method 700 executes generating maintenance actions to be conducted on the network resources based on the internal data and the external data. At a step 706 , the method 700 executes generating planning of the maintenance actions.
Abstract
Description
- The present application claims convention priority to U.S. Provisional Patent Application No. 62/738,685, filed Sep. 28, 2018, entitled “SYSTEM AND METHOD FOR MANAGING NETWORK RESOURCES” which is incorporated by reference herein in its entirety.
- The present technology relates to systems and methods for managing network resources. In particular, the systems and methods allow network resource orchestration and/or network resource maintenance.
- Network service providers typically implement and manage physical network architecture components (i.e., network hardware resources) to deploy network functions. Such network hardware resources may comprise, without being limitative, antennas, routers, storages, switches, servers, gateways. The network hardware resources typically operate in accordance with one or more protocols so as to ensure proper communication amongst the network hardware resources. Network functions are traditionally deployed as physical devices running software components that are tightly coupled to the physical devices. Such approach to network functions creates operational challenges as manual interventions are often required to upscale or downscale network resources thereby preventing fast deployment of new network functions.
- In order to address at least some of these issues, network service providers have turned to network virtual resources allowing operating virtualized network functions decoupled for the underlying hardware. The network virtual resources may rely on one or more virtual machines running software on top the physical network architecture as opposed to requiring dedicated network hardware devices for each network functions. As a result, if determination is made that additional network resources are required in an area and/or at a given moment in time, new network resources may be rapidly deployed with no or little manual interventions. As an example, an orchestration layer may deploy one or more virtual machines to add capacity to the network.
- Increase and/or decrease in network resource capacity is often reactive in nature and contingent upon arriving at some trigger point (e.g., a measurement that a network resource operates beyond its limits, loss of network functionality in part or whole). Such reactive increase and/or decrease in network resource capacity may present challenges in rendering optimal network service delivery, in particular in contexts wherein the network resources support a plurality of network applications (e.g., high throughput data consumer communications, low latency automotive connectivity, multiple heterogeneous connected devices) in dynamic time varying environments.
- Therefore, even though the recent developments identified above may provide benefits, improvements are still desirable.
- The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches.
- Embodiments of the present technology have been developed based on developers' appreciation of shortcomings associated with the prior art.
- In particular, such shortcomings may comprise (1) a reactive approach to increase and/or decrease in network resource capacity deployment, as opposed to a proactive approach; and (2) silos between various data sources based on which increase and/or decrease in network resource capacity deployment may be determined, thereby limiting an ability to implement a proactive approach.
- In one aspect, various implementations of the present technology provide a method for managing network resources enabling network services over a network, the method comprising:
-
- generating an expected performance level of the network services;
- accessing internal data relating to operations of the network and external data not relating to operations of the network;
- generating a prediction of a network service pattern based on the expected performance level of the network services, the internal data and the external data;
- identifying a decision scenario for orchestration of the network resources, the decision scenario establishing a configuration of the network resources, the decision scenario being generated based on a correlation of the prediction of the network service pattern and availability of the network resources; and
- causing to adapt the network resources based on the decision scenario.
- In other aspects, various implementations of the present technology provide a method for managing maintenance of network resources, the method comprising:
-
- accessing internal data relating to operations of the network and external data not relating to operations of the network;
- generating maintenance actions to be conducted on the network resources based on the internal data and the external data; and
- generating planning of the maintenance actions.
- In other aspects, various implementations of the present technology provide a non-transitory computer-readable medium storing program instructions for executing methods of managing network resources, the program instructions being executable by a processor of a computer-based system to carry out one or more of the above-recited methods.
- In other aspects, various implementations of the present technology provide a computer-based system, such as, for example, but without being limitative, an electronic device comprising at least one processor and a memory storing program instructions for executing methods of managing network resources, the program instructions being executable by the at least one processor of the electronic device to carry out one or more of the above-recited methods.
- In the context of the present specification, unless expressly provided otherwise, a computer system may refer, but is not limited to, an “electronic device”, an “operation system”, a “system”, a “computer-based system”, a “network system”, a “network device”, a “controller unit”, a “monitoring device”, a “control device” and/or any combination thereof appropriate to the relevant task at hand.
- In the context of the present specification, unless expressly provided otherwise, the expression “computer-readable medium” and “memory” are intended to include media of any nature and kind whatsoever, non-limiting examples of which include RAM, ROM, disks (CD-ROMs, DVDs, floppy disks, hard disk drives, etc.), USB keys, flash memory cards, solid state-drives, and tape drives. Still in the context of the present specification, “a” computer-readable medium and “the” computer-readable medium should not be construed as being the same computer-readable medium. To the contrary, and whenever appropriate, “a” computer-readable medium and “the” computer-readable medium may also be construed as a first computer-readable medium and a second computer-readable medium.
- In the context of the present specification, unless expressly provided otherwise, the words “first”, “second”, “third”, etc. have been used as adjectives only for the purpose of allowing for distinction between the nouns that they modify from one another, and not for the purpose of describing any particular relationship between those nouns.
- Implementations of the present technology each have at least one of the above-mentioned objects and/or aspects, but do not necessarily have all of them. It should be understood that some aspects of the present technology that have resulted from attempting to attain the above-mentioned object may not satisfy this object and/or may satisfy other objects not specifically recited herein.
- Additional and/or alternative features, aspects and advantages of implementations of the present technology will become apparent from the following description, the accompanying drawings and the appended claims.
- For a better understanding of the present technology, as well as other aspects and further features thereof, reference is made to the following description which is to be used in conjunction with the accompanying drawings, where:
-
FIG. 1 is a diagram of a computing environment in accordance with an embodiment of the present technology; -
FIG. 2 is a diagram of a network service provider environment in accordance with an embodiment of the present technology; -
FIG. 3 is a diagram illustrating a network management and orchestration module in accordance with an embodiment of the present technology; -
FIG. 4 is a diagram illustrating a network maintenance module in accordance with an embodiment of the present technology; -
FIG. 5 is a diagram illustrating a machine-learning module in accordance with an embodiment of the present technology; -
FIG. 6 is a diagram illustrating a first flowchart illustrating a computer-implemented method implementing embodiments of the present technology; and -
FIG. 7 is a diagram illustrating a second flowchart illustrating a computer-implemented method implementing embodiments of the present technology. - It should also be noted that, unless otherwise explicitly specified herein, the drawings are not to scale.
- The examples and conditional language recited herein are principally intended to aid the reader in understanding the principles of the present technology and not to limit its scope to such specifically recited examples and conditions. It will be appreciated that those skilled in the art may devise various arrangements which, although not explicitly described or shown herein, nonetheless embody the principles of the present technology and are included within its spirit and scope.
- Furthermore, as an aid to understanding, the following description may describe relatively simplified implementations of the present technology. As persons skilled in the art would understand, various implementations of the present technology may be of a greater complexity.
- In some cases, what are believed to be helpful examples of modifications to the present technology may also be set forth. This is done merely as an aid to understanding, and, again, not to define the scope or set forth the bounds of the present technology. These modifications are not an exhaustive list, and a person skilled in the art may make other modifications while nonetheless remaining within the scope of the present technology. Further, where no examples of modifications have been set forth, it should not be interpreted that no modifications are possible and/or that what is described is the sole manner of implementing that element of the present technology.
- Moreover, all statements herein reciting principles, aspects, and implementations of the present technology, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof, whether they are currently known or developed in the future. Thus, for example, it will be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative circuitry embodying the principles of the present technology. Similarly, it will be appreciated that any flowcharts, flow diagrams, state transition diagrams, pseudo-code, and the like represent various processes which may be substantially represented in computer-readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
- The functions of the various elements shown in the figures, including any functional block labeled as a “processor”, may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. In some embodiments of the present technology, the processor may be a general purpose processor, such as a central processing unit (CPU) or a processor dedicated to a specific purpose, such as a digital signal processor (DSP). Moreover, explicit use of the term a “processor” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read-only memory (ROM) for storing software, random access memory (RAM), and non-volatile storage. Other hardware, conventional and/or custom, may also be included.
- Software modules, or simply modules which are implied to be software, may be represented herein as any combination of flowchart elements or other elements indicating performance of process steps and/or textual description. Such modules may be executed by hardware that is expressly or implicitly shown. Moreover, it should be understood that module may include for example, but without being limitative, computer program logic, computer program instructions, software, stack, firmware, hardware circuitry or a combination thereof which provides the required capabilities.
- With these fundamentals in place, we will now consider some non-limiting examples to illustrate various implementations of aspects of the present technology.
-
FIG. 1 illustrates a diagram of acomputing environment 100 in accordance with an embodiment of the present technology is shown. In some embodiments, thecomputing environment 100 may be implemented by any of a conventional personal computer, a computer dedicated to managing network resources, a network device and/or an electronic device (such as, but not limited to, a mobile device, a tablet device, a server, a controller unit, a control device, etc.) and/or any combination thereof appropriate to the relevant task at hand. In some embodiments, thecomputing environment 100 comprises various hardware components including one or more single or multi-core processors collectively represented by aprocessor 110, a solid-state drive 120, arandom access memory 130 and an input/output interface 150. Thecomputing environment 100 may be a computer specifically designed for managing network resources. In some alternative embodiments, thecomputing environment 100 may be a generic computer system. - In some embodiments, the
computing environment 100 may also be a sub-system of one of the above-listed systems. In some other embodiments, thecomputing environment 100 may be an “off the shelf” generic computer system. In some embodiments, thecomputing environment 100 may also be distributed amongst multiple systems. Thecomputing environment 100 may also be specifically dedicated to the implementation of the present technology. As a person in the art of the present technology may appreciate, multiple variations as to how thecomputing environment 100 is implemented may be envisioned without departing from the scope of the present technology. - Communication between the various components of the
computing environment 100 may be enabled by one or more internal and/or external buses 160 (e.g. a PCI bus, universal serial bus, IEEE 1394 “Firewire” bus, SCSI bus, Serial-ATA bus, ARINC bus, etc.), to which the various hardware components are electronically coupled. - The input/
output interface 150 may allow enabling networking capabilities such as wire or wireless access. As an example, the input/output interface 150 may comprise a networking interface such as, but not limited to, a network port, a network socket, a network interface controller and the like. Multiple examples of how the networking interface may be implemented will become apparent to the person skilled in the art of the present technology. For example, but without being limitative, the networking interface may implement specific physical layer and data link layer standard such as Ethernet, Fibre Channel, Wi-Fi, Token Ring or Serial communication protocols. The specific physical layer and the data link layer may provide a base for a full network protocol stack, allowing communication among small groups of computers on the same local area network (LAN) and large-scale network communications through routable protocols, such as Internet Protocol (IP). - According to implementations of the present technology, the solid-
state drive 120 stores program instructions suitable for being loaded into therandom access memory 130 and executed by theprocessor 110 for executing managing network resources. For example, the program instructions may be part of a library or an application. - Referring to
FIG. 2 , a networkservice provider environment 200 is depicted. The networkservice provider environment 200 comprisesnetwork resources 210 and a networkresource management tool 220. The networkresource management tool 220 may monitor and/or control thenetwork resources 210 via a communication channel, such as, the Internet and/or via an intranet implemented as part of the network architecture. The networkresource management tool 220 may also access internal data and external data via the Internet and/or an intranet. - In some embodiments, the
network resources 210 comprisenetwork hardware resources 212 which may comprise, without being limitative, antennas, routers, storages, switches, servers, gateways and/or physical cabling (e.g., optic fiber lines, copper cables). In some embodiments, the physical cabling may embody multi-frequency cables allowing additional wavelengths to be enabled as communication channels using specific paths to optimize capacity and/or resources in the “backhaul” network. Thenetwork resources 210 may also comprise a virtualization layer which is enabled by networkvirtual resources 212. The networkvirtual resources 212 operate virtualized network functions such as, but not limited to, virtual compute resources, virtual storage resources and/or virtual communication channels. The virtualized network functions may comprise one or more virtual machines running different software and processes on top of thenetwork hardware resources 214. A virtual machine may be an operating system or application environment that is installed on software which imitates dedicated hardware. Specialized software, also referred to as hypervisor may emulate a CPU, memory, hard disk, network and/or other hardware resources which allows the virtual machines to share thenetwork hardware resources 214. In some embodiments, the virtualized network functions may be pre-defined functional behavior within a network, such as, but without being limitative, firewalling, domain name service (DNS), caching, network address translation (NAT), operating a proxy interface that may convert cellular packets (e.g., Access Point Name (APN) protocol) into IP packets, etc. Individual virtualized network functions may be linked or chained in a way similar to building blocks to offer a full-scale networking communication services (also referred to as network applications). - In some embodiments, the
network resources 210 may support a plurality of network services which needs for network resources may vary in time and/or geography. The networking services may happen to be competing amongst one another for network resources. The network services may comprise services with different priority needs, such as, but without being limitative, speed, timeliness, accuracy and/or a combination thereof. For example, network services may include, without being limitative, high throughput data consumer communications, low latency automotive connectivity (i.e., near real time connectivity), multiple heterogeneous connected devices. Other examples will become apparent to the person skilled in the art of the present technology. Each one of the network services may be associated with one or more Service Level Agreements (SLA) and service metrics. SLA may be interpreted as a commitment between a network service provider and a service user. Particular aspects of the service—quality, service level, availability and/or responsibilities may be agreed upon between the network service provider and the service user. In order to implement such agreement, service metrics may be defined and monitored so as to measure one or more performances parameters of the network services and take measures regarding allocation of network resources. Such service metrics may comprise, without being limitative, a latency, available upload/download bandwidths, network uptimes, number of devices connected at a same time, etc. The service metrics therefore allows defining and monitoring a service level for a given network. - In some embodiments, the network
resource management tool 220 may comprise a network management andorchestration module 222, anetwork maintenance module 224 and a machine-learningmodule 226 associated with atraining model database 228. In some embodiments, the network management andorchestration module 222 enables automation and provisional tasks relating to thenetwork resources 210. The tasks of orchestration may include configuration and execution of virtualized network functions so as to adapt thenetwork hardware resources 214 and/or the networkvirtual resources 212 so as to properly support one or more network services (for example, so as to ensure that a given network service meets requirements of an associated SLA). In some embodiments, the tasks of orchestration may include provisioning of virtual machines and application instances, security and compliance assessment, monitoring and/or reporting. As further detailed in connection with the description ofFIG. 3 , the network management andorchestration module 222 may operate predictive auto-scaling to scale-up or scale-down thenetwork resources 210. In some embodiments, this may comprise scaling-up or scaling-down virtualized network functions enabling the networkvirtual resources 212. - In some embodiments, the network management and
orchestration module 222 may complement an existing management and orchestration tool operated by a network service provider so as to optimize, improve and/or adjust service delivery to customers. In some embodiments, such a balance may be determined in line with SLA and/or overall demand. As an example, but without being limitative, a network service may be scaled down to a minimum acceptable service on one end in order to supply acceptable network service on another end. The network management andorchestration module 222 may proactively (as opposed to reactively) adapt and shape capabilities of the network resources 210 (thenetwork hardware resources 214 and/or the network virtual resources 212). The network management andorchestration module 222 may further allow delivering contextual, tailored network service levels by leveraging existing or future network infrastructures such as the networkvirtual resources 212 and/or thenetwork hardware resources 214. In some embodiments, the network management andorchestration module 222 may operate as a supervision layer on top of existing network management tools. In some embodiments, the network management andorchestration module 222 may monitor the one or more network services enabled by thenetwork resource 210. The network management andorchestration module 222 may predict network service degradation, for example, but without being limitative, due to external events (e.g., entertainment events, disaster, road traffic, weather conditions) and may adapt thenetwork resources 210 accordingly. In some embodiments, predictions of network service degradation may be based on external data processed by the machine-learningmodule 226, as it will be further detailed in the subsequent paragraphs. Tasks executed by the network management andorchestration module 222 may be based on a pro-active and predictive basis resulting in a preventive (as opposed to curative) approach to management of network resources. In some embodiments, the network management andorchestration module 222 may also be combined with self-healing, configuration and optimization solutions so as to create new instances of virtual devices or services to handle expected increases in network traffic, or disable a specific virtual or physical network resource, when imminent failure is expected. Operations of the network management andorchestration module 222 may allow improving network service customer experience while improving efficiency of the network resource usage by providing network resource usage optimization, anomaly detection, network operations management, detection of irregular operations and/or disaster recovery. - In some embodiments, the
network maintenance module 224 may rely on the machine-learningmodule 226 and the internal data and/or external data to, at least partially, automate routing, planning, scheduling and/or execution of tasks to support operations of thenetwork resources 210. In some embodiments, thenetwork maintenance module 224 may execute maintenance operations in real-time. In some embodiments, thenetwork maintenance module 224 may leverage multiple data sources (e.g., internal data and/or external data) and/or manual processes (e.g., in person verification, scanning or photography of physical integrity of hardware infrastructure by maintenance staff) to enable systemic business operations and/or decision-making agent such as, but not limited to, predictive maintenance of the network resources 210 (e.g., so as to determine proactively if specific maintenance operations are required on certain network resources). In some embodiments, thenetwork maintenance module 224 comprise an image recognition module allowing to detect and/or predict cell tower and equipment corrosion rust or physical degradation. In some embodiments, thenetwork maintenance module 224 may adaptively and/or nimbly impact field operation maintenance activities by improving workforce scheduling, planning and/or dispatching fleets, at least partially, automatically based on internal data and/or external data (e.g., aggregated contextual customer complaints in a geographic area). Thenetwork maintenance module 224 may therefore allow improved management of assets such as, thenetwork hardware resources 214 and improve their longevity. Further benefits may comprise improving network customer satisfaction, improved experience by accelerating ticket resolution, decreasing operational costs and/or time to repair network resources. In some embodiments, thenetwork maintenance module 224 may enable monitoring physical hardware components for failure, identifying quality of service or performance degradations, notifying system support teams of existing problems, scheduling reactive or proactive network maintenance, field workforce scheduling, disaster recovery (improved maintenance dispatching) and/or field troubleshooting support (contextual and/or dynamic). In some embodiments, thenetwork maintenance module 224 may also enable management of activity related to irregular operation situations (IROPS). - In some embodiments, the machine-learning
module 226 may access, use and/or process external data, internal data and/or atraining model database 228 as factors in a decision and/or inference process. In some embodiments, the machine-learningmodule 226 may be part of the network management andorchestration module 222 and/or thenetwork maintenance module 224. In alternative embodiments, the machine-learningmodule 226 may be a distinct and/or autonomous software component exchanging data with the network management andorchestration module 222 and/or thenetwork maintenance module 224 via an interface, e.g., an Application Programming Interface (API). In some embodiments, the machine-learningmodule 226 may implement one or more machine-learning algorithm so as to leverage internal data and/or external data with existing training models from thetraining model database 228. Examples of machine-learning algorithms implemented by the machine-learningmodule 228 may comprise, without being limitative, non-linear algorithm, linear regression, logistic regression, decision tree, support vector machine, naïve bayes, K-nearest neighbors, K-means, random forest, dimensionality reduction, neural network, gradient boosting, adaboost, lasso, elastic net, ridge, bayesian ridge, Automatic Relevance Determination (ARD) regression, Stochastic Gradient Descent (SGD) regressor, passive aggressive regressor, k-neighbors regressor and/or Support Vector Regression (SVR). In some embodiments, thetraining model database 228 may be implemented through database services such as, without being limitative, MySQL, PostgreSQL, MongoDB, MariaDB, Microsoft SQL Server, Oracle, Sybase, SAP HANA, MemSQL and/or IBM DB2. In some embodiments, machine-learningmodule 226 may continuously run algorithm training instances so as to improve efficiency of algorithms for a given set of network resources. - As previously explained, the network
resource management tool 220, the network management andorchestration module 222, thenetwork maintenance module 224 and/or the machine-learningmodule 226 may access internal data and/or external data. In some embodiments, internal data may comprise data only accessible by the network service provider, created and compiled by the network service provider as a result of operating the network. In contrast, external data may comprise data accessible from sources external to the network service provider and may exclude data relating to the operations of the network. Such external data are not directly related to the operations of the network. Both the internal data and the external data may be in structured or unstructured formats. Both the internal data and the external data may be stored in one or more databases and/or directly collected from various sources (either in real-time or at predefined intervals) such as, without being limitative, sensors, collectors and/or data feeds. In some embodiments, internal data may be collected from central network resources and/or from resources distributed across the network (e.g., data collected at edges and/or nodes of the network). In some embodiments, processing of the internal data may be centralised and/or decentralised (i.e., edge computing). In some embodiments, the internal data may also relate to performances and/or configuration of network resources. Multiple approaches may therefore be envisioned as to how internal data an external data may be collected and/or compiled without departing from the scope of the present technology. - In some embodiments, the internal data may comprise, for example, but without being limitative,
network data 232, operations data 234, customers data 236 andproduct data 238. Thenetwork data 232 may comprise data generated as a result of operating the network, for example, but without being limitative, data collected from network probes (radio and core, transport and access), field measurements, geocoded live data from network devices and/or other data sources. Thenetwork data 232 may also comprise data collected from quality assurance tools, country-wide, regional and local supervision platforms and/or network management and monitoring tools available from vendors of network equipment. - The operations data 234 may comprise business data resulting from business operations associated with the network, for example, but without being limitative, financial quarterly earnings, Capital Expenditure (CAPEX), market trends and/or other data sources.
- The customers data 236 may comprise data relating to customer usage of the service. Such data may be anonymized before being further process by the
network management tool 220 to ensure compliance with existing and future regulations relating to data privacy. As an example, but without being limitative, the customers data 236 may comprise historical interactions, account details, social media and news feeds and/or other data sources. In some embodiments, the customers data 236 may also comprise subscriber data and customer care/call center data. In some embodiments, the customers data 236 may also comprise customer experience systems of records, such as, but without being limitative, Customer Relationship Management (CRM) tools, SLA compliance tools and/or contextual data (e.g., subscriber/customer historical experience profile). As an example, but without being limitative, the subscriber data may comprise account details (plan, statements, payments, fees, roaming, customer segment, services), demographic and/or location. As an example, but without being limitative, the customer care/call center data may comprise historical interactions, sentiment and/or device details and issues. In some embodiments, collected data may be geotagged with a customer location at time of request for geographic optimization purposes. Collected data may be anonymized and/or aggregated so as to obfuscate individual information and ensure compliance with privacy regulations. - The
product data 238 may comprise, without being limitative, Product Offering Services (POS) data, device details and issues, location and/or other data sources. - In some embodiments, the external data may comprise, for example, but without being limitative,
environmental data 242,regional data 244,industry data 246 and/orfinancial data 248.Environmental data 242 may comprise, as an example, but without being limitative, weather data, natural disaster information, geo-political information and/or seasonal trend information.Regional data 244 may comprise, as an example, but without being limitative data relating to traffic, local events (music, sports, festivals), public transportation and/or ad placement. Theindustry data 246 and thefinancial data 248 may comprise, as an example, but without being limitative, data relating to competitor information, partner information (e.g., roaming partnership and/or terms thereof), promotional, related product trends and information and/or cross-currency. - An exemplary embodiment of the network management and
orchestration module 222 is exemplified inFIG. 3 . In this embodiment, the network management andorchestration module 222 is configured to execute various steps of amethod 300 allowing an improved delivery of network services while improving usage of network resources. In some embodiments, the network management andorchestration module 222 causes to execute the machine-learningmodule 226 which may be part of the network management andorchestration module 222 or operate as a distinct software component (e.g., so as to operate for both the network management andorchestration module 222 and the network maintenance module 224). Multiple variations as to how and where the machine-learningmodule 226 may be implemented may therefore be envisioned without departing from the scope of the present technology. - At a
step 310, the network management andorchestration module 222 may determine an expected level of network services for the network or a portion of the network. As an example, determination may be made that multiple network services have to operate on the network and therefore share thenetwork resources 210. Each one of the network services may be associated with certain service metrics that establish network performances to be matched to ensure SLA compliance of each one of the network services. In some embodiments, the network management andorchestration module 222 may detect that a network service operate outside of normal reasonable historical parameters without a significant observable change in the overall architecture of the network. - At a
step 320, the network management andorchestration module 222 may access internal data and external data. In some embodiments, a distinct software module may undertake to access the internal data and the external data. At astep 330, network service patterns are extracted based on the internal data, the external data and the expected level of network services. In some embodiments, thestep 330 may comprise determining a physical and/or organization of a network into groups (e.g., cells) where radio communication of a given cell is managed exclusively by one or multiple radio base stations. In some embodiments, the network service pattern may be associated with one or more of a local area, a regional area and/or a country-wide area. In some embodiments, thestep 330 also comprises characterizing the network service patterns. In some embodiments, characterizing the network service pattern allows augmenting the network service organization data with information relating to, for example, but without being limitative, performance and utilization of each cell and radio tower, and/or how such performance and utilization evolve over time. - At a
step 340, predictions of network service patterns and/or associated service level metrics may be generated, for example, by the machine-learningmodule 226. In some embodiments, the machine-learningmodule 226 may be trained with historical network service pattern data which enables prediction of imminent system or component failures (or degradation without failure) based on current network service pattern data. - At a
step 350, decision scenarios are established for network resources orchestration and one or more decision scenarios are selected. In some embodiments, establishment and/or selection of decision scenarios may be based on correlations of the predicted network service patterns and availability of network resources. In some embodiments, the correlations are identified and mapped on a graph. In some embodiments, the availability of network resources may relate to computing power at the core and/or at the edge of the network, storage at a local base station/node, storage at a central network equipment and/or availability of frequency bands, channels and/or a number of active nodes per channel/band (i.e., concentration). - At a
step 360, network resources are allocated in accordance with the one or more selected decision scenarios, for example, by conducting orchestration tasks resulting in scaling-up certain virtual network functions and/or scaling down other virtual network functions. In some embodiments, the selected decision scenarios is not limited to adapting the network to one network service in particular but rather establish an holistic decision scenario allowing to implement appropriate arbitration between network services running in parallel and competing to share the same network resources. In some embodiments,step 360 may comprise re-arranging a layout of the network. As an example, in a wireless network wherein overlaps exist, it may be envisioned to tune down a tower and tune up another tower thereby changing a covered area/population on the fly so as to distribute resources more evenly. - At a
step 370, a loop back mechanism may execute monitoring customer experience, network performance and/or network service level and influence modifications of a decision scenario which in turn results in further adapting the network resources so as to base orchestration of the network resources both on predictions and actual/real-life feedback. In some embodiments, thestep 370 may further comprise monitoring customer experience, network performance and/or network service level so as to detect abnormal or unusual network behaviour and customer experience. In some embodiments, the monitored customer experience, network performance and/or network service level are fed to the machine-learningmodule 226 so as to reinforce the one or more trained models based on actual/real-life responses to network resources rebalancing operations. - In some embodiments, the
method 300 may also be used to anticipate network service disruptions (or significant changes in concentration distribution across the network resources) and adapt the network resources accordingly. - An exemplary embodiment of the
network maintenance module 224 is exemplified inFIG. 4 . In this embodiment, thenetwork maintenance module 224 is configured to execute various steps of amethod 400 allowing automating, at least partially, routing, planning, scheduling and/or execution of tasks to support operations of network resources. In some embodiments, thenetwork maintenance module 224 causes to execute the machine-learningmodule 226 which may be part of thenetwork maintenance module 224 or operate as a distinct software component (e.g., so as to operate for both the network management andorchestration module 222 and the network maintenance module 224). Multiple variations as to how and where the machine-learningmodule 226 may be therefore envisioned without departing from the scope of the present technology. - At a
step 410, thenetwork maintenance module 224 may access internal data and external data. In some embodiments, a distinct software module may undertake to access the internal data and the external data. At astep 420, thenetwork maintenance module 224, based on the internal data and the external data, generate maintenance actions relating to the network resources. At astep 430, the maintenance workforce scheduling and planning of maintenance actions may be generated and executed. - An exemplary embodiment of the machine-learning
module 226 is exemplified inFIG. 5 . In this embodiment, the machine-learningmodule 226 is configured to execute various steps of amethod 500 allowing generating network service patterns. As internal data and external data are being collected and processed by the machine-learningmodule 226, the machine-learningmodule 226 may start generating one or more predictions of network service patterns. In some embodiments, the machine-learningmodule 226 may take the form of an API. The API may be hosted by a system operating the networkresource management tool 220 or may be hosted by a dedicated service platform accessible by the networkresource management tool 220. At astep 510, the machine-learningmodule 226 may execute profiling of network service patterns which may be used to reinforce algorithm training instances stored in thetraining model database 228. - Turning now to
FIG. 6 , a flowchart illustrating a computer-implementedmethod 600 of executing a method for managing network resources enabling network services over a network is illustrated. In some embodiments, the computer-implementedmethod 600 may be (completely or partially) implemented on a computing environment similar to thecomputing environment 100, such as, but not limited to, a system operating the network management andorchestration module 222. - The
method 600 comprises executing, at astep 602, generating an expected performance level of the network services. Then, at astep 604, themethod 600 executes accessing internal data relating to operations of the network and external data not relating to operations of the network. - At a
step 606, themethod 600 executes generating a prediction of a network service pattern based on the expected performance level of the network services, the internal data and the external data. Then, at astep 608, themethod 600 executes identifying a decision scenario for orchestration of the network resources, the decision scenario establishing a configuration of the network resources, the decision scenario being generated based on a correlation of the prediction of the network service pattern and availability of the network resources. At astep 610, themethod 600 then executes causing to adapt the network resources based on the decision scenario. - In some embodiments, the
method 600 may further execute monitoring at least one of a customer experience, a network performance and/or the performance level of the network services and causing to modify the decision scenario based on the at least one of the customer experience, the network performance and/or the performance level of the network services. - Turning now to
FIG. 7 , a flowchart illustrating a computer-implementedmethod 700 of executing a method for managing maintenance of network resources is illustrated. In some embodiments, the computer-implementedmethod 700 may be (completely or partially) implemented on a computing environment similar to thecomputing environment 100, such as, but not limited to, a system operating thenetwork maintenance module 224. - The
method 700 comprises executing, at astep 702, accessing internal data relating to operations of the network and external data not relating to operations of the network. Then, at astep 704, themethod 700 executes generating maintenance actions to be conducted on the network resources based on the internal data and the external data. At astep 706, themethod 700 executes generating planning of the maintenance actions. - While the above-described implementations have been described and shown with reference to particular steps performed in a particular order, it will be understood that these steps may be combined, sub-divided, or re-ordered without departing from the teachings of the present technology. At least some of the steps may be executed in parallel or in series. Accordingly, the order and grouping of the steps is not a limitation of the present technology.
- It should be expressly understood that not all technical effects mentioned herein need to be enjoyed in each and every embodiment of the present technology.
- Modifications and improvements to the above-described implementations of the present technology may become apparent to those skilled in the art. The foregoing description is intended to be exemplary rather than limiting. The scope of the present technology is therefore intended to be limited solely by the scope of the appended claims.
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/585,585 US20200106714A1 (en) | 2018-09-28 | 2019-09-27 | System and method for managing network resources |
US17/673,591 US11855909B2 (en) | 2018-09-28 | 2022-02-16 | System and method for managing network resources |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862738685P | 2018-09-28 | 2018-09-28 | |
US16/585,585 US20200106714A1 (en) | 2018-09-28 | 2019-09-27 | System and method for managing network resources |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/673,591 Continuation US11855909B2 (en) | 2018-09-28 | 2022-02-16 | System and method for managing network resources |
Publications (1)
Publication Number | Publication Date |
---|---|
US20200106714A1 true US20200106714A1 (en) | 2020-04-02 |
Family
ID=69946702
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/585,585 Abandoned US20200106714A1 (en) | 2018-09-28 | 2019-09-27 | System and method for managing network resources |
US17/673,591 Active US11855909B2 (en) | 2018-09-28 | 2022-02-16 | System and method for managing network resources |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/673,591 Active US11855909B2 (en) | 2018-09-28 | 2022-02-16 | System and method for managing network resources |
Country Status (2)
Country | Link |
---|---|
US (2) | US20200106714A1 (en) |
CA (1) | CA3057032C (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11146640B2 (en) * | 2018-09-10 | 2021-10-12 | Tata Consultancy Services Limited | System and method for enabling intelligent network services by cognitive sense-analyze-decide-respond framework |
US11176508B2 (en) * | 2019-03-12 | 2021-11-16 | International Business Machines Corporation | Minimizing compliance risk using machine learning techniques |
US20220014446A1 (en) * | 2020-07-10 | 2022-01-13 | Hewlett Packard Enterprise Development Lp | Network device association with network management system |
US20220129294A1 (en) * | 2019-01-29 | 2022-04-28 | Nippon Telegraph And Telephone Corporation | Virtualization platform and virtualization platform scaling management method |
US11363120B2 (en) * | 2019-05-13 | 2022-06-14 | Volkswagen Aktiengesellschaft | Method for running an application on a distributed system architecture |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230334433A1 (en) * | 2022-04-19 | 2023-10-19 | Ncr Corporation | Usage-based preventive terminal maintenance |
Family Cites Families (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6973622B1 (en) | 2000-09-25 | 2005-12-06 | Wireless Valley Communications, Inc. | System and method for design, tracking, measurement, prediction and optimization of data communication networks |
US7225250B1 (en) | 2000-10-30 | 2007-05-29 | Agilent Technologies, Inc. | Method and system for predictive enterprise resource management |
US20070121509A1 (en) | 2005-10-12 | 2007-05-31 | Sbc Knowledge Ventures Lp | System and method for predicting updates to network operations |
GB2432992B (en) | 2005-11-18 | 2008-09-10 | Cramer Systems Ltd | Network planning |
US8904241B2 (en) | 2011-07-27 | 2014-12-02 | Oracle International Corporation | Proactive and adaptive cloud monitoring |
US9112733B2 (en) * | 2010-11-22 | 2015-08-18 | International Business Machines Corporation | Managing service level agreements using statistical process control in a networked computing environment |
US9442771B2 (en) | 2010-11-24 | 2016-09-13 | Red Hat, Inc. | Generating configurable subscription parameters |
WO2014119719A1 (en) | 2013-02-01 | 2014-08-07 | 日本電気株式会社 | Resource control system, control pattern generation device, control device, resource control method and program |
US11095533B1 (en) | 2018-03-07 | 2021-08-17 | Amdocs Development Limited | System, method, and computer program for implementing a marketplace for edge computing |
US9853914B1 (en) | 2014-11-11 | 2017-12-26 | Amdocs Software Systems Limited | System, method, and computer program for selecting at least one new physical element and/or virtual element for use in a system including a network function virtualization orchestrator (NFV-O) |
US9338065B2 (en) | 2014-01-06 | 2016-05-10 | Cisco Technology, Inc. | Predictive learning machine-based approach to detect traffic outside of service level agreements |
US10644979B2 (en) * | 2018-06-06 | 2020-05-05 | The Joan and Irwin Jacobs Technion-Cornell Institute | Telecommunications network traffic metrics evaluation and prediction |
WO2015185108A1 (en) | 2014-06-03 | 2015-12-10 | Telefonaktiebolaget L M Ericsson (Publ) | Operational lifetime of communication network nodes |
US9742690B2 (en) | 2014-08-20 | 2017-08-22 | At&T Intellectual Property I, L.P. | Load adaptation architecture framework for orchestrating and managing services in a cloud computing system |
US10031785B2 (en) | 2015-04-10 | 2018-07-24 | International Business Machines Corporation | Predictive computing resource allocation for distributed environments |
US10349240B2 (en) * | 2015-06-01 | 2019-07-09 | Huawei Technologies Co., Ltd. | Method and apparatus for dynamically controlling customer traffic in a network under demand-based charging |
US9392471B1 (en) * | 2015-07-24 | 2016-07-12 | Viavi Solutions Uk Limited | Self-optimizing network (SON) system for mobile networks |
US10070328B2 (en) | 2015-08-20 | 2018-09-04 | International Business Mahcines Corporation | Predictive network traffic management |
US20170127427A1 (en) | 2015-11-02 | 2017-05-04 | Viavi Solutions Uk Limited | Enhancing network topology information for a self-organizing network |
US20170141967A1 (en) * | 2015-11-16 | 2017-05-18 | International Business Machines Corporation | Resource forecasting for enterprise applications |
US10491501B2 (en) | 2016-02-08 | 2019-11-26 | Ciena Corporation | Traffic-adaptive network control systems and methods |
US10135701B2 (en) * | 2016-02-19 | 2018-11-20 | At&T Intellectual Property I, L.P. | Context-aware virtualized control decision support system for providing quality of experience assurance for internet protocol streaming video services |
US20170257304A1 (en) | 2016-03-07 | 2017-09-07 | General Electric Company | Systems and methods for monitoring system performance and availability |
US10091070B2 (en) | 2016-06-01 | 2018-10-02 | Cisco Technology, Inc. | System and method of using a machine learning algorithm to meet SLA requirements |
US20170373938A1 (en) | 2016-06-27 | 2017-12-28 | Alcatel-Lucent Usa Inc. | Predictive auto-scaling of virtualized network functions for a network |
US10749807B2 (en) | 2016-08-30 | 2020-08-18 | Here Global B.V. | Wireless network optimization |
US11206193B2 (en) * | 2017-11-09 | 2021-12-21 | Futurewei Technologies, Inc. | Method and system for provisioning resources in cloud computing |
WO2019185561A1 (en) * | 2018-03-25 | 2019-10-03 | British Telecommunications Public Limited Company | Dynamic network adaptation |
US20190319881A1 (en) | 2018-04-13 | 2019-10-17 | Microsoft Technology Licensing, Llc | Traffic management based on past traffic arrival patterns |
US11134016B2 (en) | 2018-10-26 | 2021-09-28 | Hughes Network Systems, Llc | Monitoring a communication network |
-
2019
- 2019-09-27 CA CA3057032A patent/CA3057032C/en active Active
- 2019-09-27 US US16/585,585 patent/US20200106714A1/en not_active Abandoned
-
2022
- 2022-02-16 US US17/673,591 patent/US11855909B2/en active Active
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11146640B2 (en) * | 2018-09-10 | 2021-10-12 | Tata Consultancy Services Limited | System and method for enabling intelligent network services by cognitive sense-analyze-decide-respond framework |
US20220129294A1 (en) * | 2019-01-29 | 2022-04-28 | Nippon Telegraph And Telephone Corporation | Virtualization platform and virtualization platform scaling management method |
US11176508B2 (en) * | 2019-03-12 | 2021-11-16 | International Business Machines Corporation | Minimizing compliance risk using machine learning techniques |
US11363120B2 (en) * | 2019-05-13 | 2022-06-14 | Volkswagen Aktiengesellschaft | Method for running an application on a distributed system architecture |
US20220014446A1 (en) * | 2020-07-10 | 2022-01-13 | Hewlett Packard Enterprise Development Lp | Network device association with network management system |
US11558263B2 (en) * | 2020-07-10 | 2023-01-17 | Hewlett Packard Enterprise Development Lp | Network device association with network management system |
Also Published As
Publication number | Publication date |
---|---|
CA3057032A1 (en) | 2020-03-28 |
US20220174024A1 (en) | 2022-06-02 |
US11855909B2 (en) | 2023-12-26 |
CA3057032C (en) | 2023-03-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11855909B2 (en) | System and method for managing network resources | |
US10262019B1 (en) | Distributed management optimization for IoT deployments | |
Brogi et al. | How to best deploy your fog applications, probably | |
US11119878B2 (en) | System to manage economics and operational dynamics of IT systems and infrastructure in a multi-vendor service environment | |
JP7355404B2 (en) | Automatic tuner for embedding cloud microservices | |
US11283863B1 (en) | Data center management using digital twins | |
US9444717B1 (en) | Test generation service | |
US11343201B2 (en) | Intent-based orchestration using network parsimony trees | |
US20210209481A1 (en) | Methods and systems for dynamic service performance prediction using transfer learning | |
US11805005B2 (en) | Systems and methods for predictive assurance | |
Kim et al. | Prediction based sub-task offloading in mobile edge computing | |
US11722371B2 (en) | Utilizing unstructured data in self-organized networks | |
Forti et al. | Simulating fogdirector application management | |
Wen et al. | Fog orchestration for IoT services: issues, challenges and directions | |
US20180005249A1 (en) | Optimize a resource allocation plan corresponding to a legacy software product sustenance | |
US20220014446A1 (en) | Network device association with network management system | |
US11012463B2 (en) | Predicting condition of a host for cybersecurity applications | |
AU2021218217A1 (en) | Systems and methods for preventative monitoring using AI learning of outcomes and responses from previous experience. | |
Rolik et al. | IoT and cloud computing: the architecture of microcloud-based IoT infrastructure management system | |
EP3330854A1 (en) | Automatic selection of infrastructure on a hybrid cloud environment | |
López-Peña et al. | Case studies in application placement and infrastructure optimisation | |
EP4184880A1 (en) | Cloud network failure auto-correlator | |
Petrou et al. | Weighted Load Balancing Mechanisms over Streaming Big Data for Online Machine Learning. | |
US20230385045A1 (en) | Method, device, and computer program product for upgrading virtual system | |
US20220398133A1 (en) | Testing framework with load forecasting |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ELEMENT AI INC., CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:COTE, MARIE-CLAUDE;FORTIER, THOMAS;NORDELL-MARKOVITS, ALEXEI;REEL/FRAME:053959/0761 Effective date: 20200915 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
AS | Assignment |
Owner name: SERVICENOW CANADA INC., CANADA Free format text: MERGER;ASSIGNOR:ELEMENT AI INC.;REEL/FRAME:058562/0381 Effective date: 20210108 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |