CN114980158A

CN114980158A - Communication method, device, system and storage medium

Info

Publication number: CN114980158A
Application number: CN202210417033.0A
Authority: CN
Inventors: 赵娴; 曹龙雨
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-04-20
Filing date: 2022-04-20
Publication date: 2022-08-30
Also published as: WO2023202399A1

Abstract

A communication method, apparatus, system and storage medium. The method comprises the following steps: the management service consuming entity sends first indication information to an open control management functional entity, wherein the first indication information is used for indicating a service information open mode; and the open control management functional entity sends the first service information associated with the service information open mode indicated by the first indication information to the management service consuming entity according to the first indication information. The first service information is obtained after the second service information is processed, and may be, for example, partial information selected from the second service information or information obtained after the second service information is converted. By adopting the method and the system, the individual requirements of the management service consumption entity on the open service information can be met.

Description

Communication method, device, system and storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communication method, apparatus, system, and storage medium.

Background

The third generation partnership project (3 GPP) standard proposes a Service Based Management Architecture (SBMA). Among them, a management function (MnF) entity is a basic unit constituting the SBMA architecture. The MnF is a logical entity providing a specific management task or function, and management capability provided to the outside is called management service (MnS). The MnF can be used as a management service production entity (MnS producer) to provide the MnS provided by the management service production entity to a management service consumption entity.

The network management capability opening means that an operator opens the capability of network management to external third party customers (such as tenants including the operator). The third party client is used as a management service consumption entity, and can realize network management based on the network management capability opened by an operator. Different third-party clients may have differences in the aspects of the mastery level of network management knowledge and business requirements, for example, some third-party clients want to be simple and clear in management and calling operation, and some third-party clients want to be more accurate and faster in management and calling operation.

But the current management capability open technology can cause the optimization effect of the third-party client business application to be reduced.

Disclosure of Invention

The embodiment of the application provides a communication method, device, system and storage medium, which are used for meeting the individual requirements of a management service consumption entity on open service information.

In a first aspect, a communication method is provided, and the method includes: the management service consuming entity sends first indication information to an open control management functional entity, wherein the first indication information is used for indicating a service information open mode; the open control management functional entity sends first service information associated with the service information open mode indicated by the first indication information to the management service consuming entity according to the first indication information; and the management service consuming entity receives the first service information. And the first service information is obtained after the second service information is processed.

Optionally, the service information open mode indicated by the first indication information is selected by the management service consuming entity.

Optionally, the first indication information may be sent to the oam entity in a registration request, and the first service information may be sent to the management service consuming entity by the oam entity in a registration response.

In the implementation manner, the management service consuming entity indicates the service information opening manner through the first indication information, so that the open control management functional entity can send the first service information associated with the service information opening manner to the management service consuming entity according to the service information opening manner indicated by the first indication information, and the first service information is obtained after the second service information is processed, so that the management service consuming entity can obtain the management service information matched with the service information opening manner indicated by the first indication information, and thus, the personalized requirement of the management service consuming entity on the open service information can be met.

In a possible implementation manner, the first service information is partial information selected from the second service information; or the information obtained after the second service information is converted, or part of the information is selected from the second service information, and part of the information is obtained after the second service information is converted.

In the foregoing implementation manner, on one hand, the first service information may be part of information selected from the second service information, so that the first service information is more simplified than the second service information, and thus may be matched with a service information opening manner indicated by the management service consuming entity through the first indication information; on the other hand, since the first service information is obtained by converting the second service information, for example, the second service information can be converted into the first service information which is easier to understand or optimize, so that the first service information can be matched with the service information opening mode indicated by the management service consuming entity through the first indication information. Further, in the implementation manner, sensitive information in the original information model data in the operator management information base may also be protected, for example, the open control management functional entity may provide management service information that the operator does not want to be directly used for MnF to the management service consuming entity.

In one possible implementation, the second service information is used to invoke a management service. Optionally, the second service information includes management service information provided by at least one management function entity. Optionally, the at least one management function entity is configured to provide a management service subscribed by the management service consuming entity. In other words, the openness control management functional entity may process the corresponding second service information into the first service information according to the management service subscribed by the management service consuming entity, and send the first service information to the management service consuming entity.

In one possible implementation, the method further includes: after receiving the first service information, the management service consuming entity sends a first request to the open control management functional entity, where the first request includes third service information, the third service information corresponds to a target management service called by the request, and the third service information is at least one of information included in the first service information; after receiving the first request, the openness control management functional entity sends a second request to a target management functional entity for providing the target management service, where the second request includes fourth service information, the fourth service information is obtained after processing the third service information, and the fourth service information is at least one of information included in the second service information.

Optionally, the first request is used to request to invoke a target management service.

In the foregoing implementation manner, the management service consuming entity may send, according to the target management service requested to be invoked, service information (third service information) corresponding to the target management service in the received first service information to the open control management functional entity, and the open control management functional entity may process the third service information into fourth service information, where the fourth information is management service information for a target management service entity (i.e., a target management functional entity for providing the target management service), and include the fourth service information in the second request to send to the target management functional entity, so that the target management functional entity can execute the management service requested to be invoked by the management service consuming entity according to the fourth service information.

In one possible implementation, the method further includes: the open control management functional entity receives first data from the target management functional entity and sends second data to the management service consuming entity, wherein the second data is obtained after the first data is converted; the management service consuming entity receives the first data.

In the above implementation manner, if the target management functional entity needs to return the management service data after executing the management service requested to be invoked by the management service consuming entity, the first data (for example, the first management service data obtained after executing the target management service) is sent to the open control management functional entity; the open control management functional entity may convert the first data into second data based on the service information open manner indicated by the management consuming entity through the first indication information, and send the second data to the management service consuming entity, so that the data (for example, management service data) received by the management service consuming entity is adapted to the service information open manner indicated by the management service consuming entity through the first indication information, and thus, the personalized requirement of the management service consuming entity on the open service information may be satisfied.

Optionally, after the openness control management function entity receives the first request from the management service consuming entity, the openness control management function entity may further perform the following operations: determining whether the target management service corresponding to the third service information is within a management service authorization range corresponding to the management service consuming entity; if the target management service is within the management service authorization range corresponding to the management service consuming entity, the open control management functional entity sends the second request to the target management functional entity, so that the security of management function calling can be improved.

In one possible implementation, the method further includes: the open control management functional entity sends the address information of a service discovery providing entity to the management service consuming entity; the management service consuming entity receives address information of the service discovery providing entity.

In one possible implementation, the method further includes: the management service consuming entity sends identity type information and management service type information of the management service consuming entity to a service discovery providing entity corresponding to the address information of the service discovery providing entity, wherein the management service type information is management service type information included in the first service information; if the service discovery providing entity determines that the management service consuming entity is an untrusted management service consuming entity according to the identity type information, the service discovery providing entity sends the management service type information to the open control management function entity; the open control management functional entity informs the service discovery providing entity whether the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity according to the management service type information; if the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity, the service discovery providing entity sends address information of a target management function entity to the management service consuming entity, wherein the target management function entity is a target management function entity used for providing the target management service requested to be called by the management service consuming entity; and the management service consumption entity receives the address information of the target management function entity.

In the above implementation manner, the openly controlled management functional entity may send the address information of the service discovery providing entity to the management service consuming entity, so that the management service consuming entity may send the identity type information and the management service type information of the management service consuming entity to the corresponding management service consuming entity according to the address information, thereby directly interacting with the management service consuming entity to perform a service discovery process; in the process, when the service discovery providing entity judges that the management service consuming entity is an untrusted management service consuming entity, the service discovery providing entity requests the open control management functional entity to check whether the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity, so that the security of management service calling can be improved.

In a possible implementation manner, the candidate open manners of the service information open manner include a first open manner and a second open manner, where the first open manner is associated with the first service information, and the second open manner is associated with the second service information; the service information opening mode indicated by the first indication information is the first opening mode.

In the foregoing implementation manner, the service information opening manner indicated by the management service consuming entity through the first indication information may include two candidate opening manners: the first open mode and the second open mode enable the management service consuming entity to select one of the two candidate open modes according to the requirement, thereby providing a mechanism for the management service consuming entity to select the service information open mode according to the requirement.

In a second aspect, a communication method is provided, which includes: the method comprises the steps that an open control management functional entity receives first indication information from a management service consuming entity, and if the service information open mode indicated by the first indication information is the first open mode, the first service information is sent to the management service consuming entity; and if the service information open mode indicated by the first indication information is the second open mode, sending the second service information to the management service consuming entity. The first indication information is used for indicating an open mode of service information, the candidate open modes of the open mode of service information include a first open mode and a second open mode, the first open mode is associated with the first service information, the second open mode is associated with the second service information, and the first service information is obtained after the second service information is processed.

In the foregoing implementation manner, the service information opening manner indicated by the management service consuming entity through the first indication information may include two candidate opening manners: the first open mode and the second open mode enable the management service consuming entity to select one of the two candidate open modes according to the requirement, thereby providing a mechanism for the management service consuming entity to select the service information open mode according to the requirement. If the management service consuming entity indicates that the selected service information opening mode is the first opening mode through the first indication information, the open control management functional entity sends the first service information associated with the first opening mode to the management service consuming entity, and if the management service consuming entity indicates that the selected service information opening mode is the second opening mode through the first indication information, the open control management functional entity sends the second service information associated with the second opening mode to the management service consuming entity, so that the management service consuming entity can obtain the management service information matched with the service information opening mode indicated by the first indication information, and the individualized requirement of the management service consuming entity on the opened service information can be met.

In a possible implementation manner, the service information opening manner indicated by the first indication information is selected by the management service consuming entity.

In a possible implementation manner, the first service information includes: partial information selected from the second service information; and/or the information obtained after the second service information is converted.

In one possible implementation, the second service information is used to invoke a management service.

It should be noted that, in the communication method provided by the second aspect, reference may be made to the operations of the open control management function entity and the management service consuming entity in the foregoing description.

In a third aspect, a communication method is provided, the method including: the method comprises the steps that an open control management functional entity receives first indication information from a management service consuming entity, wherein the first indication information is used for indicating a service information open mode, the service information open mode is associated with first service information, and the first service information is obtained after second service information is processed; and the open control management functional entity sends the first service information to the management service consuming entity.

In one possible implementation, after the sending the first service information to the management service consuming entity, the method further includes: an open control management functional entity receives a first request from a management service consuming entity, wherein the first request comprises third service information, the third service information corresponds to a target management service requested to be called by the management service consuming entity, and the third service information is at least one of information included in the first service information; and the open control management functional entity sends a second request to a target management functional entity for providing the target management service, wherein the second request comprises fourth service information, the fourth service information is obtained after the third service information is processed, and the fourth service information is at least one of information included in the second service information.

