Device management method and communication apparatus

Abstract

A device management method and a communication apparatus, which relate to the technical field of communications. In the method, a first management device and a second management device exchange first request information and first response information. The first request information requests management of the second management device by the first management device, and / or management of the first management device by the second management device. The first response information is used for responding to the first request information. On the basis of the described procedure, the first management device and the second management device can establish a management relationship (which can be management of the second management device by the first management device, and / or management of the first management device by the second management device, etc.), thereby achieving better management of management devices. For example, after the management relationship is established between the management devices, information is directly exchanged between the management devices, so that a delay in information exchange between the management devices can be reduced, the information exchange procedure between the management devices can be shortened, and access pressure does not exclusively concentrate on upper layer management devices.

Description

A method and communication device for device management

[0001] This application claims priority to Chinese Patent Application No. 202410667867.6, filed on May 27, 2024, entitled "A Method and Communication Apparatus for Device Management", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and more specifically, to a method for device management and a communication apparatus. Background Technology

[0003] Management devices refer to hardware and software devices used to manage specified devices. For example, network management devices manage one or more network devices, IoT management devices manage one or more IoT devices, industrial management devices manage one or more industrial devices, and medical management devices manage one or more medical devices.

[0004] Currently, management of devices can be achieved through a hierarchical management approach. For example, an upper-level management device can manage one or more lower-level management devices, and a lower-level management device can manage one or more specified devices. However, this architecture has several drawbacks: all access pressure is concentrated on the upper-level management device, easily creating a system performance bottleneck; if the upper-level management device fails, the entire management system will be paralyzed, easily creating a system reliability bottleneck; and the information exchange process between lower-level management devices is lengthy and time-consuming. Therefore, how to achieve better management of devices is a pressing technical problem that needs to be solved.

[0005] Summary of the Invention

[0006] This application provides a method and communication device for device management, which can support better management of the managed devices.

[0007] In a first aspect, a method for device management is provided, comprising: sending a first request message to a second management device, the first request message requesting at least one of the following: the first management device manages the second management device, or the second management device manages the first management device; and receiving a first response message from the second management device, the first response message being used to respond to the first request message.

[0008] The technical solution described in the first aspect can be executed by a device on the first management device side. The device on the first management device side can be the first management device, or a module (such as a chip system) in the first management device, or a logic node, logic module, or software that can realize all or part of the functions of the first management device. For ease of description, the following description uses the first management device as an example.

[0009] Through the above process, the first management device and the second management device can exchange information regarding the establishment of a management relationship (which can be understood as: the first management device managing the second management device, and / or the second management device managing the first management device, etc.). This supports the establishment of a management relationship between the first and second management devices, thereby enabling better management of the devices. For example, based on the above scheme, once a management relationship is established between the management devices, they can directly exchange information. This reduces the latency and shortens the information exchange process between the management devices, and also prevents all access pressure from concentrating on the upper-level management device.

[0010] In the first aspect, the method further includes: receiving second request information from a second management device, the second request information requesting the second management device to manage the first management device, or the second request information requesting the first management device to manage the second management device; and sending second response information to the second management device, the second response information being used to respond to the second request information.

[0011] Thus, the embodiments of this application can support mutual information interaction between the first management device and the second management device, thereby enabling mutual management between the first management device and the second management device.

[0012] In the first aspect, the second request information requests the second management device to manage the first management device, and the sending of the second response information to the second management device includes: determining the second response information, the second response information indicating whether the second management device is allowed to manage the first management device; and sending the second response information to the second management device.

[0013] Thus, embodiments of this application can support the first management device in processing or responding to the second request information.

[0014] In the first aspect, the first management device manages the second management device, and the method further includes: sending a third request message to the second management device, the third request message requesting the execution of a first operation; and receiving a third response message from the second management device, the third response message indicating the execution result of the first operation.

[0015] Once the first management device and the second management device establish a management relationship, the first management device can instruct the second management device to perform certain operations, thereby enabling the management devices to collaborate in completing tasks.

[0016] In the first aspect, the second management device manages the first management device, and the method further includes: receiving a fourth request message from the second management device, the fourth message requesting the execution of a second operation; and sending a fourth response message to the second management device, the fourth response message indicating the execution result of the second operation.

[0017] Once the first management device and the second management device establish a management relationship, the first management device can perform certain operations according to the instructions of the second management device, thereby enabling the management devices to cooperate in completing tasks.

[0018] In the first aspect, sending a fourth response message to the second management device includes: determining a first device list, wherein the devices in the first device list are devices that manage the first management device, and the first device list includes the second management device; determining to perform a second operation based on the first device list; and determining the fourth response message.

[0019] Thus, the first management device can determine whether to perform the second operation based on whether the first device list includes the second management device. This allows the first management device to process only instructions from the management device that manages the first management device, which can reduce the power consumption of the first management device.

[0020] In the first aspect, the first management device manages the second management device, and the method further includes: sending a fifth request message to the second management device, the fifth request message requesting to obtain device information of the second management device; receiving a fifth response message from the second management device, the fifth response message indicating the device information of the second management device; and managing the second management device according to the device information of the second management device.

[0021] Thus, embodiments of this application can support the first management device to manage the second management device by obtaining the device information of the second management device.

[0022] In the first aspect, the first management device manages the second management device, and the method further includes: receiving first information from the second management device; and determining abnormal status information of the second management device based on the first information.

[0023] In the first aspect, before receiving the first information from the second management device, the method further includes: sending second information to the second management device, the second information configuring conditions for the second management device to report the first information to the first management device; and receiving third information from the second management device, the third information being used in response to the second information.

[0024] Thus, the first management device can be configured to have the second management device report the first information to the first management device. The second management device can determine whether to report the first information to the first management device based on whether the condition is met. This can support the first management device to determine the abnormal status information of the second management device based on the first information, and thus also support the management of the second management device.

[0025] In the first aspect, the method further includes: receiving a sixth request message from a third management device, the sixth request message requesting the third management device to manage the first management device; and sending a sixth response message to the third management device, the sixth response message being used to respond to the sixth request message.

[0026] In the first aspect, sending a sixth response message to the third management device includes: determining the sixth response message, which indicates whether the third management device is allowed to manage the first management device; and sending the sixth response message to the third management device.

[0027] In the first aspect, the sixth response information indicates permission for the third management device to manage the first management device, and the method further includes: receiving a seventh request information from the third management device, the seventh request information requesting the execution of a third operation; and sending a seventh response information to the third management device, the seventh response information indicating the execution result of the third operation.

[0028] In the first aspect, sending the seventh response information to the third management device includes: determining a second device list, wherein the devices in the second device list are devices that manage the first management device, and the second device list includes the third management device; determining to perform a third operation based on the second device list; and sending the seventh response information to the third management device.

[0029] In the first aspect, the method further includes: determining a second operation based on a third operation; sending a third request message to a second management device, the third request message requesting the execution of the second operation. Wherein, the first management device manages the second management device.

[0030] Thus, the embodiments of this application can support multiple management devices to collaborate in completing tasks.

[0031] In the first aspect, before sending the first request information to the second management device, the method further includes: receiving fourth information, the fourth information instructing the first management device to send the first information; sending the first request information to the second management device, including: sending the first information according to the fourth information.

[0032] In the first aspect, the equipment managed by the first management device is different from the equipment managed by the second management device.

[0033] In this way, management relationships can be established between management devices that do not have the same management capabilities.

[0034] In a second aspect, a method for device management is provided, comprising: receiving a first request message from a first management device, the first request message requesting at least one of the following: the first management device manages a second management device, or the second management device manages the first management device; and sending a first response message to the first management device, the first response message being used to respond to the first request message.

[0035] The solution described in the second aspect can be executed by a device on the second management device side. This device can be the second management device itself, a module within the second management device (such as a chip system), or a logic node, logic module, or software capable of implementing all or part of the functions of the second management device. For ease of description, the following description uses the second management device as an example.

[0036] Through the above process, the first management device and the second management device can exchange information regarding the establishment of a management relationship (which can be understood as the first management device managing the second management device, and / or the second management device managing the first management device, etc.). This supports the establishment of a management relationship between the first and second management devices, thereby enabling better management of the devices. For example, based on the above scheme, once a management relationship is established between the management devices, they can directly exchange information. This reduces the latency and shortens the information exchange process between the management devices, and also prevents all access pressure from being concentrated on the upper-level management device.

[0037] In a second aspect, the method further includes: sending a second request message to a first management device, the second request message requesting the second management device to manage the first management device, or the second request message requesting the first management device to manage the second management device; and receiving a second response message from the first management device, the second response message being used to respond to the second request message.

