Network intent processing method and related devices

Abstract

The embodiment of the present disclosure provides a network intention processing method and related equipment, and belongs to the technical field of network. The method comprises the following steps: a user use case interactive interface (UUI) acquires a first network intention of a first object, the first network intention being voice information comprising a first business requirement proposed by the first object; the UUI performs translation processing on the first network intention to obtain first network intention translation information, the first network intention translation information being text information comprising the first business requirement; the UUI acquires a first intention instance identifier of the first object; the UUI generates a first intention instance, the first intention instance comprising the first network intention translation information and the first intention instance identifier; according to the first intention instance, first scene use case service identifier information and first scene use case service information that match the first business requirement are determined; and the first intention instance, the first scene use case service identifier information and the first scene use case service information are associated and stored to an active available resource library (AAI).

Description

Technical Field

[0001] This disclosure relates to the field of network technology, and more specifically, to a network intent processing method, a network intent processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] In intent-based networking (IBN, also known as intention-based network, intention-based graph network, or intent-based network), intelligent software determines how to translate intents (also known as user intents, network intents, or user-network intents) into configurations for specific infrastructure (such as network devices) so that the network operates in the desired manner. Intent-based networking provides lifecycle management for network infrastructure, including design, implementation, operation, and assurance, offering a new approach to building and operating networks and improving network availability and flexibility.

[0003] Although the concept of intent-based networking has been proposed in academia for many years, no mature operator has yet implemented it. Related research has not yet mentioned, nor has it considered, closed-loop management of user network intent. Summary of the Invention

[0004] This disclosure provides a network intent processing method, a network intent processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product, which can manage network intents.

[0005] This disclosure provides a network intent processing method, the method comprising: a use case user interface (UUI) acquiring a first network intent of a first object, the first network intent being voice information including a first business requirement proposed by the first object; the UUI translating the first network intent to obtain first network intent translation information, the first network intent translation information being text information including the first business requirement; the UUI acquiring a first intent instance identifier of the first object; the UUI generating a first intent instance, the first intent instance including the first network intent translation information and the first intent instance identifier; determining first scenario use case service identifier information and first scenario use case service information matching the first business requirement based on the first intent instance; and associating and storing the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information to an Active and Available Inventory (AAI).

[0006] This disclosure provides a network intent processing apparatus, comprising: a user use case interaction interface (UUI) for acquiring a first network intent of a first object, wherein the first network intent is voice information including a first service requirement proposed by the first object; the UUI is further configured to translate the first network intent to obtain first network intent translation information, wherein the first network intent translation information is text information including the first service requirement; the UUI is further configured to acquire a first intent instance identifier of the first object; the UUI is further configured to generate a first intent instance, wherein the first intent instance includes the first network intent translation information and the first intent instance identifier; and a processing unit for determining, based on the first intent instance, first scenario use case service identifier information and first scenario use case service information matching the first service requirement; the processing unit is further configured to associate and store the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information to an active available resource library (AAI).

[0007] This disclosure provides an electronic device, including: at least one processor; and a storage device configured to store at least one program, which, when executed by the at least one processor, causes the at least one processor to implement the method described in any embodiment.

[0008] This disclosure provides a computer-readable storage medium storing a computer program for execution by an electronic device, wherein the program, when executed by a processor, implements the method in any of the possible implementations described above.

[0009] This disclosure provides a computer program product containing instructions. When the computer program product is run on an electronic device, it causes the electronic device to execute the instructions of the methods described above or any possible implementation of the methods described above.

[0010] In some embodiments of this disclosure, the technical solutions provided involve obtaining a first network intent of a first object through a User Use Case Interaction Interface (UUI). The first network intent is voice information including a first business requirement proposed by the first object. The first network intent is then translated through the UUI to obtain first network intent translation information, which is text information including the first business requirement. Next, the first intent instance identifier of the first object is obtained through the UUI. Then, a first intent instance is generated through the UUI, which includes the first network intent translation information and the first intent instance identifier. Finally, based on the first intent instance, first scenario use case service identifier information and first scenario use case service information matching the first business requirement are determined. The first intent instance, the first scenario use case service identifier information, and the first scenario use case service information are then associated and stored in the Active Available Resource Library (AAI). In other words, by generating the first intent instance, it can be used to standardize and associate the storage and interaction of the first network intent and the first network intent translation information. Attached Figure Description

[0011] Figure 1 A flowchart illustrating a network intent processing method according to an embodiment of the present disclosure is shown schematically.

[0012] Figure 2 The illustration schematically depicts an intent instance management model based on the ONAP (Open Network Automation Platform) open-source architecture, according to an embodiment of the present disclosure.

[0013] Figure 3 A flowchart illustrating a scenario use case management intent instance is shown schematically according to an embodiment of the present disclosure.

[0014] Figure 4 A flowchart illustrating an embodiment of the present disclosure of an intent management model managing intent instances is shown.

[0015] Figure 5 A schematic diagram of an intent instance data mapping relationship table according to an embodiment of the present disclosure is shown.

[0016] Figure 6 A schematic block diagram of a network intent processing apparatus according to an embodiment of the present disclosure is shown.

[0017] Figure 7 A schematic block diagram of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0018] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be more thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art.

[0019] In this disclosure, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. The terms "first," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., do not necessarily imply differences.

[0020] Figure 1 A flowchart illustrating a network intent processing method according to an embodiment of the present disclosure is shown schematically. Figure 1 As shown, the method provided in this disclosure embodiment may include the following steps.

[0021] In step S110, the user interface UUI obtains the first network intent of the first object, which is voice information including the first business requirement proposed by the first object.

[0022] The object in this disclosure embodiment can be a user, the first object can be any user, and the second object mentioned below can be another user that is different from the user corresponding to the first object.

[0023] In this embodiment of the disclosure, network intent can also be referred to as user intent. User intent refers to a user's explicit request to the operator in words to meet their own business needs. For example, a user says, "My mobile phone number is 123456789, and my home is located at Unit XXX, Building XX, XX Community, XX District, A Region. I want to watch 8K ultra-high-definition videos on my mobile phone." In the following text, the first network intent can also be referred to as the first user intent, and similarly, the second network intent can also be referred to as the second user intent.

[0024] In this embodiment of the disclosure, the first business requirement, the second business requirement, and the third business requirement may be the same or different, and can be set according to actual needs.

[0025] In step S120, the UUI performs translation processing on the first network intent to obtain first network intent translation information, which is text information including the first service requirement.

