EP3304965A1 - Procédé et appareil pour mettre en oeuvre des fonctions d'auto-fonctionnement dans un réseau - Google Patents

Procédé et appareil pour mettre en oeuvre des fonctions d'auto-fonctionnement dans un réseau

Info

Publication number
EP3304965A1
EP3304965A1 EP15730410.6A EP15730410A EP3304965A1 EP 3304965 A1 EP3304965 A1 EP 3304965A1 EP 15730410 A EP15730410 A EP 15730410A EP 3304965 A1 EP3304965 A1 EP 3304965A1
Authority
EP
European Patent Office
Prior art keywords
self
operation case
request
network node
information indicating
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP15730410.6A
Other languages
German (de)
English (en)
Inventor
Haitao Tang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Solutions and Networks Oy
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 Nokia Solutions and Networks Oy filed Critical Nokia Solutions and Networks Oy
Publication of EP3304965A1 publication Critical patent/EP3304965A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • Embodiments of the present invention relate to implementing self-operation functions within a network.
  • LTE Long-term Evolution
  • 3GPP 3 rd Generation Partnership Project
  • a method may include receiving, by a first network node, a request for a recommended action from a second network node.
  • the request comprises an event information and a context information.
  • the method may also include performing a similarity analysis to determine if the first network node has stored a self- operation case that relates to the request.
  • the method may also include determining a recommended action based on the similarity analysis.
  • the method may also include transmitting the recommended action to the second network node.
  • the first network node is configured to perform a self- operation function.
  • the determined recommended action comprises an action corresponding to the stored self-operation case. If the first network node has not stored a self-operation case that relates to the request, then the determined recommended action is recommended by a human operator.
  • the request comprises a format including at least one of information indicating a function, information indicating an instance, information indicating a sequence number, information indicating a context, and information indicating an event.
  • the method may also include extracting relevant information concerning the recommended action, constructing a corresponding self- operation case based on the extracted relevant information, storing the constructed self- operation case based on an analysis of a relation of the extracted relevant information, processing the constructed self-operation case, updating the self-operation case, and later applying the self-operation case.
  • an apparatus may include at least one processor.
  • the apparatus may also include at least one memory including computer program code.
  • the at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to receive a request for a recommended action from a network node.
  • the request comprises an event information and a context information.
  • the apparatus may also be caused to perform a similarity analysis to determine if the apparatus has stored a self-operation case that relates to the request.
  • the apparatus may also be caused to determine a recommended action based on the similarity analysis.
  • the apparatus may also be caused to transmit the recommended action to the network node.
  • the apparatus may be configured to perform a self-operation function.
  • the determined recommended action comprises an action corresponding to the stored self-operation case. If the apparatus has not stored a self-operation case that relates to the request, then the determined recommended action is recommended by a human operator.
  • the request comprises a format including at least one of information indicating a function, information indicating an instance, information indicating a sequence number, information indicating a context, and information indicating an event.
  • the apparatus is further caused to extract relevant information concerning the recommended action, construct a corresponding self- operation case based on the extracted relevant information, store the constructed self- operation case based on an analysis of a relation of the extracted relevant information, process the constructed self-operation case, update the self-operation case, and later apply the self- operation case.
  • a computer program product may be embodied on a non-transitory computer readable medium.
  • the computer program product may be configured to control a processor to perform a method according to the first embodiment.
  • a method may include receiving, by a network node, a consultation request for an expected result of a given operation.
  • the consultation request may be received from a human operator.
  • the method may also include performing a similarity analysis to determine if the network node has stored a self-operation case that relates to an element of the consultation request.
  • the method may also include transmitting a result of the similarity analysis to the human operator.
  • the network node is configured to perform a self-operation function.
  • the consultation request comprises a format corresponding to ConsultationRequest(x).
  • an apparatus may include at least one processor.
  • the apparatus may also include at least one memory including computer program code.
  • the at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to receive a consultation request for an expected result of a given operation.
  • the consultation request is received from a human operator.
  • the apparatus may also be caused to perform a similarity analysis to determine if the apparatus has stored a self-operation case that relates to an element of the consultation request.
  • the apparatus may also be caused to transmit a result of the similarity analysis to the human operator.
  • the apparatus is configured to perform a self-operation function.
  • the consultation request comprises a format corresponding to ConsuitationRequest(x).
  • a computer program product may be embodied on a non-transitory computer readable medium.
  • the computer program product may be configured to control a processor to perform a method according to the fourth embodiment.
  • a method may include receiving, by a first network node, an operation from a human operator. The method may also include forwarding the operation to a second network node. The method may also include receiving a notification indicating a result of the operation. The method may also include transmitting the notification to the human operator.
  • the first network node is configured to perform a self- operation function.
  • the operation comprises a format including at least one of information indicating a function, information indicating an instance, information indicating a sequence number, and information indicating an action.
  • the method further comprises extracting relevant information concerning the recommended action, constructing a corresponding self- operation case based on the extracted relevant information, storing the constructed self- operation case based on an analysis of a relation of the extracted relevant information, processing the constructed self-operation case, updating the self-operation case, and later applying the self-operation case.
  • an apparatus may include at least one processor.
  • the apparatus may also include at least one memory including computer program code.
  • the at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to receive an operation from a human operator.
  • the apparatus may also be caused to forward the operation to a network node.
  • the apparatus may also be caused to receive a notification indicating a result of the operation.
  • the apparatus may also be caused to transmit the notification to the human operator.
  • the apparatus may be configured to perform a self- operation function.
  • the operation comprises a format including at least one of information indicating a function, information indicating an instance, information indicating a sequence number, and information indicating an action.
  • the apparatus is further caused to extract relevant information concerning the recommended action, construct a corresponding self- operation case based on the extracted relevant information, store the constructed self- operation case based on an analysis of a relation of the extracted relevant information, process the constructed self-operation case, update the self-operation case, and later apply the self- operation case.
  • a computer program product may be embodied on a non-transitory computer readable medium.
  • the computer program product may be configured to control a processor to perform a method according to the sixth embodiment.
  • Fig. 1 illustrates an architecture of self-operation based on stored self-operation cases and human knowledge.
  • Fig. 2 illustrates example information elements of a self-operation case.
  • FIG. 3 illustrates a flowchart of a method in accordance with certain embodiments of the invention.
  • FIG. 4 illustrates a flowchart of a method in accordance with certain embodiments of the invention.
  • FIG. 5 illustrates a flowchart of a method in accordance with certain embodiments of the invention.
  • Fig. 6 illustrates an apparatus in accordance with certain embodiments of the invention.
  • Fig. 7 illustrates an apparatus in accordance with certain embodiments of the invention.
  • Fig. 8 illustrates an apparatus in accordance with certain embodiments of the invention.
  • FIG. 9 illustrates an apparatus in accordance with certain embodiments of the invention.
  • Certain embodiments of the present invention relate to implementing self-operation functions within a network. Specifically, certain embodiments of the present invention may relate to implementing self-operation functions within a network, where the self-operation functions are configured with potentially incomplete and/or inconsistent settings.
  • Self-x functions (such as self-optimizing functions, self-organizing functions, self- healing functions, self-configuring functions, and/or some Traffic Steering functions, for example) may be utilized with 3G and 4G networks. Self-x functions may be used in conjunction with operations support systems (OSS) of these networks.
  • OSS operations support systems
  • self-x functions are generally assumed to operate in accordance with rules that have been pre- defined/pre- set prior to performing network operations, while certain other rules may be provided when actually performing the network operations.
  • Self-x functions have generally reduced the amount of manual operations that are required to be performed within 3G and 4G networks.
  • 5G systems (including networks and OSS systems) are expected to utilize an even wider scope of self-x functions, as one of the objectives of implementing 5G systems is to minimize the need for human involvement while performing network operations.
  • the above-described problems may be reduced by providing directions/reasoning of how to proceed for a plurality of situations, and the directions/reasoning may be provided based on a pre-defined ontology.
  • systems that utilize such directions/reasoning may still encounter technical problems that are similar to the above-described technical problems (as when rules are utilized). For example, if the ontology has not been configured to address a certain situation in advance (regardless of whether the ontology is human-defined or is provided during the network operations), the situation may possibly not be properly addressed.
  • certain embodiments of the present invention provide a practical and realizable solution that enables a human operator to interactively work with the above networks and OSS systems during the network operations.
  • the interworking between the human operator and the networks may enable and guarantee the reliability and trustworthiness of a machine learning, and the interworking may enable/guarantee the reliability of a mutual learning between the human operator and the operation resources, as described in greater detail below.
  • Certain embodiments of the present invention are directed to implementing a self- operation function, where an OSS/network system is using potentially incomplete and/or an inconsistent set of rules/ontology. Certain embodiments may solve the problems relating to missing rules/ontology and the problems relating to inconsistencies between rules/ontology. Certain embodiments of the present invention may resolve the above-described problems during the actual network operations of the system by learning self-operation cases. Certain embodiments may apply the learned self-operation cases to actual network operations as well as to human operator consultation. [0049] Certain embodiments of the present invention can allow a human operator's role to be gradually minimized so that the human operator merely sets operation targets. At the same time, certain embodiments may guarantee the reliability and the trustworthiness of the network operations.
  • Certain embodiments may define self-operation cases, define how self-operation cases are analyzed, and/or define how consultation services are provided based on stored self- operation cases.
  • certain embodiments may be directed to a self-operation architecture that includes a human user interface (UI), a self-operation function, and/or an OSS/network function.
  • a computer may present information to a human operator via the human UI.
  • the UI may present information to the human operator via a display device, for example.
  • the UI may permit the human operator to provide an input to the network.
  • the UI may permit the human operator to provide a Response ActionRccommendation. as described in more detail below.
  • the OSS/network function may include, for example, SON coordination functions, verification functions, analytics functions, self-x functions and instances, and/or other network / OSS resources, as illustrated by Fig. 1.
  • SON coordination functions for example, SON coordination functions, verification functions, analytics functions, self-x functions and instances, and/or other network / OSS resources, as illustrated by Fig. 1.
  • two self-operation procedures may be defined, which may be referred to as "Procedure 1" and “Procedure 2" below, for example.
  • Procedure 1 may enable interactive self-operation by applying knowledge of self- operation cases or of human instructions, as described in more detail below.
  • Procedure 2 may learn and build a self-operation knowledge by automatically constructing and storing self- operation cases from information derived from the corresponding system operations and human instructions.
  • a self-operation function may learn and automatically store self- operation cases from the self-operation function's interactions with the OSS/network function and from the self- operation function's interactions with the human operator.
  • the self-operation function may then provide a recommendation to an OSS/network function (and/or to a human operator) regarding what action to take / what consequence to expect, for example.
  • the provided recommendations may be based on the stored self-operation cases and/or the information from the human operator.
  • the self- operation function can also import self- operation cases from outside sources.
  • a self-operation case may be a tuple that includes at least one of: (1) information indicating a context, (2) information indicating an event, (3) information indicating an action, (4) information indicating a result, (5) information indicating a profile, and/or (6) information indicating a group.
  • a self-operation case may be described by a corresponding tuple, including information such as: (context, event, action, result, profile, groupID).
  • Fig. 2 illustrates the elements of a tuple in accordance with certain embodiments of the present invention.
  • the self-operation case can be built gradually, which means that some of the self-operation's information elements (as reflected within the self-operation's corresponding tuple) may be initially unknown. Some of the self-operation's information elements may then be completed/filled during later relevant network operations. If all the information is available, a self-operation case can be completely built.
  • the elements of a tuple may be learned from messages exchanged between the self-operation function, other OSS/network functions, as well as a human operator. These elements may contain information (which may be "raw” information) that is extracted from the messages, and the information may provide the details of the corresponding operation.
  • the "profile” element may be obtained from analysis of learned elements by the self-operation function.
  • As network operations are performed more and more self-operation cases may be generated. Many of the self-operation cases may be similar to or may be the same as other self-operation cases. Certain embodiments may group self-operation cases according to their similarity, as discussed in more detail below.
  • such a grouping can be associated with reliability information.
  • a stored/existing self-operation case can be used to guide a new operation.
  • certain embodiments may store a percentage of self- operation cases in a group that have achieved a successful result.
  • the groupID element may be used to associate a grouping of self-operation cases with the reliability information.
  • Certain embodiments may perform a similarity analysis of the self- operation cases based on pre-defined ontology or based on rules for the self-operation cases. Self-operation cases that are determined to be similar and/or the same may be assigned to a corresponding same unique groupID.
  • Procedure I may be directed to an interactive operation that utilizes stored self-operation cases and/or human knowledge.
  • Procedure 1 may be invoked to perform interactive operations in accordance with the following defined events (referred to as events "a” to " ⁇ " below).
  • Event a may correspond to an event where an OSS/network function has no knowledge for properly determining what to do for a given event.
  • Procedure 1 may be invoked to perform the following:
  • the OSS/network function may send a request (with an "event” and a relevant "context") to the self-operation function.
  • the request may include, for example, at least one of: (1) information indicating a function, (2) information indicating an instance, (3) information indicating a sequence number, (4) information indicating a context, and/or (5) information indicating an event.
  • the request may be a request for a recommendation, and the request may be in the form of, for example: RequestActionRecommendation (functionlD, in stance 11 ), sn f , context f , event f ).
  • the functionll ) and instancelD may together identify the requesting OSS/network function.
  • the "sn f " may be a sequence number of the request that is provided by this identified function. In general, a sequence number may be a unique number assigned to an initial request. A later reply and/or related information element may be linked to the initial request and its created/used information elements.
  • the "context f " and "event f " may be the context and the event that are indicated in the request by the OSS/network function. The context and the event may correspond to context information and event information that are indicated by the initital request. For example, an initial request may be: "Can MRO configure the HO threshold between Cell A and Cell C?" With this example, the related context may be the status and configuration information of the cells, and/or the active functions or still-impacting functions on these two cells. With this example, the event may correspond to the intention to configure the threshold.
  • the self-operation function After the self-operation function receives the request, the self-operation function performs a similarity analysis to determine if the self-operation function already has knowledge in its stored self-operation case(s) that relate to the request. For example, based on a corresponding similarity measure (like a group of structured and value-assigned keywords), the self-operation function may perform a search of its stored self-operation cases. Self-operation cases that match the given similarity measure may then be considered to be the knowledge that relates to the request. With certain embodiments, the similarity measure may relate to matching context and/or matching event information, for example.
  • the self-operation function may then perform one of the following: o If the self-operation function already has knowledge in its stored self- operation cases of (context, event, action, result, profile, groupID) that relate to the request, the self-operation function performs the following:
  • the self-operation function may recommend a corresponding action to the requesting OSS/network function in the form of, for example, ResponseActionRecommendation(sn f , action)
  • the "context so " in this response may have been extended/elaborated upon by the self-operation function based on the "context f " that is received in the request from the OSS/network function.
  • the context information may be extended by adding more information elements to the original given context f . For example, the extra information element may correspond to an intended configuration event that has similar events who have similar percentages of both failure and success results in the history. Otherwise, context so may correspond to context f .
  • the self- operation function may decide if an extension of context information is needed.
  • the self-operation function may invoke Procedure 2 (B.) (as described below) to construct a current self-operation case under the existing groupID.
  • Procedure 1 continues to Step c.
  • the self-operation function further sends a request (with the "event” and its relevant "context") to the human operator.
  • the human operator may review the request via a human UI.
  • the request may be a request for a recommendation of a course of action in the form of, for example, RequestActionRecommendation (functionID, instancelD, sn so , context so , event f ).
  • the functionID and instancelD may together identify the self-operation function.
  • the "sn so " may be the sequence number of the request, as raised/provided by this self- operation function.
  • the "context s ,," and “event f " may be defined in accordance with the corresponding definitions of a self-operation case, as described above.
  • the context so in this request may have been extended by the self-operation function, based on the context f received in the request from the OSS/network function. Otherwise, context so may correspond to context f .
  • the self-operation function may decide if such an extension may be needed.
  • the human operator may decide on the corresponding action for the request, and the human operator may respond to the self-operation function in the form of, for example, ResponseActionRecommendation(sn so , action). For example, as described above, the human operator may provide an input, into the human UI, that corresponds to ResponseActionRecommendation.
  • the self-operation function may receive the operator response and may perform the following:
  • the self-operation function may recommend the corresponding action to the requesting OSS/network function in the form of, for example, ResponseActionRecommendation(sn f , action) o
  • the self-operation function may invoke Procedure 2 (A.) (as defined below) to learn from the human decision regarding how to respond to such an incident and to accordingly construct a new self-operation case.
  • the OSS/network function may perform the recommended action (if any recommended action was recommended) according to the response.
  • Procedure 1 may then end.
  • Event ⁇ may correspond to an event where the human operator consults the self-peration function regarding an expected result of an intended operation.
  • rocedure 1 may be invoked to perform the following: ⁇ a)
  • the human operator may send a consultation request to the self-operation function.
  • the consultation request may be sent with certain given elements) "x" of an assumed self-operation case, in the form of, for example, ConsultationRequest(x).
  • the "x" can correspond to "an HO optimization operation for Cell i to Cell j" and/or "an intended operation to perform load balancing between radio access 1 and radio access 2.”
  • the self-operation function may perform a similarity analysis between the given "x" and the stored self-operation cases. This similarity analysis may be able to find one or more other matching elements) *(y) for the assumed self-operation case.
  • x and y may provide all of the elements for the assumed self-operation case.
  • “y” may be determined from a self-operation case that has "x" elements) and "y" elements) in it. If there are a plurality of such self-operation cases, multiple “y”s may be found.
  • Such a self-operation case may correspond to the elements of x and y, where different matching self-operation cases may have different (actual) y elements / value of the elements.
  • the self-operation function may respond to the human operator with the found elements *(y), in the form of, for example, ConsultationResponse(*(y)).
  • the human operator may derive the expected result from x and *(y).
  • Event ⁇ may correspond to an event where the human operator sends a manual operation command to an OSS/network function (where the operation command may be sent via a self-operation function or may be monitored by the self-operation function ).
  • the manual operation command may include at least one of: (1) information indicating a function, (2) information indicating an instance. (3) information indicating a sequence number, and/or (4) information indicating an action.
  • the manual operation command may be in the form of, for example, Operation ( ⁇ functionID>, ⁇ instanceID>, ns hm , action ).
  • Procedure 1 may be invoked to perform the following:
  • the self-operation function may receive Operation( ⁇ functionID>, ⁇ in stance I D>, ns hm , action).
  • ns hm may be a unique sequence number that is assigned to identify the operation taken by the human operator. Any further messages of the operation will be identified with its sequence number so that the coming result of this operation can be linked to the operation.
  • the notification may be sent via the self-operation function.
  • the self-operation function may receive this corresponding notification
  • Procedure 1 may also invoke Procedure 2 (D.) to construct the corresponding self-operation case of this human manual operation.
  • Procedure 1 may then be ended.
  • Procedure 2 may be directed to a self-construction of a self-operation case.
  • Procedure 2 may be invoked to construct a self-operation case by one of the specifically defined events (A.-B.) accordingly:
  • Procedure 2 may be invoked to do the following: ⁇ 1) Procedure 2 may be invoked to extract the event element from the request of the OSS/network function, RequestActionRecommendation (functionID, instancelD, sn f , context f , event f )
  • Procedure 2 may extract the context element from the request of the self- operation function, RequestActionRecommendation (functionID, instancelD, sn so , context so , event f )
  • Procedure 2 may extract the action element from the human operator response, ResponseActionRecommendation(sn so , action)
  • Procedure 2 may extract the result element from this notification, where the functionID, instancelD, and sn f together identify the corresponding function, event f , context so , and action of the result.
  • Procedure 2 may analyze the relation between the elements of contextso, event f , action, and result.
  • Procedure 2 may analyze the relation between the elements and summarize the relation as: "if the context appears, the event will be triggered, and the corresponding action will be taken and the certain result will be achieved.” Later, when there are more stored similar cases, the analysis can even provide different possible relations that may be found from all of the similar self-operation cases, and the possibilities of the relations, between the elements.
  • a profile of a self-operation case can be updated after the creation of the case.
  • Procedure 2 may also assign the result/consequence of the analysis to the profile element.
  • Procedure 2 may also generate a new groupID.
  • Procedure 2 may also create and store the corresponding self-operation case (context so , event f , action, result, profile, groupID) with the above information.
  • Procedure 2 may then be ended.
  • Procedure 2 may be invoked to perform the following: ⁇ 1) When receiving the result from the notification, Notification(functionID, instancelD, sf f , result), Procedure 2 may extract the result element from this notification, where the functionID, instancelD, and sn f may together identify the corresponding function, event f , context so , and action of the result.
  • Procedure 2 may analyze the relation between the elements of the context so , event f , action, and result of the current self-operation case, and Procedure 2 may fill the analytic outcome as the profile of the current self-operation case.
  • Procedure 2 may create and store the corresponding self-operation case (context so , event f , action, result, profile, groupID) with the above information.
  • Procedure 2 may be ended.
  • Procedure 2 may be invoked to perform the following:
  • Procedure 2 may extract the information of context f , event f , action, result from the notification.
  • the self-operation function may extend context f into context so , based on the other context received. Otherwise, context so may correspond to context f .
  • the self-operation function may decide if such an extension would be needed.
  • Procedure 2 may analyze the relation between the elements of context so , event f , action, and result.
  • Procedure 2 may assign the consequence of the analysis to the profile element.
  • Procedure 2 may perform a similarity analysis to determine if the initiated self-operation case is similar to or the same as any stored self-operation case(s). If the similarity analysis indicates that the initiated self-operation case is similar to or the same as a stored self-operation case(s), Procedure 2 may assign the groupID with the corresponding ID of the store self-operation case(s). Otherwise, Procedure 2 may generate a new groupID.
  • Procedure 2 may create and store the corresponding self-operation case (context so event f , action, result, profile, groupID) with the above information.
  • Procedure 2 may be ended.
  • Procedure 2 may be invoked to do the following:
  • Procedure 2 may extract the information of an action from the operation.
  • Procedure 2 may extract the result element from this notification.
  • Procedure 2 may extract context so from the information collected via the Notification (for example, any demanded context may be extracted).
  • Procedure 2 may assign "command" to event f .
  • Procedure 2 may analyze the relation between the elements of context so , "command”, action, and result.
  • Procedure 2 rnay assign the consequence/result of the analysis to the profile element.
  • Procedure 2 may perform a similarity analysis to check if the initiated self- operation case is similar to or the same as stored self-operation case(s). If the initiated self-operation case is similar to or the same as a stored self-operation case, Procedure 2 may assign the groupID with the corresponding ID of the stored self-operation case(s). Otherwise, Procedure 2 may generate a new groupID.
  • Procedure 2 may create and store the corresponding self-operation case (context so , "command", action, result, profile, groupID) with the above information. o 1[0) Procedure 2 may be ended. [0063] Certain embodiments may be directed to providing consultation services based on the stored self-operation cases.
  • the self-operation function (with its stored self-operation cases) may serve the network operations in two ways.
  • the self-operation function may answer a human operator's questions regarding an expected result in view of an unknown element of an assumed/intended self-operation case (context, event, action, result, profile, groupID).
  • the answer to the operator's questions may be determined through a similarity analysis based on the known/assumed elements. For example, the operator can ask the self-operation function, "What result would be achievable given a specific context and action?"
  • the self-operation function may answer the human operator with ail the results that match the given context and action, such as * (event, result, profile, groupID).
  • the profile and groupID elements may possibly not participate in the similarity analysis for expected situations. However, if a match is found, certain embodiments may indicate the profile and groupID information concerning the expected situation from that matching.
  • An example of such an answer can be "(any, KPIx improvement, likelihood 93%, 1031)".
  • Certain embodiments may also answer a request from an OSS/network function with steps (a) - (g) of the Procedure l(a.).
  • Certain embodiments may import/retrieve self-operation cases from external sources.
  • the operations of a network can also generate other operation-related data.
  • Other self-operation cases may be extracted from those operation-related data by an outside function. If these self-operation cases are extracted according to the definition of a self- operation case, in accordance with certain embodiments, these self- operation cases can be imported from external sources. With the imported self- operation cases, the self-operation function should have more knowledge to make its autonomous decisions, which helps to minimize the human operator's role such that the operator merely setting operation targets.
  • Certain embodiments of the present invention may be a part of the sell -operation of
  • 5G networks Certain embodiments for 5G networks may be shown in Fig. 1. Certain embodiments may work with potentially incomplete and inconsistent rules/ontology, for example. The problems of missing rules/ontology and rule/ontology inconsistency may be resolved by certain embodiments during the actual operations, through learning self- operation cases and applying the cases to the actual operations and to human operator consultation.
  • a self-operation function may correspond to an individual product implemented over an interface-N (itf-N). Corresponding messages and information elements that cross the itf-N may be supported by standardization or OSSii. In order to be supported by standardization, some "standardization" work may be expected to be directed to itf-N or OSSii.
  • the self-operation function may be configured to be multi-vendor capable.
  • Fig. 3 illustrates a flowchart of a method in accordance with certain embodiments of the invention.
  • the method illustrated in Fig. 3 includes, at 310, receiving, by a first network node, a request for a recommended action from a second network node.
  • the request comprises an event information and a context information.
  • the method may also include, at 320, performing a similarity analysis to determine if the first network node has stored a self- operation case that relates to the request.
  • the method may also include, at 330, determining a recommended action based on the similarity analysis.
  • the method may also include, at 340, transmitting the recommended action to the second network node.
  • Fig. 4 illustrates a flowchart of a method in accordance with certain embodiments of the invention.
  • the method illustrated in Fig. 4 includes, at 410, receiving, by a network node, a consultation request for an expected result of a given operation.
  • the consultation request is received from a human operator.
  • the method may also include, at 420, performing a similarity analysis to determine if the network node has stored a self-operation case that relates to an element of the consultation request.
  • the method may also include, at 430, transmitting a result of the similarity analysis to the human operator.
  • Fig. 5 illustrates a flowchart of a method in accordance with certain embodiments of the invention.
  • the method illustrated in Fig. 5 includes, at 510, receiving, by a first network node, an operation from a human operator.
  • the method may also include, at 520, forwarding the operation to a second network node.
  • the method may also include, at 530, receiving a notification indicating a result of the operation.
  • the method may also include, at 540, transmitting the notification to the human operator.
  • Fig. 6 illustrates an apparatus in accordance with certain embodiments of the invention.
  • the apparatus can be a network node configured to perform a self-operation function and/or an OSS/network function, for example.
  • the apparatus can be a network node.
  • Apparatus 10 can include a processor 22 for processing information and executing instructions or operations.
  • Processor 22 can be any type of general or specific purpose processor. While a single processor 22 is shown in Fig. 6, multiple processors can be utilized according to other embodiments.
  • Processor 22 can also include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples.
  • DSPs digital signal processors
  • FPGAs field-programmable gate arrays
  • ASICs application-specific integrated circuits
  • Apparatus 10 can further include a memory 14, coupled to processor 22, for storing information and instructions that can be executed by processor 22.
  • Memory 14 can be one or more memories and of any type suitable to the local application environment, and can be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory.
  • memory 14 include any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non-transitory machine or computer readable media.
  • the instructions stored in memory 14 can include program instructions or computer program code that, when executed by processor 22, enable the apparatus 10 to perform tasks as described herein.
  • Apparatus 10 can also include one or more antennas (not shown) for transmitting and receiving signals and/or data to and from apparatus 10.
  • Apparatus 10 can further include a transceiver 28 that modulates information on to a carrier waveform for transmission by the antenna(s) and demodulates information received via the antenna(s) for further processing by other elements of apparatus 10.
  • transceiver 28 can be capable of transmitting and receiving signals or data directly.
  • Processor 22 can perform functions associated with the operation of apparatus 10 including, without limitation, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.
  • memory 14 can store software modules that provide functionality when executed by processor 22.
  • the modules can include an operating system 15 that provides operating system functionality for apparatus 10.
  • the memory can also store one or more functional modules 18, such as an application or program, to provide additional functionality for apparatus 10.
  • the components of apparatus 10 can be implemented in hardware, or as any suitable combination of hardware and software.
  • Apparatus 700 can be a network element/entity such as a network node that is configured to perform a self- operation function, for example.
  • Apparatus 700 can include a receiving unit 710 that receives a request for a recommended action from a network node. The request comprises an event information and a context information.
  • Apparatus 700 may also include a performing unit 720 that performs a similarity analysis to determine if the first network node has stored a self-operation case that relates to the request.
  • Apparatus 700 may also include a determining unit 730 that determines a recommended action based on the similarity analysis.
  • Apparatus 700 may also include a transmitting unit 740 that transmits the recommended action to the second network node.
  • Apparatus 800 can be a network element/entity such as a network node that is configured to perform a self- operation function, for example.
  • Apparatus 800 can include a receiving unit 810 that receives a consultation request for an expected result of a given operation. The consultation request is received from a human operator.
  • Apparatus 800 may also include a performing unit 820 that performs a simi larity analysis to determine if the network node has stored a self-operation case that relates to an element of the consultation request.
  • Apparatus 800 may also include a transmitting unit 830 that transmits a result of the similarity analysis to the human operator.
  • Apparatus 900 can be a network element/entity such as a network node that is configured to perform a self- operation function, for example.
  • Apparatus 900 can include a first receiving unit 910 that receives, by a first network node, an operation from a human operator.
  • Apparatus 900 may also include a forwarding unit 920 that forwards the operation to a second network node.
  • Apparatus 900 may also include a second receiving unit 930 that receives a notification indicating a result of the operation.
  • Apparatus 900 may also include a transmitting unit 940 that transmits the notification to the human operator.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé et un appareil qui peuvent comprendre la réception d'une demande d'une action recommandée provenant d'un nœud de réseau. La demande comprend des informations d'événement et des informations de contexte. Le procédé peut également comprendre l'exécution d'une analyse de similarité pour déterminer si l'appareil a mémorisé un cas d'auto-fonctionnement qui concerne la demande. Le procédé peut également consister à déterminer une action recommandée en fonction de l'analyse de similarité. Le procédé peut également consister à transmettre l'action recommandée au nœud de réseau.
