FIELD

[0001] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to configuring closed loop components.

BACKGROUND

[0002] In certain wireless communications networks, closed loop systems may be used. In such networks, components of the closed loop systems may need to have a change in configuration.

BRIEF SUMMARY

[0003] Methods for configuring closed loop components are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes receiving, at a first network device, a request for a timing characteristic of a closed loop process from a consumer. In some embodiments, the method includes determining, at the first network device, a plurality of closed loop components of the closed loop process. In certain embodiments, the method includes transmitting, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components. In various embodiments, the method includes receiving, at the first network device, a response to the request. The response includes the configuration information.

[0004] One apparatus for configuring closed loop components includes a first network device. In some embodiments, the apparatus includes a receiver that receives, at the first network device, a request for a timing characteristic of a closed loop process from a consumer. In various embodiments, the apparatus includes a processor that determines, at the first network device, a plurality of closed loop components of the closed loop process. In certain embodiments, the apparatus includes a transmitter that transmits, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components. In some embodiments, the receiver receives, at the first network device, a response to the request, and the response includes the configuration information.

[0005] Another embodiment of a method for configuring closed loop components includes receiving, at a first network device, a request to change a timing characteristic of a closed loop process from a consumer. In some embodiments, the method includes determining, at the first network device, a plurality of closed loop components of the closed loop process. In certain embodiments, the method includes transmitting, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components. In various embodiments, the method includes receiving, at the first network device, a response to the request. The response includes the configuration information.

[0006] Another apparatus for configuring closed loop components includes a first network device. In some embodiments, the apparatus includes a receiver that receives, at the first network device, a request to change a timing characteristic of a closed loop process from a consumer. In various embodiments, the apparatus includes a processor that determines, at the first network device, a plurality of closed loop components of the closed loop process. In certain embodiments, the apparatus includes a transmitter that transmits, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components. In some embodiments, the receiver receives, at the first network device, a response to the request, and the response includes the configuration information.

[0007] A further embodiment of a method for configuring closed loop components includes receiving, at a second network device, configuration information from a first network device for determining a timing characteristic. In some embodiments, the method includes determining, at the second network device, the timing characteristic of a plurality of closed loop components of a closed loop process. In certain embodiments, the method includes transmitting, from the second network device, the timing characteristic to the first network device.

[0008] A further apparatus for configuring closed loop components includes a second network device. In some embodiments, the apparatus includes a receiver that receives, at the second network device, configuration information from a first network device for determining a timing characteristic. In various embodiments, the apparatus includes a processor that determines, at the second network device, the timing characteristic of a plurality of closed loop components of a closed loop process. In certain embodiments, the apparatus includes a transmitter that transmits, from the second network device, the timing characteristic to the first network device.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which: [0010] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for configuring closed loop components;

[0011] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for configuring closed loop components;

[0012] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for configuring closed loop components;

[0013] Figure 4 is a schematic block diagram illustrating one embodiment of timing related to a closed loop behavior;

[0014] Figure 5 is a schematic block diagram illustrating one embodiment of component timing behavior and interaction in a closed loop system;

[0015] Figure 6 is a schematic block diagram illustrating one embodiment of communications in a closed loop system;

[0016] Figure 7 is a schematic block diagram illustrating another embodiment of communications in a closed loop system;

[0017] Figure 8 is a flow chart diagram illustrating one embodiment of a method for configuring closed loop components;

[0018] Figure 9 is a flow chart diagram illustrating another embodiment of a method for configuring closed loop components; and

[0019] Figure 10 is a flow chart diagram illustrating a further embodiment of a method for configuring closed loop components.

DETAILED DESCRIPTION

[0020] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0021] Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[0022] Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0023] Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

[0024] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0025] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc readonly memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0026] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”) or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0027] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0028] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0029] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0030] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0031] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0032] The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0033] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0034] Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0035] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0036] Figure 1 depicts an embodiment of a wireless communication system 100 for configuring a digital twin for software testing. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104 (e.g., base units). Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0037] In one embodiment, the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. In some embodiments, the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via uplink (“UL”) and/or DL communication signals 106. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication. The remote units 102 may include one or more software applications 110.

