WO2018138553A1 - Procédés, appareils et produits pour gestion automatique de réseaux - Google Patents

Procédés, appareils et produits pour gestion automatique de réseaux Download PDF

Info

Publication number
WO2018138553A1
WO2018138553A1 PCT/IB2017/050487 IB2017050487W WO2018138553A1 WO 2018138553 A1 WO2018138553 A1 WO 2018138553A1 IB 2017050487 W IB2017050487 W IB 2017050487W WO 2018138553 A1 WO2018138553 A1 WO 2018138553A1
Authority
WO
WIPO (PCT)
Prior art keywords
agent
action
decision
control agent
request message
Prior art date
Application number
PCT/IB2017/050487
Other languages
English (en)
Inventor
Bo ÅSTRÖM
Bulent Gecer
Jan Lemark
Maria Belen PANCORBO MARCOS
Stephen Terrill
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/IB2017/050487 priority Critical patent/WO2018138553A1/fr
Publication of WO2018138553A1 publication Critical patent/WO2018138553A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities

Definitions

  • NFV Network Function Virtualization
  • SDN Software Defined Networking
  • the decision agent becomes aware of the capabilities of the control agent only in a static manner (e.g., during installation of the decision agent).
  • a problem with such static configuration of the decision agent is that the capabilities of the control agent may change over time but the DA will not be aware of these changes, which could lead to the DA making a certain policy decision based on an insight and, as a result of making the policy decision, request the CA to perform an action that is not possible at the time the request is made by the DA (e.g., a scaling action). That is, for example, the actions that the control agent (or the resources managed by the control agent) can perform may change over time due to, for example, changes in network load and/or changes in resource availability. As a more specific example, during certain periods of the day the control agent may be unable to scale a system due to the resource usage of the system being at or close to 100% of capacity.
  • An object of this disclosure is to overcome the above described deficiency.
  • the control agent CA
  • the CA when the control agent (CA) receives from the DA an action request message requesting the CA to perform an action that cannot be performed, the CA reports to the DA that the requested action could not be performed.
  • the DA in response to receiving the report, selects a different action and tries again.
  • the DA is notified of any change in the capabilities of the CA. The DA stores this capability information for later use and takes it into account when deciding what action, if any, the DA should request the CA to perform.
  • a method for network management that is performed by a decision agent.
  • the method includes the decision agent determining that a first action is needed. After determining that the first action is needed, the decision agent transmits to a control agent a first action request message comprising: a) information identifying the first action and b) a report indicator indicating a request for an outcome report. After transmitting the action request message, the decision agent receives the requested outcome report, wherein the outcome report comprises information indicating whether the first action has been successfully performed. After receiving the outcome report, the decision agent determines whether the outcome report comprises information indicating whether the first action has been successfully performed. And, as a result of the decision agent determining that the outcome report does not comprise the information indicating that the first action has been successfully performed, the decision agent selects a second action based on information included in the outcome report.
  • the method also includes: after transmitting the first action request and before receiving the outcome report, the decision agent receiving from the control agent an acknowledgement indicating that the control agent will attempt to perform the requested first action.
  • the method also includes: after selecting the second action based on the information included in the outcome report, the decision agent transmitting to the control agent a second action request message comprising information identifying the selected second action and a report indicator indicating a request for an outcome report; and after transmitting the second action request message, the decision agent receiving from the control agent an acknowledgement indicating that the control agent will attempt to perform the requested second action.
  • the decision agent is a Control, Orchestration,
  • Management, Policy and Analytics, COMPA, Policy agent and the control agent comprises a COMPA Control, Orchestration and Management, COM, agent.
  • the information identifying the first action comprises information identifying a resource and information identifying that the resource should be scaled.
  • determining that the first action is needed comprises: the decision agent receiving from an analytics agent an insight; and in response to receiving the insight, the decision agent using capability information associated with the control agent to determine that the control agent is capable of performing the first action.
  • a method for network management that is performed by a control agent.
  • the method includes the control agent receiving from a decision agent a first action request message comprising: a) information identifying a first action and b) a report indicator indicating a request for an outcome report.
  • the control agent attempts to perform the first action (e.g., the control agent initiates performance of the first action).
  • the control agent determines that the first action request message comprises the report indicator; and the control agent transmits to the decision agent the requested outcome report, wherein the transmitted outcome report comprises information indicating whether the first action has been successfully performed.
  • the method further includes determining that the first action cannot be performed; and after receiving the first action request and before determining that the first action cannot be performed, transmitting to the decision agent an acknowledgement indicating that the control agent will attempt to perform the requested first action.
  • the method further includes after transmitting the requested outcome report, receiving a second action request message comprising information identifying a second action and a report indicator indicating a request for an outcome report; and after receiving the second action request message, transmitting an acknowledgement indicating that the control agent will attempt to perform the requested second action.
  • the information identifying the first action comprises information identifying a resource and information identifying that the resource should be scaled.
  • the decision agent transmitting to a control agent a notification request message instructing the control agent to provide capability change notifications to the decision agent.
  • the decision agent receives from the control agent a capability change notification message comprising capability information indicating a change in the control agent's capabilities.
  • the decision agent stores the received capability information and retrieves it at a late time and uses the retrieved capability information to determine whether the decision agent should send an action request message to the control agent.
  • the decision agent is a Control, Orchestration,
  • Management, Policy and Analytics, COMPA, Policy agent, and the control agent comprises one or more of: i) a COMPA Responsibility Domain Common Functions, RDCF, agent and ii) a service exposure agent, and the control agent further comprises a COMPA Control, Orchestration and Management, COM, agent that manages a resource.
  • the capability information indicates a change in the resource's capabilities.
  • the method further comprises the decision agent receiving from an analytics agent an insight, and in response to receiving the insight, the decision agent performs the step of using the retrieved capability information to determine whether the decision agent should send an action request message to the control agent.
  • the step of using the retrieved capability information to determine whether the decision agent should send an action request message to the control agent comprises the decision agent using the retrieved capability information to determine whether the control agent is capable of performing at least one action included in a set of candidate actions.
  • the step of using the retrieved, capability information to determine whether the decision agent should send an action request message to the control agent comprises the decision agent using the retrieved capability information to identify a set of one or more candidate actions.
  • the step of using the retrieved capability information to determine whether the decision agent should send an action request message to the control agent further comprises the decision agent using policy information to select a candidate action from the set of candidate actions.
  • the decision agent prior to the decision agent transmitting the notification- request message, the decision agent discovers that the control agent is capable of providing capability change notification messages.
  • the control agent receives a capability notification request message transmitted by a decision agent, the capability notification request message instructing the control agent to provide capability change notifications to the decision agent.
  • the control agent determines that its capabilities has changed; and after determining that the capabilities has changed, the control agent transmits to. the decision agent a capability change notification message comprising capability information indicating a change in the control agent's capabilities.
  • an apparatus that is adapted to perform any one of the above described methods.
  • FIG. 1 illustrates a system according to some embodiments.
  • FIG. 2 further illustrates components of the system according to some embodiments.
  • FIG. 3 is a flow chart illustrating a process 300 according to some embodiments.
  • FIG. 4 is a flow chart illustrating a process 400 according to some embodiments.
  • FIG. 5 is a message flow diagram further illustrating process 300 according to some embodiments.
  • FIG. 6 is a flow chart illustrating a process 600 according to some embodiments.
  • FIG. 7 is a flow chart illustrating a process 700 according to some embodiments.
  • FIG. 8 is a message flow diagram further illustrating process 600 according to some embodiments.
  • FIG. 9 illustrates an exemplary COMPA system according to some embodiments.
  • FIG. 10 is a message flow diagram illustrating a process according to some embodiments.
  • FIG. 11 is a block diagram of a computer apparatus for implementing one or more agents.
  • FIG. 12A is a diagram showing functional modules of a decision agent according to some embodiments.
  • FIG. 12B is a diagram showing functional modules of a decision agent according to some embodiments.
  • FIG. 13A is a diagram showing functional modules of a control agent according to some embodiments.
  • FIG. 13B is a diagram showing functional modules of a control agent according to some embodiments.
  • FIG. 1 illustrates an example system 100 comprising agents for managing a network 110 containing resources (e.g., in the example show, network 110 includes resources Rl, R2 and R3).
  • the agents of system 100 include: an analytics agent (AA) 102, a decision agent (DA) 104 and a control agent (CA) 106.
  • AA 102 is configured to, among other things, provide insights (i.e., reports) to DA 104.
  • AA 102 may generate an insight based on information received from network 110 and/or CA 106 and then transmit the insight to DA 104.
  • DA 104 is configured to, among other things, make policy decisions based on insights.
  • a result of a policy decision is a determination that an action request message should be transmitted to CA 106 so that CA 106 will perform the requested action by, for example, sending on or more commands to network 1 10.
  • a typical action request message is a message that instructs CA 106 to scale network 110 (e.g., add resources to network 110).
  • the agents of system 100 may be Control, Orchestration, Management, Policy and Analytics (COMPA) agents, as is illustrated in FIG. 2.
  • AA 102 may comprises a COMPA Analytics Agent 202
  • DA 104 may comprise a COMPA Policy Agent 204
  • CA 106 may comprises a COMPA Control, Orchestration and
  • COMPA Management Agent 206 and a COMPA Responsibility Domain Common Functions (RDCF) Agent 207.
  • COMPA Agents are described in International Application No. PCT/SE2016/050474.
  • FIG. 3 is a flow chart illustrating a process 300 according to some embodiments.
  • Process 300 may begin in step 302, in which DA 104 discovers CA's capabilities (e.g., discover the actions that CA can perform with respect to the resources the CA manages). For example, in step 302, DA 104 may transmit to CA 106 a COMPA Service Capability Discovery message 500 (see the message flow diagram shown in FIG. 5) and then receive from CA 106 a COMPA Service Capability Discovery Response 501 comprising capability information indicating capabilities of CA 106 (e.g., indicating actions that CA 106 may perform with respect to network 110 and indicating that CA 106 is capable of providing capability change notification messages) or a pointer to such capability information. In step 304, DA 104 receives an insight 502 from AA 102. For example, insight 502 may be a real-time or historical insight.
  • insight 502 may be a real-time or historical insight.
  • steps 302 and 304 are optional. Thus, in some embodiments, in some
  • process 300 may start with step 306, in which DA 104 determines that a first action is needed. For example, after receiving the insight 502, DA 104 may use the insight and other information (e.g., policy rules, capability information, etc.) to make a policy decision (i.e., to determine that an action is needed).
  • DA 104 transmits to CA 106 information identifying the first action and information requesting an outcome report (OR). For example, in step 308, DA 104 may transmit to CA 106 an action request message 504 (e.g., a COMPA "Request Action" message) identifying the first action and including a report indicator (RI) indicating a request for an OR.
  • action request message 504 e.g., a COMPA "Request Action" message
  • DA 104 may request an OR for the action by sending to CA 106 a separate request OR message 507 that identifies the action for which an OR is requested (e.g., a COMPA "Report Request” message).
  • step 308 comprises sending two messages: 1) an action request message 504 and 2) a request OR message 507.
  • CA 106 responds immediately to request message 504 by transmitting a positive acknowledgement (ACK) to let DA 104 know that CA has successfully received request message 504.
  • DA 104 receives the ACK.
  • the ACK includes an action ID, which can be used to request an OR.
  • the DA 104 if DA 104 transmits an action request message followed by a request OR message, the DA 104 includes in the request OR message the action ID included in the ACK message to inform CA 106 as the action for which CA 106 should send an OR.
  • step 312 DA 104 receives the requested OR 512 transmitted by CA 106.
  • OR will either indicate "success” or "failure.” That is, if CA 106 has successfully performed the requested action (e.g., a scaling action), then OR will indicate success, otherwise OR will indicate failure. Hence, the OR comprises information indicating whether the first action has been successfully performed.
  • CA 106 performs the requested action by transmitting a command 508 to a node network 110 (e.g., a resource in network 110). If CA 106 receives an ACK from network 110, then CA 106 will send to DA 104 an OR indicating success. Otherwise, if CA 106 receives a NACK from network 110 (or CA 106 receives no response from network 110), then CA 106 will send to DA 104 an OR indicating failure.
  • step 314 DA 104 parses OR 512 to determine whether success or failure is indicated. If success is not indicated (i.e., failure is indicated), then in step 316 DA 104 selects another action based on information included in the OR. Afterword, in some embodiments, optional steps 318-322 are performed.
  • step 318 DA 104 transmits to CA 106 information identifying the selected action and information requesting an OR (e.g., DA 104 may transmit to CA 106 another action request message 514 comprising: a) information identifying the selected action and b) an RI indicating a request for an OR).
  • step DA 104 receives the ACK transmitted by CA 106. And in step 322, DA 104 receives the requested OR. After step 322, process 300 may proceed back to step 314.
  • FIG. 4 is a flow chart illustrating a process 400 according to some embodiments.
  • Process 400 may begin in step 402, in which CA 106 receives from DA 104 action request message 504, which comprises the action ID identifying the first action.
  • CA 106 sends ACK 506 to DA 104.
  • CA 106 attempts to perform the identified action.
  • CA 106 determines whether an OR for the action has been requested.
  • message 504 may further include the RI indicating the request for the OR, or DA 104 may transmit to CA 106 the request OR message 507.
  • step 408 may include CA 106 determining whether action request message 504 includes the RI indicating a request for an OR and/or CA 106 determining whether it has received a request OR message 507 identifying the action identified in action request message 504.
  • CA 106 transmits to DA 104 OR 512, which, as described above, indicates whether or not the first action has performed successfully.
  • FIG. 6 is a flow chart illustrating a process 600 according to some embodiments.
  • Process 600 may begin in step 602, in which DA 104 discovers that CA 106 is capable of providing capability change notification messages. For example, in step 602, DA 104 may transmit to RDCF 207 of CA 106 a COMPA Service Capability Discovery message 802 (see the message flow diagram shown in FIG. 8) and then receive from RDCF 207 a COMPA Service Capability Discovery Response 804 comprising capability information indicating capabilities of COM 206 (e.g., indicating actions that COM 206 may perform with respect to network 110 and indicating that COM 206 is capable of providing capability change notification messages) or a pointer to such capability information.
  • capability information indicating capabilities of COM 206 (e.g., indicating actions that COM 206 may perform with respect to network 110 and indicating that COM 206 is capable of providing capability change notification messages) or a pointer to such capability information.
  • step 602 is not performed and process 600 begins with step
  • CA 106 (e.g., COM 206 of CA 106) monitors network 110 (e.g., CA 106 monitors one or more of the resources of network 110) to determine whether a status of a network 110 has changed such that CA 106 is no longer able to perform a certain action (e.g., a network scaling action) that CA 106 was previously able to perform.
  • COM 206 may monitor network 110 by transmitting query 808 to resource Rl and receiving a query result 810 from resource Rl, which query result may include information indicating whether or not resource Rl can handle additional load.
  • COM 206 determining that COM 206 can no long perform the certain action, COM 206 transmits to RDCF 207 a Service Capability Update message 812 indicating that COM 206's capabilities have changed - i.e., indicating that COM 206 is no longer able to perform the certain action.
  • RDCF 207 transmits to COM 206 an ACK 814 and transmits to DA 102 a capability change notification message 816 indicating that that COM 206 is no longer able to perform the certain action.
  • step 606 DA 104 receives capability change notification message 816.
  • step 606 DA 104 receives capability change notification message 816.
  • DA 104 obtains from the capability change notification message 816 the capability information included in the message (e.g., the information indicating that COM 206 is not able to perform the certain action) and stores in a data storage system (DSS) (see e.g., DSS 1 108 shown in FIG. 11) the obtained capability information.
  • DSS data storage system
  • the obtained capability information may be included in a database record that is stored in DSS in association with an identifier that identifies CA 106 so that DA 104 can keep track of CA 106' s capabilities as those capabilities change over time.
  • DA 104 retrieves the stored capability information (step
  • DA 104 receives an insight 818 from AA 102 indicating a problem in the network (e.g., the insight may indicate an uneven load in the network). After receiving such an insight, DA 104 retrieves the stored capability information for CA 106 (step 612) and uses the retrieved capability information (and possibly other information as well, such as policy information) to determine whether an action is needed (i.e., whether DA 104 should send to CA 106 an action request message) (step 614).
  • DA 104 may use policy information to identify a set of candidate actions based on information included in the insight and then DA 104 may use the retrieved capability information to select an action from the set of candidate actions. In this way, DA 104 determines that the selected action is needed (i.e., DA 104 determines that DA 104 should send to CA 106 an action request message).
  • DA 104 may use the retrieved capability information to identify a set of candidate actions based on information included in the insight and then DA 104 may use policy information to select an action from the set of candidate actions. In this alternative way, DA 104 determines that an action is needed.
  • step 616 which is reached when DA 104 determines that an action is needed.
  • DA 104 transmits to CA 106 an action request message 820 comprising an action ID identifying a selected action (e.g., identifying the selected candidate action).
  • the action request message may further include an RI indicating a request for an OR, or DA 104 may transmit a request OR message 821 to cause CA 106 to send an OR indicating whether or not the selected action has been performed successfully.
  • DA 104 receives an ACK from CA 106.
  • step 620 DA 104 receives from CA 106 a requested OR indicating whether or the selection action has been performed successfully. Steps 618 and 620 may be optional.
  • FIG. 7 is a flow chart illustrating a process 700 according to some embodiments.
  • Process 700 may begin in step 702, in which CA 106 receives the capability notification request message 806 transmitted by DA 104, which instructs CA 106 to provide capability change notifications to DA 104.
  • CA 106 monitors network 110 to determine whether CA 106' s capabilities have changed (step 704). For example, by monitoring network 1 10 CA 106 may determine that a resource in network 1 10 has reached a certain state such that CA 106 is no longer capable of scaling the resource because, for example, the resource is at 100% of its capacity.
  • CA 106 transmits to DA 104 a capability change notification message comprising capability information indicating a change in the control agent's capabilities.
  • the capability change notification message may include information indicating that CA 106 cannot at this time perform an action that is identified by an action identifier included in the capability change notification message.
  • FIG. 9 illustrates an exemplary COMPA system 900.
  • the exemplary COMPA system includes the following agents: analytics agent 202, policy agent 204, COM agent 206, and RDCF agent 207.
  • COM agent 206 is configured to perform requested actions, such as, for example, actions requested by a policy agent and actions for supporting resource and service onboarding requests.
  • COM agent 206 is configured to receive action request messages that request COM agent 206 to perform actions, such as, for example, onboarding and scaling of resources and/or services.
  • a resource can be any one of: a network agent (a.k.a.,
  • network function e.g., Mobility Management Entity, Serving Gateway, switching/routing equipment, computing resources, storage resources, a COMPA agent, etc.
  • policy agent 204 requests a COM agent, such as COM agent 206, to perform certain actions based on, for example, a policy decision that policy agent makes based on, for example, insights received from an analytics agent, such as analytics agent 202 or an analytics agent in another COMPA system in another RD.
  • policy agent may be configured to transmit insight request messages to an analytics agent and transmit action request messages to a COM agent.
  • policy agent 204 may be configured to receive from a COMPA system agent (e.g., a COM agent) or a non-COMPA system policy event messages that contain information for use by policy agent in making the policy decision.
  • Analytics agent 202 is configured to provide insights (i.e., reports), such as insights identifying current (and/or predicted) events or conditions within the network.
  • insights i.e., reports
  • analytics agent 202 is configured such that, in response to receiving a historical insight request message, analytics agent 202 periodically transmits an historical insight to the requesting entity, which is typically a policy agent, and is further configured such that, in response to receiving a real-time insight request message, analytics agent 202 transmits an insight to the requesting entity as soon as the insight is generated.
  • RDCF agent 207 provides service exposure, maintains catalogs (e.g., a service catalog and/or a resource catalog), and maintains inventories.
  • catalogs e.g., a service catalog and/or a resource catalog
  • analytics agent 202 is configured to act on certain defined COMPA Analytics messages.
  • COMPA Analytics messages include the following messages: 1) the historical insight request message; 2) the real-time insight request message; 3) an historical insight tuning message; and 4) an historical insight termination message.
  • Tables 1-4 illustrate the information elements that may be included in each of the messages:
  • analytics agent 202 creates in a database a record storing information contained in the received message (e.g., the periodicity, report type, etc.) and transmits to the entity that transmitted the request an acknowledgement message containing a delivery identifier for use in later retrieving the database record from the database. Also, as a result of receiving the historical insight request message, analytics agent 202 will, based on the periodicity defined in the request, periodically transmit an historical insight delivery message comprising an insight.
  • the transmitted historical insight delivery message may further include the identifier that was included in the acknowledgement message.
  • the insight included in the historical insight delivery message may be formatted using a markup language (e.g., Extensible Markup Language (XML)) or using JavaScript Object Notation (JSON)) or otherwise formatted.
  • XML Extensible Markup Language
  • JSON JavaScript Object Notation
  • analytics agent uses the delivery identifier included in the tuning message to update the database record based on the parameters included in the tuning message (e.g., the periodicity parameter).
  • analytics agent uses the delivery identifier included in the tuning message to delete the database record or update the database record to indicate that no further historical insights defined by the record should be sent.
  • analytics agent 202 With respect to the real-time insight request message, as a result of receiving this message, analytics agent 202 generates a real-time insight and transmits a real-time insight delivery message comprising the generated real-time insight. In some embodiments, after the insight request message is received and before the delivery message is sent, analytics agent 202 transmits an acknowledgement message with a delivery identifier, and the delivery message includes the delivery identifier.
  • the insight report may be formatted using XML or JSON and contains information (e.g., real-time information) requested in the real-time insight request message.
  • Policy agent 204 in some embodiments, is configured to act on certain defined
  • COMPA Policy messages include: 1) a policy data message; and 2) request policy decision message.
  • Tables 5 and 6 illustrate the information elements that may be included in each of the messages:
  • this message can be transmitted to the policy agent by any resource in the network.
  • policy agent 204 may store the event report (or stores at least some of the information included in the event report) so that the information can be used at a later time as input to a policy statement executed by policy agent 204, or policy agent may execute a policy statement based on the event report immediately after receiving the policy data message.
  • a resource e.g., a security system which may or may not follow COMPA principles
  • policy agent 204 uses the information contained in the Policy Decision Input ⁇ (and possibly previously stored event report information) to execute a policy statement, and thereby make a policy decision.
  • An identifier identifying the policy statement may be included in the Policy Decision Input IE together with parameters required by the policy statement.
  • the result of the policy decision is returned to the entity that transmitted the request policy decision message.
  • the policy agent may be triggered to send to a COM agent a Request Action message.
  • COM agent 206 in some embodiments, is configured to act on certain defined
  • COMPA COM messages include the messages identified in TABLE 7.
  • Tables 8 to 17B below illustrate an exemplary embodiment of the COM agent messages shown in table 7.
  • RDCF agent 207 in some embodiments, is configured to act on certain defined
  • COMPA RDCF messages include the messa es identified in table 18 below.
  • Tables 19-40 illustrate the information elements that may be included in each of the messages show in TABLE 18.
  • each of the messages described herein may further include a "token" information element as show below in table 42.
  • each use case can be categorized into one of the following four categories:
  • AM (sometimes referred to as autonomic networks) is about automating the operational support of the network.
  • the aim is to have a policy based control for managing the deployed and instantiated/assigned resources.
  • FIG. 10 is a message flow diagram illustrating a process 1000 for automatic management of a network.
  • process 1000 beings with step 1002, wherein policy agent 204 transmits to analytics agent 202 a request for at least one insight (i.e., a report).
  • the request may be a historical insight request message or a real-time insight request message.
  • analytics agent 202 receives data from one or more data sources 1001 (e.g., one or more resources).
  • this data includes performance information such as: number of dropped packet; memory utilization; processor utilization; number of simultaneous users; etc.
  • the data received from a resource includes information pertaining to a possible security threat.
  • Other examples of collected data include: alarms, events from networks such as PDP context establishments, call establishments, call data records, mobility management events (e.g. location update), handover event reporting, etc.
  • step 1006 analytics agent 202 process the data from the data sources to generate an insight 1007 based on the data received from the one or more sources and transmits the insight 1007 to policy agent 204, which receives the insight 1007.
  • the step of transmitting the insight includes one of: transmitting an historical insight delivery message comprising the insight and transmitting a real-time insight delivery message comprising the insight.
  • step 1008 as a result of receiving the insight 1007 (which may include network performance information and/or security information), policy agent 204 determines whether an action is needed based on information included in the insight, a policy, and capability information.
  • policy agent 204 may execute a rule contained in a policy and determine, based on 1) the rule, 2) information in one or more received insights, and 3) capability information, whether a certain condition has been satisfied (e.g., whether a certain processor utilization has stayed above a certain threshold for at least a certain amount of time and CA 106 has the capabilities to take an action to reduce the processor utililzation).
  • a certain condition e.g., whether a certain processor utilization has stayed above a certain threshold for at least a certain amount of time and CA 106 has the capabilities to take an action to reduce the processor utililzation.
  • step 101 1 As a result of determining that a network management action should be undertaken, the policy agent transmits to COM agent 206 an action request 1012 (e.g., a "Request Action” message or an "Instantiate Resource” message, defined above) identifying the network management action (the action request may also include an RI instructing COM agent 206 to send an OR).
  • action request 1012 e.g., a "Request Action” message or an "Instantiate Resource” message, defined above
  • the action request may also include an RI instructing COM agent 206 to send an OR.
  • COM agent 206 performs the requested action(s). If an OR was requested by policy agent 204, COM agent 206, in step 1015 after performing step 1014, transmits to policy agent 204 the requested OR 1016.
  • FIG. 11 is a block diagram of a computer apparatus 1100 that can be used to implement one or more of the above described agents. That is, in some embodiments, for each of the above described agents, the system 100 has a separate computer apparatus 1100 for implementing the agent, but in other embodiments, one or more agents may be implemented using only a single computer apparatus 1100. As described below, computer apparatus 1100 may consists of a single data processing apparatus or set of data processing apparatuses (i.e., computer apparatus 1100 may be a cloud computing system).
  • computer apparatus 1100 includes at least one data processing apparatus (DPA) 1102, which may include one or more processors (P) 1155 (e.g., one or more general purpose processors, such as a general purpose microprocessor, and/or one or more data processing circuits, such as an application specific integrated circuit (ASIC), field- programmable gate arrays (FPGAs), logic circuits, and the like).
  • DPA data processing apparatus
  • processors e.g., one or more general purpose processors, such as a general purpose microprocessor, and/or one or more data processing circuits, such as an application specific integrated circuit (ASIC), field- programmable gate arrays (FPGAs), logic circuits, and the like.
  • DPA data processing apparatus
  • processors e.g., one or more general purpose processors, such as a general purpose microprocessor, and/or one or more data processing circuits, such as an application specific integrated circuit (ASIC), field- programmable gate arrays (FPGAs), logic circuits, and the like.
  • Computer apparatus 1100 further includes: a network interface 1105 that includes a transmitter (Tx) 1107 and a receiver (Rx) 1 109 for use in transmitting and receiving data, respectively; and a data storage system 1108, which may include one or more non- volatile storage devices and/or one or more volatile storage devices ⁇ e.g. , random access memory (RAM)).
  • DPA 1102 includes, for example, a microprocessor
  • a computer program product (CPP) 1141 may be provided.
  • CPP 1141 includes a computer readable medium (CRM) 1142 storing a computer program (CP) 1143 comprising computer readable instructions (CRI) 1144.
  • CCM computer readable medium
  • CP computer program
  • CRM 1142 may be a non-transitory computer readable medium, such as, but not limited, to magnetic media ⁇ e.g., a hard disk), optical media ⁇ e.g. , a DVD), memory devices ⁇ e.g., random access memory), and the like, but not a signal.
  • the CRI of computer program 1143 is configured such that when executed by DPA 1102, the CRI causes the DPA 1102 to perform steps described above.
  • DPA 1102 may be configured to perform steps described herein without the need for code. That is, for example, DPA 1102 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.
  • FIG. 12A is a diagram showing functional modules of decision agent 104 according to some embodiments.
  • decision agent 104 includes: a first determining module 1202 configured to determine that a first action is needed; a transmitting module 1204 configured to employ transmitter 1107 to transmit to a control agent a first action request message after determining that the first action is needed, wherein the first action request message comprises: a) information identifying the first action and b) a report indicator indicating a request for an outcome report; a receiving module 1206 configured to employ receiver 1109 to receive the requested outcome report after transmitting the action request message, wherein the outcome report comprises information indicating whether the first action has been successfully performed; a second determining module 1208 configured to determine whether the outcome report comprises information indicating whether the first action has been successfully performed; and a selecting module 1210 configured to select a second action based on information included in the outcome report as a result of the decision agent determining that the outcome report does not comprise the information indicating that the First action has been successfully performed.
  • FIG. 12B is a diagram showing functional modules of decision agent 104 according to some embodiments.
  • decision agent 104 includes: a transmitting module 1222 configured to employ transmitter 1107 to transmit to a control agent a notification request message instructing the control agent to provide capability change notifications to the decision agent; a receiving module 1224 configured to employ receiver 1109 to receive from the control agent a capability change notification message, wherein the capability change notification message comprises capability information indicating a change in the control agent's capabilities; a storing module 1226 configured to store the received capability information; a retrieving module 1228 configured to retrieve the stored capability information; and a determining module 1230 configured to determine, based on the retrieved capability information, whether the decision agent should send an action request message to the control agent.
  • FIG. 13A is a diagram showing functional modules of control agent 106 according to some embodiments.
  • control agent 106 includes: a receiving module 1302 configured to receive from a decision agent a first action request message comprising: a) information identifying a first action and b) a report indicator indicating a request for an outcome report; an action performing module 1304 configured to attempt to perform the first action; a determining module 1306 configured to determine that the first action request message comprises the report indicator; and a transmitting module 1308 configured to transmit to the decision agent the requested outcome report, wherein the transmitted outcome report comprises information indicating whether the first action has been successfully performed.
  • FIG. 13B is a diagram showing functional modules of control agent 106 according to some embodiments.
  • control agent 106 includes: a receiving module 1322 configured to receive a capability notification request message transmitted by a decision agent, the capability notification request message instructing the control agent to provide capability change notifications to the decision agent; a determining module 1324 configured to determine that its capabilities has changed; and a transmitting module 1326 configured to employ transmitter 1107 to transmit to the decision agent a capability change notification message after the determining module determines that the capabilities has changed, wherein the capability change notification message comprises capability information indicating a change in the control agent's capabilities.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