[0026] In this embodiment of the disclosure, the translation (or escaping) process converts the original voice-based first network intent into text-based translated information. Therefore, this translated information still carries the first service requirement proposed by the first object. For example, the text generated after translating the above-mentioned voice-based user intent is "My mobile phone number is 123456789, my home is in Unit XXX, Building XX, XX Community, XX District, A Region, and I want to watch 8K ultra-high-definition video on my mobile phone."

[0027] In step S130, the UUI obtains the first intent instance identifier of the first object.

[0028] In this embodiment of the disclosure, the intent instance identifier (ID) is used to uniquely identify the identity information of each object or each user. While the user intent of the same user may change, the intent instance ID of the same user remains constant. Different user intents of the same user can correspond to the same intent instance ID. For example, the first network intent and the second network intent of the first object both correspond to the first intent instance ID. Different users can be assigned different intent instance IDs; for example, the second object can be assigned a second intent instance ID.

[0029] In step S140, the UUI generates a first intent instance, which includes the first network intent translation information and the first intent instance identifier.

[0030] In this embodiment of the disclosure, the intent instance normalizes the user's request to the network (network intent) and converts speech into text. The user intent is what the user says in words (e.g., a sentence), and the intent instance is the text generated after translating this sentence (e.g., the first network intent translation information obtained after translating the first network intent) plus an ID that identifies the user (e.g., the first intent instance ID). The user intent can change, but the user intent at any given moment is unique. The user intent of this user at this moment is the intent instance at this moment, and all user intents of the same user correspond to the same intent instance ID.

[0031] For example, if a user wants to watch a video online, the escaped first intent instance = watch video + unique first intent instance ID.

[0032] In step S150, the first scenario use case service identifier information and the first scenario use case service information that match the first business requirement are determined based on the first intent instance.

[0033] In an exemplary embodiment, the first scenario use case service identification information may include the first scenario use case service identifier and the first scenario use case service identifier generation time; the first scenario use case service information may include the first network parameter information of the first scenario use case service and the first scenario use case service update time.

[0034] In this embodiment of the disclosure, a service instance refers to a product (or scenario use case) and network performance indicators that the operator maps to meet the business needs of the customer based on an intent instance. For example, the service that the operator can provide based on a product / first scenario use case that meets the first business needs of the customer is called a first scenario use case service, and the network performance indicators of the product / first scenario use case are called the first network parameter information of the first scenario use case service, that is, the product information and network performance indicators corresponding to the service instance.

[0035] In this embodiment of the disclosure, a unique scenario use case service identifier, also known as a service instance ID, is assigned to each product / scenario use case. For example, assuming that the scenario use case that matches the first business requirement is the first scenario use case, then the corresponding first scenario use case service ID is obtained.

[0036] For example, assuming the first intent instance = watching video + first intent instance ID, then the service instance = broadband product + bandwidth 300M + latency 100ms + low guarantee level. Here, the bandwidth product is assumed to be the first scenario use case service or product, and the bandwidth 300M, latency 100ms, and low guarantee level are the first network parameter information.

[0037] In this embodiment, the intent instance and service instance are completely unknown to the user. The user's intent is also completely unknown to the underlying network devices. The intent instance stores the user's intent information. The service instance contains the corresponding product information and network performance metrics. Binding the intent instance ID to the service instance ID binds the user intent to the network performance metrics.

[0038] In step S160, the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information are associated and stored in the Active Available Resource Library (AAI).

[0039] In an exemplary embodiment, determining the first scenario use case service identifier information and the first scenario use case service information matching the first business requirement based on the first intent instance may include: the UUI sending the first intent instance to the scenario use case module in the Service Orchestration (SO); the scenario use case module determining the first scenario use case matching the first business requirement, the first network parameter information of the first scenario use case service, and the update time of the first scenario use case service based on the first network intent translation information; and the scenario use case module obtaining the first scenario use case service identifier and the generation time of the first scenario use case service identifier based on the first scenario use case.

[0040] For example, such as Figure 5 As shown, based on the data table relationship mapping in the intent instance data mapping table stored in AAI, let's assume the first intent instance in the table is called the first intent instance. The first intent instance includes the text generated after the user intent is translated: "My mobile phone number is 123456789, my home is in Unit XXX, Building XX, XX Community, XX District, A Region, I want to watch 8K ultra-high-definition video on my mobile phone" (first network intent translation information) + 123e4567-e89b-12d3-a456-426655440000 (first intent instance ID). The first scenario use case matching this first network intent translation information is assumed to be "5G (5th Generation Mobile Communication Technology) end-to-end slicing", and the service ID generation time of the first scenario use case is assumed to be "2050.10.1". "9:30:22", the service identifier for the first scenario use case is assumed to be "A_470be345-6a5a-4935-b09d-f1268689adf4", the update time for the first scenario use case service is assumed to be "2050.10.10", and the first network parameter information for the first scenario use case service is assumed to be "user downlink experience rate 1,000,000 Kbps, user uplink experience rate 5,000,000 Kbps, latency 100 ms, maximum number of supported terminals is 20, terminal mobility level is region A, and resource sharing level is full sharing".

[0041] In this embodiment of the disclosure, the intent instance ID is exemplified by a 32-bit UUID (Universally Unique Identifier), but this disclosure is not limited to this. The scenario use case service ID is exemplified by the scenario use case code_UUID, but this disclosure is not limited to this. For example, assuming the code for the first scenario use case "5G end-to-end slicing" is A, the corresponding first scenario use case service ID is "A_470be345-6a5a-4935-b09d-f1268689adf4".

[0042] In an exemplary embodiment, associating the storage of the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information to the Active Available Resource Library (AAI) may include: the scenario use case module sending the first intent instance, the first scenario use case, the first scenario use case service identifier information, and the first scenario use case service information to the AAI.

[0043] In an exemplary embodiment, the first scenario use case service identification information may include the first scenario use case service identifier and the first scenario use case service identifier generation time; the first scenario use case service information may include the first network parameter information of the first scenario use case service and the first scenario use case service update time.

[0044] In an exemplary embodiment, determining the first scenario use case service identifier information and the first scenario use case service information matching the first business requirement based on the first intent instance may include: the UUI determining the first scenario use case matching the first business requirement, the first network parameter information of the first scenario use case service, and the update time of the first scenario use case service based on the first network intent translation information; and the UUI obtaining the first scenario use case service identifier and the first scenario use case service identifier generation time based on the first scenario use case.

