Network generation method and device, interface acquisition method and device, equipment and program product

Abstract

The invention relates to a network generation method, an interface acquisition method and device, equipment and a program product, and relates to the technical field of wireless communication. The network generation method is applied to an agent instance of an agent network architecture, and comprises the following steps: in response to a subnet generation request sent by a terminal, performing intention recognition processing on the subnet generation request to obtain a subnet generation intention, and sending the subnet generation request through a pre-acquired target agent service interface; determining a subnet generation parameter corresponding to the subnet generation intention, and returning the subnet generation parameter to the terminal; and generating a network configuration file based on the subnet generation parameter confirmed by the terminal, wherein the network configuration file is configured by the management and network arrangement system and generates a target subnet. According to the method and the device, the subnet generation demand of the terminal is identified through the agent in the agent domain, and the management and network arrangement system interface is called to generate the subnet, so that the network generation efficiency and the adaptation degree of the network and the terminal service are improved, and meanwhile, the subnet generation flexibility is improved.

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication technology, and more specifically, to a network generation method, an interface acquisition method, a network generation apparatus, an interface acquisition apparatus, an electronic device, and a computer program product. Background Technology

[0002] The current 5G network meets scenario requirements through private networks and network slicing. Network deployment requires advance planning, has relatively limited functionality, and cannot quickly go live to provide services. The 3rd Generation Partnership Project (3GPP) has begun discussions on use cases and requirements for 6G, with intelligent customized networks being a key 6G scenario that has attracted widespread attention from global companies and has already had relevant use cases and requirements approved.

[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] The purpose of this disclosure is to provide a network generation method, an interface acquisition method, a network generation device, an interface acquisition device, an electronic device, a computer-readable storage medium, and a computer program product, thereby overcoming, to at least a certain extent, the problems in related technologies where network deployment requires advance planning, functions are relatively limited, subnetworks cannot be dynamically generated on demand, and services cannot be quickly launched.

[0005] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part by practice of the invention.

[0006] According to a first aspect of this disclosure, a network generation method is provided, applied to an agent instance in an agent network architecture. The method includes: responding to a subnet generation request sent by a terminal; performing intent recognition processing on the subnet generation request to obtain a subnet generation intent, wherein the subnet generation request is sent through a pre-acquired target agent service interface; determining subnet generation parameters corresponding to the subnet generation intent; returning the subnet generation parameters to the terminal; and generating a network configuration file based on the subnet generation parameters confirmed by the terminal, wherein the network configuration file is used to configure and generate a target subnet by a management and network orchestration system.

[0007] In one exemplary embodiment of this disclosure, the agent network architecture includes an agent management function, and the method further includes: receiving an agent registration request sent by an agent instance by the agent management function, the agent registration request including one or more of the following: agent instance identifier, agent instance function, available tool description, service area, and service call interface; determining and storing the registration authentication result of the agent instance based on the agent registration request; and returning the registration authentication result to the agent instance.

[0008] In one exemplary embodiment of this disclosure, the step of responding to a subnet generation request sent by a terminal and performing intent recognition processing on the subnet generation request to obtain a subnet generation intent includes: receiving a subnet generation request sent by the terminal based on the target intelligent agent service interface; performing intent recognition processing on the subnet generation request to obtain an initial subnet generation intent, the initial subnet generation intent including initial network parameter information; sending the initial network parameter information to the terminal; and updating the initial network parameter information based on the network parameter change intent sent by the terminal to obtain target network parameter information, the target network parameter information including subnet generation parameters.

[0009] In one exemplary embodiment of this disclosure, the target agent service interface is obtained through the following steps: receiving a service interface acquisition request sent by a mobility and session management function, the service interface acquisition request being generated based on a session establishment request between the terminal and the agent domain; determining an interface request acquisition result corresponding to the service interface acquisition request, the interface request acquisition result including the encoded target agent service interface; and sending the interface request acquisition result to the mobility and session management function so that the mobility and session management function can send the interface request acquisition result to the terminal.

[0010] In one exemplary embodiment of this disclosure, the session establishment request includes an agent service requirement identifier, and determining the interface request acquisition result corresponding to the service interface acquisition request includes: acquiring the terminal identifier corresponding to the terminal; performing a retrieval operation on the user data management function based on the terminal identifier and the agent service requirement identifier to determine the service subscription status of the terminal in the target agent service; performing an internal query operation to determine the agent registration content of the target agent; and determining the target agent service interface response based on the service subscription status and the agent registration content, wherein the target agent service interface response is used to generate the interface request acquisition result.

[0011] In one exemplary embodiment of this disclosure, generating a network configuration file based on the subnet generation parameters confirmed by the terminal includes: receiving a parameter confirmation request initiated by the terminal; obtaining a predefined network configuration template, filling the subnet generation parameters into the network configuration template, and generating the network configuration file; and sending the network configuration file to a management and network orchestration system through a management and network orchestration interface, wherein the network configuration file is used by the management and network orchestration system to perform subnet deployment operations.

[0012] In one exemplary embodiment of this disclosure, the method further includes: receiving a subnet generation success response sent by a management and network orchestration system; and sending the subnet generation success response to the terminal so that the terminal can access the target subnet based on the subnet generation success response.

[0013] According to a second aspect of this disclosure, an interface acquisition method is provided, applied to a central network. The method includes: receiving a session establishment request sent by a terminal to an agent domain, the session establishment request including an agent service type identifier written into a non-access stratum message; executing a session establishment process based on the session establishment request, parsing the agent service type identifier to obtain a service interface acquisition request; sending the service interface acquisition request to an agent management function, and receiving a target agent service interface returned by the agent management function; sending a session response message to the terminal, the session response message including an encoded target agent service interface, so that the terminal sends a subnet generation request based on the target agent service interface to generate a target subnet.

[0014] In one exemplary embodiment of this disclosure, the non-access stratum message includes a protocol configuration option field, which includes one or more of the following: agent service request indication, service request field length, and agent service request content.

[0015] According to a third aspect of this disclosure, a network generation apparatus is provided, applied to an agent instance of an agent network architecture. The apparatus includes: an intent recognition module, configured to respond to a subnet generation request sent by a terminal, perform intent recognition processing on the subnet generation request to obtain a subnet generation intent, wherein the subnet generation request is sent through a pre-acquired target agent service interface; a subnet parameter generation module, configured to determine subnet generation parameters corresponding to the subnet generation intent and return the subnet generation parameters to the terminal; and a subnet generation module, configured to generate a network configuration file based on the subnet generation parameters confirmed by the terminal, wherein the network configuration file is used by a management and network orchestration system to configure and generate a target subnet.

[0016] In one exemplary embodiment of this disclosure, the agent network architecture includes an agent management function, and the network generation device further includes an agent registration module, configured to: receive an agent registration request sent by an agent instance by the agent management function, wherein the agent registration request includes one or more of the following: agent instance identifier, agent instance function, available tool description, service area, and service call interface; determine and store the registration authentication result of the agent instance based on the agent registration request; and return the registration authentication result to the agent instance.