[0038] The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to and/or may include one or more of an access point, an access terminal, a base, a base station, a location server, a core network (“CN”), a radio network entity, a Node-B, an evolved node-B (“eNB”), a 5G node-B (“gNB”), a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an access point (“AP”), new radio (“NR”), a network entity, an access and mobility management function (“AMF”), a unified data management (“UDM”), a unified data repository (“UDR”), a UDM/UDR, a policy control function (“PCF”), a radio access network (“RAN”), a network slice selection function (“NSSF”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-third generation partnership project (“3GPP”) gateway function (‘TNGF”), a network function, a digital twin creation service producer, a testing management service producer, or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0039] In one implementation, the wireless communication system 100 is compliant with NR protocols, 5G Core, 5G Management and 5G Applications standardized in 3GPP, wherein the network unit 104 transmits using an orthogonal frequency division multiplexing (“OFDM”)modulation scheme on the downlink (“DL”) and the remote units 102 transmit on the UL using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, institute of electrical and electronics engineers (“IEEE”) 802. 11 variants, global system for mobile communications (“GSM”), general packet radio service (“GPRS”), universal mobile telecommunications system (“UMTS”), long term evolution (“LTE”) variants, code division multiple access 2000 (“CDMA2000”), Bluetooth®, ZigBee, Sigfoxx, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0040] The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.

[0041] The network units 104 may be part of a radio access network 108. Moreover, the radio access network 108 may communicate with a mobile core network 112. Further, the mobile core network 112 may include one or more network functions, such as UPFs 114, an AMF 116, an SMB 118, a PCT 120, a UDM 122, a network repository function (“NRF”) 124, an NSSF 126, and a network data analytics function (“NWDAF”) 128. The mobile core network 112 and/or the radio access network 108 are managed by the operations and management system (“0AM”) 130.

[0042] In various embodiments, a network unit 104 may receive, at a first network device, a request for a timing characteristic of a closed loop process from a consumer. In some embodiments, the network unit 104 may determine, at the first network device, a plurality of closed loop components of the closed loop process. In certain embodiments, the network unit 104 may transmit, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components. In various embodiments, the network unit 104 may receive, at the first network device, a response to the request. The response includes the configuration information. Accordingly, the network unit 104 may be used for configuring closed loop components.

[0043] In certain embodiments, a network unit 104 may receive, at a first network device, a request to change a timing characteristic of a closed loop process from a consumer. In some embodiments, the network unit 104 may determine, at the first network device, a plurality of closed loop components of the closed loop process. In certain embodiments, the network unit 104 may transmit, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components. In various embodiments, the network unit 104 may receive, at the first network device, a response to the request. The response includes the configuration information. Accordingly, the network unit 104 may be used for configuring closed loop components.

[0044] In some embodiments, a network unit 104 may receive, at a second network device, configuration information from a first network device for determining a timing characteristic. In some embodiments, the network unit 104 may determine, at the second network device, the timing characteristic of a plurality of closed loop components of a closed loop process. In certain embodiments, the network unit 104 may transmit, from the second network device, the timing characteristic to the first network device. Accordingly, the network unit 104 may be used for configuring closed loop components.

[0045] Figure 2 depicts one embodiment of an apparatus 200 that may be used for configuring closed loop components. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208. [0046] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0047] The memory 204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

[0048] The input device 206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0049] The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, a liquid crystal display (“UCD”), a light emitting diode (“FED”) display, an organic light emitting diode (“OEED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0050] In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.

[0051] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

[0052] Figure 3 depicts one embodiment of an apparatus 300 that may be used for configuring closed loop components. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As may be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0053] In certain embodiments, the receiver 312 receives, at the first network device, a request for a timing characteristic of a closed loop process from a consumer. In various embodiments, the processor 302 determines, at the first network device, a plurality of closed loop components of the closed loop process. In certain embodiments, the transmitter 310 transmits, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components. In some embodiments, the receiver 312 receives, at the first network device, a response to the request, and the response includes the configuration information.

[0054] In some embodiments, the receiver 312 receives, at the first network device, a request to change a timing characteristic of a closed loop process from a consumer. In various embodiments, the processor 302 determines, at the first network device, a plurality of closed loop components of the closed loop process. In certain embodiments, the transmitter 310 transmits, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components. In some embodiments, the receiver 312 receives, at the first network device, a response to the request, and the response includes the configuration information.

