Multi-tenant operation and maintenance management method, device and system

Abstract

The embodiments of the present application provide a multi-tenant operation and maintenance management method, device, and system for location information, which are used to resolve the problem of duplicate blueprint file names conflicts generated when an operator hosts operation and maintenance services for multiple tenants, which may lead to operation conflicts and / or user privacy leaks. The method includes: a first device receives a first file uploaded by a first tenant from a second device, where the first file is used to describe the operation and maintenance services provided to the first tenant; the first device determines that the name of the first file does not conflict with any file name in a set of file names stored in the first device; and the first device stores the name of the first file in the set of file names.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a multi-tenant operation and maintenance management method, device, and system. Background Art

[0002] With the increasing popularity of fifth-generation (5G) networks, more and more companies are deploying 5G networks to improve work efficiency. However, most companies lack experience in 5G network operations and maintenance (O&M) and the resources to train professional 5G network O&M personnel. Therefore, these companies choose to outsource O&M services to operators.

[0003] In the prior art, operators usually use the open network automation platform (ONAP) to implement the operation and maintenance management of 5G networks. However, when the operator hosts the operation and maintenance services of multiple tenants, multiple tenants may upload blueprint files with different contents for the same operation and maintenance operation, resulting in duplicate name conflicts in the blueprint files, which may in turn lead to operation conflicts and / or user privacy leaks. For example, suppose tenant A first uploads blueprint file A1 to ONAP, and tenant B later uploads blueprint file B1 with the same name as A1. At this time, B1 will replace A1. When tenant A calls the blueprint file to perform operation and maintenance operations, tenant A can only call blueprint file B1. On the one hand, both tenant A and tenant B can call blueprint file B1, resulting in an operation conflict. On the other hand, tenant A calls a blueprint file that does not belong to him, which causes tenant B's privacy to be leaked. Summary of the Invention

[0004] The embodiments of the present application provide a multi-tenant operation and maintenance management method, device, and system for resolving the problem of blueprint file name conflicts caused when an operator hosts operation and maintenance services for multiple tenants, which may lead to operation conflicts and / or user privacy leaks.

[0005] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0006] On the first aspect, a multi-tenant operation and maintenance management method is provided, and the communication device that executes the multi-tenant operation and maintenance management method can be a first device, or a module applied to the first device, such as a chip or a chip system. The following description is made by taking the execution subject as the first device as an example. The first device receives a first file uploaded by a first tenant from a second device, and the first file is used to describe the operation and maintenance service provided for the first tenant; the first device determines that the name of the first file does not conflict with any file name in the file name set stored in the first device; the first device stores the name of the first file in the file name set. Because the first device will continue to execute the multi-tenant operation and maintenance management method provided by the embodiment of the present application only when it determines that the name of the first file does not conflict with any file name in the file name set stored in the first device. Therefore, the multi-tenant operation and maintenance management method provided by the embodiment of the present application can ensure that the files uploaded by multiple tenants will not have the same name, and thus will not replace or overwrite each other, thereby avoiding the problems of operation conflicts and privacy leaks caused by duplicate name conflicts.

[0007] In combination with the first aspect above, in a possible implementation, the first device receives the identifier of the first tenant from the second device; after the first device stores the name of the first file in the file name set, it also includes: the first device sends a first message to the fourth device, the first message includes the identifier of the first tenant and the name of the first file, and the first message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the name of the first file. The first device receives a first indication message from the fourth device, and the first indication message is used to indicate whether the fourth device successfully or failed to store the mapping relationship between the identifier of the first tenant and the name of the first file. Through the multi-tenant operation and maintenance management method provided by the embodiment of the present application, the mapping relationship between the identifier of the first tenant and the name of the first file can be stored on the fourth device to facilitate subsequent control of the permission to call the first file, that is, only the first tenant is allowed to call the first file, and other tenants cannot call the first file.

[0008] In combination with the first aspect above, in a possible implementation, after the first device stores the name of the first file in the file name set, it also includes: the first device sends a second message to the third device, the second message includes the first file, and the second message is used to request the third device to load the first file; the first device receives a second indication message from the third device, and the second indication message is used to indicate the success or failure of loading the first file; the first device sends a third indication message to the second device, and the third indication message is used to indicate the success or failure of the first tenant to upload the first file. Through the multi-tenant operation and maintenance management method provided by the embodiment of the present application, the first file can be loaded on the third device to facilitate subsequent calls to the first file by other devices.

[0009] In a second aspect, a multi-tenant operation and maintenance management method is provided. The communication device that executes the multi-tenant operation and maintenance management method can be a first device, or a module applied to the first device, such as a chip or chip system. The following description takes the execution subject as the first device as an example. The first device receives a third message from the second device, the third message including the identifier of the first tenant and the identifier of the first network function, and the third message is used by the first tenant to request instantiation of the first network function; the first device determines that the identifier of the first network function is one of the identifiers of one or more network functions corresponding to the identifier of the first tenant stored in the first device; and the first device sends the third message to a fifth device. Because the instantiation process of the first network function will only be triggered when the first device determines that the identifier of the first network function is one of the identifiers of one or more network functions corresponding to the identifier of the first tenant stored in the first device. Therefore, the multi-tenant operation and maintenance management method provided in the embodiment of the present application can limit the permission to instantiate the first network function, thereby ensuring that tenants only access and / or operate the existing network function resources belonging to them, thereby avoiding operation conflicts and privacy leaks.

[0010] In combination with the above-mentioned second aspect, in a possible implementation, before the first device sends the third message to the fifth device, it also includes: the first device determines that the Internet Protocol IP address of the second device belongs to one of the one or more IP addresses corresponding to the identifier of the first tenant stored in the first device. Because the first device can ensure that the second device belongs to the first tenant and is not a fake by determining that the IP address of the second device belongs to one of the one or more IP addresses corresponding to the identifier of the first tenant stored in the first device, the multi-tenant operation and maintenance management method provided in the embodiment of the present application can prevent malicious tampering with data or network attacks, thereby enhancing the security of the instantiated first network function.

[0011] In conjunction with the second aspect above, in one possible implementation, before the first device receives the third message from the second device, the process further includes: the first device receiving the name of the first tenant from the second device; the first device generating an identifier of the first tenant based on the name of the first tenant; and the first device storing a mapping relationship between the identifier of the first tenant and the IP address of the second device. In the multi-tenant operation and maintenance management method provided in an embodiment of the present application, the first device stores a mapping relationship between the identifier of the first tenant and the IP address of the second device to indicate that the second device belongs to the first tenant.

[0012] On the third aspect, a multi-tenant operation and maintenance management method is provided, and the communication device that executes the multi-tenant operation and maintenance management method can be a first device, or a module applied to the first device, such as a chip or a chip system. The following description is made by taking the execution subject as the first device as an example. The first device receives a fourth message from the second device, the fourth message including the identifier of the first tenant, and the fourth message is used by the first tenant to request to perform a first operation and maintenance operation; the first device sends a fifth message to the fourth device, the fifth message including the identifier of the first tenant and a filtering condition parameter, and the fifth message is used to request the fourth device to query the operation and maintenance service file of the first tenant that meets the filtering condition parameter; the first device receives the operation and maintenance service file of the first tenant that meets the filtering condition parameter from the fourth device; the first device determines that the first operation and maintenance operation belongs to the operation and maintenance operation that the first tenant has the authority to perform as described in the operation and maintenance service file of the first tenant that meets the filtering condition parameter; the first device executes the first operation and maintenance operation to obtain the execution result of the first operation and maintenance operation. Because the first device determines that the first operation and maintenance operation belongs to the operation and maintenance operation that the first tenant has the authority to perform as described in the operation and maintenance service file of the first tenant that meets the screening condition parameters, the first operation will continue to be performed. Therefore, the multi-tenant operation and maintenance management method provided in the embodiment of the present application can control the authority to perform the first operation. For example, when the first operation is to access operation and maintenance data, the method provided in this embodiment can control the access rights to the operation and maintenance data, thereby ensuring that tenants can only access their own operation and maintenance data, thereby avoiding the problem of privacy leakage.

[0013] In conjunction with the third aspect above, in one possible implementation, before the first device performs the first operation and maintenance operation, the process further includes: the first device receiving the name of the first file corresponding to the identifier of the first tenant from the fourth device; and the first device determining that the name of the second file called to perform the first operation and maintenance operation is the name of the first file. Through the multi-tenant operation and maintenance management method provided in the embodiment of the present application, the first device can control the permission to call the first file, thereby ensuring that the first tenant can only call its own files, thereby further avoiding operation conflicts and privacy leaks.

[0014] In combination with the third aspect above, in a possible implementation, before the first device receives the fourth message from the second device, it also includes: the first device receives the first file uploaded by the first tenant from the second device, and the first file is used to describe the operation and maintenance services provided to the first tenant; the first device determines that the name of the first file does not conflict with any file name in the file name set stored in the first device; the first device stores the name of the first file in the file name set. Because the first device will continue to execute the multi-tenant operation and maintenance management method provided by the embodiment of the present application only when it determines that the name of the first file does not conflict with any file name in the file name set stored in the first device. Therefore, the multi-tenant operation and maintenance management method provided by the embodiment of the present application can ensure that files uploaded by multiple tenants will not have the same name, and thus will not replace or overwrite each other, thereby avoiding the problems of operational conflicts and privacy leaks caused by duplicate name conflicts.

[0015] In combination with the third aspect above, in a possible implementation, the first device receives the identifier of the first tenant from the second device; after the first device stores the name of the first file in the file name set, it also includes: the first device sends a first message to the fourth device, the first message includes the identifier of the first tenant and the name of the first file, and the first message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the name of the first file; the first device receives a first indication message from the fourth device, and the first indication message is used to indicate whether the fourth device successfully or failed to store the mapping relationship between the identifier of the first tenant and the name of the first file. Through the multi-tenant operation and maintenance management method provided by the embodiment of the present application, the mapping relationship between the identifier of the first tenant and the name of the first file can be stored on the fourth device to facilitate the subsequent control of the permission to call the first file, that is, only the first tenant is allowed to call the first file, and other tenants cannot call the first file.

[0016] In combination with the third aspect above, in a possible implementation, before the first device receives the fourth message from the second device, it also includes: the first device receives the name of the first tenant and the operation and maintenance service file of the first tenant from the second device, the operation and maintenance service file of the first tenant is used to describe the operation and maintenance operations that the first tenant has the right to perform; the first device generates the identifier of the first tenant according to the name of the first tenant; the first device sends a sixth message to the fourth device, the sixth message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant; the first device receives a fourth indication message from the fourth device, the fourth indication message is used to indicate whether the fourth device stores the mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant successfully or failed. Through the multi-tenant operation and maintenance management method provided by the embodiment of the present application, the fourth device can store the mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant, wherein the operation and maintenance service file of the first tenant is used to describe the operation and maintenance operations that the first tenant has the right to perform, thereby facilitating the subsequent control of the authority to perform the first operation.

[0017] In combination with the above-mentioned third aspect, in a possible implementation method, when the first operation and maintenance operation is to access first operation and maintenance data, before the first device executes the first operation and maintenance operation, it also includes: the first device receives the identifier of the first measurement task from the fourth device; the first device executes the first operation and maintenance operation to obtain the execution result of the first operation and maintenance operation, including: the first device executes the first operation and maintenance operation according to the identifier of the first measurement task to obtain the execution result of the first operation and maintenance operation.

[0018] In combination with the above-mentioned third aspect, in a possible implementation method, the first device executes the first operation and maintenance operation according to the identifier of the first measurement task to obtain the execution result of the first operation and maintenance operation, including: the first device sends a seventh message to the sixth device, the seventh message includes the filtering condition parameters and the identifier of the first measurement task, and the seventh message is used to request access to the first operation and maintenance data; the first device receives the first operation and maintenance data from the sixth device, wherein the first operation and maintenance data is the execution result of the first operation and maintenance operation.