In a possible implementation manner, after the sending the second request to the target management function entity for providing the target management service, the method further includes: the open control management functional entity receives first data from the target management functional entity; and the open control management functional entity sends second data to the management service consuming entity, wherein the second data is obtained after the first data is converted.

In one possible implementation, the method further includes: and the open control management functional entity sends the address information of the service discovery providing entity to the management service consuming entity.

In one possible implementation, the method further includes: an open control management functional entity receives management service type information from a service discovery providing entity, wherein the management service type information is the management service type information included in the first service information; and the open control management functional entity informs the discovery service providing entity whether the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity.

In a fourth aspect, a communication method is provided, the method comprising: the management service consuming entity sends first indication information to an open control management functional entity, wherein the first indication information is used for indicating a service information open mode; and the management service consuming entity receives first service information from the open control management function entity, wherein the first service information is associated with the service information open mode indicated by the first indication information, and the first service information is obtained after the second service information is processed.

In a possible implementation manner, after receiving the first service information from the openness control management function entity, the method further includes: the management service consuming entity sends a first request to the open control management function entity, wherein the first request comprises third service information, the third service information corresponds to a target management service called by the request, and the third service information is at least one of information included in the first service information.

In a possible implementation manner, after the sending the first request to the openness control management function entity, the method further includes: and the management service consuming entity receives second data from the open control management function entity, the second data is obtained after the first data is converted, and the first data is received by the open control management function entity from a target management function entity for providing the target management service.

In one possible implementation, the method further includes: the management service consuming entity receives the address information of the service discovery providing entity from the open control management function entity; the management service consuming entity sends identity type information and management service type information of the management service consuming entity to a service discovery providing entity corresponding to the address information, wherein the management service type information is management service type information included in the first service information; and the management service consuming entity receives a notification from the service discovery providing entity, wherein the notification comprises address information of a target management function entity, the target management function entity is used for providing the management service corresponding to the management service type information, and the notification is used for notifying that the management service corresponding to the management service type information is in a management service authorization range corresponding to the management service consuming entity.

In a fifth aspect, a communication method is provided, the method including: the service discovery providing entity receives identity type information and management service type information from a management service consuming entity; if the service discovery providing entity determines that the management service consuming entity is an untrusted management service consuming entity according to the identity type information, the service discovery providing entity sends the management service type information to an open control management functional entity to request the open control management functional entity to carry out service permission check; and the open control management functional entity receives a notice from the service discovery providing entity, wherein the notice is used for notifying whether the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity.

In a possible implementation manner, if the openness control management function entity notifies that the management service corresponding to the management service type information is within the management service authorization range corresponding to the management service consuming entity, the method further includes: and the service discovery providing entity sends the address information of the management function entity corresponding to the management service type information to the management service consuming entity, and the management function entity is used for providing the management service corresponding to the management service type information.

In a possible implementation manner, the management service type information is management service type information included in first service information or management service type information included in second service information, the first service information is obtained after processing the second service information, the first service information is associated with a first open mode selected by the management service consuming entity, and the second service information is associated with a second open mode selected by the management service consuming entity.

In a possible implementation manner, the first service information is partial information selected from the second service information; or the information obtained after the second service information is converted, or part of the information is selected part of the information in the second service information, and part of the information is obtained after the second service information is converted.

In a sixth aspect, a communication method is provided, the method comprising: a management functional entity receives a request from a management consuming entity, wherein the request comprises identity type information and management service type information of the management consuming entity; if the management functional entity determines that the management service consuming entity is an untrusted management service consuming entity according to the identity type information, the management service type information is sent to an open control management functional entity; and the open control management functional entity informs the management functional entity whether the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity.

In one possible implementation, the method further includes: and if the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity, the management functional entity executes the management service requested to be called by the management consuming entity.

In a possible implementation manner, the management service type information is management service type information included in second service information, and the second service information is used for invoking a management service.

In a seventh aspect, a communication system is provided, including: a management service consumption entity and an open control management function entity. The management service consuming entity is used for sending first indication information to an open control management functional entity, wherein the first indication information is used for indicating a service information open mode; receiving first service information sent by the open control management function entity; the open control management functional entity is configured to send first service information to the management service consuming entity according to the first indication information, where the first service information is obtained after processing of second service information, and the first service information is associated with the service information open mode.

In a possible implementation manner, the second service information is used for calling a management service.

In a possible implementation manner, the management service consuming entity is further configured to send a first request to the open control management function entity after receiving the first service information, where the first request includes third service information, the third service information corresponds to a target management service requested to be invoked, and the third service information is at least one of information included in the first service information; the openness control management function entity is further configured to send a second request to a target management function entity for providing the target management service after receiving the first request, where the second request includes fourth service information, the fourth service information is obtained after processing the third service information, and the fourth service information is at least one of information included in the second service information.

In a possible implementation manner, the openness control management function entity is further configured to receive first data from the target management function entity, and send second data to the management service consuming entity, where the second data is obtained after the first data is converted; the management service consuming entity is further configured to receive the first data.

In a possible implementation manner, the openness control management function entity is further configured to send address information of a service discovery providing entity to the management service consuming entity; the management service consuming entity is also used for receiving the address information of the service discovery providing entity.

In one possible implementation, the communication system further comprises a service discovery provision entity; the management service consuming entity is further configured to send identity type information of the management service consuming entity and management service type information to a service discovery providing entity corresponding to the address information of the service discovery providing entity, where the management service type information is management service type information included in the first service information; and receiving address information of a target management function entity from the service discovery providing entity. The service discovery providing entity is used for sending the management service type information to the open control management function entity if the management service consuming entity is determined to be an untrusted management service consuming entity according to the identity type information; and if the management service corresponding to the management service type information is determined to be in the management service authorization range corresponding to the management service consuming entity according to the notification from the open control management function entity, sending the address information of the target management function entity to the management service consuming entity, wherein the target management function entity is a target management function entity for providing the target management service requested to be called by the management service consuming entity. The open control management function entity is further configured to notify the service discovery providing entity whether the management service corresponding to the management service type information is within the management service authorization range corresponding to the management service consuming entity according to the management service type information.

Optionally, the communication system may also implement the method of any one of the second to sixth aspects.

In an eighth aspect, there is provided a communication apparatus comprising: a processing unit and a receiving unit and a transmitting unit coupled to the processing unit; the receiving unit is configured to receive first indication information from a management service consuming entity, where the first indication information is used to indicate a service information opening manner, the service information opening manner is associated with first service information, and the first service information is obtained after processing second service information; the sending unit is configured to send the first service information to the management service consuming entity.

In a ninth aspect, there is provided a communication apparatus comprising: a processing unit and a receiving unit and a transmitting unit coupled to the processing unit; the sending unit is configured to send first indication information to an open control management function entity, where the first indication information is used to indicate a service information open mode; the receiving unit is configured to receive first service information from the openness control management function entity, where the first service information is associated with a service information opening manner indicated by the first indication information, and the first service information is obtained after processing second service information.

In a tenth aspect, there is provided a communication apparatus comprising: a processing unit and a receiving unit and a transmitting unit coupled to the processing unit; the receiving unit is used for receiving the identity type information and the management service type information from the management service consuming entity; receiving a notification from an open control management function entity, wherein the notification is used for notifying whether the management service corresponding to the management service type information is in a management service authorization range corresponding to the management service consuming entity; the processing unit is used for determining whether the management service consuming entity is an untrusted management service consuming entity according to the identity type information; the sending unit is configured to send the management service type information to an openness control management function entity when the processing unit determines that the management service consuming entity is an untrusted management service consuming entity.

In an eleventh aspect, there is provided a communication apparatus comprising: a processing unit and a receiving unit and a transmitting unit coupled to the processing unit; the receiving unit is used for receiving a request from a management consuming entity, wherein the request comprises identity type information and management service type information of the management consuming entity; the notification is used for notifying whether the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity; the processing unit is used for determining whether the management service consuming entity is an untrusted management service consuming entity according to the identity type information; the sending unit is configured to send the management service type information to an openness control management function entity when the processing unit determines that the management service consuming entity is an untrusted management service consuming entity.

In a twelfth aspect, a communication apparatus is provided, including: a processing unit and a receiving unit and a transmitting unit coupled to the processing unit; the receiving unit is configured to receive first indication information from a management service consuming entity, where the first indication information is used to indicate a service information opening manner, and candidate opening manners of the service information opening manner include a first opening manner and a second opening manner; the sending unit is configured to send the first service information to the management service consuming entity if the service information open manner indicated by the first indication information is the first open manner, where the first service information is associated with the first open manner, and the first service information is obtained after processing of second service information; and if the service information opening mode indicated by the first indication information is the second opening mode, sending the second service information to the management service consuming entity, wherein the second service information is associated with the second opening mode.

In a thirteenth aspect, a communication apparatus is provided, including: one or more processors; the one or more memories store one or more computer programs comprising instructions that, when executed by the one or more processors, cause the communication device to perform the method of any of the methods of the above aspects.

In a fourteenth aspect, there is provided a computer readable storage medium comprising a computer program which, when run on an electronic device, causes the electronic device to perform the method of any of the methods of the above aspects.

A fifteenth aspect provides a computer program product which, when run on an electronic device, causes the electronic device to perform the method of any of the methods of the above aspects.

In a sixteenth aspect, a chip system is provided, comprising: a memory for storing a computer program; a processor; when the processor calls and runs the computer program from the memory, the electronic device installed with the chip system is caused to execute the method of any one of the methods in the aspects.

For the above beneficial effects of the second aspect to the sixteenth aspect, please refer to the beneficial effects of the first aspect, and details are not repeated.

Drawings

FIG. 1 is a schematic diagram of a logical structure of a management function entity;

FIG. 2 is a schematic diagram of logical connections between management function entities;

FIG. 3 is a diagram illustrating an open management service;

fig. 4 is a schematic diagram of an openness architecture of a network capability based on an openness control management function entity in an embodiment of the present application;

fig. 5 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 6 is a flowchart illustrating a communication method according to an embodiment of the present application;

fig. 7a is a schematic flowchart of another communication method provided in the embodiment of the present application;

fig. 7b is a flowchart illustrating another communication method according to an embodiment of the present application;

fig. 8 is a schematic diagram illustrating a registration process of a management service consuming entity and a process of invoking a management service according to an embodiment of the present application;