La flexibilité accrue fournie par les nouvelles technologies, telles que SDN et NFV, a entraîné une difficulté d'exploitation des réseaux qui nécessitent un degré élevé d'intervention manuelle. Un objet de la présente invention est de remédier à cette déficience. Ainsi, selon un mode de réalisation, lorsque l'agent de contrôle (CA) reçoit de la part d'un agent de décision (DA) un message de demande d'action demandant à l'agent de contrôle d'effectuer une action qui ne peut pas être effectuée, l'agent de contrôle rapport à l'agent de décision que l'action demandée n'a pas pu être effectuée. L'agent de décision, en réponse à la réception du rapport, sélectionne une action différente et essaie de nouveau. Selon un autre mode de réalisation, l'agent de décision est informé de tout changement des capacités de l'agent de contrôle. L'agent de décision stocke ces informations de capacité pour une utilisation ultérieure et en tient compte lorsqu'il décide de transmettre ou pas un message de demande d'action à l'agent de contrôle.
PCT/IB2017/050487 2017-01-30 2017-01-30 Procédés, appareils et produits pour gestion automatique de réseaux WO2018138553A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2017/050487 WO2018138553A1 (fr) 2017-01-30 2017-01-30 Procédés, appareils et produits pour gestion automatique de réseaux

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2017/050487 WO2018138553A1 (fr) 2017-01-30 2017-01-30 Procédés, appareils et produits pour gestion automatique de réseaux

