Intention acquisition method and device, computer equipment and storage medium

Abstract

The embodiment of the invention discloses an intention acquisition method and device, computer equipment and a storage medium, and belongs to the technical field of communication. In the embodiment of the invention, a user terminal can obtain scene information of a plurality of scenes corresponding to a first service from an intention management server, and the scene information of each scene comprises intention setting reference information of the corresponding scene. Based on this, the user terminal can set the reference information according to the intention of each scene, obtain the intention expectation in the first scene indicated by the scene demand information of the user, and further obtain the first intention. Therefore, the intention acquisition method provided by the embodiment of the invention supports intention setting based on the scene, and the user provides the scene demand information of the first service, so that intention expectation setting in a certain scene can be realized, the capability requirement on the user is reduced, the probability of occurrence of the problem of inaccurate intention setting is also reduced, and the user experience is improved. And the intention setting efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an intent acquisition method, apparatus, computer equipment and storage medium. Background Art

[0002] The standard for intent-driven mobile network management services was proposed in the 3rd Generation Partnership Project (3GPP). Based on this standard, after obtaining the user's intent, the user terminal can send the intent to the intent management server maintained by the mobile management service provider through the intent interface, and the intent management server executes the intent and feeds back the execution result. Among them, the intent can be used to indicate the expectation for a certain service or network management work. An intent may include at least one intent expectation, and an intent expectation may include an expected object, an expected target, and an expected context, wherein the expected object refers to the object to which the intent expectation applies, the expected target refers to the target that the expected object is expected to achieve, and the expected context may include the constraints of the intent expectation.

[0003] At present, users can input the desired object, desired target and desired context in the user terminal according to their own needs and prior knowledge, and the user terminal can generate the user's intention using the intention interface according to the desired object, desired target and desired context. It can be seen that the current intention setting method has high requirements on the user's ability, which easily leads to the problem of inaccurate intention setting and low setting efficiency. Summary of the invention

[0004] The present application provides an intent acquisition method, apparatus, computer device and storage medium, which can improve the accuracy and efficiency of intent setting.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions:

[0006] In a first aspect, a method for acquiring intent is provided, which is applied to a user terminal, and the method includes: receiving scene information of multiple scenes corresponding to a first service sent by an intent management server, the scene information of each scene including intent setting reference information of the corresponding scene; based on the intent setting reference information of the multiple scenes and the user's first scene requirement information, acquiring a first intent of the first service, the first intent including the intent expectation under the first scene among the multiple scenes, and the first scene requirement information is used to indicate the first scene.

[0007] In the present application, the user terminal can obtain the scene information of multiple scenes corresponding to the first service from the intent management server, wherein the scene information of each scene includes the intention setting reference information of the corresponding scene. Based on this, the user terminal can obtain the intention expectation in the first scene indicated by the user's scene requirement information according to the intention setting reference information of each scene, and then obtain the first intention. It can be seen that the intent acquisition method provided in the present application supports scene-based intent setting, and the user can provide the scene requirement information of the first service to realize the setting of the intention expectation in a certain scene, which reduces the ability requirements of the user, reduces the probability of inaccurate intent setting, and improves the efficiency of intent setting.

[0008] Optionally, before receiving scene information of multiple scenes corresponding to a first service sent by an intent management server, a scene information query request is sent to the intent management server in response to a user's scene information query instruction, and the scene information query request includes an identifier of the first service.

[0009] In the present application, the scene information query instruction can be triggered by the user, and the user terminal sends a scene information query request to the intent management server based on the user's scene information query instruction, so as to obtain the scene information of multiple scenes corresponding to the first business. It can be seen that the present application supports users to query the scene information of scenes supported by the intent management server based on their own needs.

[0010] Optionally, the scene information of each scene also includes a scene identifier of the corresponding scene, and the intention setting reference information of each scene includes at least one recommended expected target for the corresponding scene. On this basis, the implementation process of obtaining the first intention of the first business based on the intention setting reference information of the multiple scenes and the user's first scene requirement information may include: displaying the scene identifiers of the multiple scenes; receiving the scene identifier of the first scene input by the user, the first scene requirement information including the scene identifier of the first scene; displaying at least one recommended expected target for the first scene; in response to the user's selection operation of the first expected target among the at least one recommended expected target of the first scene, generating the intention expectation under the first scene based on the scene identifier of the first scene and the first expected target; generating the first intention of the first business based on the intention expectation under the first scene.

[0011] In the present application, the user terminal can display at least one recommended expected target in the scene information of the first scene, and the user can refer to the at least one recommended expected target to set the intended expected target of the first scene, thereby improving the efficiency of intention setting.

[0012] In addition, at least one recommended expected goal for the first scenario may be a personalized expected goal that is applicable to the first scenario but may not be applicable to other scenarios. On this basis, the user can achieve differentiated settings for intention expectations in different scenarios based on the recommended personalized expected goal for the first scenario.

[0013] Optionally, the intention setting reference information for each scenario also includes at least one recommended business strategy and recommended business policy constraint for the corresponding scenario. The process of generating the implementation of the intention expectation for the first scenario based on the scenario identifier of the first scenario and the first expected goal may include: displaying at least one recommended business strategy for the first scenario; in response to a user's selection operation of a first recommended business strategy among the at least one recommended business strategy for the first scenario, generating an expected context for the first scenario based on the first recommended business strategy and the recommended business policy constraint; based on the scenario identifier, expected context and the first expected goal of the first scenario, generating the intention expectation for the first scenario, the intention expectation for the first scenario including the scenario identifier, expected context and the first expected goal of the first scene.

[0014] In the present application, the user terminal can also display at least one recommended business strategy under the first scenario, and the user can select the business strategy he or she wants to use to implement the first business from the at least one recommended business strategy. On this basis, the user terminal automatically generates the expected context based on the business strategy and business policy constraints selected by the user, thereby realizing the intelligent setting of the expected context, reducing the ability requirements for the user, and improving the efficiency of intent setting.

[0015] Optionally, the first expected goal is a personalized expected goal for the first scenario, and the method further includes: receiving a general expected indicator of the first business in the multiple scenarios input by a user; on this basis, the implementation process of generating the intention expectation in the first scenario based on the scenario identifier of the first scenario and the first expected goal may include: generating the intention expectation in the first scenario based on the scenario identifier of the first scenario, the first expected goal and the general expected goal.

[0016] In the present application, the first service may also have a general expected target in each scenario. Based on this, when the first expected target selected by the user is a personalized expected target in the first scenario, the user terminal may also receive the general expected target of the first service input by the user, and then generate the intention expectation in the first scenario based on the first expected target and the general expected target, thereby achieving accurate setting of the intention expectation in the first scenario.

[0017] Optionally, the scene information of each scene also includes scene characteristics of the corresponding scene. The intention setting reference information based on the multiple scenes and the user's first scene requirement information, the implementation process of obtaining the first intention of the first business may include: obtaining the engineering parameter data of multiple business objects in the same scene applicable to the first business, the first scene requirement information including the engineering parameter data of the multiple business objects; determining the characteristics of the scenes in which the multiple business objects are located based on the engineering parameter data of the multiple business objects; determining the first scene from the multiple scenes whose scene characteristics match the characteristics of the scenes in which the multiple business objects are located; and obtaining the first intention of the first business based on the intention setting reference information of the first scene.

[0018] In this application, users can provide the user terminal with the engineering parameter data of multiple business objects in the same scene as their own scene requirement information to express their own scene requirements. On this basis, since the scene information provided by the intent management server may include scene features, the user terminal can determine the scene features of the scene based on the engineering parameter data of multiple business objects in the scene, and then determine the first scene that matches the scene among the multiple scenes supported by the intent management server, so as to realize intelligent recognition of the scene.

[0019] Optionally, the intention setting reference information of the first scene includes the intention expectation in the first scene, and the intention expectation in the first scene includes the scene identifier of the first scene and the expected target of the first scene.

[0020] In the present application, the intention setting reference information for the first scene can be the pre-set intention expectation under the first scene. In this way, after the user terminal determines the first scene based on the scene requirement information provided by the user, it can directly generate the first intention based on the intention expectation under the first scene, without the need for the user to set it himself, thereby improving the efficiency of intent setting.

[0021] Optionally, the method further includes: sending a first intention of the first service to the intention management server; and receiving a report on the implementation effect of the first intention fed back by the intention management server.

[0022] Optionally, sending the first intent of the first service to the intent management server includes: sending the first intent of the first service to the intent management server through an intent interface, the intent interface including an expected scenario list attribute, and the expected scenario list attribute is used to represent the scenario indicated by the user's scenario requirement information.

[0023] In this application, a new expected scene list attribute is added to the intent interface, and the expected scene list attribute can be used to represent the scene indicated by the user's scene requirement information. In this way, the user terminal can use the intent interface to send an intent expectation containing the identifier of the expected scene set by the user to the intent management server. It can be seen that in this application, by adding a new expected scene list attribute to the intent interface, it can support users to set intents for at least one scene they expect.

[0024] In a second aspect, a method for acquiring intent is provided, which is applied to an intent management server, and the method includes: sending scene information of multiple scenes corresponding to a first service to a user terminal, the scene information of each scene including intent setting reference information of the corresponding scene; receiving a first intent of the first service, and executing the first intent, the first intent being obtained by the user terminal based on the intent setting reference information of the multiple scenes and the user's first scene requirement information, the first intent including the intent expectation under the first scene among the multiple scenes, and the first scene requirement information being used to indicate the first scene.

[0025] In the present application, the intent management server can provide the user terminal with scene information of multiple scenes of the first service. Among them, the scene information of each scene includes the intention setting reference information of the corresponding scene. Based on this, the user terminal can obtain the intention expectation in the first scene indicated by the user's scene requirement information according to the intention setting reference information of each scene, and then obtain the first intention. It can be seen that the intent acquisition method provided in the present application supports scene-based intent setting, and the user can provide the scene requirement information of the first service to realize the setting of the intention expectation in a certain scene, which reduces the ability requirements of the user, reduces the probability of inaccurate intent setting, and improves the efficiency of intent setting.

[0026] Optionally, the implementation process of sending scene information of multiple scenes corresponding to the first service to the user terminal may include: sending the scene information of the multiple scenes to the user terminal through an intent processing function interface, the intent processing function interface including a supported scene list attribute, and the supported scene list attribute is used to indicate the scenes supported by the intent management server.

[0027] In this application, the intent management server can create and manage the intent processing function interface, which includes a supported scene list attribute, which can be used to indicate the scenes supported by the intent management server. Based on this, the intent management server can provide the user with the scene information of the scenes supported by itself through the intent processing function interface, so that the user can implement the setting of the scene-based intent expectation based on the scene information of the scenes supported by the intent management server.