[0045] In an exemplary embodiment, associating the storage of the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information to the Active Available Resource Library (AAI) may include: the UUI sending the first intent instance, the first scenario use case, the first scenario use case service identifier information, and the first scenario use case service information to the AAI.

[0046] In an exemplary embodiment, the method may further include: obtaining a second network intent of the first object through the UUI, the second network intent being voice information including a second service requirement proposed by the first object; performing translation processing on the second network intent through the UUI to obtain second network intent translation information, the second network intent translation information being text information including the second service requirement; generating a second intent instance through the UUI, the second intent instance including the second network intent translation information and a first intent instance identifier; determining second scenario use case service identifier information and second scenario use case service information matching the second service requirement based on the second intent instance; and associating and storing the second intent instance, the second scenario use case service identifier information, and the second scenario use case service information to the AAI.

[0047] In an exemplary embodiment, determining the second scenario use case service identifier information and the second scenario use case service information that match the second service requirement based on the second intent instance may include: sending the second intent instance to the scenario use case module in the service orchestration SO through the UUI; the scenario use case module determining the second scenario use case service identifier information and the second scenario use case service information that match the second service requirement based on the second network intent translation information;

[0048] In an exemplary embodiment, associating the storage of the second intent instance, the second scenario use case service identifier information, and the second scenario use case service information to the AAI may include: the scenario use case module sending the second intent instance, the second scenario use case service identifier information, and the second scenario use case service information to the AAI.

[0049] In an exemplary embodiment, determining the second scenario use case service identifier information and the second scenario use case service information that match the second business requirement based on the second intent instance may include: the UUI determining the second scenario use case service identifier information and the second scenario use case service information that match the second business requirement based on the second network intent translation information.

[0050] In an exemplary embodiment, associating the storage of the second intent instance, the second scenario use case service identifier information, and the second scenario use case service information to the AAI may include: the UUI sending the second intent instance, the second scenario use case service identifier information, and the second scenario use case service information to the AAI.

[0051] In an exemplary embodiment, the second scenario use case service identifier information may include the first scenario use case service identifier and the generation time of the second scenario use case service identifier of the first scenario use case, and the second scenario use case service information may include the second network parameter information and the update time of the second scenario use case service of the first scenario use case service; or, the second scenario use case service identifier information may include the second scenario use case service identifier and the generation time of the third scenario use case service identifier of the second scenario use case, and the second scenario use case service information may include the third network parameter information and the update time of the third scenario use case service of the second scenario use case service.

[0052] In an exemplary embodiment, if the first scenario use case still matches the second business requirement, the service identification information of the second scenario use case may include the service identification of the first scenario use case and the generation time of the service identification of the second scenario use case (i.e., the new generation time of the service identification of the first scenario use case); the service information of the second scenario use case may include the second network parameter information of the service of the first scenario use case and the update time of the service of the second scenario use case (i.e., the product or service provided by the first scenario use case remains unchanged, but the network performance indicators of the service of the first scenario use case have changed).

[0053] For example, such as Figure 5 As shown, assuming the first object updates its original first network intent "My mobile number is 123456789, my home is in Unit XXX, Building XX, XX Community, XX District, A Region, I want to watch 8K ultra-high-definition video on my phone" to the second network intent "The video is a bit choppy, please help me fix it," then the second intent instance is the text "The video is a bit choppy, please help me fix it" (i.e., the second network intent translation information) generated after translating the second user intent + "123e4567-e89b-12d3-a456-426655440000" (first intent instance ID). Assuming it still matches the first scenario use case "5G end-to-end slicing," then the associated stored information is still the first scenario use case service identifier "A_470be345-6a5a-4935-b09d-f1268689adf4," and the second scenario use case service identifier generation time is updated to "2050.10.1." "9:33:12", the service update time for the second scenario use case is changed to "2050.10.11", and the second network parameter information is changed to "user downlink experience rate 2000000Kbps, user uplink experience rate 5000000Kbps, latency 50ms, maximum number of supported terminals is 20, terminal mobility level is region A, and resource sharing level is full sharing".

[0054] In an exemplary embodiment, if the second scenario use case matches the second business requirement, the service identification information of the second scenario use case may include the service identification of the second scenario use case and the generation time of the service identification of the third scenario use case (i.e., the generation time of the service identification of the second scenario use case); the service information of the second scenario use case may include the third network parameter information of the service of the second scenario use case and the update time of the service of the third scenario use case (i.e., the specific network performance indicators of the product or service provided by the second scenario use case).

[0055] For example, such as Figure 5 As shown, suppose the first object updates its original first network intent "My mobile phone number is 123456789, my home is in Unit XXX, Building XX, XX Community, XX District, A Region, I want to watch 8K ultra-high-definition video on my mobile phone" to the second network intent "I have established a nationwide company with business in every province, please open a dedicated line for me". Then the second intent instance is the text generated after translating the second user intent: "I have established a nationwide company with business in every province, please open a dedicated line for me" (i.e., the second network intent translation information) + "123e4567-e89b-12d3-a456-426655440000" (first intent instance ID). Assume that it matches the second scenario use case "Cross-layer cross-domain VPN (Virtual Private)". The scenario use case code is assumed to be B. The associated storage is the second scenario use case service identifier "B_a06aa497-027c-40d4-941d-6627a835677f". The third scenario use case service identifier generation time is updated to "2050.10.20 9:30:22", the third scenario use case service update time becomes "2050.10.20", and the third network parameter information becomes "user downlink experience rate 1000000Kbps, user uplink experience rate 5000000Kbps, latency 20ms, maximum supported terminals 500, terminal mobility level B region, resource sharing level full sharing".

[0056] In an exemplary embodiment, the method may further include: a Data Collection and Analysis Event Triggering Component (DCAE) obtaining the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information from the AAI; the DCAE sending the obtained first intent instance, the first scenario use case service identifier information, and the first scenario use case service information to a network device to configure the network device; the DCAE obtaining first network status feedback information from the network device; the DCAE returning the first network status feedback information to the UUI; and the UUI comparing the first network status feedback information with the first user intent to determine whether the first network status feedback information meets the first service requirement.

[0057] In an exemplary embodiment, the method may further include: desensitizing the first network intent translation information to remove the first object privacy information from the first network intent translation information; and exporting the first network intent, the first network intent translation information excluding the first object privacy information, and the first network status feedback information through the intent instance data export interface.