Publications (1)

Publication Number Publication Date
WO2018138553A1 true WO2018138553A1 (fr) 2018-08-02

Family

ID=58231658

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2017/050487 WO2018138553A1 (fr) 2017-01-30 2017-01-30 Procédés, appareils et produits pour gestion automatique de réseaux

Country Status (1)

Country Link
WO (1) WO2018138553A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210243103A1 (en) * 2018-07-27 2021-08-05 Nippon Telegraph And Telephone Corporation Network system, information acquisition device, information acquisition method, and program

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016054922A1 (fr) * 2014-10-10 2016-04-14 华为技术有限公司 Procédé de coordination de décisions, dispositif de mise en œuvre et coordinateur de décisions
US20160124781A1 (en) * 2014-10-31 2016-05-05 At&T Intellectual Property I, L.P. Creating and Using Service Control Functions

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016054922A1 (fr) * 2014-10-10 2016-04-14 华为技术有限公司 Procédé de coordination de décisions, dispositif de mise en œuvre et coordinateur de décisions
US20170214544A1 (en) * 2014-10-10 2017-07-27 Huawei Technologies Co., Ltd. Decision Coordination Method, Execution Apparatus, and Decision Coordinator
US20160124781A1 (en) * 2014-10-31 2016-05-05 At&T Intellectual Property I, L.P. Creating and Using Service Control Functions

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "pCR on TR 32.842 Scaling trigger and decision", vol. SA WG5, no. Ljubljana; 20150525 - 20150529, 16 May 2015 (2015-05-16), XP050972521, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG5_TM/TSGS5_101/Docs/> [retrieved on 20150516] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210243103A1 (en) * 2018-07-27 2021-08-05 Nippon Telegraph And Telephone Corporation Network system, information acquisition device, information acquisition method, and program
US11979306B2 (en) * 2018-07-27 2024-05-07 Nippon Telegraph And Telephone Corporation Network system, information acquisition device, information acquisition method, and program