[0028] Optionally, the implementation process of receiving the first intention of the first service may include: receiving the first intention through an intention interface, the intention interface including an expected scenario list attribute, and the expected scenario list attribute is used to represent the scenario indicated by the user's scenario requirement information.

[0029] In the present application, a new expected scene list attribute is added to the intent interface, and the expected scene list attribute can be used to represent the scene indicated by the user's scene requirement information. In this way, the user terminal can use the intent interface to send an intent expectation containing the identifier of the expected scene set by the user to the intent management server. Correspondingly, the intent management server can receive and parse the intent containing the intent expectation of the scene through the intent interface. It can be seen that in this application, by adding a new expected scene list attribute to the intent interface, it can support users to set intents for at least one scene they expect.

[0030] Optionally, the intended expectation in the first scenario includes an identifier of the first scenario and an expected target of the first scenario.

[0031] Optionally, the implementation process of executing the first intention may include: determining a first desired object within the first scene based on an identification of the first scene; generating a first business policy based on an expected goal of the first scene; and sending the first business policy to the first desired object, where the first desired object is used to execute the first business policy.

[0032] In the present application, when users set intents based on scenarios, they do not need to set the expected objects in the intent expectations. The intent management server can automatically determine the expected objects in the corresponding scenarios based on the identification of the expected scenarios in the intent expectations, thereby improving the efficiency of intent setting.

[0033] Optionally, the intention expectation in the first scenario also includes an expected context, and the implementation process of generating the first business policy based on the expected goal of the first scenario may include: generating the first business policy based on the expected goal of the first scenario and the expected context.

[0034] Optionally, the method further includes: receiving an execution result of the first business policy sent by the first desired object; and sending a report on the implementation effect of the first intention to the user terminal based on the execution result of the first business policy.

[0035] Optionally, there are multiple first scenarios, and the process of implementing the first intention may include: detecting whether there is a conflict between the intention expectations under the multiple first scenarios; if there is no conflict between the intention expectations under the multiple first scenarios, executing the first intention.

[0036] In the present application, after parsing the intention expectation in the first scenario included in the first intention, the intention management server can also perform intention conflict detection to avoid the situation where the intention cannot be executed due to the conflict of intention expectation.

[0037] In a third aspect, an intention acquisition device is provided, the intention acquisition device comprising at least one module, and the at least one module is used to execute the intention acquisition method described in the first aspect or the second aspect.

[0038] In a fourth aspect, a computer device is provided, the computer device comprising a processor, the processor being used to execute at least one program instruction or code stored in a memory to implement the intention acquisition method described in the first aspect or the second aspect above.

[0039] In a fifth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium. When the instructions are executed on a computer device, the computer device executes the intention acquisition method described in the first aspect or the second aspect.

[0040] In a sixth aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer device, the computer device executes the intention acquisition method described in the first aspect or the second aspect above.

[0041] The technical effects obtained by the above-mentioned third, fourth, fifth and sixth aspects are similar to the technical effects obtained by the corresponding technical means in the first and second aspects, and will not be repeated here.

[0042] In an embodiment of the present application, for a certain service, such as the first service, the user terminal can obtain the scene information of multiple scenes corresponding to the first service from the intent management server, wherein the scene information of each scene includes the intention setting reference information of the corresponding scene. Based on this, the user terminal can obtain the intention expectation in the first scene indicated by the user's scene requirement information according to the intention setting reference information of each scene, and then obtain the first intention. It can be seen that the intent acquisition method provided in the embodiment of the present application supports scene-based intent setting, and the user can provide the scene requirement information of the first service to realize the setting of the intention expectation in a certain scene, which reduces the ability requirements of the user, reduces the probability of inaccurate intent setting, and improves the efficiency of intent setting. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 A system architecture diagram of an intent acquisition method provided in an embodiment of the present application;

[0044] Figure 2A schematic diagram of the structure of a computer device provided in an embodiment of the present application;

[0045] Figure 3 A flowchart of a method for acquiring intent provided in an embodiment of the present application;

[0046] Figure 4 A schematic diagram of a user interacting with a user terminal to query scene information provided in an embodiment of the present application;

[0047] Figure 5 A schematic diagram of an intention expectation of a user interacting with a user terminal to set a scene provided in an embodiment of the present application;

[0048] Figure 6 A flowchart of another method for acquiring intent provided in an embodiment of the present application;

[0049] Figure 7 An example diagram of an intent acquisition method provided in an embodiment of the present application applied to a network energy-saving service;

[0050] Figure 8 An example diagram of another intent acquisition method provided in an embodiment of the present application applied to a network energy-saving service;

[0051] Fig. 9 A schematic diagram of the structure of an intention acquisition device provided in an embodiment of the present application;

[0052] Fig.10 A schematic diagram of the structure of another intention acquisition device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] In order to make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0054] Before explaining the embodiments of the present application in detail, the application scenarios involved in the embodiments of the present application are first introduced.

[0055] As the architecture of mobile networks becomes more flexible and the services they support become more diverse, the management of mobile networks becomes more and more difficult. Based on this, 3GPP proposed the standard for intent-driven mobile network management services. The so-called intent-driven mobile network management service refers to the management of mobile networks based on user expectations. The standard for intent-driven mobile network management services provides standard intent interfaces and intent processing function interfaces. The user terminal can complete the issuance, confirmation, execution and obtain the results of intent execution with the intent management server through the above-mentioned various interfaces.

[0056] At present, based on the intent interface provided in the standard, an intent may include at least one intent expectation, and an intent expectation may include an expected object, an expected target, and an expected context, wherein the expected object refers to the object to which the intent expectation applies, the expected target refers to the target that the expected object is expected to achieve, and the expected context may include the constraints of the intent expectation. Based on this, the user can input the expected object, the expected target, and the expected context in the user terminal according to his own business needs and prior knowledge. The user terminal generates the corresponding intent expectation using the intent interface according to the expected object, the expected target, and the expected context input by the user, and then generates the user's intention based on the intention expectation. Afterwards, the user's intention is sent to the intent management server through the intent interface. After receiving the user's intention, the intent management server parses the user's intention based on the intent interface, and generates a business policy for achieving the user's intention. Afterwards, the business policy is sent to the expected object in the user's intention, and the expected object executes the business policy in order to achieve the user's intention.

[0057] It is worth noting that, at present, some types of mobile network management services often correspond to a variety of different scenarios, and users have different service requirements in different scenarios. For example, taking the network energy-saving service as an example, since the mobile network can be deployed in a variety of scenarios such as railways, urban areas, suburbs, and villages, and the characteristics of the mobile networks in different scenarios are different, users have different energy-saving requirements for mobile networks in different scenarios. However, since the various interfaces provided in the current standards do not support the relevant settings of the scene, the user cannot set the intention through the setting of the scene of a certain service. Based on this, an embodiment of the present application provides an intention acquisition method, in which, for a certain service, such as a first service, a user terminal can obtain the scene information of multiple scenes corresponding to the first service from the intention management server, wherein the scene information of each scene includes the intention setting reference information of the corresponding scene. Based on this, the user terminal can obtain the intention expectation under the first scene indicated by the user's scene demand information according to the intention setting reference information of each scene, and then obtain the first intention. It can be seen that the intent acquisition method provided in the embodiment of the present application supports the setting of intent through the setting of business scenarios, and the user can provide the scenario requirement information of the first business to achieve the setting of the expected intent in a certain scenario, which reduces the ability requirements of the user, reduces the probability of inaccurate intent problems, and improves the efficiency of intent setting.

[0058] Next, the system structure involved in the intention acquisition method provided in the embodiment of the present application is introduced.

[0059] From the above introduction, it can be seen that the intention acquisition method provided in the embodiment of the present application can be mainly applied to mobile network management services. Next, the system architecture applied by the intention acquisition method provided in the embodiment of the present application is introduced by taking the network energy saving service applied in the wireless communication system as an example. Figure 1 The system includes a user terminal 101, an intent management server 102 and a network element 103. A wireless communication connection is established between the user terminal 101 and the intent management server 102. A communication connection is established between the intent management server 102 and the network element 103.

[0060] In an embodiment of the present application, the user terminal 101 can obtain the scene information of multiple scenes corresponding to the network energy-saving service supported by the intent management server, and the scene information of each scene includes the intention setting reference information of the corresponding scene; based on the intention setting reference information of multiple scenes and the scene demand information of the user, the intention of the network energy-saving service is obtained, and the intention of the network energy-saving service includes the intention expectation under the first scene in multiple scenes, and the scene demand information is used to indicate the first scene. Afterwards, the user terminal 101 can send the intention of the network energy-saving service to the intent management server 102. Among them, the user terminal 101 refers to the terminal corresponding to the intent management service consumer, and the intent management service consumer is the user who provides the scene demand information mentioned above, and the user can be the operator of the network.

[0061] After receiving the intention of the network energy-saving service, the intent management server 102 can translate the intention and execute the intention to obtain a service policy for implementing the intention, and send the service policy to the network element 103, which is executed by the network element 103. The intent management server can be a server maintained by the intent management service producer.

[0062] After executing the service policy, the network element 103 may return the execution result of the intent to the intent management server 102. The network element 103 is a device in the network operated by the user, and the network element 103 is the desired object in the intent of the network energy-saving service.

[0063] It should be noted that the user terminal 101 mentioned above may be, for example, a smart phone, a tablet computer, a personal computer, etc. In the embodiment of the present application, the device for realizing the function of the terminal may be referred to as a terminal. Alternatively, a device capable of supporting the terminal to realize the function may be installed in the terminal, for example, the device may be a chip system. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0064] The above-mentioned intention management server 102 can be a separate physical server, or a server cluster, or a cloud server.

[0065] The above-mentioned network element 103 may refer to a base station (BS) in a wireless communication system. Among them, the base station may have various forms, such as a macro base station, a micro base station, a relay station and an access point. Exemplarily, when the communication system is a 5G NR communication system, the network element 103 may be a base station in 5G, wherein the base station in 5G may also be referred to as a transmission reception point (TRP) or a next-generation base station (generation node B, gNB). When the communication system is an LTE communication system, the network element 103 may be an evolved base station (evolved node B, eNB). Of course, the above-mentioned network element 103 may also be other devices in the wireless communication system, such as a core network device.

[0066] It is worth noting that the intent acquisition method provided in the embodiment of the present application can also be applied to other services in mobile network management. Correspondingly, depending on the service, the expected object in the intent set by the user is also different. Therefore, network element 103 may also be other devices, and the embodiment of the present application does not limit this.

[0067] Figure 2 The user terminal or the intention management server involved in the embodiment of the present application can be Figure 2 The computer device shown is implemented. Figure 2 As shown, the computer device may include at least one processor 201, a communication bus 202, a memory 203 and at least one communication interface 204. It should be noted that: Figure 2 The device structure shown does not constitute a limitation on the computer device. The computer device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which is not limited in the embodiments of the present application. Figure 2 A detailed introduction to the various components of computer equipment:

