Agent subnet communication method, terminal, network function entity, apparatus and medium

Abstract

Provided in the present disclosure are an agent subnet communication method, a terminal, a network function entity, an apparatus, and a medium. The method comprises: an agent of a terminal sends an agent registration request message to a first network function entity, the agent registration request message being used for triggering creating an agent communication subnet; and the agent of the terminal performs communications between agents on the basis of the agent communication subnet.

Description

Intelligent entity network communication methods, terminals, network functional entities, devices and media

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411939976.5, filed on December 26, 2024, entitled “Intelligent Subnet Communication Method, Terminal, Network Functional Entity, Apparatus and Medium”, which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to the field of communication technology, and in particular to a smart body subnet communication method, terminal, network functional entity, device and medium. Background Technology

[0004] With the development of Artificial Intelligence (AI) technology, AI agents, as intelligent entities with autonomous learning and decision-making capabilities, will become the latest form of network communication object after humans and things. For user-centric multi-agent services, multiple agents need to collaborate through subnet communication; how to create these agent communication subnets is a technical problem that needs to be solved. Summary of the Invention

[0005] This disclosure provides a method, terminal, network functional entity, device, and medium for intelligent agent subnet communication, to solve the problem of creating an intelligent agent communication subnet.

[0006] In a first aspect, this disclosure provides an intelligent agent subnet communication method, applied to a terminal, comprising:

[0007] The terminal's intelligent agent sends an intelligent agent registration request message to the first network function entity. The intelligent agent registration request message is used to trigger the creation of an intelligent agent communication subnet.

[0008] The terminal's intelligent agents communicate with each other based on the intelligent agent communication subnet.

[0009] In some embodiments, the agent registration request message includes one or more of the following information:

[0010] Types of intelligent agents;

[0011] Administrator permission identifier, or administrator information to which the agent belongs;

[0012] Communication modes;

[0013] Communication interface;

[0014] Communication address;

[0015] Business scope;

[0016] Artificial intelligence (AI) capabilities;

[0017] Computational ability;

[0018] Location information;

[0019] Mobile information;

[0020] List of service interfaces;

[0021] List of members and authorization information of the intelligent agent communication subnet;

[0022] Agent communication subnet deletion policy;

[0023] The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

[0024] In some embodiments, the method further includes:

[0025] The terminal's intelligent agent receives an intelligent agent registration response message sent by the first network function entity. The intelligent agent registration response message includes one or more of the following information:

[0026] Intelligent agent identification;

[0027] Identifier for the intelligent agent communication subnet.

[0028] In some embodiments, communication between agents is performed based on an agent communication subnet, including:

[0029] Based on the business requirements of the intelligent agent, determine the target intelligent agent for communication;

[0030] Send a first control plane request message to the first network function entity, or send a user plane message to the user plane function entity;

[0031] The first control plane request message or user plane message is used to send interactive information to the target intelligent agent.

[0032] In some embodiments, the first control plane request message includes interaction information and one or more of the following:

[0033] The communication message type is either a subnet communication transparent message or a subnet group message;

[0034] Identification of the target intelligent agent.

[0035] In some embodiments, the user plane message includes interaction information and target address information for communication.

[0036] In some embodiments, the target address information is the address information of the target agent or the address information used to indicate the group messaging within the agent's communication subnet.

[0037] In some embodiments, the first network function entity is deployed in the core network or in an agent communication network independent of the core network.

[0038] In some embodiments, the first network function entity is deployed in the core network, including:

[0039] The first network function entity is deployed within the session management function entity; or...

[0040] The first network function entity is deployed in the access and mobility management function entity and the session management function entity, respectively; or,

[0041] The first network function entity, the access and mobility management function entity, and the session management function entity are jointly deployed in a single core network function entity; or...

[0042] The first network function entity is deployed independently in the core network.

[0043] Secondly, this disclosure also provides an intelligent agent subnet communication method, applied to a first network functional entity, including:

[0044] Receive agent registration request message sent by the agent on the receiving terminal;

[0045] Based on the agent registration request message, perform one or more of the following operations:

[0046] Create an agent communication subnet or add an agent to an existing agent communication subnet;

[0047] Record and maintain relevant information about the intelligent agent;

[0048] Assign an agent identifier to the agent;

[0049] Assign an agent communication subnet identifier to the created agent communication subnet.

[0050] In some embodiments, the agent registration request message includes one or more of the following information:

[0051] Types of intelligent agents;

[0052] Administrator privilege identifier, or the administrator information to which the agent belongs, or the agent's communication subnet identifier;

[0053] Communication modes;

[0054] Communication interface;

[0055] Communication address;

[0056] Business scope;

[0057] AI capabilities;

[0058] Computational ability;

[0059] Location information;

[0060] Mobile information;

[0061] List of service interfaces;

[0062] List of members and authorization information of the intelligent agent communication subnet;

[0063] Agent communication subnet deletion policy;

[0064] The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

[0065] In some embodiments, creating an agent communication subnet or adding an agent to an existing agent communication subnet includes:

[0066] If the user on the terminal has administrator privileges, create an intelligent agent communication subnet belonging to the terminal; or,

[0067] When the terminal user is not an administrator, the agent will be added to the created agent communication subnet.

[0068] In some embodiments, the method further includes:

[0069] Send an agent registration response message to the agent on the terminal. The agent registration response message includes one or more of the following information:

[0070] Intelligent agent identification;

[0071] Identifier for the intelligent agent communication subnet.

[0072] In some embodiments, the method further includes:

[0073] Create a group session for the created agent communication subnet and perform one or more of the following operations:

[0074] Assign group session identifier;

[0075] Update group session members;

[0076] Issue group-level session traffic forwarding rules to user plane functional entities.

[0077] In some embodiments, creating a group session for the created agent communication subnet includes:

[0078] For cases where the agent communication subnet is created after the user session is created, the creation of the group session is triggered after the agent communication subnet is created; or...

[0079] In the case of creating an agent communication subnet and then creating a user session, the creation of a group session is triggered after the user session is created.

[0080] In some embodiments, the method further includes:

[0081] Receive a first control plane request message sent by a first intelligent agent. The first control plane request message is used to send interactive information to the second intelligent agent.

[0082] Based on the request message from the first control plane, interactive information is sent to the second intelligent agent.

[0083] In some embodiments, the first control plane request message includes interaction information and one or more of the following:

[0084] The communication message type is either a subnet communication transparent message or a subnet group message;

[0085] The identifier of the second intelligent agent.

[0086] In some embodiments, the method further includes:

[0087] The receiving terminal sends a registration request message from the intelligent agent.

[0088] Based on the agent's registration request message, the agent's information is deleted from the member information of the agent's communication subnet.

[0089] In some embodiments, the method further includes:

[0090] When the terminal user has administrator privileges, the system determines whether to delete the intelligent agent communication subnet belonging to the terminal based on the intelligent agent communication subnet deletion policy.

[0091] In some embodiments, the method further includes:

[0092] The terminal sends a terminal deregistration request message, which triggers the terminal's intelligent agent to deregister, or updates the terminal's intelligent agent to an offline state.

[0093] Thirdly, this disclosure also provides a terminal, including a memory, a transceiver, and a processor;

[0094] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0095] The terminal's intelligent agent sends an intelligent agent registration request message to the first network function entity. The intelligent agent registration request message is used to trigger the creation of an intelligent agent communication subnet.

[0096] The terminal's intelligent agents communicate with each other based on the intelligent agent communication subnet.

[0097] In some embodiments, the agent registration request message includes one or more of the following information:

[0098] Types of intelligent agents;

[0099] Administrator permission identifier, or administrator information to which the agent belongs;

[0100] Communication modes;

[0101] Communication interface;

[0102] Communication address;

[0103] Business scope;

[0104] Artificial intelligence (AI) capabilities;

[0105] Computational ability;

[0106] Location information;

[0107] Mobile information;

[0108] List of service interfaces;

[0109] List of members and authorization information of the intelligent agent communication subnet;

[0110] Agent communication subnet deletion policy;

[0111] The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

[0112] In some embodiments, the operation further includes:

[0113] The terminal's intelligent agent receives an intelligent agent registration response message sent by the first network function entity. The intelligent agent registration response message includes one or more of the following information:

[0114] Intelligent agent identification;

[0115] Identifier for the intelligent agent communication subnet.

[0116] In some embodiments, communication between agents is performed based on an agent communication subnet, including:

[0117] Based on the business requirements of the intelligent agent, determine the target intelligent agent for communication;

[0118] Send a first control plane request message to the first network function entity, or send a user plane message to the user plane function entity;

[0119] The first control plane request message or user plane message is used to send interactive information to the target intelligent agent.

[0120] In some embodiments, the first control plane request message includes interaction information and one or more of the following:

[0121] The communication message type is either a subnet communication transparent message or a subnet group message;

[0122] Identification of the target intelligent agent.

[0123] In some embodiments, the user plane message includes interaction information and target address information for communication.

[0124] In some embodiments, the target address information is the address information of the target agent or the address information used to indicate the group messaging within the agent's communication subnet.

[0125] In some embodiments, the first network function entity is deployed in the core network or in an agent communication network independent of the core network.

[0126] In some embodiments, the first network function entity is deployed in the core network, including:

[0127] The first network function entity is deployed within the session management function entity; or...

[0128] The first network function entity is deployed in the access and mobility management function entity and the session management function entity, respectively; or,

[0129] The first network function entity, the access and mobility management function entity, and the session management function entity are jointly deployed in a single core network function entity; or...

[0130] The first network function entity is deployed independently in the core network.

[0131] Fourthly, this disclosure also provides a first network functional entity, including a memory, a transceiver, and a processor;

[0132] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0133] Receive agent registration request message sent by the agent on the receiving terminal;

[0134] Based on the agent registration request message, perform one or more of the following operations:

[0135] Create an agent communication subnet or add an agent to an existing agent communication subnet;

[0136] Record and maintain relevant information about the intelligent agent;

[0137] Assign an agent identifier to the agent;

[0138] Assign an agent communication subnet identifier to the created agent communication subnet.

[0139] In some embodiments, the agent registration request message includes one or more of the following information:

[0140] Types of intelligent agents;

[0141] Administrator privilege identifier, or the administrator information to which the agent belongs, or the agent's communication subnet identifier;