fig. 9 is a schematic diagram illustrating a registration process of a management service consuming entity and a process of invoking a management service according to an embodiment of the present application;

fig. 10 is a schematic diagram illustrating a registration process of a management service consuming entity and a process of invoking a management service according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a communication device according to another embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. The terminology used in the following examples is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of this application and the appended claims, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, such as "one or more", unless the context clearly indicates otherwise. It should also be understood that in the embodiments of the present application, "one or more" means one, two or more; "and/or" describes the association relationship of the associated objects, indicating that three relationships may exist; for example, a and/or B, may represent: a alone, both A and B, and B alone, where A, B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

The embodiments of the present application relate to a plurality of numbers greater than or equal to two. It should be noted that, in the description of the embodiments of the present application, the terms "first", "second", and the like are used for distinguishing the description, and are not to be construed as indicating or implying relative importance or order.

The following first introduces terms related to embodiments of the present application.

(1) Network capability opening

The network management capability opening means that an operator opens the capability of network management to an external third party (3) ^rd party) client. As a management service consuming entity, a third party client may manage a network of a third party by a corresponding network management system (e.g., an operation, administration and maintenance (OAM) system of the third party, a shared operator management system, etc.) based on a network management capability opened by an operator, for example, the following network management may be implemented: the method comprises the steps of obtaining performance data of a service tenant network, configuring network parameters of the service tenant network and the like. As another example, in a slice management or vertical industry (vertical industry) oriented private network scenario, a third party who is a slice using customer or vertical industry customer may wish to pass through a pipeThe management capability openness obtains certain network management capability from an operator network so as to participate in the management or data analysis of the related slice network or private network.

The network capacity of the operator can be opened to the third-party client through the network capacity opening, so that the friendly butt joint of the network capacity and the service requirement is realized, and the resource configuration is optimized. Through the open interface open network capability, third parties can create better business applications and services using the information obtained or through configuration policy adjustments.

The following examples list several possible management services:

a Network Slice Management Function (NSMF);

a Network Slice Subnet Management Function (NSSMF);

management Data Analysis Function (MDAF);

a Communication Service Management Function (CSMF);

a Network Function Management Function (NFMF);

network Function (NF).

It should be noted that, the foregoing lists only some possible management services by way of example, and the embodiments of the present application do not limit the types and the number of the management services.

(2) Management service consumption entity and management service providing entity

The management service providing entity is an entity for providing management service, the management service consuming entity is an entity using the management service, and the management service consuming entity can obtain the management service function provided by the corresponding management service providing entity by calling the management service. In the embodiment of the present application, the management service providing entity is referred to as a management function (MnF) entity, and the management service consuming entity may include a third party client.

The third party customer, as a management service consuming entity, may use network management capabilities (called management services) opened by the operator. The third party customer may be a tenant of an operator, and may be, for example, a vertical industry customer, a slice usage customer, or a sharing operator, among others. For example, the third party is an organization or company that uses (or consumes) the operator to customize the network services.

In this embodiment, a third party client interacting with a related entity (for example, including an open control management function) on an operator network side may be a network management system of a third party or an entity for implementing network management, for example, an OAM system of the third party or a shared operator management system.

In the SBMA architecture of the 5G network management technology, a management function (MnF) is a basic unit constituting the SBMA architecture. Fig. 1 shows the logical architecture of MnF. As shown, the MnS may be provided by a management service producer (MnS producer) to a management service consumer (e.g., including a third-party network management system or other MnS) (as shown by the line with the open circle at one end in fig. 1), or may be invoked by another MnS (MnS consumer) (as shown by the line with the semi-circle at one end in fig. 1). The mutual calling MnS among the MnFs is based on a service interface.

The currently defined 3GPP MnF and the logical connection between MnF can be shown in fig. 2. The open control management function is a logic management function which is open to the outside and is used for realizing the opening of operation and maintenance management information of a network side, such as configuration information, performance measurement information, alarm and/or error information and the like.

An open mechanism of the open control management function entity can be shown in fig. 3. Wherein, both the third party (3rd party, such as vertical industry) and the management function entity MnF2 can be understood as clients which are not directly trusted by the management domain of the management function entity MnF1 but are authorized. In this case, in order to call MnS provided by the management function entity MnF1, a third party needs to implement a management service call request through the open control management function entity 1 (as indicated by a dotted path in the figure), and the management function entity MnF2 needs to implement a management service call request through the open control management function entity 2 (as indicated by a solid path in the figure). The open control management functional entity 1 and the open control management functional entity 2 can directly call MnS provided by the management functional entity MnF 1.

Currently, a third party initiates a request for management service call to an open control management function entity based on management service information (referred to as second service information or MnS info in this embodiment) provided by the open control management function entity. On one hand, the management service information (MnS info) contains more content and is highly professional, and a third party is required to understand the management service information with certain network management related knowledge, so that a management service call request can be initiated based on the management service information to realize a network management function that the third party needs to realize. From the perspective of a third party, due to different mastery levels of network management knowledge and different business requirements, part of the third parties may want to be simple and clear in management and calling operations, and part of the third parties want to be more accurate and rapid in management and calling operations, so that the requirement for flexible selection of service information with open management capability appears, but the existing technology cannot meet the personalized requirement preference of a third party autonomous management mechanism, and the optimization effect of third party business application may be reduced. On the other hand, for safety reasons, such as the need to protect sensitive information in the raw information model data in the Management Information Base (MIB) of the operator, the operator may not want to provide the management service information (MnS information) directly used for MnF to a third party for use.

Therefore, the embodiment of the present application provides a communication method, a communication system and a related device, so as to meet the personalized requirement of the management service consuming entity on the open service information. According to some embodiments of the present application, when a third party (or a third party entity, for example, including a third party network management system or a third party application server) uses a network management capability opened by an operator as a management service consuming entity, an open service information flexible selection mechanism may be provided to the third party, so that the third party selects an open form most suitable for itself based on its own grasp of network management expertise and business requirements, so as to better improve the business level of the industry.

Embodiments of the present application are described below with reference to the accompanying drawings.

Fig. 4 is a schematic diagram of an open architecture of network capabilities based on an opencontrol management function entity in the embodiment of the present application.

As shown in fig. 4, the architecture may include the following functional entities:

the management service consuming entity: for requesting to invoke a management service, for example, a management service invocation request may be initiated to a management domain (e.g., including a cross-domain management unit or a single-domain management unit). An example of a management service consuming entity is a third party entity (3) ^rd party entry), such as the third party entity may be a management system of the industry vertical. A management service request may be initiated to a management domain (either a cross-domain management system or a single-domain management system).

Cross domain management (cross domain management) unit: may correspond to a Network Management System (NMS) and is responsible for the unified management of a plurality of network element management systems.

Single domain management (domain management) unit: which may correspond to an Element Management System (EMS), is responsible for managing base stations (including, for example, 5G base stations) or core networks (including, for example, 5G core networks).

Optionally, the functional entities may perform information interaction based on presentation state transfer (REST) Application Programming Interface (API). REST is a standard method used to describe the creation of a hypertext transfer protocol (HTTP) API through which view (view) behavior can be mapped to a GET method in HTTP, create (create) behavior can be mapped to a POST method in HTTP, edit (edit) behavior can be mapped to a PUT method in HTTP, and DELETE (DELETE) behavior can be mapped to a DELETE method in HTTP.

Optionally, the cross-domain management unit and the single-domain management unit may respectively include an openness control management function entity to provide a capability openness control function.

Optionally, the cross-domain management system and the single-domain management system may respectively include a management function entity (MnF) for providing an open management service. MnF is a collection of functionally similar MnS, and may be deployed at a cross-domain management layer, such as a Network Slice Management Function (NSMF), at a single-domain management layer, such as a Network Slice Subnet Management Function (NSSMF), or at a Management Data Analysis Function (MDAF). The MnF may provide specific management services such as configuration services, performance measurement services, fault alarm services, and the like.

Optionally, the cross-domain management system may further include a service discovery provider (MnS discovery provider) for providing a function of managing service discovery.

The network capacity open architecture can be applied to providing a user-level or traffic flow-level management service function for a management service consuming entity (including vertical industry application, for example), such as providing wireless network information to help the management service consuming entity to optimize application services, thereby realizing real-time and fine wireless network information monitoring.

It should be noted that the open control management function entity in the embodiment of the present application may be an open control management function entity in the cross-domain management system in the above architecture, or may be an open control management function entity in a single-domain management system in the above architecture. Fig. 5 exemplarily illustrates a structural schematic diagram of a communication system provided in an embodiment of the present application, where an openness control management function entity in the system may be an openness control management function entity in a cross-domain management system or an openness control management function entity in a single-domain management system.

As shown in fig. 5, the communication system may include: a management service consuming entity (501a,501b) and an open control management function entity 502, and a management function entity (503a,503b,503 c). Further, a service discovery provision entity 504 may also be included. Alternatively, the service discovery provision entity 504 may be deployed on or outside an Operation Support System (OSS) layer.

The management service consuming entities (501a,501b) may perform information interaction with the open control management function entity 502, and the open control management function entity 502 may perform information interaction with the management function entities (503a,503b,503c) and the service discovery providing entity 504, respectively (as shown by the solid line connection in the figure). Optionally, the management service consuming entity (501a,501b) may also perform information interaction with the service discovery providing entity 504 and the management function entity (503a,503b,503c) (as shown by the dashed connection in the figure, the management service consuming entity 501a performs information interaction with the service discovery providing entity 504 and the management function entity 503a is only exemplarily shown in the figure).

The number of the management service consuming entities, the open control management function entity, the management function entity, and the service discovery providing entity may be one or more, and fig. 5 only exemplarily shows the case of two management service consuming entities and three management function entities, and the number of the above-mentioned function entities is not limited in the embodiment of the present application.

It should be noted that, in the embodiment of the present application, the "open control management function entity" may be referred to as an exposure management function, which is abbreviated as EGMF. The embodiment of the present application does not limit the naming mode of the "open control management function entity".

Based on the communication system, the management service consuming entity is used for sending first indication information to the open control management functional entity, wherein the first indication information is used for indicating the service information open mode. And the open control management functional entity is used for sending first service information associated with the service information open mode indicated by the first indication information to the management service consuming entity according to the first indication information, wherein the first service information is obtained after processing second service information. The management service consuming entity receives first service information sent by the open control management functional entity. The management service consuming entity may subsequently initiate a management service invocation request based on the first service information.