[0017] In one exemplary embodiment of this disclosure, the intent recognition module includes an intent recognition unit, configured to: receive a subnet generation request sent by the terminal based on the target intelligent agent service interface; perform intent recognition processing on the subnet generation request to obtain an initial subnet generation intent, the initial subnet generation intent including initial network parameter information; send the initial network parameter information to the terminal; and update the initial network parameter information based on the network parameter change intent sent by the terminal to obtain target network parameter information, the target network parameter information including subnet generation parameters.

[0018] In one exemplary embodiment of this disclosure, the intent recognition unit includes a service interface acquisition unit, configured to: receive a service interface acquisition request sent by a mobility and session management function, the service interface acquisition request being generated based on a session establishment request between the terminal and the agent domain; determine an interface request acquisition result corresponding to the service interface acquisition request, the interface request acquisition result including an encoded target agent service interface; and send the interface request acquisition result to the mobility and session management function, so that the mobility and session management function sends the interface request acquisition result to the terminal.

[0019] In one exemplary embodiment of this disclosure, the session establishment request includes an agent service request identifier, and the service interface acquisition unit includes a service interface acquisition subunit, configured to: acquire a terminal identifier corresponding to the terminal; perform a retrieval operation on the user data management function based on the terminal identifier and the agent service request identifier to determine the service subscription status of the terminal in the target agent service; perform an internal query operation to determine the agent registration content of the target agent; and determine the target agent service interface response based on the service subscription status and the agent registration content, wherein the target agent service interface response is used to generate the interface request acquisition result.

[0020] In one exemplary embodiment of this disclosure, the subnet generation module includes a subnet generation unit, configured to: receive a parameter confirmation request initiated by the terminal; obtain a predefined network configuration template, fill the subnet generation parameters into the network configuration template, and generate the network configuration file; and send the network configuration file to a management and network orchestration system through a management and network orchestration interface, wherein the network configuration file is used by the management and network orchestration system to perform subnet deployment operations.

[0021] In one exemplary embodiment of this disclosure, the network generation device further includes a subnet generation module, configured to: receive a subnet generation success response sent by a management and network orchestration system; and send the subnet generation success response to the terminal so that the terminal can access the target subnet based on the subnet generation success response.

[0022] According to a fourth aspect of this disclosure, an interface acquisition apparatus is provided, applied to a central network. The apparatus includes: a session request sending module, configured to receive a session establishment request sent by a terminal to an agent domain, the session establishment request including an agent service type identifier written into a non-access stratum message; an interface request determining module, configured to execute a session establishment process based on the session establishment request, and parse the agent service type identifier to obtain a service interface acquisition request; a target interface determining module, configured to send the service interface acquisition request to an agent management function, and receive a target agent service interface returned by the agent management function; and a session response module, configured to send a session response message to the terminal, the session response message including an encoded target agent service interface, so that the terminal can send a subnet generation request based on the target agent service interface to generate a target subnet.

[0023] According to a fifth aspect of this disclosure, an electronic device is provided, comprising: a processor; and a memory storing computer-readable instructions, which, when executed by the processor, implement the network generation method or the interface acquisition method according to any one of the preceding claims.

[0024] According to a sixth aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the network generation method or the interface acquisition method according to any one of the preceding claims.

[0025] According to a seventh aspect of this disclosure, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the network generation method or the interface acquisition method described in any one of the preceding claims.

[0026] The technical solution provided in this disclosure may include the following beneficial effects: The network generation method in the exemplary embodiments of this disclosure, on the one hand, helps improve network generation efficiency and the adaptability of the network to terminal services by having an intelligent agent in the intelligent agent domain identify the subnet generation requirements of the terminal and call the management and network orchestration system interface to generate the subnet, while also increasing the flexibility of subnet generation. On the other hand, since the intelligent agent is deployed in an intelligent agent domain that is relatively independent of the core network, it has a low coupling degree with the core network and is easy to upgrade based on the existing network.

[0027] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0028] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings: Figure 1 A flowchart illustrating an exemplary embodiment of the network generation method according to the present disclosure is shown schematically; Figure 2 The diagram illustrates a 5G-A / 6G distributed network architecture according to an exemplary embodiment of the present disclosure. Figure 3 A schematic diagram illustrating a network intelligent agent service architecture according to an exemplary embodiment of the present disclosure is shown. Figure 4 The flowchart illustrating a terminal obtaining a network operation and maintenance intelligent agent service interface according to an exemplary embodiment of the present disclosure is shown in the illustration. Figure 5 The flowchart illustrating a network operation and maintenance agent generating a subnet based on terminal demand intent according to an exemplary embodiment of the present disclosure is shown. Figure 6 A flowchart illustrating an interface acquisition method according to an exemplary embodiment of the present disclosure is shown schematically; Figure 7 The flowchart illustrating a terminal obtaining an intelligent agent service interface in a 5G-A scenario according to an exemplary embodiment of the present disclosure is shown. Figure 8 A schematic diagram illustrating the PCO field structure according to an exemplary embodiment of the present disclosure is shown. Figure 9The illustration schematically shows a flowchart of a network operation and maintenance intelligent agent generating a subnet based on terminal intent in a 5G-A scenario according to an exemplary embodiment of the present disclosure; Figure 10 A block diagram of a network generation apparatus according to an exemplary embodiment of the present disclosure is shown schematically; Figure 11 A block diagram of an interface acquisition apparatus according to an exemplary embodiment of the present disclosure is shown schematically; Figure 12 The illustration schematically shows a computer-readable storage medium according to an exemplary embodiment of the present disclosure; Figure 13 A block diagram of an electronic device according to an exemplary embodiment of the present disclosure is shown schematically. Detailed Implementation

[0029] 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 embodiments set forth herein; rather, they are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0030] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced without one or more of the specific details described, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known structures, methods, apparatuses, implementations, materials, or operations are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0031] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, or in one or more software-hardened modules, or in different network and / or processor devices and / or microcontroller devices.

[0032] AI agents, with their autonomous decision-making, intelligent interaction, and dynamic adaptation capabilities, have become one of the key technologies for the evolution of 6G networks. The 3GPP SA1 working group has begun researching potential use cases and requirements for AI agents, and SA Working Group 2 is also about to begin research on related architectures. In future 6G application scenarios, AI agent technology can be combined to achieve on-demand dynamic generation of sub-networks.

[0033] According to embodiments of this disclosure, a network generation method, an interface acquisition method, a network generation apparatus, an interface acquisition apparatus, an electronic device, a computer-readable storage medium, and a computer program product are proposed.

[0034] In this article, it is important to understand that the terms used, such as AI Agent, refer to intelligent agents that are capable of proactive thinking and action, working in a human-like manner, "understanding" user needs through large models, proactively "planning" to achieve goals, using various "tools" to complete tasks, and ultimately "acting" to execute these tasks.