[0142] Communication modes;

[0143] Communication interface;

[0144] Communication address;

[0145] Business scope;

[0146] AI capabilities;

[0147] Computational ability;

[0148] Location information;

[0149] Mobile information;

[0150] List of service interfaces;

[0151] List of members and authorization information of the intelligent agent communication subnet;

[0152] Agent communication subnet deletion policy;

[0153] The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

[0154] In some embodiments, creating an agent communication subnet or adding an agent to an existing agent communication subnet includes:

[0155] If the user on the terminal has administrator privileges, create an intelligent agent communication subnet belonging to the terminal; or,

[0156] When the terminal user is not an administrator, the agent will be added to the created agent communication subnet.

[0157] In some embodiments, the operation further includes:

[0158] Send an agent registration response message to the agent on the terminal. The agent registration response message includes one or more of the following information:

[0159] Intelligent agent identification;

[0160] Identifier for the intelligent agent communication subnet.

[0161] In some embodiments, the operation further includes:

[0162] Create a group session for the created agent communication subnet and perform one or more of the following operations:

[0163] Assign group session identifier;

[0164] Update group session members;

[0165] Issue group-level session traffic forwarding rules to user plane functional entities.

[0166] In some embodiments, creating a group session for the created agent communication subnet includes:

[0167] For cases where the agent communication subnet is created after the user session is created, the creation of the group session is triggered after the agent communication subnet is created; or...

[0168] In the case of creating an agent communication subnet and then creating a user session, the creation of a group session is triggered after the user session is created.

[0169] In some embodiments, the operation further includes:

[0170] Receive a first control plane request message sent by a first intelligent agent. The first control plane request message is used to send interactive information to the second intelligent agent.

[0171] Based on the request message from the first control plane, interactive information is sent to the second intelligent agent.

[0172] In some embodiments, the first control plane request message includes interaction information and one or more of the following:

[0173] The communication message type is either a subnet communication transparent message or a subnet group message;

[0174] The identifier of the second intelligent agent.

[0175] In some embodiments, the operation further includes:

[0176] The receiving terminal sends a registration request message from the intelligent agent.

[0177] Based on the agent's registration request message, the agent's information is deleted from the member information of the agent's communication subnet.

[0178] In some embodiments, the operation further includes:

[0179] When the terminal user has administrator privileges, the system determines whether to delete the intelligent agent communication subnet belonging to the terminal based on the intelligent agent communication subnet deletion policy.

[0180] In some embodiments, the operation further includes:

[0181] The terminal sends a terminal deregistration request message, which triggers the terminal's intelligent agent to deregister, or updates the terminal's intelligent agent to an offline state.

[0182] Fifthly, this disclosure also provides an intelligent agent subnet communication device, comprising:

[0183] The registration unit is used for the terminal's intelligent agent to send an intelligent agent registration request message to the first network function entity. The intelligent agent registration request message is used to trigger the creation of an intelligent agent communication subnet.

[0184] The communication unit is used by the terminal's intelligent agents to communicate with each other based on the intelligent agent communication subnet.

[0185] Sixthly, this disclosure also provides an intelligent agent subnet communication device, comprising:

[0186] The receiving unit is used to receive the agent registration request message sent by the agent of the terminal;

[0187] The execution unit is used to perform one or more of the following operations based on the agent registration request message:

[0188] Create an agent communication subnet or add an agent to an existing agent communication subnet;

[0189] Record and maintain relevant information about the intelligent agent;

[0190] Assign an agent identifier to the agent;

[0191] Assign an agent communication subnet identifier to the created agent communication subnet.

[0192] In a seventh aspect, this disclosure also provides a non-transiently readable storage medium storing a program for causing a processor to execute the intelligent agent subnet communication method as described in the first aspect above, or to execute the intelligent agent subnet communication method as described in the second aspect above.

[0193] Eighthly, this disclosure also provides a communication device that stores a program for causing the communication device to execute the intelligent agent subnet communication method as described in the first aspect above, or to execute the intelligent agent subnet communication method as described in the second aspect above.

[0194] Ninthly, this disclosure also provides a processor-readable storage medium storing a program for causing a processor to execute the intelligent agent subnet communication method as described in the first aspect above, or to execute the intelligent agent subnet communication method as described in the second aspect above.

[0195] In a tenth aspect, this disclosure also provides a chip product storing a program for causing the chip product to execute the intelligent agent subnet communication method as described in the first aspect above, or to execute the intelligent agent subnet communication method as described in the second aspect above.

[0196] The intelligent agent subnet communication method, terminal, network functional entity, device and medium provided in this disclosure can improve the flexibility of users in managing intelligent agent communication subnets and improve resource utilization efficiency by triggering the creation of intelligent agent communication subnets through intelligent agent registration requests. Attached Figure Description

[0197] To more clearly illustrate the technical solutions in the embodiments or related technologies of this disclosure, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0198] Figure 1 is one of the flowcharts of the intelligent agent subnet communication method provided in the embodiments of this disclosure.

[0199] Figure 2 is one of the network architecture examples for deploying the intelligent agent management function entity provided in the embodiments of this disclosure.

[0200] Figure 3 is a second example of the network architecture for deploying the intelligent agent management function entity provided in the embodiments of this disclosure.

[0201] Figure 4 is a second schematic flowchart of the intelligent agent subnet communication method provided in this embodiment of the present disclosure.

[0202] Figure 5 is a flowchart of Example 1 provided in the embodiments of this disclosure.

[0203] Figure 6 is a flowchart of Example 2 provided in the embodiments of this disclosure.

[0204] Figure 7 is a flowchart of Example 3 provided in the embodiments of this disclosure.

[0205] Figure 8 is a flowchart of Example 5 provided in the embodiments of this disclosure.

[0206] Figure 9 is a flowchart of Example 6 provided in the embodiments of this disclosure.

[0207] Figure 10 is a schematic diagram of the structure of the terminal provided in the embodiment of this disclosure.

[0208] Figure 11 is a schematic diagram of the structure of the first network functional entity provided in an embodiment of this disclosure.

[0209] Figure 12 is one of the structural schematic diagrams of the intelligent body subnet communication device provided in the embodiments of this disclosure.

[0210] Figure 13 is a second schematic diagram of the structure of the intelligent body subnet communication device provided in the embodiments of this disclosure. Detailed Implementation

[0211] In this disclosure, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0212] In this disclosure, the term "multiple" refers to two or more, and other quantifiers are similar.

[0213] In the embodiments of this disclosure, the terms "first," "second," etc., are used to distinguish similar objects and are not used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this disclosure can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, and the number of objects is not limited; for example, the first object can be one or more.

[0214] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0215] To facilitate a clearer understanding of the technical solutions of the embodiments of this disclosure, some technical content related to the embodiments of this disclosure will be introduced first.

[0216] 1. Intelligent Agent (AI Agent)

[0217] An AI Agent is an intelligent entity capable of perceiving its environment, making decisions, and executing actions. Unlike traditional artificial intelligence, an AI Agent possesses the ability to independently think and utilize tools to gradually achieve a given goal.

[0218] The core features of AI Agents include:

[0219] (1) Autonomy: AI Agents have the ability to think and act independently and can complete tasks without direct human guidance.

[0220] (2) Interactivity: AI Agents can interact with the environment or other Agents.

[0221] (3) Purposefulness: AI Agents are designed with clear goals or intentions, and their behavior is to achieve these goals.

[0222] (4) Adaptability: AI Agents can adjust their behavior according to changes in the environment to adapt to new situations.

[0223] (5) Evolution: With the development of technology, the functions and intelligence level of AI Agents are constantly improving.

[0224] 2. Intelligent agent communication network (or intelligent agent communication subnet, communication subnet, subnet, etc.)

[0225] Intelligent agent communication networks are a new type of network service for communication between various intelligent agents. They aim to provide interconnected, on-demand empowerment, secure and controllable information interaction and task collaboration networks for intelligent agents of different forms (physical or virtual), various capability levels (from high-end to low-end), and different user groups.

[0226] Although the intelligent agent communication network is a dedicated network for intelligent agent communication, it is still user-centric, with each intelligent agent belonging to a specific individual or enterprise user.

[0227] In related technologies, users are supported in creating user-level intelligent agent communication subnets based on contracts. However, if an intelligent agent communication subnet is created based on a "contract," then each intelligent agent (physical or virtual form) needs to be contracted with an operator to belong to a particular user. In a more practical situation, intelligent agents (physical or virtual forms) may be transferable, for example, gifted from user A to user B. If the user who changes the ownership of an intelligent agent is rigidly bound to a contract, it is not conducive to the user's flexible control over their own intelligent agents. At the same time, the intelligent agents may not be put into use immediately after the contract is signed, and directly creating an intelligent agent communication subnet for them would be a waste of resources.

[0228] The solutions provided in the embodiments of this disclosure trigger the creation of a user-level intelligent agent communication subnet by having a user with intelligent agent administrator privileges register an AI Agent. The network adds functions such as intelligent agent registration management and intelligent agent group-level session management to meet the communication needs of the intelligent agent subnet.

[0229] Figure 1 is a flowchart of one of the intelligent agent subnet communication methods provided in this embodiment of the present disclosure. The method is applied to a terminal (User Equipment, UE). As shown in Figure 1, the method includes the following steps 101 and 102.

[0230] Step 101: The terminal's intelligent agent sends an intelligent agent registration request message to the first network function entity. The intelligent agent registration request message is used to trigger the creation of an intelligent agent communication subnet.

[0231] Step 102: The terminal's agents communicate with each other based on the agent communication subnet.

[0232] Specifically, the first network function entity includes one or more network function entities involved in agent management, such as access and mobility management function entities, session management function entities, agent management function entities, etc.

[0233] Taking the newly added intelligent agent management function entity responsible for intelligent agent management as an example, the intelligent agent of the terminal can send an intelligent agent registration request message to the access and mobility management function entity (for example, the intelligent agent registration request message is an extended terminal registration message, which carries intelligent agent registration request information), and then the access and mobility management function entity forwards the intelligent agent registration request message to the intelligent agent management function entity; or, the intelligent agent of the terminal can send an intelligent agent registration request message to the session management function entity (for example, the intelligent agent registration request message is an extended terminal session message, which carries intelligent agent registration request information), and then the session management function entity forwards the intelligent agent registration request message to the intelligent agent management function entity; or, the intelligent agent of the terminal can send an independent intelligent agent registration request message to the intelligent agent management function entity.