In this embodiment of the present application, the first indication information is used to indicate an open mode of service information. Optionally, the first indication information may be set by the management function consuming entity, so as to indicate the service information opening manner selected by the management function consuming entity. Optionally, the first indication information may also be referred to as an open mechanism (open mechanism) parameter or an open mechanism information, and the naming of the first indication information is not limited in this embodiment of the application.

Optionally, the service information opening manner may include the following candidate opening manners: the first open mode, further, the candidate open mode may further include a second open mode. For example, the value of the first indication information may include a first value and a second value, where if the value of the first indication information is equal to the first value, it indicates that the service information open manner indicated by the first indication information is the first open manner, and if the value of the first indication information is equal to the second value, it indicates that the service information open manner indicated by the first indication information is the second open manner.

In the first open mode, service information opened to the management service consuming entity is different from management service information for the management functional entity (MnF), and it can be understood that the management service information for the MnF is service information used when the open control management functional entity calls the management functional entity (MnF), and is the same as service information in the MIB. For example, in the first open mode, the service information provided by the open control management function entity to the management service consuming entity is different from the original service information model stored in the operator MIB, for example, the service information provided by the open control management function entity to the management service consuming entity is simpler and easier to understand than the original service information stored in the operator MIB. The first open mode may also be referred to as an indirect open mode. In the second open mode, the service information open to the management service consuming entity is the same as the management service information for the management function entity (MnF). For example, in the second open mode, the service information provided by the open control management function entity to the management service consuming entity is the same as the original service information model stored in the operator MIB. The second open mode may also be referred to as a direct open mode.

In this embodiment, the management service information that is opened to the management service consuming entity in the first opening mode is referred to as first service information (also referred to as eMnS information). The first service information may be intuitively understood as service information that the management service consuming entity needs to provide to the open control management function entity to invoke an open management service (for example, including a configuration management service, a performance measurement service, an alarm information reporting service, and the like). It can be understood that there is an association relationship between the first open manner and the first service information.

In the embodiment of the present application, the management service information that is released to the management service consuming entity in the second release mode is referred to as second service information (also referred to as MnS information). The second service information may be intuitively understood as management service information required by the oam entity to invoke a management service (e.g., including a configuration management service, a performance measurement service, an alarm information reporting service, etc.). It can be understood that the second open manner has an association relationship with the second service information.

In this embodiment of the application, the first service information may be obtained after the second service information is processed. In other words, the first service information can be obtained by processing the second service information.

In the embodiment of the present application, the "processing" may also be understood as "mapping", and may include the following two meanings:

on the other hand, the first service information (eMnS information) is obtained by selecting partial information from the second service information (MnS information). In other words, a subset of the second service information may be obtained, resulting in the first service information. By this "processing" manner, only a part of all management services that can be provided by the operator can be opened to the management service consuming entity, and specifically, which management services are opened can be determined by the management service subscription business agreement that the management consuming entity subscribes with the operator. By this "processing" manner, only part of all the management service information that can be provided by the operator may be opened to the management service consuming entity, and specifically, which management service information is opened may be determined by the operator, for example, the operator may not provide sensitive management service information (for example, management service information related to a management service pricing policy) to the management service consuming entity.

Since the first service information may be part of information selected from the second service information, the first service information is more simplified than the second service information, and thus may be matched with the service information opening manner indicated by the management service consuming entity through the first indication information. Further, in the implementation manner, sensitive information in the original information model data in the operator management information base may also be protected, for example, the open control management functional entity may provide management service information that the operator does not want to be directly used for MnF to the management service consuming entity.

On the other hand, the second service information (MnS information) is converted (transform) to obtain the first service information (eMnS information). Through the conversion, the operation of the management service consuming entity for calling the open management service can be simplified, and the original management model information of the operator can be protected.

For example, the second service information can be converted into the first service information which is easier to understand or optimize, so that the first service information can be matched with the service information opening mode indicated by the management service consuming entity through the first indication information.

In a possible implementation manner, when the second service information is processed to obtain the first service information, at least one of the above operations of "selecting" and "converting" may be adopted, so that the first service information may include: the partial information selected from the second service information includes information obtained after the second service information is converted, or includes both the partial information selected from the second service information and the information obtained after the second service information is converted.

For example, the name of the management service type in the second service information may be converted, and the name of the management service type is converted from a name that needs to be understood by a certain network management professional to a more understandable name, so as to obtain the name of the management service type in the first service information, that is, the name of the management service type in the second service information is converted to the name of the management service type in the first service information. For another example, a plurality of a-type MnS components with the same or similar operation types in the second service information may be converted into an a-type MnS component with one operation type, or a plurality of B-type MnS components acting on the same network element in the second service information may be converted into one B-type MnS component acting on the network element, or a plurality of C-type components in the second service information may be converted into a Key Performance Indicator (KPI) or a Key Quality Indicator (KQI).

In the embodiment of the application, partial information or all information in the second service information can be converted to obtain the first service information. Taking the example that the second service information includes multiple management service components (MnS components) and management service types (MnS types), in this embodiment of the present application, at least one of the multiple components and/or the management service types may be converted to obtain the first service information.

Taking the MnS component defined in the current 3GPP standard as an example, the MnS information (second service information) may include the following three types of components:

type a management service component (MnS component Type a): on behalf of a class of operations or notifications, one example of a type a management service component is: in the configuration management service, a management object instance createMOI () is created. The MnS information may include a wide variety of MnS component Type a.

Type B management service component (MnS component Type B): an object representing an operation, i.e. a management object instance. The MnS information may include a wide variety of MnS component types B.

C-Type management service component (MnS component Type C): representing associated data such as performance data, alarm data, etc.

In the embodiment of the present application, optionally, as for MnS component Type a in MnS information (second service information), a variety of MnS component types a may be converted into several types of operations (call actions).

For example, the MnS component type a in the MnS information (second service information) may include:

createomomei (create management object information), getMOIAttributes (get management object information attributes), modifymobinutables (modify management object information attributes), deleteMOI (delete management object information), creatememeasurementjob (create measurement task), stopmeassurerementjob (stop measurement task), listMeasurementJob (list measurement task), getalilistlist (get alarm list), notifynnewalarm (notify new alarm), notifychangedam (notify changed alarm), notifylaralarm (notify alarm list rebuild), notifycorrected (notify relevant notify changed), getalimentcount, setcom (set comment), acknowledgallacknowledgarecknowledgers (confirm alarm), notifordellardementearlarearancewhanged (notify relevant notify changed), getalarm count, setcomunt (clear alarm, etc.).

For MnS component type a in MnS information (second service information) described above, in the embodiment of the present application, it may be converted into the following 7 types of operations: create (create), delete (delete), modify (modify), list (list), subscribe (subscribe), unsubscribe (unsubscribe), upload (upload). For example, createMOI, createMeasurementJob in MnS component type a described above may be converted to a create (create) operation in eMnS component type a.

In the embodiment of the present application, optionally, as for MnS component Type B in MnS information (second service information), a variety of MnS component types B may be converted into network elements of corresponding types.

For example, the MnS component type B in the MnS information (second service information) may include:

TraceJob, PerfMetricJob, MnsInfo, heartbeat control, Files, GNBDUFunction, NRCellCU, NRCellDU, BWP, wdwidth part, AMFFunction, nwdaff function, NetworkSlice subnet, etc.

For MnS component type B in the MnS information (second service information), in this embodiment, it may be converted into the following Network Elements: access and mobility management function (AMF), User Plane Function (UPF), Session Management Function (SMF), gNB (base station), Network Exposure Function (NEF), Unified Data Management (UDM), and the like. For example, NRCellCU and NRCellDU in the MnS component type B may be converted into gNB, and AMFFunction in the MnS component type B may be converted into AMF, for example.

In this embodiment, optionally, for the MnS component type C in the MnS information, data of the MnS component type C may be aggregated and packaged into a Key Performance Indicator (KPI), a Key Quality Indicator (KQI), and the like, which are easily understood by a management service consuming entity (such as a third party).

For example, the MnS component type C in the MnS information (second service information) may include:

the QoS information may include, for example, average delay of downlink (DL air interface, where DL is an english abbreviation of downlink, that is, downlink), distribution of delay DL air interface, DL total PRB Usage (total downlink physical resource block Usage), average UE throughput (average UE (user equipment or terminal) throughput), RRC connection number (RRC (radio resource control) connection number), inter-gNB handles (inter-base station handover), number of QoS flow allocated to release (number of QoS flows trying to release), and the like.

For the MnS component type C in the MnS information (second service information), optionally, in the embodiment of the present application, it may be converted into KPI or KQI.

Taking the MnS type defined in the current 3GPP standard as an example, the MnS information (second service information) may include the following four MnS types:

ProvMnS: providing MnS;

FaultSupervisionMnS: fault monitoring MnS;

streamingdatareporting mns: streaming data report MnS;

FileDataReportingMnS: the file data reports MnS.

For the above four MnS types, in the embodiment of the present application, it may be optionally converted into the following MnS types: configuration management (provisioning), alarm management (Fault provisioning), and Performance management (Performance administration). For example, the faultSupervisionMnS in the MnS component type C may be converted into alarm management (Fault Supervision), and for example, the streamDataReportingMnS in the MnS component type C may be converted into Performance management (Performance Association).

It should be noted that the above conversion manner from the second service information (MnS information) to the first service information (eMnS information) is merely an example, and the specific conversion manner is not limited in the embodiment of the present application. According to the above conversion method, the first service information may also be processed to obtain corresponding second service information.

Based on the architecture shown in fig. 4 or fig. 5, the following describes the communication method provided in the embodiment of the present application in detail with reference to fig. 6, fig. 7a, and fig. 7b, respectively.

Fig. 6 is a schematic flowchart of a communication method according to an embodiment of the present disclosure. Through the process, the corresponding service information can be sent to the management service consuming entity based on the first indication information which is sent by the management service consuming entity and used for indicating the service information opening mode.

As shown in fig. 6, the process may include the following steps:

601: the management service consuming entity sends first indication information to the open control management functional entity, wherein the first indication information is used for indicating the service information open mode. The service information opening mode is associated with first service information, and the first service information is obtained after the second service information is processed.

Optionally, the management service consuming entity may set a value of the first indication information according to the service information opening manner selected by the management service consuming entity, so that the first service information may indicate the service information opening manner selected by the management service consuming entity.

Optionally, the candidate open manners of the service information open manner may include a first open manner and a second open manner, where the first open manner is associated with the first service information, and the second open manner is associated with the second service information. In this flow, the service information opening method indicated by the first indication information is described as the first opening method.