[0019] In combination with the third aspect above, in a possible implementation, after the first device executes the first operation and maintenance operation, it also includes: the first device sends an eighth message to the fourth device, and the eighth message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation; the first device receives a fifth indication message from the fourth device, and the fifth indication message is used to indicate whether the fourth device stores the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation successfully or failed. Through the multi-tenant operation and maintenance management method provided by the embodiment of the present application, the fourth device can store the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation, thereby facilitating the subsequent control of the execution authority of the second operation and maintenance operation, wherein the second operation and maintenance operation can, for example, be accessing and / or operating the execution result of the first operation and maintenance operation.

[0020] In combination with the third aspect above, in a possible implementation, after the first device executes the first operation and maintenance operation, the method further includes: the first device sending an execution result of the first operation and maintenance operation to the second device.

[0021] In a fourth aspect, a communication device is provided for implementing the above method. The communication device includes modules, units, or means corresponding to the above method. The modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules or units corresponding to the above functions.

[0022] In combination with the above-mentioned fourth aspect, in a possible implementation method, the communication device includes: a transceiver module, a processing module and a storage module; the transceiver module is used to receive a first file uploaded by a first tenant from a second device, and the first file is used to describe the operation and maintenance service provided to the first tenant; the processing module is used to determine that the name of the first file does not conflict with any file name in the file name set stored in the communication device; the storage module is used to store the name of the first file in the file name set.

[0023] In combination with the above-mentioned fourth aspect, in a possible implementation method, the transceiver module is also used to: receive the identifier of the first tenant from the second device; send a first message to the fourth device, the first message including the identifier of the first tenant and the name of the first file, and the first message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the name of the first file; receive first indication information from the fourth device, and the first indication information is used to indicate whether the fourth device succeeds or fails in storing the mapping relationship between the identifier of the first tenant and the name of the first file.

[0024] In combination with the above-mentioned fourth aspect, in a possible implementation method, the transceiver module is also used to: send a second message to a third device, the second message including the first file, and the second message being used to request the third device to load the first file; receive second indication information from the third device, the second indication information being used to indicate success or failure in loading the first file; and send third indication information to the second device, the third indication information being used to indicate success or failure in uploading the first file by the first tenant.

[0025] In combination with the fourth aspect above, in a possible implementation, the processing module may be a processor, and the transceiver module may be a communication interface.

[0026] Among them, the technical effects brought about by any possible implementation method of the above-mentioned fourth aspect can be referred to the technical effects brought about by different implementation methods of the above-mentioned first aspect, and will not be repeated here.

[0027] In a fifth aspect, a communication device is provided for implementing the above method. The communication device includes modules, units, or means corresponding to the above method. The modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules or units corresponding to the above functions.

[0028] In combination with the above-mentioned fifth aspect, in a possible implementation, the communication device includes: a transceiver module, a processing module and a storage module; the transceiver module is used to receive a third message from the second device, the third message including the identifier of the first tenant and the identifier of the first network function, and the third message is used by the first tenant to request instantiation of the first network function; the processing module is used to determine that the identifier of the first network function is one of the identifiers of one or more network functions corresponding to the identifier of the first tenant stored in the communication device; the transceiver module is also used to send the third message to the fifth device.

[0029] In combination with the fifth aspect above, in a possible implementation, the processing module is further used to determine that the IP address of the second device belongs to one of the one or more IP addresses corresponding to the identifier of the first tenant stored in the communication device.

[0030] In combination with the above-mentioned fifth aspect, in a possible implementation method, the transceiver module is also used to receive the name of the first tenant from the second device; the processing module is also used to generate the identifier of the first tenant based on the name of the first tenant; the storage module is used to store the mapping relationship between the identifier of the first tenant and the IP address of the second device.

[0031] In combination with the fifth aspect above, in a possible implementation, the processing module may be a processor, and the transceiver module may be a communication interface.

[0032] Among them, the technical effects brought about by any possible implementation method of the above-mentioned fifth aspect can be referred to the technical effects brought about by different implementation methods in the above-mentioned second aspect, and will not be repeated here.

[0033] In a sixth aspect, a communication device is provided for implementing the above method. The communication device includes modules, units, or means corresponding to the above method. The modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules or units corresponding to the above functions.

[0034] In combination with the above-mentioned sixth aspect, in a possible implementation method, the communication device includes: a transceiver module, a processing module and a storage module; the transceiver module is used to receive a fourth message from the second device, the fourth message including the identifier of the first tenant, and the fourth message is used by the first tenant to request to perform a first operation and maintenance operation; the transceiver module is also used to send a fifth message to the fourth device, the fifth message including the identifier of the first tenant and the filtering condition parameters, and the fifth message is used to request the fourth device to query the operation and maintenance service file of the first tenant that meets the filtering condition parameters; the transceiver module is also used to receive the operation and maintenance service file of the first tenant that meets the filtering condition parameters from the fourth device; the processing module is used to determine that the first operation and maintenance operation belongs to the operation and maintenance operation that the first tenant has the authority to perform as described in the operation and maintenance service file of the first tenant that meets the filtering condition parameters; the processing module is also used to execute the first operation and maintenance operation to obtain the execution result of the first operation and maintenance operation.

[0035] In combination with the above-mentioned sixth aspect, in a possible implementation method, the transceiver module is also used to receive the name of the first file corresponding to the identifier of the first tenant from the fourth device; the processing module is also used to determine that the name of the second file called to perform the first operation and maintenance operation is the name of the first file.

[0036] In combination with the above-mentioned sixth aspect, in a possible implementation method, the transceiver module is also used to receive a first file uploaded by the first tenant of the second device, and the first file is used to describe the operation and maintenance services provided to the first tenant; the processing module is used to determine that the name of the first file does not conflict with any file name in the file name set stored in the communication device; and the storage module is used to store the name of the first file in the file name set.

[0037] In combination with the above-mentioned sixth aspect, in a possible implementation method, the transceiver module is also used to: receive the identifier of the first tenant from the second device; send a first message to the fourth device, the first message including the identifier of the first tenant and the name of the first file, and the first message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the name of the first file; receive first indication information from the fourth device, and the first indication information is used to indicate whether the fourth device succeeds or fails in storing the mapping relationship between the identifier of the first tenant and the name of the first file.

[0038] In combination with the above-mentioned sixth aspect, in a possible implementation method, the transceiver module is also used to receive the name of the first tenant and the operation and maintenance service file of the first tenant from the second device, and the operation and maintenance service file of the first tenant is used to describe the operation and maintenance operations that the first tenant is authorized to perform; the processing module is also used to generate the identifier of the first tenant based on the name of the first tenant; the transceiver module is also used to send a sixth message to the fourth device, and the sixth message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant; the transceiver module is also used to receive fourth indication information from the fourth device, and the fourth indication information is used to indicate whether the fourth device successfully or failed to store the mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant.

[0039] In combination with the above-mentioned sixth aspect, in a possible implementation method, when the first operation and maintenance operation is to access the first operation and maintenance data, the transceiver module is also used to receive the identifier of the first measurement task from the fourth device; the processing module is also used to execute the first operation and maintenance operation to obtain the execution result of the first operation and maintenance operation, including: executing the first operation and maintenance operation according to the identifier of the first measurement task to obtain the execution result of the first operation and maintenance operation.

[0040] In combination with the above-mentioned sixth aspect, in a possible implementation method, the processing module is also used to execute the first operation and maintenance operation according to the identifier of the first measurement task to obtain the execution result of the first operation and maintenance operation, including: the transceiver module is also used to send a seventh message to the sixth device, the seventh message including the filtering condition parameters and the identifier of the first measurement task, and the seventh message is used to request access to the first operation and maintenance data; the transceiver module is also used to receive the first operation and maintenance data from the sixth device, wherein the first operation and maintenance data is the execution result of the first operation and maintenance operation.

[0041] In combination with the above-mentioned sixth aspect, in a possible implementation method, the transceiver module is also used to: send an eighth message to the fourth device, and the eighth message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation; receive fifth indication information from the fourth device, and the fifth indication information is used to indicate whether the fourth device succeeds or fails in storing the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation.

[0042] In combination with the sixth aspect above, in a possible implementation, the transceiver module is further configured to send an execution result of the first operation and maintenance operation to the second device.

[0043] In combination with the sixth aspect above, in a possible implementation, the processing module may be a processor, and the transceiver module may be a communication interface.

[0044] Among them, the technical effects brought about by any possible implementation method of the above-mentioned sixth aspect can be referred to the technical effects brought about by different implementation methods of the above-mentioned third aspect, and will not be repeated here.

[0045] In the seventh aspect, a communication system is provided, which includes a first device and a second device; the second device is used to send a first file uploaded by a first tenant to the first device, and the first file is used to describe the operation and maintenance service provided to the first tenant; the first device is used to receive the first file uploaded by the first tenant from the second device; the first device is also used to determine that the name of the first file does not conflict with any file name in the file name set stored in the first device; the first device is also used to store the name of the first file in the file name set.

[0046] Since the first device in the communication system provided by the seventh aspect can execute the multi-tenant operation and maintenance management method in the first aspect, the technical effects brought about by the seventh aspect can be referred to the technical effects brought about by the first aspect and different implementation methods in the first aspect, and will not be repeated here.

[0047] In an eighth aspect, a communication system is provided, which includes a first device, a second device and a fifth device; the second device is used to send a third message to the first device, the third message including an identifier of the first tenant and an identifier of the first network function, and the third message is used by the first tenant to request instantiation of the first network function; the first device is used to receive the third message from the second device; the first device is further used to determine that the identifier of the first network function is one of the identifiers of one or more network functions corresponding to the identifier of the first tenant stored in the first device; the first device is further used to send the third message to the fifth device; the fifth device is used to receive the third message from the first device.

[0048] Since the first device in the communication system provided in the eighth aspect can execute the multi-tenant operation and maintenance management method in the second aspect, the technical effects brought about by the eighth aspect can be referred to the technical effects brought about by the second aspect and different implementation methods in the second aspect, and will not be repeated here.

[0049] In a ninth aspect, a communication system is provided, which includes a first device, a second device and a fourth device; the second device is used to send a fourth message to the first device, the fourth message including an identifier of a first tenant, and the fourth message is used by the first tenant to request to perform a first operation and maintenance operation; the first device is used to receive the fourth message from the second device; the first device is also used to send a fifth message to the fourth device, the fifth message including an identifier of the first tenant and a filtering condition parameter, and the fifth message is used to request the fourth device to query the operation and maintenance service file of the first tenant that meets the filtering condition parameter; the The fourth device is used to receive the fifth message from the first device; the fourth device is also used to send the operation and maintenance service file of the first tenant that meets the filtering condition parameters to the first device; the first device is also used to receive the operation and maintenance service file of the first tenant that meets the filtering condition parameters from the fourth device; the first device is also used to determine that the first operation and maintenance operation belongs to the operation and maintenance operation that the first tenant has the authority to perform as described in the operation and maintenance service file of the first tenant that meets the filtering condition parameters; the first device is also used to execute the first operation and maintenance operation to obtain the execution result of the first operation and maintenance operation.

[0050] Since the first device in the communication system provided by the ninth aspect can execute the multi-tenant operation and maintenance management method in the third aspect, the technical effects brought about by the ninth aspect can be referred to the technical effects brought about by the third aspect and different implementation methods in the third aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 It is a structural diagram of ONAP in the prior art;

[0052] Figure 2 This is a schematic diagram of the evolution of ONAP in the prior art from supporting only carrier networks to supporting multi-tenant networks;

[0053] Figure 3 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0054] Figure 4 A schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0055] Figure 5A schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0056] Figure 6 A schematic diagram illustrating the evolution of ONAP in the prior art to the enhanced ONAP provided in the embodiments of the present application in a scenario supporting multi-tenant networks;

[0057] Figure 7 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0058] Figure 8 A multi-tenant operation and maintenance management method provided in this application embodiment Figure 1 ;

[0059] Figure 9 A multi-tenant operation and maintenance management method provided in this application embodiment Figure 2 ;

[0060] Figure 10 A multi-tenant operation and maintenance management method provided in this application embodiment Figure 3 ;

[0061] Figure 11 Another multi-tenant operation and maintenance management method provided in this application embodiment Figure 1 ;

[0062] Figure 12 Another multi-tenant operation and maintenance management method provided in this application embodiment Figure 2 ;