[0058] In an exemplary embodiment, the method may further include: the UUI sending a first close intent instance request for the first object to a scenario use case module in the SO, the first close intent instance request carrying the first intent instance identifier; the scenario use case module sending a first stop intent service request to the AAI, the first stop intent service request carrying the first intent instance identifier; and the AAI deleting the intent instance bound to the first intent instance identifier and its scenario use case service identifier information and scenario use case service information based on the first intent instance identifier carried in the received first stop intent service request.

[0059] In an exemplary embodiment, the method may further include: the UUI sending a first close intent instance request for the first object to the AAI, the first close intent instance request carrying the first intent instance identifier; the AAI deleting the intent instance bound to the first intent instance identifier and its scenario use case service identifier information and scenario use case service information according to the first intent instance identifier carried by the received first stop intent service request.

[0060] In an exemplary embodiment, the method may further include: the UUI acquiring a third network intent of a second object, the third network intent being voice information including a third service requirement proposed by the second object; the UUI performing translation processing on the third network intent to obtain third network intent translation information, the third network intent translation information being text information including the third service requirement; the UUI acquiring a second intent instance identifier of the second object; the UUI generating a third intent instance, the third intent instance including the third network intent translation information and the second intent instance identifier; determining third scenario use case service identifier information and third scenario use case service information matching the third service requirement based on the third intent instance; and associating and storing the third intent instance, the third scenario use case service identifier information, and the third scenario use case service information to the Active Available Resource Library (AAI).

[0061] The network intent processing method provided in this disclosure obtains a first network intent of a first object through a user interface (UUI). The first network intent is voice information including a first business requirement proposed by the first object. The first network intent is then translated through the UUI to obtain first network intent translation information, which is text information including the first business requirement. Then, the first intent instance identifier of the first object is obtained through the UUI. Next, a first intent instance is generated through the UUI. The first intent instance includes the first network intent translation information and the first intent instance identifier. Then, based on the first intent instance, first scenario use case service identifier information and first scenario use case service information matching the first business requirement are determined. The first intent instance, the first scenario use case service identifier information, and the first scenario use case service information are associated and stored in the Active Available Resource Library (AAI). That is, by generating the first intent instance, it can be used to standardize and associate the storage and interaction of the first network intent and the first network intent translation information.

[0062] The following is combined Figures 2 to 5 The methods provided in the embodiments of this disclosure are illustrated by examples.

[0063] This disclosure proposes a network intent management model and apparatus based on intent instances, which can be used for the management and storage of various network intents in a random intent graph network. By proposing the concept of intent instances, it is used to standardize and associate the storage and interactive updates of user intents, the storage, reading and updating of intent translation result parameters (network intent translation information), and the storage of network status feedback information.

[0064] Figure 2 This illustration schematically depicts an intent instance management model based on the ONAP open-source architecture according to an embodiment of this disclosure. Figure 2As shown, the intent instance management model (also known as the intent management model / network intent management model) can include a user interface (UUI).

[0065] UUI can be used to implement user interaction interfaces for intent input; UUI can also implement intent translation functions, such as using natural language processing for translation.

[0066] Figure 2 In this embodiment, two intent input interfaces are provided between UUI and AAI:

[0067] The first approach is for UUI to directly interact with the Activity Available Resource Library (Instance Repository) AAI to store and manage intent instances.

[0068] The second approach involves UUI interacting with AAI through the scenario use case module in the service orchestration SO to store and manage intent instances. Specifically, the service orchestration SO manages scenario use cases; for this approach, the scenario use case module in the SO is responsible for reading network intent translation information from UUI and storing it in AAI.

[0069] The Activity Available Resource Library (Instance Repository) AAI can be used to store intent instances.

[0070] The Data Collection Analytics and Events (DCAE) component can retrieve intent instance updates from AAI, enabling intent monitoring and analysis.

[0071] In AI / ML strategy selection, AI (Artificial Intelligence) refers to artificial intelligence, and ML (Machine Learning) refers to deep learning / machine learning. In this embodiment, the specific network parameter information for the scenario use case service is not hard-coded but learned through intelligent algorithms. Artificial intelligence and machine learning algorithms are used to train the specific network parameter information of the scenario use case service until it meets the business requirements of the intent instance, at which point the strategy is generated.

[0072] After the policy is generated, DCAE distributes the policy to specific network element information through the use case execution policy interface.

[0073] UUI uses the slice KPI monitoring interface to periodically obtain network information from DCAE after the policy is issued, as network status feedback information, such as obtaining the current bandwidth.

[0074] Figure 3 A flowchart illustrating a scenario use case management intent instance according to an embodiment of this disclosure is shown schematically. Figure 3As shown, the steps may include the following.

[0075] During the intent instance creation phase:

[0076] Step 1.1: UUI creates a new first intent instance ID. The first intent instance ID can be a 32-bit UUID, for example: 123e4567-e89b-12d3-a456-426655440000. One or more user intents issued by the same user are bound to the same intent instance ID. Different users create different intent instance IDs. If the user intent is voice, the intent instance is the result of the user intent voice-to-text conversion plus the corresponding intent instance ID created.

[0077] UUI binds the user intent (referring to the voice information input by the user, such as the first network intent) to the newly created first intent instance ID and sends it to the scenario use case module in SO. That is, UUI inputs the user intent into the scenario use case module in SO, carrying the intent instance ID.

[0078] For example, suppose that in step 1.1, the UUI inputs the first network intent translation information and the first intent instance ID into the scenario use case module in the SO.

[0079] Step 1.2: After the scenario use case module in SO receives the user intent sent by UUI and the intent instance ID it carries, the scenario use case module creates a use case service ID. The scenario use case module binds the intent instance ID and the use case service ID and stores it in AAI. That is, the scenario use case module sends the intent to AAI, carrying the intent instance ID and the use case service ID (i.e., scenario use case service ID), so as to save the intent in AAI (save intent with intent instance ID, use case service ID).

[0080] For example, the scenario use case module in SO sends the first network intent, the first intent instance, and the first scenario use case service identifier to AAI. AAI can use methods such as... Figure 5 The intent instance data shown is stored in the form of a data table.

[0081] Step 1.3: After AAI receives the intent sent by the scenario use case module in SO, along with the intent instance ID and use case service ID, it associates and stores them, and provides an intent monitoring interface for DCAE to listen to the latest user intent in real time. In other words, AAI provides the user intent to DCAE for monitoring.