EP15730410.6A 2015-05-29 2015-05-29 Procédé et appareil pour mettre en oeuvre des fonctions d'auto-fonctionnement dans un réseau Withdrawn EP3304965A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2015/061927 WO2016192746A1 (fr) 2015-05-29 2015-05-29 Procédé et appareil pour mettre en œuvre des fonctions d'auto-fonctionnement dans un réseau

Publications (1)

Publication Number Publication Date
EP3304965A1 true EP3304965A1 (fr) 2018-04-11

Family

ID=53442728

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15730410.6A Withdrawn EP3304965A1 (fr) 2015-05-29 2015-05-29 Procédé et appareil pour mettre en oeuvre des fonctions d'auto-fonctionnement dans un réseau

Country Status (2)

Country Link
EP (1) EP3304965A1 (fr)
WO (1) WO2016192746A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3596989B1 (fr) 2017-03-15 2024-03-27 Nokia Technologies Oy Procédé, support de stockage non transitoire lisible par ordinateur et appareil de demande et de fourniture de service de réseau automatique assistée dans un environnement de réseau
EP3673686A1 (fr) 2017-08-23 2020-07-01 Nokia Solutions and Networks Oy Évaluation et gestion automatiques d'expériences de resélection de tranche
US11405263B2 (en) 2018-02-02 2022-08-02 Nokia Solutions And Networks Oy Using self-operation cases to identify and resolve issues causing network slice reselection
US10728954B2 (en) 2018-08-07 2020-07-28 At&T Intellectual Property I, L.P. Automated network design and traffic steering
WO2020048594A1 (fr) * 2018-09-06 2020-03-12 Nokia Technologies Oy Procédure d'optimisation d'un réseau auto-organisateur

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Telecom Management: Principles and high level requirements (Release 1999)", 3GPP STANDARD; 3G TS 32.101, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V3.2.0, 1 July 2000 (2000-07-01), pages 1 - 39, XP050373923 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Fault Management; Part 1: 3G fault management requirements (Release 9)", 3GPP STANDARD ; TECHNICAL SPECIFICATION ; 3GPP TS 32.111-1, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V9.1.0, 20 March 2015 (2015-03-20), pages 1 - 19, XP051297522 *
See also references of WO2016192746A1 *

