Agent for determining and sharing sturdiness levels of network resources in a secure manner
The agent on a distributed ledger securely determines and shares network resource sturdiness levels, addressing the lack of standardization in conventional systems and enhancing resilience during emergencies by enabling secure resource preemption and temporary network activation.
Patent Information
- Application Number
- PCT/SE2023/050649
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-06-22
- Publication Date
- 2024-12-26
AI Technical Summary
Conventional network orchestration systems are not designed to handle catastrophic events like wars and natural disasters, which require collaboration among network operators to share and determine the sturdiness levels of network resources securely, as they lack a standardized method for assessing and sharing resilience metrics, and are vulnerable to security and confidentiality concerns.
An agent interfaces with a distributed ledger to determine and verify the sturdiness levels of network resources using a consensus mechanism, allowing secure sharing and preemption of resources during emergency situations, ensuring resilience and preventing record falsification.
Enables secure and standardized determination and sharing of network resource sturdiness levels, facilitating collaborative resource preemption and temporary network activation during emergencies, while maintaining security and confidentiality.
Smart Images

Figure SE2023050649_26122024_PF_FP_ABST
Abstract
Description
SPECIFICATIONAGENT FOR DETERMINING AND SHARING STURDINESS LEVELS OF NETWORK RESOURCES IN A SECURE MANNERTECHNICAL FIELD
[0001] Embodiments disclosed herein relate to the field of computer networks, and more specifically, to an agent for determining and sharing sturdiness levels of network resources in a secure manner.BACKGROUND
[0002] During emergency situations such as natural events, wars, and other high-risk scenarios, network infrastructure that connects critical organizations and people may be impacted by massive failures as a consequence of earthquakes, flooding, or hostile activities. For example, the network infrastructure may be targeted by physical attacks (e.g., with missiles and / or bombs) and / or cyber-attacks, which can result in the loss of network services.
[0003] During such emergency situations, the network operator should be able to preserve the most critical functions of its network so that the network can provide essential network services such as connectivity for government, shelters, and / or communities. The network operator should be able to provide a resilient network that can withstand large-scale catastrophic events.
[0004] Conventional network orchestration systems are designed to optimize the deployment of network services according to the network conditions and the traffic demand. They typically leverage software defined networking (SDN) controllers and path computation engines (PCEs) to preserve quality of service (QoS) and service level agreement (SLA) characteristics in the network. Conventional network orchestration systems may react to changes to network conditions such as failures or congestion and are typically designed to serve each network operator independently, preserving the confidentiality of each network operator. However, conventional network orchestration systems are not designed to deal with catastrophic events such as wars, natural disasters, and other high-risk scenarios (e.g., in which human activities purposefully destroy or hijack the network infrastructure itself), which require collaboration among network operators to be recovered.SUMMARY
[0005] A method performed by one or more network devices implementing an agent of a network operator is disclosed. The method includes obtaining, for each of one or more networkresources managed by the network operator, a set of parameter values of the network resource, determining, for each of the one or more network resources, a sturdiness level of the network resource based on a sturdiness determination algorithm and the set of parameter values of the network resource, and sending a request to a distributed ledger to store one or more sturdiness level records that indicate the sturdiness levels of the one or more network resources, wherein the one or more sturdiness level records are verified by participants of the distributed ledger using a consensus mechanism based on the sturdiness determination algorithm and the sets of parameter values of the one or more network resources before being stored in the distributed ledger.
[0006] A non-transitory machine-readable storage medium is disclosed that provides instructions that, if executed by one or more processors of a network device functioning as an agent of a network operator, will cause said agent to perform operations including obtaining, for each of one or more network resources managed by the network operator, a set of parameter values of the network resource, determining, for each of the one or more network resources, a sturdiness level of the network resource based on a sturdiness determination algorithm and the set of parameter values of the network resource, and sending a request to a distributed ledger to store one or more sturdiness level records that indicate the sturdiness levels of the one or more network resources, wherein the one or more sturdiness level records are verified by participants of the distributed ledger using a consensus mechanism based on the sturdiness determination algorithm and the sets of parameter values of the one or more network resources before being stored in the distributed ledger.
[0007] A network device configured to function as an agent of a network operator is disclosed. The network device includes one or more processors and a non-transitory machine-readable storage medium that stores instructions, which when executed by the one or more processors, causes the agent to perform operations including obtaining, for each of one or more network resources managed by the network operator, a set of parameter values of the network resource, determining, for each of the one or more network resources, a sturdiness level of the network resource based on a sturdiness determination algorithm and the set of parameter values of the network resource, and sending a request to a distributed ledger to store one or more sturdiness level records that indicate the sturdiness levels of the one or more network resources, wherein the one or more sturdiness level records are verified by participants of the distributed ledger using a consensus mechanism based on the sturdiness determination algorithm and the sets of parameter values of the one or more network resources before being stored in the distributed ledger.
[0008] A method performed by one or more network devices implementing a network orchestrator is disclosed. The method includes obtaining, from a distributed ledger, sturdiness levels of one or more network resources, designing a temporary network, sending one or more requests to one or more agents to preempt one or more network resources for use by the temporary network in response to a determination that the temporary network is to be activated, and activating the temporary network.
[0009] A non-transitory machine-readable storage medium is disclosed that provides instructions that, if executed by one or more processors of a network device functioning as an agent of a network operator, will cause said agent to perform operations including obtaining, from a distributed ledger, sturdiness levels of one or more network resources, designing a temporary network, sending one or more requests to one or more agents to preempt one or more network resources for use by the temporary network in response to a determination that the temporary network is to be activated, and activating the temporary network.
[0010] A network device configured to function as a network orchestrator is disclosed. The network device includes one or more processors and a non-transitory machine-readable storage medium that stores instructions, which when executed by the one or more processors, causes the network orchestrator to perform operations including obtaining, from a distributed ledger, sturdiness levels of one or more network resources, designing a temporary network, sending one or more requests to one or more agents to preempt one or more network resources for use by the temporary network in response to a determination that the temporary network is to be activated, and activating the temporary network.BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The invention may best be understood by referring to the following description and accompanying drawings that are used to illustrate particular embodiments of the invention. In the drawings:
[0012] Figure 1 is a diagram showing an environment in which sturdiness levels of network resources can be determined and shared in a secure manner, according to some embodiments.
[0013] Figure 2 is a diagram showing interactions between components to store sturdiness levels of network resources in a secure manner, according to some embodiments.
[0014] Figure 3 is a diagram showing interactions between components to preempt network resources, according to some embodiments.
[0015] Figure 4 is a diagram showing interactions between components to release network resources from preemption, according to some embodiments.
[0016] Figure 5A is a diagram showing two mobile network operators providing network coverage during normal (non-emergency) conditions, according to some embodiments.
[0017] Figure 5B is a diagram showing a reduction in network coverage due to an emergency situation, according to some embodiments.
[0018] Figure 5C is a diagram showing preemption of a base station to restore network coverage during the emergency situation, according to some embodiments.
[0019] Figure 5D is a diagram showing a reduction in coverage due to an emergency situation, according to some embodiments.
[0020] Figure 5E is a diagram showing preemption of a cloud resource to restore network coverage during the emergency situation, according to some embodiments.
[0021] Figure 6 is a flow diagram of a method for determining and sharing sturdiness levels of network resources in a secure manner, according to some embodiments.
[0022] Figure 7 is a flow diagram of a method for activating a temporary network, according to some embodiments.
[0023] Figure 8 illustrates a further implementation example for particular embodiments of the described solution.
[0024] Figure 9 illustrates three specific examples of a network device (ND) that may be used to implement particular embodiments of the described solution.DETAILED DESCRIPTION
[0025] The following description describes methods and apparatus for determining and sharing sturdiness levels of network resources in a secure manner. In the following description, numerous specific details such as logic implementations, opcodes, means to specify operands, resource partitioning / sharing / duplication implementations, types and interrelationships of system components, and logic partitioning / integration choices are set forth in order to provide a more thorough understanding of embodiments. It will be appreciated, however, by one skilled in the art that embodiments may be practiced without such specific details. In other instances, control structures, gate level circuits and full software instruction sequences have not been shown in detail in order not to obscure the description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.
[0026] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to thesame embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0027] Bracketed text and blocks with dashed borders (e.g., large dashes, small dashes, dotdash, and dots) may be used herein to illustrate optional operations that add additional features to embodiments. However, such notation should not be taken to mean that these are the only options or optional operations, and / or that blocks with solid borders are not optional in certain embodiments.
[0028] In the following description and claims, the terms “coupled” and “connected,” along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. “Coupled” is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, co-operate or interact with each other. “Connected” is used to indicate the establishment of communication between two or more elements that are coupled with each other.
[0029] An electronic device stores and transmits (internally and / or with other electronic devices over a network) code (which is composed of software instructions and which is sometimes referred to as computer program code or a computer program) and / or data using machine-readable media (also called computer-readable media), such as machine-readable storage media (e.g., magnetic disks, optical disks, solid state drives, read only memory (ROM), flash memory devices, phase change memory) and machine-readable transmission media (also called a carrier) (e.g., electrical, optical, radio, acoustical or other form of propagated signals - such as carrier waves, infrared signals). Thus, an electronic device (e.g., a computer) includes hardware and software, such as a set of one or more processors (e.g., wherein a processor is a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, other electronic circuitry, a combination of one or more of the preceding) coupled to one or more machine-readable storage media to store code for execution on the set of processors and / or to store data. For instance, an electronic device may include non-volatile memory containing the code since the non-volatile memory can persist code / data even when the electronic device is turned off (when power is removed), and while the electronic device is turned on that part of the code that is to be executed by the processor(s) of that electronic device is typically copied from the slower nonvolatile memory into volatile memory (e.g., dynamic random access memory (DRAM), static random access memory (SRAM)) of that electronic device. Typical electronic devices also include a set of one or more physical network interface(s) (NI(s)) to establish networkconnections (to transmit and / or receive code and / or data using propagating signals) with other electronic devices. For example, the set of physical NIs (or the set of physical NI(s) in combination with the set of processors executing code) may perform any formatting, coding, or translating to allow the electronic device to send and receive data whether over a wired and / or a wireless connection. In some embodiments, a physical NI may comprise radio circuitry capable of receiving data from other electronic devices over a wireless connection and / or sending data out to other devices via a wireless connection. This radio circuitry may include transmitted s), received s), and / or transceiver(s) suitable for radiofrequency communication. The radio circuitry may convert digital data into a radio signal having the appropriate parameters (e.g., frequency, timing, channel, bandwidth, etc.). The radio signal may then be transmitted via antennas to the appropriate recipient(s). In some embodiments, the set of physical NI(s) may comprise network interface controller(s) (NICs), also known as a network interface card, network adapter, or local area network (LAN) adapter. The NIC(s) may facilitate in connecting the electronic device to other electronic devices allowing them to communicate via wire through plugging in a cable to a physical port connected to a NIC. One or more parts of an embodiment o may be implemented using different combinations of software, firmware, and / or hardware.
[0030] A network device (ND) is an electronic device that communicatively interconnects other electronic devices on the network (e.g., other network devices, end-user devices). Some network devices are “multiple services network devices” that provide support for multiple networking functions (e.g., routing, bridging, switching, Layer 2 aggregation, session border control, Quality of Service, and / or subscriber management), and / or provide support for multiple application services (e.g., data, voice, and video).
[0031] As mentioned above, conventional network orchestration systems are not designed to deal with catastrophic events such as wars, natural disasters, and other high-risk scenarios.When catastrophic events occur, it may be helpful for network operators to collaborate with each other to share network resources. For example, if a network operator is no longer able to provide network services to a particular geographic area due to an attack on its network infrastructure, it may be helpful for the network operator to collaborate with another network operator who is able to provide network services to that geographic area. However, such collaboration requires that the network operators share network deployment details with each other and / or with third parties (e.g., a government authority), which may raise security and confidentiality concerns. There is a risk that any information that is shared could be leaked and used to conduct targeted attacks on critical network infrastructure. During emergency situations, it is important for network operators to be able to provide a resilient network that can withstand possible attacks and disasters. In order to design / configure a resilient network, networkoperators need to know the sturdiness levels of the available network resources. However, there is no standard way for network operators to determine and share the sturdiness levels of network resources with each other. Each network operator may have a different way of determining the sturdiness levels of their network resources. Also, there is a risk that sturdiness levels can be faked to create a competitive advantage or threat.
[0032] Embodiments are disclosed herein that allow network operators to determine and share the sturdiness levels of their network resources in a secure manner. The sturdiness level of a network resource is a new metric introduced by the present disclosure that may indicate how resilient the network resource is against potential attacks or disasters. Embodiments provide an agent that interfaces with a distributed ledger on behalf of a network operator. The agent may obtain information about certain network resources managed by the network operator (e.g., network resources that are considered to be sufficiently sturdy to be used during emergency situations), determine the sturdiness levels of the network resources based on a sturdiness determination algorithm and the obtained information, and send a request to the distributed ledger to store sturdiness level records that indicate the sturdiness levels of the network resources. The participants of the distributed ledger may verify the sturdiness level records using a consensus mechanism before the sturdiness levels are stored in the distributed ledger. The consensus mechanism may ensure that the sturdiness levels were correctly determined using the correct sturdiness determination algorithm.
[0033] A network orchestrator may access the sturdiness level records stored in the distributed ledger to determine the sturdiness levels of the network resources managed by the network operator. During an emergency situation (e.g., a bombing of network infrastructure that results in loss of network services), the network orchestrator may design a temporary network that uses one or more of the network resources managed by the network operator (and possibly one or more network resources managed by other network operators) to restore network services. The network orchestrator may send a request to the agent to preempt the one or more network resources for use by the temporary network. In response to receiving the request, the agent may preempt the one or more network resources and send a request to the distributed ledger to store one or more preemption records that indicate that the one or more network resource are preempted. The participants of the distributed ledger may verify the one or more preemption records using the consensus mechanism before storing the one or more preemption records in the distributed ledger. The network orchestrator may then activate the temporary network.
[0034] When the emergency situation ends, the network orchestrator may deactivate the temporary network. The network orchestrator may then send a request to the agent to release the one or more network resources from preemption. In response to receiving the request, the agentmay release the one or more network resources from preemption and send a request to the distributed ledger to store one or more release records that indicate that the one or more network resources are released from preemption. The participants of the distributed ledger may verify the one or more release records using the consensus mechanism before storing the one or more release records in the distributed ledger.
[0035] In an embodiment, there can be multiple network operators, with each network operator having its own agent. This may help maintain a clean demarcation and segregation between network operators. A multi-operator network orchestrator (e.g., which may be controlled / operated by a government authority or other higher-level authority) may communicate with the respective agents of the network operators to preempt network resources across multiple networks managed by multiple network operators (e.g., to respond to an emergency situation). In an embodiment, different regions / divisions controlled by a network operator may have its own agent. A network orchestrator may communicate with the respective agents of the different regions / divisions to preempt network resources across multiple regions / divisions.
[0036] The use of a shared distributed ledger and consensus mechanism ensures that the different network operators and stakeholders use the same sturdiness determination algorithm to determine sturdiness levels and prevents records from being altered or faked. Due to its distributed nature, the distributed ledger is resilient against attacks. Also, storing the preemption records and release records in the distributed ledger allows for an official and effective way of tracking network resource usage for billing and charging amongst network operators and stakeholders.
[0037] Figure l is a diagram showing an environment in which sturdiness levels of network resources can be determined and shared in a secure manner, according to some embodiments.
[0038] As shown in the diagram, the environment includes a network orchestrator 110, a distributed ledger 120, and an ultra-resilient network layer 160. Also, the environment includes components that are operated / controlled by a first mobile network operator (“mobile network operator A”) including agent 130A, network management system 140A, and network 150A. Also, the environment includes components that are operated / controlled by a second mobile network operator (“mobile network operator B”) including agent 130B, network management system 140B, and network 150B. Although the environment is shown as including two network operators, it should be appreciated that the techniques disclosed herein can be used in an environment with more than two network operators or an environment with a single network operator.
[0039] Network 150A may provide network services for users / customers of network operator A. Similarly, network 150B may provide network services for users / customers of network operator B. In an embodiment, network 150A and / or network 150B is a mobile network such as a Third Generation Partnership Project (3GPP) Fifth Generation (5G) mobile network or similar mobile network. In an embodiment, network 150A and / or network 150B is a non-mobile network (e.g., a fixed cabled network). A network 150 may include various network resources 165 that can be used to provide network services. For example, as shown in the diagram, network 150A may include network resources 165 A, 165B, and 165C among other network resources. Also, as shown in the diagram, network 150B may include network resources 165D, 165E, and 165F among other network resources. In an embodiment where a network 150 is a mobile network, a network resource 165 may be, for example, a core network component, a base station, and / or a cloud resource.
[0040] A network management system 140 may perform various network management functions for a network 150. For example, network management system 140A may perform network management functions for network 150A. Similarly, network management system 140B may perform management functions for network 150B. Network management functions may include monitoring, configuring, updating, and / or troubleshooting network resources 165 in a network 150. A network management system 140 may maintain a network resource database 145. For example, as shown in the diagram, network management system 140 A may maintain network resource database 145 A and network management system 140B may maintain network resource database 145B. A network resource database 145 may store various information regarding the network resources 165 of a network 150. For example, network resource database 145 A may store various information regarding the network resources 165 of network 150A and network resource database 145B may store various information regarding the network resources 165 of mobile network 150B. The information stored in a network resource database 145 may include parameter values that are indicative of the sturdiness levels of network resources 165.
[0041] An agent 130 may interface with the network orchestrator 110 and the distributed ledger 120 on behalf of a network operator. For example, agent I30A may interface with the network orchestrator 110 and the distributed ledger 120 on behalf of network operator A. Similarly, agent 130B may interface with the network orchestrator 110 and the distributed ledger 120 on behalf of network operator B. The network orchestrator 110 may communicate with agents 130 using an application programming interface (API). The API may allow the network orchestrator 110 to send requests to the agents 130 to update sturdiness levels ofnetwork resources 165, preempt network resources 165, and release network resources 165 from preemption.
[0042] An agent 130 may communicate with a network management system 140 to obtain information regarding network resources 165. For example, agent 130A may communicate with network management system 140 A to obtain information regarding network resources 165 managed by network operator A (e.g., which may be stored in network resource database 145 A) and agent 130B may communicate with network management system 140B to obtain information regarding network resources 165 managed by network operator B (e.g., which may be stored in network resource database 145B).
[0043] Each agent 130 may register with the distributed ledger 120 and receive the same sturdiness determination algorithm from the distributed ledger 120 as part of the registration process. For example, agent 130A and 130B may both receive the same sturdiness determination algorithm from the distributed ledger 120 when they register with the distributed ledger 120. As will be described in additional detail herein, the sturdiness determination algorithm may be used to determine the sturdiness levels of network resources 165. The sturdiness level of a network resource 165 may indicate how resilient the network resource 165 is against potential attacks or disasters. The sturdiness level may take into account the availability, security, safety, trust, and / or performance of the network resource 165.
[0044] As mentioned above, the network orchestrator 110 may send requests to agents 130 to update the sturdiness levels of network resources 165 (e.g., using an API). In response to receiving a request to update the sturdiness levels of network resources 165, an agent 130 may obtain the relevant parameter values of certain network resources 165 (e.g., from a network management system 140), determine the sturdiness levels of the network resources 165 based on the sturdiness determination algorithm and parameter values of the network resources 165, and send a request to the distributed ledger 120 to store one or more sturdiness level records 180 that indicate the sturdiness levels of the network resources 165. An agent 130 may choose to update sturdiness levels for certain network resources 165 that are considered to be sufficiently sturdy to be used during emergency situations.
[0045] For example, the network orchestrator 110 may send a request to agent 130A to update the sturdiness levels of network resources 165 managed by network operator A. In response to receiving the request, agent 130A may obtain the relevant parameter values of network resources 165A, 165B, and 165C (e.g., from network management system 145A), determine the sturdiness levels of network resources 165 A, 165B, and 165C based on the sturdiness determination algorithm and the parameter values of network resources 165 A, 165B, and 165C, and send a request to the distributed ledger 120 to store sturdiness level records 180 that indicatethe sturdiness levels of network resources 165 A, 165B, and 165C. Similarly, the network orchestrator 110 may send a request to agent 130B to update sturdiness levels of network resources 165 managed by network operator B. In response to receiving the request, agent 13 OB may obtain the relevant parameter values of network resources 165D, 165E, and 165F (e.g., from network management system 140B), determine the sturdiness levels of network resources 165D, 165E, and 165F based on the sturdiness determination algorithm and the parameter values of network resources 165D, 165E, and 165F, and send a request to the distributed ledger 120 to store sturdiness level records 180 that indicate the sturdiness levels of network resources 165D, 165E, and 165F. Although an example is described above where the network orchestrator 110 triggers the agents 130 to update sturdiness levels in the distributed ledger 120, in some embodiments the agents 130 may update sturdiness levels in the distributed ledger on their own initiative (e.g., periodically update sturdiness levels without receiving an explicit request from the network orchestrator 110).
[0046] The sturdiness level records 180 may be verified by participants of the distributed ledger 120 based on a consensus mechanism before being stored in the distributed ledger 120. The consensus mechanism may ensure that any sturdiness levels were correctly determined using the correct sturdiness determination algorithm. The use of the consensus mechanism helps prevent faked records from being stored in the distributed ledger 120 and / or helps prevent the unauthorized modification of records stored in the distributed ledger 120.
[0047] In an embodiment, when an agent 130 sends a request to the distributed ledger 120 to store a sturdiness level record 180 for a network resource 165, the agent includes an encrypted identifier of the network resource 165 in the request. The agent 130 may encrypt the identifier of the network resource 165 using the public key it received when it registered with the distributed ledger 120. Only entities that know the private key corresponding to the public key (e.g., the network orchestrator 110) may be able to decrypt the identifier of the network resource 165 from a sturdiness level record.
[0048] Thus, the agents 130 may share the sturdiness levels of certain network resources 165 by storing sturdiness level records 180 in the distributed ledger. The network resources 165 may form an ultra-resilient network layer 160 that includes sturdy network resources 165 (e.g., network resources 165A-F) that can be used during emergency situations.
[0049] The network orchestrator 110 may access the sturdiness level records 180 stored in the distributed ledger 120 to determine the sturdiness levels of network resources 165 managed by the network operators. If the network orchestrator 110 detects an emergency situation, the network orchestrator 110 may design a temporary network that can provide the needed network services using network resources 165 managed by one or more network operators. For example,if the network orchestrator 110 detects an emergency situation where certain network services are interrupted due to catastrophic network failures, the network orchestrator 110 may design a temporary network that makes use of network resource 165 A managed by mobile network operator A and network resource 165D managed by mobile network operator B to help restore the network services until the emergency situation ends.
[0050] The network orchestrator 110 may send requests to agents 130 to preempt the network resources 165. In response to receiving a request to preempt a network resource 165, an agent 130 may preempt the network resource 165 and send a request to the distributed ledger 120 to store a preemption record 185 that indicates that the network resource 165 is preempted. Preempting a network resource 165 may involve reallocating the network resource 165 for use by another network (which may include applying a particular configuration to the network resource so that it is suitable to be used by the other network). For example, the network orchestrator 110 may send a request to agent 130A to preempt network resource 165 A. In response to receiving the request, agent 130A may preempt network resource 165 A and send a request to the distributed ledger 120 to store a preemption record 185 that indicates that network resource 165 A is preempted. Similarly, the network orchestrator 110 may send a request to agent 130B to preempt network resource 165D. In response to receiving the request, agent 130B may preempt network resource 165D and send a request to the distributed ledger 120 to store a preemption record 185 that indicates that network resource 165D is preempted. The preemption records 185 may be verified by participants of the distributed ledger 120 based on a consensus mechanism before being stored in the distributed ledger 120.
[0051] The network orchestrator 110 may then activate the temporary network. When the network orchestrator 110 determines that the emergency situation has ended, the network orchestrator 110 may deactivate the temporary network and release the network resources 165 used by the temporary network from preemption.
[0052] The network orchestrator 110 may send requests to agents 130 to release network resources 165 from preemption. In response to receiving a request to release a network resource 165 from preemption, an agent 130 may release the network resource 165 from preemption and send a request to the distributed ledger 120 to store a release record 190 that indicates that the network resource 165 is released. Releasing a network resource 165 from preemption may involve reallocating the network resource 165 back to its original network (the network that the network resource 165 was allocated to prior to preemption). For example, the network orchestrator 110 may send a request to agent 130A to release network resource 165 A from preemption. In response to receiving the request, agent 130A may release network resource 165A from preemption and send a request to the distributed ledger 120 to store arelease record 190 that indicates that network resource 165 A is released. Similarly, the network orchestrator 110 may send a request agent 13 OB to release network resource 165D from preemption. In response to receiving the request, agent 13 OB may release network resource 165D from preemption and send a request to the distributed ledger 120 to store a release record 190 that indicates that network resource 165D is released. The release records 190 may be verified by participants of the distributed ledger 120 based on a consensus mechanism before being stored in the distributed ledger 120.
[0053] As mentioned above, the sturdiness determination algorithm may be used to determine the sturdiness level of a network resource 165. The sturdiness determination algorithm may determine the sturdiness level of a network resource 165 based on parameter values of the network resource 165. The parameter values of the network resource 165 may include a set of parameter values that corresponds to a set of sturdiness parameters. Sturdiness parameters may be parameters that have been determined to be relevant to the sturdiness of a network resource 165. As a non-limiting example, the sturdiness parameters may include the vulnerability level of the network resource 165, the disaster risk of the network resource 165, the network resource’s proximity to borders, the security level of the location of the network resource 165, the level of energy power autonomy of the network resource 165, and / or other parameters. It should be appreciated that the set of parameters that are used to determine the sturdiness level of a network resource 165 may vary depending on the implementation.
[0054] In an embodiment, the parameter values of a network resource 165 are stored and / or shared using the below format or similar format. By way of example only, the format is shown using extensible Markup Language (XML) notation.<xs:complexType name="SturdinessParameters"><xs:sequence><xs:element name="VulnerabilityLevel" type="xs:integer" / ><xs:element name="DisasterRisk" minOccurs="0" maxOccurs="unbounded" / ><xs:sequence><xs:element name="typeOfRisk" type- ' TypeOfRisk " / > <xs:element name="RiskEvaluation" type="xs:integer" / > <xs:sequence / ><xs:element name="ProximityToBorders" minOccurs- ' 1 " maxOccurs="unbounded" / > <xs:sequence><xs:element name="Neighboring" type="xs:string" / ><xs:element name="TensOfKilometers" type="xs:integer" / ><xs:sequence / ><xs:element name="SecureLocation" type="xs:integer" / ><xs:element name="EnergyPowerAutonomy" minOccurs="l" maxOccur s= " unb ounded " / ><xs:sequence><xs:element name="typeOfUsedEnergy" type="TypeOfUsedEnergy" / ><xs:element name="SupplyingSecurityLevel" type="xs:integer" / ><xs:element name="StockageLevel" type="xs:integer" / ><xs:sequence / ><xs:element name=" other SturdinessParameter" type="OtherSturdinessParameter" minOccurs="0" maxOccurs="unbounded" / ><xs:sequence><xs:element name- ' SturdinessParameter" type="xs:string" / ><xs:element name- 'LevelOfSturdiness" type="xs:integer" / ><xs:sequence / >< / xs:sequence>< / xs:complexType><xs:simpleType name- ' TypeOfRisk "><xs:restriction base="xs:string"><xs:enumeration value="earthquake" / ><xs:enumeration value="flood" / ><xs:enumeration value= "tsunami " / ><xs:enumeration value="eruption" / ><xs:enumeration value="landslide" / ><xs:enumeration value="other" / >< / xs:restriction>< / xs:simpleType><xs:simpleType name- ' TypeOfUsedEnergy "><xs restriction base="xs:string"><xs:enumeration value="methane" / ><xs:enumeration value="propane" / ><xs:enumeration value- ' diesel" / ><xs:enumeration value="coal" / ><xs:enumeration value="wind" / ><xs:enumeration value="sun" / ><xs:enumeration value="other" / >< / xs:restriction>< / xs:simpleType>
[0055] The format conveys a list of sturdiness parameters. The sturdiness parameters include a vulnerability level parameter (“VulnerabilityLevel”), a disaster risk parameter (“DisasterRisk”), a proximity to borders parameter (“Proximity ToB orders”), a secure location parameter (“SecureLocation”), an energy power autonomy parameter (“EnergyPowerAutonomy”), and other parameters (“otherSturdinessParameter”). The vulnerability level parameter may indicate the level of security of the software installed on a network resource (e.g., it can reflect the number of common vulnerabilities and exposures (CVEs) present at a certain moment in a node). The disaster risk parameter may indicate the type of disasters that are known to affect the network resource. The disaster risk parameter includes a type of risk sub-parameter (“typeOfRisk”) and a risk evaluation sub-parameter (“RiskEvaluation”). The type of risk sub-parameter may have a value of “earthquake,” “flood,” “tsunami,” “eruption,” landslide,” or “other.” The risk evaluation sub-parameter may indicate the probability and the impacts related to the type of risk (e.g., a network resource located in Pompeii (seismic territory, close to a Vulcan and to a closed sea) may have a high (large integer) value for earthquake, a medium value for eruption, a low value for tsunami, and no value (e.g., 0) for other reasons). The proximity to borders parameter indicates the distance (e.g., in tens of kilometers (km)) of a network resource from national borders and the bordering country / neighbor (e.g., Germany, Poland, etc.). The proximity to borders parameter includes a neighboring sub-parameter (“Neighboring”) and a tens of kilometers sub-parameter ("TensOfKilometers”). The neighboring sub-parameter may indicate the neighbor (e.g., France, Germany, Canada, etc. - the algorithm may take into account if the neighbor is an allied country, a neutral country, or an adversary). The tens of kilometers sub-parameter may indicate how far a network resource is from the neighbor in units of tens of kms (although other embodiments may use a different unit of distance). The secure location parameter indicates the security level of the place where the network resource is installed (e.g., the security level may be different depending on whether the network resource is installed in a bunker, under a mountain, or close to critical targets, etc.). The energy power autonomy parameter indicates the level of autonomy a network resource has in terms of its energy supply. The energy power autonomy parameter includes a type of used energy sub-parameter (“typeOfUsedEnergy”), a supplyingsecurity level sub-parameter (“SupplyingSecurityLevel”), and a stockage level sub-parameter (“StockageLevel”). The type of used energy sub-parameter may have a value of “methane,” “propane,” “diesel,” “coal,” “wind,” “sun,” or “other.” The supplying security level subparameter may indicate how easily additional energy supply can be obtained (e.g., if the power is provided by methane and the methane is provided by another country, this can cause problems). The stockage level sub-parameter may indicate how much supply of energy is available (e.g., how much time the network resource can continue to be available if the supplier does not supply any more energy).
[0056] In an embodiment, each parameter value is a value that is between 0 and 1 (e.g., where a higher value indicates a higher sturdiness level and a lower value indicates a lower sturdiness level). For example, a parameter value that indicates a network resource’s proximity to borders may be determined using the formula provided below.
[0057] In the formula, StPTBis a parameter value that indicates the network resource’s proximity to borders, TV is a sub-parameter value that indicates the neighboring country, and TOK is a sub-parameter value that indicates the distance of the network resourcel65 from the national borders of the country (in units of tens of kilometers). Also, FPTB(which may be a value between 0 and 1) is a weight assigned to the distance Of the network resource 165 from the national border and FPTB(N) (which value maybe different depending on the neighbor N) is a more specific weight assigned to the neighboring country. As an example, the value of FPTB(N) may be higher if the neighboring country is considered an enemy, while the value of FPTB(N) may be lower if the neighboring country is considered an allied country (which makes StPTBhigher, closer to 1). StPTBwill be a value between 0 and 1.
[0058] Other sturdiness parameter values may be determined in a similar way to be a value between 0 and 1 based on relevant factors.
[0059] The sturdiness level of a network resource 165 may be determined based on a set of parameter values of the network resource 165. For example, the sturdiness level of a network resource 165 may be determined using the below formula. stx = nr=i 'St%i
[0060] In the formula, Stx is the sturdiness level of network resource x and Stxtis the parameter value of network resource x for a particular parameter i. 77 is a multiplication / product operation and n is the number of parameters. In an embodiment, each of the parameter values can be weighted based on its importance.
[0061] While particular formulas for determining parameter values and sturdiness levels are describe above, it should be appreciated that these formulas are provided by way of example to illustrate one embodiment. It will be appreciated that other embodiments can use different formulas / algorithms to determine the parameter values and / or sturdiness levels.
[0062] Figure 2 is a diagram showing interactions between components to store sturdiness levels of network resources in a secure manner, according to some embodiments.
[0063] As shown in the diagram, the agent 130 may send a request to register with the distributed ledger 120. The registration request may include an agent ID associated with the agent 130 that uniquely identifies the agent 130 (among other agents).
[0064] If the distributed ledger 120 successfully authenticates and registers the agent 130, the distributed ledger 120 may send a registration acknowledgement (ACK) to the agent 130. The registration ACK may include a public key and a sturdiness determination algorithm. The public key may correspond to a private key that is known to the network orchestrator 110. The sturdiness determination algorithm may be an algorithm for determining the sturdiness level of a network resource based on parameter values of the network resource (e.g., as described herein above).
[0065] The network orchestrator 110 may send a request to the agent 130 to update the sturdiness levels of network resources. In response to receiving this request, the agent 130 may send a request to the network management system 140 for sturdiness parameter values of the network resources. In response to receiving this request, the network management system 140 may send the sturdiness parameter values of network resources R1 to Rw to the agent 130.
[0066] For each network resource, the agent 130 may determine the sturdiness level of the network resource using the sturdiness determination algorithm and the parameter values of the network resource and send a request to the distributed ledger 120 to store a sturdiness level record in the distributed ledger 120 that indicates the sturdiness level of the network resource.
[0067] For example, as shown in the diagram, the agent 130 may determine the sturdiness level of R1 using the sturdiness determination algorithm and send a request to the distributed ledger 120 to store a sturdiness level record for R1 in the distributed ledger 120. The request to store the sturdiness level record for R1 may include an encrypted ID of R1 (e.g., encrypted using the public key received during registration with the distributed ledger 120), the sturdiness level of Rl, and the sturdiness parameter values of R1 that were used to determine the sturdiness level of Rl. The participants of the distributed ledger 120 may verify the sturdiness level record for Rl using a consensus mechanism (e.g., verify that the sturdiness level of Rl has been correctly determined using the correct sturdiness determination algorithm). If consensus is reached, the sturdiness level record for Rl may be stored in the distributed ledger 120. Theagent 130 may perform similar operations for the other network resources (e.g., network resources R2 to Rw) to store sturdiness level records for those network resources in the distributed ledger 120.
[0068] When the network management system 140 has finished sending sturdiness parameter values to the agent 130, the network management system 140 may send an indication to the agent 130 that the parameter values for all network resources have been sent. The agent 130 may then send an acknowledgement to the network orchestrator 110 that the sturdiness levels have been updated in the distributed ledger 120. The acknowledgement may include the agent ID of the agent 130.
[0069] Subsequently, the network orchestrator 110 may send a request to the distributed ledger 120 for the network resources managed by the mobile network operator. The request may include the agent ID of the agent 130. In response to receiving this request, the distributed ledger 120 may send the list of network resources (e.g., Rl-Rw) managed by the network operator and their sturdiness levels, as stored in distributed ledger 120, to the network orchestrator 110.
[0070] Figure 3 is a diagram showing interactions between components to preempt network resources, according to some embodiments.
[0071] As shown in the diagram, in response to detecting an emergency situation, the network orchestrator 110 may design a temporary network that uses various network resources including network resource Rx managed by a first network operator (network operator A) and network resource Ry managed by a second network operator (network operator M).
[0072] The network orchestrator 110 may then send requests to the appropriate agents 130 to preempt the network resources. For example, the network orchestrator 110 may send a request to agent 130A of network operator A to preempt Rx. The request may include the ID of Rx and a configuration to apply to Rx. In response to receiving this request, agent 130A may preempt Rx and send a request to the distributed ledger 120 to store a preemption record that indicates that Rx is preempted. Agent 130A may cause the configuration to be applied to the network resource (e.g., via a node command line, or via a network management system). The participants of the distributed ledger 120 may verify the preemption record for Rx using a consensus mechanism. If consensus is reached, the preemption record for Rx may be stored in the distributed ledger 120. Agent 130A may then send an acknowledgement to the network orchestrator 110 that indicates that Rx is preempted.
[0073] The network orchestrator 110 may send additional requests to agent 130A and / or other agents 130 to preempt additional network resources. For example, as shown in the diagram, the network orchestrator 110 may then send a request to agent 130M of network operator M topreempt Ry. The request may include the ID of Ry and a configuration to apply to Ry. In response to receiving this request, agent 130M may preempt Ry and send a request to the distributed ledger 120 to store a preemption record that indicates that Ry is preempted.Agent 130M may cause the configuration to be applied to the network resource (e.g., via a node command line, or via a network management system). The participants of the distributed ledger 120 may verify the preemption record for Ry using a consensus mechanism. If consensus is reached, the preemption record for Ry may be stored in the distributed ledger 120.Agent 130M may then send an acknowledgement to the network orchestrator 110 that indicates that Ry is preempted.
[0074] Once all the needed network resources that are needed for the temporary network are preempted, the network orchestrator 110 may activate the temporary network.
[0075] Figure 4 is a diagram showing interactions between components to release network resources from preemption, according to some embodiments.
[0076] In response to detecting that the emergency situation has ended, the network orchestrator 110 may deactivate the temporary network.
[0077] The network orchestrator 110 may then send requests to the appropriate agents 130 to release the preempted network resources. For example, the network orchestrator 110 may send a request to agent 130A to release Rx. The request may include the ID of Rx. In response to receiving this request, agent 130A may release Rx from preemption and send a request to the distributed ledger 120 to store a release record that indicates that Rx is released from preemption. The participants of the distributed ledger 120 may verify the release record for Reusing a consensus mechanism. If consensus is reached, the release record for Rx may be stored in the distributed ledger 120. Agent 130A may then send an acknowledgement to the network orchestrator 110 that indicates that the Rx is released from preemption.
[0078] The network orchestrator 110 may send additional requests to agent 130A and / or other agents 130 to release previously preempted network resources. For example, as shown in the diagram, network orchestrator 110 may send a request to agent 130M to release Ry. The request may include the ID of Ry. In response to receiving this request, agent 130M may release Ry from preemption and send a request to the distributed ledger 120 to store a release record that indicates that Ry is released from preemption. The participants of the distributed ledger 120 may verify the release record for Fly using a consensus mechanism. If consensus is reached, the release record for R may be stored in the distributed ledger 120. Agent 130M may then send an acknowledgement to the network orchestrator 110 that indicates that the Ry is released from preemption.
[0079] Example use cases are described below to further demonstrate the technical and practical benefits of the embodiments described herein. The example use cases assume a situation with two mobile network operators using different frequencies to provide 5G coverage over a geographic area from different sites.
[0080] Figure 5A is a diagram showing two mobile network operators providing network coverage during normal (non-emergency) conditions, according to some embodiments. As shown in the diagram, mobile network operator A may operate a core network 510A and a base station 520 A. Base station 520 A may be connected to core network 510A using a mobile backhaul. Similarly, mobile network operator B may operate a core network 510B and a base station 520B. Base station 520B may be connected to core network 510B using a mobile backhaul. Base station 520 A may provide network coverage for a certain geographical area, as depicted in the diagram by the shaded portion emanating from base station 520A. Similarly, base station 520B may provide network coverage for a certain geographical area, as depicted in the diagram by the shaded portion emanating from base station 520B.
[0081] Figure 5B is a diagram showing a reduction in network coverage due to an emergency situation, according to some embodiments. As shown in the diagram, base station 520A of mobile network operator A may become unavailable due to an emergency situation. This may result in the lack of coverage or reduced coverage for subscribers of mobile network operator A in the geographic area near base station 520A.
[0082] Figure 5C is a diagram showing preemption of a base station to restore network coverage during the emergency situation, according to some embodiments. If mobile network operator A is not able to restore network coverage in the area in a short amount of time, an authority (e.g., a government authority) may decide to preempt base station 520B (and possibly other base stations managed by mobile network operator B or other mobile network operators) to temporarily provide network coverage in the area. Base station 520B of mobile network operator B may temporarily provide network coverage in the geographic area, as depicted in the diagram by the additional shaded portion emanating from base station 520B.
[0083] Accomplishing such preemption would typically require paperwork and agreements between the mobile network operators or other stakeholders, trusted communications between the mobile network operators or other stakeholders (which is not always possible, e.g., in war zones), and performing a manual switchover. However, with embodiments described herein, the preemption can be performed quickly and securely with fewer manual steps.
[0084] For example, a network orchestrator may send requests to the agents of the respective mobile network operators to update the sturdiness levels in the distributed ledger. When there is an emergency situation, the network orchestrator may determine that a certain geographic areahas lost network coverage (e.g., due to a base station failure) and needs emergency network support to provide mission critical services.
[0085] The network orchestrator may access the sturdiness level records stored in the distributed ledger to determine whether any of the mobile network operators have resilient / sturdy network resources covering the same geographic area (e.g., an alternative base station that can support the lost frequencies and provide mobile network operator service roaming). The network orchestrator may verify the sturdiness levels of the network resources and send requests to the relevant agents to preempt the network resources. The agents may preempt the network resources (e.g., an agent may send a request to its network management system to reallocate the network resource to a temporary network, independently from its current usage) and store preemption records in the distributed ledger that indicate that the network resources are preempted.
[0086] When the emergency situation ends, the network orchestrator may send requests to the relevant agents to release the preempted network resources. The agents may release the preempted network resources (reallocate the network resources to the mobile network operators) and store release records in the distributed ledger that indicate that the network resources are released (e.g., for tracking, charging / billing, and / or security reasons).
[0087] With embodiments, the mobile network operators do not need to share frequency maps and coverage maps with each other, and any preemption and release of network resources can be securely and immutably tracked in the distributed ledger.
[0088] Figure 5D is a diagram showing a reduction in coverage due to an emergency situation, according to some embodiments.
[0089] As shown in the diagram, core network 510A of mobile network operator A may become unavailable due to an emergency situation (e.g., due to a cloud failure or the failure of mobile backhaul links between core network 510A and base station 520A). This may result in the lack of coverage or reduced coverage for subscribers of mobile network operator A in the geographic area near base station 520A.
[0090] Figure 5E is a diagram showing preemption of a cloud resource to restore network coverage during the emergency situation, according to some embodiments.
[0091] If mobile network operator A is not able to restore network coverage in the area in a short amount of time, an authority (e.g., a government authority) may decide to preempt cloud resources of mobile network operator B to host core network services of mobile network operator A. For example, a temporary core network 510AE may be hosted using the cloud resources of mobile network operator B, which allows base station 520A of mobile networkoperator A to provide network coverage in the geographies area again, as depicted in the diagram by the shaded portion emanating from base station 520A.
[0092] With embodiments described herein, the preemption can be performed quickly and securely with fewer manual steps.
[0093] For example, the network orchestrator may send requests to the agents of the respective mobile network operators to update the sturdiness levels in the distributed ledger. When there is an emergency situation, the network orchestrator may determine that a certain geographic area has lost network coverage (e.g., due to a core network failure) and needs emergency network support to provide mission critical services.
[0094] The network orchestrator may access the sturdiness level records stored in the distributed ledger to determine whether any of the mobile network operators have resilient / sturdy network resources covering the same geographic area (e.g., an alternative cloud resource that can host core services to provide network coverage in the area). The network orchestrator may verify the sturdiness levels of the network resources and send requests to the relevant agents to preempt the network resources. The agents may preempt the network resources (e.g., an agent may send a request to its network management system to reallocate the network resource to a temporary network, independently from its current usage) and store preemption records in the distributed ledger that indicate that the network resources are preempted.
[0095] When the emergency situation ends, the network orchestrator may send requests to the relevant agents to release the preempted network resources. The agents may release the preempted network resources (reallocate the network resources to the mobile network operators) and store release records in the distributed ledger that indicate that the network resources are released (e.g., for tracking, charging / billing, and / or security reasons).
[0096] Figure 6 is a flow diagram of a method for determining and sharing sturdiness levels of network resources in a secure manner, according to some embodiments. In an embodiment, the method is performed by an agent of a mobile network operator.
[0097] The operations in the flow diagrams will be described with reference to the exemplary embodiments of the other figures. However, it should be understood that the operations of the flow diagrams can be performed by embodiments other than those discussed with reference to the other figures, and the embodiments discussed with reference to these other figures can perform operations different than those discussed with reference to the flow diagrams.
[0098] While the flow diagrams in the figures show a particular order of operations performed by certain embodiments, it should be understood that such order is provided by way of exampleand should not be regarded as limiting (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).
[0099] At operation 605, the agent obtains, for each of one or more network resources managed by the network operator, a set of parameter values of the network resource. In an embodiment, the set of parameter values of a network resource is obtained based on communicating with a network management system of the network operator. In an embodiment, the set of parameter values of a network resource indicate one or more of a vulnerability level of the network resource, a disaster risk of the network resource, the network resource’s proximity to borders, a security level of a location of the network resource, and an energy power autonomy level of the network resource.
[0100] At operation 610, the agent determines, for each of the one or more network resources, a sturdiness level of the network resource based on a sturdiness determination algorithm and the set of parameter values of the network resource. The sturdiness level of the network resource may indicate how resilient the network resource is against potential attacks or disasters. In an embodiment, the agent registers with the distributed ledger and receives the sturdiness determination algorithm from the distributed ledger. In an embodiment, the sturdiness determination algorithm determines a sturdiness level of a network resource based on calculating a weighted product of parameter values of the network resource.
[0101] At operation 615, the agent sends a request to a distributed ledger to store one or more sturdiness level records that indicate the sturdiness levels of the one or more network resources, wherein the one or more sturdiness level records are verified by participants of the distributed ledger using a consensus mechanism based on the sturdiness determination algorithm and the sets of parameter values of the one or more network resources before being stored in the distributed ledger. In an embodiment, the agent receives a public key from the distributed ledger (e.g., as part of a registration process with the distributed ledger), encrypts an identifier of a network resource using the public key, and includes the encrypted identifier of the network resource in a sturdiness level record that indicates a sturdiness level of the network resource. In an embodiment, the distributed ledger is a blockchain.
[0102] At operation 620, the agent determines whether it has received a request to preempt a network resource managed by the network operator. If the agent has not received a request to preempt a network resource managed by the network operator, the agent waits until it has received a request. If the agent has received a request to preempt a network resource managed by the network operator, the method proceeds to operation 625.
[0103] At operation 625, the agent preempts the network resource and sends a request to the distributed ledger to store a preemption record that indicates that the network resource ispreempted, wherein the preemption record is verified by the participants of the distributed ledger using the consensus mechanism before being stored in the distributed ledger. In an embodiment, the request to preempt the network resource indicates a configuration to apply to the network resource and the preempting involves applying the configuration to the network resource.
[0104] At operation 630, the agent determines whether it has received a request to release the network resource from preemption. If the agent has not received a request to release the network resource from preemption, the agent waits until it has received a request. If the agent has received a request to release the network resource from preemption, the method proceeds to operation 635.
[0105] At operation 635, the agent releases the network resource from preemption and send a request to the distributed ledger to store a release record that indicates that the network resource is released from preemption, wherein the release record is verified by participants of the distributed ledger using the consensus mechanism before being stored in the distributed ledger.
[0106] Operations 620-635 may be repeated for each preemption request.
[0107] In an embodiment, the agent generates a bill for usage of the preempted network resource based on accessing the preemption record and the release record.
[0108] Figure 7 is a flow diagram of a method for activating a temporary network, according to some embodiments. In an embodiment, the method is performed by a network orchestrator.
[0109] At operation 705, the network orchestrator determines whether a temporary network is to be activated. If the network orchestrator determines that a temporary network is not to be activated, the network orchestrator may wait until it determines that a temporary network is to be activated before proceeding to operation 710. If the network orchestrator determines that a temporary network is to be activated, the method proceeds to operation 710. In an embodiment, the determination that the temporary network is to be activated is based on network failures detected by the one or more network operators. The network failures may include one or more of a core network failure, a base station failure, and a transport network failure (e.g., failure of a mobile backhaul and / or a mobile fronthaul).
[0110] At operation 710, the network orchestrator obtains, from a distributed ledger, sturdiness levels of one or more network resources.
[0111] At operation 715, the network orchestrator designs a temporary network.
[0112] At operation 720, the network orchestrator sends one or more requests to one or more agents to preempt one or more network resources for use by the temporary network. In an embodiment, a request to preempt a network resource indicates a configuration to apply to the network resource.
[0113] At operation 725, the network orchestrator activates the temporary network.
[0114] At operation 730, the network orchestrator determines whether the temporary network is to be deactivated. If the network orchestrator determines that the temporary network is not to be deactivated, the network orchestrator may wait until it determines that the temporary network is to be deactivated before proceeding to operation 735. If the network orchestrator determines that the temporary network is to be deactivated, the method proceeds to operation 735.
[0115] At operation 735, the network orchestrator deactivates the temporary network.
[0116] At operation 740, the network orchestrator sends one or more requests to the one or more agents to release the one or more preempted network resources from preemption. The method may then proceed back to operation 705.
[0117] In an embodiment, the network orchestrator sends a request to an agent to update sturdiness levels of network resources in the distributed ledger.
[0118] Figure 8 is a diagram showing a mobile network that includes a network device that can implement embodiments.
[0119] As shown in the diagram, the mobile network includes base stations, user equipment (UE), and a network device (ND) 820.
[0120] Network device (ND) 820 may, in some embodiments, be an electronic device that can be communicatively connected to other electronic devices on the network (e.g., other network devices, user equipment devices (UEs), radio base stations, etc.). The base stations (depicted by radio towers in the diagram) may include radio access features that provide wireless radio network access to other electronic devices such as user equipment devices (UEs) (depicted by handheld devices in the diagram). For example, a base station may be an eNodeB in Long Term Evolution (LTE) or a NodeB in Wideband Code Division Multiple Access (WCDMA). A UE may be a device that can be used to access the mobile network over a wireless connection. For example, a UE may be a smartphone, laptop, or tablet.
[0121] As depicted in Figure 8, the example network device 820 comprises processor 811, memory 812, and interface 813. These components may work together to provide various network device functionality as disclosed herein.
[0122] Processor 811 may be a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, any other type of electronic circuitry, or any combination of one or more of the preceding. The processor 811 may comprise one or more processor cores. In particular embodiments, some or all of the functionality described herein as being provided by network device 820 may be implemented by processor 811 executing software instructions, either alone or in conjunction with other network device 820 components, such as memory 812.
[0123] Memory 812 may store code (which is composed of software instructions and which is sometimes referred to as computer program code or a computer program) and / or data using non-transitory machine-readable (e.g., computer-readable) media, such as machine-readable storage media (e.g., magnetic disks, optical disks, solid state drives, read only memory (ROM), flash memory devices, phase change memory) and machine-readable transmission media (e.g., electrical, optical, radio, acoustical or other form of propagated signals - such as carrier waves, infrared signals). For instance, memory 812 may comprise non-volatile memory containing code to be executed by processor 811. Where memory 812 is non-volatile, the code and / or data stored therein can persist even when the network device is turned off (when power is removed). In some instances, while network device 820 is turned on that part of the code that is to be executed by the processor(s) 811 may be copied from non-volatile memory into volatile memory (e.g., dynamic random access memory (DRAM), static random access memory (SRAM)) of network device 820.
[0124] Interface 813 may be used in the wired and / or wireless communication of signaling and / or data to or from network device 820. For example, interface 813 may perform any formatting, coding, or translating to allow network device 820 to send and receive data whether over a wired and / or a wireless connection. In some embodiments, interface 813 may comprise radio circuitry capable of receiving data from other devices in the network over a wireless connection and / or sending data out to other devices via a wireless connection. This radio circuitry may include transmitter(s), receiver(s), and / or transceiver(s) suitable for radiofrequency communication. The radio circuitry may convert digital data into a radio signal having the appropriate parameters (e.g., frequency, timing, channel, bandwidth, etc.). The radio signal may then be transmitted via antennas to the appropriate recipient(s). In some embodiments, interface 813 may comprise network interface controller(s) (NICs), also known as a network interface card, network adapter, local area network (LAN) adapter or physical network interface. The NIC(s) may facilitate in connecting the network device 820 to other devices allowing them to communicate via wire through plugging in a cable to a physical port connected to a NIC.
[0125] The components of network device 820 are each depicted as separate boxes located within a single larger box for reasons of simplicity in describing certain aspects and features of network device 820 disclosed herein. In practice however, one or more of the components illustrated in the example network device 820 may comprise multiple different physical elements (e.g., interface 813 may comprise terminals for coupling wires for a wired connection and a radio transceiver for a wireless connection).
[0126] The solution described herein may be implemented in the network device 820 by means of a computer program comprising instructions which, when executed on at least oneprocessor, cause the at least one processor to carry out the actions according to any of the above features and embodiments, where appropriate. For example, memory 812 may include an agent module 815 that when executed by processor 811 causes the ND 820 to perform agent operations, as described herein above. In an embodiment, memory 812 includes a network management system (NMS) module 836 that when executed by processor 811 causes the ND 820 to perform NMS operations, as described herein above.
[0127] While the modules are illustrated as being implemented in software stored in memory 812, other embodiments implement part or all of each of these modules in hardware.
[0128] Figure 9 is a diagram showing examples of how a ND 900 (e.g., ND 820) may be implemented in certain embodiments of the described solution including: 1) a special-purpose network device 902 that uses custom processing circuits such as application-specific integrated- circuits (ASICs) and a proprietary operating system (OS); and 2) a general purpose network device 904 that uses common off-the-shelf (COTS) processors and a standard OS which has been configured to provide one or more of the features or functions disclosed herein.
[0129] Special -purpose network device 902 includes hardware 910 comprising processor(s) 912, and interface 916, as well as memory 918 having stored therein software 920. In one embodiment, the software 920 implements the modules described with regard to the previous figures. During operation, the software 920 may be executed by the hardware 910 to instantiate a set of one or more software instance(s) 922. Each of the software instance(s) 922, and that part of the hardware 910 that executes that software instance (be it hardware dedicated to that software instance, hardware in which a portion of available physical resources (e.g., a processor core) is used, and / or time slices of hardware temporally shared by that software instance with others of the software instance(s) 922), form a separate virtual network element 930A-R. Thus, in the case where there are multiple virtual network elements 930A-R, each operates as one of the network devices from the preceding figures.
[0130] In an embodiment, software 920 includes a network orchestration module, which when executed by hardware 910, causes the special -purpose network device 902 to perform network orchestrator operations described herein above.
[0131] Returning to Figure 9, the example general purpose network device 904 includes hardware 940 comprising a set of one or more processor(s) 942 (which are often COTS processors) and interface 946, as well as memory 948 having stored therein software 950. During operation, the processor(s) 942 execute the software 950 to instantiate one or more sets of one or more applications 964A-R. While certain embodiments do not implement virtualization, alternative embodiments may use different forms of virtualization. For example, in certain alternative embodiments virtualization layer 954 represents the kernel of an operatingsystem (or a shim executing on a base operating system) that allows for the creation of multiple instances 962A-R called software containers that may each be used to execute one (or more) of the sets of applications 964A-R. In this embodiment, software containers 962A-R (also called virtualization engines, virtual private servers, or jails) are user spaces (typically a virtual memory space) that may be separate from each other and separate from the kernel space in which the operating system is run. In certain embodiments, the set of applications running in a given user space, unless explicitly allowed, may be prevented from accessing the memory of the other processes. In other such alternative embodiments virtualization layer 954 may represent a hypervisor (sometimes referred to as a virtual machine monitor (VMM)) or a hypervisor executing on top of a host operating system; and each of the sets of applications 964A-R may run on top of a guest operating system within an instance 962A-R called a virtual machine (which in some cases may be considered a tightly isolated form of software container that is run by the hypervisor). In certain embodiments, one, some or all of the applications are implemented as unikemel(s), which can be generated by compiling directly with an application only a Limited set of libraries (e.g., from a library operating system (LibOS) including drivers / Hbraries of OS services) that provide the particular OS sendees needed by the application. As a unikemel can be implemented to run directly on hardware 940, directly on a hypervisor (in which case the unikernel is sometimes described as running within a LibOS virtual machine), or in a software container, embodiments can be implemented fully with unikernels running directly on a hypervisor represented by virtualization layer 954, unikernels running within software containers represented by instances 962A-R, or as a combination of unikernels and the above-described techniques (e.g., unikemels and virtual machines both run directly on a hypervisor, unikernels and sets of applications that are run in different software containers).
[0132] The instantiation of the one or more sets of one or more applications 964A-R, as well as virtualization if implemented are collectively referred to as software instance(s) 952. Each set of applications 964 A-R, corresponding virtualization construct (e.g., instance 962 A-R) if implemented, and that part of the hardware 940 that executes them (be it hardware dedicated to that execution and / or time slices of hardware temporally shared by software containers 962A-R), forms a separate virtual network element(s) 960A-R.
[0133] The virtual network element(s) 960A-R perform similar functionality to the virtual network element(s) 930A-R. This virtualization of the hardware 940 is sometimes referred to as network function virtualization (NFV)). Thus, NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which could be located in for example data centers and customer premiseequipment (CPE). However, different embodiments may implement one or more of the software container(s) 962A-R differently. While embodiments are illustrated with each instance 962A-R corresponding to one VNE 960A-R, alternative embodiments may implement this correspondence at a finer level granularity; it should be understood that the techniques described herein with reference to a correspondence of instances 962A-R to VNEs also apply to embodiments where such a finer level of granularity and / or unikernels are used.
[0134] In an embodiment, software 950 includes a network orchestration module, which when executed by hardware 940, causes the general-purpose network device 904 to perform network orchestrator operations described herein above.
[0135] The third exemplary ND implementation in Figure 9 is a hybrid network device 906, which includes both custom ASICs / proprietary OS and COTS processors / standard OS in a single ND or a single card within an ND. In certain embodiments of such a hybrid network device, a platform virtual machine (VM), such as a VM that that implements the functionality of the special-purpose network device 902, could provide for para-virtualization to the hardware present in the hybrid network device 906.
[0136] Some portions of the preceding detailed descriptions have been presented in terms of algorithms and symbolic representations of transactions on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consi stent sequence of transactions leading to a desired result. The transactions are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
[0137] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as "processing" or "computing" or "calculating" or "determining" or "displaying" or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
[0138] The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method transactions. The required structure for a variety of these systems will appear from the description above. In addition, embodiments are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of embodiments as described herein.
[0139] An embodiment may be an article of manufacture in which a non-transitory machine- readable storage medium (such as microelectronic memory) has stored thereon instructions (e.g., computer code) which program one or more data processing components (generically referred to here as a “processor”) to perform the operations described above. In other embodiments, some of these operations might be performed by specific hardware components that contain hardwired logic (e.g., dedicated digital filter blocks and state machines). Those operations might alternatively be performed by any combination of programmed data processing components and fixed hardwired circuit components.
[0140] Throughout the description, embodiments have been presented through flow diagrams. It will be appreciated that the order of transactions and transactions described in these flow diagrams are only intended for illustrative purposes and not intended to be limiting. One having ordinary skill in the art would recognize that variations can be made to the flow diagrams.
[0141] In the foregoing specification, embodiments have been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the disclosure provided herein. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
Claims
CLAIMSWhat is claimed is:
1. A method performed by one or more network devices implementing an agent of a network operator, the method comprising: obtaining (605), for each of one or more network resources managed by the network operator, a set of parameter values of the network resource; determining (610), for each of the one or more network resources, a sturdiness level of the network resource based on a sturdiness determination algorithm and the set of parameter values of the network resource; and sending (615) a request to a distributed ledger to store one or more sturdiness level records that indicate the sturdiness levels of the one or more network resources, wherein the one or more sturdiness level records are verified by participants of the distributed ledger using a consensus mechanism based on the sturdiness determination algorithm and the sets of parameter values of the one or more network resources before being stored in the distributed ledger.
2. The method of claim 1, further comprising: receiving a request to preempt a network resource managed by the network operator; and responsive to receiving the request to preempt the network resource, preempting (625) the network resource and sending a request to the distributed ledger to store a preemption record that indicates that the network resource is preempted, wherein the preemption record is verified by participants of the distributed ledger using the consensus mechanism before being stored in the distributed ledger.
3. The method of claim 2, wherein the request to preempt the network resource indicates a configuration to apply to the network resource and the preempting involves applying the configuration to the network resource.
4. The method of claim 2, further comprising: receiving a request to release the network resource from preemption; and responsive to receiving the request to release the network resource from preemption, releasing (635) the network resource from preemption and sending a request to the distributed ledger to store a release record in the distributed ledger that indicates that the network resource is released from preemption, wherein therelease record is verified by participants of the distributed ledger using the consensus mechanism.
5. The method of claim 4, further comprising: generating a bill for usage of the preempted network resource based on accessing the preemption record and the release record.
6. The method of claim 1, wherein the set of parameter values of a network resource indicate one or more of a vulnerability level of the network resource, a disaster risk of the network resource, the network resource’s proximity to borders, a security level of a location of the network resource, and an energy power autonomy level of the network resource.
7. The method of claim 1, wherein the set of parameter values of a network resource is obtained based on communicating with a network management system of the network operator.
8. The method of claim 1, further comprising: registering with the distributed ledger; and receiving the sturdiness determination algorithm from the distributed ledger.
9. The method of claim 8, further comprising: receiving a public key from the distributed ledger; encrypting an identifier of a network resource using the public key; and including the encrypted identifier of the network resource in a sturdiness level record that indicates a sturdiness level of the network resource.
10. The method of claim 1, wherein the distributed ledger is a blockchain.
11. The method of claim 1, wherein the sturdiness level of the network resource indicates how resilient the network resource is against potential attacks.
12. The method of claim 1, wherein the sturdiness determination algorithm determines a sturdiness level of a network resource based on calculating a weighted product of parameter values of the network resource.
13. A method performed by one or more network devices implementing a network orchestrator, the method comprising: obtaining (710), from a distributed ledger, sturdiness levels of one or more network resources; designing (715) a temporary network;sending (720) one or more requests to one or more agents to preempt one or more network resources for use by the temporary network in response to a determination (705) that the temporary network is to be activated; and activating (725) the temporary network.
14. The method of claim 13, further comprising: sending (740) one or more requests to the one or more agents to release the one or more preempted network resources from preemption in response to a determination (730) that the temporary network is to be deactivated.
15. The method of claim 13, wherein a request to preempt a network resource indicates a configuration to apply to the network resource.
16. The method of claim 13, further comprising: sending a request to an agent to update sturdiness levels of network resources in the distributed ledger.
17. The method of claim 13, wherein the determination that the temporary network is to be activated is based on network failures detected by one or more network operators, wherein the network failures include one or more of: a core network failure, a base station failure, and a transport network failure.
18. A non-transitory machine-readable medium comprising computer program code which when executed by a network device functioning as an agent of a network operator carries out the method steps of any of claims 1-12.
19. A non-transitory machine-readable medium comprising computer program code which when executed by a network device functioning as a network orchestrator carries out the method steps of any of claims 13-17.
20. A network device (820) to function as an agent of a network operator, the network device comprising: one or more processors (811); and a non-transitory machine-readable storage medium (812) that stores instructions, which when executed by the one or more processors, causes the agent to perform the method steps of any one of claims 1-12.
21. A network device (900) to function as a network orchestrator, the network device comprising: one or more processors (942); and a non-transitory machine-readable storage medium (948) that stores instructions, which when executed by the one or more processors, causes the network orchestrator to perform the method steps of any one of claims 13-17.
Citation Information
Patent Citations
Cooperative preemption in a distributed multi-tenant resource pool
US11128701B1
The internet of things
US20190349426A1
Methods and devices for resource sharing using smart contracts
US20220166667A1
Transaction platforms where systems include sets of other systems
WO2023097026A2
Cited By
Planning and orchestrating a resilient temporary network
WO2025211996A1