[0063] Figure 13 Another multi-tenant operation and maintenance management method provided in this embodiment of the application Figure 1 ;

[0064] Figure 14 Another multi-tenant operation and maintenance management method provided in this embodiment of the application Figure 2 ;

[0065] Figure 15 A flowchart of another multi-tenant operation and maintenance management method provided in an embodiment of the present application;

[0066] Figure 16 A multi-tenant operation and maintenance management method provided in this application embodiment Figure 4 ;

[0067] Figure 17 Another multi-tenant operation and maintenance management method provided in this application embodiment Figure 3 ;

[0068] Figure 18 Another multi-tenant operation and maintenance management method provided in this embodiment of the application Figure 3 ;

[0069] Figure 19 Another multi-tenant operation and maintenance management method provided in this embodiment of the application Figure 4 ;

[0070] Figure 20 A schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0071] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship. For example, A / B can represent A or B; "and / or" in the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. At the same time, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way for easy understanding.

[0072] In addition, the business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Persons skilled in the art will appreciate that, as new business scenarios emerge, the technical solutions provided by the embodiments of this application will also be applicable to similar technical problems. The following first describes a business scenario in the embodiments of this application.

[0073] With the increasing popularity of 5G networks, more and more companies are deploying them to improve work efficiency. When deploying and using 5G networks, companies face the challenge of managing and operating these networks. Specifically, network operations and management encompass the following four aspects: planning, construction, maintenance, and optimization:

[0074] "Plan" the network, that is, plan the network topology and parameters;

[0075] "Build" the network, that is, deploy network equipment and configure the network;

[0076] "Maintain" the network, that is, maintain network performance and troubleshoot network failures;

[0077] "Optimize" the network: that is, optimize the network configuration.

[0078] Because network operations and maintenance involve a wide range of areas and require high technical expertise, they require specialized personnel. Most companies lack the skills and experience to manage network operations and maintenance, and lack the resources to train specialized personnel. Therefore, they choose to outsource these services to carriers. In other words, these companies act as tenants, leasing the carriers' O&M resources.

[0079] It should be noted that the aforementioned "company" or "tenant" can be a business-to-business (2B) vertical industry, i.e., an enterprise with clear downstream customers in the supply chain, where the downstream customers are businesses. For example, a 2B vertical industry can be a steel mill or a metal processing plant.

[0080] In existing technologies, operators usually use ONAP to implement operation and maintenance management of 5G networks. Figure 1 The structure of ONAP is shown in Figure 1. ONAP consists of a design framework and an operational framework. The design framework is used to design the platform's business logic. After the design is completed, the operational framework executes the business logic designed in the design framework.

[0081] The design-state framework includes service design and creation (SDC), while the operational-state framework includes service orchestration (SO), configuration database (ConfigDB), active and available inventory (A&AI), data movement as a platform (DMaap), common controller software development kit / controller design studio (CCSDK / CDS), data collection, analytics and events (DCAE), multi-virtualized infrastructure manager (Multi-VIM), virtual function controller (VF-C), and application controller (APP-C). The functions of each module are described below:

[0082] SDC is used by operators' operation and maintenance personnel to design the business logic of the platform, such as design result testing and verification, resource confirmation and other processes.

[0083] SO is used to orchestrate operation and maintenance services. SO can implement flow operations through models from SDC, where the model includes information and resource descriptions of multiple virtual network functions (VNFs).

[0084] ConfigDB is used to store network configuration information data in the running framework.

[0085] A&AI is used to form an inventory resource table for effective network resources. A&AI is also used to store mapping relationships between network resources.

[0086] DMaap is used to support data transmission between ONAP internal modules.

[0087] CCSDK / CDS can load blueprint files to call controllers to implement the O&M services described in the blueprint files. Users can also customize O&M services by designing their own blueprint files and uploading them to ONAP.

[0088] DCAE consists of multiple components that work together to collect, analyze, and generate network data.

[0089] Multi-VIM is used to manage virtual network facilities provided by different manufacturers, such as OpenStack and VMware.

[0090] VF-C is used to control VNF.

[0091] APP-C is used to control applications.

[0092] Although not shown, the runtime framework also includes a policy framework and an external application programming interface (API) framework. The policy framework is used to deploy and execute policies. The external API framework is used to define and describe the APIs between ONAP and external systems, primarily including ONAP's northbound interfaces to business support systems (BSS) or operations support systems (OSS). BSS or OSS can call common APIs with ONAP, allowing them to access ONAP resources and services without making significant modifications to the BSS or OSS.

[0093] Combined with the above business scenarios, such as Figure 2 As shown, Figure 1 The ONAP shown is no longer used only for the operation and maintenance management of the operator's 5G network, but is also used for the operation and maintenance management of the 5G networks of multiple tenants hosted by the operator. Among them, the element management system (EMS) is used to manage network elements in the 5G network of the operator or multiple tenants hosted by the operator. However, when the operator hosts the operation and maintenance services of multiple tenants, the following problems will arise:

[0094] Problem 1: Blueprint file name conflicts may occur

[0095] Multiple tenants may upload blueprint files with different contents for the same operation, resulting in duplicate blueprint file names, which may lead to operation conflicts and / or user privacy leaks.

[0096] For example, suppose Tenant A first uploads blueprint file A1 to ONAP. Tenant B later uploads blueprint file B1 with the same name as A1. In this case, B1 replaces A1. When Tenant A calls a blueprint file to perform an operation, it can only call blueprint file B1. This creates an operational conflict because both Tenant A and Tenant B can call blueprint file B1. Furthermore, Tenant A calls a blueprint file that doesn't belong to it, potentially leaking Tenant B's privacy.

[0097] Issue 2: Tenants may access and / or operate physical network function (PNF) resources that do not belong to them

[0098] In existing ONAP, since all network resources are owned by the operator, the PNF Plug and Play (PnP) process only transmits the PNF identity without defining the tenant to which the PNF belongs. The PNF PnP process is used to describe the process of PNF access to the network and instantiation and activation.

[0099] Only passing the PNF identifier in the PNF PnP process may cause tenants to access and / or operate PNF stock resources that do not belong to them. Assuming that tenant A can access and / or operate tenant B's PNF stock resources, then, on the one hand, tenant A and tenant B can operate on the same PNF stock resources, resulting in an operation conflict. On the other hand, tenant B's privacy may be leaked.

[0100] Problem 3: Tenants may access non-own O&M data

[0101] In the existing ONAP, since all operation and maintenance data belongs to the operator, when a tenant requests access to operation and maintenance data, ONAP cannot identify different tenants. As a result, tenants may access operation and maintenance data that does not belong to them, resulting in the privacy leakage of other tenants.

[0102] like Figure 3As shown, a communication system 30 is provided in an embodiment of the present application. The communication system 30 includes a first device 301 and a second device 302. The second device 302 is used to send a first file uploaded by a first tenant to the first device 301, and the first file is used to describe the operation and maintenance service provided to the first tenant. The first device 301 is used to receive the first file uploaded by the first tenant from the second device 302. The first device 301 is also used to determine that the name of the first file does not conflict with any file name in the file name set stored in the first device 301. The first device 301 is also used to store the name of the first file in the file name set. The specific implementation and technical effects of this solution will be described in detail in the subsequent method embodiments and will not be repeated here.

[0103] like Figure 4 As shown, another communication system 40 provided in an embodiment of the present application. The communication system 40 includes a first device 401, a second device 402, and a fifth device 403. The second device 402 is used to send a third message to the first device 401, the third message including the identifier of the first tenant and the identifier of the first network function, and the third message is used by the first tenant to request instantiation of the first network function. The first device 401 is used to receive the third message from the second device 402. The first device 401 is also used to determine that the identifier of the first network function is one of the identifiers of one or more network functions corresponding to the identifier of the first tenant stored in the first device 401. The first device 401 is also used to send a third message to the fifth device 403. The fifth device 403 is used to receive the third message from the first device 401. The specific implementation and technical effects of this solution will be described in detail in the subsequent method embodiments and will not be repeated here.

[0104] like Figure 5As shown, another communication system 50 provided in an embodiment of the present application. The communication system 50 includes a first device 501, a second device 502, and a fourth device 503. The second device 502 is used to send a fourth message to the first device 501, the fourth message including the identifier of the first tenant, and the fourth message is used by the first tenant to request to perform a first operation and maintenance operation. The first device 501 is used to receive the fourth message from the second device 502. The first device 501 is also used to send a fifth message to the fourth device 503, the fifth message including the identifier of the first tenant and a filtering condition parameter, and the fifth message is used to request the fourth device 503 to query the operation and maintenance service file of the first tenant that meets the filtering condition parameter. The fourth device 503 is used to receive the fifth message from the first device 501. The fourth device 503 is also used to send the operation and maintenance service file of the first tenant that meets the filtering condition parameter to the first device 501. The first device 501 is also used to receive the operation and maintenance service file of the first tenant that meets the filtering condition parameter from the fourth device 503. The first device 501 is further configured to determine whether the first operation and maintenance operation is an operation and maintenance operation that the first tenant is authorized to perform, as described in the operation and maintenance service file of the first tenant that meets the screening condition parameters. The first device 501 is further configured to execute the first operation and maintenance operation to obtain an execution result of the first operation and maintenance operation. The specific implementation and technical effects of this solution will be described in detail in subsequent method embodiments and are not further elaborated here.

[0105] Figure 6 The following is a schematic diagram showing the enhanced ONAP provided in the embodiment of the present application for operation and maintenance management of 5G networks of multiple tenants hosted by an operator. Figure 2 The diagram shown is a schematic diagram of the operation and maintenance management of the 5G network of multiple tenants hosted by the operator. Figure 6 The operating state framework also includes a tenant operation and maintenance collaboration module, which is used to manage tenants and provide operation and maintenance services for tenants. In addition, Figure 6 The enhanced A&AI in ONAP is also used to store tenant association information, such as the tenant's Internet Protocol (IP) address, the tenant's PNF inventory resources, the tenant's blueprint file name, etc.

[0106] For example, the above Figure 3 The first device 301, Figure 4 The first device 401 or Figure 5 The first device 501 in the example may be Figure 6 The tenant operation and maintenance collaboration module in the above Figure 4 The fifth device 403 in the embodiment may be Figure 6 In SO, the above Figure 5 The fourth device 503 in the embodiment may be Figure 6A&AI in the above Figure 3 The second device 302, Figure 4 The second device 402 or Figure 5 The second device 502 in the example can be at least one of an SDC, a BSS, an OSS, a virtual user (virtual identifier, VID), or a tenant virtual operation panel. The tenant virtual operation panel is a virtual operation panel located on the tenant side, for example, the tenant virtual operation panel is an operation panel of a computer in a control room of a steel mill.

[0107] Optionally, the relevant functions of the first device, the second device, the fifth device, or the fourth device in the embodiments of the present application can be implemented by a single device, or by multiple devices, or by one or more functional modules within a single device, and the embodiments of the present application do not specifically limit this. It is understood that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0108] For example, the related functions of the first device, the second device, the fifth device or the fourth device in the embodiment of the present application can be Figure 7 It is implemented by the communication device 700 in FIG.

[0109] Figure 7 FIG. 7 is a schematic diagram of the structure of a communication device 700 provided in an embodiment of the present application. The communication device 700 includes one or more processors 701, a communication line 702, and at least one communication interface ( Figure 7 The example in which the communication interface 704 and a processor 701 are included is merely exemplary), and a memory 703 may also be included optionally.

[0110] The processor 701 may be a CPU, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0111] The communication line 702 may include a path for connecting different components.

[0112] Communication interface 704 can be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), etc. For example, the transceiver module can be a device such as a transceiver or a transceiver. Optionally, communication interface 704 can also be a transceiver circuit located within processor 701 to implement signal input and output to the processor.

[0113] The memory 703 may be a device having a storage function. For example, it may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may be independent and connected to the processor via a communication line 702. The memory may also be integrated with the processor.

[0114] The memory 703 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 701. The processor 701 is used to execute the computer-executable instructions stored in the memory 703, thereby implementing the multi-tenant operation and maintenance management method provided in the embodiment of the present application.