[0234] Upon receiving the agent registration request message, the first network function entity checks whether the agent communication subnet associated with the agent has been created and whether the terminal has administrator privileges. If the agent communication subnet associated with the agent has not yet been created and the terminal is a user with administrator privileges, then the creation of the agent communication subnet belonging to the terminal is triggered. Subsequently, the agents of the terminal communicate with each other based on the agent communication subnet.

[0235] The intelligent agent subnet communication method provided in this disclosure can improve the flexibility of user management of intelligent agent communication subnets and improve resource utilization efficiency by triggering the creation of intelligent agent communication subnets through intelligent agent registration requests.

[0236] Figures 2 and 3 illustrate two different network architectures for deploying intelligent agent management functional entities. To facilitate understanding of the technical solutions disclosed herein, the relevant technical terms involved in this disclosure will be explained below in conjunction with Figures 2 and 3.

[0237] Administrator: refers to the administrator terminal to which the intelligent agent belongs. As shown in Figure 2, intelligent agent 1 of UE1, intelligent agent 2 of UE2, and intelligent agent 3 of UE3 all belong to UE1, while intelligent agent 4 of UE4 and intelligent agent 5 of UE5 all belong to UE4. The intelligent agents of different UEs can be divided into different communication subnets according to the different administrators they belong to.

[0238] Access methods: Terminals can access the core network in different ways, as shown in Figure 2. UE1, UE2, and UE4 access the core network in the mobile access mode, while UE3 and UE5 access the core network in the fixed access mode. Regardless of the access method (mobile access, fixed access, etc.), the UE can support intelligent body subnet communication through the network.

[0239] AAMF: AI Agent Management Function (AAMF) entity. By adding AAMF to the network, it is responsible for agent registration management, agent session management, agent empowerment and collaboration support, security and trust management, etc., to provide key functions for agents to communicate in the subnet. In Figure 2, AAMF is deployed in the core network. In Figure 3, AAMF is not deployed in the core network, but is deployed separately on the network side as an agent communication network.

[0240] When the AAMF is deployed independently as an agent communication network, all messages sent by the UE to the AAMF are forwarded to the AAMF by the core network user plane function entity, and the destination address of the message is the AAMF's communication address. Similarly, all messages sent by the AAMF to the UE are forwarded to the UE by the core network user plane function entity, and the source address of the message is the AAMF's communication address. The AAMF's communication address information can be provided to the UE by the core network before the UE sends an agent registration request message. For example, the core network's policy control function entity selects a suitable AAMF for the UE's agent and notifies the UE of the AAMF's communication address information from the core network.

[0241] MM: Access and Mobility Management Function entity.

[0242] SM: Session Management Function entity.

[0243] UPF+: Enhanced User Plane Function (UPF) entity.

[0244] UDM+: Enhanced Unified Data Management (UDM) entity.

[0245] NRF+: Enhanced Network Repository Function (NRF) entity.

[0246] PCF+: Enhanced Policy Control Function (PCF) entity.

[0247] By enhancing network elements such as NRF, UDM, UPF, and PCF in the network to support agent-related functions, it supports agent subnet communication.

[0248] In some embodiments, the agent registration request message includes one or more of the following information:

[0249] Types of intelligent agents;

[0250] Administrator permission identifier, or administrator information to which the agent belongs;

[0251] Communication modes;

[0252] Communication interface;

[0253] Communication address;

[0254] Business scope;

[0255] AI capabilities;

[0256] Computational ability;

[0257] Location information;

[0258] Mobile information;

[0259] List of service interfaces;

[0260] List of members and authorization information of the intelligent agent communication subnet;

[0261] Agent communication subnet deletion policy;

[0262] The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

[0263] Information on intelligent agent types includes, for example, personal AI agents and enterprise AI agents.

[0264] Information about the communication interface may include, for example, whether it supports the control plane, the user plane, or both.

[0265] Communication address information includes, for example, IP address, URI, port, address prefix, or interface identifier. If this communication address information is not included, the network can directly use the UE's address as the agent's communication address. IP refers to the Internet Protocol (IP), and URI refers to the Uniform Resource Identifier (URI).

[0266] Motion information includes, for example, being stationary or having a range of movement speed.

[0267] In some embodiments, the method further includes:

[0268] The terminal's intelligent agent receives an intelligent agent registration response message sent by the first network function entity. The intelligent agent registration response message includes one or more of the following information:

[0269] Intelligent agent identification;

[0270] Identifier for the intelligent agent communication subnet.

[0271] For example, after receiving a registration request message from an agent, the first network functional entity can assign a corresponding identifier (ID) to the agent, and then return the agent's identifier to the agent in the agent registration response message. The agent's ID is unique within the agent communication subnet or globally unique, and is mainly used to identify the communication object when communicating within the subnet.

[0272] For example, after receiving the agent registration request message, the first network functional entity triggers the creation of the agent communication subnet and assigns the agent communication subnet identifier. Then, it can carry the agent communication subnet identifier in the agent registration response message and return it to the agent.

[0273] For example, after receiving the agent registration request message, if the agent communication subnet associated with the agent has been created and the agent communication subnet identifier has been assigned, the first network function entity can return the agent communication subnet identifier to the agent in the agent registration response message.

[0274] In some embodiments, communication between agents is performed based on an agent communication subnet, including:

[0275] Based on the business requirements of the intelligent agent, determine the target intelligent agent for communication;

[0276] Send a first control plane request message to the first network function entity, or send a user plane message to the user plane function entity;

[0277] The first control plane request message or user plane message is used to send interactive information to the target intelligent agent.

[0278] For example, an intelligent agent can query a first network function entity for other intelligent agents that can meet its business needs. Based on the agent's query request, the first network function entity selects a suitable target intelligent agent within the intelligent agent communication subnet associated with that agent and notifies the agent that initiated the query of the target intelligent agent's information. Alternatively, an intelligent agent can subscribe to information about each intelligent agent within its associated intelligent agent communication subnet from the first network function entity and determine the target intelligent agent for communication based on the information of each intelligent agent and its business needs.

[0279] Once the target agent is identified, interaction can be performed through the control plane or the user plane. It should be noted that there can be one or more target agents, and the interaction information can be sent to multiple target agents or sent to a single (or several) target agents; this disclosure does not impose any limitations.

[0280] In cases where interactive information is transmitted through the control plane interface, the agent can send a first control plane request message to the first network function entity, which will then forward the interactive information to the target agent.

[0281] In some embodiments, the first control plane request message includes interaction information and one or more of the following:

[0282] The communication message type is either a subnet communication transparent message or a subnet group message;

[0283] Identification of the target intelligent agent.

[0284] For example, if the interactive information is sent to agents within the agent communication subnet, the first control plane request message may carry the interactive information as well as the information that "the communication message type is a subnet group message". After receiving the first control plane request message, the first network function entity determines that the interactive information needs to be sent to agents within the agent communication subnet, and then sends the interactive information to the agents within the agent communication subnet respectively.

[0285] For example, the interaction information is not sent in bulk. The first control plane request message may carry interaction information and the information that "the communication message type is subnet communication transparent message". It may also carry the identifier of the target intelligent agent. After receiving the first control plane request message, the first network function entity determines the target intelligent agent to forward it and then sends the interaction information to the target intelligent agent.

[0286] When transmitting interactive information through the user plane interface, the agent can send a user plane message to the user plane functional entity, which will then forward the interactive information to the target agent.

[0287] In some embodiments, the user plane message includes interaction information and target address information for communication.

[0288] In some embodiments, the target address information is the address information of the target agent or the address information used to indicate the group messaging within the agent's communication subnet.

[0289] For example, if the interaction information is sent to agents within the agent communication subnet, the user plane message can carry address information indicating the group message to be sent within the agent communication subnet, such as group multicast / broadcast address information. This address information can be an IP address, port number, etc., and there are no specific restrictions.

[0290] For example, if the interaction information is not sent to multiple people, the user-face message can carry the address information of the target agent.

[0291] In some embodiments, the first network function entity is deployed in the core network (as shown in Figure 2) or in an agent communication network independent of the core network (as shown in Figure 3).

[0292] In some embodiments, the first network function entity is deployed in the core network, including:

[0293] (1) The first network function entity is deployed on the session management function entity.

[0294] For example, taking Figure 2 as an example, the functions corresponding to AAMF can all be deployed in SM, without the need to add AAMF as a separate network function. The related functions or processes handled by AAMF are all completed by SM.

[0295] (2) The first network function entity is deployed in the access and mobility management function entity and the session management function entity, respectively.

[0296] For example, taking Figure 2 as an example, the agent registration function and the agent communication subnet creation function are deployed in MM, and the group session function is deployed in SM.

[0297] (3) The first network function entity, the access and mobility management function entity, and the session management function entity are deployed together in a core network function entity.

[0298] For example, the functions corresponding to AAMF, MM, and SM can be deployed together in a single core network function.

[0299] (4) The first network function entity is deployed independently in the core network. As shown in Figure 2, AMF can be deployed as an independent network function in the core network.

[0300] Figure 4 is a second flowchart of the intelligent agent subnet communication method provided in this embodiment of the present disclosure. The method is applied to a first network functional entity. As shown in Figure 4, the method includes the following steps 401 and 402.

[0301] Step 401: Receive the agent registration request message sent by the agent of the terminal.

[0302] Step 402: Based on the agent registration request message, perform one or more of the following operations:

[0303] Create an agent communication subnet or add an agent to an existing agent communication subnet;

[0304] Record and maintain relevant information about the intelligent agent;

[0305] Assign an agent identifier to the agent;

[0306] Assign an agent communication subnet identifier to the created agent communication subnet.

[0307] Specifically, the first network function entity includes one or more network function entities involved in agent management, such as access and mobility management function entities, session management function entities, agent management function entities, etc.