[0055] In various embodiments, the receiver 312 receives, at the second network device, configuration information from a first network device for determining a timing characteristic. In various embodiments, the processor 302 determines, at the second network device, the timing characteristic of a plurality of closed loop components of a closed loop process. In certain embodiments, the transmitter 310 transmits, from the second network device, the timing characteristic to the first network device.

[0056] In certain embodiments, closed loops are used for a collection of components. Components may be stages of a closed loop or other components such as a knowledge sharing part of a closed loop. In some embodiments, all components of a closed loop are implemented as management service producers. It should be noted that various behavioral aspects of a closed loop, particularly related to time, may depend on those components. There may not be a way to uniformly configure components.

[0057] In various embodiments, timing aspects of a closed loop may be configured. In certain embodiments, an impact time may refer to a time it takes to perceive via performance key performance indicators (“KPIs”) an effect of a self organizing network (“SON”) configuration in a network. In some embodiments, a reaction time and closed loop periods may be defined. In various embodiments, timing aspects of a closed loop may be detected and influenced.

[0058] In certain embodiments, timing may be important for understanding behaviors of various closed loops in a system and may facilitate ensuring proper behavior of an automation system. For example, if an ultra-reliable low-latency communication (“URLLC”) service requires a fast response time for failure of a closed loop (“CL”) responsible for monitoring and configuring failure of the URLLC service, it may have a worst case response time less than a downtime acceptable for the URLLC service. In another example, a time period of a CL may be relevant for understanding interactions and/or conflicts between CLs.

[0059] In some embodiments, open loops involve an operator to be part of at least one of the stages in the loop, while in a closed loop stage the operator only defines a goal for the closed control loop and the loop once configured runs automatically. Various embodiments of control loops attempt to control a status of managed objects trying to keep them as close as possible to an operator specified goal if a goal is available. It should be noted that closed loops may be complex entities or simple entities. [0060] In certain embodiments, there may be a simple policy based closed loop where a KPI threshold may be configured over monitoring data to activate pre-configured policies that issue an execution command for a managed entity. In some embodiments, a closed loop system may include an analytics phase and a decision phase (e.g., which may be based on some artificial intelligence (“Al”) and machine learning based decision making). In various embodiments, there may be fast and slow closed loops (e.g., the fast closed loop works based on pre-defined policybased decisions and the slow closed loop analyzes the effect of the decisions on the network and may execute changes in how the fast closed loop takes its decisions). Such embodiments may be considered as a set of two distinct loops with the slow closed loop (e.g., outer loop) considering the fast loop’s (e.g., inner loop) decision making as a managed entity.

[0061] In certain embodiments, collection and ordering of components within a CL may be referred to as a chain that forms a closed loop. Moreover, the exchange of data and control messages between the various components of the CL chain may be referred to as a flow in the CL. There may be multiple flows running concurrently in a CL chain. Together the CL chain and how they determine the flow of messages between the CL components in the chain determines the behavior of the CL.

[0062] In some embodiments, a CL is a “chain” of management services (“MnSs”) or MnS producers. In various embodiments, an MnS component type B may refer to management information represented by information models representing managed entities. Moreover, a MnS component type B may also be called a network resource model (“NRM”). In certain embodiments, MnS component type B examples include various network resource models.

[0063] In some embodiments, an MnS component type C includes performance information of a managed entity and fault information of the managed entity. Examples of a management service component type C may include: 1) alarm information; and/or 2) performance data.

[0064] In various embodiments, an MnS producer may be described as a set of meta data called an MnS producer profile. The profile may hold information about the supported MnS components and their version numbers. This may also include information about support of optional features. For example, a read operation on a complete subtree of managed object instances may support applying filters to a scoped set of objects as an optional feature. In certain embodiments, an MnS profile may include information about whether filtering is supported.

[0065] In some embodiments, an MnS includes: 1) a MnS component type A; and 2a) an MnS component type B; or 2b) an MnS component type B and a MnS component type C. [0066] In various embodiments, instances of management services carry information about specified management service components in a metadata attributes.