[0068] Processor 201 is the control center of the computer device, which can be a processor or a general term for multiple processing elements. For example, processor 201 can be a general-purpose central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application, such as: one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (field programmable gate array, FPGA). Among them, processor 201 can perform various functions of the computer device by running or executing software programs stored in memory 203, and calling data stored in memory 203. For example, the actions of the user terminal or the intent management server in each embodiment described below can be executed by the processor calling the data in the memory.

[0069] As an embodiment, the processor 201 may include one or more CPUs, such as Figure 2 CPU0 and CPU1 are shown in the figure.

[0070] As an example, a computer device may include multiple processors, such as Figure 2 201 and processor 205 shown in FIG. Each of these processors may be a single-CPU processor or a multi-CPU processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0071] The communication bus 202 may include a path to transmit information between the above components. The communication bus 202 may be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 2 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0072] The memory 203 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 203 may exist independently and be connected to the processor 201 via the communication bus 202. The memory 203 may also be integrated with the processor 201. Among them, the memory 203 is used to store the software program that executes the solution provided in the embodiment of the present application, and is controlled and executed by the processor 201.

[0073] The communication interface 204 is used to communicate with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), etc. The communication interface 204 may include a receiving unit to implement a receiving function, and a sending unit to implement a sending function.

[0074] As an embodiment, the computer device may further include an output device 206 and an input device 207. The output device 206 communicates with the processor 201 and may display information in a variety of ways. For example, the output device 206 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 207 communicates with the processor 201 and may receive input in a variety of ways. For example, the input device 207 may be a mouse, a keyboard, a touch screen device, or a sensor device.

[0075] The above-mentioned computer device may be a general-purpose computer device or a special-purpose computer device, for example, a desktop computer, a portable computer, a network server, etc., which is not limited in the present embodiment of the application.

[0076] Next, some nouns involved in the embodiments of the present application are introduced.

[0077] 1. Intention

[0078] Intent refers to the expectation of requirements, goals and constraints for a specific service or network management workflow. In other words, intent is the expectation put forward by users for certain services or network management tasks.

[0079] 2. Intent Interface

[0080] The intent interface is a standard interface for intent-driven mobile network management services proposed by 3GPP and is used to describe intent.

[0081] The intent interface may include multiple attributes, which may include at least one intent expectation (intentExpectation), a user label (userlabel), an intent context (intentContexts), and an intent fulfillment effect report (intentFulfillmentInfo). Among them, the intent expectation is used to describe the user's specific requirements. The user label is used to uniquely identify the user. The intent context is used to describe the constraints of the intent, which are the constraints when the entire intent is applied. The intent fulfillment effect report is used to describe the implementation status of the intent and the corresponding reasons.

[0082] Next, each attribute in the intent interface is introduced in detail.

[0083] (1) Intent expectations may include the following attributes:

[0084] ExpectationID: used to uniquely identify an intent expectation.

[0085] ExpectationVerb: used to describe the characteristics of the intent expectation. For example, the expectationVerb can be ensure, which indicates that the intent expectation is to ensure that a certain goal is achieved. Alternatively, the expectationVerb can be deliver, which indicates that the intent expectation is to deliver a certain goal.

[0086] Expectation Object: It is used to describe the object to which the intent expectation applies. For example, in a network energy-saving service, the expectation object can be the network element for which the user hopes to achieve the energy-saving goal. The expectation object also includes multiple attributes, namely object type (objectType), object instance (objectInstance) and object context. Among them, the object type is used to describe the type of the expected object, the object instance is used to describe a specific object instance to which the intent expectation applies, and the object context is used to describe the constraints of the expected object. Through the object context, the screening of the expected object can be achieved.

[0087] ExpectationTarget: used to describe the goal that the intention expects the expected object to achieve. The expected target may include multiple attributes, namely target name (targetName), target condition (targetCondition), target value range (targetValueRange) and target context (targetContexts). Among them, the target name refers to the name of the expected target. Generally, the expected target can be an indicator used to characterize the performance of the expected object or some other abstract indicators. The target condition is used to describe the restrictions on the expected target, wherein the target condition may include equal to, less than, greater than, within the range, outside the range, one of them, less than or equal to, greater than or equal to, not one of them, both belong to, etc. The target value range is used to describe the value range applicable to the target name and target condition. The target context is used to describe the constraints of the expected target, which may indicate the application conditions of the expected target.

[0088] ExpectationContexts: used to describe the constraints of the intent expectation. The constraints may refer to the application conditions of the schematic expectation. For example, the expectation context may be a time condition, which indicates that the intent expectation is applied when the time condition is met.

[0089] (2) Intent context may include the following attributes:

[0090] Context Attribute: A specific attribute related to the object to which the intent applies or its characteristics, or an attribute related to the operating conditions of the object to which it applies. For example, the context attribute of the intent context can be the time when the intent is expected to apply.

[0091] Context Condition: used to describe the restrictions on context attributes. For example, context conditions may include equal to, less than, greater than, within range, outside range, one of, less than or equal to, greater than or equal to, not one of, both of, etc.

[0092] Context value range (contextValueRange): used to describe the value range applicable to context attributes and context conditions.

[0093] It should be noted that in the embodiments of the present application, other contexts, such as expected context, object context, and target context, may include context attributes, context conditions, and context value ranges.

[0094] (3) The intent-realization effect report may include the following attributes:

[0095] Goal fulfillment status (fulfilmentStatus): used to describe whether the desired goal of the intent is currently achieved. The goal fulfillment status can be not fulfilled or fulfilled.

[0096] Unfulfilled state: used to describe the specific state of an intent when it is not fulfilled, which may include acknowledged state, compliant state, degraded state, suspended state, terminated state, and fulfilment failed state. The acknowledged state is the initial state when the intent management server receives the intent, the accepted state is the state after the intent management server detects the intent and determines that the intent meets the execution requirements, the degraded state refers to the state after the intent is initially fulfilled and after a period of observation, it does not meet the fulfillment state, the suspended state refers to the state in which the intent is postponed, the terminated state refers to the state in which the intent execution is stopped, and the failed state refers to the state in which the intent goal is not achieved.

[0097] Not Fulfilled Reason: used to describe the reason associated with any of the above-mentioned not fulfilled states.

[0098] 3. Intent processing function interface

[0099] The intent handling function interface is an interface added in 3GPP and managed and supported by the intent management server to provide users with specific intent capabilities supported by the intent management server. The intent handling function interface may include an intent handling capability list (intentHandlingCapabilityList) attribute, which includes one or more intent handling capabilities (intentHandlingCapability).

[0100] Among them, the intent processing capability can include the following attributes:

[0101] (1) Intent Handling Capability ID: used to uniquely identify an intent handling capability.

[0102] (2) Supported Expectation Object Type (supportedExpectationObjectType): used to indicate the type of expectation object supported by a specific intent handling function.

[0103] (3) Supported Expectation Target Names: used to indicate the names of the expectation targets supported by a specific intent handling function.

[0104] From the above introduction to the intent interface and the intent processing function interface, it can be seen that the current standard interface does not include scene-related attributes and therefore does not support scene-based intent settings. Based on this, in an embodiment of the present application, scene-related attributes can be added to the above standard interface to support scene-based intent settings.

[0105] Exemplarily, in an embodiment of the present application, a scenario-related attribute can be added to the intent interface to describe the scenario expected by the user, so as to implement the delivery of the scenario expected by the user. In addition, a scenario-related attribute can also be added to the intent processing function interface to describe the scenarios supported by the intent management server, so as to implement the reporting of supported scenarios to the user.

[0106] Specifically, an attribute may be added to the intent expectation attribute of the intent interface, and the added attribute may be an expectation scenario list (expectationScenarioList) attribute, and the attribute value of the expectation scenario list attribute may include the identifier of at least one expected scenario expected by the user, and the at least one expected scenario is the scenario applicable to the intent expectation. It should be noted that the attribute value of the expectation scenario list attribute is readable, writable and mutable, and when the attribute value of the expectation scenario list attribute changes, a notification is allowed to be triggered.

[0107] In addition, an attribute can be added to the intent processing capability of the aforementioned intent processing function interface. The added attribute can be a supported scenario list (supportedScenarioInfoList) attribute, which is used to indicate the scenarios supported by the intent management server. Among them, the supported scenario list attribute can include multiple supported scenario attributes, and the attribute value of each supported scenario attribute can include the scene information of a scene supported by the intent management server. The scene information may include a scene identifier and the intent setting reference information of the corresponding scene. The intent setting reference information refers to information that provides a reference for users to set the intent corresponding to the corresponding scene. Among them, the attribute value of the supported scenario list attribute is readable, writable and variable, and when the attribute value of the supported scenario list attribute changes, notification is allowed to be triggered.

[0108] Of course, the above-mentioned expected scene list attributes and supported scene list attributes can also be set in other structures of the standard interface, and the embodiments of the present application are not limited to this.

[0109] By adding a supported scenario list attribute to the intent processing function interface in the standard interface, the intent management server can create its own intent processing function interface according to the scenarios applicable to different services. The intent processing function interface includes the scenario information of the scenarios supported by the intent management server. In this way, through the intent processing function interface, the intent management server can provide users with scenario information of multiple scenarios supported by itself. In addition, by adding an expected scenario list attribute to the intent interface of the standard interface, users can be supported to set intents through the user terminal for at least one scenario they expect. Based on this, the specific implementation process of the user terminal and the intent management server obtaining the user's intent containing the expected scenario based on the standard interface is introduced below. See Figure 3 , the process includes the following steps:

[0110] Step 301: The intent management server sends scene information of multiple scenes corresponding to a first service to a user terminal, and the user terminal receives the scene information of the multiple scenes, where the scene information of each scene includes intent setting reference information of the corresponding scene.

[0111] In a possible implementation, when the user wants to set the intent of the first service based on the scenario, the user can perform a scenario query operation on the user terminal to trigger a scenario information query instruction. In response to the scenario information query instruction, the user terminal can send a scenario information query request to the intent management server. After receiving the scenario information query request, the intent management server sends the scenario information of the scenario supported by the intent management server corresponding to the first service to the user terminal.

[0112] For example, see Figure 4, a human-computer interaction interface 40 may be displayed on the user terminal, and a scene information query bar 41 may be displayed in the human-computer interaction interface 40, and the user may enter the identifier of the first service in the scene information query bar 41, and the first service is the service that the user currently intends to set. For example, the first service may be a network energy-saving service. Afterwards, the user may click the scene query button 42 corresponding to the scene information query bar to trigger the scene information query instruction. After detecting the scene information query instruction, the user terminal may obtain the identifier of the first service input by the user, and based on the identifier of the first service, generate a scene information query request, wherein the scene information query request includes the identifier of the first service.

