Intention updating method and device, equipment and medium
By receiving intent update requests and verifying account identity and permissions, and obtaining and executing network policies, the problem of malicious users and resources was solved during intent update process, improving network security and update efficiency.
Patent Information
- Application Number
- CN202411441580.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-15
- Publication Date
- 2025-01-10
- Estimated Expiration
- 2044-10-15
AI Technical Summary
There is a risk of illegally initiated by malicious users or systems during the intent update process, resulting in network security threats, and intent updates initiated by legitimate users may result in waste of resources due to infeasibility, and intent updates cannot be accurately and effectively.
By receiving an intent update request, obtaining the identity and permissions of the initiating account, determining whether it is legal and has update permissions, and obtaining and executing pre-save network policies if allowed to ensure the legality and security of intent updates.
It effectively avoids the intent update requests initiated by accounts that do not have legal identity or update permissions, avoids the intent itself infeasibility, ensures the accuracy and network security of intent update requests, and improves the network security and resource utilization efficiency.
Smart Images

Figure CN119299190A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network technology and security, and in particular to an intent update method, device, equipment and medium. Background Art
[0002] Currently, with the continuous evolution of business scenarios in intent-based networks, dynamic adjustment of network configuration has become a key link to ensure business continuity. This adjustment requires that intent must be able to keep up with the pace of business and achieve instant and accurate updates. However, in actual operations, the intent update process faces multiple security challenges.
[0003] On the one hand, intent updates may be illegally initiated by malicious users or systems. These unauthorized updates may attempt to disrupt the normal operation of the network or introduce harmful configurations, thus posing a serious threat to the security of the network. On the other hand, even if the update is initiated by a legitimate user, the intent update may not be performed accurately and effectively due to the infeasibility of the intent itself, resulting in a waste of resources. Summary of the invention
[0004] The embodiments of the present application provide an intent update method, apparatus, device and medium for solving the problem that the intent update process in the related technology cannot be accurately and effectively performed, thereby causing network security problems.
[0005] In a first aspect, an embodiment of the present application provides a method for updating intent, the method comprising:
[0006] Receive intent update request;
[0007] Obtain the account that initiated the update intention request, and determine whether the account has a legitimate identity and whether it has update authority; if so, determine whether to allow the update intention request to be executed based on whether the pre-saved allowed operation objects and contents include the operation objects and operation contents included in the update intention request;
[0008] If the intended update request is allowed to be executed, the network policy saved corresponding to the operation object and the operation content is obtained, and the network policy is executed.
[0009] In a second aspect, an embodiment of the present application further provides an intent update device, the device comprising:
[0010] A receiving module, used for receiving an intent update request;
[0011] An acquisition and determination module is used to obtain the account that initiates the intended update request, determine whether the account has a legal identity and whether it has update authority; if so, determine whether to allow the intended update request to be executed based on whether the objects and contents of the pre-saved allowed operations contain the operation objects and operation contents contained in the intended update request;
[0012] The processing module is used to obtain the network policy saved corresponding to the operation object and the operation content, and execute the network policy if the execution of the intention update request is allowed.
[0013] In a third aspect, an embodiment of the present application further provides an electronic device, including:
[0014] A memory for storing program instructions;
[0015] The processor is used to call the program instructions stored in the memory and execute the steps included in any one of the above-mentioned intention update methods according to the obtained program instructions.
[0016] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the method for intended updating as described in any one of the above items.
[0017] In an embodiment of the present application, an electronic device receives an intent update request; obtains the account that initiated the intent update request, and if the account has a legal identity and has update authority, then based on the operation object, operation content, and pre-saved objects and content of allowed operations contained in the intent update request, detects whether the intent update request is allowed to be executed; if the intent update request is allowed to be executed, then based on the operation object and operation content, determines the corresponding network policy and executes the network policy. Since the electronic device determines whether the account that initiated the intent update request has a legal identity and has update authority, it can avoid accounts that do not have a legal identity or do not have update authority from initiating intent update requests, and the electronic device determines whether to allow the execution of the intent update request, which can avoid problems such as the infeasibility of the intent itself, so that the policy corresponding to the intent update request can be accurately and effectively executed, thereby improving the security of the network. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] In order to more clearly illustrate the technical solution of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0019] Figure 1 A process diagram of the intent update method provided in an embodiment of the present application;
[0020] Figure 2 A detailed process diagram of an intention update provided in an embodiment of the present application;
[0021] Figure 3 A schematic diagram of an intention update structure provided in an embodiment of the present application;
[0022] Figure 4 A structural diagram of an intention update device provided in an embodiment of the present application;
[0023] Figure 5 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0024] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.
[0025] Obviously, the drawings described below are only some examples or embodiments of the present application. For ordinary technicians in this field, the present application can also be applied to other similar scenarios based on these drawings without creative work. In addition, it can also be understood that although the efforts made in this development process may be complicated and lengthy, for ordinary technicians in this field related to the content disclosed in this application, some changes in design, manufacturing or production based on the technical content disclosed in this application are just conventional technical means, and should not be understood as insufficient content disclosed in this application.
[0026] Reference to "embodiments" in this application means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those of ordinary skill in the art that the embodiments described in this application may be combined with other embodiments without conflict.
[0027] The words "connected", "connected", "coupled" and the like involved in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The "plurality" involved in this application refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship. The terms "first", "second", "third" and the like involved in this application are merely used to distinguish similar objects, and do not represent a specific ordering of objects.
[0028] In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the fact that they can be implemented by ordinary technicians in this field. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.
[0029] In order to accurately and effectively perform intent updates, thereby improving network security, the embodiments of the present application provide an intent update method, apparatus, device, and medium.
[0030] The intention update method includes: an electronic device receiving an intention update request; obtaining an account that initiates the intention update request, and determining whether the account has a legal identity and whether it has update authority; if so, determining whether to allow the intention update request to be executed based on whether pre-saved objects and contents of allowed operations include the operation objects and operation contents included in the intention update request; if the intention update request is allowed to be executed, obtaining a network policy saved corresponding to the operation object and operation content, and executing the network policy.
[0031] Embodiment 1:
[0032] Figure 1 A schematic diagram of a process of an intent update method provided in an embodiment of the present application, the process comprising the following steps:
[0033] S101: receiving an intent update request.
[0034] The intention update method provided in the embodiment of the present application is applied to an electronic device, which may be a smart device such as a PC or a server.
[0035] In order to accurately and effectively update the intent, the electronic device may first receive an intent update request. It should be noted that after receiving the intent request, receiving a request carrying the intent is an intent update request.
[0036] In one possible implementation, when a business person needs to update an existing intent, the business person will use an authorized and configured device, which usually has a specific application or system interface for intent management and update operations. In such a preset page, the business person can clearly see all the intents defined in the current system, as well as the detailed information and status of each intent. In order to initiate an intent update request, the business person will find and click a preset button on the preset page, such as a button clearly marked as "Update". The design of this "Update" button is usually intuitive and easy to identify to ensure that the business person can accurately trigger the update process. Once the business person clicks this button, the electronic device will immediately recognize and receive the intent update request.
[0037] S102: Obtain the account that initiates the intention update request, and determine whether the account has a legal identity and whether it has update authority; if so, determine whether to allow the intention update request to be executed based on whether the pre-saved allowed operation objects and content include the operation objects and operation content included in the intention update request.
[0038] After receiving an intent update request, in order to improve network security, the electronic device can obtain the account that initiated the intent update request. In one possible implementation, the business personnel has logged in to a corresponding account in a specific application or system interface. Therefore, the intent update request received by the electronic device carries the account, and the electronic device can determine the account as the account that initiated the intent update request.
[0039] In order to improve network security, the electronic device locally pre-stores each legal account and each account with update permission. The electronic device can determine whether the account is legal based on whether each pre-stored legal account contains the acquired account, and determine whether the account has update permission based on whether each pre-stored account with update permission contains the acquired account. If the account has a legal identity and has update permission, the account is allowed to perform intention update. If the account does not have a legal identity or does not have update permission, the account is not allowed to perform intention update, and the execution of the intention update request is stopped.
[0040] If it is determined that the account has a legitimate identity and the account has update permission, the electronic device can determine whether the intent corresponding to the intent update request is a feasible intent. If it is determined that the intent corresponding to the intent update request is not a feasible intent, the execution of the intent update request is stopped. Specifically, the electronic device pre-stores the operation objects and content associated with each feasible intent, which constitute the scope of operations allowed to be executed. When receiving an intent update request, the electronic device checks whether the operation objects and content specified in the request have been pre-stored as objects and content allowed to be operated.
[0041] In terms of specific implementation, there are two possible verification methods:
[0042] Direct matching method: If the pre-stored list of allowed operation objects and contents directly includes the operation object and content in the request, it is determined that the intended update request is allowed to be executed.
[0043] Intent group matching method: In addition, if there are one or more intent groups, and any of these intent groups contains the operation object and content in the request, it can also be determined that the intent update request is allowed to execute. The intent group here refers to a set of operation objects and contents that have some association or similarity.
[0044] The verification method to be selected may be pre-configured, and the specific verification method to be selected is not limited herein. Through these two verification methods, the electronic device can accurately determine whether an intended update request is allowed to be executed, thereby ensuring the legitimacy and security of the operation.
[0045] It should be noted that by judging whether to allow the execution of the intention update request based on whether the pre-saved objects and contents of allowed operations include the operation objects and operation contents included in the intention update request, it is possible to determine whether the update intention is a safe intention, that is, whether the intent does not contain malicious operations, malicious privilege escalation, etc. after translation, and whether the indicators after the intent translation are within the established rules of the network.
[0046] S103: If the execution of the intended update request is allowed, obtaining the network policy saved corresponding to the operation object and the operation content, and executing the network policy.
[0047] In order to accurately and effectively perform the intention update, the electronic device pre-stores the correspondence between the object and content of the operation and the policy. If it is determined that the intention update request is allowed to be executed, the electronic device can obtain the network policy corresponding to the operation object and operation content contained in the intention update request. After determining the network policy, the electronic device can execute the network policy.
[0048] It should be noted that, in a possible implementation, the update intention request may also include an operation duration. If the operation duration is included, when the electronic device executes the network policy, the execution duration is the operation duration.
[0049] In a possible implementation, after determining the network policy, the electronic device may control the corresponding device to execute the network policy.
[0050] If the intent update request carries an operation purpose, the electronic device can obtain the network policy corresponding to the operation object, operation content and operation purpose. The operation target refers to the specific purpose that is expected to be achieved or achieved in the intent update request. For example, if the service assurance level is increased to level 3, "level 3" is the operation purpose.
[0051] The method provided in the embodiment of the present application is applicable to the update of user intention or device intention in scenarios such as the Internet of Things and the Internet of Vehicles, and is applicable to the automated and intelligent security management of future networks.
[0052] Among them, the intent layer of the electronic device may receive the user's intent, update and verify the intent, and translate the verified intent to form an executable network policy. Specifically, the intent update module may be responsible for receiving update intent requests to adapt the network to the ever-changing business environment. The intent source verification module is responsible for conducting a preliminary review of the intent update operation, including identity legitimacy verification, intent legitimacy verification, and discarding interference from unknown sources or malicious intent. The intent feasibility verification module is responsible for feasibility checks on the update intent, including the enforceability of the policy after the intent translation, potential conflict risks, etc.
[0053] Suppose there is a smart home system in which the electronic devices pre-save the correspondence between different operation objects (such as the brightness and color of the light bulb) and operation contents (such as adjusting to a certain brightness level, changing to a certain color) and the corresponding network policies. For example, a business person wants to update the brightness intention of a smart light bulb so that when the user says "brighten the light bulb", the light bulb can automatically adjust to a brighter level. In this case, the business person will click the "Update" button on his device to initiate an intention update request. After receiving this intention update request, the electronic device will check the legitimacy of the request and confirm whether it is allowed to execute. Once it is confirmed to be allowed, the electronic device will search for the corresponding network policy based on the operation object and operation content specified in the request. Suppose the network policy found is: when receiving the "brighten" instruction, increase the brightness level of the light bulb by 20%. The electronic device will execute this network policy and automatically adjust the brightness of the light bulb to a higher level. In this way, through the cooperation of the intention update request and the network policy, the smart home system can flexibly adjust the device status according to the user's instructions and provide more personalized services.
[0054] The embodiment of the present application is equivalent to providing a method for intent security update in an intent network, wherein the intent network is an advanced network architecture and management method that allows network administrators to define network behavior by expressing high-level business intent without directly operating the underlying network configuration details. In an intent network, users only need to express the state or effect achieved by the network, without using detailed operations of network commands, to achieve the goal of network configuration. An intent network is an intelligent network topology structure, and the network automatically translates and configures according to the user's ideas to meet user needs.
[0055] In an embodiment of the present application, an electronic device receives an intent update request; obtains the account that initiated the intent update request, and if the account has a legal identity and has update authority, then based on the operation object, operation content, and pre-saved objects and content of allowed operations contained in the intent update request, detects whether the intent update request is allowed to be executed; if the intent update request is allowed to be executed, then based on the operation object and operation content, determines the corresponding network policy and executes the network policy. Since the electronic device determines whether the account that initiated the intent update request has a legal identity and has update authority, it can avoid accounts that do not have a legal identity or do not have update authority from initiating intent update requests, and the electronic device determines whether to allow the execution of the intent update request, which can avoid problems such as the infeasibility of the intent itself, so that the policy corresponding to the intent update request can be accurately and effectively executed, thereby improving the security of the network.
[0056] Embodiment 2:
[0057] In order to accurately obtain the account that initiates the update intention request, based on the above embodiment, in the embodiment of the present application, obtaining the account that initiates the update intention request includes:
[0058] If the update intention request carries voice information, voiceprint recognition is performed on the voice information, and according to the pre-stored correspondence between voiceprint and account, the account corresponding to the identified target voiceprint is determined as the account that initiated the update intention request; or,
[0059] If the update intent request carries account information, the account that initiates the update intent request is determined according to the account information carried in the update intent request.
[0060] In actual scenarios, business personnel can initiate an intent update request through voice information. Specifically, the business personnel can send a voice message to the collection device, and the collection device will send the intent update request carrying the voice information to the electronic device. At this time, the intent update request received by the electronic device carries the voice information. After receiving the intent update request carrying the voice information, the electronic device can obtain the voice information carried in the intent update request. After obtaining the voice information, it performs voiceprint recognition on the voice information. The electronic device pre-stores the correspondence between the voiceprint and the account locally. The electronic device can determine the account corresponding to the identified target voiceprint as the account that initiated the intent update request.
[0061] In another possible implementation, the business personnel can initiate an intent update request based on the authorized and configured device they use. The device used by the business personnel themselves usually has a specific application or system interface for intent management and update operations. In such a preset page, the business personnel can clearly see all the intents defined in the current system, as well as the detailed information and status of each intent. In order to initiate an intent update request, the business personnel will find and click a preset button on the preset page, such as a button clearly marked as "Update". Once the business personnel clicks this button, the electronic device will immediately recognize and receive the intent update request. It should be noted that since the application or system interface has logged in to the user's account, when the business personnel sends an intent update request through their device, the intent request will automatically be accompanied by account information. Therefore, if the intent update request carries account information, the electronic device can determine the account that initiates the intent update request based on the account information carried in the intent update request. Specifically, the electronic device can determine the account information carried in the intent update request as the account that initiates the intent update request.
[0062] Embodiment 3:
[0063] In order to accurately and effectively perform the intent update, based on the above embodiments, in the embodiment of the present application, before determining whether to allow the execution of the intent update request based on whether the pre-saved allowed operation object and content include the operation object and operation content included in the intent update request, the method also includes:
[0064] If the intention update request carries voice information, semantic recognition is performed on the voice information, and the operation object and operation content are determined based on the result of the semantic recognition. Subsequent steps are performed to determine whether the execution of the intention update request is allowed based on whether the pre-saved objects and contents allowed to operate include the operation objects and operation contents included in the intention update request.
[0065] In an embodiment of the present application, if the intended update request carries voice information, the electronic device can perform semantic recognition on the voice information. Specifically, how to perform semantic recognition on the voice information is a prior art and will not be described in detail here.
[0066] After obtaining the result of semantic recognition, the electronic device can determine the operation object and operation content contained in the intended update request based on the result of semantic recognition. In one possible implementation, the electronic device pre-stores each object, and if the result of semantic recognition includes any pre-stored object, the object is determined as the operation object, and each content is also pre-stored in the electronic device, and if the result of semantic recognition includes any pre-stored content, the content can be determined as the operation content.
[0067] After determining the operation object and the operation content, the electronic device may perform a subsequent step based on the operation object and the operation content to determine whether to allow the execution of the intended update request.
[0068] In order to accurately and effectively perform the intent update, based on the above embodiments, in the embodiment of the present application, before obtaining the account that initiates the intent update request, the method further includes:
[0069] Identify the operation object and operation content included in the intended update request. If the operation object and operation content included in the intended update request are correct, execute the subsequent step of obtaining the account that initiated the intended update request.
[0070] Since in actual scenarios, the intent update request may not conform to the format and the intent update request cannot be executed at this time, the electronic device can perform a format review on the intent update request before obtaining the account that initiated the intent update request. Specifically, the electronic device can identify the operation object and operation content contained in the intent update request. If the intent update request carries voice information, the electronic device can perform semantic recognition on the voice information. After obtaining the result of the semantic recognition, the electronic device can perform semantic recognition based on the result of the semantic recognition. If the intent update request does not carry voice information, but carries an operation object and operation content, the electronic device obtains the operation object and operation content carried in the intent update request.
[0071] If the intent update request contains the operation object and operation content, it can be determined that the format review has passed, and the subsequent steps of obtaining the account that initiated the intent update request can be performed based on the intent update request.
[0072] It should be noted that if the business personnel initiates an intent update request based on the fact that they are using an authorized and configured device, the device used by the business personnel themselves usually has a specific application or system interface for intent management and update operations. In such a preset page, the business personnel can select the operation object and operation content. At this time, the intent update request received by the electronic device carries the operation object and operation content.
[0073] In one possible implementation, a preset operation object or a preset operation content may require an operation duration. Therefore, if the operation object is a preset operation object, or the operation content is a preset operation content, the electronic device can determine that the format review has passed when the operation object, operation content and operation duration are included in the intention update request, and perform subsequent steps to obtain the account that initiated the intention update request.
[0074] Embodiment 4:
[0075] In order to improve network security, based on the above embodiments, in the embodiment of the present application, the determination of whether to allow the execution of the intention update request according to whether the pre-saved allowed operation object and content include the operation object and operation content included in the intention update request includes:
[0076] Obtain the objects and contents of allowed operations that are pre-saved for the account; and determine whether to allow the account to execute the intention update request based on whether the objects and contents of allowed operations that are pre-saved for the account include the operation objects and operation contents included in the intention update request.
[0077] Since different accounts have different objects and contents that are allowed to be operated on in actual scenarios, in order to improve network security and prevent accounts without permission from arbitrarily updating intent, the electronic device pre-stores the objects and contents that are allowed to be operated on for each account. The electronic device can obtain the objects and contents that are allowed to be operated on the account, and determine whether to allow the account to execute the intent update request based on whether the objects and contents that are allowed to be operated on the account contain the operation objects and operation contents contained in the intent update request. Specifically, if the objects that are allowed to be operated on the account contain the operation objects contained in the intent update request, and the contents that are allowed to be operated on the account contain the operation contents contained in the intent update request, it can be determined that the account has the permission to execute the intent update request, and the account is allowed to execute the intent update request.
[0078] In one possible implementation, the electronic device may first determine whether the intention update request is a feasible intention based on whether the saved objects and contents allowed for operation include the operation object and operation content; if the operation object and operation content are included, then determine whether the account has the authority to execute the intention update request based on whether the saved objects and contents allowed for operation for the account include the operation object and operation content.
[0079] Embodiment 5:
[0080] In order to accurately and effectively update the intent, based on the above embodiments, in the embodiment of the present application, after obtaining the network policy corresponding to the operation object and the operation content, and before executing the network policy, the method further includes:
[0081] For each currently pending request, determining whether the intended update request is related to the pending request based on whether the candidate object and candidate content contained in the pending request are identical to at least one of the operation object and the operation content;
[0082] If it is determined that the intended update request is not related to any of the currently pending requests, then the subsequent step is to execute the network policy.
[0083] In actual application scenarios, since the intent update request may be associated with the currently queued request to be executed, this correlation may cause the same intent to be executed repeatedly, resulting in unnecessary waste of resources. Therefore, after obtaining the corresponding network policy, the electronic device will make a key judgment: whether the intent update request is associated with any pending intent update request. Such a judgment mechanism is intended to avoid repeated allocation and execution of resources.
[0084] Specifically, the electronic device can determine, for each current request to be executed, whether the received intention update request is related to the request to be executed based on whether the candidate object and candidate content contained in the request to be executed are identical to at least one of the operation object and the operation content. If the candidate object is identical to the operation object, or the candidate content is identical to the operation content, it can be determined whether the received intention update request is related to the request to be executed.
[0085] This process is equivalent to determining whether the network policy corresponding to the intent update request is relevant to the policy corresponding to the existing intent.
[0086] If it is determined that the intent update request is not related to any of the currently pending requests, the electronic device does not need to perform operations such as intent merging, and can execute subsequent steps to execute the network policy corresponding to the intent update request.
[0087] In an embodiment of the present application, the intent correlation check module may be responsible for performing correlation checks between intents, so that multiple intents with similar strategies can be merged for processing to improve efficiency.
[0088] It should be noted that the purpose of this judgment is to improve execution efficiency, so the update intention will continue to be executed regardless of whether it is relevant or not.
[0089] Embodiment 6:
[0090] In order to accurately and effectively update the intent, based on the above embodiments, in the embodiment of the present application, the method further includes:
[0091] If it is determined that the intention update request is related to any current request to be executed, and the candidate target corresponding to the request to be executed is different from the operation target carried in the intention update request, then determine whether the policy corresponding to the request to be executed is currently being executed. If so, stop the execution and execute the network policy. If not, and the policy has not been executed, delete the policy corresponding to the request to be executed and execute the network policy.
[0092] In actual applications, if the intent update request is related to any current request to be executed, and if the candidate target corresponding to the request to be executed is inconsistent with the operation target clearly stated in the intent update request, this may indicate that there is an error in the intent information sent previously, so it is necessary to make necessary corrections to the intent corresponding to the request to be executed. Here, the operation target refers to the specific purpose that is expected to be achieved or achieved in the intent update request. In order to accurately and effectively execute the intent and improve efficiency, the electronic device will adopt a merging strategy. Considering that users usually express their latest needs through subsequent requests, the electronic device will choose to execute only the latest received intent update request. Specifically, the electronic device can check whether the policy corresponding to the request to be executed is currently being executed. If it is being executed, the electronic device will release the relevant resources, stop the execution of the policy, and execute the newly acquired network policy instead. If the policy corresponding to the request to be executed is not currently executed and the policy has not been executed, the electronic device will delete the policy corresponding to the request to be executed to avoid performing redundant operations and directly execute the newly acquired network policy.
[0093] The electronic device control layer can be used to control network policies and network status, update network policies for update intentions, and perceive network status in real time. The electronic device network layer is used to implement network policies and analyze network status. The implementation of network policies is to determine whether the policy is currently being executed.
[0094] That is to say, if the strategy translated from the new intent is not relevant to the currently executed strategy, the network status is perceived and analyzed, the implementation of the network strategy is monitored, and it is determined whether the network resources are occupied by the network strategy of the existing intent and whether the conditions for executing the updated intent are met. If the resources are occupied, the updated intent should be given high priority, and the resources should be released to provide network conditions for the execution of the new intent. If the resources are not occupied, the updated strategy is implemented.
[0095] For example, if the policy after the new intent is translated is relevant to the existing policy, and the policy after the new intent is not translated is different from the existing policy, the relevant policies will be merged for execution. If one of the purposes of updating the intent is to improve the service assurance level to level 3, where the level definition is set by other configurations in the network system, and the policy executed by the existing intent is also to improve the service assurance level to level 4, then the policies of the two intents can be merged and processed, and the latest intent policy level 3 will prevail. Levels 3 and 4 refer to specific operational goals.
[0096] The processing flow provided by the embodiment of the present application ensures that the electronic device can efficiently and accurately respond to the user's intended update while avoiding unnecessary waste of resources.
[0097] Four modules are added in the embodiment of the present application: intention update module, intention source verification module, intention feasibility verification module, and intention relevance check module. Through the information interaction between different modules, the standardization of the intention update process is ensured. Five judgment conditions are added: judgment on the identity of the intention initiator, judgment on the legality of the intention, judgment on the feasibility of the intention, judgment on the relevance of the intention, and judgment on the network resources. According to the judgment results of different conditions, corresponding implementation strategies are adopted respectively.
[0098] Electronic devices verify the legitimacy of the updated intention, verify the security of the intention, review the feasibility of the intention, check the correlation of multiple intentions, and determine the resources required for policy implementation to ensure the legality and rationality of the intention implementation. By taking targeted and differentiated measures for multiple judgment results, the applicable scenarios of the intention update process are expanded to ensure the scientific nature of the policy implementation conditions.
[0099] Embodiment 7:
[0100] Figure 2 A detailed process diagram of an intention update provided in an embodiment of the present application, the process has the following steps:
[0101] S201: Receive an intent update request, perform semantic conversion on the new intent, and conduct a preliminary review of the format, etc.
[0102] When the intent update request carries voice information, semantic conversion is performed.
[0103] Specifically, how to perform format review has been described in the above embodiments and will not be repeated here.
[0104] S202: Obtain the account that initiates the update intent request.
[0105] S203: Determine whether the account has a legal identity and whether it has update authority. If so, execute S204; if not, execute S205.
[0106] S204: Determine whether to allow the execution of the intention update request based on whether the pre-saved allowed operation objects and contents include the operation objects and operation contents included in the intention update request. If so, execute S206; if not, execute S205.
[0107] S205: End.
[0108] S206: Determine the network policy corresponding to the intended update request.
[0109] S207: Determine whether the intended update request is related to the request to be executed, if so, execute S208, if not, execute S209.
[0110] This process is equivalent to determining whether the updated intent is relevant to the existing intent.
[0111] S208: If it is determined that the intent update request is related to any current request to be executed, and the candidate target corresponding to the request to be executed is different from the operation target carried in the intent update request, then determine whether the policy corresponding to the request to be executed is currently being executed. If so, stop the execution and execute the network policy. If not, and the policy has not been executed, delete the policy corresponding to the request to be executed and execute the network policy.
[0112] S209: Execute the network policy.
[0113] In the embodiments of the present application, in order to solve the security problems such as identity spoofing of the initiator, conflict of update policies, insufficient network resources, etc. in the process of intent update, in order to meet the needs of user intent or device intent to update the intent under changing business scenarios, a method based on security judgment such as legitimacy verification, feasibility verification, policy conflict determination, network resource assurance, etc. is proposed to optimize the intent update process. The present application promotes the rationalization of the intent update process by adding intent update modules, security verification modules, network policy update modules, etc. to the intent layer, control layer, and network layer, respectively, to perform identity authentication, feasibility verification, conflict determination, resource determination, etc. on the intent update process. Using the method proposed in the embodiments of the present application, the security review and security management of intent updates by the intent network can be effectively improved, which helps to achieve the reliability and availability of the intent network and provide a new method for the secure development of future intelligent networks.
[0114] Figure 3 A schematic diagram of an intentional update structure provided in an embodiment of the present application.
[0115] Depend on Figure 3 It can be seen that the intent layer is used to receive intent update requests, verify the source of the intent update requests, and specifically verify whether the account that initiates the intent update request has a legal identity and whether it has update permissions; and verify the feasibility of the intent, that is, based on whether the pre-saved allowed operation objects and content include the operation objects and operation content included in the intent update request, determine whether to allow the intent update request to be executed, and perform a relevance check on the intent.
[0116] The control layer determines the network strategy, obtains the intent relevance check results determined by the intent layer through the intent interface, and performs network status perception.
[0117] The network layer is used for the implementation of network strategies and the analysis of network status, and the network layer and the control layer interact through the network interface.
[0118] Embodiment 8:
[0119] Based on the same inventive concept, the present application embodiment provides an intention update device, please refer to Figure 4 , the device comprises:
[0120] Receiving module 401, used for receiving an intention update request;
[0121] The acquisition and determination module 402 is used to obtain the account that initiated the intended update request, determine whether the account has a legal identity and whether it has update authority; if so, determine whether to allow the intended update request to be executed based on whether the pre-saved objects and contents of allowed operations include the operation objects and operation contents included in the intended update request;
[0122] The processing module 403 is used to obtain the network policy saved corresponding to the operation object and the operation content, and execute the network policy if the execution of the intended update request is allowed.
[0123] In one possible implementation, the acquisition and determination module 402 is specifically used to perform voiceprint recognition on the voice information if the intention update request carries voice information, and determine the account corresponding to the identified target voiceprint as the account that initiated the intention update request based on the pre-saved correspondence between the voiceprint and the account; or, if the intention update request carries account information, determine the account that initiated the intention update request based on the account information carried in the intention update request.
[0124] In one possible implementation, the acquisition and determination module 402 is also used to perform semantic recognition on the voice information if the intention update request carries voice information, determine the operation object and operation content according to the result of the semantic recognition, and perform subsequent steps to determine whether to allow the execution of the intention update request based on whether the pre-saved objects and contents allowed to operate include the operation objects and operation contents included in the intention update request.
[0125] In a possible implementation, the acquisition determination module 402 is also used to identify the operation object and operation content contained in the intention update request. If the operation object and operation content are contained in the intention update request, the subsequent step of obtaining the account that initiated the intention update request is executed.
[0126] In one possible implementation, the acquisition determination module 402 is specifically used to obtain the objects and contents of allowed operations that are pre-saved for the account; and determine whether to allow the account to execute the intention update request based on whether the objects and contents of allowed operations saved for the account include the operation objects and operation contents included in the intention update request.
[0127] In a possible implementation, the processing module 403 is also used to determine, for each current request to be executed, whether the intention update request is related to the request to be executed based on whether the candidate object and candidate content contained in the request to be executed are identical to at least one of the operation object and the operation content; if it is determined that the intention update request is not related to each current request to be executed, then execute the subsequent step of executing the network policy.
[0128] In one possible implementation, the processing module 403 is also used to determine whether the policy corresponding to the request to be executed is currently being executed if it is determined that the intention update request is related to any current request to be executed, and the candidate target corresponding to the request to be executed is different from the operation target carried in the intention update request. If so, stop the execution and execute the network policy; if not, and the policy has not been executed, delete the policy corresponding to the request to be executed and execute the network policy.
[0129] Embodiment 9:
[0130] Based on the same inventive concept, the present application embodiment provides an electronic device, which can implement the function of the above intention update, please refer to Figure 5 The device includes a processor 501, a memory 503 and a communication bus 504, wherein the processor 501, the communication interface 502, and the memory 503 communicate with each other through the communication bus 504.
[0131] The memory 503 stores a computer program. When the program is executed by the processor 501, the processor 501 performs the following steps:
[0132] Receive intent update request;
[0133] Obtain the account that initiated the update intention request, and determine whether the account has a legitimate identity and whether it has update authority; if so, determine whether to allow the update intention request to be executed based on whether the pre-saved allowed operation objects and contents include the operation objects and operation contents included in the update intention request;
[0134] If the intended update request is allowed to be executed, the network policy saved corresponding to the operation object and the operation content is obtained, and the network policy is executed.
[0135] In a possible implementation manner, obtaining the account that initiates the intended update request includes:
[0136] If the update intention request carries voice information, voiceprint recognition is performed on the voice information, and according to the pre-stored correspondence between voiceprint and account, the account corresponding to the identified target voiceprint is determined as the account that initiated the update intention request; or,
[0137] If the update intent request carries account information, the account that initiates the update intent request is determined according to the account information carried in the update intent request.
[0138] In a possible implementation, before determining whether to allow execution of the intended update request based on whether the pre-saved allowed operation object and content include the operation object and operation content included in the intended update request, the method further includes:
[0139] If the intention update request carries voice information, semantic recognition is performed on the voice information, and the operation object and operation content are determined based on the result of the semantic recognition. Subsequent steps are performed to determine whether the execution of the intention update request is allowed based on whether the pre-saved objects and contents allowed to operate include the operation objects and operation contents included in the intention update request.
[0140] In a possible implementation manner, before obtaining the account that initiates the intended update request, the method further includes:
[0141] Identify the operation object and operation content included in the intended update request. If the operation object and operation content included in the intended update request are correct, execute the subsequent step of obtaining the account that initiated the intended update request.
[0142] In a possible implementation, determining whether to allow execution of the intention update request according to whether the pre-saved allowed operation object and content include the operation object and operation content included in the intention update request includes:
[0143] Obtain the objects and contents of allowed operations that are pre-saved for the account; and determine whether to allow the account to execute the intention update request based on whether the objects and contents of allowed operations that are pre-saved for the account include the operation objects and operation contents included in the intention update request.
[0144] In a possible implementation manner, after acquiring the network policy stored corresponding to the operation object and the operation content and before executing the network policy, the method further includes:
[0145] For each currently pending request, determining whether the intended update request is related to the pending request based on whether the candidate object and candidate content contained in the pending request are identical to at least one of the operation object and the operation content;
[0146] If it is determined that the intended update request is not related to any of the currently pending requests, then the subsequent step is to execute the network policy.
[0147] In a possible implementation, the method further includes:
[0148] If it is determined that the intention update request is related to any current request to be executed, and the candidate target corresponding to the request to be executed is different from the operation target carried in the intention update request, then determine whether the policy corresponding to the request to be executed is currently being executed. If so, stop the execution and execute the network policy. If not, and the policy has not been executed, delete the policy corresponding to the request to be executed and execute the network policy.
[0149] The communication bus mentioned in the above server can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.
[0150] The communication interface 502 is used for communication between the electronic device and other devices.
[0151] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.
[0152] The above-mentioned processor can be a general-purpose processor, including a central processing unit, a network processor (Network Processor, NP), etc.; it can also be a digital signal processing processor (Digital Signal Processing, DSP), an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc.
[0153] Embodiment 10:
[0154] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program executable by an electronic device. When the program runs on the electronic device, the electronic device implements the following steps when executing:
[0155] Receive intent update request;
[0156] Obtain the account that initiated the update intention request, and determine whether the account has a legitimate identity and whether it has update authority; if so, determine whether to allow the update intention request to be executed based on whether the pre-saved allowed operation objects and contents include the operation objects and operation contents included in the update intention request;
[0157] If the intended update request is allowed to be executed, the network policy saved corresponding to the operation object and the operation content is obtained, and the network policy is executed.
[0158] In a possible implementation manner, obtaining the account that initiates the intended update request includes:
[0159] If the update intention request carries voice information, voiceprint recognition is performed on the voice information, and according to the pre-stored correspondence between voiceprint and account, the account corresponding to the identified target voiceprint is determined as the account that initiated the update intention request; or,
[0160] If the update intent request carries account information, the account that initiates the update intent request is determined according to the account information carried in the update intent request.
[0161] In a possible implementation, before determining whether to allow execution of the intended update request based on whether the pre-saved allowed operation object and content include the operation object and operation content included in the intended update request, the method further includes:
[0162] If the intention update request carries voice information, semantic recognition is performed on the voice information, and the operation object and operation content are determined based on the result of the semantic recognition. Subsequent steps are performed to determine whether the execution of the intention update request is allowed based on whether the pre-saved objects and contents allowed to operate include the operation objects and operation contents included in the intention update request.
[0163] In a possible implementation manner, before obtaining the account that initiates the intended update request, the method further includes:
[0164] Identify the operation object and operation content included in the intended update request. If the operation object and operation content included in the intended update request are correct, execute the subsequent step of obtaining the account that initiated the intended update request.
[0165] In a possible implementation, determining whether to allow execution of the intention update request according to whether the pre-saved allowed operation object and content include the operation object and operation content included in the intention update request includes:
[0166] Obtain the objects and contents of allowed operations that are pre-saved for the account; and determine whether to allow the account to execute the intention update request based on whether the objects and contents of allowed operations that are pre-saved for the account include the operation objects and operation contents included in the intention update request.
[0167] In a possible implementation manner, after acquiring the network policy stored corresponding to the operation object and the operation content and before executing the network policy, the method further includes:
[0168] For each currently pending request, determining whether the intended update request is related to the pending request based on whether the candidate object and candidate content contained in the pending request are identical to at least one of the operation object and the operation content;
[0169] If it is determined that the intended update request is not related to any of the currently pending requests, then the subsequent step is to execute the network policy.
[0170] In a possible implementation, the method further includes:
[0171] If it is determined that the intention update request is related to any current request to be executed, and the candidate target corresponding to the request to be executed is different from the operation target carried in the intention update request, then determine whether the policy corresponding to the request to be executed is currently being executed. If so, stop the execution and execute the network policy. If not, and the policy has not been executed, delete the policy corresponding to the request to be executed and execute the network policy.
[0172] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0173] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0174] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0175] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0176] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.
Claims
1. An intention update method, characterized in that: The method comprises: Receive intent update request; Obtain the account that initiated the update intention request, and determine whether the account has a legitimate identity and whether it has update authority; if so, determine whether to allow the update intention request to be executed based on whether the pre-saved allowed operation objects and contents include the operation objects and operation contents included in the update intention request; If the intended update request is allowed to be executed, the network policy saved corresponding to the operation object and the operation content is obtained, and the network policy is executed.
2. The method according to claim 1, characterized in that The obtaining of the account that initiates the intended update request includes: If the update intention request carries voice information, voiceprint recognition is performed on the voice information, and according to the pre-stored correspondence between voiceprint and account, the account corresponding to the identified target voiceprint is determined as the account that initiated the update intention request; or, If the update intent request carries account information, the account that initiates the update intent request is determined according to the account information carried in the update intent request.
3. The method according to claim 1, characterized in that Before determining whether to allow the execution of the intended update request based on whether the pre-saved allowed operation object and content include the operation object and operation content included in the intended update request, the method further includes: If the intention update request carries voice information, semantic recognition is performed on the voice information, and the operation object and operation content are determined based on the result of the semantic recognition. Subsequent steps are performed to determine whether the execution of the intention update request is allowed based on whether the pre-saved objects and contents allowed to operate include the operation objects and operation contents included in the intention update request.
4. The method according to claim 1, characterized in that: Before obtaining the account that initiates the intended update request, the method further includes: Identify the operation object and operation content included in the intended update request. If the operation object and operation content included in the intended update request are correct, execute the subsequent step of obtaining the account that initiated the intended update request.
5. The method according to claim 1, characterized in that The determining whether to allow the execution of the intention update request according to whether the pre-saved allowed operation object and content include the operation object and operation content included in the intention update request includes: Obtain the objects and contents of allowed operations that are pre-saved for the account; and determine whether to allow the account to execute the intention update request based on whether the objects and contents of allowed operations that are pre-saved for the account include the operation objects and operation contents included in the intention update request.
6. The method according to claim 1, characterized in that After acquiring the network policy saved corresponding to the operation object and the operation content, and before executing the network policy, the method further includes: For each currently pending request, determining whether the intended update request is related to the pending request based on whether the candidate object and candidate content contained in the pending request are identical to at least one of the operation object and the operation content; If it is determined that the intended update request is not related to any of the currently pending requests, then the subsequent step is to execute the network policy.
7. The method according to claim 6, characterized in that The method further comprises: If it is determined that the intention update request is related to any current request to be executed, and the candidate target corresponding to the request to be executed is different from the operation target carried in the intention update request, then determine whether the policy corresponding to the request to be executed is currently being executed. If so, stop the execution and execute the network policy. If not, and the policy has not been executed, delete the policy corresponding to the request to be executed and execute the network policy.
8. An intention updating device, characterized in that: The device comprises: A receiving module, used for receiving an intent update request; An acquisition and determination module is used to obtain the account that initiates the intended update request, determine whether the account has a legal identity and whether it has update authority; if so, determine whether to allow the intended update request to be executed based on whether the objects and contents of the pre-saved allowed operations contain the operation objects and operation contents contained in the intended update request; The processing module is used to obtain the network policy saved corresponding to the operation object and the operation content, and execute the network policy if the execution of the intention update request is allowed.
9. An electronic device, characterized in that: include: A memory for storing program instructions; A processor is used to call the program instructions stored in the memory, and execute the steps included in the method for updating the intention according to any one of claims 1 to 7 according to the obtained program instructions.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the method for updating according to any one of claims 1 to 7.
Citation Information
Patent Citations
Method, device and system for controlling network strategy
CN102882712A
Database operation alarm system and method
CN114510524A
Intention conflict processing method and device and readable storage medium
CN115915218A
Equipment control method and device, electronic device and storage medium
CN116088331A
Mobile terminal data protection method and device, electronic equipment and storage medium
CN117113305A