[0038] In the second aspect, the first request information requests the first management device to manage the second management device, and sends the first response information to the first management device, including: determining the first response information, the first response information indicating whether the first management device is allowed to manage the second management device; and sending the first response information to the first management device.

[0039] In the second aspect, the first management device manages the second management device, and the method further includes: receiving a third request message from the first management device, the third request message requesting the execution of a first operation; and sending a third response message to the first management device, the third response message indicating the execution result of the first operation.

[0040] In the second aspect, the third response information to the first management device includes: determining a third device list, wherein the devices in the third device list are devices that manage the second management device, and the third device list includes the first management device; determining to perform a first operation based on the third device list; and determining the third response information.

[0041] In this way, the second management device can determine whether to perform the first operation based on whether the third device list includes the first management device. This allows the second management device to process only instructions from the management device that manages the second management device, which can reduce the power consumption of the second management device.

[0042] In the second aspect, the second management device manages the first management device, and the method further includes: sending a fourth request message to the first management device, the fourth request message requesting the execution of a second operation; and receiving a fourth response message from the first management device, the fourth response message indicating the execution result of the second operation.

[0043] In the second aspect, the first management device manages the second management device, and the method further includes: receiving a fifth request message from the first management device, the fifth request message requesting to obtain device information of the second management device; sending a fifth response message to the first management device, the fifth response message indicating the device information of the second management device, the device information of the second management device being used by the first management device to manage the second management device.

[0044] In the second aspect, the first management device manages the second management device, and the method further includes: sending first information to the first management device, the first information being used by the first management device to determine abnormal status information of the second management device.

[0045] In the second aspect, before sending the first information to the first management device, the method further includes: receiving second information from the first management device, the second information configuring conditions for the second management device to report the first information to the first management device; and sending third information to the first management device, the third information being used in response to the second information.

[0046] In the second aspect, the equipment managed by the first management device is different from the equipment managed by the second management device.

[0047] In this way, it is possible to establish management relationships between devices that do not have the same management capabilities.

[0048] Thirdly, a communication device is provided, which may be a first management device, or a device or module for performing the functions of the first management device.

[0049] One possible implementation is that the communication device may include modules or units corresponding to the methods / operations / steps / actions described in the first aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.

[0050] Fourthly, a communication device is provided, which may be a second management device, or a device or module for performing the functions of the second management device.

[0051] One possible implementation is that the communication device may include modules or units corresponding to the methods / operations / steps / actions described in the second aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.

[0052] Fifthly, a communication device is provided, including a processor configured to, by executing a computer program or instructions, or by logic circuitry, cause the communication device to perform the method described in the first aspect and any possible manner of the first aspect; or to cause the communication device to perform the method described in the second aspect and any possible manner of the second aspect.

[0053] In one possible implementation, the communication device also includes a memory for storing the computer program or instructions.

[0054] In one possible implementation, the communication device also includes a communication interface for inputting and / or outputting signals.

[0055] A sixth aspect provides a communication device including logic circuitry and an input / output interface for inputting and / or outputting signals, the logic circuitry being configured to perform the method described in the first aspect and any possible mode of the first aspect; or, the logic circuitry being configured to perform the method described in the second aspect and any possible mode of the second aspect.

[0056] In a seventh aspect, a computer-readable storage medium is provided, on which a computer program or instructions are stored, which, when executed on a computer, cause the method described in the first aspect and any possible manner of the first aspect to be performed; or cause the method described in the second aspect and any possible manner of the second aspect to be performed.

[0057] Eighthly, a computer program product is provided, comprising instructions that, when executed on a computer, cause the method described in the first aspect and any possible mode of the first aspect to be performed; or cause the method described in the second aspect and any possible mode of the second aspect to be performed.

[0058] A ninth aspect provides a chip or chip system comprising: one or more processors configured to execute computer programs or instructions in the memory, such that the chip or chip system implements the methods of the first aspect and any possible implementation thereof; or, such that the chip or chip system implements the methods of the second aspect and any possible implementation thereof.

[0059] For a description of the beneficial effects of any of the third to ninth aspects, please refer to the description of the beneficial effects of the first to second aspects, which will not be repeated here. Attached Figure Description

[0060] Figure 1 is a schematic diagram of application scenario 100 of an embodiment of this application.

[0061] Figure 2 is a schematic diagram of the architecture of the applicable system 200 according to an embodiment of this application.

[0062] Figure 3 is a schematic diagram of the interactive flow of the device management method 300 according to an embodiment of this application.

[0063] Figure 4 is a schematic diagram of the interaction flow of the device management method 400 according to an embodiment of this application.

[0064] Figure 5 is a schematic diagram of the interaction flow of the device management method 500 according to an embodiment of this application.

[0065] Figure 6 is a schematic diagram of the interactive flow of the device management method 600 according to an embodiment of this application.

[0066] Figure 7 is a schematic diagram of the interaction flow of the device management method 700 according to an embodiment of this application.

[0067] Figure 8 is a schematic diagram of the interaction flow of the device management method 800 according to an embodiment of this application.

[0068] Figure 9 is a schematic diagram of the interactive flow of the device management method 900 according to an embodiment of this application.

[0069] Figure 10 is a schematic block diagram of a communication device 1000 according to an embodiment of this application.

[0070] Figure 11 is a schematic block diagram of a communication device 1100 according to an embodiment of this application. Detailed Implementation

[0071] To facilitate understanding of the embodiments of this application, the following points will be explained first.

[0072] 1. Unless otherwise stated, “multiple” means two or more.

[0073] 2. Unless otherwise specified or in case of logical conflict, the terms and / or descriptions in different embodiments of this application are consistent and can be referenced in each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0074] III. The various numerical designations used in this application are merely for descriptive convenience and are not intended to limit the scope of protection of this application. The magnitude of the serial numbers used in this application does not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic. For example, the terms "first," "second," "third," "fourth," and other various terminology (if present) in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. Such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein.

[0075] Furthermore, any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0076] IV. The terms “comprising” and “having” and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are expressly listed, but may include other steps or units that are not expressly listed or that are inherent to such process, method, product or device.

[0077] V. In this application, "for indicating" can be understood as "enabling", and "enabling" includes direct enabling and indirect enabling. When describing information for enabling A, it may include whether the information directly enables A or indirectly enables A, but it does not mean that the information necessarily carries A.

[0078] The information that enables the information is called the information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled, such as, but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or its index. It can also be indirectly enabled by enabling other information, where there is a relationship between the other information and the information to be enabled. It can also enable only a part of the information to be enabled, while the other parts are known or pre-agreed upon. For example, enabling specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing enabling overhead to some extent. Simultaneously, common parts of various pieces of information can be identified and enabled uniformly to reduce the enabling overhead caused by individually enabling the same information.

[0079] In addition, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.

[0080] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0081] VI. In this application, "pre-configuration" may include pre-defined features, such as protocol definitions. These "pre-defined features" can be implemented by pre-storing corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including various network elements). This application does not limit the specific implementation method.

[0082] VII. The term "storage" or "preservation" in this application can refer to storage in one or more memory devices. These memory devices can be separately configured or integrated into an encoder, decoder, processor, or communication device. Alternatively, some memory devices can be separately configured, while others can be integrated into a decoder, processor, or communication device. The type of memory can be any form of storage medium, and this is not limited.

[0083] 8. The term "protocol" in this application may refer to standard protocols in the field of communications, for example, it may include fourth-generation (4G) protocols. th Generation 4G network, fifth generation (5G) network th This application does not limit the scope to 5G network protocols, 5.5G network protocols, or related protocols applied in future communication networks.

[0084] 9. The arrows or boxes indicated by dashed lines in the schematic diagrams in the accompanying drawings of this application represent optional steps or optional modules.

[0085] 10. Unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. In this application, "and / or" is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0086] XI. In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of a chip interface, and "receive" can also be understood as the "input" of a chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0087] Figure 1 is a schematic diagram of application scenario 100 according to an embodiment of this application. As shown in Figure 1, in application scenario 100, there are multiple management devices, such as management device 1 and management device 2. The devices managed by each management device (which can also be understood as the management scope of the management device) can be different. For example, management device 1 manages devices 11 and 12 (or, the management scope of management device 1 includes devices 11 and 12), and management device 2 manages devices 21 and 22 (or, the management scope of management device 2 includes devices 21 and 22). Among them, device 11 is different from any one of devices 21 and 22, and device 12 is different from any one of devices 21 and 22.