[0308] Taking the newly added intelligent agent management function entity responsible for intelligent agent management as an example, the intelligent agent of the terminal can send an intelligent agent registration request message to the access and mobility management function entity (for example, the intelligent agent registration request message is an extended terminal registration message, which carries intelligent agent registration request information), and then the access and mobility management function entity forwards the intelligent agent registration request message to the intelligent agent management function entity; or, the intelligent agent of the terminal can send an intelligent agent registration request message to the session management function entity (for example, the intelligent agent registration request message is an extended terminal session message, which carries intelligent agent registration request information), and then the session management function entity forwards the intelligent agent registration request message to the intelligent agent management function entity; or, the intelligent agent of the terminal can send an independent intelligent agent registration request message to the intelligent agent management function entity.

[0309] The intelligent agent subnet communication method provided in this embodiment allows a first network functional entity to perform one or more operations, such as creating an intelligent agent communication subnet, adding an intelligent agent to an existing intelligent agent communication subnet, recording and maintaining relevant information of the intelligent agent, assigning an intelligent agent identifier to the intelligent agent, and assigning an intelligent agent communication subnet identifier to the created intelligent agent communication subnet, after receiving an intelligent agent registration request message. This supports intelligent agent subnet communication, and the creation of the intelligent agent communication subnet is triggered by the intelligent agent registration request, which can improve the flexibility of user management of intelligent agent communication subnets and improve resource utilization efficiency.

[0310] In some embodiments, the agent registration request message includes one or more of the following information:

[0311] Types of intelligent agents;

[0312] Administrator privilege identifier, or the administrator information to which the agent belongs, or the agent's communication subnet identifier;

[0313] Communication modes;

[0314] Communication interface;

[0315] Communication address;

[0316] Business scope;

[0317] AI capabilities;

[0318] Computational ability;

[0319] Location information;

[0320] Mobile information;

[0321] List of service interfaces;

[0322] List of members and authorization information of the intelligent agent communication subnet;

[0323] Agent communication subnet deletion policy;

[0324] The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

[0325] If the agent to which the agent initiating the registration request belongs has already created an agent communication subnet, and the agent initiating the registration request has obtained the identifier of that agent communication subnet, then the agent registration request can be initiated through the "agent communication subnet identifier," thereby avoiding the security risks caused by directly carrying the administrator's identity identifier.

[0326] In some embodiments, creating an agent communication subnet or adding an agent to an existing agent communication subnet includes:

[0327] If the user on the terminal has administrator privileges, create an intelligent agent communication subnet belonging to the terminal; or,

[0328] When the terminal user is not an administrator, the agent will be added to the created agent communication subnet.

[0329] Taking Figure 2 as an example, UE1 is an administrator user. After agent 1 of UE1 initiates an agent registration request, the first network function entity checks whether the agent communication subnet associated with agent 1 has been created and whether UE1 has administrator privileges. If the agent communication subnet associated with agent 1 has not yet been created and UE1 is an administrator user, then the creation of the agent communication subnet belonging to UE1 is triggered.

[0330] For example, if UE2 is an administrator user, after agent 2 of UE2 initiates an agent registration request, the first network function entity checks whether the agent communication subnet associated with agent 2 has been created and whether UE2 has administrator privileges. If the agent communication subnet associated with agent 2 has been created and UE2 is not an administrator user, agent 2 can be added to the created agent communication subnet (belonging to the agent communication subnet of UE1).

[0331] In some embodiments, the method further includes:

[0332] Send an agent registration response message to the agent on the terminal. The agent registration response message includes one or more of the following information:

[0333] Intelligent agent identification;

[0334] Identifier for the intelligent agent communication subnet.

[0335] For example, after receiving the agent registration request message, the first network functional entity can assign a corresponding ID to the agent and then return the agent identifier to the agent in the agent registration response message.

[0336] For example, after receiving the agent registration request message, the first network functional entity triggers the creation of the agent communication subnet and assigns the agent communication subnet identifier. Then, it can carry the agent communication subnet identifier in the agent registration response message and return it to the agent.

[0337] For example, after receiving the agent registration request message, if the agent communication subnet associated with the agent has been created and the agent communication subnet identifier has been assigned, the first network function entity can return the agent communication subnet identifier to the agent in the agent registration response message.

[0338] In some embodiments, the method further includes:

[0339] Create a group session for the created agent communication subnet and perform one or more of the following operations:

[0340] Assign group session identifier;

[0341] Update group session members;

[0342] Issue group-level session traffic forwarding rules to user plane functional entities.

[0343] Specifically, the agent communication subnet enables communication between members within the subnet by creating "group sessions". After the agent communication subnet is created, the first network function entity creates a group session for the agent communication subnet and performs one or more operations such as assigning group session identifiers, updating group session members, and issuing traffic forwarding rules for group-level sessions to the user plane function entity.

[0344] It should be noted that the "Agent Communication Subnet Identifier" is used to notify the UE side, so that UEs within the same agent communication subnet can intuitively obtain this information and provide it to users or third parties. The "Group Session Identifier," on the other hand, is only used for internal network management of subnet communication. A mapping relationship may exist between the "Agent Communication Subnet Identifier" and the "Group Session Identifier."

[0345] The creation of group sessions and the assignment of group session identifiers, updating group session members, and issuing traffic forwarding rules for group-level sessions to user plane functional entities, or one or more of these operations, can be performed by the agent management functional entity or the session management functional entity.

[0346] In some embodiments, creating a group session for the created agent communication subnet includes:

[0347] For cases where the agent communication subnet is created after the user session is created, the creation of the group session is triggered after the agent communication subnet is created; or...

[0348] In the case of creating an agent communication subnet and then creating a user session, the creation of a group session is triggered after the user session is created.

[0349] Specifically, in this embodiment of the disclosure, the creation or update of a group session can be triggered independently of agent registration after the user session is created, or the agent can trigger the creation or update of a group session after the user registration and user session creation are completed.

[0350] For example, after UE1 completes user registration and user session creation, UE1's agent 1 initiates an agent registration request. The first network function entity creates an agent communication subnet belonging to UE1 based on the agent registration request message of agent 1, and then triggers a group session to create the agent communication subnet.

[0351] For example, after UE1 completes user registration, Agent 1 of UE1 initiates an agent registration request. Based on Agent 1's agent registration request message, the first network function entity creates an agent communication subnet belonging to UE1. At this point, the creation of the group session for this agent communication subnet is not triggered. Instead, the group session creation is triggered after UE1 completes user session creation. In this case, the session management function entity can uniformly perform session-related management operations, including group session creation, assigning group session identifiers, updating group session members, and issuing group-level session traffic forwarding rules to the user plane function entity.

[0352] In some embodiments, the method further includes:

[0353] Receive a first control plane request message sent by a first intelligent agent. The first control plane request message is used to send interactive information to the second intelligent agent.

[0354] Based on the request message from the first control plane, interactive information is sent to the second intelligent agent.

[0355] Specifically, the first and second agents can be any agents communicating within the agent subnet, and there are no restrictions on this. There can be one or more second agents, and the interaction information can be sent in groups or sent to a single (or several) second agents, and there are no restrictions on this.

[0356] When the first intelligent agent sends interactive information to the second intelligent agent, the first intelligent agent can send the interactive information to the second intelligent agent through the control plane or the user plane.

[0357] In cases where interactive information is transmitted through the control plane interface, the first intelligent agent can send a first control plane request message to the first network function entity, which will then forward the interactive information to the second intelligent agent.

[0358] In some embodiments, the first control plane request message includes interaction information and one or more of the following:

[0359] The communication message type is either a subnet communication transparent message or a subnet group message;

[0360] The identifier of the second intelligent agent.

[0361] For example, if the interactive information is sent to agents within the agent communication subnet, the first control plane request message may carry the interactive information as well as the information that "the communication message type is a subnet group message". After receiving the first control plane request message, the first network function entity determines that the interactive information needs to be sent to agents within the agent communication subnet, and then sends the interactive information to the agents within the agent communication subnet respectively.

[0362] For example, the interaction information is not sent in bulk. The first control plane request message may carry interaction information and the information that "the communication message type is subnet communication transparent message". It may also carry the identifier of the second agent. After receiving the first control plane request message, the first network function entity determines the second agent to forward it and then sends the interaction information to the second agent.

[0363] In cases where interactive information is transmitted through the user plane interface, the first intelligent agent can send a user plane message to the user plane functional entity, which will then forward the interactive information to the second intelligent agent.

[0364] In some embodiments, the user plane message includes interaction information and target address information for communication. The target address information is the address information of the second agent or the address information used to instruct the agent to send mass messages within the communication subnet.

[0365] For example, if the interaction information is sent to agents within the agent communication subnet, the user plane message can carry address information indicating the group message to be sent within the agent communication subnet, such as group multicast / broadcast address information. This address information can be an IP address, port number, etc., and there are no specific restrictions.

[0366] For example, if the interaction information is not sent to multiple people, the user-face message can carry the address information of the second agent.

[0367] In some embodiments, the method further includes:

[0368] The receiving terminal sends a registration request message from the intelligent agent.

[0369] Based on the agent's registration request message, the agent's information is deleted from the member information of the agent's communication subnet.

[0370] The deregistration of an agent can be triggered by the agent on the terminal sending an agent deregistration request message to the first network function entity. The method for sending the agent deregistration request message can be the same as that for sending the agent registration request message described above, and will not be repeated here.

[0371] After receiving the agent's registration request message, the first network functional entity can delete the agent's information from the agent's communication subnet member information.

[0372] In some embodiments, the method further includes:

[0373] When the terminal user has administrator privileges, the system determines whether to delete the intelligent agent communication subnet belonging to the terminal based on the intelligent agent communication subnet deletion policy.

[0374] The agent communication subnet deletion strategy includes, for example, one or more of the following:

[0375] Delete the agent communication subnet according to the duration or deadline (e.g., delete the agent communication subnet after a certain duration or deadline is reached).

[0376] Determine whether to delete the agent communication subnet based on whether there are registered agent members in the subnet (e.g., if there are no registered agent members in the subnet, then delete the agent communication subnet).

[0377] Determine whether to delete the agent communication subnet based on whether the administrator is registered (e.g., delete the agent communication subnet if the administrator is not registered).

[0378] The intelligent agent communication subnet is deleted according to the instruction initiated by the UE, and the UE is a UE with deletion authorization;

[0379] Delete an agent communication subnet according to its usage status (e.g., delete the agent communication subnet if it has not been used for a certain period of time).