[0115] Alternatively, in an embodiment of the present application, the processor 701 may also execute the processing-related functions in the multi-tenant operation and maintenance management method provided in the following embodiments of the present application, and the communication interface 704 is responsible for communicating with other devices or communication networks. The embodiment of the present application does not specifically limit this.

[0116] The computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0117] In a specific implementation, as an embodiment, the processor 701 may include one or more CPUs, such as Figure 7 CPU0 and CPU1 in.

[0118] In a specific implementation, as an embodiment, the communication device 700 may include multiple processors, such as Figure 7 701 and processor 707 in FIG. Each of these processors may be a single-CPU processor or a multi-CPU processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0119] In a specific implementation, as an embodiment, the communication apparatus 700 may further include an output device 705 and an input device 706. The output device 705 communicates with the processor 701 and may display information in a variety of ways.

[0120] The communication device 700 can be a general purpose device or a dedicated device. For example, the communication device 700 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a vehicle terminal device, an embedded device, or a computer with Figure 7 The embodiment of the present application does not limit the type of the communication device 700.

[0121] Combine Figure 3 The communication system shown, Figure 8 A flowchart of a multi-tenant operation and maintenance management method provided by an embodiment of the present application is shown. The multi-tenant operation and maintenance management method includes the following steps S801-S803:

[0122] S801: A first device receives a first file uploaded by a first tenant of a second device, where the first file is used to describe an operation and maintenance service provided to the first tenant.

[0123] For example, the first tenant may be a 2B vertical industry, such as a steel mill or a metal processing plant, etc., which are uniformly described here and will not be repeated below.

[0124] For example, the first device in the embodiment of the present application may be Figure 6 The tenant operation and maintenance collaboration module in .

[0125] For example, the second device in the embodiment of the present application may be Figure 6The SDC and / or tenant virtual operation panel in the operator's network can be used. That is, the first file can be sent to the first device by the tenant's operation and maintenance personnel via the tenant's virtual operation panel, or by the operator's operation and maintenance personnel via the SDC. The tenant virtual operation panel is a virtual operation panel located on the tenant side, for example, the operation panel of a computer in the control room of a steel plant. The SDC can be located in the operator's computer room.

[0126] Illustratively, the first file in the embodiment of the present application may be a blueprint file.

[0127] Optionally, in an embodiment of the present application, the first device may also receive an identifier of the first tenant from the second device. The identifier of the first tenant and the first file uploaded by the first tenant may be sent simultaneously by the second device to the first device, and this embodiment of the present application does not specifically limit this.

[0128] S802: The first device determines that the name of the first file does not conflict with any file name in the file name set stored in the first device.

[0129] Exemplarily, the set of file names stored in the first device may be a set of names of blueprint files uploaded to the first device before step S801.

[0130] S803: The first device stores the name of the first file in a file name set.

[0131] In an embodiment of the present application, the first device stores the name of the first file in the file name set, which can be understood as the first device updating the stored file name set to prepare for the next time the first tenant or other tenants upload a file.

[0132] Optionally, in an embodiment of the present application, when the first device determines that the name of the first file conflicts with one of the file names in the file name set stored in the first device, the first device may send a message to the second device prompting the first tenant to modify the name of the first file. This embodiment of the present application does not specifically limit this.

[0133] In the multi-tenant operation and maintenance management method provided in the embodiment of the present application, the first device will only continue to execute the multi-tenant operation and maintenance management method provided in the embodiment of the present application when the first device determines that the name of the first file does not conflict with any file name in the set of file names stored in the first device. Therefore, in response to the first problem of existing ONAP, the method provided in this embodiment can ensure that files uploaded by multiple tenants do not have the same name, and thus will not replace or overwrite each other, thereby avoiding operational conflicts and privacy leaks caused by duplicate name conflicts.

[0134] Optionally, in the embodiment of the present application, Figure 9 As shown, after the above step S803, the multi-tenant operation and maintenance management method provided in the embodiment of the present application may include the following steps S901-S903:

[0135] S901: A first device sends a second message to a third device, wherein the second message includes a first file and is used to request the third device to load the first file.

[0136] For example, the third device in the embodiment of the present application may be Figure 6 For example, CCSDK can load a blueprint file to implement the operation and maintenance services described in the blueprint file for the first tenant.

[0137] S902: The first device receives second indication information from the third device, where the second indication information is used to indicate success or failure in loading the first file.

[0138] In one possible implementation, the second indication information includes a success or failure indication, in which case the second indication information can be represented by one bit. For example, a bit value of "1" indicates that the first file was loaded successfully, and a bit value of "0" indicates that the first file was loaded unsuccessfully; or, for example, a bit value of "0" indicates that the first file was loaded successfully, and a bit value of "1" indicates that the first file was loaded unsuccessfully.

[0139] Optionally, in an embodiment of the present application, the second indication information may further include the name of the first file, which is not specifically limited in the embodiment of the present application.

[0140] Optionally, in an embodiment of the present application, when the second indication information is used to indicate a failure to load the first file, the second indication information may also be used to indicate a reason for the failure to load the first file, which is not specifically limited in this embodiment of the present application.

[0141] S903: The first device sends third indication information to the second device, where the third indication information is used to indicate whether the first tenant has successfully uploaded the first file or failed.

[0142] In one possible implementation, the third indication information includes a success or failure indication. In this case, the third indication information can be represented by one bit. For example, a bit value of "1" indicates that the first file upload is successful, and a bit value of "0" indicates that the first file upload fails; or, for example, a bit value of "0" indicates that the first file upload is successful, and a bit value of "1" indicates that the first file upload fails.

[0143] Optionally, in an embodiment of the present application, the third indication information may further include an identifier of the first tenant and the name of the first file, which is not specifically limited in this embodiment of the present application.

[0144] Optionally, in an embodiment of the present application, when the third indication information is used to indicate that the first tenant failed to upload the first file, the third indication information can also be used to indicate the reason for the failure to upload the first file, which is not specifically limited in this embodiment of the present application.

[0145] Through the above steps S901-S903, the first file can be loaded on the third device, so as to facilitate subsequent calling of the first file by other devices.

[0146] Optionally, in an embodiment of the present application, when the first device receives the identifier of the first tenant from the second device, such as Figure 10 As shown, after step S803, the multi-tenant operation and maintenance management method provided in the embodiment of the present application may further include the following steps S1001 and S1002:

[0147] S1001: A first device sends a first message to a fourth device, wherein the first message includes an identifier of a first tenant and a name of a first file, and the first message is used to request the fourth device to store a mapping relationship between the identifier of the first tenant and the name of the first file.

[0148] For example, the fourth device in the embodiment of the present application may be Figure 6 A&AI in.

[0149] S1002: The first device receives first indication information from the fourth device, where the first indication information is used to indicate whether the fourth device succeeds or fails in storing the mapping relationship between the identifier of the first tenant and the name of the first file.

[0150] In one possible implementation, the first indication information includes a success or failure indication, in which case the first indication information can be represented by one bit. For example, a bit value of "1" indicates that the fourth device successfully stores the mapping relationship between the first tenant's identifier and the name of the first file, and a bit value of "0" indicates that the fourth device fails to store the mapping relationship between the first tenant's identifier and the name of the first file; or, for example, a bit value of "0" indicates that the fourth device successfully stores the mapping relationship between the first tenant's identifier and the name of the first file, and a bit value of "1" indicates that the fourth device fails to store the mapping relationship between the first tenant's identifier and the name of the first file.

[0151] Optionally, in an embodiment of the present application, the first indication information may further include an identifier of the first tenant and a name of the first file, which is not specifically limited in this embodiment of the present application.

[0152] Optionally, in an embodiment of the present application, when the first indication information is used to indicate that the fourth device fails to store the mapping relationship between the identifier of the first tenant and the name of the first file, the first indication information can also be used to indicate the reason why the fourth device fails to store the mapping relationship between the identifier of the first tenant and the name of the first file. This embodiment of the present application does not specifically limit this.

[0153] Through the above steps S1001 and S1002, the mapping relationship between the identifier of the first tenant and the name of the first file can be stored on the fourth device to facilitate subsequent control of the permission to call the first file, that is, only the first tenant is allowed to call the first file, while other tenants cannot call the first file.

[0154] Combine Figure 4 The communication system shown, Figure 11 A flowchart of another multi-tenant operation and maintenance management method provided by an embodiment of the present application is shown. The multi-tenant operation and maintenance management method includes the following steps S1101-S1103:

[0155] S1101: A first device receives a third message from a second device, wherein the third message includes an identifier of a first tenant and an identifier of a first network function, and the third message is used by the first tenant to request instantiation of the first network function.

[0156] For example, the first device in the embodiment of the present application may be Figure 6 The tenant operation and maintenance collaboration module in .

[0157] For example, the second device in the embodiment of the present application may be Figure 6 At least one of the BSS, OSS, VID or tenant virtual operation panel.

[0158] Exemplarily, the network function in the embodiment of the present application may be a PNF.

[0159] S1102: The first device determines that the identifier of the first network function is one of the identifiers of one or more network functions corresponding to the identifier of the first tenant stored in the first device.

[0160] Optionally, in an embodiment of the present application, before step S1101, a mapping relationship between the identifier of the first tenant and the identifiers of one or more network functions is pre-stored in the first device.

[0161] In an embodiment of the present application, if the first device determines that the identifier of the first network function is one of the identifiers of one or more network functions corresponding to the identifier of the first tenant stored in the first device, the first device can continue to trigger the instantiation process of the first network function; if the first device determines that the identifier of the first network function is not any of the identifiers of one or more network functions corresponding to the identifier of the first tenant stored in the first device, the first device does not allow the first tenant to instantiate the first network function, that is, the following step S1103 is not executed at this time.

[0162] S1103. The first device sends a third message to the fifth device.

[0163] For example, the fifth device in the embodiment of the present application may be Figure 6 Specifically, the first device may call the instantiation interface of the SO to continue to trigger the instantiation process of the first network function.

[0164] In the multi-tenant operation and maintenance management method provided in the embodiment of the present application, the instantiation process of the first network function is triggered only when the first device determines that the identifier of the first network function is one of the identifiers of one or more network functions corresponding to the identifier of the first tenant stored in the first device. Therefore, in response to the second problem of the existing ONAP, the method provided in this embodiment can limit the permission to instantiate the first network function, thereby ensuring that tenants can only access and / or operate the existing network function resources belonging to them, thereby avoiding operational conflicts and privacy leaks.

[0165] Optionally, in an embodiment of the present application, before the above-mentioned step S1103, the multi-tenant operation and maintenance management method provided by the embodiment of the present application may also include: the first device determines that the IP address of the second device belongs to one of the one or more IP addresses corresponding to the identifier of the first tenant stored in the first device.

[0166] That is, in an embodiment of the present application, the first device can ensure that the second device belongs to the first tenant and is not a fake by determining that the IP address of the second device belongs to one of the one or more IP addresses corresponding to the identifier of the first tenant stored in the first device, so as to prevent malicious tampering of data or network attacks, thereby enhancing the security of the instantiated first network function.

[0167] Optionally, in the embodiment of the present application, Figure 12 As shown, before the above step S1101, the multi-tenant operation and maintenance management method provided in the embodiment of the present application may include the following steps S1201-S1203:

[0168] S1201: A first device receives a name of a first tenant from a second device.

[0169] For example, the second device in the embodiment of the present application may be Figure 6 The tenant virtual operation panel in .

[0170] For example, the first tenant may be a certain 2B vertical industry, and the name of the first tenant may be a certain steel plant or a certain metal processing plant, etc.

[0171] S1202: The first device generates an identifier of the first tenant according to the name of the first tenant.

[0172] In the embodiment of the present application, the identifier of the first tenant is used to uniquely identify the first tenant, that is, the name of the first tenant and the identifier of the first tenant are in a one-to-one correspondence, so as to facilitate subsequent operation permission control.

[0173] S1203: The first device stores a mapping relationship between the identifier of the first tenant and the IP address of the second device.

[0174] In one possible implementation, the first device may obtain the IP address of the second device by receiving a message from the second device, or the first device may receive the IP address of the second device sent by the second device, which is not limited in this embodiment of the present application.