[0035] UE (User Equipment): Various terminal devices with wireless communication capabilities that support users' access to network services.

[0036] SBI (Service Based Interface): A service-based interface in the 5G core network. It uses HTTP on the Internet for communication and provides a standardized means for interoperability between control plane network elements within the 5GC.

[0037] GTP-U (General Packet Radio Services Tunnelling Protocol for User Plane): A tunneling protocol based on IP / UDP in mobile communication, used to establish tunnels between GTP-U protocol entities, mainly responsible for user plane data transmission.

[0038] UDM (Unified Data Management): In the 5G core network, it is responsible for the management of 5G user identifiers, subscription data, authentication data, and user service element registration management.

[0039] AMF (Access and Mobility Management Function): In the 5G core network, it directly manages the access requests of 5G users through base stations and is responsible for functions such as registration management, connection management, reachability management, and mobility management.

[0040] SMF (Session Management Function): In the 5G core network, it is responsible for user session management, routing, user plane management, policy control, billing and other functions.

[0041] UPF (User Plane Function): In the 5G core network, it independently undertakes the function of user plane data processing, mainly responsible for the routing and forwarding of user data packets, policy execution and protocol adaptation.

[0042] SUPI (Subscription Permanent Identifier): The true identity identifier of a 5G terminal, consisting of the country code, network code, and mobile user identification code.

[0043] NAS (Non-Access Stratum): In mobile communications, it is responsible for authentication, registration, and connection / session management between the UE and the core network.

[0044] PCO (Protocol Configuration Option): Used to provide the UE with additional information for connecting to the network. In this disclosure, it is used to implement the service interface for the UE to obtain network operation and maintenance intelligence.

[0045] DN (Data Network): The external data network of the 5G core network, such as operator services, Internet or third-party services, etc.

[0046] DNN (Data Network Name): In 5G networks, it is used to identify external networks, for session management and service selection, user plane resource allocation and path selection, and to work in conjunction with network slicing.

[0047] PDU (Protocol Data Unit): In the 5G core network, PDU connection service is the service of exchanging data packets between user equipment (UE) and data network (DN). A PDU session refers to the communication process between a user equipment (UE) and a data network (DN). After a PDU session is established, a data transmission channel between the UE and the DN is established.

[0048] MANO (Management and Orchestration): Responsible for the lifecycle management, resource orchestration, and service deployment of virtualized network functions.

[0049] Furthermore, the number of any 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.

[0050] The principles and spirit of this disclosure will be explained in detail below with reference to several representative embodiments.

[0051] Based on this, in this example embodiment, a network generation method is first provided. This network generation method is based on the implementation of intelligent agents in the intelligent agent network architecture. The network generation method of this disclosure can be implemented using a server or using a terminal device. The terminal described in this disclosure can include mobile terminals such as mobile phones, tablets, laptops, handheld computers, and personal digital assistants (PDAs), as well as fixed terminals such as desktop computers. Figure 1 A schematic diagram illustrating a network generation method flow according to some embodiments of the present disclosure is provided. (Reference) Figure 1 The network generation method may include the following steps: Step S110: In response to the subnet generation request sent by the terminal, perform intent recognition processing on the subnet generation request to obtain the subnet generation intent, and send the subnet generation request through the pre-acquired target intelligent agent service interface; Step S120: Determine the subnet generation parameters corresponding to the subnet generation intention, and return the subnet generation parameters to the terminal; Step S130: Generate a network configuration file based on the subnet generation parameters confirmed by the terminal. The network configuration file is used by the management and network orchestration system to configure and generate the target subnet.

[0052] According to the network generation method in this example embodiment, on the one hand, by having an intelligent agent in the intelligent agent domain identify the subnet generation requirements of the terminal and call the management and network orchestration system interface to generate the subnet, it helps to improve network generation efficiency and the adaptability of the network to terminal services, while also increasing the flexibility of subnet generation. On the other hand, since the intelligent agent is deployed in an intelligent agent domain that is relatively independent of the core network, it has a low coupling degree with the core network and is easy to upgrade based on the existing network.

[0053] The network generation method in this example embodiment will be further explained below.

[0054] Based on existing distributed network architectures, this disclosure proposes a 5G evolution (5G-Advanced, 5G-A) / 6G distributed network architecture, referencing... Figure 2 , Figure 2 A schematic diagram illustrating a 5G-A / 6G distributed network architecture according to an exemplary embodiment of this disclosure is shown. Figure 2As shown, the distributed network architecture is logically divided into two levels, including distributed subnets (also known as distributed networks) and a central network.

[0055] The central network and distributed networks each contain their corresponding Network Functions (NFs). The central network primarily targets individual consumer users (2C users), meeting wide-area coverage requirements and supporting intelligence, sensing, and real-time communication. The distributed subnets include edge networks for individual consumers (To Customer, 2C) and dedicated networks for industry enterprises (To Business, 2B). The distributed subnets primarily meet the low-latency access requirements of 2C users and 2B private network services, such as access services that do not require users to leave the campus (e.g., mining operations).

[0056] Based on the aforementioned distributed network architecture, this disclosure proposes a network intelligent agent service architecture as follows: Figure 3 As shown, Figure 3 A schematic diagram illustrating a network agent service architecture according to an exemplary embodiment of the present disclosure is shown. Figure 3 In addition to existing 5G network elements such as UDM, AMF, and SMF, it also includes NF Repository Function (NRF), Service Communication Proxy (SCP), and agent-related agent management functions and agent instances; among them, agent management function can be considered as agent management center.

[0057] Specifically, the intelligent agent management function manages the registration and status monitoring of intelligent agent entities, as well as providing intelligent agent service addressing and external access functions for end users. Different intelligent agent entities possess one or more different functions, such as network operation and maintenance and campus security. After an intelligent agent entity goes online, it needs to register its own information with the intelligent agent management function, including instance ID, instance function description, service area, and service call interface.

[0058] In this architecture, the agent management function is a newly added network element in the core network control plane, interacting with other network elements through the newly added SBI interface. The agent instance logically belongs to the agent domain of the network, and the UE communicates with the agent through the GTP-U tunnel of the UE / RadioAccess Network (RAN) - agent domain. Among them, GTP (GPRS Tunneling Protocol) can be decomposed into three independent protocols, including GTP-C, GTP-U and GTP'. GTP-U is used to transmit user data between the radio access network and the core network within the General Packet Radio Service (GPRS) core network.

[0059] In one exemplary embodiment of this disclosure, the agent management function receives an agent registration request sent by an agent instance. The agent registration request includes one or more of the following: agent instance identifier, agent instance function, description of available tools, service area, and service call interface. Based on the agent registration request, the function determines and stores the registration authentication result of the agent instance and returns the registration authentication result to the agent instance.