[0082] Step 1.4: DCAE feeds back the network status to UUI.

[0083] For example, suppose the network state reported in step 1.4 is referred to as the first network state feedback information.

[0084] During the update intent phase:

[0085] Step 2.1: UUI sends an update users' intent to the scenario use case module in SO.

[0086] For example, suppose the second network intent, which refers to the user's intention to update the first object, can carry the second network intent translation information.

[0087] Step 2.2: After receiving the updated user intent sent by UUI, the scenario use case module in SO creates a new use case service ID and binds the new use case service ID to the updated user intent, storing it in AAI and associating it with an existing intent instance (such as the first intent instance in the above intent instance creation stage). That is, the scenario use case module sends the updated user intent to AAI, carrying the new use case service ID.

[0088] The new use case service ID can be a first scenario use case service identifier but with a new second scenario use case service identifier generation time, or it can be a second scenario use case service identifier different from the first scenario use case service identifier and with a third scenario use case service identifier generation time. That is, in this embodiment, if the matching scenario use case changes, the service instance ID changes accordingly; if the matching scenario use case remains unchanged, the service instance ID remains unchanged. When the specific network parameter information of the scenario use case service changes, the change time is recorded. Figure 5 The update time of the scenario use case service.

[0089] In this embodiment of the disclosure, if it is still the first object, the user intent update still retains the intent instance ID (e.g., the first intent instance ID) from the intent instance creation phase, indicating that the user intent update (second network intent) is bound to the new use case service ID. In this way, the two first network intents and second network intents bound to different use case service IDs can be associated through the first intent instance ID.

[0090] Step 2.3: After AAI receives the updated user intent carrying the new use case service ID sent by the scenario use case module in SO, it associates and stores it, and provides the new user intent to DCAE for monitoring through the intent monitoring interface.

[0091] The user's new intent could be, for example, the second network intent and the second intent instance mentioned above.

[0092] Step 2.4: DCAE reports the network status to UUI.

[0093] For example, suppose the network state fed back in step 2.4 is called the second network state feedback information.

[0094] During the close intent instance phase:

[0095] Step 3.1: UUI sends a stop intent service to the scenario use case module in SO.

[0096] For example, UUI sends a first close intent instance request for a first object to AAI, which carries the first intent instance ID.

[0097] Step 3.2: After receiving the stop intent service sent by UUI, the scenario use case module in SO sends the stop intent service to AAI, carrying the intent instance ID.

[0098] For example, the first intent instance ID carried in the first close intent instance request received by AAI can delete all intent instances, their scenario use case service identifiers and scenario use case service information stored in AAI that are bound to the first intent instance ID.

[0099] For example, with Figure 5Taking the six intent instances listed as examples, they are all bound to the first intent instance ID "123e4567-e89b-12d3-a456-426655440000". Therefore, the data in these six rows can be deleted.

[0100] The method provided in this disclosure, from the perspective of practical development and implementation, offers a network intent closed-loop management model and apparatus based on intent instances. Based on the intent instances provided in this disclosure, it is easy to achieve a unified association between user intents and scenario service configurations and network status, thereby realizing closed-loop protection of user network intents. It can also collect closed-loop offline historical data to achieve source tracing analysis of network protection capabilities, further improving network service quality.

[0101] The method provided in this disclosure ensures that users can meet their differentiated network needs, technically satisfying their desire for flexible network application selection and improving user experience. It lays the technical foundation for operators to provide differentiated services and user SLA (Service Level Agreement) guarantees, increasing product added value and achieving profit growth.

[0102] Figure 4 A flowchart illustrating the management of intent instances by an intent management model according to an embodiment of the present disclosure is shown schematically. Figure 4 As shown, the steps may include the following.

[0103] During the intent instance creation phase:

[0104] Step 4.1, UUI collects use case service IDs.

[0105] For example, UUI reads the first scenario use case service ID, binds the first network intent to the newly created first intent instance ID and the read first scenario use case service ID, and stores it in AAI.

[0106] In this embodiment of the disclosure, the UUI can obtain the use case service ID from the scenario use case module in the SO. The scenario use case module can generate the use case service ID based on the intent instance ID and return the use case service ID to the UUI. The UUI stores the mapping relationship between the intent instance ID and the use case service ID in the AAI, and the UUI manages the intent instances.

[0107] Step 4.2: UUI sends the intent to AAI, carrying the intent instance ID and use case service ID, to save the intent in AAI.

[0108] Step 4.3: After AAI receives the intent sent by UUI and the intent instance ID and use case service ID it carries, it associates and stores them, and then provides the user intent to DCAE for monitoring.

[0109] AAI provides a user intent monitoring interface for DCAE to listen to the latest user intents in real time.

[0110] Step 4.4: DCAE reports the network status to UUI.

[0111] During the intention update phase:

[0112] Step 5.1: UUI collects new use case service IDs and binds new user intents (such as second network intents) to the new use case service IDs.

[0113] Step 5.2, UUI sends the updated user intent to AAI, carrying the new use case service ID.

[0114] Step 5.3: After receiving the updated user intent sent by UUI carrying the new use case service ID, AAI associates the new user intent with the new use case service ID and stores it to associate it with the existing intent instance, and provides the new user intent to DCAE for monitoring.

[0115] Step 5.4: DCAE reports the network status to UUI.

[0116] During the closing intent instance phase:

[0117] Step 6.1: UUI sends a "stop intent service with intent instance ID" message to AAI. This means UUI can directly disable the intent service from AAI.

[0118] This disclosure provides embodiments that Figure 3 and Figure 4 During the implementation of the two intent management solutions on the live network, users can choose the one that best suits their needs.

[0119] Regarding intent networks, especially user network intent management, the relevant technologies do not mention the ability to manage user network intents in a closed loop, and there is no consideration for managing user intents in a closed loop.

[0120] This disclosure addresses the need for closed-loop management and storage of user network intents in the practice of customizable graph network applications by proposing a network intent management model device based on intent instances, which is the foundation for realizing customizable graph network applications.

[0121] On the one hand, embodiments of this disclosure propose the concept of intent instances for closed-loop management and storage of user network intents. On the other hand, embodiments of this disclosure provide two methods for creating intent instances, enabling centralized or distributed unified network intent management, wherein... Figure 2 It is centralized. Figure 3 It is distributed. Centralized network intent management is executed by the scenario use case module of service orchestration, while distributed network intent management is generated by UUI and managed by AAI. The method provided in this disclosure embodiment can manage and store user network intents in a closed loop, thereby achieving closed-loop protection for the business requirements put forward by users.