[0088] The types of management device 1 and management device 2 can be the same or different. For example, both management device 1 and management device 2 can be network management devices. Another example is that management device 1 is a network management device, and management device 2 is an Internet of Things (IoT) management device.

[0089] Currently, a hierarchical management approach is used to manage both management device 1 and management device 2. For example, device A is set up, and device A manages both management device 1 and management device 2. In this way, management device 1, management device 2, and device A constitute a management system. Device A is the upper-level management device in this management system, while management device 1 and management device 2 are the lower-level management devices. Devices 11 and 12 are designated devices managed by management device 1, and devices 21 and 22 are designated devices managed by management device 2.

[0090] As shown in the background section, the aforementioned management system has some drawbacks, such as system performance bottlenecks and system reliability bottlenecks. Therefore, this application provides a device management method and communication apparatus, which can support better management of the managed devices. See Figure 2.

[0091] Figure 2 is a schematic diagram of the architecture of the applicable system 200 according to an embodiment of this application. As shown in Figure 2, in the applicable system 200, when there are multiple management devices, such as management device 1, management device 2, management device 3 and management device 4, management devices 1 to management device 4 can interact with each other to establish management relationships between the management devices.

[0092] For example, management device 1 and management device 2 interact with each other to establish a management relationship between them; management device 1 and management device 3 interact with each other to establish a management relationship between them; management device 1 and management device 4 interact with each other to establish a management relationship between them; management device 2 and management device 3 interact with each other to establish a management relationship between them; management device 2 and management device 4 interact with each other to establish a management relationship between them; and management device 3 and management device 4 interact with each other to establish a management relationship between them.

[0093] A description of the management relationship can be found in Table 1. The content in Table 1 is for illustrative purposes only and is not intended as a final limitation.

[0094] Table 1

[0095] As shown in Table 1, the upper part of the arrow represents the managing device (which can also be understood as the management node) that manages other managed devices, and the lower part of the arrow represents the managed device (which can also be understood as the managed node):

[0096] Manage equipment 1; manage equipment 2;

[0097] Managing Equipment 1; Managing Equipment 3;

[0098] Management equipment 1 manages management equipment 4;

[0099] Management Equipment 2 manages Management Equipment 1;

[0100] Management equipment 2; Management equipment 3;

[0101] Management equipment 2; Management equipment 4;

[0102] Management equipment 3 manages management equipment 1;

[0103] Management equipment 3 manages management equipment 2;

[0104] Management equipment 3; Management equipment 4;

[0105] Management equipment 4; Management equipment 1;

[0106] Management equipment 4 manages management equipment 2;

[0107] Management equipment 4. Management equipment 3.

[0108] The above example illustrates a single management device managing another single management device, but it is not limited to scenarios where one management device manages multiple management devices, such as management device 1 managing management device 2 and management device 3. Furthermore, it does not limit the scenarios where a managed device can also manage other management devices, such as management device 1 managing management device 2 and management device 4, or management device 2 managing management device 3. Additionally, it does not limit scenarios where management devices manage each other, such as management device 1 managing management device 2, or management device 2 managing management device 1.

[0109] In this embodiment, the management relationship (which can also be replaced by other terms, such as association relationship) can be understood as the relationship between a management device that manages other management devices and the managed device. For example, if management device 1 manages management device 2, a management relationship is established between management device 1 and management device 2. That is, in this management relationship, there exists a management device (such as management device 1) that manages other management devices and a managed device (such as management device 2) that is being managed. In order to support the establishment of management relationships between management devices, the management devices can exchange information about how to establish management relationships, as shown in Figure 3.

[0110] For ease of understanding and explanation, the following description of the device management method of this application embodiment uses the interaction between a first management device (e.g., management device 1) and a second management device (e.g., management device 2) as an example. However, this should not limit the subject executing the device management method. For example, the method executed by the management device can also be executed by a module (e.g., a circuit, chip, or chip system) in the management device, or by a logic node, logic module, or software that can implement all or part of the functions of the management device, without limitation.

[0111] Figure 3 is a schematic diagram of the interaction flow of a device management method 300 according to an embodiment of this application. As shown in Figure 3, method 300 includes:

[0112] S301, the first management device sends a first request message to the second management device. Correspondingly, the second management device receives the first request message.

[0113] The first request information requests at least one of the following:

[0114] The first management device manages the second management device, or the second management device manages the first management device.

[0115] For example, a first request message requests a first management device to manage a second management device. The first management device can be a management device that manages the second management device (or, the first management device can be a management node of the second management device, hereinafter referred to as a management node). The second management device can be a management device managed by the first management device (or, the second management device can be a managed node of the first management device, hereinafter referred to as a managed node). In this way, it is possible to support the management of the second management device by the first management device.

[0116] For example, a first request message may request a second management device to manage a first management device. The second management device can be a management node of the first management device, and the first management device can be a managed node of the second management device. In this way, the second management device can manage the first management device.

[0117] For example, a first request might request a first management device to manage a second management device, and vice versa. The first management device can be a management node for the second management device, and the second management device can be a managed node for the first management device. Conversely, the first management device can also be a managed node for the second management device, and vice versa. This allows for mutual management between the first and second management devices.

[0118] Optionally, the first request information can also be used to request the establishment of a first management relationship between the first management device and the second management device. For example, the first request information requests the establishment of a first management relationship between the first management device and the second management device, and the first management relationship can instruct the first management device to manage the second management device, and / or the second management device to manage the first management device.

[0119] Optionally, the first management relationship may indicate at least one of a first role and a second role, where the first role is the role of the first management device as a management node and the second role is the role of the first management device as a managed node.

[0120] When the first management relationship indicates a first role, the second management device can determine that the first management device requests management of the second management device. When the first management relationship indicates a second role, the second management device can determine that the first management device requests management of the first management device. When the first management relationship indicates both a first role and a second role, the second management device can determine that the first management device requests management of the second management device, and vice versa. In summary, the second management device can determine the content requested by the first management device based on the role indicated by the first management relationship.

[0121] One possible implementation is that the first request information may include the identification information and management permission information of the first management device. For example, the first request information may be used to request the first management device to manage the second management device, and the first request information may carry information indicating the permissions of the first management device when managing the second management device; or the first request information may be used to request the second management device to manage the first management device, and the first request information may carry information indicating the permissions of the second management device when managing the first management device.

[0122] The aforementioned management permissions can be understood as follows: the first management device instructs the second management device to report the device information of the second management device (such as the resource information and operating status information of the second management device); or, the first management device instructs the second management device to report some information to the first management device when the agreed or configured conditions are met (such as alarm information obtained or monitored by the second management device); or, the first management device instructs the second management device to perform a specified operation (such as performing link fault analysis).

[0123] Furthermore, once a management relationship is successfully established between the first management device and the second management device, the aforementioned management permissions can be changed or reconfigured without limitation.

[0124] One possible implementation is that the first request information may also include at least one of the following: the device type of the first management device, the identifier of the manufacturer to which the first management device belongs, and authentication information (such as certificate authentication or user password). In this way, the second management device can authenticate the first management device based on the above information, and then determine whether to allow the first management device to manage the second management device or whether to manage the first management device, etc.

[0125] For example, the first request information includes the device type of the first management device, such as the first management device being a network management device, the second management device being an IoT management device, the second management device determining that it does not allow the first management device to manage the second management device, or the second management device determining that it does not manage the first management device, etc.

[0126] For example, the first request information includes the identifier of the manufacturer to which the first management device belongs. For instance, the identifier of the manufacturer to which the first management device belongs indicates that the first management device belongs to the first manufacturer, the second management device belongs to the second manufacturer, the second management device determines that the first management device is not allowed to manage the second management device, or the second management device determines that it will not manage the first management device, etc.

[0127] For example, the first request information includes authentication information, and the second management device authenticates the first management device based on the aforementioned information. After the first management device passes the authentication process, the second management device determines whether to allow the first management device to manage the second management device, or determines to manage the first management device, etc.

[0128] S302, the second management device sends a first response message to the first management device. Correspondingly, the first management device receives the first response message.

[0129] The first response information is used to respond to the first request information. For example, the first response information indicates the processing result of the second management device on the first request information, or the first response information indicates the response result of the second management device on the first request information.

[0130] For example, the first request information requests the first management device to manage the second management device, and the first response information indicates whether the second management device allows the first management device to manage the second management device. For instance, the first response information indicates that the second management device allows the first management device to manage the second management device, or the first response information indicates that the second management device does not allow the first management device to manage the second management device.