[0060] Figure 3 The illustrated agent network architecture includes agent management functionality. Agent instances register by sending a registration request to the agent management functionality. (Reference) Figure 4 , Figure 4 The flowchart illustrating a terminal obtaining a network operation and maintenance intelligent agent service interface according to an exemplary embodiment of the present disclosure is shown.

[0061] In step 0a, each agent instance initiates registration with the agent management center (i.e., the agent management function) of the central network, carrying the agent instance ID, the agent instance's function (such as network operation and maintenance, security services, etc.), a description of available tools (such as subnet generation, camera image processing, etc.), service area, and service call interface information. The agent management function authenticates the agent registration request sent by the agent instance. In step 0b, after the agent registration request is successfully authenticated, the agent management function stores the agent registration information. In step 0c, the agent management function sends a registration response to the agent, that is, returns the corresponding registration authentication result to the agent instance, including the result of successful authentication and the result of unsuccessful authentication.

[0062] Through the above steps, each agent instance registers its own information with the agent management function, enabling the agent management function to monitor the status of the agent instances. Furthermore, the agents disclosed herein are deployed in an agent domain relatively independent of the core network, with low coupling to the core network, facilitating easy upgrades to the existing network. For example, Figure 3The intelligent agent domain in this disclosure includes business intelligent agents and network operation and maintenance intelligent agents; in this disclosure, the network operation and maintenance intelligent agent has network generation capabilities.

[0063] In one exemplary embodiment of this disclosure, for step S110, in response to a subnet generation request sent by a terminal, intent recognition processing is performed on the subnet generation request to obtain a subnet generation intent, including: receiving a subnet generation request sent by the terminal based on a target intelligent agent service interface; performing intent recognition processing on the subnet generation request to obtain an initial subnet generation intent, the initial subnet generation intent including initial network parameter information; sending the initial network parameter information to the terminal; and updating the initial network parameter information based on the network parameter change intent sent by the terminal to obtain target network parameter information, the target network parameter information including subnet generation parameters.

[0064] The subnet generation request can be a request sent by the terminal to generate a target subnet to provide services based on specific scenario requirements. Network parameter information can be the specific information about the relevant network parameters used by the target agent to generate the target subnet. Initial network parameter information can be the network parameters obtained after initial intent recognition processing of the subnet generation request. Target network parameter information can be the network parameters obtained after updating the initial network parameter information.

[0065] refer to Figure 5 , Figure 5 The illustration schematically depicts a flowchart of a network operation and maintenance agent generating a subnet based on terminal demand intent according to an exemplary embodiment of this disclosure. The terminal sends a subnet generation request through a pre-obtained target agent service interface. In this disclosure, the target agent service interface can be a service interface corresponding to the network operation and maintenance agent, and this service interface is based on... Figure 4 It is obtained through the process.

[0066] Continue to refer to Figure 5 In step 1, the terminal initiates a subnet generation request. The terminal initiates the subnet generation request by calling the network operations and maintenance intelligent agent service interface, carrying the user's request intent (such as subnet service duration, subnet service area, and subnet service quality requirements). This subnet generation request needs to be routed to the intelligent agent through a pre-established UE-to-intelligent agent domain PDU session. For example, the subnet generation request may be sent to the network operations and maintenance intelligent agent based on user plane functions.

[0067] After receiving a subnet generation request from a terminal, the network operations and maintenance (O&M) agent, in step 2, identifies the terminal's subnet generation intention and converts it into network parameters. Specifically, the O&M agent performs intention recognition processing on the subnet generation request to obtain an initial subnet generation intention, which includes initial network parameter information. In step 3, the O&M agent returns the initial network parameter information to the terminal, and this response is routed to the terminal through the same PDU session.

[0068] Upon receiving the initial network parameter information, the terminal will determine whether the initial network parameter information matches the subnet generation request it sent. If the terminal believes that the initial network parameter information returned by the network operation and maintenance intelligence does not match the subnet generation request, then in step 4, the terminal will initiate a network parameter change request to the network operation and maintenance intelligence by calling the service interface to generate a network parameter modification intent.

[0069] In step 5, the network operations and maintenance agent identifies the terminal's intent to modify network parameters and updates the previously generated network parameters. For example, based on the network parameter change intent sent by the terminal, the network operations and maintenance agent updates the initial network parameter information to obtain the target network parameter information, which includes the updated subnet generation parameters. In step 6, the network operations and maintenance agent returns the updated network parameters, i.e., the target network parameter information.

[0070] In this disclosure, steps 4 to 6 can be a set of steps involving interaction between the terminal and the network operation and maintenance intelligent agent to correct intent recognition errors, executed zero to multiple times. This depends on the network operation and maintenance intelligent agent's ability to recognize the terminal's intent. Fine-tuning the agent's large model can reduce the number of parameter corrections initiated by the terminal. If the network parameters generated by the agent on the first attempt meet the terminal's needs, this set of steps can be skipped. This set of steps ensures that the network operation and maintenance intelligent agent can correctly convert the terminal's demand intent into network parameters. By introducing multiple interaction steps between the terminal and the intelligent agent to reduce demand recognition errors, the adaptability of subnet generation can be improved, meeting the needs of future 5G-A / 6G intelligent customized networks.

[0071] It will be readily understood by those skilled in the art that the target intelligent agent in this disclosure may also be other intelligent agents with network operation and maintenance functions, and this disclosure does not impose any special restrictions on the specific type of intelligent agent.

[0072] In one exemplary embodiment of this disclosure, the target agent service interface is obtained through the following steps: receiving a service interface acquisition request sent by a mobility and session management function, the service interface acquisition request being generated based on a session establishment request between the terminal and the agent domain; determining the interface request acquisition result corresponding to the service interface acquisition request, the interface request acquisition result including the encoded target agent service interface; and sending the interface request acquisition result to the mobility and session management function so that the mobility and session management function can send the interface request acquisition result to the terminal.

[0073] Here, "agent domain" refers to the domain in which an agent resides, and it is an agent domain independent of the core network. "Session establishment request" can be a session request initiated by a terminal to interact with a specific agent within the agent domain. "Service interface acquisition request" can be a request initiated by a terminal to obtain the service interface of a specific agent. "Interface request acquisition result" can be the interface acquisition result returned by the agent management function based on the service interface acquisition request.

[0074] Continue to refer to Figure 4 In step 1, the terminal requiring subnet generation initiates a network operation and maintenance intelligent agent service interface acquisition request to the central network via uplink NAS signaling, carrying information such as the intelligent agent service request identifier (network operation and maintenance). In step 2, after receiving the uplink NAS request from the terminal, the central network's mobility and session management function extracts and parses the intelligent agent service interface acquisition request carried in the NAS signaling.

[0075] In step 3, the mobility and session management function forwards the terminal's network operation and maintenance intelligent agent service interface acquisition request to the intelligent agent management function. After receiving the service interface acquisition request, in step 4, the intelligent agent management function retrieves whether the current terminal has subscribed to the network operation and maintenance intelligent agent service based on the terminal identifier (such as SUPI) and the intelligent agent service demand identifier from the user data management function.