[0122] Figure 5 A schematic diagram of an intent instance data mapping relationship table according to an embodiment of the present disclosure is shown. Figure 5 As shown, the network intent management and data table (i.e., the intent instance data mapping relationship table) are based on intent instances:

[0123] Using the intent instance ID as the key ID, all user intent-related information for the same user can be associated and mapped, including but not limited to:

[0124] 1. Scenario Use Case Service ID (also known as Use Case Service ID or Service Instance ID) provides services based on different scenario use cases as user intent needs are continuously updated.

[0125] For example, cloud network private lines and 5G private lines support dual-scenario use case services. Therefore, there will be constantly changing use case service IDs bound to the same intent instance ID, and the use case service content of different scenarios (the specific network parameter information of the scenario use case service and the update time of the scenario use case service) will also be associated together.

[0126] Assuming the user intent (first network intent) in the intent instance creation step requires a service from a cloud-network leased line scenario use case (which can be called the first scenario use case), the use case service ID bound to this user intent refers to the cloud-network leased line scenario use case service ID. Subsequently, if the same user changes their business requirements (second business requirements), and also requires a service from a 5G leased line scenario use case (second scenario use case), the new user intent (second network intent) will be bound to the 5G leased line scenario use case service ID. A single intent instance ID can be used to associate the scenario use cases required by different user intents from the same user.

[0127] 2. User intent and intent translation information (network intent translation information): The user's constantly changing intents are linked together to linearly show the changes in user intent. The intent translation information and the specific network parameter information of the scenario use case service can show the changes in the network services provided. All of these information are associated with a unified intent instance ID. The specific network parameter information of the scenario use case service refers to the specific scenario use case and the specific values ​​of the corresponding network performance indicators in each scenario use case.

[0128] For example, such as Figure 5 As shown, the user's intent changed from "My mobile number is 123456789, my home is in Unit XXX, Building XX, XX Community, XX District, A Region, I want to watch 8K ultra-high-definition video on my mobile phone" to "The video is a bit choppy, please fix it for me", then to "The video is still a bit choppy, please fix it for me", then to "I have established a nationwide company with business in every province, please open a dedicated line for me", then to "I require strict confidentiality of the company's data", and finally to "I have a large video conference to hold today, please ensure that the conference can proceed smoothly". The specific network parameter information for the scenario use case service changes from "User downlink experience rate 1,000,000 Kbps, user uplink experience rate 5,000,000 Kbps, latency 100ms, maximum supported terminals 20, terminal mobility level A, resource sharing level full sharing" to "User downlink experience rate 2,000,000 Kbps, user uplink experience rate 5,000,000 Kbps, latency 50ms, maximum supported terminals 20, terminal mobility level A, resource sharing level full sharing", and then to "User downlink experience rate 3,000,000 Kbps, user uplink experience rate 5,000,000 Kbps, latency 20ms, maximum supported terminals 20, terminal mobility level A, resource sharing level full sharing". The initial setting was changed from "Full Sharing" to "User downlink experience rate 1,000,000 Kbps, user uplink experience rate 5,000,000 Kbps, latency 20ms, maximum number of supported terminals 500, terminal mobility level B, resource sharing level Full Sharing". Then it was changed to "User downlink experience rate 1,000,000 Kbps, user uplink experience rate 5,000,000 Kbps, latency 20ms, maximum number of supported terminals 500, terminal mobility level B, resource sharing level Dedicated". Finally, it was changed to "User downlink experience rate 1,000,000 Kbps, user uplink experience rate 5,000,000 Kbps, latency 10ms, maximum number of supported terminals 500, terminal mobility level B, resource sharing level Dedicated".

[0129] This intent instance data mapping can be used to assess, predict, and optimize the future network's ability to support user intents. For example, if the base station signal near a user's home is not very good, and the user in that community needs to watch 8K ultra-high-definition video at home, a 3,000,000 Kbps bandwidth, 20 ms latency video slicing product can be directly activated for the user.

[0130] For example, assuming there are 5 network performance metrics in total, the specific values ​​of these 5 metrics will be determined in the service instance generated based on the intent instance and the product.

[0131] For example, for the intent instance of installing broadband, the corresponding product / scenario use case mapped by the operator is broadband product, with performance indicators such as: uplink speed: 50M, downlink speed: 200M, latency: 100ms, and guarantee level: low.

[0132] The aforementioned performance metrics can be stored in the service instance as specific network parameter information for the scenario use case service. When configuring the network later, the specific configuration is performed on the network device according to the metrics of the service instance.

[0133] When a user's intent is updated to "Videos are buffering too much, please fix it," the intent instance is updated (the intent instance ID remains unchanged). The service instance adjusts its downlink speed from 200Mbps to 300Mbps (the service instance ID remains unchanged; it only changes if the carrier's product is changed).

[0134] After the network performance metrics corresponding to the intent instance are distributed to the network device, the performance of the live network is compared with that of the service instance to determine whether the user's business needs are met. The result of whether the user's business needs are met is then associated with the corresponding intent instance ID and stored in the database.

[0135] 3. Changes in network status for the same user represent the guarantee of the corresponding business services for the user's intent. The relevant information can linearly evaluate changes in network service capabilities, and then be used to assess, predict, and optimize the future network's ability to support user intent.

[0136] 4. Export and summarize anonymized data:

[0137] In network intent management, individual user information is isolated; network intents do not recognize detailed user information. Each user's intent is managed by a unique intent instance ID, and data between different users is isolated through this intent instance ID.

[0138] like Figure 2 As shown, regarding the aforementioned network intent information, the apparatus provided in this disclosure embodiment can also provide a de-identified data aggregation and export interface or an intent instance data export interface, which can be based on, for example... Figure 5 The table-relationship mapping model shown (intent instance data mapping data table) exports network intent-related information, providing a data foundation for the training and application of subsequent intent network-related intelligent algorithm models.

[0139] In this embodiment of the disclosure, user personal information is not exported when exporting network intent-related information. User intents may contain the user's personal privacy information, such as the user's home address where broadband is installed and the user's age. During intent translation, the user's privacy information is translated into text and stored in the intent instance. However, the user's privacy information is not exported during the export of network intent-related information.