[0131] For example, the first request information requests the second management device to manage the first management device, and the first response information indicates whether the second management device should manage the first management device. For instance, the first response information indicates that the second management device should manage the first management device, or the first response information indicates that the second management device should not manage the first management device.

[0132] For example, the first request information requests the first management device to manage the second management device and the second management device to manage the first management device, and the first response information indicates whether the second management device allows the first management device to manage the second management device and whether the second management device manages the first management device. For example, the first response information indicates that the second management device allows the first management device to manage the second management device and that the second management device manages the first management device; another example is that the first response information indicates that the second management device allows the first management device to manage the second management device and that the second management device does not manage the first management device; yet another example is that the first response information indicates that the second management device does not allow the first management device to manage the second management device and that the second management device manages the first management device; and yet another example is that the first response information indicates that the second management device does not allow the first management device to manage the second management device and does not manage the first management device.

[0133] When a first request message requests the first management device to manage the second management device, the second management device can determine whether to allow the first management device to manage the second management device through various methods. For example:

[0134] Method 1:

[0135] After going online, the first and second management devices trigger a self-discovery operation. They can discover each other's existence and exchange their identification information, such as manufacturer information, device owner identification information, and supported management protocols, according to the self-discovery protocol. When the second management device receives a first request from the first management device, it determines whether the first management device can manage it based on the aforementioned information.

[0136] Method 2:

[0137] Both the first and second management devices have the same parameters (such as management relationship identifier, management relationship index, or other content). These parameters are used by the second management device to determine whether the first management device is allowed to manage the second management device. These parameters are written by the device owner or manufacturer, etc.

[0138] For example, the first request information includes parameters stored by the first management device. When the second management device receives the first request information, it determines whether the first management device can manage the second management device based on these parameters. For instance, if the parameter identifier in the first request information is the same as the parameter stored by the second management device, the second management device determines that it allows the first management device to manage the second management device; if the parameter in the first request information is different from the parameter stored by the second management device, the second management device determines that it does not allow the first management device to manage the second management device.

[0139] Method 3:

[0140] The first request information includes parameters stored by the first management device (which may be the parameters mentioned above). When the second management device receives the first request information, the administrator manually determines whether the first management device can manage the second management device. For example, if the administrator determines that the parameters in the first request information are the same as the parameters stored by the second management device, the administrator can determine that the first management device is allowed to manage the second management device; if the administrator determines that the parameters in the first request information are different from the parameters stored by the second management device, the administrator can determine that the first management device is not allowed to manage the second management device.

[0141] Through the above process, management devices can exchange information regarding the establishment of management relationships (which can be understood as the first management device managing the second management device, and / or the second management device managing the first management device, etc.). This supports the establishment of management relationships between the first and second management devices, thereby enabling better management of the devices. For example, based on the above scheme, once a management relationship is established between management devices, they can directly exchange information. This reduces the latency and shortens the information exchange process between management devices, and also prevents all access pressure from concentrating on the upper-level management device, etc.

[0142] Optionally, method 300 may also include:

[0143] S303, the second management device sends a second request message to the first management device. Correspondingly, the first management device receives the second request message.

[0144] The second request information requests the second management device to manage the first management device, or the second request information requests the first management device to manage the second management device. The content requested by the second request information is relative to the content requested by the first request information.

[0145] For example, a first request message may request a first management device to manage a second management device, while a second request message may request the second management device to manage the first management device. Thus, the second management device can also request to manage the first management device, which supports mutual management between the first and second management devices.

[0146] For example, if the first request information requests the second management device to manage the first management device, the second request information can request the first management device to manage the second management device. In this way, the second management device can also request the first management device to manage the second management device, which can support mutual management between the first and second management devices.

[0147] When the first request information requests the first management device to manage the second management device and the second management device to manage the first management device, the second management device may also send a second request information to the first management device, and there is no limitation on this.

[0148] For the content carried by the second request information, please refer to the aforementioned description of the content carried by the first request information, which will not be repeated here.

[0149] S304. The first management device sends a second response message to the second management device. Correspondingly, the second management device receives the second response message.

[0150] The second response information is used to respond to the second request information. For example, the second response information indicates the processing result of the first management device on the second request information, or the second response information indicates the response result of the first management device on the second request information.

[0151] For example, the second request information requests the second management device to manage the first management device, and the second response information indicates whether the first management device allows the second management device to manage the first management device. For instance, the second response information may indicate that the first management device allows the second management device to manage the first management device, or the second response information may indicate that the first management device does not allow the second management device to manage the first management device, etc.

[0152] For example, the second request information requests the first management device to manage the second management device, and the second response information indicates whether the first management device should manage the second management device. For instance, the second response information may indicate that the first management device manages the second management device, or it may indicate that the first management device does not manage the second management device.

[0153] For example, the second request information requests the first management device to manage the second management device and the second management device to manage the first management device, and the second response information indicates whether the second management device allows the first management device to manage the second management device and whether the second management device manages the first management device. For instance, the second response information may indicate that the first management device manages the second management device and allows the second management device to manage the first management device; or, the second response information may indicate that the first management device manages the second management device and does not allow the second management device to not manage the first management device; or, the second response information may indicate that the first management device does not manage the second management device and allows the second management device to manage the first management device; or, the second response information may indicate that the first management device does not manage the second management device and does not allow the second management device to manage the first management device.

[0154] Optionally, when the second request information requests the second management device to manage the first management device, S304 may include:

[0155] S304a, The first management device determines the second response information, and the second response information indicates whether the second management device is allowed to manage the first management device;

[0156] S304b: The first management device sends a second response message to the second management device. Correspondingly, the second management device receives the second response message.

[0157] For a description of how the first management device determines the second response information, please refer to the aforementioned description of how the second management device determines the first response information, which will not be repeated here.

[0158] Thus, embodiments of this application can support the first management device in processing or responding to the second request information.

[0159] Through S303 and S304, after the first management device sends a first request message to the second management device, the second management device can also send a second request message to the first management device. This can support mutual information interaction between the first management device and the second management device, or it can support mutual management between the first management device and the second management device.

[0160] One possible implementation is that the devices managed by the first management device are different from the devices managed by the second management device.

[0161] For example, the first management device is management device 1, and the second management device is management device 2. The devices managed by management device 1 are different from the devices managed by management device 2. In this way, it is possible to support the establishment of management relationships between management devices that do not have the same management capabilities.

[0162] Once a management relationship is established between the first management device and the second management device, if the first management device manages the second management device, the first management device can manage the second management device; that is, the first management device acts as the management node of the second management device, and the second management device acts as the managed node of the first management device. Conversely, if the second management device manages the first management device, the second management device can manage the first management device; that is, the second management device acts as the management node of the first management device, and the first management device acts as the managed node of the second management device. In other words, once a management relationship is established between a management node and a managed node, the management node can manage the managed node.

[0163] The following description, in conjunction with the accompanying diagrams, illustrates how a management node manages a managed node. For ease of description, the following descriptions will separately illustrate the management of a second management device by a first management device and the management of a first management device by a second management device.

[0164] Figure 4 is a schematic diagram of the interaction flow of the device management method 400 according to an embodiment of this application. As shown in Figure 4, a first management device manages a second management device, with the first management device acting as a management node and the second management device acting as a managed node. Method 400 includes:

[0165] S401, the first management device sends a third request message to the second management device. Correspondingly, the second management device receives the third request message.

[0166] The third request information requests the second management device to perform the first operation. For example, the first management device manages devices 11 and 12, and the second management device manages devices 21 and 22. Devices 11 and 12 are connected (this connection can be physical, such as through a physical port, or logical, i.e., not through a physical port). Devices 12 and 21 are connected (this connection can be physical or logical). Devices 21 and 22 are connected (this connection can be physical or logical). Therefore, devices 11 and 22 are connected (this connection can be physical or logical). The first operation is to analyze the link failure between devices 11 and 22 on devices 21 and 22.

[0167] One possible implementation is that the first operation is determined based on the administrator's instructions.

[0168] For example, an administrator sends instruction information 1 to a first management device, instructing the first management device to perform operation 1. The first management device decomposes operation 1 to obtain at least one operation, which includes the first operation. The first management device instructs a second management device to perform the first operation. The first management device performs some or all of the operations other than the first operation in the at least one operation. For example, operation 1 is to analyze the link failure between device 11 and device 22, the first operation is to analyze the link failure between device 11 and device 22 on devices 21 and 22, and the operation other than the first operation in the at least one operation is to analyze the link failure between device 11 and device 22 on devices 11 and 12.