[0076] The intelligent agent management function determines whether the corresponding service interface can be provided to the terminal by querying the interface request retrieval results corresponding to the service interface. Specifically, it retrieves the corresponding interface request retrieval results by querying the specific registration information of the network operation and maintenance intelligent agent, including its service open interfaces.

[0077] When a terminal subscribes to the network operations and maintenance intelligent agent service, the intelligent agent management function returns the network operations and maintenance intelligent agent service interface to the terminal through an interface request retrieval result. Specifically, the interface request retrieval result sends the interface request retrieval result to the mobility and session management function, which then sends the result back to the terminal. Through these steps, the terminal obtains the service interface of the network operations and maintenance intelligent agent, facilitating communication between the terminal and the intelligent agent based on this service interface.

[0078] In one exemplary embodiment of this disclosure, determining the interface request acquisition result corresponding to the service interface acquisition request includes: acquiring the terminal identifier corresponding to the terminal; performing a retrieval operation on the user data management function based on the terminal identifier and the intelligent agent service demand identifier to determine the service signing status of the terminal in the target intelligent agent service; performing an internal query operation to determine the intelligent agent registration content of the target intelligent agent; and determining the target intelligent agent service interface response based on the service signing status and the intelligent agent registration content, wherein the target intelligent agent service interface response is used to generate the interface request acquisition result.

[0079] Among these, the intelligent agent service request identifier can be the identifier corresponding to the intelligent agent service interface that the terminal needs to obtain. The service subscription status can be the status of whether the terminal has subscribed to the target intelligent agent service. The internal query operation can be a query operation performed by the intelligent agent management function to query the registration information of one or more intelligent agents. The intelligent agent registration content can be the specific registration information of the target intelligent agent.

[0080] Continue to refer to Figure 4 In step 5, the agent management function queries the internal storage for the specific registration information of the network operations and maintenance agent, including service open interfaces. In step 6, the agent management function returns the network operations and maintenance agent service interface response to the mobility and session management function. In step 7, the mobility and session management function encodes the network operations and maintenance agent service interface into NAS signaling.

[0081] In step 8, the mobility and session management function returns the network operations and maintenance intelligent agent service interface via downlink NAS signaling. In step 9, the terminal parses and extracts the network operations and maintenance intelligent agent service interface carried in the NAS message. The intelligent agent management function can determine whether it can provide a service interface to the terminal through a query operation and returns the service interface response to the terminal so that the terminal can perform subsequent operations based on the service interface response.

[0082] In one exemplary embodiment of this disclosure, generating a network configuration file based on subnet generation parameters confirmed by the terminal includes: receiving a parameter confirmation request initiated by the terminal; obtaining a predefined network configuration template, filling the subnet generation parameters into the network configuration template, and generating a network configuration file; and sending the network configuration file to a management and network orchestration system through a management and network orchestration interface, wherein the network configuration file is used by the management and network orchestration system to perform subnet deployment operations.

[0083] The parameter confirmation request can be a request sent by the terminal to the agent management function to confirm network parameters. The network configuration template can be the template used by the management and network orchestration system when generating subnets. The network configuration file can be the configuration file generated by filling the subnet generation parameters into the network configuration template. The subnet deployment operation can be the specific operation by which the management and network orchestration system allocates a target subnet to the terminal.

[0084] Continue to refer to Figure 5 When the terminal determines that the subnet generation parameters generated by the network operations and maintenance agent match its own subnet generation request, in step 7, the terminal initiates a network parameter confirmation request, prompting the agent to proceed to the next step. In step 8, after receiving the terminal's network parameter confirmation request, the network operations and maintenance agent fills the subnet generation parameters into the network configuration template, generates a network configuration file, and sends the network configuration file to the management and network orchestration system (i.e., the MANO system). The network configuration file generated by the network operations and maintenance agent through the above steps can serve as the basis for the MANO system to perform subnet deployment operations.

[0085] In one exemplary embodiment of this disclosure, for step S130, a subnet generation success response is received from the management and network orchestration system; a subnet generation success response is sent to the terminal so that the terminal can access the target subnet based on the subnet generation success response.

[0086] Continue to refer to Figure 5 In step 9, the network operations and maintenance agent submits a network configuration file to the MANO system through the MANO system interface. In step 10, the MANO system allocates subnet resources based on the network configuration file and deploys the subnet according to the configuration. In step 11, the MANO system returns a response indicating successful deployment of the target subnet. In step 12, the network operations and maintenance agent returns a response indicating successful deployment of the target subnet to the terminal. In step 13, the terminal accesses the target subnet and obtains the services provided by the target subnet. Through the above steps, the terminal can access the target subnet and perform network communication.

[0087] The network generation method disclosed herein, on the one hand, improves network generation efficiency and the adaptability of the network to terminal services by having an intelligent agent in the intelligent agent domain identify the subnet generation requirements of the terminal and call the management and network orchestration system interface to generate the subnet, while also increasing the flexibility of subnet generation. On the other hand, since the intelligent agent is deployed in an intelligent agent domain relatively independent of the core network, its coupling with the core network is low, making it easy to upgrade based on the existing network. Furthermore, by introducing multiple interaction steps between the terminal and the intelligent agent to reduce requirement identification errors, it helps to improve the adaptability of subnet generation and meet the needs of intelligent customized networks for future mobile communication standards (such as 5G-A / 6G). Moreover, during the network generation process, the user plane enables the interaction of specific service messages between the UE and the network operation and maintenance intelligent agent, satisfying the C / U separation requirement.

[0088] Next, in this example embodiment, an interface acquisition method is provided, which is mainly based on the user plane function of the core network. Figure 6 The illustration schematically depicts a flowchart of an interface acquisition method according to some embodiments of the present disclosure. References Figure 6 The method for obtaining this interface may include the following steps: Step S610: Receive a session establishment request sent by the terminal to the agent domain. The session establishment request includes an agent service type identifier written into the non-access stratum message. Step S620: Execute the session establishment process based on the session establishment request, parse the agent service type identifier, and obtain the service interface acquisition request; Step S630: Send a service interface acquisition request to the agent management function and receive the target agent service interface returned by the agent management function; Step S640: Send a session response message to the terminal. The session response message includes the encoded target agent service interface, so that the terminal can send a subnet generation request based on the target agent service interface to generate the target subnet.

[0089] According to the interface acquisition method in this example embodiment, the network operation and maintenance intelligent agent service interface is acquired through the NAS message flow between the UE and the core network control plane. Subsequently, the specific service message interaction between the UE and the network operation and maintenance intelligent agent can be realized through the user plane, thus meeting the C / U separation requirement.

[0090] The interface acquisition method in this example embodiment will be further explained below.