[0175] Through the above steps S1201 to S1203, the first device may store the mapping relationship between the identifier of the first tenant and the IP address of the second device, to indicate that the second device belongs to the first tenant.

[0176] Combine Figure 5 The communication system shown, Figure 13 A flowchart of another multi-tenant operation and maintenance management method provided by an embodiment of the present application is shown. The multi-tenant operation and maintenance management method includes the following steps S1301-S1305:

[0177] S1301: A first device receives a fourth message from a second device, wherein the fourth message includes an identifier of a first tenant, and the fourth message is used by the first tenant to request execution of a first operation and maintenance operation.

[0178] For example, the first device in the embodiment of the present application may be Figure 6 The tenant operation and maintenance collaboration module in .

[0179] For example, the second device in the embodiment of the present application may be Figure 6 The tenant virtual operation panel in .

[0180] For example, the first operation in the embodiments of the present application may be creating a management object instance (MOI), obtaining MOI parameters, modifying MOI parameters, or deleting an MOI in configuration management. The first operation may also be accessing PM data in performance management (PM), which is not limited in the present application. The PM data is network performance data, such as network throughput, latency, etc.

[0181] Optionally, the fourth message in the embodiment of the present application also includes a screening condition parameter. Exemplarily, the screening condition parameter can be a pre-set keyword used to filter the operation and maintenance service files of the first tenant. In the embodiment of the present application, the operation and maintenance service files of the first tenant are used to describe the operation and maintenance operations that the first tenant has the authority to perform. S1302. The first device sends a fifth message to the fourth device. The fifth message includes the identifier of the first tenant and the screening condition parameter, and the fifth message is used to request the fourth device to query the operation and maintenance service files of the first tenant that meet the screening condition parameter.

[0182] For example, the fourth device in the embodiment of the present application may be Figure 6 A&AI in.

[0183] In a possible implementation, the screening condition parameter in the fifth message may be sent by the second device to the first device.

[0184] In another possible implementation, the screening condition parameter in the fifth message may also be generated by the first device according to the fourth message.

[0185] S1303: The first device receives an operation and maintenance service file of the first tenant that meets the screening condition parameters from the fourth device.

[0186] S1304: The first device determines that the first operation and maintenance operation is an operation and maintenance operation that the first tenant has the permission to perform, as described in the operation and maintenance service file of the first tenant that meets the screening condition parameters.

[0187] S1305: The first device performs a first operation and maintenance operation to obtain an execution result of the first operation and maintenance operation.

[0188] For example, when the first operation and maintenance operation is to create an MOI, the execution result of the first operation and maintenance operation may be the identifier and / or name of the created MOI. When the first operation and maintenance operation is to access first operation and maintenance data, the execution result of the first operation and maintenance operation may be the first operation and maintenance data.

[0189] In the multi-tenant operation and maintenance management method provided in the embodiment of the present application, the first device will only execute the first operation when it determines that the first operation and maintenance operation belongs to the operation and maintenance operation that the first tenant has the authority to perform as described in the operation and maintenance service file of the first tenant that meets the screening condition parameters. Therefore, the method provided by this embodiment can control the authority to perform the first operation. In response to the third problem of the existing ONAP, for example, when the first operation is to access operation and maintenance data, the method provided by this embodiment can control the access rights to the operation and maintenance data, thereby ensuring that tenants can only access their own operation and maintenance data, thereby avoiding the problem of privacy leakage.

[0190] Optionally, before step S1305, the multi-tenant operation and maintenance management method provided in the embodiment of the present application may further include:

[0191] The first device receives the name of the first file corresponding to the first tenant's identifier from the fourth device, and determines that the name of the second file invoked to perform the first operation is the name of the first file. Through this solution, the first device can control the permission to invoke the first file, thereby ensuring that the first tenant can only invoke their own files, further avoiding operational conflicts and privacy leaks.

[0192] Optionally, in the embodiment of the present application, before the first device receives the name of the first file corresponding to the identifier of the first tenant from the fourth device, the first device may execute Figure 8 Steps S801-S803 shown, and Figure 10 Steps S1001-S1002 are shown, so that the fourth device stores the mapping relationship between the identifier of the first tenant and the name of the first file.

[0193] Optionally, in the embodiment of the present application, Figure 14 As shown, before the above step S1301, the multi-tenant operation and maintenance management method provided in the embodiment of the present application may include the following steps S1401-S1404:

[0194] S1401: A first device receives a name of a first tenant and an operation and maintenance service file of the first tenant from a second device. The operation and maintenance service file of the first tenant is used to describe the operation and maintenance operations that the first tenant is authorized to perform.

[0195] S1402: The first device generates an identifier of the first tenant according to the name of the first tenant.

[0196] The relevant description of step S1402 can refer to the above step S1202 and will not be repeated here.

[0197] S1403: The first device sends a sixth message to the fourth device, wherein the sixth message is used to request the fourth device to store a mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant.

[0198] In one possible implementation, the sixth message includes the first tenant's identifier and the first tenant's operation and maintenance service file. Optionally, the sixth message also includes the first tenant's name and information describing the first tenant. The information describing the first tenant may, for example, include the first tenant's office address or emergency contact number.

[0199] S1404: The first device receives fourth indication information from the fourth device, where the fourth indication information is used to indicate whether the fourth device succeeds or fails in storing the mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant.

[0200] In one possible implementation, the fourth indication information includes a success or failure indication, in which case the fourth indication information can be represented by one bit. For example, a bit value of "1" indicates that the fourth device successfully stores the mapping relationship between the first tenant's identifier and the first tenant's operation and maintenance service file, and a bit value of "0" indicates that the fourth device fails to store the mapping relationship between the first tenant's identifier and the first tenant's operation and maintenance service file; or, for example, a bit value of "0" indicates that the fourth device successfully stores the mapping relationship between the first tenant's identifier and the first tenant's operation and maintenance service file, and a bit value of "1" indicates that the fourth device fails to store the mapping relationship between the first tenant's identifier and the first tenant's operation and maintenance service file.

[0201] Optionally, in the embodiment of the present application, the fourth indication information may further include an identifier of the first tenant, which is not specifically limited in the embodiment of the present application.

[0202] Optionally, in an embodiment of the present application, when the fourth indication information is used to indicate that the fourth device fails to store the mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant, the fourth indication information can also be used to indicate the reason for the failure of the fourth device to store the mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant. The embodiment of the present application does not make specific limitations on this.

[0203] Through the above steps S1401-S1404, the fourth device can store a mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant, wherein the operation and maintenance service file of the first tenant is used to describe the operation and maintenance operations that the first tenant has the authority to perform, thereby facilitating the subsequent control of the authority to perform the first operation. Optionally, in an embodiment of the present application, when the first operation and maintenance operation is to access the first operation and maintenance data, before step S1305, the multi-tenant operation and maintenance management method provided by the embodiment of the present application may also include: the first device receives the identifier of the first measurement task from the fourth device. Accordingly, the first device performs the first operation and maintenance operation to obtain the execution result of the first operation and maintenance operation (the above step S1305) includes: the first device performs the first operation and maintenance operation according to the identifier of the first measurement task to obtain the execution result of the first operation and maintenance operation.

[0204] Optionally, in an embodiment of the present application, the first device performs a first operation and maintenance operation based on the identifier of the first measurement task to obtain an execution result of the first operation and maintenance operation, including: the first device sends a seventh message to a sixth device. The seventh message includes a filtering condition parameter and the identifier of the first measurement task, and is used to request access to the first operation and maintenance data. The first device receives the first operation and maintenance data from the sixth device. The first operation and maintenance data is the execution result of the first operation and maintenance operation.

[0205] For example, the sixth device in the embodiment of the present application may be Figure 6 DCAE in.

[0206] For example, if the filtering condition parameter in step S1302 is set to "throughput data for the past two days," the first measurement task may be a task for measuring network throughput. The sixth device may first filter all measured throughput data based on the identifier of the task for measuring network throughput, and then filter "throughput data for the past two days" based on the filtering condition parameter "for the past two days" as the first operation and maintenance data. Alternatively, the sixth device may first filter data measured by all measurement tasks for the past two days based on the filtering condition parameter "for the past two days," and then filter "throughput data for the past two days" based on the identifier of the task for measuring network throughput as the first operation and maintenance data. This embodiment does not limit this.

[0207] Optionally, in an embodiment of the present application, after the first device performs the first operation and maintenance operation to obtain the execution result of the first operation and maintenance operation (the above-mentioned step S1305), the multi-tenant operation and maintenance management method provided by the embodiment of the present application may also include: the first device sends an eighth message to the fourth device. The eighth message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation. The first device receives fifth indication information from the fourth device. The fifth indication information is used to indicate whether the fourth device successfully or failed to store the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation.

[0208] In a possible implementation, the eighth message includes the identifier of the first tenant and the execution result of the first operation and maintenance operation.

[0209] In one possible implementation, the fifth indication information includes a success or failure indication, in which case the fifth indication information can be represented by one bit. For example, a bit value of "1" indicates that the fourth device successfully stores the mapping relationship between the first tenant's identifier and the execution result of the first operation and maintenance operation, and a bit value of "0" indicates that the fourth device fails to store the mapping relationship between the first tenant's identifier and the execution result of the first operation and maintenance operation; or, for example, a bit value of "0" indicates that the fourth device successfully stores the mapping relationship between the first tenant's identifier and the execution result of the first operation and maintenance operation, and a bit value of "1" indicates that the fourth device fails to store the mapping relationship between the first tenant's identifier and the execution result of the first operation and maintenance operation.

[0210] Optionally, in an embodiment of the present application, the fifth indication information may further include an identifier of the first tenant and / or an execution result of the first operation and maintenance operation, which is not specifically limited in this embodiment of the present application.

[0211] Optionally, in an embodiment of the present application, when the fifth indication information is used to indicate that the fourth device fails to store the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation, the fifth indication information can also be used to indicate the reason for the failure of the fourth device to store the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation. The embodiment of the present application does not make specific limitations on this.

[0212] Based on the above scheme, the fourth device can store the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation, so as to facilitate the subsequent control of the execution authority of the second operation and maintenance operation, wherein the second operation and maintenance operation can be, for example, accessing and / or operating the execution result of the first operation and maintenance operation.

[0213] Optionally, in an embodiment of the present application, after the first device performs the first operation and maintenance operation to obtain the execution result of the first operation and maintenance operation (the above-mentioned step S1305), the multi-tenant operation and maintenance management method provided by the embodiment of the present application may also include: the first device sends the execution result of the first operation and maintenance operation to the second device.

[0214] Among them, due to the above Figures 8 to 14 The first device in the embodiment described may be implemented as follows Figure 7 The architecture of the communication device 700 shown in FIG. 1 , therefore, the action of the first device in the above embodiment can be performed by Figure 7 The processor 701 in the communication apparatus 700 shown calls the application code stored in the memory 703 to instruct the first device to execute, and this embodiment does not impose any limitation on this.

[0215] The following will be combined Figure 6 The enhanced ONAP modules shown above Figures 8 to 14 The embodiments are described in detail.

[0216] In the embodiment of the present application, for the first tenant, it is necessary to first generate a unique identifier and store the mapping relationship between the identifier and the first tenant's IP address or operation and maintenance service file to facilitate subsequent multi-tenant operation and maintenance management. Figure 12 and Figure 14 The embodiments described, such as Figure 15 As shown, a multi-tenant operation and maintenance management method provided in an embodiment of the present application includes the following steps:

[0217] S1501: The tenant virtual operation panel sends a ninth message to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the ninth message from the tenant virtual operation panel, wherein the ninth message is used to request the creation of a tenant account.

[0218] In an embodiment of the present application, the ninth message may include the name of the first tenant and the operation and maintenance service file of the first tenant, wherein the operation and maintenance service file of the first tenant is used to describe the operation and maintenance operations that the first tenant is authorized to perform.

[0219] Optionally, in an embodiment of the present application, the ninth message also includes the IP address of the tenant virtual operation panel and / or information used to describe the first tenant.

[0220] For example, Figure 15 As shown, the name of the ninth message may be CreateTenantAccount request.