[0169] The first management device can analyze the link faults from device 11 to device 22 on device 11 and device 12 on its own, or it can instruct device 11 to analyze the link faults from device 11 to device 22 on device 11 and instruct device 12 to analyze the link faults from device 11 to device 22 on device 12, without limitation.

[0170] Another possible implementation is that the first operation is determined based on the instructions of the third management device that manages the first management device.

[0171] For example, a third management device sends instruction information 2 to a first management device, instructing the first management device to perform operation 2. The first management device decomposes operation 2 to obtain at least one operation, which includes the first operation. The first management device instructs a second management device to perform the first operation. The first management device performs some or all of the operations other than the first operation in the at least one operation. For example, operation 1 is to analyze the link failure between device 11 and device 22, the first operation is to analyze the link failure between device 11 and device 22 on device 21 and device 22, and the operation other than the first operation in the at least one operation is to analyze the link failure between device 11 and device 22 on device 11 and device 12.

[0172] The first management device can analyze the link fault from device 11 to device 22 on device 11 and device 12 on its own, or it can analyze the link fault from device 11 to device 22 on device 11 through device 11 or analyze the link fault from device 11 to device 22 on device 12 through device 12. There is no limitation on this.

[0173] S402, the second management device sends a third response message to the first management device. Correspondingly, the first management device receives the third response message.

[0174] The third response information indicates the result of the execution of the first operation. For example, the third response information indicates that the second management device has successfully executed the first operation, or the third response information indicates that the second management device has not successfully executed the first operation.

[0175] Using the above method, once a management relationship is established between the first management device and the second management device, the first management device can instruct the second management device to perform certain operations, thereby enabling the management devices to collaborate in completing tasks.

[0176] Optionally, S402 includes:

[0177] S402a, The second management device determines the list of third devices.

[0178] The devices in the third device list are those that manage the second management device, and the third device list includes the first management device.

[0179] S402b, The second management device determines the first operation to be performed based on the third device list.

[0180] For example, if the second management device determines that the third device list includes the first management device, and the second management device determines that the first management device is the management device that manages the second management device, then the second management device performs the first operation. If the second management device determines that the third device list does not include the first management device, and the second management device determines that the first management device is not the management device that manages the second management device, then the second management device does not perform the first operation. A description of the third device list can be found in Table 2.

[0181] Table 2

[0182] As shown in Table 2:

[0183] The identifier for management device 1 is identifier 1;

[0184] The identifier for management device 2 is identifier 2;

[0185] The identifier for management device 3 is identifier 3.

[0186] Thus, when the second management device determines that the third request information comes from the first management device (e.g., the third request information includes the identification information of the first management device), the second management device can determine whether to perform the first operation based on the third device list. Alternatively, the second management device can determine whether to perform the first operation based on whether the third device list includes the first management device. This allows the second management device to process only instructions from the management device that manages it, thereby reducing the power consumption of the second management device.

[0187] One possible implementation is that the third device list also includes information on the administrative permissions for each managed device. See Table 3 for a further description of the third device list.

[0188] Table 3

[0189] As shown in Table 3:

[0190] The identifier for managed device 1 is identifier 1, and the management permission is permission 1;

[0191] The identifier for managed device 2 is identifier 2, and the management permission is permission 2;

[0192] The identifier for managed device 3 is identifier 3, and the management permission is permission 3.

[0193] In this way, the second management device can determine whether to execute the first operation based on the permissions of the first management device. When the second management device determines that the first management device has the permission to instruct the second management device to execute the first operation, the second management device executes the first operation, which can reduce the power consumption of the second management device.

[0194] When the second management device determines that the third device list includes the first management device, and determines that the first management device in the third device list has management permissions that allow the second management device to perform the first operation, the second management device performs the first operation. If the second management device determines that the first management device in the third device list does not have management permissions that allow the second management device to perform the first operation, the second management device does not perform the first operation.

[0195] When the second management device processes the first operation, the second management device can complete the processing of the first operation on its own, or it can complete the processing of the first operation through the equipment managed by the second management device, without limitation.

[0196] S402c, the second management device determines the third response information.

[0197] Based on S402a-S402c, embodiments of this application can support the second management device to complete the processing or response to the third request information.

[0198] The method shown in Figure 4 enables the management devices to collaborate in completing tasks.

[0199] Figure 5 is a schematic diagram of the interaction flow of a device management method 500 according to an embodiment of this application. As shown in Figure 5, a second management device manages a first management device, with the first management device acting as a managed node and the second management device acting as a management node. Method 500 includes:

[0200] S501, the second management device sends a fourth request message to the first management device. Correspondingly, the first management device receives the fourth request message.

[0201] The fourth request information requests the first management device to perform the second operation. For example, the first management device manages devices 11 and 22, and the second management device manages devices 21 and 22. Devices 11 and 12 are connected, devices 12 and 21 are connected, and devices 21 and 22 are connected. Therefore, devices 11 and 22 are connected. The first operation is to analyze link failures, etc., between devices 11 and 22 on devices 21 and 22.

[0202] One possible implementation is that the second operation is determined based on the administrator's instructions.

[0203] For example, the administrator sends instruction message 3 to the second management device, which instructs the second management device to perform operation 3. The second management device decomposes operation 3 to obtain at least one operation, which includes the second operation. The second management device instructs the first management device to perform the second operation. The second management device performs some or all of the operations other than the second operation in the at least one operation. For example, operation 3 is to analyze the link failure between device 11 and device 22, the second operation is to analyze the link failure between device 11 and device 22 on devices 11 and 12, and the operation other than the second operation in the at least one operation is to analyze the link failure between device 11 and device 22 on devices 21 and 22.

[0204] The second management device can independently analyze the link faults between device 11 and device 22 on devices 21 and 22, and can also instruct device 21 to analyze the link faults between device 11 and device 22, and instruct device 22 to analyze the link faults between device 11 and device 22, without limitation.

[0205] Another possible implementation is that the second operation is determined based on the instructions of the fourth management device that manages the second management device.

[0206] For example, the fourth management device sends instruction information 4 to the second management device, instructing the second management device to perform operation 4. The second management device decomposes operation 4 to obtain at least one operation, which includes the second operation. The second management device instructs the first management device to perform the second operation, and the second management device performs some or all of the operations other than the second operation in the at least one operation. For example, operation 4 is to analyze the link failure between device 11 and device 22, the second operation is to analyze the link failure between device 11 and device 22 on devices 11 and 12, and the operation other than the second operation in the at least one operation is to analyze the link failure between device 11 and device 22 on devices 21 and 22.

[0207] The second management device can independently analyze the link faults between device 11 and device 22 on devices 21 and 22, and can also instruct device 21 to analyze the link faults between device 11 and device 22, and instruct device 22 to analyze the link faults between device 11 and device 22, without limitation.

[0208] S502, the first management device sends a fourth response message to the second management device. Correspondingly, the second management device receives the fourth response message.

[0209] The fourth response information indicates the result of the second operation. For example, the fourth response information indicates that the first management device has successfully executed the second operation, or the fourth response information indicates that the first management device has not successfully executed the second operation.

[0210] Using the above method, once a management relationship is established between the first management device and the second management device, the second management device can instruct the first management device to perform certain operations, thereby enabling the management devices to collaborate in completing tasks.

[0211] Optionally, S502 includes:

[0212] S502a, The first management device determines the first device list.

[0213] The devices in the first device list are those that manage the first management device, and the first device list includes the second management device.

[0214] S502b, The first management device determines the second operation to be performed based on the first device list.

[0215] For example, if the first management device determines that the first device list includes the second management device, and determines that the second management device is the management device that manages the first management device, then the first management device performs the second operation. If the first management device determines that the first device list does not include the second management device, and determines that the second management device is not the management device that manages the first management device, then the first management device does not perform the second operation. Alternatively, the first management device can determine whether to perform the second operation based on whether the first device list includes the second management device. This allows the first management device to process only instructions from the management device that manages the first management device, which can reduce the power consumption of the first management device.

[0216] One possible implementation is that the first device list also includes information on the management permissions for each managed device.

[0217] When the first management device determines that the first device list includes the second management device, and determines that the management permissions of the second management device in the first device list allow the first management device to perform the second operation, the first management device performs the second operation. If the first management device determines that the management permissions of the second management device in the first device list do not allow the first management device to perform the first operation, the first management device does not perform the second operation. Thus, when the first management device determines that the second management device has the permission to instruct the first management device to perform the second operation, the first management device performs the second operation, which can reduce the power consumption of the first management device.