[0091] refer to Figure 7 , Figure 7 This illustration schematically depicts a flowchart of a terminal obtaining an intelligent agent service interface in a 5G-A scenario according to an exemplary embodiment of this disclosure. Before the terminal sends a service interface request, the intelligent agent registration process is as follows: Figure 4 The registration process for obtaining the network operation and maintenance intelligent agent service interface is the same for the middle terminal. In step 0a, each network intelligent agent instance initiates an intelligent agent registration request to the intelligent agent management function, carrying the intelligent agent instance ID, the intelligent agent instance's function and available toolkit description, service area and service interface, including the Uniform Resource Identifier (URI) of the service IP address (Internet Protocol Address); after the intelligent agent management center authenticates the legality of the registered network intelligent agents, it stores the registration content of each intelligent agent.

[0092] After the agent instance registration operation is completed, in step 1, the UE with subnet generation needs writes its own network operation and maintenance agent service open interface acquisition requirements into the PCO field of the PDU session establishment request NAS message, which is the protocol configuration option field of the non-access stratum message.

[0093] In one exemplary embodiment of this disclosure, the non-access stratum message includes a protocol configuration option field, which includes one or more of the following: agent service request indication, service request field length, and agent service request content.

[0094] Specifically, the PCO Additional parameters list for the NAS message of the PDU session will include a new AI Agent Service Request Indicator, a new Length of AI Agent Service Request Contents, and a new AI Agent Service Request Contents. The request content can carry the identifier of the requested AI agent service type (e.g., network operations AI agent).

[0095] Figure 8 A schematic diagram illustrating the PCO field structure according to an exemplary embodiment of this disclosure is shown. Figure 8 As shown, in the NAS signaling of the session message, a single PCO field consists of an independent container ID (occupying two bytes), a content length indicator (occupying one byte), and the container content (maximum 255 bytes). The container ID range of 0xFF00H to 0xFFFFH is reserved for operator use and is not currently in use.

[0096] An implementation scheme for PCO carrying requests / responses to the agent service interface involves selecting an operator-specific ID (e.g., 0xFF00H) to identify the agent service interface request (uplink) / response (downlink), with the content length indicating the length of the request / response, and the container content carrying the specific content of the request / response. For service interface information, a length of 255 bytes is sufficient for encoding.

[0097] Continue to refer to Figure 7 In step 2, the UE sends an uplink NAS message to the AMF of the central network, carrying a PDU session establishment request. The request carries a PCO field that encodes the agent service interface acquisition request, and the requested DNN is configured as an agent domain identifier, which is used by the SMF to select a specific UPF to establish a UE-agent domain PDU session.

[0098] In step 3, the AMF identifies the uplink NAS message carrying a request related to PDU session establishment based on the NAS message indication. In step 4, the AMF initiates a session establishment request to the SMF through the SMF's SBI interface, transparently transmitting the NAS message related to the UE's PDU session establishment.

[0099] In step 5, the SMF will execute the standard 5G PDU session establishment process and simultaneously extract and parse the network operation and maintenance intelligent agent service interface acquisition request carried in the PCO field. In step 6, the SMF will initiate the intelligent agent service interface acquisition request for the UE to the intelligent agent management function through the SBI interface of the intelligent agent management function.

[0100] In step 7, the agent management function queries whether the UE has subscribed to the network operations and maintenance agent service through the UDM's SBI interface, based on the UE identifier (such as SUPI) and agent service type identifier. In step 8, the agent management function queries the internal network operations and maintenance agent's specific registration information, including service interfaces. In step 9, the agent management function returns the network operations and maintenance agent service interface to the SMF.

[0101] In step 10, the SMF encodes the network operations and maintenance intelligent agent service open interface into the PCO field of the PDU session establishment response NAS message. In step 11, the SMF returns a PDU session establishment response to the UE via the AMF, carrying the PCO field of the encoded intelligent agent service interface. In step 12, the UE parses and extracts the network operations and maintenance intelligent agent service interface carried in the PCO field.

[0102] This embodiment omits the description of the conventional 5G PDU session establishment process, including user session subscription data query, UPF selection, and user plane GTP-U tunnel establishment. The advantages are as follows: Firstly, it does not require modification to the existing NAS message fields and NAS message passing processing framework, resulting in minimal changes to the existing 5G-A network. Secondly, the NAS PCO field only carries the content of the intelligent agent service addressing request and response, without carrying specific user requirements, thus meeting the 255-byte maximum length limit of the PCO container. Thirdly, after obtaining the intelligent agent service interface, the network operation and maintenance intelligent agent service can be accessed through a simultaneously established PDU session connecting the intelligent agent domain, simplifying the implementation process.

[0103] Furthermore, this disclosure Figure 9 This illustration schematically depicts a flowchart of a network operation and maintenance intelligent agent generating a subnet based on terminal intent in a 5G-A scenario according to an exemplary embodiment of this disclosure. In this embodiment, the 5G network element UPF serves as a user plane function, inheriting the GTP-U tunnel between the UE and the intelligent agent domain for message routing between the UE client and the network operation and maintenance intelligent agent. For example, in step 1, the UE calls the intelligent agent service interface to initiate a subnet generation request. The specific implementation process of the remaining steps is similar to... Figure 5 The process of "network operation and maintenance intelligent agent generating subnet based on terminal demand intent" is the same as that in the previous disclosure, so this disclosure will not repeat it again.

[0104] This disclosure proposes a network generation method based on a network operation and maintenance (O&M) intelligent agent. The O&M intelligent agent is deployed in an intelligent agent domain and registers its own information with the newly added intelligent agent management network element (also known as intelligent agent management function) in the core network. Terminals accessing the central network obtain the O&M intelligent agent service call interface through the NAS signaling process and then initiate subnet customization requests. The O&M intelligent agent generates a subnet configuration file based on the request identification result and distributes it to the MANO system. The MANO system then generates the subnet based on the terminal's requirements, providing customized services to the terminal. This solution can improve network generation efficiency and the adaptability of the network to terminal services, meeting the needs of future 5G-A / 6G intelligent customized networks.

[0105] It should be noted that although the steps of the method in this invention are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0106] Furthermore, in this example embodiment, a network generation apparatus is also provided. (See reference...) Figure 10The network generation device 1000 is applied to an agent instance in an agent network architecture. The network generation device 1000 may include: an intent recognition module 1010, a subnet parameter generation module 1020, and a subnet generation module 1030.

[0107] Specifically, the intent recognition module 1010 is used to respond to the subnet generation request sent by the terminal, perform intent recognition processing on the subnet generation request to obtain the subnet generation intent, and send the subnet generation request through the pre-acquired target intelligent agent service interface; the subnet parameter generation module 1020 is used to determine the subnet generation parameters corresponding to the subnet generation intent and return the subnet generation parameters to the terminal; the subnet generation module 1030 is used to generate a network configuration file based on the subnet generation parameters confirmed by the terminal, and the network configuration file is used by the management and network orchestration system to configure and generate the target subnet.