[0067] In certain embodiments, the following definitions apply: 1) a response time - defined as the time it takes for a CL to react to an issue in a system that would fall under its responsibility (e.g., an issue that is likely to adversely affect a goal of the CL); 2) a period - an inherent time interval used by the closed loop to check whether network performance is suitable for its goals - even if the closed loop is triggered by events it still has a period, as those events are only detected at certain time periods by an event detection system; and/or 3) an execution time - this refers to a sum of time that a components need to run to process data monitored in the network - the execution time is the sum of the execution time of the components of the CL that are part of a direct response - the other components are not a direct part of the CL. As used herein, all components of a closed loop (e.g., including stages) are referred to as components.

[0068] In some embodiments, a closed loop may have a fixed measurable period irrespective of its design. This fixed measurable period may act like a quantization of a continuous time in which the system operates with respect to the closed loop. Events that happen between two consecutive periods may essentially be simultaneous in the eyes of a closed loop - unless they have an internal timestamp that can order them.

[0069] Figure 4 is a schematic block diagram illustrating one embodiment of timing 400 related to a closed loop behavior. The timing 400 includes a plurality of time periods 401 of a closed loop system. A first event 402 (e.g., Event 1), a second event 404 (e.g., Event 2), and a third event 406 (e.g., Event 3) are illustrated. As may be appreciated, the third event 406 may cause an impact on a CL goal. A time 408 is the first time that the CL can respond to the third event 406. Further, a time 410 may be a time at which the CL executes an Action A in response to the third event 406. Moreover, a time 412 may be a time at which the effect of Action A is measurable in the network.

[0070] Figure 5 is a schematic block diagram illustrating one embodiment of component timing behavior in a closed loop system 500. The closed loop system 500 includes a component A 502 (e.g., performance monitor), a component B 504 (e.g., analytics timer triggered read from A), a component C 506 (e.g., a decision that waits for events from component B), and a component D 508 (e.g., provisioning and or orchestration MnS - with an event triggered from C).

[0071] The times in the closed loop system 500 are determined by how the components in the closed loop are stitched together and what each of their exact configurations is. The component A 502 has a period of t seconds and the component B 504 has a period of T (e.g., much greater the t) seconds. Further, the component C 506 has a listener which only reacts to certain event publications from the component B 504. Moreover, the component D 508 similarly listens to publications from the component C 506. Component A 502 is for monitoring, component B 504 is for analytics, component C 506 is a decision phase that reacts to the analytics insight of component B 504, and component D 508 is an execution engine orchestrating the decisions taken by component C 506.

[0072] This closed loop reads in data at a period of t seconds because that is the period at which component A 502 collects performance KPIs from the network. Component B 504, however, only reads the data every T seconds; therefore, the period of the loop cannot be t but is rather at best T seconds. Component C 506 reacts to component B 504 and, therefore, automatically acquires the period of component B 504 and the same is true for component D 508. Therefore, the overall closed loop has a period of T seconds. The period of a closed loop may be defined as the highest period of its components. At least one component of the closed loop, in particular performance monitoring, may always have a period.

[0073] The worst-case reaction time of the closed loop system 500 (e.g., if there is a need to react) is at worst T seconds plus processing time of the components. However, calculating the worst-case reaction time may depend on how the closed loop components are linked. For Figure 5, if T < t, then the worst case would be t+T.

[0074] In certain embodiments, if component B 504 is configured to analyze data every T/2 seconds, the time period of the closed loop drops to T/2 as long as T/2 > t. If the component B 504 is configured to a time t’ less then t, then the new time period of the closed loop is t.

[0075] In some embodiments, changing a time period may be simple for a closed loop analyzing entity to analyze the closed loop components and configure the appropriate component with a new time period. In various embodiments, a change in a time period affects a worst case response time.

[0076] In various embodiments, the time-period of component B 504 cannot be changed. In such embodiments, another way of changing a time period of the closed loop is to configure component B 504 to listen to publications from component A 502. In such embodiments, component B 504 works on a notification from component A 504 and, therefore, acquires the time period of component A 504. Then the closed loop has a time period of t, so the closed loop is limited by two choices to have a time period of t or T. In such embodiments, a worst-case response time of the CL may be changed. Moreover, an execution time of the CL can also be changed with by changing the component, or some configuration of the component (e.g., using a different analytics model that changes the execution time of the component). [0077] In a first embodiment, configurations of components of a closed loop may be made by an entity that can manage closed loops. Various portions of the first embodiments are shown in Figure 6 and Figure 7.