[0113] Of course, the user can also trigger the scene information query instruction through other implementation methods. For example, when multiple scenes in the scene list supported by the intent management server are scenes for the first business and do not include scenes for other businesses, a scene information query button can be directly displayed in the human-computer interaction interface of the user terminal, and the user can directly click the scene information query button to trigger the scene information query instruction. Alternatively, the user can directly perform a pre-set gesture operation on the user terminal to trigger the scene information query instruction. In this case, after detecting the scene information query instruction, the user terminal can generate a scene information query request, wherein the scene information query request does not include the identifier of the first business. The above are examples of several user-triggered scene information query instructions given in the embodiments of the present application, and do not constitute a limitation on the embodiments of the present application.

[0114] After generating a scene information query request, the user terminal may send the scene information query request to the intent management server. After receiving the scene information query request, the intent management server obtains scene information of multiple scenes corresponding to the first service and returns the scene information of multiple scenes corresponding to the first service to the user terminal.

[0115] As can be seen from the above introduction, a supported scenario list attribute is newly added to the intent processing capability of the intent processing function interface. Based on this, the intent processing capability of the intent processing function interface managed and supported by the intent management server may include a list of scenarios supported by the intent management server. In this case, the intent management server can send scenario information of multiple scenarios of the first service supported by itself to the user terminal through the intent processing function interface.

[0116] Exemplarily, in a possible situation, if the scenarios in the scenario list supported by the intent management server included in the intent processing function interface are all scenarios for the first service, the intent management server can directly obtain the supported scenario list from the intent processing function interface, and return scenario information of multiple scenarios in the supported scenario list to the user terminal. At this time, the multiple scenarios are the scenarios supported by the intent management server for the first service.

[0117] In another possible scenario, if the supported scenario lists included in different intent processing capabilities in the intent processing function interface correspond to different services, the supported scenario lists in each intent processing capability may include not only supported scenario attributes, but also service attributes, wherein the attribute value of the service attribute may be the identifier of the service corresponding to the supported scenario list. Based on this, after receiving the scene information query request, the intent management server obtains the identifier of the first service in the scene information query request, and then obtains the supported scenario list corresponding to the identifier of the first service through the intent processing function interface, and sends the scene information of multiple scenes in the supported scenario list corresponding to the obtained identifier of the first service to the user terminal. At this time, the scene information of the multiple scenes is the scene information of the multiple scenes corresponding to the first service.

[0118] Taking the first service as a network energy-saving service as an example, the multiple scenarios corresponding to the first service may include railway scenarios, scenic area scenarios, highway scenarios, urban scenarios, suburban scenarios, rural scenarios, residential scenarios, business district scenarios, school scenarios, etc.

[0119] It should be noted that, as can be seen from the above introduction, the attribute value of the supported scene attribute in the supported scene list may include scene information of the supported scene, and the scene information may include scene identification and intention setting reference information. Based on this, the scene information of each scene corresponding to the first service may include the scene identification and intention setting reference information of the corresponding scene, wherein the scene identification is used to uniquely identify a scene, and the intention setting reference information provides a reference for the user to set the intention corresponding to the first service in the corresponding scene, that is, the intention setting reference information can be used to instruct the user how to set the intention of the first service in the corresponding scene.

[0120] Exemplarily, the intention setting reference information of a certain scenario may include at least one of a recommended expected goal, a recommended business strategy, and a recommended business strategy constraint for the scenario.

[0121] Among them, the recommended expected goal of the scene may be an expected goal that is recommended to the user to set the first business and is applicable to the scene when the intention expectation corresponds to the scene. It should be noted that the recommended expected goal of the scene may include the general expected goal of the first business and the personalized expected goal in the scene, wherein the general expected goal refers to the expected goal applicable to each scene of the first business, and the personalized expected goal may refer to the expected goal that is applicable to the scene and may not be applicable to other scenes. Of course, the recommended expected goal of the scene may also include the personalized expected goal in the scene, but does not include the general expected goal of the first business. In addition, the recommended expected goal of the scene includes at least a target name, and optionally, in addition to this, it may also include one or more of the target conditions, target value ranges, and target contexts corresponding to the target name.

[0122] For example, taking the first service as a network energy-saving service, the general expected target of the first service in various scenarios may include one or more of network energy efficiency, network energy consumption, average user uplink rate, and average user downlink rate. For the railway scenario, the personalized expected target in this scenario may include call drop rate, same-frequency or different-frequency handover success rate.

[0123] The recommended business strategy of a scenario may refer to a business strategy recommended to be adopted in order to achieve the intention of the first business in the scenario.

[0124] The recommended business policy constraint of a scenario may refer to the constraint conditions of the business policy that can be adopted in the scenario to achieve the intention of the first business, that is, to indicate which constraints need to be imposed when executing the business policy in the scenario to achieve the intention of the first business.

[0125] For example, taking the first service as a network energy-saving service as an example, Table 1 shows the recommended expected goals, recommended service strategies and recommended service strategy constraints for each scenario corresponding to the first service. As shown in Table 1, since the scenario characteristics of each scenario are different, the recommended expected goals of each scenario may also be different, that is, the recommended expected goals of each scenario are actually personalized expected goals recommended for users in the corresponding scenario. In addition, in the recommended service strategies corresponding to each scenario, the symbol shutdown strategy refers to the time domain shutdown of the network device, and the channel shutdown strategy refers to the shutdown of some of the multiple transmitters and receivers formed by the antenna array of the network device. The convergence scheduling strategy refers to scheduling the network device for centralized transmission and reception. The carrier shutdown strategy refers to shutting down some cells of the network device. The deep sleep strategy refers to the network device entering a sleep state. The recommended service strategy constraints corresponding to each scenario may include service strategies that are not recommended in the corresponding scenario. For example, in the railway scenario, the recommended service strategies include symbol shutdown strategies, channel shutdown strategies and convergence scheduling strategies, and the recommended service strategy constraints include service strategies that are not recommended, that is, carrier shutdown and deep sleep are not recommended. Optionally, the recommended business policy constraints corresponding to each scenario may include other constraints that the business policies that can be adopted in the corresponding scenario to achieve the intention of the first business must be subject to. For example, in the railway scenario, no matter what business policy is subsequently executed to achieve the intention of the first business, the constraint is to ensure user experience.

[0126] Table 1 Reference information for intent settings of multiple scenarios corresponding to network energy-saving services

[0127]

[0128] Optionally, in some possible situations, the intention setting reference information of a certain scene may also be the pre-configured intention expectation of the first service in the scene. The intention expectation includes the scene identifier of the scene and at least one expected target. In addition, the intention expectation may also include an expected context.

[0129] Optionally, in addition to the intention setting reference information, the scene information of each scene may also include the scene characteristics of the corresponding scene. For example, for network energy-saving services, the scene characteristics of the railway scene are guaranteed coverage along the railway and frequent user switching; the scene characteristics of the scenic spot scene are a large number of users in multiple months during the peak season and a small number of users in multiple months during the off-season.

[0130] Optionally, the scene information of each scene may also include scene description information for describing the corresponding scene, or the scene description information may also be understood as a definition of the corresponding scene. For example, for a scenic scene, the scene description information may be scenic spots, parks, and other areas. For an urban scene, the scene description information may be a core area of ​​the city.

[0131] In another possible implementation, since the intent processing function interface is managed and supported by the intent management server, in the embodiment of the present application, the intent management server can actively send scenario information of the supported scenarios to the user terminal after creating its own intent processing function interface or when there are new supported scenarios in the intent processing function interface. The supported scenarios of the intent management server include multiple scenarios corresponding to the first service.

[0132] Step 302: The user terminal obtains a first intention of a first service based on the intention setting reference information of multiple scenarios and the user's first scenario requirement information.

[0133] After receiving the scenario information of multiple scenarios corresponding to the first service sent by the intent management server, the user terminal can obtain the first intent of the first service based on the scenario information of the multiple scenarios and the user's first scenario requirement information. The first intent includes the intent expectation under the first scenario in the multiple scenarios, and the first scenario requirement information is used to indicate the first scenario.

[0134] In a first possible implementation, after receiving scene information of multiple scenes, the user terminal may display scene identifiers of multiple scenes. Afterwards, the user terminal may receive a scene identifier of a first scene input by a user, wherein the first scene requirement information includes the scene identifier of the first scene; display at least one recommended desired target of the first scene; in response to a user's selection operation of a first desired target among at least one recommended desired target of the first scene, generate an intention expectation under the first scene based on the scene identifier of the first scene and the first desired target; and generate a first intention of the first service based on the intention expectation under the first scene.

[0135] Exemplarily, after receiving the scene information of multiple scenes, the user terminal can display the scene identifiers of the multiple scenes in the human-computer interaction interface. The user can select the scene identifier of the first scene from the displayed scene identifiers of the multiple scenes, and in response to the user's selection operation on the scene identifier of the first scene, the user terminal receives the scene identifier of the first scene input by the user. At this time, the first scene is the scene selected by the user for his own needs, so the scene identifier of the first scene is the user's first scene demand information.

[0136] After receiving the scene identification of the first scene input by the user, the user terminal may display at least one recommended desired target included in the intention setting reference information of the first scene.

[0137] Among them, it can be known from the above introduction that the at least one recommended expected target includes at least a target name, based on which the user terminal can display the target name of the at least one recommended expected target. The user can select the target name of the first expected target from the displayed target names. In response to the user's selection operation on the target name of the first expected target, the user terminal can generate the intention expectation under the first scene based on the target name of the first expected target and the scene identifier of the first scene.

[0138] It should be noted that if at least one recommended expected target includes, in addition to the target name, also includes target conditions, target value range and target context corresponding to the target name, the user terminal directly obtains the first expected target after detecting the user's selection operation on the target name of the first expected target, and then uses the intention interface to generate the intention expectation under the first scene based on the first expected target and the scene identifier of the first scene.

[0139] Optionally, in some possible situations, after detecting the user's selection operation on the target name of the first expected target, the user terminal may also display the target condition, target value range and target context of the first expected target and the modification options corresponding to these three items of information. The user can click on the modification option corresponding to any item of information to convert the corresponding item of information to an editing state, after which the user can modify the corresponding item of information. After receiving the user's modification information on a certain item of information, the user terminal uses the intention interface to update the corresponding item of information based on the modification information, and then generates the first expected target based on the updated information and the target name of the first expected target, and generates the intention expectation under the first scene based on the first expected target and the scene identifier of the first scene.

[0140] Optionally, if at least one recommended desired target includes a target name but does not include a target condition, target value range, and target context corresponding to the target name, then after detecting the user's selection operation on the target name of the first desired target, the user terminal can display a setting box corresponding to the target condition, target value range, and target context corresponding to the target name, so that the user can enter the target condition, target value range, and target context corresponding to the target name set by the user in the setting box. Afterwards, the user terminal uses the intention interface to generate a first desired target based on the received user-set target condition, target value range, and target context and the target name of the first desired target, and generates the intention expectation under the first scenario based on the first desired target and the scenario identifier of the first scenario.