For a description of the service information opening manner and the first service information and the second service information, reference may be made to the foregoing embodiments.

602: and the open control management functional entity sends the first service information to the management service consuming entity.

In this step, if the open control management functional entity determines that the corresponding service information open mode is the first open mode according to the first indication information, the second service information is processed to obtain first service information associated with the first open mode, and the first service information is sent to the management service consuming entity, so that the management service consuming entity subsequently initiates a management service invocation request based on the first service information.

Optionally, after receiving the first indication information, the open control management functional entity may perform authentication and verification on the management service consuming entity, and if the authentication and verification is passed, send the first service information to the management service consuming entity, otherwise, return failure information like the management service consuming entity, and end the process.

Optionally, in the foregoing flow, the first indication information may be carried in a registration request sent by the management service consuming entity and sent to the openness control management functional entity, and the first service information may be carried in a registration response returned by the openness control management functional entity and sent to the management service consuming entity. In other words, the above flow may be a registration flow of the management service consuming entity with the opengcfunction entity.

Optionally, in the registration process of the management service consuming entity to the open control management functional entity, the management service consuming entity may further carry tenant description information (tenant profile) of the management service consuming entity in the registration request and send the registration request to the open control management functional entity, where the tenant description information may include information (such as a type of the management service) of the management service used by the management service consuming entity in a subscription. The open control management functional entity can determine the management service signed and used by the management service consuming entity according to the tenant description information, process second service information corresponding to the management service signed and used by the management service consuming entity to obtain corresponding first service information, and then send the first service information to the management service consuming entity by carrying the first service information in a registration response.

For the related description of processing the second service information to obtain the first service information, reference may be made to the foregoing embodiments.

In a possible implementation manner, the candidate open manners of the service information open manner include a first open manner and a second open manner, where the first open manner is associated with the first service information, and the second open manner is associated with the second service information. The service information open mode indicated by the first indication information sent by the management service consuming entity may be a first open mode (for example, the management service consuming entity selects the first open mode), or may be a second open mode (for example, the management service consuming entity selects the second open mode). If the openness control management functional entity determines that the service information opening manner indicated by the first indication information is the first opening manner according to the first indication information sent by the management service consuming entity, processing may be performed according to the flow shown in fig. 6 (for example, including sending the first service information to the management service consuming entity); if the open control management functional entity determines that the service information open mode indicated by the first indication information is the second open mode according to the first indication information sent by the management service consuming entity, sending second service information associated with the second open mode to the management service consuming entity according to the second open mode indicated by the first indication information.

In a possible implementation manner, the method may further include the following steps: and the open control management functional entity sends the address information of the service discovery providing entity to the management service consuming entity. Optionally, the subsequent management service consuming entity may initiate a service discovery process to the corresponding service discovery providing entity according to the address information of the service discovery providing entity.

In the above flow, the management service consuming entity indicates the service information opening manner through the first indication information, so that the open control management functional entity can send the first service information associated with the service information opening manner to the management service consuming entity according to the service information opening manner indicated by the first indication information, and since the first service information is obtained after the second service information is processed, the management service consuming entity can obtain the management service information matched with the service information opening manner indicated by the first indication information, thereby satisfying the personalized demand of the management service consuming entity on the open service information. Furthermore, the sensitive information in the original information model in the operator management information base can be protected through the process, for example, the relevant service information related to the management service pricing policy in the operator management information base can not be provided for the management service consuming entity.

In this embodiment of the application, after obtaining the open service information (for example, obtaining the first service information) based on the flow shown in fig. 6, the management service consuming entity may initiate a management service invoking flow according to the service information. Fig. 7a and 7b respectively show a call flow of the management service provided by the embodiment of the present application.

Referring to fig. 7a, a schematic flowchart of a communication method according to an embodiment of the present application is provided. Through the flow, the calling process of the management service can be realized. The process takes the service information opening manner selected by the management service consuming entity as the first opening manner, and obtains the first service information associated with the first opening manner based on the process shown in fig. 6 as an example description.

As shown in fig. 7a, the process may include the following steps:

701: and the management service consuming entity sends a first request to the open control management functional entity, wherein the first request comprises third service information.

Optionally, the first request is used to request to invoke a target management service. Optionally, the target management service may include one or more. The target management service may include, for example, one or more of a configuration service, a performance measurement service, and a fault alarm service.

The third service information corresponds to a target management service requested to be invoked by the management service consuming entity, and the third service information is at least one of information included in the first service information, that is, the third service information is a subset of the first service information. For example, if the management service consuming entity signs up for the configuration service, the performance measurement service, and the fault warning service, the first service information includes service information of these three management services. If the management service consuming entity requests to call the fault alarm service currently, service information (called as third service information) corresponding to the fault alarm service is extracted from the first service information, and the third service information is carried in the first request and is sent to the open control management function entity.

Alternatively, the first request may be a management service invocation request. It should be noted that the naming of the first request is not limited in the embodiments of the present application.

702: and the open control management functional entity sends a second request to a target management functional entity for providing the target management service, wherein the second request comprises fourth service information.

The fourth service information is obtained after the third service information is processed. The fourth service information is at least one of information included in the second service information, that is, the fourth service information is a subset of the second service information. The fourth service information is used for the target management functional entity, that is, the target management functional entity can execute the corresponding management service according to the fourth service information.

In this step, after receiving the first request, the open control management functional entity may determine the service information open mode selected by the management service consuming entity according to the first indication information sent by the management service consuming entity before the first request. And if the service information open mode selected by the management service consumption entity is the first open mode, processing the third service information carried in the first request to obtain fourth service information, carrying the fourth service information in the second request, and sending the fourth service information to the target management function entity.

And processing the third service information to obtain fourth service information, wherein the process of processing the second service information to obtain the first service information is a corresponding processing process. Taking the target management service requested to be invoked by the management service consuming entity as the fault alert service as an example, if the type B component in the third service information includes "gbb (base station)", the type B service component may be converted into "NRCellCU (NR cell centralized unit), NRCellDU (NR cell distributed unit), BWP (partial bandwidth)" in the fourth service information.

Optionally, after receiving the first request, the open control management functional entity may determine, according to the management service subscribed by the management service consuming entity, whether the target management service corresponding to the third service information is within the management service authorization range corresponding to the management service consuming entity; if the target management service is in the management service authorization range corresponding to the management service consuming entity, the open control management functional entity sends the second request to the target management functional entity, and if the target management service is not in the management service authorization range corresponding to the management service consuming entity, the open control management functional entity rejects the first request, so that the security of management function calling can be improved.

Optionally, the above process may further include the following steps: and after receiving the first request, the open control management functional entity acquires the address information of the target management functional entity from the service discovery providing entity. At 702, the openness control management function entity sends a second request to the target management function entity according to the address information of the target management function entity.

703: and after receiving the second request, the target management functional entity executes corresponding management service according to the fourth service information.

In the above flow, the management service consuming entity may send, according to the target management service requested to be invoked, service information (third service information) corresponding to the target management service in the received first service information to the open control management functional entity, and the open control management functional entity may process the third service information into fourth service information, where the fourth information is management service information for a target management service entity (i.e., a target management functional entity for providing the target management service), and include the fourth service information in the second request to send to the target management functional entity, so that the target management functional entity can execute the management service requested to be invoked by the management service consuming entity according to the fourth service information.

In a possible implementation manner, after the target management functional entity executes the corresponding management service according to the fourth service information, the process may further include the following steps:

704: and the target management functional entity sends the first data to the open control management functional entity.

The first data may also be referred to as management service data, which is a result obtained after the openly controlling management functional entity executes the target management service. For example, if the target management service is a performance measurement service, the first data obtained after the performance measurement service is executed may include information such as a time delay of a downlink air interface of a base station, an average throughput, and a time delay of inter-base station handover.

705: and the open control management functional entity sends second data to the management service consuming entity, wherein the second data is obtained after the first data is converted.

In this step, after receiving the first data, the open control management functional entity may determine the service information open mode selected by the management service consuming entity according to the first indication information sent by the management service consuming entity before the first data. If the service information open mode selected by the management service consumption entity is the first open mode, the first data is converted to obtain second data, and the second data is sent to the management service consumption entity.

Optionally, a method of converting the first data into the second data is similar to a method of converting the second service information into the first service information. For example, the first data may be converted into KPI or KQI, for example, still taking the performance measurement service as an example, the first data may be converted into a corresponding KQI according to information such as delay of downlink air interface of the base station, average throughput, and handover delay between base stations, where the KQI may represent one of the following network performance qualities: good performance, general performance and poor performance.

Referring to fig. 7b, a schematic flowchart of another communication method provided in the embodiment of the present application is shown. Through the flow, the calling process of the management service can be realized. The process takes the service information open mode selected by the management service consuming entity as the first open mode, and obtains the first service information associated with the first open mode based on the process shown in fig. 6 as an example description.

As shown in fig. 7b, the process may include the following steps:

711: the management service consuming entity sends the identity type information of the management service consuming entity and the management service type information to the service discovery providing entity.

The identity type information of the management service consuming entity is used for indicating whether the management service consuming entity is a management service consuming entity inside the management domain or a management service consuming entity outside the management domain, and if the management service consuming entity is the management service consuming entity outside the management domain, the management service consuming entity is not trusted.

The management service type information is management service type information included in the first service information. Illustratively, the management service type information is management service type information of a target management service that the management service consuming entity requests to invoke. For example, if the management service consuming entity requests to invoke the fault alarm service, the management service type information corresponding to the fault alarm service is extracted from the first service information, and the management service type information is sent to the service discovery providing entity.

Optionally, in this step, the management service consuming entity may send the identity type information of the management service consuming entity and the management service type information to the corresponding service discovery providing entity according to the address information of the service discovery providing entity obtained before. The step of the management service consuming entity receiving the address information of the service discovery providing entity can be seen as the related step in fig. 6.

Optionally, the management service consuming entity may carry the identity type information and the management service type information of the management service consuming entity in a service discovery request, and send the service discovery request to the service discovery providing entity, where the service discovery request is used to request to obtain address information of a target management service, and the target management service is a management service corresponding to the management service type information. It should be noted that the naming of the message is not limited in the embodiment of the present application.

712: and the service discovery providing entity determines the management service consuming entity to be an untrusted management service consuming entity according to the identity type information of the management service consuming entity.

713: the service discovery providing entity sends the management service type information to the open control management function entity.

Optionally, the service discovery providing entity may carry the management service type information in an authorization check request, and send the authorization check request to the open control management functional entity, where the authorization check request is used to request to check whether the management service corresponding to the management service type information is within the authorization range of the management service corresponding to the management service consuming entity. Optionally, the permission check request may further include identification information of the management service consuming entity.