[0078] Figure 6 is a schematic block diagram illustrating one embodiment of communications in a closed loop system 600. The system includes a CL MnS producer 602 (e.g., CL management entity), a CL time analysis service producer 604, and one or more CL components 606 (e.g., management function (“MnF”) or another MnS producer).

[0079] In a first communication 608, an authorized consumer may request time analysis details for any closed loop (e.g., request for the time period and/or worst case response of a CL). In the request, a way of identifying a closed loop may be provided.

[0080] The CL MnS producer 602 identifies 610 CL components (e.g., the MnS producers that form the CL). The identification may be made using a database lookup.

[0081] In a second communication 612, the CL MnS producer 602 fetches configurations with respect to the CL from each of the CL components.

[0082] In a third communication 614, each component replies with the configurations it has with respect to the particular CL. The configuration information may include: 1) a period of the component if it has one; 2) which other component it responds to as part of the closed loop; 3) which other components listen to this component as part of the closed loop; and/or 4) any other component or inter component information relevant to calculating the period of the closed loop.

[0083] In a fourth communication 616, the data (e.g., configuration information) is sent for time analysis to the CL time analysis service producer 604.

[0084] In certain embodiments, steps 610, 612, and 614 may be performed by the CL time analysis service producer 604.

[0085] The CL time analysis service producer 604 analyzes 618 the collected details and calculates a time period, a worst response time, an average response time with standard deviations, and so forth relevant to the CL.

[0086] In a fifth communication 620 (e.g., optional), the CL time analysis service producer 604 may include an analytics engine, and work by fetching historical data in relation to the CL, particularly for average and standard deviations of response time.

[0087] In a sixth communication 622, the calculated time details are provided to the CL MnS producer 602.

[0088] In a seventh communication 624, the CL MnS producer 602 provides the information (e.g., time details of the loop) to the requesting consumer of step 608. The information returned to the requesting customer may include: 1) a period of a closed loop; 2) a worst-case response time of a closed loop; 3) an impact time of a closed loop; 4) a way a closed loop is constructed; and/or 5) possibilities for changes to any of the information returned. In certain embodiments, any of the CL MnS producers 602 may be co-located with any other MnS producer. In particular, the CL time analysis service producer 604 may be located with the CL MnS producer 602.

[0089] Figure 7 is a schematic block diagram illustrating another embodiment of communications in a closed loop system 700 (e.g., including an ability to configure the timing of the closed loop system 700). The system includes a CL MnS producer 702 (e.g., CL management entity), a CL time analysis service producer 704, and one or more CL components 706 (e.g., management function (“MnF”) or another MnS producer).

[0090] In a first communication 708, the CL MnS producer 702 receives a request for configuring a new time behavior for a closed loop (e.g., a new time period). The request may include a range of acceptable values (e.g., less than 5 second time period).

[0091] The CL MnS producer 702 identifies 710 CL components (e.g., the MnS producers that form the CL). The identification may be made using a database lookup.

[0092] In a second communication 712, the CL MnS producer 702 fetches configurations with respect to the CL from each of the CL components.

[0093] In a third communication 714, each component replies with the configurations it has with respect to the particular CL. The configuration information may include: 1) a period of the component if it has one; 2) which other component it responds to as part of the closed loop; 3) which other components listen to this component as part of the closed loop; and/or 4) any other component or inter component information relevant to calculating the period of the closed loop.

[0094] In a fourth communication 716, the data (e.g., configuration information) is sent for time analysis to the CL time analysis service producer 704. In some embodiments, the fourth communication 716 includes a new configuration for the time behavior of the CL.

[0095] In certain embodiments, steps 710, 712, and 714 may be performed by the CL time analysis service producer 704.

[0096] The CL time analysis service producer 704 analyzes 718 the collected details and calculates a time period, a worst response time, an average response time with standard deviations, and so forth relevant to the CL.

[0097] In some embodiments, if a configuration is available, the requested time may be matched.