[0141] It should be noted that, as can be seen from the above introduction, at least one recommended expected target of the scene may include the general expected target of the first business, or may not include the general expected target of the first business. Based on this, when the first expected target is a personalized expected target in the first scene, rather than a general expected target of the first business, the user terminal can also obtain the general expected target set by the user, and then generate the intention expectation in the first scene based on the scene identifier of the first scene, the first expected target and the general expected target set by the user.

[0142] Among them, if at least one recommended expected target includes a general expected target, the user terminal can display the target name of the general expected target and the setting box of the target condition, target value range and target context of the general expected target while displaying the setting box of the target condition, target value range and target context of the first expected target. In this way, the user terminal can obtain the target condition, target value range and target context of the general expected target entered by the user in the setting box, and generate a general expected target based on the above information.

[0143] Optionally, if at least one of the recommended expected targets does not include a general expected target, and the user knows the target name of the general expected target of the first business supported by the intent management server, the user can directly enter the target name, target condition, target value range and target context of the general expected target on the user terminal, and the user terminal can generate the general expected target based on the target name, target condition, target value range and target context of the general expected target entered by the user. If the user is not clear about the target name of the general expected target of the first business supported by the intent management server, the user can also trigger the intent processing capability query instruction on the user terminal. In response to the intent processing capability query instruction, the user terminal can send an intent processing capability query request to the intent management server. After receiving the intent processing capability query request, the intent management server can return the intent processing capability corresponding to the first business supported by itself to the user terminal. Among them, the intent processing capability includes the target name of the general expected target of the first business supported by the intent management server and the type of the expected object. Among them, there can be one or more general expected targets of the first business. After receiving the intent processing capability corresponding to the first business returned by the intent management server, the user terminal can display the target name of the general expected target of the first business. In response to the user's selection operation on the target name of one or more displayed general expected targets, the user terminal can display a setting box corresponding to the target conditions, target value range and target context of the general expected target selected by the user. The user can enter the information he wants to set in the corresponding setting box, and the user terminal generates a corresponding general expected target based on the target name of the general expected target selected by the user and the target conditions, target value range and target context of the general expected target entered by the user.

[0144] For example, see Figure 5 , taking the first service as a network energy-saving service as an example, after receiving the scene information of the corresponding multiple scenes, the user terminal can display the scene identification of each scene in the human-computer interaction interface. The user can select a scene identification from them, for example, the scene identification selected by the user is "railway scene". After detecting the user's selection operation on "railway scene", the user terminal can display the target names of two recommended expected targets corresponding to the railway scene, which are the same-frequency or different-frequency switching success rate and the call drop rate. At this time, the two recommended expected targets are personalized expected targets in the railway scene, and the user can select one or two target names from the target names of the two recommended expected targets. For example, the user selected the call drop rate. The user terminal displays the setting box corresponding to the call drop rate, and the user can enter the corresponding target condition and target value range in the setting box. The target context is empty. In addition, the user terminal can also display a setting box for a general expected target, and the user can enter the target name of energy consumption (EC) in the setting box, and set the corresponding target condition and target value range. After obtaining the above information entered by the user, the user terminal can use the intention interface to generate the intention expectation under the first scene, wherein the intention expectation under the first scene may include the following information:

[0145] expectationScenario: railway;

[0146] expectationTarget: drop_call_rate ≤ 2% and EC > 15%.

[0147] It should be noted that in some possible situations, when at least one recommended expected target for the first scene displayed by the user terminal is a personalized recommended expected target under the first scene, the user may not select the first expected target, but input a general expected target. That is, the user may not set a personalized expected target under the first scene, but only set a general expected target for the first business.

[0148] Optionally, as can be seen from the foregoing introduction, the scene's intention setting reference information can also include at least one recommended business strategy and recommended business strategy constraints for the scene. Based on this, in an embodiment of the present application, the user terminal can also display at least one recommended business strategy for the first scene; in response to the user's selection operation of a first recommended business strategy among at least one recommended business strategy for the first scene, based on the first recommended business strategy and the recommended business strategy constraints, generate an expected context for the first scene; based on the scene identifier, expected context, and first expected target of the first scene, generate an intention expectation for the first scene, and the intention expectation for the first scene includes the scene identifier, expected context, and first expected target of the first scene.

[0149] Exemplarily, the user terminal may display at least one recommended business strategy for the first scene while displaying at least one recommended expected target for the first scene. That is, after receiving the scene identifier of the first scene input by the user, the user terminal may simultaneously display at least one recommended expected target and at least one recommended business strategy for the first scene in the human-computer interaction interface. Alternatively, the user terminal may also display at least one recommended business strategy corresponding to the first scene after obtaining the information of the first expected target and the general expected target set by the user through the method described above.

[0150] For at least one recommended business strategy for the first scenario displayed by the user terminal, the user can select a first recommended business strategy from them. In response to the selection operation for the first recommended business strategy, the user terminal can generate an expected context for the first scenario based on the first recommended business strategy and the recommended business strategy constraint. The first recommended business strategy selected by the user can be one or more.

[0151] It should be noted that the recommended business strategy for the first scenario refers to the business strategy recommended for achieving the intention of the first business in the first scenario. The recommended business strategy constraint refers to the constraint conditions of the business strategy that can be adopted in order to achieve the intention of the first business in the first scenario. On this basis, according to the first recommended business strategy selected by the user, the business strategy that the user hopes to adopt to achieve the intention expectations in the first scenario can be determined, and according to the recommended business strategy constraint, the constraints that the first recommended business strategy that the user wants to adopt needs to be subject to can be determined. Therefore, based on the above-mentioned first recommended business strategy and recommended business strategy constraints, the user terminal can determine the constraints required to execute the intention expectations in the first scenario, that is, the expected context of the first scenario.

[0152] Exemplarily, taking the first service as a network energy-saving service, in the railway scenario, the recommended service strategies are symbol shutdown, channel shutdown and convergence scheduling, and the recommended service strategy constraints include prohibiting carrier shutdown and deep sleep to ensure user experience. Based on this, when the recommended service strategy selected by the user is convergence scheduling, the user terminal can determine the expected context of the first scenario as prohibiting shutdown according to the recommended service strategy and the recommended service strategy constraints, that is, when executing the intended expectation under the first scenario, it is prohibited to execute shutdown strategies including symbol shutdown, channel shutdown, carrier shutdown and deep sleep.

[0153] After generating the expected context of the first scene, the user terminal generates the intention expectation under the first scene based on the scene identifier of the first scene, the expected context, the first expected target generated above, or the first expected target and the general expected target. At this time, the expected target of the intention expectation includes the first expected target, or the first expected target and the general expected target. The identifier of the expected scene of the intention expectation is the scene identifier of the first scene, and the expected context of the intention expectation is the generated expected context of the first scene.

[0154] Optionally, in some possible situations, the scene information may also include scene characteristics and scene description information. In this case, in order to help users better understand each scene and thus better set the intention corresponding to the required scene, the user terminal can display the scene characteristics and scene description information of each scene while displaying the scene identification of each scene, so as to assist users in scene identification, desired scenes and selection of recommended business strategies.

[0155] In a second possible implementation, after obtaining the scene information of multiple scenes corresponding to the first business, the user terminal can obtain the engineering parameter data of multiple business objects in the same scene applicable to the first business. At this time, the user's first scene demand information includes the engineering parameter data of the multiple business objects; based on the engineering parameter data of the multiple business objects, the characteristics of the scenes in which the multiple business objects are located are determined; from the multiple scenes corresponding to the first business, the first scene whose scene characteristics match the characteristics of the scenes in which the multiple business objects are located is determined; and reference information is set based on the intention of the first scene to obtain the first intention of the first business.

[0156] It should be noted that in some cases, when a user wants to perform a first service in a certain area or a certain scene, it may not be clear what kind of scene the area or the scene can be specifically defined as. For example, when a user wants to apply a network energy-saving service in a certain area, it may not be possible to determine whether the traffic characteristics of the area are closer to an urban area, a suburb, or a rural area. In this case, the user can provide the user terminal with the industrial parameter data of multiple business objects in the same scene as their own scene requirement information to express their own scene requirements. On this basis, since the scene information provided by the intent management server may include scene features, the user terminal can determine the scene features of the scene based on the industrial parameter data of multiple business objects in the scene, and then determine the first scene that matches the scene in the multiple scenes supported by the intent management server, so as to realize intelligent recognition of the scene.

[0157] Exemplarily, the user terminal can receive the engineering parameter data of multiple business objects in the same scene sent by the user through other devices, or the engineering parameter data of business objects in different areas or scenes can be pre-stored on the user terminal, and the user can select the engineering parameter data of multiple business objects in a scene to be set. In response to the user's selection operation, the user terminal obtains the engineering parameter data of the multiple business objects selected by the user.

[0158] Among them, the business object refers to an object that can be applied to the first business. Taking the first business as the network energy-saving business as an example, the business object can be an object in the network that can execute the network energy-saving business, such as a base station in the network. In addition, the industrial parameter data of the business object can be data that can characterize the characteristics of the scene in which the business object is located. Exemplarily, the industrial parameter data of the business object may include at least one of the object attribute data and working data of the business object. For example, in the network energy-saving business, the industrial parameter data of the business object may include the equipment attributes and working data of the base station. The working data may include the utilization rate of the physical resource block (PRB) of the base station at different times, the number of access users, and other data that can characterize the traffic characteristics of the scene in which the base station is located.

[0159] After obtaining the engineering parameter data of multiple business objects in a certain scene, the user terminal can use a pre-trained machine learning model to process the engineering parameter data of the multiple business objects, so as to determine the scene characteristics of the scene in which the multiple business objects are located. Alternatively, the user terminal can also determine the scene characteristics corresponding to the engineering parameter data of each business object according to a pre-set mapping strategy between engineering parameter data and scene characteristics, and then use the common scene characteristics of business objects greater than a certain threshold as the characteristics of the scene in which the multiple business objects are located.

[0160] After determining the characteristics of the scenes in which the multiple business objects are located, the user terminal can match the characteristics of the scenes in which the multiple business objects are located with the scene characteristics included in the scene information of the multiple scenes corresponding to the first business supported by the intent management server, and take the scene corresponding to the matched scene characteristics as the first scene. At this time, the first scene is the scene that is most similar to the scene in which the multiple business objects are located, that is, the first scene is closest to the scene required by the user.