[0380] When the terminal is a user with administrator privileges, the agent of the terminal initiates an agent deregistration request. The first network function entity can delete the agent communication subnet belonging to the terminal if the deletion conditions in the agent communication subnet deletion policy are met.

[0381] In some embodiments, the method further includes:

[0382] The terminal sends a terminal deregistration request message, which triggers the terminal's intelligent agent to deregister, or updates the terminal's intelligent agent to an offline state.

[0383] In this embodiment, the deregistration of the terminal's intelligent agent can be triggered based on the terminal's deregistration in the communication network, or the registration information of the terminal's intelligent agent can be retained, and its status can be updated only to offline. Retaining the registration information of the terminal's intelligent agent facilitates the switching of the terminal's access network (e.g., from fixed access to mobile access). The information of the terminal's intelligent agent and the intelligent agent's communication subnet does not need to be re-established; only updates are required. This process is faster and better ensures the service continuity of the intelligent agent's communication subnet.

[0384] The methods provided in the various embodiments of this disclosure are based on the same technical concept, so the implementation of each method can be referred to each other, and repeated parts will not be described again.

[0385] The methods provided in the above embodiments of this disclosure are illustrated by specific examples below.

[0386] Example 1: Create a user-level agent communication subnet, and the agent registers in method one.

[0387] Figure 5 is a flowchart of Example 1 provided in the embodiments of this disclosure. As shown in Figure 5, the process mainly includes:

[0388] Step 1-0: Add and deploy the AAMF network function in the network, and AAMF completes registration with NRF.

[0389] Step 1-1: UE1 signs up for the administrator privileges of the intelligent agent communication subnet.

[0390] Steps 1-2: UE1 completes user registration and user session creation.

[0391] Step 1-2a: Agent 1 of UE1 requests agent registration.

[0392] The registration message of UE1 or the session message of UE1 can be extended to carry the registration request information of the agent, and then the MM or SM can forward the message to the AAMF; alternatively, a separate message can be sent to carry the registration request information of the agent and sent to the AAMF.

[0393] The agent registration request message includes one or more of the following information:

[0394] Types of intelligent agents;

[0395] Administrator privilege identifier, or the identity information of the UE to which the intelligent agent belongs;

[0396] Communication modes;

[0397] Communication interface;

[0398] Communication address;

[0399] Business scope;

[0400] AI capabilities;

[0401] Computational ability;

[0402] Location information;

[0403] Mobile information;

[0404] List of service interfaces;

[0405] List of members and authorization information of the intelligent agent communication subnet;

[0406] Agent communication subnet deletion policy;

[0407] The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

[0408] Steps 1-3: AAMF receives the registration request message from Agent 1 of UE1, records and maintains the relevant information of Agent 1, including the corresponding UE1 identity identifier, administrator permissions, etc., and assigns the corresponding ID to Agent 1.

[0409] AAMF can subscribe to the state of the UE (such as active state, idle state, etc.) to synchronously maintain the state of the agent.

[0410] An agent's ID is unique within the agent's communication subnet or globally, and is mainly used to identify the object being communicated when communicating within the subnet.

[0411] Steps 1-4: If the AAMF check has not yet created the communication subnet associated with agent 1, then confirm its administrator privileges.

[0412] Steps 1-4a: AAMF initiates identity and permission verification with UDM to obtain whether UE1 has the authority of the intelligent agent communication subnet administrator in its subscription information.

[0413] Steps 1-5: Based on the results returned in Step 1-4a, AAMF confirms that UE1 currently has administrator privileges, then creates an agent communication subnet belonging to UE1, assigns an "agent communication subnet identifier", updates the communication subnet node information, and adds agent 1.

[0414] Steps 1-5a: AAMF notifies UE1 of the "Agent Communication Subnet Identifier".

[0415] Step 1-5b: Considering that other UEs may have registered as agents before UE1, if the AAMF determines that the identity information of the UE to which the agent belongs is the same as that of UE1 based on the agent's registration information, and verifies the "Agent Communication Subnet Member List and Authorization Information" carried in Step 1-2, then the AAMF sends a message to these other registered agents to notify them of their "Agent Communication Subnet Identifier".

[0416] Whether or not verification of the "intelligent agent communication subnet member list and authorization information" is required depends on the UE or operator policy.

[0417] Steps 1-6: The communication subnet enables communication between members within the subnet by creating "group sessions". AAMF assigns group session IDs, updates group session members, and sets relevant Quality of Service (QoS) policy information.

[0418] The "Agent Communication Subnet Identifier" is used to notify the UE side, enabling UEs within the same agent communication subnet to intuitively obtain this information and provide it to users or third parties. The "Group Session Identifier," on the other hand, is only used for internal network management of subnet communication. A mapping relationship may exist between the "Agent Communication Subnet Identifier" and the "Group Session Identifier."

[0419] Steps 1-6a: AAMF sends group-level session traffic forwarding rules to UPF.

[0420] AAMF can work with SM to update traffic forwarding rules, with SM uniformly supporting the distribution of traffic forwarding rules between user and group levels, such as internal interfaces and group session IDs.

[0421] Steps 1-7: UE2 completes user registration and user session creation.

[0422] Steps 1-7a: Agent 2 of UE2 requests agent registration (the registration process is the same as that of Agent 1 of UE1), carrying registration information, including the identity information of the owner UE (UE1 in this scenario), or "agent communication subnet identifier".

[0423] For example, suppose a user can query the "Agent Communication Subnet Identifier" of UE1 administrator and set it for UE2. Then UE2 can initiate a registration request through the "Agent Communication Subnet Identifier", thereby avoiding the security risks of directly carrying UE1's identity identifier.

[0424] Steps 1-8: AAMF receives the registration request message from Agent 2 of UE2, records and maintains the relevant information of Agent 2, including the corresponding UE2 identity identifier, owner information, etc., and assigns the corresponding ID to Agent 2.

[0425] Steps 1-8a: AAMF obtains the administrator identity information of the corresponding communication subnet based on the owner information of agent 2 or the "agent communication subnet identifier", and performs authentication and other verifications with the administrator to determine whether agent 2 is allowed to join the communication subnet.

[0426] Step 1-8b, or if the UE1 administrator authorizes the network to perform identity authentication and verification on members joining the communication subnet, then agent 2 can be directly authenticated by AAMF to UDM to obtain whether agent 2 belongs to the UE1 administrator.

[0427] Step 1-8c: If an agent has subscribed to communication subnet information from AAMF, it will notify the relevant agent when there is a change in the communication subnet members or state.

[0428] Steps 1-9: AAMF updates group session members.

[0429] Step 1-9a: AAMF updates group-level traffic forwarding rules to UPF.

[0430] Example 2: Create a user-level agent communication subnet, and the agent registers in method two.

[0431] In Example 1, both the communication subnet and group session are created only after the user session is created. The key difference between Example 2 and Example 1 is that in Example 2, communication subnet registration can occur immediately after user registration. Subnet group session creation is triggered when a member of the communication subnet creates a user session. This decouples the agent's communication subnet registration from group session registration.

[0432] Figure 6 is a flowchart of Example 2 provided in the embodiments of this disclosure. As shown in Figure 6, the process mainly includes:

[0433] Step 2-0: Add and deploy the AAMF network function in the network, and AAMF completes registration with NRF.

[0434] Step 2-1: UE1 signs up for the administrator privileges of the intelligent agent communication subnet.

[0435] Step 2-2: UE1 completes user registration.

[0436] Step 2-2a: Agent 1 of UE1 requests agent registration.

[0437] The registration message of UE1 or the session message of UE1 can be extended to carry the registration request information of the agent, and then the MM or SM can forward the message to the AAMF; alternatively, a separate message can be sent to carry the registration request information of the agent and sent to the AAMF.

[0438] The agent registration request message includes one or more of the following information:

[0439] Types of intelligent agents;

[0440] Administrator privilege identifier, or the identity information of the UE to which the intelligent agent belongs;

[0441] Communication modes;

[0442] Communication interface;

[0443] Communication address;

[0444] Business scope;

[0445] AI capabilities;

[0446] Computational ability;

[0447] Location information;

[0448] Mobile information;

[0449] List of service interfaces;

[0450] List of members and authorization information of the intelligent agent communication subnet;

[0451] Agent communication subnet deletion policy;

[0452] The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

[0453] Steps 2-3: AAMF receives the registration request message from Agent 1 of UE1, records and maintains the relevant information of Agent 1, including the corresponding UE1 identity identifier, administrator permissions, etc., and assigns the corresponding ID to Agent 1.

[0454] AAMF can subscribe to the state of the UE (such as active state, idle state, etc.) to synchronously maintain the state of the agent.

[0455] An agent's ID is unique within the agent's communication subnet or globally, and is mainly used to identify the object being communicated when communicating within the subnet.

[0456] Steps 2-4: AAMF checks if the communication subnet associated with agent 1 has been created yet, then confirm its administrator privileges.

[0457] Step 2-4a: AAMF initiates identity and permission verification with UDM to obtain whether UE1 has the permissions of an intelligent agent communication subnet administrator in its subscription information.

[0458] Steps 2-5: Based on the results returned in Steps 1-4a, AAMF confirms that UE1 currently has administrator privileges, then creates an agent communication subnet belonging to UE1, assigns an "agent communication subnet identifier", updates the communication subnet node information, and adds agent 1.

[0459] Step 2-5a: AAMF notifies UE1 of the "Agent Communication Subnet Identifier".

[0460] Step 2-5b: Considering that other UEs may have registered as agents before UE1, if the AAMF determines that the identity information of the UE to which the agent belongs is the same as that of UE1 based on the agent's registration information, and verifies the "Agent Communication Subnet Member List and Authorization Information" carried in Step 1-2, then the AAMF sends a message to these other registered agents to notify them of their "Agent Communication Subnet Identifier".

[0461] Whether or not verification of the "intelligent agent communication subnet member list and authorization information" is required depends on the UE or operator policy.

[0462] Steps 2-6: UE1 completes user session creation.

[0463] Step 2-6a: If the SM determines that the communication subnet to which UE1 belongs has been created, then it will trigger the creation or update of the group session.

[0464] Step 2-6b: The SM performs unified session-related management operations and updates the group sessions and corresponding group-level traffic forwarding rules to the UPF.

[0465] Steps 2-7: UE2 completes user registration and user session creation.