[0098] In a fifth communication 720, the configuration of the components that provide the new time behavior of the CL is performed. This may include any combination of: 1) the change in time period of the component (e.g., changing the time period of component B to read the output of component A); and/or a change in the way one component listens and/or responds to another component in the chain of the CL.

[0099] In a sixth communication 722, the response of the configuration may be transmitted (e.g., success or failure). The reason for failure may also be included.

[0100] In a seventh communication 724, a response to step 716 may be transmitted and may include a configuration of the CL.

[0101] In an eighth communication 726, a response to the request to change the timing behavior of the CL is made (e.g., success or failure). The success may include new timing behavior.

[0102] In various embodiments, if a configuration is available, only an alternate configuration is possible.

[0103] In an optional nineth communication 728, since the configuration requested in step 716 is not possible, a response is provided. The response may include a failure and may include an alternate configuration. For example, if the requested time period of 5 seconds is not possible but an alternate of 3 seconds is, the request returns a failure with a possible alternate of 3 seconds.

[0104] In an optional tenth communication 730, a response is provided to the consumer. The response may include the same details as step 720.

[0105] In an optional eleventh communication 732, the consumer may select one of the provided alternatives as a configuration, when provided in step 722.

[0106] In an optional twelfth communication 734, an alternate time period is requested with a transmission to the CL time analysis MnS producer 704.

[0107] In an optional thirteenth communication 736, the configuration of the component relating to the alternate time period is performed.

[0108] In an optional fourteenth communication 738, the response including success or failure of the configuration is provided.

[0109] In an optional fifteenth communication 740, the response including success or failure of the configuration is provided.

[0110] In an optional sixteenth communication 742, the response including success or failure of the configuration is provided.

[0111] Figure 8 is a flow chart diagram illustrating one embodiment of a method 800 for configuring closed loop components. In some embodiments, the method 800 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 800 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0112] In various embodiments, the method 800 includes receiving 802, at a first network device, a request for a timing characteristic of a closed loop process from a consumer. In some embodiments, the method 800 includes determining 804, at the first network device, a plurality of closed loop components of the closed loop process. In certain embodiments, the method 800 includes transmitting 806, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components. In various embodiments, the method 800 includes receiving 808, at the first network device, a response to the request. The response includes the configuration information.

[0113] In certain embodiments, the first network device comprises a closed loop management service producer, a closed loop management entity, or a combination thereof. In some embodiments, the method 800 further comprises transmitting, from the first network device, the configuration information of the at least one closed loop component of the plurality of closed loop components to a second network device for determining the timing characteristic.

[0114] Figure 9 is a flow chart diagram illustrating one embodiment of a method 900 for configuring closed loop components. In some embodiments, the method 900 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 900 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0115] In various embodiments, the method 900 includes receiving 902, at a first network device, a request to change a timing characteristic of a closed loop process from a consumer. In some embodiments, the method 900 includes determining 904, at the first network device, a plurality of closed loop components of the closed loop process. In certain embodiments, the method 900 includes transmitting 906, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components. In various embodiments, the method 900 includes receiving 908, at the first network device, a response to the request. The response includes the configuration information.

[0116] In certain embodiments, the first network device comprises a closed loop management service producer, a closed loop management entity, or a combination thereof. In some embodiments, the method 900 further comprises transmitting, from the first network device, the configuration information of the at least one closed loop component of the plurality of closed loop components to a second network device for determining changes to the configuration information of the at least one closed loop component of the plurality of closed loop components to change the timing characteristic of the closed loop. In various embodiments, the method 900 further comprises receiving, at the first network device, information indicating the changes to the configuration information of the at least one closed loop component of the plurality of closed loop components to change the timing characteristic of the closed loop.

[0117] In one embodiment, the method 900 further comprises transmitting a response to the consumer indicating that the timing characteristic of the closed loop is changed. In certain embodiments, the method 900 comprises further comprises changing the configuration information of the at least one closed loop component of the plurality of closed loop components based on the determined changes and configuring a different behavior for the plurality of closed loop components. In some embodiments, the different behavior comprises changing a timing behavior or an interaction between a plurality of the at least one component of the plurality of components.