It should be noted that the naming of the message is not limited in the embodiment of the present application.

714: and the open control management functional entity informs the service discovery providing entity whether the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity according to the management service type information.

The process is described by taking the case that the management service corresponding to the management service type information is within the management service authorization range corresponding to the management service consuming entity.

Optionally, if the management service corresponding to the management service type information is not within the management service authorization range corresponding to the management service consuming entity, the open control management functional entity sends a failure notification to the service discovery providing entity, and ends the process.

715: the service discovery providing entity sends the address information of the target management function entity to the management service consuming entity.

716: and the management service consuming entity sends a first request to the open control management functional entity, wherein the first request comprises third service information.

Optionally, the first request may further include the address information of the target management function entity acquired in step 714.

717: and the open control management functional entity sends a second request to a target management functional entity for providing the target management service, wherein the second request comprises fourth service information.

718: and after receiving the second request, the target management functional entity executes corresponding management service according to the fourth service information.

719: and the target management functional entity sends the first data to the open control management functional entity.

720: and the open control management functional entity sends second data to the management service consuming entity, wherein the second data is obtained after the first data is converted.

The specific implementation of steps 716-720 in the flow shown in FIG. 7b is substantially the same as the specific implementation of steps 701-705 in the flow shown in FIG. 7 a.

In the above process, the openly controlled management functional entity may send the address information of the service discovery providing entity to the management service consuming entity, so that the management service consuming entity may send the identity type information and the management service type information of the management service consuming entity to the corresponding management service consuming entity according to the address information, thereby directly interacting with the management service consuming entity to perform the service discovery process; in the process, when the service discovery providing entity judges that the management service consuming entity is an untrusted management service consuming entity, the service discovery providing entity requests the open control management functional entity to check whether the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity, so that the security of management service calling can be improved.

In connection with the flow shown in fig. 6 and the flow shown in fig. 7a, fig. 8 illustrates a process of registering and invoking a management service for a management service consuming entity. During the registration process, the management service consuming entity selects a first open mode.

As shown in fig. 8, the process may include the following steps:

801: the management service consuming entity sends a registration request to the open control management functional entity, wherein the registration request comprises first indication information, and the service information open mode indicated by the first indication information is a first open mode.

The first indication information in the registration request message represents a selection of an open form of management service information by the management service consuming entity. In this flow, for example, the service information opening manner indicated by the first indication information is a first opening manner, that is, the service information that the management service consuming entity wants to open to the management service consuming entity is optimized and easily understood service information.

Optionally, the registration request may also carry identification information of the management service consuming entity (for example, a customer ID, where the ID is an english abbreviation of identification, that is, an identifier), and tenant description information (for example, a tenant profile). The customer ID is an identifier describing the management service consuming entity, and may be a name (name) of a customer, such as a vertical industry enterprise name, or a digital identifier representing the management service consuming entity. the smart profile is a description file describing basic information of a management service consumption entity, and may include requirements of the management service consumption entity on Service Level Specification (SLS), including index requirements such as time delay, reliability, and resource isolation.

802: after receiving the registration request, the open control management functional entity processes the first service information (eMnS information) based on the second service (MnS information) according to the first open mode indicated by the first indication information.

In this step, the open control management functional entity may first open a business contract according to tenant description information (e.g., a tenant profile) of the management service consuming entity and a capability signed with an operator (network service provider or network operation provider), and perform authentication and authorization for the identity of the management service consuming entity. If the authentication passes, a tenant id (operator id), stored tenant information (tenant profile), and open mode information (here, related information of the first open mode, such as a value of the first indication information) are generated. Optionally, one implementation manner of storing the information may be: and establishing a tenant management object instance, and storing the corresponding relation between the tenant identification and the open mode by the open control management functional entity, for example, storing the open mode as an attribute of the tenant instance.

In this step, the open control management functional entity determines that the service information open mode selected by the management service consuming entity is the first open mode according to the first indication information, and then acquires corresponding first service information (eMnS information) based on second service information (MnS information) of the management service according to the management service subscribed by the management service consuming entity.

803: and the open control management functional entity sends a registration response to the management service consuming entity, wherein the registration response comprises the first service information. Optionally, the registration response may further include identification information (e.g., operator ID) of the management service consuming entity.

804: the management service consuming entity sends a first management service calling request to the open control management functional entity, wherein the request comprises third service information.

The third service information is a subset of the first service information returned by the open control management function entity to the management service consuming entity in 803, and is service information of a target management service requested to be invoked by the management service consuming entity, for example, the target management service may be one or more management services such as configuration management, performance measurement, alarm collection, and the like.

The first management service invocation request may also include an identity (such as an operator ID) of the management service consuming entity, and the identity may uniquely identify the management service consuming entity within the management domain.

805: and the open control management functional entity performs authority check. This step is an optional step.

In this step, the openness control management functional entity may check, according to the identification information (e.g., operator ID) of the management service consuming entity, based on tenant information (e.g., tenant profile) of the management service consuming entity, whether the target management service requested to be invoked by the management service consuming entity is within a management consumption range allowed by the management service consuming entity (i.e., determine whether the management service consuming entity subscribes to the target management service). If the check is passed, the subsequent steps are continuously executed, otherwise, the open control management functional entity refuses the management service calling request of the management service consuming entity, and the request failure result is returned to the management service consuming entity.

806: and the open control management functional entity processes the third service information into fourth service information.

807: the oam function entity sends a Service Discovery request to a MnS Discovery Service provider (MnS Discovery Service provider) to request address information of a target oam function entity. The target management function entity is a management function entity capable of providing the target management service.

The service discovery request may include identification information (such as an identification of an opencontrol management function entity), and a MnS type of the target management service, where the MnS type is management service type information included in the fourth service information.

808: the service discovery providing entity returns a service discovery response to the openmanager function entity, wherein the service discovery response may include address information of the target manager function entity.

809: and the open control management functional entity sends a second service calling request to the target management functional entity according to the address information of the target management functional entity, wherein the second service calling request can carry fourth service information.

In this step, the open control management function entity may send a second management service call request to the corresponding target management function entity according to the component (MnS component) of the target management service and the address information of the target management function entity.

810: and the target management functional entity responds to the second management service calling request and executes corresponding management service.

Optionally, if the management service requested to be invoked is performance data measurement or alarm data reporting, the target management functional entity returns related original data (i.e., the first data) to the open control management functional entity.

811: if 810 there is the first data returned, the opencontrol management function entity performs the conversion of the first data to the second data.

812: and the open control management functional entity sends a management service calling response to the management service consuming entity, wherein the management service calling response comprises the second data.

For a specific implementation manner of each step in the flow shown in fig. 8, reference may be made to the relevant contents of the foregoing embodiments.

The process shown in fig. 8 provides a mechanism for selecting an open service information manner, and provides a process for performing service invocation based on the first service information associated with the first open manner after the first open manner is selected by the third party as the management service consuming entity. Through the process, the preference of a third party for calling the management service, which is simple and easy to operate, can be met, and an original management service information model and data in an operator can be protected.

In connection with the flow shown in fig. 6 and the flow shown in fig. 7b, fig. 9 illustrates a process of registering and invoking a management service for a management service consuming entity. During the registration process, the management service consuming entity selects a first open mode.

As shown in fig. 9, the process may include the following steps:

901: the management service consuming entity sends a registration request to the open control management functional entity, wherein the registration request comprises first indication information, and the service information open mode indicated by the first indication information is a first open mode.

902: after receiving the registration request, the open control management functional entity processes the first service information (eMnS information) based on the second service (MnS information) according to the first open mode indicated by the first indication information.

903: the method comprises the steps that an open control management function entity sends a registration response to a management Service consumption entity, wherein the registration response comprises first Service information and address information of a Service Discovery providing entity (MnS Discovery Service provider). Optionally, the registration response may further include identification information (e.g., operator ID) of the management service consuming entity.

904: the management service consuming entity sends a service discovery request to the service discovery providing entity according to the address information of the service discovery providing entity obtained in 903, where the service discovery request may include an identity of the management service consuming entity, an eMnS type of a target management service, and identity type information of the management service consuming entity. The identity type information may represent whether the management service consuming entity is a management service consuming entity inside the operator administrative trust domain or a management service consuming entity outside the operator administrative trust domain.

905: the service discovery providing entity judges whether the management service consuming entity is from the inside or outside of the operator management trust domain according to the identity type information of the management service consuming entity, if the management service consuming entity is judged to be from the outside, the subsequent 906 is executed, otherwise, the steps 906 to 908 are skipped, and the 909 is directly executed.

906: the service discovery providing entity sends an authority check request to the open control management function entity, wherein the request can comprise the identification information of the management service consuming entity and the emNS type of the target management service.

907: the open control management function entity checks whether the target management service is in the range of the management service subscribed by the management service consuming entity.

908: and the open control management functional entity judges that the target management service is in the range of the management service signed and used by the management service consumption entity, and returns the service authority check result and the MnS type to the service discovery providing entity.

909: the service discovery providing entity sends the address information of the target management function entity to the management service consuming entity.

910: and the management service consuming entity sends a first management service calling request to the open control management functional entity, wherein the request comprises third service information.

911: and the open control management functional entity performs authority check. This step is an optional step.

912: and the open control management functional entity processes the third service information into fourth service information.

913: and the open control management functional entity sends a second management service calling request to the target management functional entity, wherein the fourth service information can be carried.

914: the target management function entity responds to the second management service invocation request.

For example, if the management service requested to be invoked is performance data measurement or alarm data reporting, the target management function entity returns relevant original data (original data, that is, the first data) to the open control management function entity.

915: if 914 has the first data returned, the open control management function entity executes the conversion from the first data to the second data.

916: and the open control management function entity sends a management service calling response to the management service consuming entity, wherein the management service calling response comprises second data.

The relevant contents in 901 to 903 in the flow shown in FIG. 9 can refer to the relevant contents in 801 to 803 in the flow shown in FIG. 8, and the relevant contents in 910 to 916 can refer to the relevant contents in 804 to 812 in the flow shown in FIG. 8.

For a specific implementation manner of each step in the flow shown in fig. 9, reference may be made to the relevant contents of the foregoing embodiments.

The process shown in fig. 9 provides a mechanism for selecting an open service information manner, and provides a process for performing service invocation based on the first service information associated with the first open manner after the first open manner is selected by the third party as the management service consuming entity. Through the process, the preference of a third party for calling the management service, which is simple and easy to operate, can be met, and an original management service information model and data in an operator can be protected.