Also Published As

Publication number Publication date
WO2016192746A1 (fr) 2016-12-08

Similar Documents

Publication Publication Date Title
WO2016192746A1 (fr) Procédé et appareil pour mettre en œuvre des fonctions d'auto-fonctionnement dans un réseau
US10225145B2 (en) Method and device for updating client
CN107302443B (zh) 基于网络配置协议的设备配置方法及装置
US9467499B2 (en) Method and management apparatus for performing operation on device resource
US10187272B2 (en) Interface management service entity, function service entity, and element management method
US20170163478A1 (en) Method,electronic device and system for updating client configuration in key-value pair database
US9009306B2 (en) Method, system, client and server for locating operation nodes in communication system
US10715628B2 (en) Attribute operating method and device
CN113162888B (zh) 安全威胁事件处理方法、装置及计算机存储介质
CN114090388A (zh) 信息获取方法、服务器集群、服务器及设备
US10205767B2 (en) Management system and method for a big data processing device
US11088989B2 (en) Semantic validation method and apparatus
CN105955790B (zh) 数据处理方法及装置
US11985029B2 (en) Pico-base station configuration method and apparatus, storage medium and electronic apparatus
US20130046888A1 (en) Method and device for managing devices in device management system
CN107425994B (zh) 一种实现参数远程管理的方法、终端和服务器
US20180124576A1 (en) Method and apparatus for implementing member resource processing
US20210274023A1 (en) Apparatus control method, device, control node, network apparatus and data center
US20180183861A1 (en) Internet-of-things transaction resoruce with finite state automata
US10033528B2 (en) Method of communicating between a server and a secure element
CN111385110B (zh) 网络的管理方法及装置
US20210127014A1 (en) Methods and devices for using a uniform application program interface for validation and recovery
KR101792331B1 (ko) M2M/IoT 플랫폼에서 트랜잭션 방법 및 시스템
KR102528717B1 (ko) 보안 기능을 지원하는 api 통합 처리를 위한 게이트웨이 장치 및 이의 동작 방법
CN110083442B (zh) 一种用户任务的操作方法、服务器及可存储介质

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180102

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20190328

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SOLUTIONS AND NETWORKS OY

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20211118

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

INTC Intention to grant announced (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20220510

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20220921