[0218] When the first management device processes the second operation, the first management device can complete the processing of the second operation on its own, or it can complete the processing of the second operation through the equipment managed by the first management device, without limitation.

[0219] S502c, the first management device determines the fourth response information.

[0220] Based on the above S502a-S502c, the embodiments of this application can support the second management device to complete the processing or response to the third request information.

[0221] The method shown in Figure 5 enables the management devices to collaborate in completing tasks.

[0222] Figures 4 and 5 illustrate the operation performed by the managed node. The following section describes how the management node obtains device information from the managed node.

[0223] Figure 6 is a schematic diagram of the interaction flow of a device management method 600 according to an embodiment of this application. As shown in Figure 6, a first management device manages a second management device, with the first management device acting as a management node and the second management device acting as a managed node. Method 600 includes:

[0224] S601, the first management device sends a fifth request message to the second management device. Correspondingly, the second management device receives the fifth request message.

[0225] The fifth request requests information about the second management device. For example, the device information of the second management device includes, but is not limited to:

[0226] Equipment resource information (equipment identifier, equipment name, equipment category, equipment manufacturer, equipment serial number, equipment model, equipment version, expiration information (production date, activation date, expiration date, etc.), equipment location, etc.)

[0227] Device status information (device online status, device operating status, device service status, device location information (for movable devices))

[0228] Key performance indicators (KPIs) for equipment (including network KPIs and business KPIs, etc.)

[0229] S602, the second management device sends a fifth response message to the first management device. Correspondingly, the first management device receives the fifth response message.

[0230] The fifth response information indicates the device information of the second management device. Alternatively, the fifth response information includes the device information of the second management device.

[0231] S603. The first management device manages the second management device based on the device information of the second management device.

[0232] For example, when the device information of the second management device includes network KPI information, the first management device can schedule the network resources of the second management device based on the network KPI information of the second management device, and so on.

[0233] For example, when the equipment information of the second management device includes equipment status information, the first management device can manage the equipment operation status of the second management device based on the equipment status information of the second management device, such as cross-management domain (management domain can be understood as the management scope of a certain management device) fault analysis or cross-management domain fault repair, etc.

[0234] The method shown in Figure 6 allows the embodiments of this application to support the management of the second management device by the first management device.

[0235] Figure 6 illustrates how the management node obtains device information from the managed node. The following section describes how the management node is configured to report information from the managed node.

[0236] Figure 7 is a schematic diagram of the interaction flow of a device management method 700 according to an embodiment of this application. As shown in Figure 7, a first management device manages a second management device, with the first management device acting as a management node and the second management device acting as a managed node. Method 700 includes:

[0237] S701, the first management device sends second information to the second management device. Correspondingly, the second management device receives the second information.

[0238] The second information configuration specifies the conditions under which the second management device reports the first information to the first management device.

[0239] For example, the first information is information indicating that the device managed by the second management device is offline, and the condition for reporting the first information is: the device managed by the second management device is detected to be offline;

[0240] For example, the first information is information indicating that the communication link managed by the second management device is disconnected or degraded, and the condition for reporting the first information is: the communication link managed by the second management device is detected to be disconnected or degraded.

[0241] S702, the second management device sends a third message to the first management device. Correspondingly, the third message is used to respond to the second message.

[0242] For example, the third information indicates that the second management device can send the first information to the first management device according to the above conditions.

[0243] S703, the second management device sends the first information to the first management device. Correspondingly, the first management device receives the first information.

[0244] For example, when the second management device determines that the above conditions are met, the second management device reports the first information to the first management device.

[0245] Through S702 and S703, the first management device can configure the conditions for the second management device to report the first information to the first management device. The second management device can report the first information to the first management device based on whether the conditions are met. This can support the first management device to determine the abnormal status information of the second management device based on the first information.

[0246] S704. The first management device determines the abnormal status information of the second management device based on the first information.

[0247] For example, the first information indicates that a device managed by the second management device is offline. Based on the first information, the first management device determines that the device managed by the second management device has gone offline. Accordingly, the first management device modifies the corresponding status information in the global device management table or the global topology diagram. For example, the first management device sets the device managed by the second management device to offline, or the first management device performs further fault analysis or repair, etc.

[0248] For example, the first information indicates that the communication link managed by the second management device is disconnected or degraded. The first management device determines whether the communication link managed by the second management device is disconnected or degraded based on the first information. Accordingly, the first management device modifies the corresponding status information in the global link management table or global topology diagram. For example, the first management device sets the link managed by the second management device to be disconnected or degraded, or the first management device performs further fault analysis or repair.

[0249] The above description uses the information interaction between the first management device and the second management device as an example. The following text describes the information interaction between the first management device and the third management device.

[0250] Figure 8 is a schematic diagram of the interaction flow of a device management method 800 according to an embodiment of this application. As shown in Figure 8, method 800 includes:

[0251] S801, the third management device sends a sixth request message to the first management device. Correspondingly, the first management device receives the sixth request message.

[0252] The sixth request information is used to request the third management device to manage the first management device.

[0253] Optionally, the sixth request information can also be used to request the first management device to manage the third management device, etc.

[0254] Optionally, the sixth request information can also be used to request the establishment of a second management relationship between the first management device and the third management device. For example, the sixth request information requests the establishment of a second management relationship between the first management device and the third management device, which can instruct the third management device to manage the first management device.

[0255] Optionally, the second management relationship may indicate at least one of a third role and a fourth role, where the third role is the role of the first management device as a managed node, and the fourth role is the role of the third management device as a management node.

[0256] When the second management relationship indicates a third role, the first management device can determine that the third management device is requesting management of the first management device. When the second management relationship indicates a fourth role, the first management device can determine that the third management device is requesting management of the first management device. When the second management relationship indicates both a third and a fourth role, the first management device can determine that the third management device is requesting management of the first management device. In summary, the first management device can determine the content requested by the third management device based on the role indicated by the second management relationship.

[0257] One possible implementation is that the sixth request information may include the identification information and management authority information of the third management device. For example, the sixth request information is used to request the third management device to manage the first management device, and the sixth request information may carry information indicating the authority of the third management device when managing the first management device.

[0258] S802, the first management device sends a sixth response message to the third management device. Correspondingly, the third management device receives the sixth response message.

[0259] When the sixth request information requests the third management device to manage the first management device, the first management device can determine whether to allow the third management device to manage the first management device through the aforementioned methods 1-3, which will not be elaborated further.

[0260] Through the above process, the first management device can also establish management relationships with other management devices.

[0261] Optionally, when the sixth request information requests the third management device to manage the first management device, S802 may include:

[0262] S802a, The first management device determines the sixth response information.

[0263] S802b, the first management device sends the sixth response information to the third management device.

[0264] For a description of how the first management device determines the sixth response information, please refer to the aforementioned description of how the second management device determines the first response information, which will not be repeated here.

[0265] Optionally, method 800 may also include:

[0266] S803, the third management device sends a seventh request message to the first management device. Correspondingly, the first management device receives the seventh request message.

[0267] The seventh request information is used to request the first management device to perform a third operation. For example, the third management device manages devices 31 and 32, the first management device manages devices 11 and 12, and the second management device manages devices 21 and 22. Devices 31 and 32 are connected, devices 32 and 11 are connected, devices 11 and 12 are connected, devices 12 and 21 are connected, and devices 21 and 22 are connected. Therefore, devices 31 and 22 are connected, and the third operation is to analyze the link failure between devices 31 and 22.

[0268] S804. The first management device sends a seventh response message to the third management device. Correspondingly, the third management device receives the seventh response message.

[0269] The seventh response information indicates the result of the third operation. For example, the seventh response information indicates that the first management device has successfully executed the third operation, or the seventh response information indicates that the first management device has not successfully executed the third operation.

[0270] Through S803 and S804, after a management relationship is established between the first management device and the third management device, the third management device can instruct the first management device to perform certain operations, thereby enabling the management devices to cooperate in completing tasks.

[0271] Optionally, S804 may include:

[0272] S804a, The first management device determines the list of the second devices.

[0273] The devices in the second device list are those that manage the first management device, and the second device list includes the third management device.

[0274] S804b: The first management device determines the third operation to be performed based on the second device list.

[0275] For example, if the first management device determines that the second device list includes the third management device, and determines that the third management device is the management device that manages the first management device, the first management device performs a third operation. If the first management device determines that the second device list does not include the third management device, and determines that the third management device is not the management device that manages the first management device, the first management device does not perform a third operation.

[0276] One possible implementation is that the second device list also includes information on the management permissions for each managed device.

