CN106484381B - data center model, information processing method and device - Google Patents

data center model, information processing method and device Download PDF

Info

Publication number
CN106484381B
CN106484381B CN201510546724.0A CN201510546724A CN106484381B CN 106484381 B CN106484381 B CN 106484381B CN 201510546724 A CN201510546724 A CN 201510546724A CN 106484381 B CN106484381 B CN 106484381B
Authority
CN
China
Prior art keywords
object instance
state
information
dependency relationship
instance
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.)
Active
Application number
CN201510546724.0A
Other languages
Chinese (zh)
Other versions
CN106484381A (en
Inventor
齐飞
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.)
Huawei Cloud Computing Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201510546724.0A priority Critical patent/CN106484381B/en
Publication of CN106484381A publication Critical patent/CN106484381A/en
Application granted granted Critical
Publication of CN106484381B publication Critical patent/CN106484381B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Debugging And Monitoring (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiment of the invention discloses information processing methods, which are applied to a data center model provided by the invention, wherein the data center model comprises a th object instance and a second object instance, a th object instance and the second object instance have a dependency relationship, and the function realization of the second object instance depends on the function realization of the th object instance, the method comprises the steps of obtaining the information of the th object instance, determining the state of an th object instance according to the information of the th object instance, determining the logic state of the second object instance according to the state of the th object instance and the dependency relationship between the th object instance and the second object instance, and storing the logic state of the second object instance.

Description

data center model, information processing method and device
Technical Field
The invention relates to the field of computers, in particular to data center models, information processing methods and devices.
Background
Data Centers (DC) often contain a large number of devices, with different devices providing different functions at different levels. In the prior art, a data center administrator needs to manage the devices of the data center on different levels by using different management software, for example, network management software is used for managing network connection, virtualization management software is used for managing virtualized devices, and service management software is used for managing application programs. Since a data center administrator manages equipment and needs to master a plurality of management software, great inconvenience is caused to the administrator.
In order to solve the technical problem, the management software of the system of the data center is developed, the management software of the system can be compatible with the management software of each layer, and the data provided by the management software of each layer are aggregated to be analyzed and processed, so that the purpose of managing the devices on different layers is achieved, in order to achieve the purpose of managing the devices of the data center by the system , the management software of the system needs to model the management objects of the management systems on different layers by the system , and how to model based on the data center is a difficult point of designing the management software of the system .
For example, referring to fig. 1, a th switch of the physical layer corresponds to a th switch server in a two-layer network, and a gateway server in a three-layer network, a switch port a of the physical layer corresponds to a Lan (local area network) port a of a th switch server in the two-layer network, and a physical port a of the physical layer also corresponds to an ip (internet protocol) port in the three-layer network.
However, in practical application, due to reasons, the information of the object instance is completely missing, so that the state of the object instance cannot be updated in time, or the information of the object instance is partially missing, so that the state of the object instance is updated in time, but is not comprehensive, so that when a system or an administrator performs analysis according to the state of the object instance, the analysis may be inaccurate, or even the result of an analysis error may be caused.
For example, in the prior art, the state of the object instance is used as an input, the root cause of the system failure is analyzed through the failure correlation matrix, and if the state of the object instance is not updated in time or the updated state is incomplete, the analyzed result may be inaccurate.
Assuming that the physical port a in fig. 1 fails due to damage, because a physical port a failure may cause a Lan port access failure, in an ideal case, the system should receive alarm information of "physical port a failure" and "Lan port a access failure", and should determine that the state of the physical port a is a failure according to the alarm information of "physical port a failure", and determine that the state of the Lan port a is a failure according to the alarm information of "Lan port a access failure".
The above example takes the alarm information as an example, which illustrates that, when the information of the object instance is totally or partially missing, the analysis result of the system management software information may be inaccurate or even wrong, and the information of the object instance not only includes the alarm information but also includes other non-alarm information, and the purpose of information analysis is not only to determine the root of the fault, but also may have other analysis purposes.
Disclosure of Invention
In order to solve the above technical problem, embodiments of the present invention provide data center models, information processing methods and apparatuses, which play a role in updating and supplementing the state of an object instance, thereby improving the accuracy of analysis performed by a system or an administrator according to the state of the object instance.
, the embodiment of the invention provides data center model, the model comprises a physical layer and at least network topology layers, the physical layer comprises physical object instances and connection relations between the physical object instances, the network topology layers comprise logical object instances established according to logical functions expressed by the physical object instances in the network topology layers, and the connection relations between the logical object instances, the physical object instances and the logical object instances are both called object instances;
the model also includes dependencies between the object instances, which means that the functional implementation of object instances is dependent on the functional implementation of another object instances.
In a th possible implementation manner of the aspect of , the dependency relationship includes a dependency relationship and a mapping relationship, where the dependency relationship means that object instances are functionally and structurally dependent on object instances of the same layer, and the dependent object instances are functionally and functionally dependent on the functional implementation of the dependent object instances;
the mapping relation refers to the relation between object instances at a low level and object instances established by the logical functions of the object instances represented at a high level, and the functional implementation of the object instances at the high level depends on the functional implementation of the object instances at the low level.
In a second aspect, an embodiment of the present invention provides information processing methods, where the method is applied to the data center model provided in the embodiment of the present invention in the aspect, the data center model includes a th object instance and a second object instance, the th object instance and the second object instance have the dependency relationship, and a functional implementation of the second object instance depends on a functional implementation of the th object instance;
the method comprises the following steps:
acquiring information of object instance, and determining the state of object instance according to the information of object instance;
determining a logical state of the second object instance according to the state of the th object instance and a dependency relationship between the th object instance and the second object instance;
storing a logical state of the second object instance.
In possible implementation manners of the second aspect, the method further includes:
acquiring information of the second object instance, and determining the actual state of the second object instance according to the information of the second object instance;
if the actual state is the same as the logic state, the storing the logic state of the second object instance specifically includes:
storing an actual state or the logical state of the second object instance.
In a second possible implementation manner of the second aspect, the method further includes: the fault level corresponding to the logic state of the second object instance is a logic fault level; the fault grade corresponding to the actual state of the second object instance is an actual fault grade;
if the actual state is different from the logic state, the storing the logic state of the second object instance includes:
if the actual fault level is higher than the logic fault level, storing the actual state of the second object instance;
storing the logical state of the second object instance if the logical failure level is higher than the actual failure level;
if the actual failure level is equal to the logical failure level, storing the logical state and/or the actual state of the second object instance.
With reference to the second aspect or the th or second possible implementation manner of the second aspect, in a third possible implementation manner, the information of the object instance includes the information of the th object instance and the second information of the th object instance;
the determining the state of the th object instance according to the information of the th object instance comprises:
determining state of the th object instance according to the information of the th object instance;
determining a second state of the th object instance according to second information of the th object instance;
if the th state is the same as the second state, then the th state or the second state is taken as the state of the th object instance.
With reference to the third possible implementation manner of the second aspect, in a fourth possible implementation manner, the fault level corresponding to the th state is a th fault level, and the fault level corresponding to the second state is a second fault level;
if the th state is different from the second state and the th failure level is higher than the second failure level, then the th state is taken as the th object instance's state;
if the th state is different from the second state and the second failure level is higher than the th failure level, then the second state is taken as the state of the th object instance;
if the th state is different from the second state and the th failure level is equal to the second failure level, then the th state and/or the second state are taken as the state of the th object instance.
In a fifth possible implementation manner of the second aspect, the data center model further includes a third object instance, where the third object instance has the dependency relationship with the second object instance, and a functional implementation of the third object instance is dependent on a functional implementation of the second object instance;
after storing the logical state of the second object instance, the method further comprises:
determining the logic state of the third object instance according to the state of the second object instance and the dependency relationship between the second object instance and the third object instance;
storing a logical state of the third object instance.
In a sixth possible implementation manner of the second aspect, the data center model further includes a fourth object instance, where the fourth object instance has the dependency relationship with the second object instance, and a functional implementation of the fourth object instance is dependent on a functional implementation of the second object instance;
after storing the logical state of the second object instance, the method further comprises:
obtaining a dependency relationship between the object instance and the fourth object instance according to the dependency relationship between the object instance and the second object instance and the dependency relationship between the fourth object instance and the second object instance;
determining a logical state of the fourth object instance according to the state of the object instance and a dependency relationship between the object instance and the fourth object instance;
storing a logical state of the fourth object instance.
In a third aspect, information processing apparatuses are provided, where the apparatuses are applied to the data center model provided in the embodiments of the present invention in the aspect, the data center model includes a th object instance and a second object instance, the th object instance and the second object instance have the dependency relationship, and the functional implementation of the second object instance depends on the functional implementation of the th object instance;
the device comprises an th acquisition unit, a th determination unit, a logic state determination unit and a th storage unit, wherein the th acquisition unit is connected with the th determination unit, the th determination unit is connected with the logic state determination unit, and the logic state determination unit is connected with the th storage unit;
the acquisition unit is used for acquiring information of an object instance;
the logic state determining unit is used for determining the logic state of the second object instance according to the state of the th object instance and the dependency relationship between the th object instance and the second object instance;
the th storage unit is used for storing the logic state of the second object instance.
In possible implementation manners of the third aspect, the apparatus further includes a second obtaining unit and a second determining unit, the second obtaining unit is connected to the second determining unit, and the second determining unit is connected to the storage unit;
the second obtaining unit is used for obtaining the information of the second object instance;
the second determining unit is used for determining the actual state of the second object instance according to the information of the second object instance;
the th storage unit includes a th storage sub-unit;
the th storage subunit is configured to store an actual state or a logical state of the second object instance if the actual state is the same as the logical state.
With reference to the th possible implementation manner of the third aspect, in a second possible implementation manner, the apparatus further includes:
the fault level corresponding to the logic state of the second object instance is a logic fault level; the fault grade corresponding to the actual state of the second object instance is an actual fault grade;
the th storage unit comprises a second storage sub-unit, a third storage sub-unit or a fourth storage sub-unit;
the second storage subunit is configured to store the actual state of the second object instance if the actual state is different from the logical state and the actual failure level is higher than the logical failure level;
the third storage subunit is configured to store the logic state of the second object instance if the actual state is different from the logic state and the logic failure level is higher than the actual failure level;
the fourth storage subunit is configured to store the logic state and/or the actual state of the second object instance if the actual failure level is equal to the logic failure level.
With reference to the third aspect or the or the second possible implementation manner of the aspect, in a third possible implementation manner, the information of the th object instance includes th information of the th object instance and second information of the th object instance;
the determining unit, configured to determine the status of the th object instance according to the th object instance information, includes:
the determining unit is used for determining the th state of the th object instance according to the th information of the th object instance, determining the second state of the th object instance according to the second information of the th object instance, and taking the th state or the second state as the th object instance if the th state is the same as the second state.
With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner, the fault level corresponding to the th state is a th fault level, and the fault level corresponding to the second state is a second fault level;
the th determination unit is further configured to:
if the th state is different from the second state and the th failure level is higher than the second failure level, then the th state is taken as the th object instance's state;
if the th state is different from the second state and the second failure level is higher than the th failure level, then the second state is taken as the state of the th object instance;
if the th state is different from the second state and the th failure level is equal to the second failure level, then the th state and/or the second state are taken as the state of the th object instance.
In a fifth possible implementation manner of the third aspect, the data center model further includes a third object instance, where the third object instance and the second object instance have the dependency relationship, and a functional implementation of the third object instance is dependent on a functional implementation of the second object instance;
the device also comprises a third determining unit and a second storage unit, wherein the th storage unit is connected with the third determining unit, and the third determining unit is connected with the second storage unit;
the third determining unit is used for determining the logic state of the third object instance according to the state of the second object instance and the dependency relationship between the second object instance and the third object instance;
the second storage unit is used for storing the logic state of the third object instance.
In a sixth possible implementation manner of the third aspect, the data center model further includes a fourth object instance, where the fourth object instance has the dependency relationship with the second object instance, and a functional implementation of the fourth object instance is dependent on a functional implementation of the second object instance;
the device also comprises a dependency relationship calculation unit, a fourth determination unit and a third storage unit, wherein the th storage unit is connected with the dependency relationship calculation unit, the dependency relationship calculation unit is connected with the fourth determination unit, and the fourth determination unit is connected with the third storage unit;
a dependency relationship calculation unit, configured to obtain a dependency relationship between the th object instance and the fourth object instance according to a dependency relationship between the th object instance and the second object instance and a dependency relationship between the fourth object instance and the second object instance;
the fourth determination unit is used for determining the logic state of the fourth object instance according to the state of the th object instance and the dependency relationship between the th object instance and the fourth object instance;
the third storage unit is configured to store a logic state of the fourth object instance.
The invention provides different data center models from the prior art, wherein the models comprise a physical layer and at least network topology layers, the physical layer comprises physical object instances and connection relations among the physical object instances, the network topology layers comprise logical object instances established according to logical functions expressed by the physical object instances in the network topology layers, and the connection relations among the logical object instances, the physical object instances and the logical object instances are called object instances, the data center models comprise object instances and second object instances, the object instances and the second object instances have the dependency relations, and the function implementation of the second object instances depends on the function implementation of the object instances, the data center models provided by the invention have the dependency relations among the second object instances and the object instances, when the state of the object instances is determined according to the information of the object instances, the state instances can be updated according to the state of the object instances and object instances, and the state of the second object instances can be accurately updated according to the state of the second object instances.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic diagram of a prior art data center model;
FIG. 2 is a schematic diagram of a data center model provided by an embodiment of the invention;
FIG. 3 is a flow chart of an embodiment of methods for processing information according to the present invention;
FIG. 4 is a flowchart of a second embodiment of methods for processing information according to the present invention;
FIG. 5 is a flowchart of a third embodiment of methods for processing information according to the present invention;
FIG. 6 is a flowchart of a fourth embodiment of methods for processing information according to the present invention;
FIG. 7 is a flow chart of an embodiment five of information processing methods provided by the invention;
FIG. 8 is a block diagram of an embodiment of information processing apparatuses according to the present invention;
FIG. 9 is a block diagram of a second embodiment of types of information processing apparatuses provided by the present invention;
FIG. 10 is a block diagram of a third embodiment of types of information processing apparatuses provided by the present invention;
fig. 11 is a block diagram of a fourth configuration of information processing apparatuses according to a fourth embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only partial embodiments of of the present invention, rather than all embodiments.
In practical application, due to reasons, the information of the object instance is totally missing, so that the state of the object instance cannot be updated in time, or the information of the object instance is partially missing, so that the state of the object instance is updated in time but is incomplete, and therefore, when the management software of the system analyzes according to the state of the object instance, the analysis may be inaccurate, and even wrong analysis results are obtained.
In order to overcome the technical problem, the data center model is provided, the model comprises a physical layer and at least network topology layers, the physical layer comprises physical object instances and connection relations among the physical object instances, the network topology layers comprise logical object instances established according to logical functions expressed by the physical object instances in the network topology layers, and the connection relations among the logical object instances, the physical object instances and the logical object instances are both called object instances.
The dependency relationship comprises the dependency relationship and a mapping relationship, wherein the dependency relationship means that object instances are subordinate to object instances of the same layer in functional structure, the subordinate object instances depend on the functional implementation of the subordinate object instances in functional implementation, for example, referring to fig. 2, a physical port a of a physical layer is subordinate to a th switch, a Lan port a of a second layer in a network topology layer is subordinate to a th switch server, and IP ports of a third layer in the network topology layer are subordinate to a gateway server.
For example, referring to fig. 2, the functional implementation of the Lan port a at the second layer in the network topology layer depends on the physical port a at the physical layer, and the functional implementation of the IP port at the third layer in the network topology layer depends on the Lan port a at the second layer.
The low level is , which is a physical layer, and the high level is a network topology layer, such as two or three layers in fig. 2, and the low level and the high level are both network topology layers, such as two layers in fig. 2 and three layers in high level.
It should be noted that the dependency between two object instances is typically unidirectional, i.e., if object instance a depends on object instance B, then object instance B cannot depend on object instance a.
In practical application, a cim (common Information model) model may be used to establish the object instances and the dependency relationships between the object instances, or the cim model may be abstracted and modeled according to the function of each layer in a TCP/IP (Transmission control Protocol/Internet Protocol) multi-layer structure model. Since the above two modeling means are commonly used by those skilled in the art, the present invention does not give further details on the specific modeling steps and methods.
Method example
Based on the data center model provided by the invention, the invention provides embodiments of the information processing method , wherein the th object instance and the second object instance in the information processing method are two object instances in the data center model, and the functional implementation of the second object instance depends on the functional implementation of the th object instance.
Referring to fig. 3, the information processing method provided in this embodiment includes the following steps:
step S101, obtaining th object instance information, and determining the th object instance state according to the th object instance information.
In this embodiment, the system management software determines the state of the th object instance by obtaining information of the th object instance, where the information includes alarm information and non-alarm information, where the alarm information refers to information that the object instance monitored by the hierarchical management software is in an abnormal state, for example, the host temperature is higher than a preset maximum temperature, and the non-alarm information refers to information that the object instance monitored by the hierarchical management software is in a normal state, for example, the host temperature is lower than the preset maximum temperature, there are various ways to obtain information, for example, the system 1 management software actively, periodically or aperiodically collects information generated by each hierarchical management software, or the hierarchical management software actively, periodically or aperiodically pushes information of an object embodiment of a corresponding layer to the system management software, or the like to the system management software, and in any way, the rd object instance cannot directly interact with the system management software, and thus, in the information, the location information carrying the corresponding object instance of the "Lan access information" Lan ", the switch 23 st object instance may be identified as a physical switch , and thus, the switch may be located by the switch physical switch , and the switch , the switch may be identified as the physical switch, and the physical switch , where the switch may be located, and the switch, the physical switch may be identified as the physical switch , and the physical switch, and the physical switch, thus, the physical port, where the physical switch, the physical port may be identified as the physical switch, the physical port, and the physical port, may be identified as the.
In the implementation, after the th object instance information is acquired, the status of the th object instance is determined according to the th object instance information.
In this embodiment, the type of the state of the object instance is different according to the different types of the information of the th object instance, if the information of the th object instance is non-alarm information, the state of the th object instance is a normal state, for example, if the information of the th object instance is normal for IP access, the state of the th object instance may be "normal for IP access", if the information of the th object instance is alarm information, the state of the th object instance is a fault state, for example, if the information of the th object instance is a fault for IP access, the state of the th object instance may be "fault for IP access". the "fault" refers to a case where an anomaly occurs in sense, for example, a network traffic anomaly, a CPU overload (for example, an occupancy of 90% for a server is down, but no misconjugation is included, which means that the management software cannot monitor the managed object instance within minutes, and therefore, the second object instance may be in a status of the second object instance, if the second object instance is in which the status of the second object instance is calculated by the object instance is not normal status of the second object instance, and the status of the second object instance is calculated according to the step S .
For example, in practical applications, since different physical devices may be provided by different vendors and different network topology layers may be provided by different operators, the descriptions of the same cases of the same object instances may be different for different vendors or operators, for example, when an IP access failure occurs, the information provided by different vendors is "IP access failure" and the information provided by ericsson is "IP unreachable", which means the same information is completely the same, in order to facilitate management for the administrator and the system, the two information may be converted into 3528 states that the management software can identify by itself, for example, the two information ports 2 are determined to be in the access failure state, so the invention may determine how to determine the actual state of the object instance 73 3 according to the rules of the state determination technology of the object instance .
Besides, information record tables are respectively set for each object instance, and the information record tables are used for recording the information received by the corresponding object instance, so that the administrator can conveniently view the information when needed.
Step S102, determining the logic state of the second object instance according to the state of the th object instance and the dependency relationship between the th object instance and the second object instance.
In this embodiment, if the status of the th object instance is determined, the logical status of the second object instance is determined according to the status of the th object instance and the dependency relationship between the th object instance and the second object instance, and the logical status of the second object instance is the status that the second object instance should theoretically show, if the status of the th object instance is the normal status, the logical status of the second object instance is also the normal status, and if the status of the th object instance is the fault status, the status of the second object instance may be the fault status and may be the normal status.
Or, even if the system management software receives the information of the second object instance, but the actual state of the second object instance determined by the information is not the same as the logical state of the second object instance, indicating that the information corresponding to the logical state of the second object instance is likely to be lost, the present embodiment achieves the purpose of updating and supplementing the state of the second object instance by storing the logical state of the second object instance and using the logical state of the second object instance as of the state of the second object instance, and also improves the accuracy of the system or the administrator analyzing according to the state of the second object instance.
Of course, if the actual state of the second object instance determined according to the information of the second object instance is the same as the logic state of the second object instance, it indicates that the information corresponding to the logic state is not missing, and only states may be retained.
Step S103: storing a logical state of the second object instance.
According to the method, the information of the object instance is acquired, the state of the th object instance is determined according to the information of the th object instance, the state of the th object instance is guaranteed to be updated, then on the basis, the logic state of the second object instance is determined according to the state of the th object instance and the dependency relationship between the th object instance and the second object instance, and the logic state of the second object instance is stored.
Method embodiment two
Referring to fig. 4, it is a flowchart of a second embodiment of information processing methods provided by the present invention.
The information processing method provided by the embodiment comprises the following steps:
step S201, obtaining th object instance information, and determining the th object instance state according to the th object instance information.
And S202, determining the logic state of the second object instance according to the state of the th object instance and the dependency relationship between the th object instance and the second object instance, wherein the fault level corresponding to the logic state of the second object instance is a logic fault level.
Step S203: and acquiring information of a second object instance, and determining the actual state of the second object instance according to the information of the second object instance, wherein the fault level corresponding to the actual state of the second object instance is the actual fault level.
Step S204: judging whether the actual state is the same as the logic state, if so, executing step S205; if not, go to step S206;
step S205: and storing the actual state or the logic state of the second object instance, and ending the process.
Step S206: judging whether the actual fault level is higher than the logic fault level, if so, executing step S207; if not, step S208 is performed.
Step S207: and storing the actual state of the second object instance, and ending the process.
Step S208: judging whether the logic fault level is equal to the actual fault level, if so, executing step S209; if not, step S210 is performed.
Step S209: and storing the actual state and/or the logic state of the second object instance, and ending the process.
Step S210: and storing the logic state of the second object instance, and ending the process.
In the method embodiment , no matter whether the information of the second object instance is acquired, the logic state of the second object instance is used as the state of the second object instance to update and supplement the state of the second object instance, however, in practical application, if the information of the second object instance is received, two situations may occur, where is that the actual state of the second object instance determined according to the information of the second object instance is the same as the logic state, and in order not to generate redundant information and cause unnecessary burden to a system, this embodiment takes from both the actual state and the logic state to fill in the state list of the second object instance.
The method comprises the steps of obtaining a fault logic level of a first object instance, obtaining a fault logic level of a second object instance, obtaining a fault logic level of the first object instance, obtaining a fault logic level of the second object instance, and storing the fault logic level of the second object instance as a fault logic level, wherein the fault logic level of the second object instance is higher than the fault logic level of the first object instance, if the fault logic level of the second object instance is higher than the fault logic level of the first object instance, and the fault logic level of the second object instance is higher than the fault logic level of the second object instance.
In addition, the sequence of step S201 to step S210 provided in this embodiment does not limit the present invention, and in practical applications, step S203 does not occur after step S202, as long as it occurs before step S204 is executed.
Method embodiment three
Referring to fig. 5, it is a flowchart of a third embodiment of information processing methods provided by the present invention.
The information processing method provided by the embodiment comprises the following steps:
step S301, obtaining information of an object instance, wherein the information of the object instance comprises information of the 0 th object instance and second information of the th object instance, and step S302, determining a th state of the th object instance according to information of the th object instance, and a fault level corresponding to the th state is a th fault level.
And S303, determining a second state of the th object instance according to second information of the th object instance, wherein the fault level corresponding to the second state is a second fault level.
And step S304, judging whether the th state is the same as the second state, if so, executing step S305, and if not, executing step S306.
Step S305, the th state or the second state is taken as the state of the th object instance.
And step S306, judging whether the th fault level is higher than the second fault level, if so, executing step S307, and if not, executing step S308.
Step S307, the th state is taken as the state of the th object instance, and then step S310 is executed.
Step S308, judging whether the th fault level is equal to the second fault level, if not, executing step S309, and if so, executing step S310.
Step S309, the second state is taken as the state of the th object instance, and then step S311 is executed.
Step S310, the th state and/or the second state are/is taken as the state of the th object instance, and then step S311 is executed.
Step S311, determining the logic state of the second object instance according to the state of the th object instance and the dependency relationship between the th object instance and the second object instance.
Step S312: and storing the logic state of the second object instance, and ending the process.
In practical applications, there may be a case where the object instance receives a plurality of information, and in this case, the statuses of the object instance determined respectively according to the plurality of information may be the same or different, in this embodiment, the information and the second information are taken as representatives of the object instance receiving the plurality of information, and in order to avoid redundancy of information, only states are reserved when the state of the object instance determined according to the 2 information is the same as the second status of the object instance determined according to the second information.
On the premise that the th state and the second state are different, if the th fault level is higher than the second fault level, the th state is taken as the state of the th object instance, if the th fault level is lower than the second fault level, the second state is taken as the state of the th object instance, and if the th fault level is equal to the second fault level, the th state and/or the second state is taken as the state of the th object instance.
It is to be understood that, although the present invention distinguishes the scenario of the second method embodiment from the scenario of the third method embodiment as two separate scenarios, in practical applications, the two scenarios may occur simultaneously, and therefore, in another embodiments, the steps S201 to S210 and the steps S301 to S312 may be merged into method flows, which is not described herein again for reasons of brevity.
Method example four
Referring to fig. 6, it is a flowchart of an embodiment four of information processing methods provided by the present invention.
The information processing method provided by the embodiment comprises the following steps:
step S401, obtaining information of object instance, and determining state of object instance according to information of object instance.
Step S402, determining the logic state of the second object instance according to the state of the th object instance and the dependency relationship between the th object instance and the second object instance.
Step S403: storing a logical state of the second object instance.
Step S404: and determining the logic state of the third object instance according to the state of the second object instance and the dependency relationship between the second object instance and the third object instance.
Step S405: storing a logical state of the third object instance.
In practical applications, not every object instance with missing information, but with its directly dependent object instance having information, how to supplement the state of the object instance with missing information.
For example, in fig. 2, the functional implementation of the IP port depends on the functional implementation of the Lan port a, and the functional implementation of the Lan port a depends on the functional implementation of the physical port a, if the physical port a fails, the Lan port a access failure may be caused, and the Lan port a access failure may cause the IP port access failure, so in an ideal case, the system should receive three pieces of information, namely "physical port a failure", "Lan port a access failure", and "IP port access failure", and determine that the state of the physical port a is a failure according to the information of the "physical port a failure", determine that the state of the Lan port a is an access failure according to the information of the "Lan port a access failure", and determine that the state of the IP port is an access failure according to the information of the "IP port access failure". However, in practice, the information received by the system is "physical port a failure" and "IP packet loss ratio exceeds a threshold value", and the information of "Lan port a access failure" and "IP port access failure" is not received, then, by using the information processing method provided by this embodiment, according to the state of physical port a failure and the dependency relationship of Lan port a on physical port a, it can be determined that the state of Lan port a is Lan port a access failure; according to the access fault of the Lan port A and the dependency relationship of the IP port depending on the Lan port A, the state of the IP port can be determined to be the access fault of the IP port. Therefore, the state of the Lan port a is updated, and the state of the IP port is complemented. When the system utilizes the fault incidence matrix for analysis, the root cause of the fault can be determined according to the physical port A fault, the Lan port A access fault, the IP port access fault and the IP packet loss rate exceeding the threshold value, so that the accuracy of fault root cause analysis is improved.
Method example five
Referring to fig. 7, it is a flowchart of an embodiment five of information processing methods provided by the present invention.
The information processing method provided by the embodiment comprises the following steps:
step S401, obtaining information of object instance, and determining state of object instance according to information of object instance.
Step S402, determining the logic state of the second object instance according to the state of the th object instance and the dependency relationship between the th object instance and the second object instance.
Step S403: storing a logical state of the second object instance.
Step S404, obtaining the dependency relationship between the th object instance and the fourth object instance according to the dependency relationship between the th object instance and the second object instance and the dependency relationship between the fourth object instance and the second object instance.
Step S405, determining the logic state of the fourth object instance according to the state of the th object instance and the dependency relationship between the th object instance and the fourth object instance.
Step S406: storing a logical state of the fourth object instance.
In the fourth embodiment of the method, a layer-by-layer calculation manner is adopted to calculate the logic state of a third object instance which does not directly depend on a th object instance with information, but in the present embodiment, for a fourth object instance which does not directly depend on a th object instance, the dependency relationship between the th object instance and the second object instance and the dependency relationship between the second object instance and the fourth object instance can be obtained, the logic state of the fourth object instance is calculated by combining the states of the th object instance, and the logic state of the fourth object instance is taken as the state of the fourth object instance.
Apparatus embodiment
Referring to fig. 8, a block diagram of an embodiment of information processing apparatuses according to the present invention is shown.
The information processing apparatus provided by this embodiment is applied to the data center model provided by the present invention, wherein the data center model includes th object instance and second object instance, the th object instance and the second object instance have the dependency relationship, and the functional implementation of the second object instance depends on the functional implementation of the th object instance.
The device comprises an acquisition unit 11, a determination unit 12, a logic state determination unit 13 and a storage unit 14, wherein the acquisition unit 11 is connected with the determination unit 12, the determination unit 12 is connected with the logic state determination unit 13, and the logic state determination unit 13 is connected with the storage unit 14;
the th acquiring unit 11 is used for acquiring th object instance information;
the th determining unit 12 is used for determining the status of the th object instance according to the th object instance information;
the logic state determining unit 13 is configured to determine a logic state of the second object instance according to the state of the th object instance and a dependency relationship between the th object instance and the second object instance;
the th storage unit 14 is used for storing the logic state of the second object instance.
According to the method, the information of the object instance is acquired, the state of the th object instance is determined according to the information of the th object instance, the state of the th object instance is guaranteed to be updated, then on the basis, the logic state of the second object instance is determined according to the state of the th object instance and the dependency relationship between the th object instance and the second object instance, and the logic state of the second object instance is stored.
Device embodiment II
Referring to fig. 9, it is a block diagram of a second embodiment of information processing apparatuses according to the present invention.
On the basis of the device embodiment , the device further comprises a second obtaining unit 15 and a second determining unit 16, wherein the second obtaining unit 15 is connected with the second determining unit 16, and the second determining unit 16 is connected with the storage unit 14.
The second obtaining unit 15 is configured to obtain information of the second object instance.
The second determining unit 16 is configured to determine an actual state of the second object instance according to the information of the second object instance.
The th memory cell 14 includes a th memory sub-cell 141, a second memory sub-cell 142, a third memory sub-cell 143, or a fourth memory sub-cell 144.
The th storage subunit 141 is configured to store an actual state or a logical state of the second object instance if the actual state is the same as the logical state.
The second storage subunit 142 is configured to store the actual state of the second object instance if the actual state is different from the logic state and the actual failure level is higher than the logic failure level.
The third storage subunit 143 is configured to store the logic state of the second object instance if the actual state is different from the logic state and the logic failure level is higher than the actual failure level.
The fourth storage subunit 144 is configured to store the logic state of the second object instance and/or the actual state if the actual failure level is equal to the logic failure level.
The fault level corresponding to the logic state of the second object instance is a logic fault level; and the fault level corresponding to the actual state of the second object instance is an actual fault level.
In addition, in this implementation, the information of the th object instance includes th information of the th object instance and second information of the th object instance.
The determining unit 12, configured to determine the status of the th object instance according to the th object instance information, includes:
the determining unit 12 is configured to determine a th state of the th object instance according to the th information of the th object instance, determine a second state of the th object instance according to the th object instance, wherein the th state corresponds to a th failure level, and the second state corresponds to a second failure level;
if the th state is the same as the second state, then the th state or the second state is taken as the state of the th object instance;
if the th state is different from the second state and the th failure level is higher than the second failure level, then the th state is taken as the th object instance's state;
if the th state is different from the second state and the second failure level is higher than the th failure level, then the second state is taken as the state of the th object instance;
if the th state is different from the second state and the th failure level is equal to the second failure level, then the th state and/or the second state are taken as the state of the th object instance.
In this embodiment, when the th object instance has more than states, only the th object instance is reserved in a more serious state, and thus the number of logical states of the second object instance is also reduced, which effectively improves the efficiency of searching for the root cause of the fault by an administrator or a system.
Device embodiment III
Referring to fig. 10, it is a block diagram of a third configuration of information processing apparatuses according to a third embodiment of the present invention.
In this embodiment, the data center model further includes a third object instance, where the third object instance and the second object instance have the dependency relationship, and a functional implementation of the third object instance depends on a functional implementation of the second object instance.
On the basis of the device embodiment or on the basis of the device embodiment two (the situation on the basis of the device embodiment two is not shown in fig. 10), the device further comprises a third determining unit 17 and a second storage unit 18, wherein the storage unit 14 is connected with the third determining unit 17, and the third determining unit 17 is connected with the second storage unit 18;
the third determining unit 17 is configured to determine a logic state of the third object instance according to the state of the second object instance and a dependency relationship between the second object instance and the third object instance;
the second storage unit 18 is configured to store a logic state of the third object instance.
The embodiment adopts a layer-by-layer calculation mode to calculate the logic state of the third object instance which does not directly depend on the th object instance with information, and the update of the state of the third object instance is realized.
Example four of the device
Referring to fig. 11, it is a block diagram of an embodiment four of information processing apparatuses provided by the present invention.
The data center model further comprises a fourth object instance, the fourth object instance and the second object instance have the dependency relationship, and the functional implementation of the fourth object instance depends on the functional implementation of the second object instance;
on the basis of the device embodiment or the second device embodiment (the situation on the basis of the second device embodiment is not shown in FIG. 11), the device further comprises a dependency relationship calculation unit 19, a fourth determination unit 20 and a third storage unit 21, wherein the storage unit 14 is connected with the dependency relationship calculation unit 19, the dependency relationship calculation unit 19 is connected with the fourth determination unit 20, and the fourth determination unit 20 is connected with the third storage unit 21;
a dependency relationship calculating unit 19, configured to obtain a dependency relationship between the th object instance and the fourth object instance according to the dependency relationship between the th object instance and the second object instance and the dependency relationship between the fourth object instance and the second object instance;
the fourth determining unit 20 is configured to determine a logical state of the fourth object instance according to the state of the th object instance and a dependency relationship between the th object instance and the fourth object instance;
the third storage unit 21 is configured to store a logic state of the fourth object instance.
According to the embodiment, the dependency relationship between the th object instance and the fourth object instance is obtained according to the th object instance and the second object instance, and the dependency relationship between the fourth object instance and the second object instance, and the logic state of the fourth object instance which does not directly depend on the th object instance with information is calculated according to the th object instance state and the dependency relationship between the th object instance and the fourth object instance, so that the state of the fourth object instance is updated.
The '' of the th object instance mentioned in the embodiments of the present invention is used for name identification only and does not represent the th object instance in sequence.
It will be understood by those skilled in the art that all or part of the steps of the above method embodiments may be implemented by hardware associated with program instructions, the program may be stored in computer readable storage medium, and when executed, the program performs the steps of the above method embodiments, and the storage medium may be at least of read-only memory (ROM), RAM, magnetic disk or optical disk, and other various media capable of storing program code.
The above-described device and system embodiments are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e., may be located in places, or may be distributed on a plurality of network units.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (15)

1, A method of creating a data center model, the method comprising:
the data center model comprises a physical layer and at least network topology layers, wherein the physical layer comprises physical object instances and connection relations among the physical object instances;
the model also comprises dependency relationships among the object instances, wherein the dependency relationships mean that the functional implementation of object instances is dependent on the functional implementation of another object instances;
the model comprises a object instance and a second object instance, wherein the object instance and the second object instance have the dependency relationship, and the functional implementation of the second object instance depends on the functional implementation of the object instance;
after determining the state of the object instance, determining the logic state of the second object instance according to the the state of the object instance and the dependency between the the object instance and the second object instance;
the dependency relationship comprises a dependency relationship and a mapping relationship, wherein the dependency relationship means that object instances are functionally and structurally dependent on other object instances, and the dependent object instances are functionally dependent on the functional implementation of the dependent object instances;
the mapping relation refers to the relation between object instances at a low level and object instances established by the logic functions presented by the object instances at a high level.
2, information processing method, characterized in that, the method is applied to the data center model of claim 1, the data center model comprises object instance and second object instance, the object instance and the second object instance have the dependency relationship, and the functional implementation of the second object instance depends on the functional implementation of the object instance;
the method comprises the following steps:
acquiring information of object instance, and determining the state of object instance according to the information of object instance;
determining a logical state of the second object instance according to the state of the th object instance and a dependency relationship between the th object instance and the second object instance;
storing a logical state of the second object instance.
3. The method of claim 2, further comprising:
acquiring information of the second object instance, and determining the actual state of the second object instance according to the information of the second object instance;
if the actual state is the same as the logic state, the storing the logic state of the second object instance specifically includes:
storing an actual state or the logical state of the second object instance.
4. The method of claim 3, wherein the failure level corresponding to the logical state of the second object instance is a logical failure level; the fault grade corresponding to the actual state of the second object instance is an actual fault grade;
if the actual state is different from the logic state, the storing the logic state of the second object instance includes:
if the actual fault level is higher than the logic fault level, storing the actual state of the second object instance;
storing the logical state of the second object instance if the logical failure level is higher than the actual failure level;
if the actual failure level is equal to the logical failure level, storing the logical state and/or the actual state of the second object instance.
5. The method of any of claims 2 to 4, wherein the information of the object instance includes information of the object instance and second information of the object instance;
the determining the state of the th object instance according to the information of the th object instance comprises:
determining state of the th object instance according to the information of the th object instance;
determining a second state of the th object instance according to second information of the th object instance;
if the th state is the same as the second state, then the th state or the second state is taken as the state of the th object instance.
6. The method of claim 5, wherein the th state corresponds to a th fault level, and wherein the second state corresponds to a second fault level;
if the th state is different from the second state and the th failure level is higher than the second failure level, then the th state is taken as the th object instance's state;
if the th state is different from the second state and the second failure level is higher than the th failure level, then the second state is taken as the state of the th object instance;
if the th state is different from the second state and the th failure level is equal to the second failure level, then the th state and/or the second state are taken as the state of the th object instance.
7. The method of claim 2, wherein the data center model further comprises a third object instance, wherein the third object instance has the dependency relationship with the second object instance, and wherein the functional implementation of the third object instance is dependent on the functional implementation of the second object instance;
after storing the logical state of the second object instance, the method further comprises:
determining the logic state of the third object instance according to the state of the second object instance and the dependency relationship between the second object instance and the third object instance;
storing a logical state of the third object instance.
8. The method of claim 2, wherein the data center model further comprises a fourth object instance, the fourth object instance having the dependency relationship with the second object instance, a functional implementation of the fourth object instance being dependent on a functional implementation of the second object instance;
after storing the logical state of the second object instance, the method further comprises:
obtaining a dependency relationship between the object instance and the fourth object instance according to the dependency relationship between the object instance and the second object instance and the dependency relationship between the fourth object instance and the second object instance;
determining a logical state of the fourth object instance according to the state of the object instance and a dependency relationship between the object instance and the fourth object instance;
storing a logical state of the fourth object instance.
The information processing apparatus of 9, , wherein the apparatus is applied to the data center model of claim 1, the data center model comprises a th object instance and a second object instance, the th object instance and the second object instance have the dependency relationship, and the functional implementation of the second object instance depends on the functional implementation of the th object instance;
the device comprises an th acquisition unit, a th determination unit, a logic state determination unit and a th storage unit, wherein the th acquisition unit is connected with the th determination unit, the th determination unit is connected with the logic state determination unit, and the logic state determination unit is connected with the th storage unit;
the acquisition unit is used for acquiring information of an object instance;
the logic state determining unit is used for determining the logic state of the second object instance according to the state of the th object instance and the dependency relationship between the th object instance and the second object instance;
the th storage unit is used for storing the logic state of the second object instance.
10. The apparatus according to claim 9, further comprising a second obtaining unit and a second determining unit, wherein the second obtaining unit is connected to the second determining unit, and the second determining unit is connected to the storage unit;
the second obtaining unit is used for obtaining the information of the second object instance;
the second determining unit is used for determining the actual state of the second object instance according to the information of the second object instance;
the th storage unit includes a th storage sub-unit;
the th storage subunit is configured to store an actual state or a logical state of the second object instance if the actual state is the same as the logical state.
11. The apparatus of claim 10, further comprising:
the fault level corresponding to the logic state of the second object instance is a logic fault level; the fault grade corresponding to the actual state of the second object instance is an actual fault grade;
the th storage unit comprises a second storage sub-unit, a third storage sub-unit or a fourth storage sub-unit;
the second storage subunit is configured to store the actual state of the second object instance if the actual state is different from the logical state and the actual failure level is higher than the logical failure level;
the third storage subunit is configured to store the logic state of the second object instance if the actual state is different from the logic state and the logic failure level is higher than the actual failure level;
and the fourth storage subunit is configured to store the logic state of the second object instance and/or the actual state if the actual state is different from the logic state and the actual failure level is equal to the logic failure level.
12. The apparatus according to any of claims 9 to 11, wherein the information of the object instance comprises information of the object instance and second information of the object instance;
the determining unit, configured to determine the status of the th object instance according to the th object instance information, includes:
the determining unit is used for determining the th state of the th object instance according to the th information of the th object instance, determining the second state of the th object instance according to the second information of the th object instance, and taking the th state or the second state as the th object instance if the th state is the same as the second state.
13. The apparatus of claim 12, wherein the th state corresponds to a th fault level, and wherein the second state corresponds to a second fault level;
the th determination unit is further configured to:
if the th state is different from the second state and the th failure level is higher than the second failure level, then the th state is taken as the th object instance's state;
if the th state is different from the second state and the second failure level is higher than the th failure level, then the second state is taken as the state of the th object instance;
if the th state is different from the second state and the th failure level is equal to the second failure level, then the th state and/or the second state are taken as the state of the th object instance.
14. The apparatus of claim 9, wherein the data center model further comprises a third object instance, wherein the third object instance has the dependency relationship with the second object instance, and wherein a functional implementation of the third object instance is dependent on a functional implementation of the second object instance;
the device also comprises a third determining unit and a second storage unit, wherein the th storage unit is connected with the third determining unit, and the third determining unit is connected with the second storage unit;
the third determining unit is used for determining the logic state of the third object instance according to the state of the second object instance and the dependency relationship between the second object instance and the third object instance;
the second storage unit is used for storing the logic state of the third object instance.
15. The apparatus of claim 9, wherein the data center model further comprises a fourth object instance, wherein the fourth object instance has the dependency relationship with the second object instance, and wherein a functional implementation of the fourth object instance is dependent on a functional implementation of the second object instance;
the device also comprises a dependency relationship calculation unit, a fourth determination unit and a third storage unit, wherein the th storage unit is connected with the dependency relationship calculation unit, the dependency relationship calculation unit is connected with the fourth determination unit, and the fourth determination unit is connected with the third storage unit;
a dependency relationship calculation unit, configured to obtain a dependency relationship between the th object instance and the fourth object instance according to a dependency relationship between the th object instance and the second object instance and a dependency relationship between the fourth object instance and the second object instance;
the fourth determination unit is used for determining the logic state of the fourth object instance according to the state of the th object instance and the dependency relationship between the th object instance and the fourth object instance;
the third storage unit is configured to store a logic state of the fourth object instance.
CN201510546724.0A 2015-08-31 2015-08-31 data center model, information processing method and device Active CN106484381B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510546724.0A CN106484381B (en) 2015-08-31 2015-08-31 data center model, information processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510546724.0A CN106484381B (en) 2015-08-31 2015-08-31 data center model, information processing method and device

Publications (2)

Publication Number Publication Date
CN106484381A CN106484381A (en) 2017-03-08
CN106484381B true CN106484381B (en) 2020-01-31

Family

ID=58236212

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510546724.0A Active CN106484381B (en) 2015-08-31 2015-08-31 data center model, information processing method and device

Country Status (1)

Country Link
CN (1) CN106484381B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103414597A (en) * 2013-08-30 2013-11-27 上海寰创通信科技股份有限公司 Status updating system and status updating method of logical ports
CN104756443A (en) * 2012-08-24 2015-07-01 Vce有限责任公司 Managing converged information technology infrastructure with generic object instances

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080222603A1 (en) * 2006-10-12 2008-09-11 Hewlett-Packard Development Company L.P. Addressing managed elements in a common information model environment
KR101277274B1 (en) * 2009-11-27 2013-06-20 한국전자통신연구원 Method and Apparatus for Mapping a Physical Resource Model to a Logical Resource Model

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104756443A (en) * 2012-08-24 2015-07-01 Vce有限责任公司 Managing converged information technology infrastructure with generic object instances
CN103414597A (en) * 2013-08-30 2013-11-27 上海寰创通信科技股份有限公司 Status updating system and status updating method of logical ports

Also Published As

Publication number Publication date
CN106484381A (en) 2017-03-08

Similar Documents

Publication Publication Date Title
CN110036600B (en) Network health data convergence service
CN110036599B (en) Programming interface for network health information
US10454752B2 (en) System and method for processing alerts indicative of conditions of a computing infrastructure
US20190286510A1 (en) Automatic correlation of dynamic system events within computing devices
US10048996B1 (en) Predicting infrastructure failures in a data center for hosted service mitigation actions
US8819220B2 (en) Management method of computer system and management system
US9246777B2 (en) Computer program and monitoring apparatus
US10462027B2 (en) Cloud network stability
CN110955550B (en) Cloud platform fault positioning method, device, equipment and storage medium
CN102752142B (en) A kind of method for supervising of the information system based on Conceptual Modeling and supervisory control system
CN110784515A (en) Data storage method based on distributed cluster and related equipment thereof
CN114553672B (en) Method, device, equipment and medium for determining performance bottleneck of application system
CN112040506A (en) Reliability evaluation method and device of wireless sensor network and storage medium
CN112256498A (en) Fault processing method and device
CN113450033B (en) CMDB-based change influence analysis method and management equipment
GB2463343A (en) Fault diagnosis using device interdependencies and fault history for networked systems
CN109997337B (en) Visualization of network health information
CN107426012B (en) Fault recovery method and device based on super-fusion architecture
CN109510730A (en) Distributed system and its monitoring method, device, electronic equipment and storage medium
US20140115165A1 (en) Resource management system, resource management method, and computer product
CN106484381B (en) data center model, information processing method and device
US20230153725A1 (en) Techniques for determining service risks and causes
CN113238893A (en) Disaster recovery system, method, computer device and medium for multiple data centers
JP7269822B2 (en) Communication monitoring device and communication monitoring method
CN102822806B (en) Detect the state that gets nowhere of application

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20220211

Address after: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province

Patentee after: Huawei Cloud Computing Technology Co.,Ltd.

Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd.

TR01 Transfer of patent right