[0221] S1502: The tenant operation and maintenance collaboration module generates an identifier of the first tenant according to the name of the first tenant.

[0222] The relevant description of step S1502 can refer to the above step S1202 and will not be repeated here.

[0223] S1503. The tenant operation and maintenance collaboration module stores a mapping relationship between the identifier of the first tenant and the IP address of the tenant virtual operation panel.

[0224] The relevant description of step S1503 can refer to the above step S1203 and will not be repeated here.

[0225] S1504: The tenant operation and maintenance collaboration module sends a sixth message to A&AI, and A&AI receives the sixth message from the tenant operation and maintenance collaboration module. The sixth message is used to request A&AI to store a mapping relationship between the first tenant's identifier and the first tenant's operation and maintenance service file.

[0226] Among them, the relevant description of the sixth message can be referred to Figure 14 The embodiments described above will not be described in detail here.

[0227] For example, Figure 15 As shown, the name of the sixth message may be a save tenant account information request (SaveTenantAccountInfo request).

[0228] S1505. A&AI stores a mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant.

[0229] Optionally, if the above-mentioned sixth message also includes the name of the first tenant and information used to describe the first tenant, A&AI can also store the mapping relationship between the identifier of the first tenant, the operation and maintenance service files of the first tenant, and the name of the first tenant and the information used to describe the first tenant.

[0230] S1506. A&AI sends fourth indication information to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the fourth indication information from A&AI.

[0231] The description of the fourth instruction information can be found in Figure 14 The embodiments described above will not be described in detail here.

[0232] For example, Figure 15 As shown, the fourth indication information can be carried by the storage tenant account information response (SaveTenantAccountInfo response) sent by A&AI to the tenant operation and maintenance collaboration module.

[0233] S1507: The tenant operation and maintenance collaboration module sends sixth indication information to the tenant virtual operation panel, and the tenant virtual operation panel receives the sixth indication information from the tenant operation and maintenance collaboration module, wherein the sixth indication information is used to indicate whether the tenant account creation is successful or failed.

[0234] In one possible implementation, the sixth indication information includes a success or failure indication. In this case, the sixth indication information can be represented by one bit. For example, a bit value of "1" indicates that the tenant account creation is successful, and a bit value of "0" indicates that the tenant account creation fails; or, for example, a bit value of "0" indicates that the tenant account creation is successful, and a bit value of "1" indicates that the tenant account creation fails.

[0235] Optionally, in the embodiment of the present application, the sixth indication information may further include an identifier of the first tenant, which is not specifically limited in the embodiment of the present application.

[0236] Optionally, in an embodiment of the present application, when the sixth indication information is used to indicate a failure in creating a tenant account, the sixth indication information may also be used to indicate a reason for the failure in creating the tenant account, which is not specifically limited in this embodiment of the present application.

[0237] For example, Figure 15 As shown, the sixth indication information may be carried in a CreateTenantAccount response sent by the tenant operation and maintenance collaboration module to the tenant virtual operation panel.

[0238] Based on the above solution, on the one hand, the tenant operation and maintenance collaboration module can store the mapping relationship between the first tenant's identifier and the IP address of the tenant's virtual operation panel to indicate that the tenant's virtual operation panel belongs to the first tenant. On the other hand, the A&AI can store the mapping relationship between the first tenant's identifier and the first tenant's operation and maintenance service file, where the first tenant's operation and maintenance service file is used to describe the operation and maintenance operations that the first tenant is authorized to perform, thereby facilitating the subsequent control of the permission to perform the first operation.

[0239] Combine Figure 3 The communication system 30 shown in FIG. 30 takes the first device 301 as the tenant operation and maintenance collaboration module and the second device 302 as the tenant virtual operation panel and / or SDC as an example. Figure 8 、 Figure 9 and Figure 10 The embodiments described, such as Figure 16 As shown, a multi-tenant operation and maintenance management method provided in an embodiment of the present application includes the following steps:

[0240] S1601a: The tenant virtual operation panel sends a tenth message to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the tenth message from the tenant virtual operation panel. The tenth message is used by the first tenant to request to upload the first file.

[0241] In the embodiment of the present application, the tenth message includes the identifier of the first tenant and the first file. For example, the first file in the embodiment of the present application may be a blueprint file, such as Figure 16 As shown, the name of the tenth message may be DistributeBlueprintFile request.

[0242] S1601b. The SDC sends the tenth message to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the tenth message from the SDC.

[0243] As described above, since the blueprint file can be sent to the tenant operation and maintenance collaboration module through the above-mentioned step S1601a and / or step S1601b, only step S1601a can be executed without executing step S1601b, or only step S1601b can be executed without executing step S1601a, or step S1601a can be executed first and then step S1601b, or step S1601b can be executed first and then step S1601a, or step S1601a and step S1601b can be executed at the same time. The embodiment of the present application does not limit this.

[0244] S1602: The tenant operation and maintenance collaboration module determines that the name of the blueprint file does not conflict with any file name in the file name set stored in the tenant operation and maintenance collaboration module.

[0245] The relevant description of step S1602 can refer to the above step S802 and will not be repeated here.

[0246] S1603. The tenant operation and maintenance collaboration module stores the name of the blueprint file in the file name set.

[0247] The relevant description of step S1603 can refer to the above step S803 and will not be repeated here.

[0248] S1604. The tenant operation and maintenance collaboration module sends a second message to CCSDK, and CCSDK receives the second message from the tenant operation and maintenance collaboration module.

[0249] The relevant description of the second message can be found in Figure 9 The embodiments described above will not be described in detail here.

[0250] For example, Figure 16 As shown, the name of the second message may be DistributeBlueprintFile request.

[0251] S1605. CCSDK loads the blueprint file.

[0252] S1606. CCSDK sends second indication information to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the second indication information from CCSDK.

[0253] The relevant description of the second indication information can be found in Figure 9 The embodiments described above will not be described in detail here.

[0254] For example, Figure 16 As shown, the second indication information can be carried by the upload blueprint file response (DistributeBlueprintFile response) sent by CCSDK to the tenant operation and maintenance collaboration module.

[0255] S1607a: The tenant operation and maintenance collaboration module sends third indication information to the tenant virtual operation panel, and the tenant virtual operation panel receives the third indication information from the tenant operation and maintenance collaboration module, wherein the third indication information is used to indicate whether the first tenant successfully uploads the first file or fails.

[0256] The description of the third instruction information can be found in Figure 9 The embodiments described above will not be described in detail here.

[0257] For example, Figure 16 As shown, the third indication information can be carried in the upload blueprint file response (DistributeBlueprintFile response) sent by the tenant operation and maintenance collaboration module to the tenant virtual operation panel.

[0258] S1607b. The tenant operation and maintenance collaboration module sends third indication information to the SDC, and the SDC receives the third indication information from the tenant operation and maintenance collaboration module.

[0259] For example, Figure 16 As shown, the third indication information can also be carried in the upload blueprint file response (DistributeBlueprintFile response) sent by the tenant operation and maintenance collaboration module to the SDC.

[0260] In the embodiment of the present application, if step S1601a is executed, then step S1607a is also executed; if step S1601a is not executed, then step S1607a is not executed. If step S1601b is executed, then step S1607b is also executed; if step S1601b is not executed, then step S1607b is not executed.

[0261] S1608. The tenant operation and maintenance collaboration module sends a first message to A&AI, and A&AI receives the first message from the tenant operation and maintenance collaboration module.

[0262] The description of the first message can be found in Figure 10 The embodiments described above will not be described in detail here.

[0263] For example, Figure 16 As shown, the name of the first message may be a name request for storing a blueprint file (SaveBlueprintName request).

[0264] S1609. A&AI stores the mapping relationship between the first tenant's identifier and the name of the blueprint file.

[0265] S1610. A&AI sends first indication information to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the first indication information from A&AI.

[0266] The description of the first indication information can be found in Figure 10 The embodiments described above will not be described in detail here.

[0267] For example, Figure 16 As shown, the first indication information can be carried by the name response (SaveBlueprintName response) of the storage blueprint file sent by A&AI to the tenant operation and maintenance collaboration module.

[0268] Based on the above solution, on the one hand, the tenant operation and maintenance collaboration module will only continue to execute this solution when it determines that the name of the blueprint file does not conflict with any file name in the file name set stored in the tenant operation and maintenance collaboration module. Therefore, this solution can ensure that files uploaded by multiple tenants do not have the same name, and thus will not replace or overwrite each other, thereby avoiding operational conflicts and privacy leaks caused by duplicate name conflicts. On the other hand, it can enable A&AI to store the mapping relationship between the first tenant's identifier and the name of the blueprint file, so as to facilitate the subsequent control of the permission to call the blueprint file, that is, only the first tenant is allowed to call the blueprint file, while other tenants cannot call the blueprint file.

[0269] Combine Figure 4 The communication system 40 shown in FIG. 4 is a first device 401 as a tenant operation and maintenance collaboration module, a second device 402 as a BSS, OSS, VID, or a tenant virtual operation panel, a fifth device 403 as an SO, and a first network function as a PNF. Figure 11 and Figure 12 The embodiments described, such as Figure 17 As shown, a multi-tenant operation and maintenance management method provided in an embodiment of the present application includes the following steps:

[0270] S1701: BSS, OSS, VID or tenant virtual operation panel sends a third message to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the third message from BSS, OSS, VID or tenant virtual operation panel.

[0271] The description of the third message can be found in Figure 11 The embodiments described above will not be described in detail here.

[0272] For example, Figure 17 As shown, the name of the third message may be PNF Instantiation.

[0273] S1702. The tenant operation and maintenance collaboration module determines that the identifier of the PNF is one of the identifiers of one or more PNFs corresponding to the identifier of the first tenant stored in the tenant operation and maintenance module.

[0274] The relevant description of step S1702 can refer to the above step S1102 and will not be repeated here.

[0275] S1703: The tenant operation and maintenance collaboration module determines that the BSS, OSS, VID, or IP address of the tenant virtual operation panel belongs to one of the one or more IP addresses corresponding to the identifier of the first tenant stored in the tenant operation and maintenance module.

[0276] The relevant description of step S1702 can be found in Figure 11 The embodiments described above will not be described in detail here.

[0277] Optionally, in order to be able to execute step S1703, before step S1701, the first device can store the mapping relationship between the first tenant's identifier and the BSS, OSS, VID or IP address of the tenant's virtual operation panel by pre-executing the above steps S1201-S1203. For detailed description, please refer to the above steps S1201-S1203.

[0278] S1704. The tenant operation and maintenance collaboration module sends a third message to the SO, and the SO receives the third message from the tenant operation and maintenance collaboration module.

[0279] S1705. SO starts a thread controlled by resource level flow (RLF).

[0280] In the embodiment of the present application, the thread is used to perform operations related to A&AI records.

[0281] S1706: SO sends the eleventh message to A&AI, and A&AI receives the eleventh message from SO. The eleventh message is used by SO to query whether the PNF identifier exists in the record of A&AI.

[0282] In the embodiment of the present application, the eleventh message includes an identifier of the PNF. For example, the name of the eleventh message may be Check A&AI Entry.

[0283] If the SO query finds that there is no PNF identifier in the A&AI record, the following step S1707 is executed:

[0284] S1707: The SO sends a twelfth message to the A&AI, and the A&AI receives the twelfth message from the SO. The twelfth message is used by the SO to create a record of the PNF identifier and the first tenant identifier in the A&AI.

[0285] In an embodiment of the present application, the twelfth message includes the PNF identifier and the first tenant identifier. Exemplarily, the name of the twelfth message may be Create A&AI Entry with TenantID&PNF ID using the PNF identifier and the first tenant identifier.

[0286] S1708. SO subscribes to virtual event streaming (VES) events.

[0287] In an embodiment of the present application, SO can subscribe to the VES event "PNF Ready". When a record of the PNF identifier and the first tenant identifier is created in A&AI, SO will be notified that the PNF record is completed.