[0140] For example, such as Figure 5 In the intent instance data mapping table shown, when exporting data for the user intent "My mobile phone number is 123456789, my home is in Unit XXX, Building XX, XX Community, District XX, A, and I want to watch 8K ultra-high-definition video on my mobile phone", only the "location information (District XX, XX Community, A)" and "watch 8K ultra-high-definition video" are exported. The user's mobile phone number is not exported, thus ensuring the security of user data.

[0141] This disclosure provides a network user intent management model based on intent instances, which is the foundation for the implementation of spontaneous intent graph network functions. Based on the model / device provided in this disclosure, closed-loop management of user intent and monitoring of network status can be realized, enabling closed-loop perception and feedback of user intent.

[0142] Meanwhile, this disclosure provides a function for summarizing and exporting anonymized user information data, including original user intent interaction information (network intent, referring to the user's initial input intent), intent translation result information (network intent translation information, which is the translated information after the original user intent interaction information has been translated, and may include the translated text information of the user intent and the intent instance ID), and network status feedback information. The network status feedback information can be stored in a dedicated database. By comparing the network status feedback information with the user intent in the intent instance, a result can be obtained as to whether the current network satisfies the user intent. Furthermore, a standard data specification is established, which can provide a data foundation for the training and application of subsequent intent network-related intelligent algorithm models.

[0143] Figure 6 A schematic block diagram of a network intent processing apparatus according to an embodiment of the present disclosure is shown. Figure 6 As shown, the network intent processing device 600 provided in this embodiment may include a user use case interaction interface UUI 610 and a processing unit 620.

[0144] UUI 610 can be used to obtain the first network intent of a first object, wherein the first network intent is voice information including the first service request proposed by the first object.

[0145] UUI 610 can also be used to translate the first network intent to obtain first network intent translation information, wherein the first network intent translation information is text information including the first service requirement.

[0146] UUI 610 can also be used to obtain the first intent instance identifier of the first object.

[0147] UUI 610 can also be used to generate a first intent instance, which includes the first network intent translation information and the first intent instance identifier.

[0148] Processing unit 620 can be used to determine first scenario use case service identifier information and first scenario use case service information that match the first business requirement based on the first intent instance.

[0149] Processing unit 620 can also be used to associate and store the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information to the Active Available Resource Library (AAI).

[0150] In an exemplary embodiment, the processing unit 620 may include a UUI 610.

[0151] In an exemplary embodiment, the processing unit 620 may include UUI 610 and scenario use case modules in SO.

[0152] Figure 6 Other aspects of the embodiments can be found in the other embodiments described above.

[0153] It should also be understood that the above is only to help those skilled in the art better understand the embodiments of this disclosure, and is not intended to limit the scope of the embodiments of this disclosure. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples given above. For example, some steps in the above methods may be unnecessary, or new steps may be added, etc. Alternatively, any combination of any two or more of the above embodiments may be used. Such modifications, changes, or combinations also fall within the scope of the embodiments of this disclosure.

[0154] It should also be understood that the above description of the embodiments of this disclosure focuses on highlighting the differences between the various embodiments. Similarities or differences not mentioned can be referred to each other, and for the sake of brevity, they will not be repeated here.

[0155] It should also be understood that the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this disclosure.

[0156] It should also be understood that in the embodiments of this disclosure, "pre-setting" or "pre-defining" can be achieved by pre-saving the corresponding code, table or other means that can be used to indicate relevant information in the device (e.g., including terminal and network devices), and this disclosure does not limit the specific implementation method.

[0157] It should also be understood that, in the various embodiments of this disclosure, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0158] The foregoing section detailed examples of network intent processing methods provided in this disclosure. It is understood that UUI, AAI, DCAE, SO, and the scenario use case module, in order to implement the aforementioned functions, include corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0159] The following is for reference. Figure 7 It shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of this application. Figure 7 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0160] Reference Figure 7 The electronic device provided in this embodiment may include: a processor 701, a communication interface 702, a memory 703, and a communication bus 704.

[0161] The processor 701, communication interface 702, and memory 703 communicate with each other via communication bus 704.

[0162] Optionally, the communication interface 702 can be an interface for a communication module, such as the interface for a GSM (Global System for Mobile communications) module. The processor 701 is used to execute the program. The memory 703 is used to store the program. The program may include a computer program containing computer operation instructions. The program may include a video client program.

[0163] The processor 701 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present disclosure.

[0164] The memory 703 may include high-speed RAM (random access memory) memory, and may also include non-volatile memory, such as at least one disk storage.

[0165] Specifically, the program can be used for: the User Interface (UUI) to obtain a first network intent of a first object, wherein the first network intent is voice information including a first business requirement proposed by the first object; the UUI to translate the first network intent to obtain first network intent translation information, wherein the first network intent translation information is text information including the first business requirement; the UUI to obtain a first intent instance identifier of the first object; the UUI to generate a first intent instance, wherein the first intent instance includes the first network intent translation information and the first intent instance identifier; determining a first scenario use case service identifier information and a first scenario use case service information matching the first business requirement based on the first intent instance; and associating and storing the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information to the Active Available Resource Library (AAI).

[0166] It should be understood that any number of elements in the accompanying drawings is for illustrative purposes only and not for limitation, and any naming is for distinction only and has no limiting meaning.

[0167] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0168] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A method for processing network intent, characterized in that, include: The user interface (UUI) obtains the first network intent of the first object, which is voice information including the first business requirement proposed by the first object. The UUI translates the first network intent to obtain first network intent translation information, which is text information including the first service requirement. The UUI obtains the first intent instance identifier of the first object; The UUI generates a first intent instance, which includes the first network intent translation information and the first intent instance identifier. Based on the first intent instance, determine the first scenario use case service identifier information and the first scenario use case service information that match the first business requirement; The first intent instance, the first scenario use case service identifier information, and the first scenario use case service information are associated and stored in the Active Available Resource Library (AAI).

2. The method according to claim 1, characterized in that, The first scenario use case service identifier information includes the first scenario use case service identifier and the generation time of the first scenario use case service identifier; The first scenario use case service information includes the first network parameter information of the first scenario use case service and the update time of the first scenario use case service; Specifically, determining the first scenario use case service identifier information and the first scenario use case service information that match the first business requirement based on the first intent instance includes: The UUI sends the first intent instance to the scenario use case module in the service orchestration SO; The scenario use case module determines, based on the first network intent translation information, the first scenario use case matching the first business requirement, the first network parameter information of the first scenario use case service, and the update time of the first scenario use case service; The scenario use case module obtains the service identifier of the first scenario use case and the generation time of the service identifier of the first scenario use case based on the first scenario use case. The association storage of the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information to the Active Available Resource Library (AAI) includes: The scenario use case module sends the first intent instance, the first scenario use case, the first scenario use case service identifier information, and the first scenario use case service information to the AAI.