[0277] When the first management device determines that the second device list includes the third management device, and determines that the management permissions of the third management device in the second device list allow the first management device to perform the third operation, the first management device performs the third operation. If the first management device determines that the management permissions of the third management device in the second device list do not allow the first management device to perform the third operation, the first management device does not perform the third operation.

[0278] When the first management device processes the third operation, the first management device can complete the processing of the third operation on its own, or it can complete the processing of the third operation through the equipment managed by the first management device, without limitation.

[0279] S804c, the first management device determines the seventh response information.

[0280] Based on S804a-S804c, the embodiments of this application can support the first management device to complete the processing or response to the seventh request information.

[0281] The method shown in Figure 8 enables the management of collaborative task completion between devices.

[0282] One possible implementation, method 800, may also include:

[0283] S805, The first management device determines the second operation based on the third operation.

[0284] For example, the third operation could be analyzing link failures between device 31 and device 22, while the second operation could be analyzing link failures between device 31 and device 22 on both devices 21 and 22. This allows for collaborative operation by multiple management devices.

[0285] S806. The first management device sends a third request message to the second management device. Correspondingly, the second management device receives the third request message.

[0286] S807, the second management device sends a third response message to the first management device. Correspondingly, the first management device receives the third response message.

[0287] For a description of S806 and S807, please refer to the descriptions of S401 and S402, which will not be repeated here.

[0288] Through the above-described S805-S807, the embodiments of this application can support multiple management devices to collaboratively complete tasks.

[0289] Using the methods described above, management devices can exchange information regarding the establishment of management relationships, thereby supporting the establishment of such relationships and enabling highly reliable management of the devices. Once a management relationship is established between the management devices, the management node can manage the managed node.

[0290] The following section, in conjunction with Figure 9, further describes the process of establishing management relationships between the aforementioned management devices.

[0291] Figure 9 is a schematic diagram of the interaction flow of a device management method 900 according to an embodiment of this application. As shown in Figure 9, the method 900 includes:

[0292] S901, The first management device receives the fourth information.

[0293] The fourth piece of information may come from the administrator, or it may come from other management devices; there is no limitation on this.

[0294] The fourth information instructs the first management device to send the first request information. Alternatively, the fourth information may indicate that the first management device is a management node or a managed node. When the fourth information indicates that the first management device is a management node, the fourth information may indicate a management device included as a managed node of the first management device, such as a second management device. When the fourth information indicates that the first management device is a managed node, the fourth information may indicate a management device included as a management node of the second management device, such as a second management device.

[0295] Optionally, the fourth information may also include the identification information of the second management device. In this way, the first management device can send a first request to the second management device based on the identification information of the second management device.

[0296] S902, the first management device sends a first request message to the second management device based on the fourth information. Correspondingly, the second management device receives the first request message.

[0297] For a description of S902, please refer to the description of S301, which will not be repeated here.

[0298] S903, the second management device sends a first response message to the first management device. Correspondingly, the first management device receives the first response message.

[0299] For a description of S902, please refer to the description of S302, which will not be repeated here.

[0300] S904, The first management device sends the fifth message. The fifth message is used in response to the fourth message.

[0301] When the fourth message originates from an administrator, the first management device can send the fifth message to that administrator. When the fourth message originates from another management device, the first management device can send the fifth message to that management device. The fifth message is a response to the fourth message.

[0302] For example, the fifth message indicates that the first management device successfully manages the second management device, or the fifth message indicates that the second management device successfully manages the first management device; or the fifth message indicates that the first management device fails to successfully manage the second management device, or the fifth message indicates that the second management device refuses to manage the first management device, etc.

[0303] Through method 900, embodiments of this application can support the interaction of first request information and first response information between the first management device and the second management device, thereby enabling the establishment of a management relationship between the first management device and the second management device.

[0304] To achieve the functions of the methods provided in this application, the first management device, the second management device, and the third management device may each include hardware structures and / or software modules, implementing the aforementioned functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0305] Figure 10 is a schematic block diagram of a communication device 1000 according to an embodiment of this application. The communication device 1000 includes a processing circuit 1010 and a transceiver circuit 1020, which can be interconnected or coupled to each other, for example, through a bus 1030. The communication device 1000 can be a first management device, a second management device, or a third management device.

[0306] Optionally, the communication device 1000 may further include a memory 1040. The memory 1040 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM). The memory 1040 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. The memory in the embodiments of this application may also be a circuit or any other device capable of implementing a storage function for storing computer programs or instructions, and / or data.

[0307] The processing circuit 1010 can be all or part of the processing circuitry in one or more processors, or it can be one or more processors. The processor can be a central processing unit (CPU). If the processing circuit 1010 is a CPU, the CPU can be a single-core CPU or a multi-core CPU. The processing circuit 1010 can be a signal processor, a chip, or other integrated circuit capable of implementing the methods of this application, or a portion of the circuitry within the aforementioned processor, chip, or integrated circuit that performs processing functions. Additionally, the transceiver circuit 1020 can be a transceiver, or an input / output interface. An input / output interface is used for inputting or outputting signals or data and can also be referred to as an input / output circuit.

[0308] When the communication device 1000 is a first management device, the processing circuit 1010 is configured to perform the following operations: send a first request message to a second management device, and receive a first response message from the second management device, etc.

[0309] When the communication device 1000 is a second management device, exemplarily, the processing circuit 1010 is configured to perform the following operations: receive a first request message from a first management device, and send a first response message to the first management device, etc.

[0310] When the communication device 1000 is a third management device, the processing circuit 1010 is configured to perform the following operations: send a sixth request message to the first management device, and receive a sixth response message from the first management device, etc.

[0311] When the communication device 1000 is a first management device, a second management device, or a third management device, it will be responsible for executing the methods or steps related to the first management device, the second management device, or the third management device in the aforementioned method embodiments.

[0312] When the communication device 1000 is a first management device, a second management device, or a third management device, the transceiver circuit 1020 can be a transceiver.

[0313] When the communication device 1000 is a chip used for a first management device, a second management device, or a third management device, the transceiver circuit 1020 can be an input / output circuit.

[0314] The above description is merely exemplary. For details, please refer to the content shown in the above method embodiments.

[0315] The implementation of each operation in Figure 10 can also be described in the corresponding description of the method embodiments shown in Figures 3 to 9.

[0316] Figure 11 is a schematic block diagram of a communication device 1100 according to an embodiment of this application. The communication device 1100 can be a first management device, a second management device, or a third management device, used to implement the methods involved in the above embodiments.

[0317] The communication device 1100 includes a transceiver unit 1110 and a processing unit 1120. The transceiver unit 1110 may include a sending unit and a receiving unit. The sending unit performs the sending action of the communication device, and the receiving unit performs the receiving action of the communication device. For ease of description, the sending unit and the receiving unit are combined into a single transceiver unit in this embodiment. This will be explained uniformly here and will not be repeated later.

[0318] When the communication device 1100 is a first management device, exemplarily, the transceiver unit 1110 is used to send a first request information to a second management device, and to receive a first response information from the second management device, etc.; the processing unit 1120 is used to determine the first request information, etc.

[0319] When the communication device 1100 is a second management device, exemplarily, the transceiver unit 1110 is used to: receive a first request information from the first management device, and to send a first response information to the first management device, etc.; the processing unit 1120 is used to determine the first response information, etc.

[0320] When the communication device 1100 is a third management device, exemplarily, the transceiver unit 1110 is used to: send a sixth request message to the first management device, and to receive a sixth response message from the first management device; the processing unit 1120 is used to determine second data, etc.

[0321] When the communication device 1100 is a first management device, a second management device, or a third management device, it will be responsible for executing one or more of the methods or steps related to the first management device, the second management device, or the third management device in the aforementioned method embodiments.

[0322] Optionally, the communication device 1100 further includes a storage unit 1130 for storing programs or code for performing the aforementioned methods.

[0323] The transceiver unit in Figure 11 corresponds to the transceiver circuit in Figure 10, and the processing unit in Figure 11 corresponds to the processing circuit in Figure 10.

[0324] The apparatus embodiments shown in Figures 10 and 11 are used to implement the contents described in Figures 3 to 9. The specific execution steps and methods of the apparatus shown in Figures 10 and 11 can be found in the foregoing method embodiments.

[0325] This application also provides a chip, including a processor, for calling and executing instructions stored in a memory, causing a communication device on which the chip is installed to perform the methods described in the examples above. The memory may be integrated within the chip or located externally.