[0288] Based on the above scheme, when the tenant operation and maintenance collaboration module determines that the PNF identifier is one of the identifiers of one or more PNFs stored in the tenant operation and maintenance collaboration module corresponding to the identifier of the first tenant, the PNF instantiation process will be triggered. Therefore, this scheme can limit the authority to instantiate PNF, thereby ensuring that tenants only access and / or operate their own PNF stock resources, thereby avoiding operation conflicts and privacy leaks.

[0289] Furthermore, in the above solution, on the one hand, the tenant operation and maintenance collaboration module determines that the IP address of the BSS, OSS, VID, or tenant virtual operation panel belongs to one of the one or more IP addresses corresponding to the identifier of the first tenant stored in the tenant operation and maintenance module to ensure that the BSS, OSS, VID, or tenant virtual operation panel belongs to the first tenant and is not a fake, so as to prevent malicious tampering with data or network attacks, thereby enhancing the security of the instantiated PNF. On the other hand, the tenant operation and maintenance collaboration module can store the mapping relationship between the identifier of the first tenant and the BSS, OSS, VID, or IP address of the tenant virtual operation panel to indicate that the BSS, OSS, VID, or tenant virtual operation panel belongs to the first tenant.

[0290] Combine Figure 5 The communication system 50 shown in FIG. 5 is a first device 501 as a tenant operation and maintenance collaboration module, a second device 502 as a tenant virtual operation panel, a fourth device 503 as A&AI, and the first operation is to create an MOI. Figure 13 and Figure 14 The embodiments described, such as Figure 18 As shown, a multi-tenant operation and maintenance management method provided in an embodiment of the present application includes the following steps:

[0291] S1801: The tenant virtual operation panel sends a fourth message to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the fourth message from the tenant virtual operation panel. The fourth message includes the identifier of the first tenant and is used by the first tenant to request the creation of an MOI.

[0292] Optionally, the fourth message also includes at least one of a managed object class (ManagedObjectClass), a managed object instance (ManagedObjectInstance), a reference object instance (ReferenceObjectInstance) or an input parameter list (AttributeListIn). The above parameters are used to provide the required information for creating an MOI. The specific meanings of the above parameters can be referred to the existing technology and will not be repeated here.

[0293] For example, Figure 18As shown, the name of the fourth message may be CreateMOIrequest.

[0294] S1802. The tenant operation and maintenance collaboration module sends a fifth message to A&AI, and A&AI receives the fifth message from the tenant operation and maintenance collaboration module.

[0295] Among them, the relevant description of the fifth message can be referred to Figure 13 The embodiments described above will not be described in detail here.

[0296] For example, Figure 18 As shown, the name of the fifth message may be a query tenant information request (QueryTenantInfo request).

[0297] S1803: A&AI sends a thirteenth message to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the thirteenth message from A&AI. The thirteenth message is used by A&AI to feedback the operation and maintenance service file of the first tenant that meets the screening condition parameters.

[0298] In an embodiment of the present application, the thirteenth message includes the operation and maintenance service file of the first tenant that meets the screening condition parameters.

[0299] Optionally, the thirteenth message also includes the name of the blueprint file.

[0300] For example, Figure 18 As shown, the name of the thirteenth message may be a query tenant information response (QueryTenantInfo response).

[0301] Optionally, to enable execution of step S1803, before step S1801, the tenant operation and maintenance collaboration module may pre-execute steps S1401-S1404 above, so that A&AI stores the mapping relationship between the first tenant's identifier and the first tenant's operation and maintenance service file, thereby facilitating subsequent control of the MOI creation authority. For detailed descriptions, please refer to steps S1401-S1404 above.

[0302] Optionally, in order to be able to execute step S1803, before step S1801, the tenant operation and maintenance collaboration module can pre-execute the above steps S801-S803 and steps S1001-S1002 so that A&AI stores the mapping relationship between the identifier of the first tenant and the name of the blueprint file. For detailed description, please refer to the above steps S801-S803 and steps S1001-S1002.

[0303] S1804: The tenant operation and maintenance collaboration module determines that the created MOI belongs to an operation and maintenance operation that the first tenant has the authority to perform as described in the operation and maintenance service file of the first tenant that meets the screening condition parameters.

[0304] S1805. The tenant operation and maintenance collaboration module determines that the name of the second file called to perform the first operation and maintenance operation is the name of the blueprint file.

[0305] S1806: The tenant operation and maintenance collaboration module sends a fourteenth message to the SO, and the SO receives the fourteenth message from the tenant operation and maintenance collaboration module, wherein the fourteenth message is used to request the creation of an MOI.

[0306] In an embodiment of the present application, the fourteenth message includes at least one of ManagedObjectClass, ManagedObjectInstance, ReferenceObjectInstance or AttributeListIn.

[0307] Exemplarily, the name of the fourteenth message may be Create MOI Request.

[0308] S1807. The SO sends the fourteenth message to the CCSDK or CDS, and the CCSDK or CDS receives the fourteenth message from the SO.

[0309] S1808, CCSDK, or CDS loads the blueprint file to create the MOI.

[0310] S1809. CCSDK or CDS sends the fourteenth message to PNF or EMS, and PNF or EMS receives the fourteenth message from CCSDK or CDS.

[0311] S1810, PNF, or EMS creates an MOI.

[0312] S1811: The PNF or EMS sends seventh indication information to the CCSDK or CDS, and the CCSDK or CDS receives the seventh indication information from the PNF or EMS, wherein the seventh indication information is used to indicate whether the PNF or EMS succeeds or fails in creating the MOI.

[0313] In one possible implementation, the seventh indication information includes a success or failure indication. In this case, the seventh indication information may be represented by one bit. For example, a bit value of "1" indicates that the PNF or EMS successfully created the MOI, and a bit value of "0" indicates that the PNF or EMS failed to create the MOI; or, for example, a bit value of "0" indicates that the PNF or EMS successfully created the MOI, and a bit value of "1" indicates that the PNF or EMS failed to create the MOI.

[0314] Optionally, in an embodiment of the present application, the seventh indication information may further include an output parameter list attributeListOut, wherein attributeListOut is used to describe information of the created MOI. For example, attributeListOut may include the identifier of the MOI and the name of the MOI, etc. The specific meaning of attributeListOut can be referred to the prior art and will not be repeated here.

[0315] Optionally, in an embodiment of the present application, when the seventh indication information is used to indicate that the PNF or EMS fails to create the MOI, the seventh indication information can also be used to indicate the reason why the PNF or EMS fails to create the MOI. This embodiment of the present application does not specifically limit this.

[0316] For example, Figure 18 As shown, the seventh indication information can be carried by creating an MOI response (CreateMOIresponse).

[0317] S1812. CCSDK or CDS sends seventh indication information to SO, and SO receives the seventh indication information from CCSDK or CDS.

[0318] S1813. The SO sends the seventh indication information to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the seventh indication information from the SO.

[0319] S1814. The tenant operation and maintenance collaboration module sends seventh instruction information to the tenant virtual operation panel, and the tenant virtual operation panel receives the seventh instruction information from the tenant operation and maintenance collaboration module.

[0320] S1815: The tenant operation and maintenance collaboration module sends an eighth message to A&AI, and A&AI receives the eighth message from the tenant operation and maintenance collaboration module, wherein the eighth message is used to request A&AI to store the mapping relationship between the identifier of the first tenant and the execution result of creating the MIO.

[0321] In a possible implementation, the eighth message includes the identifier of the first tenant and the execution result of creating the MIO. The execution result of creating the MIO may be information describing the created MOI, such as the identifier and name of the MOI.

[0322] For example, Figure 18 As shown, the name of the eighth message may be SaveTenantMOIinfo request.

[0323] S1816. A&AI stores the mapping relationship between the identifier of the first tenant and the created MOI information.

[0324] S1817. A&AI sends the fifth indication information to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the fifth indication information from A&AI.

[0325] The description of the fifth indication information can be found in Figure 13 The embodiments described above will not be described in detail here.

[0326] For example, Figure 18 As shown, the fifth indication information can be carried by the storage tenant MOI information response (SaveTenantMOIinfo response) sent by A&AI to the tenant operation and maintenance collaboration module.

[0327] Based on the above solution, the tenant operation and maintenance collaboration module will only execute the MOI creation operation if it determines that the MOI creation operation is an operation and maintenance operation that the first tenant has permission to perform as described in the first tenant's operation and maintenance service file that meets the screening condition parameters. Therefore, this solution can control the permission to create MOIs.

[0328] Furthermore, on the one hand, the A&AI can store a mapping between the first tenant's identifier and the created MOI information, thereby facilitating subsequent control over the execution permissions of a second operation, such as obtaining or modifying the created MOI information. On the other hand, by determining that the name of the second file invoked to execute the first operation is the name of the blueprint file, the tenant operation collaboration module can control the permissions for invoking the blueprint file, ensuring that the first tenant can only invoke its own files, further avoiding operational conflicts and privacy leaks.

[0329] Combine Figure 5 The system shown in the figure takes the first device as the tenant operation and maintenance collaboration module, the second device as the tenant virtual operation panel, the fourth device as A&AI, and the first operation as accessing PM data as an example. Figure 13 and Figure 14 The embodiments described, such as Figure 19 As shown, a multi-tenant operation and maintenance management method provided in an embodiment of the present application includes the following steps:

[0330] S1901: The tenant virtual operation panel sends a fourth message to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the fourth message from the tenant virtual operation panel. The fourth message is used by the first tenant to request access to PM data.

[0331] In this embodiment of the present application, the fourth message includes the identifier of the first tenant and a screening condition parameter.

[0332] For example, Figure 19As shown, the name of the fourth message may be GetTenantPMdata request.

[0333] S1902. The tenant operation and maintenance collaboration module sends a fifth message to A&AI, and A&AI receives the fifth message from the tenant operation and maintenance collaboration module.

[0334] Among them, the relevant description of the fifth message can be referred to Figure 13 The embodiments described above will not be described in detail here.

[0335] For example, Figure 19 As shown, the name of the fifth message can be GetTenantPMjobInfo request. Figure 13 An example of the first measurement task in the described embodiment.

[0336] S1903: A&AI sends a fifteenth message to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the fifteenth message from A&AI. The fifteenth message is used by A&AI to feedback the identifier of the first measurement task.

[0337] In the embodiment of the present application, the fifteenth message includes the operation and maintenance service file of the first tenant that meets the screening condition parameters and the identifier of the first measurement task.

[0338] For example, Figure 19 As shown, the name of the fifteenth message may be Get TenantPMjobInfo response (GetTenantPMjobInfo response).

[0339] In one possible implementation, to enable step S1903, the tenant operation and maintenance collaboration module may pre-execute steps S1401-S1404 before step S1901, so that A&AI stores the mapping between the first tenant's identifier and the first tenant's operation and maintenance service file, thereby facilitating subsequent control of access permissions to PM data. For detailed descriptions, please refer to steps S1401-S1404.

[0340] S1904. The tenant operation and maintenance collaboration module determines that the access to the PM data MOI belongs to an operation and maintenance operation that the first tenant has the authority to perform as described in the operation and maintenance service file of the first tenant that meets the screening condition parameters.

[0341] S1905. The tenant operation and maintenance collaboration module sends the seventh message to DCAE, and DCAE receives the seventh message from the tenant operation and maintenance collaboration module.

[0342] Among them, the relevant description of the seventh message can be referred to Figure 13The embodiments described above will not be described in detail here.

[0343] For example, Figure 19 As shown, the name of the seventh message may be GetTenantPMdata request.

[0344] The description of step S1905 can be found in Figure 13 The embodiments described above will not be described in detail here.

[0345] S1906. DCAE queries PM data.

[0346] The description of step S1906 can be found in Figure 13 The embodiments described above will not be described in detail here.

[0347] S1907: DCAE sends the sixteenth message to the tenant operation and maintenance collaboration module, and the tenant operation and maintenance collaboration module receives the sixteenth message from DCAE. The sixteenth message is used by DCAE to feedback the PM data it has queried.

[0348] In an embodiment of the present application, the sixteenth message includes PM data.

[0349] For example, Figure 19 As shown, the name of the sixteenth message may be GetTenantPMdata response.