In connection with the flow shown in fig. 6 and the flow shown in fig. 7b, fig. 10 illustrates a process of registering and invoking a management service for a management service consuming entity. During the registration process, the management service consuming entity selects the second open mode.

As shown in fig. 10, the process may include the following steps:

1001: the management service consuming entity sends a registration request to the open control management functional entity, wherein the registration request comprises first indication information, and the service information open mode indicated by the first indication information is a second open mode.

1002: after receiving the registration request, the open control management functional entity determines that the open service information is a second service (MnS information) according to a second open mode indicated by the first indication information.

1003: the openness control management function entity sends a registration response to the management Service consuming entity, where the registration response includes the second Service information and address information of a Service Discovery providing entity (MnS Discovery Service provider). Optionally, the registration response may further include identification information (e.g., operator ID) of the management service consuming entity.

1004: the management service consuming entity sends a service discovery request to the service discovery providing entity according to the address information of the service discovery providing entity obtained in 1003, where the service discovery request may include an identity of the management service consuming entity, an MnS type of the target management service, and identity type information of the management service consuming entity. The identity type information may represent whether the management service consuming entity is a management service consuming entity inside the operator administrative trust domain or a management service consuming entity outside the operator administrative trust domain.

1005: the service discovery providing entity judges whether the management service consuming entity is from the inside or outside of the operator management trust domain according to the identity type information of the management service consuming entity, if the management service consuming entity is judged to be from the outside, the subsequent step 1006 is executed, otherwise, the steps 1006 to 1008 are skipped, and the step 1009 is directly executed.

1006: the service discovery providing entity sends a permission check request to the open control management function entity, wherein the permission check request can comprise the identification information of the management service consuming entity and the MnS type of the target management service.

1007: the open control management function entity checks whether the target management service is in the range of the management service subscribed by the management service consuming entity.

1008: and the open control management functional entity judges that the target management service is in the range of the management service signed and used by the management service consumption entity, and returns the service authority check result and the MnS type to the service discovery providing entity.

1009: the service discovery providing entity sends the address information of the target management function entity to the management service consuming entity.

1010: and the management service consuming entity sends a management service calling request to the target management function entity according to the address information of the target management function entity, wherein the request comprises fourth service information. The fourth service request message is a subset of the second service message, and is a service message corresponding to the target management service, for example, the fourth service request message may be an MnS type of the target management service.

The management service invocation request may also include identification information (e.g., operator ID) and identity type information of the management service consuming entity. The identity type information may represent whether the management service consuming entity is a management service consuming entity inside the operator administrative trust domain or a management service consuming entity outside the operator administrative trust domain.

1011: the target management function entity determines whether the management service consumption entity is from inside or outside the operator management trust domain, if the management service consumption entity is from outside, the subsequent step 1012 is executed, otherwise, the steps 1012-1014 are skipped, and the step 1015 is directly executed.

1012: the target management function entity sends an authority check request to the openness control management function entity, wherein the request can comprise the identification information of the management service consumption entity and the MnS type of the target management service.

1013: the open control management function entity checks whether the target management service is in the range of the management service subscribed by the management service consuming entity.

1014: the open control management functional entity judges that the target management service is in the management service range signed and used by the management service consuming entity, and returns the service authority check result to the target management functional entity.

1015: the target management function entity responds to the management service calling request, and if the returned data exist, the target management function entity sends the data to the management service consuming entity.

For a specific implementation manner of each step in the flow shown in fig. 10, reference may be made to the relevant contents of the foregoing embodiments.

The flow shown in fig. 10 provides a mechanism for selecting an open service information manner, and provides a flow for performing a multiplexing call based on the original MnS information after selecting a second open manner as a third party managing a service consuming entity. The preference of a third party for calling the management service accurately and quickly can be met through the process.

Based on the same technical concept, the embodiment of the application also provides a communication device. The communication device may perform the processes performed by the relevant entities in fig. 6, fig. 7a, fig. 7b, fig. 8, fig. 9, or fig. 10. For example, the flow of opening the control management function entity in each of the above-mentioned figures may be performed, or the flow of managing the service consumption entity in each of the figures may be performed, or the flow of managing the service consumption entity in fig. 7a, 7b, 8, 9, or 10 may be performed, or the flow of discovering the service provision entity in fig. 7a, 7b, 8, 9, or 10 may be performed.

As shown in fig. 11, the communication device 1100 may include: processing unit 1101, receiving unit 1102, and transmitting unit 1103. The receiving unit 1102 and the sending unit 1103 are respectively coupled to the processing unit 1101.

When the communication device 1100 executes the process executed by the openness control management function entity in the embodiment of the present application, the functions of the functional modules may include:

the receiving unit 1102 is configured to receive first indication information from a management service consuming entity, where the first indication information is used to indicate a service information opening manner, the service information opening manner is associated with first service information, and the first service information is obtained after processing second service information. The sending unit 1103 is configured to send the first service information to the management service consuming entity.

the receiving unit 1102 is configured to receive first indication information from a management service consuming entity, where the first indication information is used to indicate a service information opening manner, and candidate opening manners of the service information opening manner include a first opening manner and a second opening manner; the sending unit 1103 is configured to send the first service information to the management service consuming entity if the service information open manner indicated by the first indication information is the first open manner, where the first service information is associated with the first open manner, and the first service information is obtained after processing of second service information; and if the service information opening mode indicated by the first indication information is the second opening mode, sending the second service information to the management service consuming entity, wherein the second service information is associated with the second opening mode.

When the communication device 1100 executes the process executed by the management service consuming entity in the embodiment of the present application, the functions of the functional modules may include:

a sending unit 1103 is configured to send first indication information to an open control management function entity, where the first indication information is used to indicate an open mode of service information; the receiving unit 1102 is configured to receive first service information from the openness control management function entity, where the first service information is associated with a service information opening manner indicated by the first indication information, and the first service information is obtained after processing second service information.

When the communication device 1100 executes the procedure of the service discovery providing entity row in the embodiment of the present application, the functions of the functional modules may include:

the receiving unit 1102 is configured to receive identity type information and management service type information from a management service consuming entity; receiving a notification from an open control management function entity, wherein the notification is used for notifying whether the management service corresponding to the management service type information is in a management service authorization range corresponding to the management service consuming entity; the processing unit 1101 is configured to determine whether the management service consuming entity is an untrusted management service consuming entity according to the identity type information; the sending unit 1103 is configured to send the management service type information to the openc management function entity when the processing unit 1101 determines that the management service consuming entity is an untrusted management service consuming entity.

When the communication device 1100 executes the process executed by the management function entity in the embodiment of the present application, the functions of the above function modules may include:

the receiving unit 1102 is configured to receive a request from a management consuming entity, where the request includes identity type information and management service type information of the management consuming entity; the management service consuming entity is used for receiving a management service authorization range corresponding to the management service type information; the processing unit 1101 is configured to determine whether the management service consuming entity is an untrusted management service consuming entity according to the identity type information; the sending unit 1103 is configured to send the management service type information to the openness control management function entity when the processing unit 1101 determines that the management service consuming entity is an untrusted management service consuming entity.

It should be noted that the communication device 1100 can implement the method steps in the method embodiment and achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those of the method embodiment in this embodiment are omitted here.

For ease of understanding, only the structure of the communication apparatus 1200 required to perform the method of the present application is shown in fig. 12, and the present application does not limit the communication apparatus to have more components. The communication apparatus 1200 may be configured to perform the steps performed by the openness control management function entity or the management service consuming entity or the management function entity or the service discovery providing entity in the above method embodiments. The communication device 1200 may include a communication interface 1201, a memory 1202, and a processor 1203. The communication interface 1201 may be used for communication by a communication device, such as for sending or receiving signals. The memory 1202 is coupled to the processor 1203 and may be used for storing programs and data necessary for the communication device 1200 to implement various functions. The processor 1203 is configured to support the communication apparatus 1200 to perform the processing functions performed by the open control management function entity or the management service consuming entity or the management function entity or the service discovery providing entity in the above-described method. The memory 1202 and the processor 1203 may be integrated or may be independent of each other.

Illustratively, the communication interface 1201 may be a communication port, such as a communication port (or interface) for communication between network elements. The communication interface 1201 may also be referred to as a transceiving unit or a communication unit. The processor 1203 may be implemented by a processing chip or processing circuit. The communication interface 1201 can receive or transmit information in a wireless manner or a wired manner.

For example, when the communication apparatus 1200 is used as an open control management function entity, the first indication information sent by the management service consuming entity may be acquired based on the communication interface 1201, and further, the service information associated with the service information open mode indicated by the first indication information may be sent to the management service consuming entity through the communication interface 1201. In addition, during the management service calling process, the communication interface 1201 can also interact with the management service consuming entity, the management function entity, the service discovery providing entity and the like to perform relevant information.

For another example, when the communication apparatus 1200 is used as a management service consuming entity, the first indication information may be sent to the open control management function entity based on the communication interface 1201, and further, the service information associated with the service information open mode indicated by the first indication information may be received from the open control management function entity through the communication interface 1201. In addition, during the management service calling process, the communication interface 1201 can also interact with the open control management function entity, the service discovery providing entity and the like to perform related information.

In addition, according to the actual use requirement, the communication device provided by the embodiment of the present application may include a processor, and the processor invokes an external transceiver and/or a memory to implement the above functions or steps or operations. The communication device may also include a memory that is called by the processor and executes programs stored in the memory to implement the functions or steps or operations described above. Alternatively, the communication device may also include a processor and a transceiver (or a communication interface), and the processor calls and executes a program stored in an external memory to implement the above functions or steps or operations. Alternatively, the communication device may also include a processor, memory, and a transceiver.

Based on the same concept as the method embodiments, an embodiment of the present application further provides a computer-readable storage medium, on which program instructions (or computer programs, or instructions) are stored, and when the program instructions are executed by a processor, the computer performs the operations performed by the openness control management function entity or the management service consuming entity or the management function entity or the service discovery providing entity in any possible implementation manner of the method embodiments and the method embodiments.

Based on the same concept as the method embodiments, the present application further provides a computer program product, which includes program instructions, and when the computer program product is called by a computer and executed, the computer program product may enable the computer to implement the operations performed by the open control management functional entity or the management service consuming entity or the management functional entity or the service discovery providing entity in any one of the possible implementation manners of the method embodiments and the method embodiments.