Similar Documents

Publication Publication Date Title
EP3231135B1 (fr) Corrélation d&#39;alarme dans un environnement de virtualisation de fonction de réseau
EP2921955B1 (fr) Capacité de surveillance dans une architecture orientée service
CN111861140B (zh) 一种业务处理方法、装置、存储介质和电子装置
CN111095900B (zh) 用于分布式云环境中sla管理的方法和装置
GB2587697A (en) Service experience analytics for network slice instance
US10367696B2 (en) Automatic network management system and methods
US20220141311A1 (en) Resource subscription method, device and server, and computer storage medium
US20160344582A1 (en) Call home cluster
US10547496B2 (en) Automatic network management system and methods
US11388109B2 (en) Hierarchical capacity management in a virtualization environment
US11303521B1 (en) Support platform with bi-directional communication channel for performing remote actions on computing devices
US20230086473A1 (en) Smart retry policy for automated provisioning of online resources
CN109314697B (zh) 自动网络管理系统和方法
EP3672203A1 (fr) Procédé de distribution pour le calcul de données distribué, dispositif, serveur et support de stockage
WO2018138553A1 (fr) Procédés, appareils et produits pour gestion automatique de réseaux
US10873514B2 (en) Neighbor monitoring in a hyperscaled environment
US11128520B2 (en) System and method for real-time network engineering control
CN114024968A (zh) 一种基于中间设备的报文发送方法、装置和电子设备
US11425003B2 (en) Network aware element and a method for using same
WO2007100413A2 (fr) Interopérabilité entre porteuses pour services critiques
WO2020113405A1 (fr) Mises à jour de configurations de fonctions de services dans une architecture de réseau basée sur des services
US20230058330A1 (en) Discovery of service instance
CN116319591A (zh) 消息队列集群的数据处理方法、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17709178

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17709178

Country of ref document: EP

Kind code of ref document: A1