[0350] S1908: The tenant operation and maintenance collaboration module sends the seventeenth message to the tenant virtual operation panel, and the tenant virtual operation panel receives the seventeenth message from the tenant operation and maintenance collaboration module. The seventeenth message is used to feed back PM data to the tenant virtual operation panel.

[0351] In this embodiment of the present application, the seventeenth message includes PM data.

[0352] Optionally, the seventeenth message further includes an identifier of the first tenant.

[0353] For example, Figure 19 As shown, the name of the seventeenth message may be GetTenantPMdata response.

[0354] Based on the above solution, the tenant operation and maintenance collaboration module will only continue to execute the operation of accessing PM data when it determines that the operation of accessing PM data belongs to the operation and maintenance operation that the first tenant has the authority to perform as described in the operation and maintenance service file of the first tenant that meets the filtering condition parameters. Therefore, this solution can control the access rights to the operation and maintenance data, thereby ensuring that tenants can only access their own operation and maintenance data, thereby avoiding privacy leakage problems.

[0355] It can be understood that in the above embodiments, the methods and / or steps implemented by the first device can also be implemented by components (such as chips or circuits) that can be used for the first device or a device that includes the first device.

[0356] It is understandable that, in order to implement the above functions, the first device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0357] The embodiment of the present application can divide the functional modules of the first device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0358] For example, the first device, the second device, the fifth device or the fourth device in the embodiment of the present application can all adopt Figure 20 The communication device 200 shown in FIG. 2 includes a transceiver module 201, a processing module 202, and a storage module 203. The transceiver module 201, which may also be referred to as a transceiver unit, is used to implement transceiver functions, and may be, for example, a transceiver circuit, a transceiver, a transceiver, or a communication interface.

[0359] Taking the communication device 200 as the first device in the above method embodiment as an example, then:

[0360] The transceiver module 201 is used to receive a first file uploaded by a first tenant from a second device, where the first file is used to describe the operation and maintenance services provided to the first tenant; the processing module 202 is used to determine that the name of the first file does not conflict with any file name in the file name set stored in the communication device; the storage module 203 is used to store the name of the first file in the file name set.

[0361] In one possible implementation, the transceiver module 201 is also used to: receive the identifier of the first tenant from the second device; send a first message to the fourth device, the first message including the identifier of the first tenant and the name of the first file, and the first message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the name of the first file; receive first indication information from the fourth device, and the first indication information is used to indicate whether the fourth device succeeds or fails in storing the mapping relationship between the identifier of the first tenant and the name of the first file.

[0362] In one possible implementation, the transceiver module 201 is also used to: send a second message to a third device, the second message includes the first file, and the second message is used to request the third device to load the first file; receive second indication information from the third device, the second indication information is used to indicate the success or failure of loading the first file; send third indication information to the second device, and the third indication information is used to indicate the success or failure of the first tenant uploading the first file.

[0363] The transceiver module 201 is used to receive a third message from the second device, where the third message includes the identifier of the first tenant and the identifier of the first network function, and the third message is used by the first tenant to request instantiation of the first network function; the processing module 202 is used to determine that the identifier of the first network function is one of the identifiers of one or more network functions corresponding to the identifier of the first tenant stored in the communication device; the transceiver module 201 is also used to send the third message to the fifth device.

[0364] In a possible implementation, the processing module 202 is further configured to determine that the IP address of the second device belongs to one of the one or more IP addresses corresponding to the identifier of the first tenant stored in the communication apparatus.

[0365] In one possible implementation, the transceiver module 201 is also used to receive the name of the first tenant from the second device; the processing module 202 is also used to generate the identifier of the first tenant based on the name of the first tenant; and the storage module 203 is used to store the mapping relationship between the identifier of the first tenant and the IP address of the second device.

[0366] The transceiver module 201 is used to receive a fourth message from the second device, the fourth message including the identifier of the first tenant, and the fourth message is used by the first tenant to request to perform a first operation and maintenance operation. The transceiver module 201 is also used to send a fifth message to the fourth device, the fifth message including the identifier of the first tenant and the filtering condition parameters, and the fifth message is used to request the fourth device to query the operation and maintenance service file of the first tenant that meets the filtering condition parameters. The transceiver module 201 is also used to receive the operation and maintenance service file of the first tenant that meets the filtering condition parameters from the fourth device. The processing module 202 is used to determine that the first operation and maintenance operation belongs to the operation and maintenance operation that the first tenant has the authority to perform as described in the operation and maintenance service file of the first tenant that meets the filtering condition parameters; the processing module 202 is also used to execute the first operation and maintenance operation to obtain the execution result of the first operation and maintenance operation.

[0367] In one possible implementation, the transceiver module 201 is also used to receive the name of the first file corresponding to the identifier of the first tenant from the fourth device; the processing module 202 is also used to determine that the name of the second file called to perform the first operation and maintenance operation is the name of the first file.

[0368] In one possible implementation, the transceiver module 201 is also used to receive a first file uploaded by a first tenant from a second device, where the first file is used to describe the operation and maintenance services provided to the first tenant; the processing module 202 is also used to determine that the name of the first file does not conflict with any file name in the file name set stored in the first device; and the storage module 203 is used to store the name of the first file in the file name set.

[0369] In one possible implementation, the transceiver module 201 is also used to: receive the identifier of the first tenant from the second device; send a first message to the fourth device, the first message including the identifier of the first tenant and the name of the first file, and the first message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the name of the first file; receive first indication information from the fourth device, and the first indication information is used to indicate whether the fourth device succeeds or fails in storing the mapping relationship between the identifier of the first tenant and the name of the first file.

[0370] In one possible implementation, the transceiver module 201 is also used to receive the name of the first tenant and the operation and maintenance service file of the first tenant from the second device, where the operation and maintenance service file of the first tenant is used to describe the operation and maintenance operations that the first tenant has the authority to perform; the processing module 202 is also used to generate an identifier of the first tenant based on the name of the first tenant; the transceiver module 201 is also used to send a sixth message to the fourth device, where the sixth message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant; the transceiver module 201 is also used to receive fourth indication information from the fourth device, where the fourth indication information is used to indicate whether the fourth device successfully or failed to store the mapping relationship between the identifier of the first tenant and the operation and maintenance service file of the first tenant.

[0371] In one possible implementation, when the first operation and maintenance operation is accessing first operation and maintenance data, the transceiver module 201 is further configured to receive an identifier of a first measurement task from the fourth device. The processing module 202 is further configured to execute the first operation and maintenance operation to obtain an execution result of the first operation and maintenance operation, including executing the first operation and maintenance operation according to the identifier of the first measurement task to obtain an execution result of the first operation and maintenance operation.

[0372] In one possible implementation, the processing module 202 is also used to execute the first operation and maintenance operation according to the identifier of the first measurement task to obtain the execution result of the first operation and maintenance operation, including: the transceiver module 201 is also used to send a seventh message to the sixth device, the seventh message includes the filtering condition parameters and the identifier of the first measurement task, and the seventh message is used to request access to the first operation and maintenance data; the transceiver module 201 is also used to receive the first operation and maintenance data from the sixth device, wherein the first operation and maintenance data is the execution result of the first operation and maintenance operation.

[0373] In one possible implementation, the transceiver module 201 is also used to: send an eighth message to the fourth device, where the eighth message is used to request the fourth device to store the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation; and receive fifth indication information from the fourth device, where the fifth indication information is used to indicate whether the fourth device successfully stores the mapping relationship between the identifier of the first tenant and the execution result of the first operation and maintenance operation.

[0374] In a possible implementation, the transceiver module 201 is further configured to send the execution result of the first operation and maintenance operation to the second device.

[0375] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0376] In this embodiment, the communication device 200 is presented in the form of various functional modules divided in an integrated manner. Here, "module" can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions.

[0377] When the communication device 200 is the first device in the above method embodiment, in a simple embodiment, those skilled in the art may imagine that the communication device 200 may be used Figure 7 The form of the communication device 700 is shown.

[0378] for example, Figure 7 The processor 701 or 707 in the communication device 700 shown can call the computer execution instructions stored in the memory 703 to enable the communication device 700 to execute the multi-tenant operation and maintenance management method in the above method embodiment. Figure 20 The function / implementation process of the processing module 202 can be achieved by Figure 7 The processor 701 or 707 in the communication device 700 is implemented by calling the computer execution instructions stored in the memory 703 . Figure 20 The function / implementation process of the transceiver module 201 can be achieved by Figure 7 This is implemented by the communication interface 704 shown in FIG.

[0379] Since the communication device 200 provided in this embodiment can execute the above-mentioned multi-tenant operation and maintenance management method, the technical effects that can be obtained can refer to the above-mentioned method embodiment and will not be repeated here.

[0380] It should be noted that one or more of the above modules or units can be implemented by software, hardware, or a combination of the two. When any of the above modules or units is implemented by software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method flow. The processor can be built into an SoC (system on chip) or an ASIC, or it can be an independent semiconductor chip. In addition to the core used to execute software instructions to perform calculations or processing within the processor, it can further include necessary hardware accelerators, such as a field programmable gate array (FPGA), a PLD (programmable logic device), or a logic circuit that implements dedicated logic operations.

[0381] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0382] Optionally, an embodiment of the present application further provides a chip system, comprising: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instruction in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the first device also includes a memory. Optionally, the chip system can be composed of a chip, or can include a chip and other discrete devices, which is not specifically limited in the embodiment of the present application.

[0383] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may 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 media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0384] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0385] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

Claims

1. A multi-tenant operation and maintenance management method, characterized in that: The method comprises: The first device receives a first file uploaded by a first tenant of the second device, where the first file is used to describe an operation and maintenance service provided to the first tenant; The first device determines that the name of the first file does not conflict with any file name in a file name set stored in the first device; the first device stores the name of the first file in the file name set; or The first device determines that the name of the first file conflicts with one of the file names in the file name set stored in the first device; the first device sends a message to the second device prompting the first tenant to modify the name of the first file.

2. The method according to claim 1, characterized in that The method further comprises: The first device receives the identifier of the first tenant from the second device; After the first device stores the name of the first file in the file name set, the method further includes: The first device sends a first message to a fourth device, where the first message includes an identifier of the first tenant and a name of the first file, and the first message is used to request the fourth device to store a mapping relationship between the identifier of the first tenant and the name of the first file; The first device receives first indication information from the fourth device, where the first indication information is used to indicate whether storage by the fourth device of a mapping relationship between the identifier of the first tenant and the name of the first file succeeds or fails.

3. The method according to claim 1, characterized in that After the first device stores the name of the first file in the file name set, the method further includes: The first device sends a second message to a third device, where the second message includes the first file and is used to request the third device to load the first file; The first device receives second indication information from the third device, where the second indication information is used to indicate success or failure in loading the first file; The first device sends third indication information to the second device, where the third indication information is used to indicate whether the first tenant succeeds or fails in uploading the first file.

4. A communication device, characterized in that: The communication device includes: a transceiver module, a processing module and a storage module; The transceiver module is configured to receive a first file uploaded by a first tenant of a second device, where the first file is used to describe an operation and maintenance service provided to the first tenant; The processing module is configured to determine that the name of the first file does not conflict with any file name in the file name set stored in the communication device; the storage module is configured to store the name of the first file in the file name set; or The processing module is used to determine that the name of the first file conflicts with one of the file names in the file name set stored in the communication device; the transceiver module is also used to send a message to the second device prompting the first tenant to modify the name of the first file.

5. The communication device according to claim 4, characterized in that The transceiver module is further used for: receiving an identifier of the first tenant from the second device; Sending a first message to a fourth device, where the first message includes an identifier of the first tenant and a name of the first file, and the first message is used to request the fourth device to store a mapping relationship between the identifier of the first tenant and the name of the first file; First indication information is received from the fourth device, where the first indication information is used to indicate whether the fourth device succeeds or fails in storing a mapping relationship between the identifier of the first tenant and the name of the first file. The communication device according to claim 4 , wherein: The transceiver module is further used for: Sending a second message to a third device, where the second message includes the first file and the second message is used to request the third device to load the first file; receiving second indication information from the third device, where the second indication information is used to indicate success or failure in loading the first file; Send third indication information to the second device, where the third indication information is used to indicate whether the first tenant succeeds or fails in uploading the first file.

Images