Based on the same concept as the method embodiment, the present application further provides a chip or a chip system, where the chip is coupled to the transceiver and is used to implement the operations executed by the open control management function entity or the management service consuming entity or the management function entity or the service discovery providing entity in any possible implementation manner of the method embodiment and the method embodiment. The chip system may include the chip, as well as components including memory, communication interfaces, and the like.

Based on the same concept as the method embodiment, the embodiment of the present application further provides a communication system, where the communication system includes an open control management functional entity and a management service consuming entity, and may further include a management functional entity, and further may further include a service discovery providing entity.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method of communication, comprising:

receiving first indication information from a management service consumption entity, wherein the first indication information is used for indicating a service information opening mode, the service information opening mode is associated with first service information, and the first service information is obtained after processing second service information;

sending the first service information to the management service consuming entity.

2. The method of claim 1, wherein the first service information comprises:

partial information selected from the second service information; and/or

And the second service information is converted to obtain information.

3. The method of any of claims 1-2, wherein the second service information is used to invoke a management service.

4. A method according to any of claims 1-3, wherein after said sending said first service information to said management service consuming entity, said method further comprises:

receiving a first request from the management service consuming entity, wherein the first request includes third service information, the third service information corresponds to a target management service requested to be called by the management service consuming entity, and the third service information is at least one of information included in the first service information;

and sending a second request to a target management function entity for providing the target management service, wherein the second request comprises fourth service information, the fourth service information is obtained after the third service information is processed, and the fourth service information is at least one of information included in the second service information.

5. The method of claim 4, wherein after sending the second request to a target management function entity for providing the target management service, the method further comprises:

receiving first data from the target management function entity;

and sending second data to the management service consumption entity, wherein the second data is obtained after the first data is converted.

6. The method of any one of claims 1-5, further comprising:

and sending the address information of the service discovery providing entity to the management service consuming entity.

7. The method of claim 6, wherein the method further comprises:

receiving management service type information from a service discovery providing entity, wherein the management service type information is management service type information included in the first service information;

and informing the discovery service providing entity whether the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity.

8. The method according to any of claims 1-7, wherein the candidate open manners of the service information open manners include a first open manner and a second open manner, the first open manner being associated with the first service information, the second open manner being associated with the second service information;

the service information open mode indicated by the first indication information is the first open mode.

9. A method of communication, comprising:

sending first indication information to an open control management function entity, wherein the first indication information is used for indicating a service information open mode;

and receiving first service information from the open control management function entity, wherein the first service information is associated with a service information open mode indicated by the first indication information, and the first service information is obtained after processing second service information.

10. The method of claim 9, wherein the first service information comprises:

partial information selected from the second service information; and/or

And the second service information is converted to obtain information.

11. A method according to any of claims 9-10, wherein the second service information is used to invoke a management service.

12. The method of any one of claims 9-11, wherein after receiving the first service information from the opencontrol management function entity, the method further comprises:

and sending a first request to the openness control management functional entity, wherein the first request comprises third service information, the third service information corresponds to a target management service called by the request, and the third service information is at least one of information included in the first service information.

13. The method of claim 12, wherein after the sending the first request to the opencontrol management function entity, the method further comprises:

receiving second data from the openness control management function entity, wherein the second data is obtained after conversion of first data, and the first data is received by the openness control management function entity from a target management function entity for providing the target management service.

14. The method of any one of claims 9-13, further comprising:

receiving address information of a service discovery providing entity from the open control management function entity;

sending identity type information and management service type information of a management service consuming entity to a service discovery providing entity corresponding to the address information, wherein the management service type information is management service type information included in the first service information;

receiving a notification from the service discovery providing entity, where the notification includes address information of a target management function entity, the target management function entity is configured to provide a management service corresponding to the management service type information, and the notification is configured to notify that the management service corresponding to the management service type information is within a management service authorization range corresponding to the management service consuming entity.

15. A method of communication, comprising:

the management service consuming entity sends first indication information to an open control management functional entity, wherein the first indication information is used for indicating a service information open mode;

the open control management functional entity sends first service information to the management service consuming entity according to the first indication information, wherein the first service information is obtained after second service information is processed, and the first service information is associated with the service information open mode;

the management service consuming entity receives the first service information.

16. The method of claim 15, wherein the first service information comprises:

partial information selected from the second service information; and/or

And the second service information is converted to obtain information.

17. A method according to any of claims 15-16, wherein the second service information is used to invoke a management service.

18. The method of any one of claims 15-17, further comprising:

after receiving the first service information, the management service consuming entity sends a first request to the open control management functional entity, where the first request includes third service information, the third service information corresponds to a target management service called by the request, and the third service information is at least one of information included in the first service information;

after receiving the first request, the openness control management functional entity sends a second request to a target management functional entity for providing the target management service, where the second request includes fourth service information, the fourth service information is obtained after processing the third service information, and the fourth service information is at least one of information included in the second service information.

19. The method of claim 18, wherein the method further comprises:

the open control management functional entity receives first data from the target management functional entity and sends second data to the management service consuming entity, wherein the second data is obtained after the first data is converted;

the management service consuming entity receives the first data.

20. The method of any one of claims 15-19, further comprising:

the open control management functional entity sends the address information of a service discovery providing entity to the management service consuming entity;

the management service consuming entity receives address information of the service discovery providing entity.

21. The method of claim 20, wherein the method further comprises:

the management service consuming entity sends identity type information and management service type information of the management service consuming entity to a service discovery providing entity corresponding to the address information of the service discovery providing entity, wherein the management service type information is management service type information included in the first service information;

if the service discovery providing entity determines that the management service consuming entity is an untrusted management service consuming entity according to the identity type information, the service discovery providing entity sends the management service type information to the open control management function entity;

the open control management functional entity informs the service discovery providing entity whether the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity according to the management service type information;

if the management service corresponding to the management service type information is in the management service authorization range corresponding to the management service consuming entity, the service discovery providing entity sends address information of a target management function entity to the management service consuming entity, wherein the target management function entity is a target management function entity used for providing the target management service requested to be called by the management service consuming entity;

and the management service consumption entity receives the address information of the target management function entity.

22. The method according to any of claims 15-21, wherein the candidate open manners of the service information open manners include a first open manner and a second open manner, the first open manner being associated with the first service information, the second open manner being associated with the second service information;

23. A communication system, comprising: a management service consumption entity and an open control management function entity;

the management service consuming entity is used for sending first indication information to the open control management functional entity, wherein the first indication information is used for indicating the service information open mode; receiving first service information sent by the open control management function entity;

the open control management functional entity is configured to send first service information to the management service consuming entity according to the first indication information, where the first service information is obtained after processing of second service information, and the first service information is associated with the service information open mode.

24. The communication system of claim 23, wherein the first service information comprises:

partial information selected from the second service information; and/or

And the second service information is converted to obtain information.

25. A communication system according to any of claims 23-24, wherein the second service information is used to invoke a management service.

26. The communication system according to any of claims 23-25, characterized by:

the management service consuming entity is further configured to send a first request to the open control management functional entity after receiving the first service information, where the first request includes third service information, the third service information corresponds to a target management service called by the request, and the third service information is at least one of information included in the first service information;

the openness control management function entity is further configured to send a second request to a target management function entity for providing the target management service after receiving the first request, where the second request includes fourth service information, the fourth service information is obtained after processing the third service information, and the fourth service information is at least one of information included in the second service information.

27. The communication system of claim 26, wherein:

the open control management functional entity is further configured to receive first data from the target management functional entity and send second data to the management service consuming entity, where the second data is obtained after the first data is converted;

the management service consuming entity is further configured to receive the first data.

28. The communication system according to any of claims 23-27, wherein:

the open control management function entity is also used for sending the address information of the service discovery providing entity to the management service consuming entity;

the management service consuming entity is also used for receiving the address information of the service discovery providing entity.

29. The communication system of claim 28, wherein the communication system further comprises a service discovery providing entity;

the management service consuming entity is further configured to send identity type information of the management service consuming entity and management service type information to a service discovery providing entity corresponding to the address information of the service discovery providing entity, where the management service type information is management service type information included in the first service information; and receiving address information of a target management function entity from the service discovery providing entity;

the service discovery providing entity is used for sending the management service type information to the open control management function entity if the management service consuming entity is determined to be an untrusted management service consuming entity according to the identity type information; if the management service corresponding to the management service type information is determined to be within the management service authorization range corresponding to the management service consuming entity according to the notification from the open control management function entity, sending the address information of the target management function entity to the management service consuming entity, wherein the target management function entity is a target management function entity for providing the target management service requested to be called by the management service consuming entity;

the open control management function entity is further configured to notify the service discovery providing entity whether the management service corresponding to the management service type information is within the management service authorization range corresponding to the management service consuming entity according to the management service type information.

30. The communication system according to any of claims 23-29, wherein the candidate open manners of the service information open manners include a first open manner and a second open manner, the first open manner being associated with the first service information, the second open manner being associated with the second service information;

31. A communications apparatus, comprising: a processing unit and a receiving unit and a transmitting unit coupled to the processing unit;

the receiving unit is configured to receive first indication information from a management service consuming entity, where the first indication information is used to indicate a service information opening manner, the service information opening manner is associated with first service information, and the first service information is obtained after processing second service information;

the sending unit is configured to send the first service information to the management service consuming entity.

32. A communications apparatus, comprising: a processing unit and a receiving unit and a transmitting unit coupled to the processing unit;

the sending unit is configured to send first indication information to an open control management function entity, where the first indication information is used to indicate a service information open mode;

the receiving unit is configured to receive first service information from the openness control management function entity, where the first service information is associated with a service information opening manner indicated by the first indication information, and the first service information is obtained after processing second service information.

33. A communications apparatus, comprising: one or more processors; the one or more memories store one or more computer programs, the one or more computer programs comprising instructions, which when executed by the one or more processors, cause the communication device to perform the method of any of claims 1-8.

34. A communications apparatus, comprising: one or more processors; the one or more memories store one or more computer programs, the one or more computer programs comprising instructions, which when executed by the one or more processors, cause the communication device to perform the method of any of claims 9-14.

35. A computer-readable storage medium, comprising a computer program which, when run on an electronic device, causes the electronic device to perform the method of any of claims 1-8 or to perform the method of any of claims 9-14.

36. A computer program product, characterized in that it, when run on an electronic device, causes the electronic device to perform the method of any of claims 1-8 or to perform the method of any of claims 9-14.

37. A chip system, comprising: a memory for storing a computer program; a processor; when the processor calls and runs the computer program from the memory, the electronic device with the chip system installed is caused to execute the method according to any one of claims 1-8 or the method according to any one of claims 9-14.