[0118] Figure 10 is a flow chart diagram illustrating one embodiment of a method 1000 for configuring closed loop components. In some embodiments, the method 1000 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 1000 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0119] In various embodiments, the method 1000 includes receiving 1002, at a second network device, configuration information from a first network device for determining a timing characteristic. In some embodiments, the method 1000 includes determining 1004, at the second network device, the timing characteristic of a plurality of closed loop components of a closed loop process. In certain embodiments, the method 1000 includes transmitting 1006, from the second network device, the timing characteristic to the first network device.

[0120] In certain embodiments, the first network device comprises a closed loop management service producer, a closed loop management entity, or a combination thereof. In some embodiments, the configuration information comprises configuration information corresponding to the plurality of closed loop components. In various embodiments, the second network device comprises a closed loop time analysis service producer.

[0121] In one embodiment, the method 1000 further comprises receiving, at the second network device, a request to change the timing configuration from the first network device. In certain embodiments, the method 1000 further comprises transmitting, from the second network device an updated configuration to the plurality of closed loop components to change the timing configuration of the plurality of closed loop components. In some embodiments, the method 1000 further comprises receiving, at the second network device, a response from the plurality of closed loop components indicating that the updated configuration has been applied to change the timing configuration.

[0122] In various embodiments, the method 1000 further comprises transmitting, from the second network device, information indicating to the first network device that the timing configuration is changed. In one embodiment, changing the timing configuration comprises configuring a different behavior for the plurality of closed loop components. In certain embodiments, the different behavior comprises a timing of at least one component of the plurality of components.

[0123] In one embodiment, an apparatus comprises a first network device. The apparatus further comprises: a receiver that receives, at the first network device, a request for a timing characteristic of a closed loop process from a consumer; a processor that determines, at the first network device, a plurality of closed loop components of the closed loop process; and a transmitter that transmits, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components, wherein the receiver receives, at the first network device, a response to the request, and the response comprises the configuration information.

[0124] In certain embodiments, the first network device comprises a closed loop management service producer, a closed loop management entity, or a combination thereof.

[0125] In some embodiments, the transmitter transmits, from the first network device, the configuration information of the at least one closed loop component of the plurality of closed loop components to a second network device for determining the timing characteristic.

[0126] In one embodiment, a method of a first network device comprises: receiving, at the first network device, a request for a timing characteristic of a closed loop process from a consumer; determining, at the first network device, a plurality of closed loop components of the closed loop process; transmitting, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components; and receiving, at the first network device, a response to the request, wherein the response comprises the configuration information.

[0127] In certain embodiments, the first network device comprises a closed loop management service producer, a closed loop management entity, or a combination thereof. [0128] In some embodiments, the method further comprises transmitting, from the first network device, the configuration information of the at least one closed loop component of the plurality of closed loop components to a second network device for determining the timing characteristic.

[0129] In one embodiment, an apparatus comprises a first network device. The apparatus further comprises: a receiver that receives, at the first network device, a request to change a timing characteristic of a closed loop process from a consumer; a processor that determines, at the first network device, a plurality of closed loop components of the closed loop process; and a transmitter that transmits, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components, wherein the receiver receives, at the first network device, a response to the request, and the response comprises the configuration information.

[0130] In certain embodiments, the first network device comprises a closed loop management service producer, a closed loop management entity, or a combination thereof.

[0131] In some embodiments, the transmitter transmits, from the first network device, the configuration information of the at least one closed loop component of the plurality of closed loop components to a second network device for determining changes to the configuration information of the at least one closed loop component of the plurality of closed loop components to change the timing characteristic of the closed loop.

[0132] In various embodiments, the receiver receives, at the first network device, information indicating the changes to the configuration information of the at least one closed loop component of the plurality of closed loop components to change the timing characteristic of the closed loop.

[0133] In one embodiment, the transmitter transmits a response to the consumer indicating that the timing characteristic of the closed loop is changed.

[0134] In certain embodiments, the processor changes the configuration information of the at least one closed loop component of the plurality of closed loop components based on the determined changes and configuring a different behavior for the plurality of closed loop components.

[0135] In some embodiments, the different behavior comprises changing a timing behavior or an interaction between a plurality of the at least one component of the plurality of components.