[0108] In one exemplary embodiment of this disclosure, the agent network architecture includes an agent management function, and the network generation device 1000 further includes an agent registration module, configured to: receive an agent registration request sent by an agent instance by the agent management function, wherein the agent registration request includes one or more of the following: agent instance identifier, agent instance function, description of available tools, service area and service call interface; determine and store the registration authentication result of the agent instance based on the agent registration request; and return the registration authentication result to the agent instance.

[0109] In one exemplary embodiment of this disclosure, the intent recognition module 1010 includes an intent recognition unit, configured to: receive a subnet generation request sent by a terminal based on a target intelligent agent service interface; perform intent recognition processing on the subnet generation request to obtain an initial subnet generation intent, the initial subnet generation intent including initial network parameter information; send the initial network parameter information to the terminal; and update the initial network parameter information based on the network parameter change intent sent by the terminal to obtain target network parameter information, the target network parameter information including subnet generation parameters.

[0110] In one exemplary embodiment of this disclosure, the intent recognition unit includes a service interface acquisition unit, configured to: receive a service interface acquisition request sent by a mobility and session management function, the service interface acquisition request being generated based on a session establishment request between the terminal and the agent domain; determine the interface request acquisition result corresponding to the service interface acquisition request, the interface request acquisition result including an encoded target agent service interface; and send the interface request acquisition result to the mobility and session management function, so that the mobility and session management function can send the interface request acquisition result to the terminal.

[0111] In one exemplary embodiment of this disclosure, the session establishment request includes an agent service request identifier, and the service interface acquisition unit includes a service interface acquisition subunit, used for: acquiring the terminal identifier corresponding to the terminal; performing a retrieval operation on the user data management function based on the terminal identifier and the agent service request identifier to determine the service signing status of the terminal in the target agent service; performing an internal query operation to determine the agent registration content of the target agent; and determining the target agent service interface response based on the service signing status and the agent registration content, wherein the target agent service interface response is used to generate the interface request acquisition result.

[0112] In one exemplary embodiment of this disclosure, the subnet generation module 1030 includes a subnet generation unit, configured to: receive a parameter confirmation request initiated by a terminal; obtain a predefined network configuration template, fill in the subnet generation parameters into the network configuration template, and generate a network configuration file; and send the network configuration file to a management and network orchestration system through a management and network orchestration interface, wherein the network configuration file is used by the management and network orchestration system to perform subnet deployment operations.

[0113] In one exemplary embodiment of this disclosure, the network generation apparatus 1000 further includes a subnet generation module, configured to: receive a subnet generation success response sent by a management and network orchestration system; and send a subnet generation success response to a terminal so that the terminal can access the target subnet based on the subnet generation success response.

[0114] Next, in this example embodiment, an interface acquisition device is also provided. (See reference...) Figure 11 The interface acquisition device 1100 is applied to the central network. The interface acquisition device 1100 may include: a session request sending module 1110, an interface request determination module 1120, a target interface determination module 1130, and a session response module 1140.

[0115] Specifically, the session request sending module 1110 is used to receive a session establishment request between the terminal and the agent domain, the session establishment request including an agent service type identifier written into the non-access stratum message; the interface request determination module 1120 is used to execute a session establishment process based on the session establishment request, parse the agent service type identifier, and obtain a service interface acquisition request; the target interface determination module 1130 is used to send a service interface acquisition request to the agent management function and receive the target agent service interface returned by the agent management function; the session response module 1140 is used to send a session response message to the terminal, the session response message including the encoded target agent service interface, so that the terminal can send a subnet generation request based on the target agent service interface to generate a target subnet.

[0116] The specific details of the virtual modules of each network generation device and interface acquisition device mentioned above have been described in detail in the corresponding network generation method and interface acquisition method. For any undisclosed details, please refer to the implementation method in the method section, and therefore will not be repeated here.

[0117] It should be noted that although several modules or units of the network generation apparatus and interface acquisition apparatus have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0118] Exemplary embodiments of this disclosure also provide a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the network generation method or interface acquisition method described above.

[0119] In one implementation, the computer program product may be a tangible product containing a computer program, such as a computer-readable storage medium storing the computer program. (See reference...) Figure 12 , Figure 12 The schematic diagram illustrates a computer-readable storage medium 1200 according to an exemplary embodiment of the present disclosure. The computer-readable storage medium 1200 can be a storage medium based on electrical, magnetic, optical, electromagnetic, infrared, or other signals, including but not limited to: random access memory (RAM), read-only memory (ROM), magnetic tape, floppy disk, flash memory, hard disk drive (HDD), solid-state drive (SSD), etc. Exemplarily, a computer program product can be implemented as a non-volatile storage medium storing a computer program, such as read-only memory, NAND flash memory, etc.

[0120] In one implementation, the computer program product can be an intangible product containing a computer program. For example, the computer program product can be implemented as a virtual digital product, such as an executable file, installation package, or other digital file storing the computer program.

[0121] Computer program code can be written in one or more programming languages. Examples of programming languages ​​include C, Java, and C++. Program code can execute entirely on the user's computing device, partially on the user's computing device, or as a standalone software package. It can also execute partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, such as a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via an internet connection provided by a mobile network operator).

[0122] Computer programs can be carried or transmitted via signals such as electrical, magnetic, optical, electromagnetic, and infrared rays. Electronic devices can convert the signals carrying computer programs into digital signals, thereby running the computer programs. When a computer program runs on an electronic device, its code is used to cause the electronic device to execute (more specifically, the processor of the electronic device to execute) the method steps of various exemplary embodiments of this disclosure, such as the network generation method and interface acquisition method described above.

[0123] Exemplary embodiments of this disclosure also provide an electronic device, which may include a processor and a memory. The memory stores executable instructions of the processor, such as a computer program. The processor executes the executable instructions to perform the method steps of various exemplary embodiments of this disclosure. Furthermore, the electronic device may also include a display for displaying a graphical user interface.

[0124] The following is for reference. Figure 13 The electronic device is illustrated by way of a general-purpose computing device. It should be understood that... Figure 13 The electronic device 1300 shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0125] like Figure 13 As shown, the electronic device 1300 may include: a processor 1310, a memory 1320, a bus 1330, an I / O (input / output) interface 1340, a network adapter 1350, and a display 1360.

[0126] Memory 1320 may include volatile memory, such as RAM 1321 and cache unit 1322, and may also include non-volatile memory, such as ROM 1323. Memory 1320 may also include one or more program modules 1324, such program modules 1324 including, but not limited to: operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. For example, program module 1324 may include the modules in the above-described apparatus.

[0127] The processor 1310 may include one or more processing units, such as an AP (Application Processor), a modem processor, a GPU (Graphics Processing Unit), an ISP (Image Signal Processor), a controller, an encoder, a decoder, a DSP (Digital Signal Processor), a baseband processor, and / or an NPU (Neural-Network Processing Unit).