[0466] It should be noted that in steps 2-7, UE2 can also complete user registration, similar to UE1, and then create user sessions later. After UE2's user sessions are created, the group sessions will be updated.

[0467] Step 2-7a: Agent 2 of UE2 requests agent registration (the registration process is the same as that of Agent 1 of UE1), carrying registration information, including the identity information of the owner UE (UE1 in this scenario), or "agent communication subnet identifier".

[0468] For example, suppose a user can query the "Agent Communication Subnet Identifier" of UE1 administrator and set it for UE2. Then UE2 can initiate a registration request through the "Agent Communication Subnet Identifier", thereby avoiding the security risks of directly carrying UE1's identity identifier.

[0469] Steps 2-8: AAMF receives the registration request message from Agent 2 of UE2, records and maintains the relevant information of Agent 2, including the corresponding UE2 identity identifier, owner information, etc., and assigns the corresponding ID to Agent 2.

[0470] Step 2-8a: AAMF obtains the administrator identity information of the corresponding communication subnet based on the owner information of agent 2 or the "agent communication subnet identifier", and performs authentication and other verifications with the administrator to determine whether agent 2 is allowed to join the communication subnet.

[0471] Step 2-8b, or if the UE1 administrator authorizes the network to perform identity authentication and verification on members joining the communication subnet, then agent 2 can be directly authenticated by AAMF to UDM to obtain whether agent 2 belongs to the UE1 administrator.

[0472] Step 2-8c: If the agent has subscribed to communication subnet information from AAMF, it will notify the relevant agent when there is a change in the communication subnet members or state.

[0473] Steps 2-9: AAMF updates group session members.

[0474] Step 2-9a: AAMF updates the group-level traffic forwarding rules to UPF.

[0475] Example 3: The agent registers in a subnet (agent communication subnet).

[0476] Figure 7 is a flowchart of Example 3 provided in the embodiments of this disclosure. As shown in Figure 7, the process mainly includes:

[0477] Step 3-1: Agent 1 of UE1 completes agent registration, in which communication subnet deletion conditions (policies) are set.

[0478] Note: The conditions for deleting a communication subnet can be based on the deletion policy issued by the administrator or a unified policy formulated by the operator.

[0479] Deletion strategies include, but are not limited to:

[0480] According to duration or deadline;

[0481] Based on whether or not a subnet agent member is registered;

[0482] Based on whether the administrator is registered;

[0483] Deleted according to the instruction initiated by the UE, which is a UE authorized to delete;

[0484] According to the usage status of the communication subnet, such as if it has not been used for more than a threshold time.

[0485] Step 3-2: Agent 2 of UE2 requests agent to register.

[0486] Step 3-3: AAMF checks whether the registration was initiated by the administrator UE. If not, it directly updates the communication subnet node information and deletes the information of the corresponding agent 2.

[0487] Steps 3-4a and 3-4b correspond to Method 1 of Example 1.

[0488] Step 3-4a: AAMF updates group session member information.

[0489] Step 3-4b: AAMF updates the group-level traffic forwarding rules to UPF.

[0490] Steps 3-4c and 3-4d correspond to Method 2 of Example 2.

[0491] Steps 3-4c: AAMF notifies SM to update group session.

[0492] Steps 3-4d: SM updates the group-level traffic forwarding rules to UPF.

[0493] Steps 3-5: Agent 1 of UE1 requests agent registration.

[0494] Steps 3-6: AAMF updates the communication subnet node information and deletes the information of the corresponding agent 1.

[0495] Step 3-7, AAMF check, involves the administrator registering and making a judgment based on the communication subnet deletion policy in Step 3-1.

[0496] Step 3-7a: If the conditions are met, delete the communication subnet and notify other members within the subnet.

[0497] Step 3-7b: AAMF notifies subnet member agent 2 of the deletion of the communication subnet and the reason for deletion.

[0498] Step 3-7c: If the conditions are not met, the communication subnet is retained. Members within the subnet can still communicate normally within the subnet.

[0499] Steps 3-8a and 3-8b correspond to Method 1 of Example 1.

[0500] Step 3-8a: AAMF updates group session members or deletes the group session.

[0501] Step 3-8b: AAMF updates or deletes group-level traffic forwarding rules to UPF.

[0502] Steps 3-8c and 3-8d correspond to Method 2 of Example 2.

[0503] Step 3-8c: AAMF notifies SM to update group session.

[0504] Steps 3-8d: SM updates group-level traffic forwarding rules to UPF.

[0505] Example 4: The terminal registers with the communication network.

[0506] Compared to Example 3, the main difference lies in whether the agent's deregistration is triggered internally along with the UE-level communication network deregistration if the UE's agent does not actively initiate deregistration. This can be determined based on the operator's policy configuration; alternatively, the agent's deregistration can be triggered internally simultaneously with the UE-level communication network deregistration; or the registration information of the deregistered UE's agent can be retained, and only the agent's status can be updated to offline. This facilitates faster processing and better guarantees the service continuity of the communication subnet when the UE switches access networks (e.g., from fixed access to mobile access), as the agent and subnet information do not need to be re-established, only updated.

[0507] Example 5: Control plane communication between user-level intelligent agents.

[0508] Figure 8 is a flowchart of Example 5 provided in the embodiments of this disclosure. As shown in Figure 8, the process mainly includes:

[0509] Step 5-1: Agent 1 queries AAMF according to business requirements to obtain whether there are other agents in the subnet that can meet the business requirements, and sets the identifier for transmitting interaction information through the control plane interface.

[0510] Note: If agent 1 has subscribed to information about subnet-related nodes and corresponding agents on AAMF based on its "communication subnet identifier", then this query step 5-1 to step 5-3 can be omitted.

[0511] Step 5-2: Based on the information requested by agent 1, AAMF searches for a suitable agent in its communication subnet nodes and selects the optimal one based on information such as capabilities, communication interface, and control plane.

[0512] Step 5-3: AAMF notifies Agent 1 that it has selected a suitable communication target, which is Agent 2 in this example. It also notifies Agent 1 of Agent 2's ID, address, service interface, capabilities and other information.

[0513] Step 5-4: Agent 1 sends a control plane transparent signaling message to AAMF, which carries a subnet communication transparent message type, carries the target agent 2 (ID) of the transparent communication, and the communication content is the transparent container (the content of the interaction with agent 2).

[0514] Step 5-4a: For scenarios involving broadcasting within the communication subnet, steps 5-1 to 5-3 are not required. Agent 1 sends control plane signaling to AAMF, carrying a communication message type of subnet-wide mass message and a communication content of a transparent container (the content of the mass message).

[0515] Step 5-5: If the communication message type sent by agent 1 is a subnet communication transparent message, then obtain the information of agent 2 in the message.

[0516] Step 5-5a: If the communication message type sent by agent 1 is a group message within the subnet, then send the corresponding message content to each agent in the corresponding group session that supports control plane interface communication.

[0517] Note: Group messaging sends messages to all nodes in the communication subnet. The process for sending a single message is similar to sending a message to a single agent. Please refer to the steps below, which will not be repeated here.

[0518] Steps 5-6: AAMF checks whether Agent 2 is reachable. If not, it initiates a paging process.

[0519] Note: If AAMF has not subscribed to the state of UE2, you can query MM or SM at this step.

[0520] Step 5-6a: If agent 2 is unreachable, check the AAMF and cache the message sent by agent 1 according to the policy.

[0521] Step 5-6b: Trigger paging UE2 to make agent 2 reachable.

[0522] Steps 5-6c: Page UE2 successfully, notify AAMF agent 2 that communication is reachable.

[0523] Steps 5-7: AAMF transparently forwards the message content to agent 2, carrying the communication message type as subnet communication transparent message, indicating that the message source is agent 1, and sends the message to agent 2.

[0524] Steps 5-8: AAMF sends control plane signaling to agent 2, which carries the content of the interaction between agent 1 and agent 2.

[0525] Steps 5-9: Agent 2 receives the message sent by Agent 1 through the control plane.

[0526] Step 5-10: Agent 2 replies to AAMF with a response message, indicating that it has received the message sent in step 5-8.

[0527] Step 5-11: AAMF replies with a response message to agent 1, indicating that the message sent to agent 2 in step 5-4 was successfully forwarded.

[0528] Note: All control plane messages sent by the intelligent agent must carry a message sequence number identifier in order to correctly distinguish the request message corresponding to the response message.

[0529] Example 6: User plane communication between user-level intelligent agents.

[0530] Figure 9 is a flowchart of Example 6 provided in the embodiments of this disclosure. As shown in Figure 9, the process mainly includes:

[0531] Step 6-1: Agent 2 queries AAMF according to business requirements to obtain whether there are other agents in the subnet that can meet the business requirements, and sets the identifier for transmitting interaction information through the user plane interface.

[0532] Note: If agent 2 has subscribed to information about subnet-related nodes and corresponding agents on AAMF based on its "communication subnet identifier", then this query step 6-1 to step 6-3 can be omitted.

[0533] Step 6-2: Based on the information requested by agent 2, AAMF searches for a suitable agent in its communication subnet nodes and selects the optimal one based on information such as capabilities and whether the communication interface is a user plane.

[0534] Step 6-3: AAMF notifies Agent 2 that it has selected a suitable communication target, which is Agent 1 in this example. It also notifies Agent 2 of Agent 1's ID, address, service interface, capabilities and other information.

[0535] Step 6-4: Agent 2 sends a user plane message to UPF, which carries the communication destination address as the address of Agent 1.

[0536] Step 6-4a: For scenarios involving mass messaging within the communication subnet, steps 6-1 to 6-3 are not required. Agent 2 sends a user plane message, which carries the target address as the multicast / broadcast address within the group.

[0537] Step 6-5: Based on the fact that the destination address of the message sent by agent 2 is agent 1, query the group session forwarding rules and forward the message.

[0538] Note: When UPF receives a message from agent 2 of UE2, it first matches the UE2 user session forwarding rules. The outgoing interface is an internal interface, so it needs to continue querying the group-level session forwarding rules.

[0539] Step 6-5a: If the destination address of the message sent by agent 2 is a group multicast / broadcast address, then forward it to each agent in the corresponding group session.

[0540] Note: Group messaging sends messages to all nodes in this communication subnet. The process for sending a single message is similar to sending a message to a single agent; please refer to the steps below, which will not be repeated here.