[0136] In one embodiment, a method of a first network device comprises: receiving, at the first network device, a request to change a timing characteristic of a closed loop process from a consumer; determining, at the first network device, a plurality of closed loop components of the closed loop process; transmitting, from the first network device, a request to at least one closed loop component of the plurality of closed loop components for configuration information corresponding to the at least one closed loop component of the plurality of closed loop components; and receiving, at the first network device, a response to the request, wherein the response comprises the configuration information.

[0137] In certain embodiments, the first network device comprises a closed loop management service producer, a closed loop management entity, or a combination thereof.

[0138] In some embodiments, the method further comprises transmitting, from the first network device, the configuration information of the at least one closed loop component of the plurality of closed loop components to a second network device for determining changes to the configuration information of the at least one closed loop component of the plurality of closed loop components to change the timing characteristic of the closed loop.

[0139] In various embodiments, the method further comprises receiving, at the first network device, information indicating the changes to the configuration information of the at least one closed loop component of the plurality of closed loop components to change the timing characteristic of the closed loop.

[0140] In one embodiment, the method further comprises transmitting a response to the consumer indicating that the timing characteristic of the closed loop is changed.

[0141] In certain embodiments, the method comprises further comprises changing the configuration information of the at least one closed loop component of the plurality of closed loop components based on the determined changes and configuring a different behavior for the plurality of closed loop components.

[0142] In some embodiments, the different behavior comprises changing a timing behavior or an interaction between a plurality of the at least one component of the plurality of components.

[0143] In one embodiment, an apparatus comprises a second network device. The apparatus further comprises: a receiver that receives, at the second network device, configuration information from a first network device for determining a timing characteristic; a processor that determines, at the second network device, the timing characteristic of a plurality of closed loop components of a closed loop process; and a transmitter that transmits, from the second network device, the timing characteristic to the first network device.

[0144] In certain embodiments, the first network device comprises a closed loop management service producer, a closed loop management entity, or a combination thereof. [0145] In some embodiments, the configuration information comprises configuration information corresponding to the plurality of closed loop components.

[0146] In various embodiments, the second network device comprises a closed loop time analysis service producer.

[0147] In one embodiment, the receiver receives, at the second network device, a request to change the timing configuration from the first network device.

[0148] In certain embodiments, the transmitter transmits, from the second network device an updated configuration to the plurality of closed loop components to change the timing configuration of the plurality of closed loop components.

[0149] In some embodiments, the receiver receives, at the second network device, a response from the plurality of closed loop components indicating that the updated configuration has been applied to change the timing configuration.

[0150] In various embodiments, the transmitter transmits, from the second network device, information indicating to the first network device that the timing configuration is changed.

[0151] In one embodiment, changing the timing configuration comprises configuring a different behavior for the plurality of closed loop components.

[0152] In certain embodiments, the different behavior comprises a timing of at least one component of the plurality of components.

[0153] In one embodiment, a method of a second network device comprises: receiving, at the second network device, configuration information from a first network device for determining a timing characteristic; determining, at the second network device, the timing characteristic of a plurality of closed loop components of a closed loop process; and transmitting, from the second network device, the timing characteristic to the first network device.

[0154] In certain embodiments, the first network device comprises a closed loop management service producer, a closed loop management entity, or a combination thereof.

[0155] In some embodiments, the configuration information comprises configuration information corresponding to the plurality of closed loop components.

[0156] In various embodiments, the second network device comprises a closed loop time analysis service producer.

[0157] In one embodiment, the method further comprises receiving, at the second network device, a request to change the timing configuration from the first network device.

[0158] In certain embodiments, the method further comprises transmitting, from the second network device an updated configuration to the plurality of closed loop components to change the timing configuration of the plurality of closed loop components. [0159] In some embodiments, the method further comprises receiving, at the second network device, a response from the plurality of closed loop components indicating that the updated configuration has been applied to change the timing configuration.

[0160] In various embodiments, the method further comprises transmitting, from the second network device, information indicating to the first network device that the timing configuration is changed.

[0161] In one embodiment, changing the timing configuration comprises configuring a different behavior for the plurality of closed loop components.

[0162] In certain embodiments, the different behavior comprises a timing of at least one component of the plurality of components.

[0163] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.