[0161] For example, taking the network energy-saving service as an example, based on the working parameter data of multiple base stations in a certain area, it is determined that the scene characteristics of the area are long-term high traffic, and among the multiple scenarios corresponding to the network energy-saving service supported by the intent management server, the scene characteristics of the urban scene are also long-term high traffic. In this case, it can be determined that the characteristics of the area where the multiple base stations are located are consistent with the scene characteristics of the urban scene, that is, the two match, and therefore, the scene where the multiple base stations are located can be determined as an urban scene.

[0162] Optionally, in some possible situations, after acquiring the engineering parameter data of multiple business objects, the user terminal may also input the engineering parameter data of the multiple business objects into a pre-trained deep learning model, and the deep learning model processes the engineering parameter data of the multiple business objects, thereby directly outputting scenes that match the scenes in which the multiple business objects are located.

[0163] After determining the first scene that matches the scene in which multiple business objects are located, the user terminal can adopt the method introduced in the first implementation method to generate the intention expectation under the first scene by displaying the recommended expected goal and recommended business strategy of the first scene to the user and receiving the corresponding setting information input by the user, and then generate the first intention of the first business based on the intention expectation under the first scene.

[0164] Optionally, in a possible implementation, the intention setting reference information of the first scene may also be a pre-set intention expectation under the first scene, the identifier of the expected scene in the intention expectation is the identifier of the first scene, and the expected target is the pre-set first expected target, and optionally, the intention expectation may also include a pre-set expected context. In this case, the user terminal can directly generate the first intention of the first service based on the intention expectation under the first scene.

[0165] For example, still taking the network energy-saving service as an example, assuming that it is determined that the scenarios in which multiple base stations are located match the urban scenarios, the user terminal can directly obtain the intention setting reference information of the urban scenario, and the intention setting reference information of the urban scenario includes the intention expectation in the urban scenario. For example, the intention expectation in the urban scenario is as follows:

[0166] expectationScenario:urban(urban area);

[0167] expectationTarget: EC>5%and Average_user_throughput (average user throughput)>90%.

[0168] It is worth noting that in an embodiment of the present application, the first scene selected by the user through the method provided in the aforementioned first possible implementation method may be one or more. Alternatively, in a second possible implementation method, the user may provide multiple groups of engineering parameter data of business objects, each group corresponding to a scene, so that the user terminal can determine the corresponding multiple first scenes based on the engineering parameter data of the multiple groups of business objects. Based on this, in the case where there is one first scene, after the user terminal generates the intent expectation under the first scene based on the intent interface, it can continue to generate a first intent containing the intent expectation under the first scene based on the intent interface. Optionally, in the case where there are multiple first scenes, after the user terminal generates the intent expectation under each first scene based on the intent interface, it can continue to use the intent interface to use the intent expectation under each first scene as one of the intent expectations in the first intent, thereby obtaining a first intent containing the intent expectations of the multiple first scenes.

[0169] It can be seen that in the embodiments of the present application, one intent may include multiple intention expectations under the first scenarios, and the intention expectations of each first scenario are different, thereby realizing the batch delivery of the intention expectations of multiple different first scenarios and the differentiated setting of the intention expectations of different scenarios.

[0170] Step 303: The user terminal sends a first intent to the intent management server, and the intent management server receives the first intent.

[0171] After acquiring the first intent of the first service, the user terminal may call the intent interface to send the first intent to the intent management server. Correspondingly, the intent management server may receive the first intent through the intent interface.

[0172] Step 304: The intent management server executes the first intent.

[0173] In an embodiment of the present application, the intent management server can use the intent interface to parse the first intent to obtain the various information in the intent expectations under the first scenario contained in the first intent. Thereafter, the intent management server can execute the first intent based on the various information in the intent expectations under the first scenario obtained by parsing.

[0174] As can be seen from the above introduction, the intention expectation under the first scenario can include the identifier of the expected scenario, that is, the identifier of the first scenario, and in addition, the expected target of the first scenario. Based on this, the intention management server can determine the first expected object in the first scenario based on the identifier of the first scenario obtained through parsing; generate the first business policy based on the expected target of the first scenario; send the first business policy to the first expected object, and the first expected object is used to execute the first business policy.

[0175] Among them, the scene information of multiple scenes corresponding to the first business supported by the intent management server includes scene description information, and the scene description information may include area information corresponding to the corresponding scene. Based on this, the intent management server may obtain the scene description information of the first scene based on the identifier of the first scene, determine the area information corresponding to the first scene based on the scene description information of the first scene, and then determine the business object applicable to the first business in the area according to the area information. At this time, the business object applicable to the first business in the area is the first expected object in the first scene. Among them, there may be one or more first expected objects.

[0176] Optionally, the intent management server may also maintain a mapping relationship between the identifiers of different scenes and the corresponding area information. Based on this, the intent management server may also directly obtain the area information corresponding to the identifier of the first scene from the mapping relationship, and then obtain the first desired object located in the first scene based on the area information.

[0177] For example, taking the network energy-saving service as an example, the first scenario is the railway scenario, and the area information corresponding to the railway scenario may be the area along the railway. The intent management server may determine the base stations in the area along the railway as the desired objects in the railway scenario.

[0178] It can be seen that in the embodiments of the present application, when the user sets the intent based on the scenario, he or she does not need to set the expected object in the intent expectation. The intent management server can automatically determine the expected object in the corresponding scenario based on the identification of the expected scenario in the intent expectation. In this way, the efficiency of intent setting can be improved.

[0179] In addition, the intent management server may also generate a first business strategy for achieving the expected goal according to the expected goal of the first scenario, wherein the expected goal of the first scenario may include the first expected goal in the aforementioned step 302, and may also include a general expected goal of the first business.

[0180] It should be noted that in one possible scenario, the intent expectation in the first scenario does not include the expected context, that is, the user has not set the corresponding expected context. In this case, the intent management server can obtain the recommended business policy and recommended business policy constraints of the first scenario from the scenario information of the first scenario. After that, the intent management server can generate the first business policy by combining the recommended business policy, recommended business policy constraints and the expected goal of the first scenario.

[0181] Among them, for each recommended business strategy of the first scenario, the intent management server can maintain at least one execution plan corresponding to the corresponding recommended business strategy. Based on this, the intent management server obtains at least one execution plan corresponding to each recommended business strategy, and determines the target execution plan that meets the constraints of the recommended business strategy from the at least one execution plan corresponding to each recommended business strategy. For each determined target execution plan, the intent management server can estimate the estimated target value of the expected target corresponding to the execution parameters of the target execution plan when different execution parameter values ​​are used. Afterwards, select at least one group of execution parameter values ​​whose corresponding estimated target values ​​meet the expected target of the first scenario from the different execution parameter values. Afterwards, the intent management server can arbitrarily select a group of execution parameter values ​​from the at least one group of execution parameter values, or select the best group of execution parameter values ​​from the at least one group of execution parameter values, and generate the first business strategy based on the selected group of execution parameter values ​​and the corresponding target execution plan.

[0182] Specifically, when the intent management server selects the best set of execution parameter values ​​from at least one set of execution parameter values, it can make the selection based on the target conditions and target value range of the expected target in the first scenario. For example, when the target conditions and target value range of the expected target of the first scenario indicate that the user wants the expected target to be greater than a certain threshold, the intent management server can select a set of execution parameter values ​​with the largest corresponding estimated target values ​​from at least one set of execution parameter values. For another example, when the target conditions and target value range of the expected target of the first scenario indicate that the user wants the expected target to be less than a certain threshold, the intent management server can select a set of execution parameter values ​​with the smallest corresponding estimated target values ​​from at least one set of execution parameter values.

[0183] Optionally, in another possible scenario, the intent expectation in the first scenario may also include an expected context. In this case, the intent management server may directly generate a first business policy based on the expected goal and expected context of the first scenario obtained through parsing.

[0184] It should be noted that, as can be seen from the above introduction, the expected context in the intention expectation under the first scenario is the constraint condition required to execute the intention expectation under the first scenario. Based on this, the intention management server can use the expected context as a business policy constraint, determine the target execution plan and the corresponding execution parameter value with reference to the method introduced above, and generate the first business policy based on the target execution plan and the corresponding execution parameter value.

[0185] Since the first business policy is a policy for achieving the expected goal in the intended expectation in the first scenario, the intent management server can send the first business policy to the first expected object in the first scenario, and the first expected object will execute the first business policy to achieve the expected goal in the first scenario.

[0186] When there are multiple first scenarios, for each intention expectation under the first scenario, the intention management server can obtain the corresponding first business policy through the above method, and send the corresponding first business policy to the expected object under the corresponding first scenario, so as to complete the execution of the intention expectation under the first scenario, thereby completing the execution of the first intention.

[0187] Optionally, after parsing the intention expectation in the first scenario included in the first intention, the intention management server may also perform intention conflict detection to avoid the situation where the intention cannot be executed due to the conflict of intention expectation.

[0188] Exemplarily, when there are multiple first scenarios, the intent management server can detect whether there is a conflict between the intent expectations under the multiple first scenarios; if there is no conflict between the intent expectations under the multiple first scenarios, the first intent is executed.

[0189] Among them, for any two first scenarios among multiple first scenarios, the intention management server can detect whether the intention expectation under one of the two first scenarios will cause the intention expectation under another first scenario to fail to execute. If so, it is determined that there is a conflict between the two intention scenarios.

[0190] For example, in some possible situations, the areas corresponding to two first scenes may partially overlap, so that the expected objects in the overlapping area need to achieve the expected goals of the two first scenes at the same time. In this case, if the expected goals of the two first scenes conflict, the expected objects in the overlapping area of ​​the two first scenes will not be able to achieve the expected goals. Based on this, the intent management server can detect whether there is a conflict between the expected goals of the two first scenes. For example, the intent management server can detect whether there is an intersection between the condition range composed of the target conditions and target value ranges of the expected goals of the two first scenes. If there is no intersection, it is determined that the intention expectations of the two first scenes conflict.

[0191] Optionally, the intention management server may not only detect whether there is a conflict between intention expectations in multiple first scenarios, but also detect whether there is a conflict between the intention expectation in any first scenario and the intention expectation in the second intention of the first service that is currently being executed.

[0192] For example, there is a partial overlap between the areas corresponding to a first scene in the first intention and the scene in the second intention. In this case, the intention management server can refer to the method introduced above to detect whether there is a conflict in the expected targets in the intention expectations of the two scenes.

[0193] For another example, if the second intention of the first business and the first intention include the intention expectation under the same first scenario, that is, the identifiers of the expected scenarios in the two intention expectations are the same, the intention management server can detect whether there are conflicting target names or conflicting condition ranges in the expected targets of the two intention expectations. If so, it is determined that there is a conflict between the intention expectation under the first scenario in the first intention and the intention expectation under the first scenario in the second intention.

[0194] After the intent management server sends the first business policy to the first expected object in the first scene, each first expected object executes the first business policy and returns the execution result of the first business policy to the intent management server; the intent management server sends a report on the implementation effect of the first intention to the user terminal based on the execution results of the first business policy returned by each first expected object.