[0128] The processor 1310 can be used to execute executable instructions stored in the memory 1320, such as the network generation method or interface acquisition method described above.

[0129] Bus 1330 is used to connect different components of electronic device 1300 and may include a data bus, an address bus and a control bus.

[0130] Electronic device 1300 can communicate with one or more external devices 1400 (such as keyboard, mouse, external controller, etc.) through I / O interface 1340.

[0131] Electronic device 1300 can communicate with one or more networks via network adapter 1350. For example, network adapter 1350 can provide mobile communication solutions such as 3G / 4G / 5G, or wireless communication solutions such as wireless LAN, Bluetooth, and near-field communication. Network adapter 1350 can communicate with other modules of electronic device 1300 via bus 1330.

[0132] although Figure 13 As not shown in the diagram, other hardware and / or software modules may also be configured in the electronic device 1300, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0133] As can be seen from the above, the technical solutions disclosed herein can be implemented as methods, apparatus, systems, computer program products, storage media, electronic devices, etc. Those skilled in the art will understand that various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software aspects, which may be referred to as "circuit," "module," or "system," respectively.

[0134] It should be understood that this disclosure is not limited to the specific methods, steps, or structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. Those skilled in the art will readily conceive of other embodiments based on the specific implementations provided in this disclosure. Therefore, the specific implementations provided in this disclosure are merely exemplary, and the scope and spirit of this disclosure are indicated by the claims, and should cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary technical means in the art not disclosed in this disclosure.

Claims

1. A network generation method, characterized in that, The method, applied to an agent instance in an agent network architecture, includes: In response to a subnet generation request sent by a terminal, the subnet generation request is processed for intent recognition to obtain the subnet generation intent. The subnet generation request is sent through a pre-acquired target agent service interface. Determine the subnet generation parameters corresponding to the subnet generation intention, and return the subnet generation parameters to the terminal; A network configuration file is generated based on the subnet generation parameters confirmed by the terminal. The network configuration file is used by the management and network orchestration system to configure and generate the target subnet.

2. The method according to claim 1, characterized in that, The agent network architecture includes agent management functions, and the method further includes: The agent management function receives an agent registration request sent by the agent instance. The agent registration request includes one or more of the following: agent instance identifier, agent instance function, description of available tools, service area, and service call interface. Based on the agent registration request, determine and store the registration authentication result of the agent instance; Return the registration and authentication result to the agent instance.

3. The method according to claim 1, characterized in that, The subnet generation request sent by the terminal is responded to by performing intent recognition processing on the subnet generation request to obtain the subnet generation intent, including: Receive the subnet generation request sent by the terminal based on the target intelligent agent service interface; The subnet generation request is subjected to intent recognition processing to obtain an initial subnet generation intent, which includes initial network parameter information; Send the initial network parameter information to the terminal; Based on the network parameter change intent sent by the terminal, the initial network parameter information is updated to obtain the target network parameter information, which includes subnet generation parameters.

4. The method according to claim 3, characterized in that, The target intelligent agent service interface is obtained through the following steps: Receive a service interface acquisition request sent by the mobility and session management function, the service interface acquisition request being generated based on a session establishment request between the terminal and the agent domain. Determine the interface request acquisition result corresponding to the service interface acquisition request, wherein the interface request acquisition result includes the encoded target intelligent agent service interface; The interface request result is sent to the mobile and session management function, so that the mobile and session management function can send the interface request result to the terminal.

5. The method according to claim 4, characterized in that, The session establishment request includes an agent service request identifier, and determining the interface request acquisition result corresponding to the service interface acquisition request includes: Obtain the terminal identifier corresponding to the terminal; Based on the terminal identifier and the intelligent agent service demand identifier, a retrieval operation is performed on the user data management function to determine the service signing status of the terminal in the target intelligent agent service. Perform an internal query to determine the agent registration information of the target agent; Based on the service signing status and the agent registration content, the target agent service interface response is determined, and the target agent service interface response is used to generate the interface request result.

6. The method according to claim 1, characterized in that, The process of generating a network configuration file based on the subnet generation parameters confirmed by the terminal includes: Receive parameter confirmation request initiated by the terminal; Obtain a predefined network configuration template, fill the subnet generation parameters into the network configuration template, and generate the network configuration file; The network configuration file is sent to the management and network orchestration system through the management and network orchestration interface. The network configuration file is used by the management and network orchestration system to perform subnet deployment operations.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Receive a subnet generation success response from the management and network orchestration system; A subnet generation success response is sent to the terminal so that the terminal can access the target subnet based on the subnet generation success response.

8. A method for obtaining an interface, characterized in that, Applied to a central network, the method includes: The receiving terminal sends a session establishment request with the agent domain, the session establishment request including an agent service type identifier written into the non-access stratum message; Based on the session establishment request, the session establishment process is executed, and the service type identifier of the intelligent agent is parsed to obtain the service interface acquisition request. Send a service interface acquisition request to the agent management function, and receive the target agent service interface returned by the agent management function; A session response message is sent to the terminal, the session response message including an encoded target agent service interface, so that the terminal can send a subnet generation request based on the target agent service interface to generate a target subnet.

9. The method according to claim 8, characterized in that, The non-access layer message includes a protocol configuration option field, which includes one or more of the following: agent service request indication, service request field length, and agent service request content.

10. A network generation apparatus, characterized in that, An agent instance applied to an agent network architecture, the device comprising: The intent recognition module is used to respond to the subnet generation request sent by the terminal, perform intent recognition processing on the subnet generation request to obtain the subnet generation intent, and send the subnet generation request through the pre-acquired target intelligent agent service interface; The subnet parameter generation module is used to determine the subnet generation parameters corresponding to the subnet generation intention and return the subnet generation parameters to the terminal. The subnet generation module is used to generate a network configuration file based on the subnet generation parameters confirmed by the terminal. The network configuration file is used by the management and network orchestration system to configure and generate the target subnet.

11. An interface acquisition device, characterized in that, Applied to a central network, the device includes: The session request sending module is used to receive a session establishment request sent by the terminal between the terminal and the agent domain. The session establishment request includes an agent service type identifier written into the non-access stratum message. The interface request determination module is used to execute the session establishment process based on the session establishment request, parse the service type identifier of the intelligent agent, and obtain the service interface acquisition request. The target interface determination module is used to send the service interface acquisition request to the agent management function and receive the target agent service interface returned by the agent management function. The session response module is used to send a session response message to the terminal. The session response message includes an encoded target agent service interface, so that the terminal can send a subnet generation request based on the target agent service interface to generate a target subnet.

12. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the network generation method as described in any one of claims 1 to 7, or the interface acquisition method as described in any one of claims 8 to 9.

13. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the network generation method as described in any one of claims 1 to 7, or the interface acquisition method as described in any one of claims 8 to 9.

Images