[0541] Step 6-6: UPF checks whether agent 1 is reachable. If not, it initiates a paging process.

[0542] Step 6-6a: If agent 1 is unreachable, check the UPF and cache the message sent by agent 2 according to the policy.

[0543] Step 6-6b: Trigger paging UE1 to make agent 1 reachable via communication.

[0544] Step 6-6c: Pager UE1 successfully, notifying UPF agent 1 that communication is reachable.

[0545] Steps 6-7: UPF sends the message to agent 1 according to the group session forwarding rules.

[0546] Note: This is based on a group session forwarding mechanism similar to that of a 5G Local Area Network (LAN). First, the user session rules of UE2 are processed, with the exit point being an internal interface. Then, the internal interface is used to search within the group session of the agent corresponding to UE2 to see if the communication destination address is a member of the group session. In this example, the target agent is agent 1. Since the group session query shows that agent 1 of UE1 is a member of the group session, forwarding is then directly performed again through the internal interface based on UE1.

[0547] Steps 6-8: UPF forwards user plane messages to agent 1. The message content includes the content of the interaction between agent 2 and agent 1.

[0548] Steps 6-9: Agent 1 receives the message sent by Agent 2 through the user plane.

[0549] Example 7: Different deployment methods of agent management functions in the core network.

[0550] 1. The intelligent agent management function is deployed in the SM network function.

[0551] The main difference compared to Example 1 is:

[0552] (1) The functions corresponding to AAMF are all deployed in the SM network functions, and there is no need to add AAMF as an independent network function and related interactions with NRF separately.

[0553] (2) All related functions or processes handled by AAMF are completed by SM.

[0554] Other similar cases will not be elaborated upon further.

[0555] 2. The agent management function is deployed in the MM and SM network functions respectively.

[0556] Compared to Example 2, the main difference is:

[0557] (1) The agent registration function and communication subnet creation function are deployed in the MM network function, and the group session function is deployed in the SM network function.

[0558] (2) It is necessary to add a process for MM to notify SM to create group sessions.

[0559] (3) Since the MM may be replaced as the UE moves, it is necessary to support the synchronization of agent registration information and communication subnet information between MMs.

[0560] Other similar cases will not be elaborated upon further.

[0561] Example 8: Deployment of agent management functions on the network side.

[0562] Referring to Figure 3, AAMF-related functions can be deployed separately on the network side as an intelligent agent communication network, rather than within the core network. Messages sent by the UE are forwarded to the AAMF by the core network user plane (UPF+).

[0563] 1. The key difference in the process compared to Example 1 is:

[0564] Step 1-1 (replace step 1-1 in the previous text, the same applies below) The agent's contract data can also be directly deployed on AAMF.

[0565] Step 1-2: Add process: Select the appropriate AAMF through the policy control function (PCF+) and notify the UE of the AAMF's communication address by the core network.

[0566] Step 1-2a: The destination address of the registration request message sent by the UE is the communication address of the AAMF obtained in step 1-2.

[0567] Steps 1-4a, including agent administrator permission authentication, can be completed locally in AAMF and do not require interaction with UDM.

[0568] Steps 1-6a: The forwarding rules for the agent user and the corresponding user group of the communication subnet can be sent to the corresponding agent communication user plane function of AAMF, without needing to interact with UPF.

[0569] Steps 1-8b, including agent administrator permission authentication, can be completed locally in AAMF and do not require interaction with UDM.

[0570] Steps 1-9a: The forwarding rules for the agent user and the corresponding user group of the communication subnet can be sent to the corresponding agent communication user plane function of AAMF, without needing to interact with UPF.

[0571] 2. The key difference in the process compared to Example 5 is:

[0572] Steps 5-6, 5-6a, and 5-6c are not involved.

[0573] Steps 5-8: The message is sent directly to the UPF, which then forwards it to the UE. Whether the UE is reachable can be determined using existing mechanisms within the UPF.

[0574] 3. The key difference in the process compared to Example 6 is:

[0575] Step 6-1: The destination address of the message sent by agent 2 is the communication address of AAMF.

[0576] Step 6-3: The source address for AAMF to send messages is the AAMF communication address.

[0577] In either step 6-4 or step 6-4a, the message is sent to the user plane of AAMF for processing. The destination address of the message is either the address of the intelligent agent at the communication peer or the multicast / broadcast address within the group.

[0578] Step 6-5 or step 6-5a are both executed in AAMF.

[0579] Steps 6-6, 6-6a, and 6-6c are not involved.

[0580] Steps 6 and 7 are both executed in AAMF.

[0581] Steps 6-8: The message is sent directly to the UPF, which then forwards it to the UE. Whether the UE is reachable can be determined using existing mechanisms within the UPF.

[0582] Figure 10 is a schematic diagram of the structure of a terminal provided in an embodiment of this disclosure. As shown in Figure 10, the terminal includes a memory 1020, a transceiver 1010, and a processor 1000; wherein the processor 1000 and the memory 1020 may also be physically arranged separately.

[0583] The memory 1020 is used to store computer programs; the transceiver 1010 is used to send and receive data under the control of the processor 1000.

[0584] In Figure 10, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1000 and memory represented by memory 1020. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described in detail herein. The bus interface provides an interface. The transceiver 1010 may be multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 1030 may also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0585] The processor 1000 is responsible for managing the bus architecture and general processing, while the memory 1020 can store the data used by the processor 1000 when performing operations.

[0586] The processor 1000 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0587] The processor 1000 executes any of the terminal-side methods provided in this disclosure embodiment by calling a computer program stored in the memory 1020, according to the obtained executable instructions.

[0588] Figure 11 is a schematic diagram of the structure of the first network functional entity provided in the embodiment of this disclosure. As shown in Figure 11, the first network functional entity includes a memory 1120, a transceiver 1110 and a processor 1100; wherein the processor 1100 and the memory 1120 can also be physically arranged separately.

[0589] The memory 1120 is used to store computer programs; the transceiver 1110 is used to send and receive data under the control of the processor 1100.

[0590] In Figure 11, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1100 and memory represented by memory 1120. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described in detail herein. The bus interface provides an interface. The transceiver 1110 may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media.

[0591] The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 can store the data used by the processor 1100 when performing operations.

[0592] The processor 1100 can be a CPU, ASIC, FPGA or CPLD, and the processor can also adopt a multi-core architecture.

[0593] The processor 1100 executes any of the methods described in the first network functional entity provided in this disclosure embodiment by calling a computer program stored in the memory 1120, in accordance with the obtained executable instructions.

[0594] It should be noted that the terminal and the first network function entity provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0595] The intelligent entity subnet communication device provided in the embodiments of this disclosure is described below. The intelligent entity subnet communication device described below can be referred to in correspondence with the intelligent entity subnet communication method described above.

[0596] Figure 12 is a schematic diagram of one of the structures of the intelligent agent subnet communication device provided in the embodiments of this disclosure. As shown in Figure 12, the device includes:

[0597] The registration unit 1210 is used for the terminal's intelligent agent to send an intelligent agent registration request message to the first network function entity. The intelligent agent registration request message is used to trigger the creation of an intelligent agent communication subnet.

[0598] The communication unit 1220 is used for the terminal's intelligent agents to communicate with each other based on the intelligent agent communication subnet.

[0599] In some embodiments, the agent registration request message includes one or more of the following information:

[0600] Types of intelligent agents;

[0601] Administrator permission identifier, or administrator information to which the agent belongs;

[0602] Communication modes;

[0603] Communication interface;

[0604] Communication address;

[0605] Business scope;

[0606] Artificial intelligence (AI) capabilities;

[0607] Computational ability;

[0608] Location information;

[0609] Mobile information;

[0610] List of service interfaces;

[0611] List of members and authorization information of the intelligent agent communication subnet;

[0612] Agent communication subnet deletion policy;

[0613] The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

[0614] In some embodiments, the registration unit 1210 is further configured to:

[0615] The terminal's intelligent agent receives an intelligent agent registration response message sent by the first network function entity. The intelligent agent registration response message includes one or more of the following information:

[0616] Intelligent agent identification;

[0617] Identifier for the intelligent agent communication subnet.

[0618] In some embodiments, communication between agents is performed based on an agent communication subnet, including:

[0619] Based on the business requirements of the intelligent agent, determine the target intelligent agent for communication;

[0620] Send a first control plane request message to the first network function entity, or send a user plane message to the user plane function entity;

[0621] The first control plane request message or user plane message is used to send interactive information to the target intelligent agent.

[0622] In some embodiments, the first control plane request message includes interaction information and one or more of the following:

[0623] The communication message type is either a subnet communication transparent message or a subnet group message;

[0624] Identification of the target intelligent agent.

[0625] In some embodiments, the user plane message includes interaction information and target address information for communication.

[0626] In some embodiments, the target address information is the address information of the target agent or the address information used to indicate the group messaging within the agent's communication subnet.

[0627] In some embodiments, the first network function entity is deployed in the core network or in an agent communication network independent of the core network.

[0628] In some embodiments, the first network function entity is deployed in the core network, including:

[0629] The first network function entity is deployed within the session management function entity; or...

[0630] The first network function entity is deployed in the access and mobility management function entity and the session management function entity, respectively; or,

[0631] The first network function entity, the access and mobility management function entity, and the session management function entity are jointly deployed in a single core network function entity; or...

[0632] The first network function entity is deployed independently in the core network.

[0633] Figure 13 is a second schematic diagram of the structure of the intelligent agent subnet communication device provided in this embodiment of the present disclosure. As shown in Figure 13, the device includes:

[0634] The receiving unit 1310 is used to receive an agent registration request message sent by the agent of the terminal;

[0635] Execution unit 1320 is configured to perform one or more of the following operations based on the agent registration request message:

[0636] Create an agent communication subnet or add an agent to an existing agent communication subnet;

[0637] Record and maintain relevant information about the intelligent agent;

[0638] Assign an agent identifier to the agent;

[0639] Assign an agent communication subnet identifier to the created agent communication subnet.

[0640] In some embodiments, the agent registration request message includes one or more of the following information:

[0641] Types of intelligent agents;

[0642] Administrator privilege identifier, or the administrator information to which the agent belongs, or the agent's communication subnet identifier;