3. The method according to claim 1, characterized in that, The first scenario use case service identifier information includes the first scenario use case service identifier and the generation time of the first scenario use case service identifier; The first scenario use case service information includes the first network parameter information of the first scenario use case service and the update time of the first scenario use case service; Specifically, determining the first scenario use case service identifier information and the first scenario use case service information that match the first business requirement based on the first intent instance includes: The UUI determines, based on the first network intent translation information, a first scenario use case that matches the first business requirement, the first network parameter information of the first scenario use case service, and the update time of the first scenario use case service; The UUI obtains the service identifier of the first scenario use case and the generation time of the service identifier of the first scenario use case based on the first scenario use case. The association storage of the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information to the Active Available Resource Library (AAI) includes: The UUI sends the first intent instance, the first scenario use case, the first scenario use case service identifier information, and the first scenario use case service information to the AAI.

4. The method according to claim 1, characterized in that, Also includes: The second network intent of the first object is obtained through the UUI, and the second network intent is voice information including the second service requirement proposed by the first object; The second network intent is translated using the UUI to obtain second network intent translation information, which is text information including the second service requirement. A second intent instance is generated through the UUI, the second intent instance including the second network intent translation information and the first intent instance identifier; Based on the second intent instance, determine the second scenario use case service identifier information and the second scenario use case service information that match the second business requirement; The second intent instance, the second scenario use case service identifier information, and the second scenario use case service information are associated and stored in the AAI.

5. The method according to claim 4, characterized in that, Based on the second intent instance, determine the second scenario use case service identifier information and the second scenario use case service information that match the second business requirement, including: The second intent instance is sent to the scenario use case module in the service orchestration SO via the UUI; The scenario use case module determines the second scenario use case service identifier information and the second scenario use case service information that match the second business requirement based on the second network intent translation information; The process of associating and storing the second intent instance, the second scenario use case service identifier information, and the second scenario use case service information with the AAI includes: The scenario use case module sends the second intent instance, the second scenario use case service identifier information, and the second scenario use case service information to the AAI.

6. The method according to claim 4, characterized in that, Based on the second intent instance, determine the second scenario use case service identifier information and the second scenario use case service information that match the second business requirement, including: The UUI determines the second scenario use case service identifier information and the second scenario use case service information that match the second service requirement based on the second network intent translation information; The process of associating and storing the second intent instance, the second scenario use case service identifier information, and the second scenario use case service information with the AAI includes: The UUI sends the second intent instance, the second scenario use case service identifier information, and the second scenario use case service information to the AAI.

7. The method according to claim 4, characterized in that, The second scenario use case service identifier information includes the first scenario use case service identifier and the generation time of the second scenario use case service identifier. The second scenario use case service information includes the second network parameter information of the first scenario use case service and the update time of the second scenario use case service. or, The second scenario use case service identification information includes the second scenario use case service identification and the third scenario use case service identification generation time. The second scenario use case service information includes the third network parameter information of the second scenario use case service and the third scenario use case service update time.

8. The method according to claim 1, characterized in that, Also includes: The data collection and analysis event triggering component DCAE obtains the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information from the AAI. The DCAE sends the acquired first intent instance, first scenario use case service identifier information, and first scenario use case service information to the network device to configure the network device. The DCAE acquires the first network status feedback information of the network device; The DCAE returns the first network status feedback information to the UUI; The UUI compares the first network status feedback information with the first network intent to determine whether the first network status feedback information meets the first service requirement.

9. The method according to claim 8, characterized in that, Also includes: The first network intent translation information is desensitized to remove the first object privacy information from the first network intent translation information; The first network intent, the first network intent translation information excluding the privacy information of the first object, and the first network status feedback information are exported through the intent instance data export interface.

10. The method according to claim 1, characterized in that, Also includes: The UUI sends a first shutdown intent instance request for the first object to the scenario use case module in the SO, and the first shutdown intent instance request carries the first intent instance identifier; The scenario use case module sends a first stop intent service request to the AAI, and the first stop intent service request carries the first intent instance identifier; The AAI deletes the intent instance bound to the first intent instance identifier and its scenario use case service identifier information and scenario use case service information based on the first intent instance identifier carried in the first stop intent service request it receives.

11. The method according to claim 10, characterized in that, Also includes: The UUI sends a first shutdown intent instance request for the first object to the AAI, and the first shutdown intent instance request carries the first intent instance identifier; The AAI deletes the intent instance bound to the first intent instance identifier and its scenario use case service identifier information and scenario use case service information based on the first intent instance identifier carried in the first stop intent service request it receives.

12. The method according to claim 1, characterized in that, Also includes: The UUI obtains the third network intent of the second object, and the third network intent is voice information including the third service requirement proposed by the second object; The UUI translates the third network intent to obtain third network intent translation information, which is text information including the third service requirement; The UUI obtains the second intent instance identifier of the second object; The UUI generates a third intent instance, which includes the third network intent translation information and the second intent instance identifier. Based on the third intent instance, determine the third scenario use case service identifier information and the third scenario use case service information that match the third business requirement; The third intent instance, the third scenario use case service identifier information, and the third scenario use case service information are associated and stored in the Active Available Resource Library (AAI).

13. A network intent processing apparatus, characterized in that, include: User-defined interface (UUI) is used to obtain the first network intent of the first object, wherein the first network intent is voice information including the first business requirement proposed by the first object. The UUI is also used to translate the first network intent to obtain first network intent translation information, wherein the first network intent translation information is text information including the first service requirement; The UUI is also used to obtain the first intent instance identifier of the first object; The UUI is also used to generate a first intent instance, the first intent instance including the first network intent translation information and the first intent instance identifier; The processing unit is configured to determine, based on the first intent instance, first scenario use case service identifier information and first scenario use case service information that match the first business requirement; The processing unit is also used to associate and store the first intent instance, the first scenario use case service identifier information, and the first scenario use case service information to the Active Available Resource Library (AAI).

14. An electronic device, characterized in that, include: At least one processor; A storage device configured to store at least one program, which, when executed by the at least one processor, causes the at least one processor to implement the method as described in any one of claims 1 to 12.

15. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 12.

16. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1-12.

Images