[0195] Among them, the execution result of the first business policy may include the specific execution information of the first business policy, and the intent management server may calculate the target value actually achieved by each first expected object based on the specific execution information when each first expected object executes the first business policy. Alternatively, the execution result of the first business policy may also include the target value actually achieved by the first expected object, so that the intent management server can directly obtain the target value actually achieved by each first expected object. Afterwards, the intent management server may compare the target value actually achieved by each first expected object with the expected target in the intent expectation under the first scenario, so as to determine the achievement of the intent expectation under the first scenario. Afterwards, the intent management server may generate a report on the implementation effect of the first intention based on the achievement of the intent expectation under the first scenario.

[0196] Specifically, if the target values ​​actually achieved by each first expected object meet the expected goals of the first scenario, it is determined that the intention expectation under the first scenario is achieved. When each intention expectation in the first intention is achieved, the intention management server can determine that the target achievement status of the first intention is an achieved status, and use the intention interface to feedback an intention achievement effect report to the user terminal, and the intention achievement effect report includes the target achievement status of the first intention.

[0197] If there is an expected object whose actual target value does not meet the expected target of the first scenario, it means that the intention expectation of the first scenario has not been achieved. In this case, the intention management server determines that the target achievement status of the first intention is an unachieved state. For unachieved intention expectations, the intention management server can also generate a reason for the non-achievement of the first intention based on the specific execution information when the first business policy is executed by the expected object that does not meet the expected target of the first scenario. Afterwards, the intention management server can use the intention interface to feedback an intention realization effect report to the user terminal, and the intention realization effect report includes that the target achievement status of the first intention is an unachieved state and the corresponding reason for non-achievement.

[0198] In an embodiment of the present application, for a certain service, such as the first service, the user terminal can obtain the scene information of multiple scenes corresponding to the first service from the intent management server, wherein the scene information of each scene includes the intention setting reference information of the corresponding scene. Based on this, the user terminal can obtain the intention expectation in the first scene indicated by the user's scene requirement information according to the intention setting reference information of each scene, and then obtain the first intention. It can be seen that the intent acquisition method provided in the embodiment of the present application supports scene-based intent setting, and the user can provide the scene requirement information of the first service to realize the setting of the intention expectation in a certain scene, which reduces the ability requirements of the user, reduces the probability of inaccurate intent setting, and improves the efficiency of intent setting.

[0199] In addition, in an embodiment of the present application, for different scenarios of the same business, the intent management server can recommend personalized expected goals in the corresponding scenarios to users. In this way, users can achieve differentiated settings and batch distribution of intent expectations in different scenarios based on the personalized expected goals recommended by the intent management server, thereby improving the accuracy and efficiency of intent settings.

[0200] Based on the intention acquisition method described in the above embodiment, the present application embodiment also provides a detailed implementation process of the intention acquisition method, see Figure 6 , the process may include the following steps:

[0201] Step 601: The user terminal receives a scene information query instruction from the user.

[0202] Step 602: The user terminal sends a scene information query request to the intent management server.

[0203] Step 603: The intent management server obtains scenario information of multiple scenarios corresponding to the first service from the intent processing function interface.

[0204] Step 604: The intent management server sends scenario information of multiple scenarios corresponding to the first service to the user terminal.

[0205] Step 605: The user terminal displays the scenario information of the multiple scenarios, and receives the identifier of the first scenario, the first expected goal, and the first recommended business strategy selected by the user based on the scenario information of the multiple scenarios.

[0206] Step 606: The user terminal generates a first intent based on the identifier of the first scenario, the first expected goal, the first recommended business policy, and the recommended business policy constraint.

[0207] Step 607: The user terminal sends a first intent to the intent management server, where the first intent includes an identifier of a first scenario, a first expected target, and an expected context.

[0208] Step 608: The intent management server translates the first intent to obtain the identifier of the first scenario, the first expected target, and the expected context.

[0209] Step 609: The intent management server determines a first desired object in the first scene based on the identifier of the first scene, and generates a first business policy based on the first desired goal and the expected context.

[0210] Step 610: The intent management server sends a first service policy to a first desired object.

[0211] Step 611: The first expected object executes the first business policy.

[0212] Step 612: The first desired object sends the execution result of the first business policy to the intent management server.

[0213] Step 613: The intent management server generates a report on the implementation effect of the first intent based on the execution result of the first business policy.

[0214] Step 614: The intent management server sends a report on the implementation effect of the first intent to the user terminal.

[0215] Among them, the detailed implementation methods of the above steps 601 to 614 can refer to the relevant implementation methods of the aforementioned embodiments, and the embodiments of the present application will not be repeated here.

[0216] Based on the intention acquisition method provided in the above embodiment, the above intention acquisition method is exemplarily described below by taking the first service as a network energy-saving service as an example.

[0217] In the first example, assume that the user wants to differentiate the intention expectations for multiple different scenarios, such as Figure 7 As shown, the user can first set the energy-saving intention on the user terminal. When setting the energy-saving intention, the user terminal can query the supported scene list 70 corresponding to the network energy-saving service supported by the intention management server. The supported scene list 70 includes scene information of scenes such as railways, scenic spots, highways, urban areas, suburbs, villages, residential areas, business districts and schools. The user can complete the setting of the energy-saving intention on the user terminal through the method introduced in the aforementioned embodiment based on the scene information of these scenes. After obtaining the energy-saving intention set by the user, the user terminal sends the energy-saving intention. Figure 7 As shown, the energy-saving intention sent may include two intention expectations, namely, intention expectation 71 in the railway scenario and intention expectation 72 in the scenic spot scenario. Among them, the expected scenario in the intention expectation 71 in the railway scenario is identified as railway, the expected target is EC>15%, and the expected context is to prohibit carrier shutdown and deep sleep. The expected scenario in the intention expectation 72 in the scenic spot scenario is identified as scenic spot, the expected target is EC>20%, and the expected context is from January to March, that is, the intention expectation 72 is executed from January to March. After the energy-saving intention is sent, the intention management server translates the intention and then executes the energy-saving intention. Among them, as Figure 7 As shown, in the process of executing the energy-saving intention, the railway area 711 and the service strategy 712 corresponding to the intention expectation 71, the scenic area and park area 721 and the corresponding service strategy 722 corresponding to the intention expectation 72 can be determined. Then, the corresponding service strategy is sent to the base station in the corresponding area. After that, the intention management server evaluates the effect of the intention realization and reports the effect of the intention realization.

[0218] In the second example, suppose the user wants to set the intention expectations corresponding to three different areas, but the user is not clear about what scenarios each of these three areas belongs to. Based on this, the user can provide three sets of work parameter data corresponding to the three areas, such as Figure 8As shown, the three groups of working parameter data are working parameter data of multiple base stations in area 1, working parameter data of multiple base stations in area 2, and working parameter data of multiple base stations in area 3. Based on the working parameter data in each area, the user terminal determines that area 1 has long-term high traffic characteristics, area 2 has tidal traffic characteristics, and area 3 has long-term low traffic characteristics. According to the scene characteristics of the three areas, the user terminal performs scene matching in the supported scene list corresponding to the network energy-saving service supported by the intent management server. Area 1 matches the urban scene, area 2 matches the suburban scene, and area 3 matches the rural scene. The scene information of the supported scene list is pre-configured with intention expectations of various scenes. On this basis, the user terminal obtains the pre-set intention expectation 80 in the urban scene, the intention expectation 81 in the suburban scene, and the intention expectation 82 in the rural scene. After that, based on these three intention expectations, the scene intention is issued.

[0219] Next, the intention acquisition device provided in the embodiment of the present application is introduced.

[0220] Fig. 9 is a schematic diagram of the structure of an intention acquisition device provided in an embodiment of the present application. The intention acquisition device 900 can be deployed in the user terminal of the aforementioned embodiment. Fig. 9 , the intention acquisition device 900 may include: a receiving module 901 and a processing module 902.

[0221] The receiving module 901 is used to execute step 301 in the aforementioned embodiment; the processing module 902 is used to execute step 302 in the aforementioned embodiment.

[0222] Optionally, the device 900 further includes a sending module 903, which is used to: in response to a scene information query instruction of the user, send a scene information query request to the intent management server, where the scene information query request includes an identifier of the first service.

[0223] Optionally, the scene information of each scene also includes a scene identifier of the corresponding scene, and the intention setting reference information of each scene includes at least one recommended expected target for the corresponding scene. The processing module 902 is specifically used to: display the scene identifiers of multiple scenes; receive the scene identifier of the first scene input by the user, and the first scene requirement information includes the scene identifier of the first scene; display at least one recommended expected target for the first scene; in response to the user's selection operation of the first expected target among the at least one recommended expected target of the first scene, generate the intention expectation under the first scene based on the scene identifier and the first expected target of the first scene; based on the intention expectation under the first scene, generate the first intention of the first business.

[0224] Optionally, the intention setting reference information for each scenario also includes at least one recommended business strategy and recommended business policy constraint for the corresponding scenario, and the processing module 902 is specifically used to: display at least one recommended business strategy for the first scenario; in response to a user's selection operation of a first recommended business strategy among at least one recommended business strategy for the first scenario, generate an expected context for the first scenario based on the first recommended business strategy and the recommended business policy constraint; based on the scene identifier, expected context and first expected target of the first scene, generate an intention expectation for the first scenario, and the intention expectation for the first scenario includes the scene identifier, expected context and first expected target of the first scene.

[0225] Optionally, the receiving module 901 is also used to receive general expected indicators of the first business in multiple scenarios input by the user; the processing module 902 is specifically used to generate the intention expectation in the first scenario based on the scenario identifier of the first scenario, the first expected goal and the general expected goal, and the first expected goal is a personalized expected goal in the first scenario.

[0226] Optionally, the scene information of each scene also includes scene characteristics of the corresponding scene, and the processing module 902 is specifically used to: obtain the engineering parameter data of multiple business objects in the same scene applicable to the first business, and the first scene requirement information includes the engineering parameter data of multiple business objects; based on the engineering parameter data of multiple business objects, determine the characteristics of the scenes in which the multiple business objects are located; determine the first scene from multiple scenes whose scene characteristics match the characteristics of the scenes in which the multiple business objects are located; set reference information based on the intention of the first scene to obtain the first intention of the first business.

[0227] Optionally, the intention setting reference information of the first scene includes the intention expectation in the first scene, and the intention expectation in the first scene includes the scene identifier of the first scene and the expected target of the first scene.

[0228] Optionally, the sending module 903 is further used to send the first intention of the first service to the intention management server; the receiving module 901 is further used to receive the implementation effect report of the first intention fed back by the intention management server.

[0229] Optionally, the sending module 903 is specifically used to send the first intention of the first service to the intent management server through the intent interface, and the intent interface includes an expected scenario list attribute, and the expected scenario list attribute is used to represent the scenario indicated by the user's scenario requirement information.