[0643] Communication modes;

[0644] Communication interface;

[0645] Communication address;

[0646] Business scope;

[0647] AI capabilities;

[0648] Computational ability;

[0649] Location information;

[0650] Mobile information;

[0651] List of service interfaces;

[0652] List of members and authorization information of the intelligent agent communication subnet;

[0653] Agent communication subnet deletion policy;

[0654] The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

[0655] In some embodiments, creating an agent communication subnet or adding an agent to an existing agent communication subnet includes:

[0656] If the user on the terminal has administrator privileges, create an intelligent agent communication subnet belonging to the terminal; or,

[0657] When the terminal user is not an administrator, the agent will be added to the created agent communication subnet.

[0658] In some embodiments, the device further includes:

[0659] The sending unit is used to send an agent registration response message to the agent of the terminal. The agent registration response message includes one or more of the following information:

[0660] Intelligent agent identification;

[0661] Identifier for the intelligent agent communication subnet.

[0662] In some embodiments, the execution unit 1320 is further configured to:

[0663] Create a group session for the created agent communication subnet and perform one or more of the following operations:

[0664] Assign group session identifier;

[0665] Update group session members;

[0666] Issue group-level session traffic forwarding rules to user plane functional entities.

[0667] In some embodiments, creating a group session for the created agent communication subnet includes:

[0668] For cases where the agent communication subnet is created after the user session is created, the creation of the group session is triggered after the agent communication subnet is created; or...

[0669] In the case of creating an agent communication subnet and then creating a user session, the creation of a group session is triggered after the user session is created.

[0670] In some embodiments, the device further includes a forwarding unit for:

[0671] Receive a first control plane request message sent by a first intelligent agent. The first control plane request message is used to send interactive information to the second intelligent agent.

[0672] Based on the request message from the first control plane, interactive information is sent to the second intelligent agent.

[0673] In some embodiments, the first control plane request message includes interaction information and one or more of the following:

[0674] The communication message type is either a subnet communication transparent message or a subnet group message;

[0675] The identifier of the second intelligent agent.

[0676] In some embodiments, the apparatus further includes a first deregistration unit, configured to:

[0677] The receiving terminal sends a registration request message from the intelligent agent.

[0678] Based on the agent's registration request message, the agent's information is deleted from the member information of the agent's communication subnet.

[0679] In some embodiments, the first deregistration unit is further configured to:

[0680] When the terminal user has administrator privileges, the system determines whether to delete the intelligent agent communication subnet belonging to the terminal based on the intelligent agent communication subnet deletion policy.

[0681] In some embodiments, the apparatus further includes a second deregistration unit for:

[0682] The terminal sends a terminal deregistration request message, which triggers the terminal's intelligent agent to deregister, or updates the terminal's intelligent agent to an offline state.

[0683] It should be noted that the intelligent body subnet communication device provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0684] It should be noted that the division of units in the embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0685] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0686] On the other hand, embodiments of this disclosure also provide a processor-readable storage medium storing a program for causing a processor to execute the intelligent agent subnet communication method provided in the above embodiments.

[0687] It should be noted that the processor-readable storage medium provided in this embodiment can implement all the method steps implemented in the above method embodiments and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0688] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0689] The technical solutions provided in this disclosure are applicable to a variety of systems. For example, applicable systems may include Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, and 6G (sixth generation mobile communication technology) systems. These systems may include terminal equipment and network equipment. The systems may also include a core network component, such as an Evolved Packet Core (EPC), a 5G core network (5GC), or a 6G core network.

[0690] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0691] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0692] These processor-executable instructions may also be stored in a processor-readable memory that can instruct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0693] These processor-executable instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0694] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.

Claims

1. A smart agent subnet communication method, applied to a terminal, comprising: The terminal's intelligent agent sends an intelligent agent registration request message to the first network function entity, and the intelligent agent registration request message is used to trigger the creation of an intelligent agent communication subnet; The terminal's agents communicate with each other based on the agent communication subnet.

2. The intelligent agent subnet communication method according to claim 1, wherein, The agent registration request message includes one or more of the following information: Types of intelligent agents; Administrator permission identifier, or administrator information to which the intelligent agent belongs; Communication modes; Communication interface; Communication address; Business scope; Artificial intelligence (AI) capabilities; Computational ability; Location information; Mobile information; List of service interfaces; List of members and authorization information of the intelligent agent communication subnet; Agent communication subnet deletion policy; The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

3. The intelligent agent subnet communication method according to claim 1 or 2, wherein, The method further includes: The terminal's intelligent agent receives an intelligent agent registration response message sent by the first network function entity, the intelligent agent registration response message including one or more of the following information: Intelligent agent identification; Identifier for the intelligent agent communication subnet.

4. The intelligent agent subnet communication method according to claim 1, wherein, The communication between agents based on the agent communication subnet includes: Based on the business requirements of the intelligent agent, the target intelligent agent for communication is determined; Send a first control plane request message to the first network function entity, or send a user plane message to the user plane function entity; The first control plane request message or the user plane message is used to send interactive information to the target intelligent agent.

5. The intelligent agent subnet communication method according to claim 4, wherein, The first control plane request message includes the interaction information and one or more of the following: The communication message type is either a subnet communication transparent message or a subnet group message; The identifier of the target intelligent agent.

6. The intelligent agent subnet communication method according to claim 4, wherein, The user plane message includes the interaction information and the target address information for communication.

7. The intelligent agent subnet communication method according to claim 6, wherein, The target address information is either the address information of the target intelligent agent or the address information used to instruct the intelligent agent to send mass messages within the communication subnet.

8. The intelligent agent subnet communication method according to claim 1, wherein, The first network functional entity is deployed in the core network or in an intelligent agent communication network independent of the core network.

9. The intelligent agent subnet communication method according to claim 8, wherein, The first network functional entity is deployed in the core network and includes: The first network function entity is deployed within the session management function entity; or, The first network function entity is deployed in the access and mobility management function entity and the session management function entity, respectively; or, The first network function entity, access and mobility management function entity, and session management function entity are jointly deployed in a core network function entity; or, The first network functional entity is deployed independently in the core network.

10. A smart agent subnet communication method, applied to a first network functional entity, comprising: Receive agent registration request message sent by the agent on the receiving terminal; Based on the agent registration request message, perform one or more of the following operations: Create an agent communication subnet or add the agent to an existing agent communication subnet; Record and maintain relevant information about the intelligent agent; Assign an agent identifier to the agent; Assign an agent communication subnet identifier to the created agent communication subnet.

11. The intelligent agent subnet communication method according to claim 10, wherein, The agent registration request message includes one or more of the following information: Types of intelligent agents; Administrator permission identifier, or the administrator information to which the intelligent agent belongs, or the intelligent agent communication subnet identifier; Communication modes; Communication interface; Communication address; Business scope; AI capabilities; Computational ability; Location information; Mobile information; List of service interfaces; List of members and authorization information of the intelligent agent communication subnet; Agent communication subnet deletion policy; The authorized network may authenticate members of the intelligent agent communication subnet, or the unauthorized network may authenticate members of the intelligent agent communication subnet.

12. The intelligent agent subnet communication method according to claim 10 or 11, wherein, The creation of the agent communication subnet or the addition of the agent to an existing agent communication subnet includes: If the user on the terminal has administrator privileges, create an intelligent agent communication subnet belonging to the terminal; or, If the terminal is used by a user without administrator privileges, the agent will be added to the created agent communication subnet.

13. The intelligent agent subnet communication method according to claim 10 or 11, wherein, The method further includes: Send an agent registration response message to the agent of the terminal, wherein the agent registration response message includes one or more of the following information: Intelligent agent identification; Identifier for the intelligent agent communication subnet.

14. The intelligent agent subnet communication method according to claim 10, wherein, The method further includes: Create a group session for the created agent communication subnet and perform one or more of the following operations: Assign group session identifier; Update group session members; Issue group-level session traffic forwarding rules to user plane functional entities.

15. The intelligent agent subnet communication method according to claim 14, wherein, The creation of a group session for the created agent communication subnet includes: In the case where the agent communication subnet is created after the user session is created, the creation of the group session is triggered after the agent communication subnet is created; or... In the case where a user session is created after an agent communication subnet is created, the creation of the group session is triggered after the user session is created.

16. The intelligent agent subnet communication method according to claim 10, wherein, The method further includes: Receive a first control plane request message sent by a first intelligent agent, the first control plane request message being used to send interaction information to a second intelligent agent; Based on the first control plane request message, the interaction information is sent to the second intelligent agent.

17. The intelligent agent subnet communication method according to claim 16, wherein, The first control plane request message includes the interaction information and one or more of the following: The communication message type is either a subnet communication transparent message or a subnet group message; The identifier of the second intelligent agent.

18. The intelligent agent subnet communication method according to claim 10, wherein, The method further includes: Receive the agent registration request message sent by the agent of the terminal; Based on the agent's registration request message, the agent's information is deleted from the agent communication subnet member information to which the agent belongs.

19. The intelligent agent subnet communication method according to claim 18, wherein, The method further includes: If the terminal is a user with administrator privileges, determine whether to delete the intelligent agent communication subnet belonging to the terminal based on the intelligent agent communication subnet deletion policy.

20. The intelligent agent subnet communication method according to claim 10, wherein, The method further includes: Based on the terminal deregistration request message sent by the terminal, the terminal's intelligent agent is triggered to deregister, or the terminal's intelligent agent is updated to an offline state.

21. A terminal, comprising a memory, a transceiver, and a processor; Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: The terminal's intelligent agent sends an intelligent agent registration request message to the first network function entity, and the intelligent agent registration request message is used to trigger the creation of an intelligent agent communication subnet; The terminal's agents communicate with each other based on the agent communication subnet.

22. A first network functional entity, comprising a memory, a transceiver, and a processor; Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Receive agent registration request message sent by the agent on the receiving terminal; Based on the agent registration request message, perform one or more of the following operations: Create an agent communication subnet or add the agent to an existing agent communication subnet; Record and maintain relevant information about the intelligent agent; Assign an agent identifier to the agent; Assign an agent communication subnet identifier to the created agent communication subnet.

23. A processor-readable storage medium storing a program for causing a processor to perform the method of any one of claims 1 to 9, or to perform the method of any one of claims 10 to 20.

Images