[0326] This application also provides another chip, including: an input interface, an output interface, and a processing circuit, wherein the input interface, the output interface, and the processor are connected through an internal connection path, and the processing circuit is used to execute code in memory. When the code is executed, the processing circuit is used to execute the methods in the above examples.

[0327] Optionally, the chip also includes a memory for storing computer programs or code. The input and output interfaces can be independent of each other, or they can be integrated into a single input / output interface.

[0328] The processing circuitry can be all or part of the processing circuitry in one or more processors, or one or more processors.

[0329] This application also provides a processor for coupling with a memory for performing the methods and functions of a network device or terminal device involved in any of the above embodiments.

[0330] In another embodiment of this application, a computer program product containing instructions is provided, which, when run on a computer, enables the implementation of the methods described in the foregoing embodiments.

[0331] This application also provides a computer program that, when run on a computer, enables the implementation of the methods described in the foregoing embodiments.

[0332] In another embodiment of this application, a computer-readable storage medium is provided, which stores a computer program that, when executed by a computer, implements the methods described in the foregoing embodiments.

[0333] It should be understood that in the embodiments of this application, the processor can be a central processing unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0334] In addition, the processor may include one or more of the following: a central processing unit (CPU), a baseband processor, a digital signal processor (DSP), a microprocessor (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an artificial intelligence processor (AI processor), or a neural processing unit (NPU).

[0335] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced synchronous SDRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0336] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0337] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0338] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for example, the division of units is merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0339] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the above functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

[0340] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Claims

1. A method for equipment management, characterized in that, Applied to the first management device, including: Send a first request message to the second management device, wherein the first request message requests at least one of the following: The first management device manages the second management device, or the second management device manages the first management device; Receive first response information from the second management device, the first response information being used to respond to the first request information.

2. The method according to claim 1, characterized in that, The method further includes: Receive a second request message from the second management device, the second request message requesting the second management device to manage the first management device, or the second request message requesting the first management device to manage the second management device; Send a second response message to the second management device, the second response message being used to respond to the second request message.

3. The method according to claim 2, characterized in that, The second request information requests the second management device to manage the first management device, and the step of sending the second response information to the second management device includes: The second response information is determined, and the second response information indicates whether the second management device is allowed to manage the first management device; Send the second response information to the second management device.

4. The method according to any one of claims 1 to 3, characterized in that, The first management device manages the second management device, and the method further includes: Send a third request message to the second management device, the third request message requesting the execution of the first operation; Receive a third response message from the second management device, the third response message indicating the execution result of the first operation.

5. The method according to any one of claims 1 to 3, characterized in that, The second management device manages the first management device, and the method further includes: Receive a fourth request message from the second management device, the fourth message requesting the execution of a second operation; A fourth response message is sent to the second management device, the fourth response message indicating the execution result of the second operation.

6. The method according to claim 5, characterized in that, Sending the fourth response information to the second management device includes: A first device list is determined, wherein the devices in the first device list are devices that manage the first managed device, and the first device list includes the second managed device; Based on the first device list, determine to perform the second operation; Determine the fourth response information.

7. The method according to any one of claims 1 to 4, characterized in that, The first management device manages the second management device, and the method further includes: Send a fifth request message to the second management device, the fifth request message requesting to obtain the device information of the second management device; Receive a fifth response message from the second management device, the fifth response message indicating device information of the second management device; The second management device is managed based on its device information.

8. The method according to any one of claims 1 to 4, characterized in that, The first management device manages the second management device, and the method further includes: Receive first information from the second management device; Based on the first information, the abnormal status information of the second management device is determined.

9. The method according to claim 8, characterized in that, Before receiving the first information from the second management device, the method further includes: Send second information to the second management device, wherein the second information configures the conditions for the second management device to report the first information to the first management device; Receive third information from the second management device, the third information being used in response to the second information.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: Receive a sixth request message from a third management device, the sixth request message requesting the third management device to manage the first management device; A sixth response message is sent to the third management device, the sixth response message being used to respond to the sixth request message.

11. The method according to claim 10, characterized in that, Sending the sixth response information to the third management device includes: The sixth response information is determined, and the sixth response information indicates whether the third management device is allowed to manage the first management device; The sixth response information is sent to the third management device.

12. The method according to claim 10 or 11, characterized in that, The sixth response information indicates permission for the third management device to manage the first management device, and the method further includes: Receive a seventh request message from the third management device, the seventh request message requesting the execution of a third operation; A seventh response message is sent to the third management device, the seventh response message indicating the execution result of the third operation.

13. The method according to claim 12, characterized in that, Sending the seventh response information to the third management device includes: A second device list is determined, wherein the devices in the second device list are the devices that manage the first management device, and the second device list includes the third management device; Based on the second device list, determine to perform the third operation; The seventh response information is sent to the third management device.

14. The method according to claim 12 or 13, characterized in that, The method further includes: The second operation is determined based on the third operation; A third request message is sent to the second management device, the third request message requesting the execution of the second operation; wherein, the first management device manages the second management device.

15. The method according to any one of claims 1 to 14, characterized in that, Before sending the first request information to the second management device, the method further includes: Receive a fourth message, the fourth message instructing the first management device to send the first request message; Sending the first request information to the second management device includes: Based on the fourth information, the first request information is sent.

16. The method according to any one of claims 1 to 15, characterized in that, The devices managed by the first management device are different from the devices managed by the second management device.

17. A method for equipment management, characterized in that, Applied to the second management device, including: Receive a first request message from a first management device, the first request message requesting at least one of the following: The first management device manages the second management device, or the second management device manages the first management device; Send a first response message to the first management device, the first response message being used to respond to the first request message.

18. The method according to claim 17, characterized in that, The method further includes: Send a second request message to the first management device, the second request message requesting the second management device to manage the first management device, or the second request message requesting the first management device to manage the second management device; Receive a second response message from the first management device, the second response message being used to respond to the second request message.

19. The method according to claim 17 or 18, characterized in that, The first request information requests the first management device to manage the second management device, and the step of sending the first response information to the first management device includes: The first response information is determined, and the first response information indicates whether the first management device is allowed to manage the second management device; Send the first response information to the first management device.

20. The method according to any one of claims 17 to 19, characterized in that, The first management device manages the second management device, and the method further includes: Receive a third request message from the first management device, the third request message requesting the execution of a first operation; A third response message is sent to the first management device, the third response message indicating the execution result of the first operation.

21. The method according to claim 20, characterized in that, The third response information to the first management device includes: A third device list is determined, wherein the devices in the third device list are devices that manage the second management device, and the third device list includes the first management device; Based on the third device list, it is determined that the first operation will be performed; Determine the third response information.

22. The method according to claim 17 or 18, characterized in that, The second management device manages the first management device, and the method further includes: Send a fourth request message to the first management device, the fourth request message requesting the execution of the second operation; Receive a fourth response message from the first management device, the fourth response message indicating the execution result of the second operation.

23. The method according to any one of claims 17 to 21, characterized in that, The first management device manages the second management device, and the method further includes: Receive a fifth request message from the first management device, the fifth request message requesting to obtain device information of the second management device; A fifth response message is sent to the first management device, the fifth response message indicating the device information of the second management device, the device information of the second management device being used by the first management device to manage the second management device.

24. The method according to any one of claims 17 to 21, characterized in that, The first management device manages the second management device, and the method further includes: Send first information to the first management device, the first information being used by the first management device to determine the abnormal status information of the second management device.

25. The method according to claim 24, characterized in that, Before sending the first information to the first management device, the method further includes: Receive second information from the first management device, wherein the second information configures the conditions for the second management device to report the first information to the first management device; A third message is sent to the first management device, the third message being used in response to the second message.

26. The method according to any one of claims 17 to 25, characterized in that, The devices managed by the first management device are different from the devices managed by the second management device.

27. A communication device, characterized in that, Includes a processor, the processor being configured to cause the communication device to perform the method of any one of claims 1 to 26 by executing a computer program or instructions, or by using logic circuitry.

28. The communication device according to claim 27, characterized in that, The communication device further includes a memory for storing the computer program or instructions.

29. The communication device according to claim 27 or 28, characterized in that, The communication device further includes a communication interface for inputting and / or outputting signals.

30. A communication device, characterized in that, It includes logic circuitry and input / output interfaces, the input / output interfaces being used to input and / or output signals, and the logic circuitry being used to perform the method of any one of claims 1 to 26.

31. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a computer, cause the method of any one of claims 1 to 26 to be performed.

32. A computer program product, characterized in that, It includes instructions that, when run on a computer, cause the method of any one of claims 1 to 26 to be performed.

Images