[0230] In an embodiment of the present application, for a certain service, such as the first service, the user terminal can obtain the scene information of multiple scenes corresponding to the first service from the intent management server, wherein the scene information of each scene includes the intention setting reference information of the corresponding scene. Based on this, the user terminal can obtain the intention expectation in the first scene indicated by the user's scene requirement information according to the intention setting reference information of each scene, and then obtain the first intention. It can be seen that the intent acquisition method provided in the embodiment of the present application supports scene-based intent setting, and the user can provide the scene requirement information of the first service to realize the setting of the intention expectation in a certain scene, which reduces the ability requirements of the user, reduces the probability of inaccurate intent setting, and improves the efficiency of intent setting.

[0231] Fig.10 1 is a schematic diagram of another structure of an intention acquisition device provided in an embodiment of the present application. The intention acquisition device 1000 can be deployed in the intention management server of the aforementioned embodiment, see Fig.10 The intention acquisition device 1000 includes a sending module 1001, a receiving module 1002 and a processing module 1003.

[0232] The sending module 1001 is used to execute step 301 in the aforementioned embodiment; the receiving module 1002 is used to execute step 303 in the aforementioned embodiment; and the processing module 1003 is used to execute step 304 in the aforementioned embodiment.

[0233] Optionally, the sending module 1001 is specifically used to: send scene information of multiple scenes to the user terminal through the intent processing function interface, the intent processing function interface includes a supported scene list attribute, and the supported scene list attribute is used to indicate the scenes supported by the intent management server.

[0234] Optionally, the receiving module 1002 is specifically used to: receive the first intent through an intent interface, the intent interface includes an expected scene list attribute, and the expected scene list attribute is used to represent the scene indicated by the user's scene requirement information.

[0235] Optionally, the intended expectation in the first scenario includes an identifier of the first scenario and an expected target of the first scenario.

[0236] Optionally, the processing module 1003 is specifically used to: determine a first desired object in the first scene based on an identifier of the first scene; generate a first business policy based on an expected goal of the first scene; send the first business policy to the first desired object, and the first desired object is used to execute the first business policy.

[0237] Optionally, the intention expectation in the first scenario also includes an expected context, and the processing module 1003 is specifically used to generate a first business strategy based on the expected target and the expected context of the first scenario.

[0238] Optionally, the receiving module 1002 is further used to: receive the execution result of the first business policy sent by the first desired object; the sending module 1001 is further used to: send a report on the implementation effect of the first intention to the user terminal based on the execution result of the first business policy.

[0239] Optionally, there are multiple first scenarios, and the processing module is specifically used to: detect whether there is a conflict between the intention expectations under the multiple first scenarios; if there is no conflict between the intention expectations under the multiple first scenarios, execute the first intention.

[0240] In an embodiment of the present application, the intent management server can provide the user terminal with scene information of multiple scenes of the first service. The scene information of each scene includes the intention setting reference information of the corresponding scene. Based on this, the user terminal can obtain the intention expectation in the first scene indicated by the user's scene requirement information according to the intention setting reference information of each scene, and then obtain the first intention. It can be seen that the intent acquisition method provided in the embodiment of the present application supports scene-based intent setting, and the user can provide the scene requirement information of the first service to realize the setting of the intention expectation in a certain scene, which reduces the ability requirements of the user, reduces the probability of inaccurate intent setting, and improves the efficiency of intent setting.

[0241] It should be noted that the division of modules in the various intention acquisition devices provided in the above embodiments is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0242] If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device or processor to execute all or part of the steps of the method of each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0243] In addition, the intention acquisition device and the intention acquisition method embodiment provided in the above embodiments belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0244] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0245] In each embodiment of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment according to their inherent logical relationship. In the embodiment of the present application, "at least one" refers to one or more, and "multiple" refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of the embodiment of the present application, the character " / " generally indicates that the front and back associated objects are in an "or" relationship. In the present application, "first", "second" and various digital numbers are only for the convenience of description, and are not used to limit the scope of the embodiment of the present application. For example, to distinguish different messages, etc., rather than to describe a specific order or sequence.

[0246] It is understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic.

[0247] Finally, it should be noted that the above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for acquiring intention, characterized in that: Applied to a user terminal, the method comprises: Receive scene information of multiple scenes corresponding to the first service sent by the intent management server, where the scene information of each scene includes intent setting reference information of the corresponding scene; Based on the intention setting reference information of the multiple scenarios and the user's first scenario requirement information, the first intention of the first service is obtained, the first intention includes the intention expectation under the first scenario among the multiple scenarios, and the first scenario requirement information is used to indicate the first scenario.

2. The method according to claim 1, characterized in that Before receiving the scene information of multiple scenes corresponding to the first service sent by the intention management server, the method further includes: In response to a scene information query instruction from a user, a scene information query request is sent to the intent management server, wherein the scene information query request includes an identifier of the first service.

3. The method according to claim 1 or 2, characterized in that: The scenario information of each scenario also includes a scenario identifier of the corresponding scenario, the intention setting reference information of each scenario includes at least one recommended expected target of the corresponding scenario, and acquiring the first intention of the first service based on the intention setting reference information of the multiple scenarios and the first scenario requirement information of the user includes: Display scene identifiers of the multiple scenes; receiving a scene identifier of the first scene input by a user, wherein the first scene requirement information includes the scene identifier of the first scene; displaying at least one recommended desired goal for the first scenario; In response to a user selecting a first desired target among at least one recommended desired target for the first scenario, generating an intention expectation for the first scenario based on a scenario identifier of the first scenario and the first desired target; Based on the intention expectation in the first scenario, a first intention of the first business is generated.

4. The method according to claim 3, characterized in that The intention setting reference information of each scenario also includes at least one recommended business strategy and recommended business strategy constraint of the corresponding scenario. The generating of the intention expectation under the first scenario based on the scenario identifier of the first scenario and the first expected goal includes: Displaying at least one recommended business strategy for the first scenario; In response to a user selecting a first recommended business strategy among at least one recommended business strategy for the first scenario, generating an expected context for the first scenario based on the first recommended business strategy and the recommended business strategy constraint; Based on the scenario identification, expected context and first expected target of the first scenario, the intention expectation in the first scenario is generated, and the intention expectation in the first scenario includes the scenario identification, expected context and first expected target of the first scenario.

5. The method according to claim 3, characterized in that: The method further comprises: Receiving common expected indicators of the first business in the multiple scenarios input by a user; The generating the intention expectation in the first scenario based on the scenario identifier of the first scenario and the first expected target includes: Based on the scenario identifier of the first scenario, the first expected goal and the general expected goal, an intention expectation under the first scenario is generated, and the first expected goal is a personalized expected goal of the first scenario.

6. The method according to claim 1 or 2, characterized in that: The scenario information of each scenario also includes scenario features of the corresponding scenario, and the acquiring the first intent of the first service based on the intention setting reference information of the multiple scenarios and the first scenario requirement information of the user includes: Acquire engineering parameter data of a plurality of business objects in the same scenario applicable to the first business, wherein the first scenario requirement information includes the engineering parameter data of the plurality of business objects; Determining, based on the work parameter data of the multiple business objects, characteristics of the scenarios in which the multiple business objects are located; Determine, from the multiple scenes, a first scene whose scene characteristics match the characteristics of the scenes where the multiple business objects are located; Based on the intention setting reference information of the first scenario, a first intention of the first service is acquired.

7. The method according to claim 6, characterized in that The intention setting reference information of the first scene includes the intention expectation in the first scene, and the intention expectation in the first scene includes the scene identifier of the first scene and the expected target of the first scene.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: Sending a first intent of the first service to the intent management server; Receive a report on the implementation effect of the first intention fed back by the intention management server.

9. The method according to claim 8, characterized in that Sending the first intent of the first service to the intent management server includes: The first intent of the first service is sent to the intent management server through an intent interface, wherein the intent interface includes an expected scenario list attribute, and the expected scenario list attribute is used to represent the scenario indicated by the user's scenario requirement information.

10. The method according to any one of claims 1 to 9, characterized in that: The first service is a network energy-saving service.

11. A method for acquiring intention, characterized in that: Applied to an intent management server, the method comprises: Sending scenario information of multiple scenarios corresponding to the first service to the user terminal, where the scenario information of each scenario includes intention setting reference information of the corresponding scenario; Receive the first intention of the first service and execute the first intention, wherein the first intention is obtained by the user terminal based on the intention setting reference information of the multiple scenarios and the user's first scenario requirement information, and the first intention includes the intention expectation under the first scenario among the multiple scenarios, and the first scenario requirement information is used to indicate the first scenario.

12. The method according to claim 11, characterized in that The sending the scenario information of the multiple scenarios corresponding to the first service to the user terminal includes: The scene information of the multiple scenes is sent to the user terminal through an intent processing function interface, and the intent processing function interface includes a supported scene list attribute, and the supported scene list attribute is used to indicate the scenes supported by the intent management server.

13. The method according to claim 11 or 12, characterized in that: The first intention of receiving the first service includes: The first intent is received through an intent interface, wherein the intent interface includes an expected scenario list attribute, and the expected scenario list attribute is used to represent the scenario indicated by the user's scenario requirement information.

14. The method according to any one of claims 11 to 13, characterized in that: The intended expectation in the first scenario includes an identifier of the first scenario and an expected target of the first scenario.

15. The method according to claim 14, characterized in that The executing the first intention includes: Based on the identification of the first scene, determining a first desired object within the first scene; Based on the desired goal of the first scenario, generating a first business strategy; The first service policy is sent to the first desired object, where the first desired object is used to execute the first service policy.

16. The method according to claim 15, characterized in that The intention expectation in the first scenario also includes an expected context, and the generating of the first business strategy based on the expected goal of the first scenario includes: The first business policy is generated based on the desired goal of the first scenario and the desired context.

17. The method according to claim 15 or 16, characterized in that The method further comprises: receiving an execution result of the first service policy sent by the first desired object; Based on the execution result of the first business policy, a report on the implementation effect of the first intention is sent to the user terminal.

18. The method according to any one of claims 11 to 17, characterized in that: There are multiple first scenarios, and executing the first intention includes: Detect whether there is a conflict between the intention expectations in multiple first scenarios; If there is no conflict between the intention expectations in the multiple first scenarios, the first intention is executed.

19. An intention acquisition device, characterized in that: The device comprises at least one module, and the at least one module is used to execute the intention acquisition method described in any one of claims 1 to 18.

20. A computer device, characterized in that: The computer device includes a processor, which is used to execute at least one program instruction or code stored in a memory to implement the intention acquisition method described in any one of claims 1 to 18.

21. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on a computer device, the computer device executes the intention acquisition method according to any one of claims 1 to 18.

Images