Communication method and apparatus

Abstract

The present application discloses a communication method and apparatus, applicable to fields such as multi-agent collaboration. The method comprises: a collaborative control function network element in an access network or a core network receives first collaboration request information, the first collaboration request information comprising description information of a collaborative task, wherein at least one agent participating in the collaborative task comprises a first agent; and the collaborative control function network element sends execution request information to the first agent, the execution request information being used for requesting the first agent to execute a sub-task of the collaborative task. In this way, according to embodiments of the present application, a collaborative control function network element is introduced into a core network or an access network, and agents are controlled to complete a collaborative task by means of the collaborative control function network element. The transmission latency between the collaborative control function network element and the agents is low, and thus the collaboration requirements of a low-latency service are met.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on November 17, 2023, with application number 202311554405.5 and invention name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] With the rapid development of artificial intelligence (AI) technology, the trend of intelligent terminal devices is becoming more and more obvious. For example, various intelligent entities such as robots, smart cars, smart phones, smart wearable devices with intelligent technology are emerging in an endless stream.

[0005] Currently, there are more and more scenarios where multiple intelligent agents collaborate to complete a task (i.e., multi-agent collaboration), such as multiple intelligent vehicles collaborating to complete road condition analysis. Multi-agent collaboration has become an important means of solving complex problems and realizing more advanced applications.

[0006] However, how to achieve multi-agent collaboration still needs further research.

[0007] Summary of the Invention

[0008] The present application provides a communication method and device for achieving collaborative tasks through network element control of intelligent entities in a core network or access network, thereby reducing transmission delays and meeting the collaborative needs of low-latency services.

[0009] In a first aspect, the present application provides a communication method, wherein the execution subject of the method is a collaborative control function network element or a module of a collaborative control function network element in a network, the collaborative control function network element is a control plane network element, and the network is a core network or an access network. Here, the collaborative control function network element is used as an example for description. In this method, the collaborative control function network element receives a first collaborative request message from a second intelligent agent, and the first collaborative request message includes description information of a collaborative task; wherein at least one intelligent agent participating in the collaborative task includes a first intelligent agent; and an execution request message is sent to the first intelligent agent, and the execution request message is used to request the first intelligent agent to perform a subtask of the collaborative task.

[0010] In this way, the embodiment of the present application introduces a collaborative control function network element in the core network or access network, and controls the intelligent body through the collaborative control function network element to complete the collaborative task. Since the transmission delay between the network element in the core network or access network and the intelligent body is small, it is easy to meet the collaborative requirements of low-latency services.

[0011] In one possible design, the method further includes: receiving status information from the first agent, the status information being used to indicate the status of the first agent; determining whether the status information satisfies the status requirements of the collaborative task for the agents participating in the collaborative task; wherein the status requirements are determined based on the description information of the collaborative task.

[0012] In this way, considering that the intelligent agent may have mobility (for example, the intelligent agent is a mobile terminal), the collaborative control function network element can determine that the first intelligent agent participates in the collaborative task when the status information of the first intelligent agent meets the status requirements, thereby making the determined intelligent agent participating in the collaborative task more reasonable and accurate, and avoiding the problem of determining an intelligent agent that does not meet the status requirements as an intelligent agent participating in the collaborative task, resulting in failure of task execution.

[0013] In one possible design, the state of the first agent includes at least one of the following: the network connection state of the first agent; the computing resource state of the first agent; the location state of the first agent; the power state of the first agent; the motion state of the first agent; and the memory state of the first agent.

[0014] In one possible design, the method further includes: sending status request information to the first agent, where the status request information is used to request the status information.

[0015] In this way, the collaborative control function network element sends status request information to the first intelligent agent, and then the first intelligent agent feeds back status information based on the request of the collaborative control function network element, so that the first intelligent agent can feed back status information in a targeted manner.

[0016] In one possible design, the method further includes: receiving capability information from the first agent; determining whether the capability information meets the capability requirements of the collaborative task for the agents participating in the collaborative task; wherein the capability requirements are determined based on the description information of the collaborative task.

[0017] In this way, the collaborative control function network element can determine the intelligent agent that the first intelligent agent participates in the collaborative task when the capability information of the first intelligent agent meets the capability requirements, thereby making the determined intelligent agent that participates in the collaborative task more reasonable and accurate.

[0018] In one possible design, the capability information is used to indicate the type of data that the first agent supports sensing and / or the type of task that the first agent supports executing.

[0019] In one possible design, receiving capability information from the first agent includes receiving a registration request message from the first agent, wherein the registration request message includes the capability information.

[0020] In one possible design, the method further includes: determining that the first collaboration request information includes an identifier of the first agent.

[0021] In one possible design, the method further includes: receiving feedback information from the first agent, the feedback information including the execution result of the subtask; determining the execution result of the collaborative task based on the feedback information; and sending the execution result of the collaborative task to the second agent.

[0022] In one possible design, the method further includes: sending collaborative configuration request information to the first agent, the collaborative configuration request information including configuration parameters required for the first agent to participate in the collaborative task; and receiving collaborative configuration response information from the first agent, the collaborative configuration response information being used to indicate that the configuration of the first agent is successful.

[0023] In one possible design, the method further includes: determining, based on the description information of the collaborative task, that a maximum transmission delay required by the collaborative task is greater than a threshold.

[0024] In one possible design, the method further includes: receiving a deregistration request message from the first agent; and releasing the connection between the first agent and the collaborative control function network element according to the deregistration request message.

[0025] In one possible design, the first intelligent agent is a terminal device or an access network device.

[0026] In one possible design, a collaborative task refers to a task that cannot be completed by the initiator and requires the collaboration of one or more intelligent agents. The one or more intelligent agents are the agents participating in the collaborative task.

[0027] In one possible design, the collaborative task is a perception task or a computing task.

[0028] In a second aspect, the present application provides a communication method, wherein the execution subject of the method is a first agent or a module of the first agent. This method is described herein using the first agent as the execution subject as an example. In this method, the first agent receives an execution request message from a collaborative control function network element in a network, wherein the execution request message is used to request the first agent to execute a subtask of a collaborative task; wherein the network is an access network or a core network; and the subtask is executed according to the execution request message.

[0029] In one possible design, the method further includes: sending status information of the first agent to the collaborative control function network element, where the status information is used to indicate the status of the first agent.

[0030] In one possible design, the state of the first agent includes at least one of the following: the network connection state of the first agent; the computing resource state of the first agent; the location state of the first agent; the power state of the first agent; the motion state of the first agent; and the memory state of the first agent.

[0031] In one possible design, the method further includes: receiving status request information from the collaborative control function network element, where the status request information is used to request the status information.

[0032] In one possible design, the method further includes: sending capability information of the first agent to the collaborative control function network element, where the capability information of the first agent is used to indicate the type of data that the first agent supports perceiving and / or the type of task that the first agent supports executing.

[0033] In one possible design, sending the capability information of the first intelligent agent to the collaborative control function network element includes: sending a registration request message to the collaborative control function network element, wherein the registration request message includes the capability information.

[0034] In one possible design, the method also includes: receiving collaborative configuration request information from the collaborative control function network element, the collaborative configuration request information including the configuration parameters required for the first intelligent agent to participate in the collaborative task; and sending collaborative configuration response information to the collaborative control function network element, the collaborative configuration response information being used to indicate that the configuration of the first intelligent agent is successful.

[0035] In one possible design, the method further includes: sending feedback information to the collaborative control function network element, wherein the feedback information includes the execution result of the subtask.

[0036] In one possible design, the method further includes: sending a deregistration request message to the collaborative control function network element.

[0037] In one possible design, the first intelligent agent is a terminal device or an access network device.

[0038] In a third aspect, the present application provides a communication method, in which the execution subject of the method is a second agent or a module of the second agent. Here, the second agent is described as an example of the execution subject. In this method, the second agent sends a first collaborative request message to a collaborative control function network element in the network, wherein the first collaborative request message includes description information of the collaborative task; wherein the network is an access network or a core network; and receives a collaborative response message from the collaborative control function network element, wherein the collaborative response message includes the execution result of the collaborative task.

[0039] In one possible design, the second intelligent agent is a terminal device or an access network device.

[0040] The communication method provided in the second or third aspect above corresponds to the first aspect, and the beneficial effects of the relevant technical features can refer to the description of the first aspect.

[0041] In a fourth aspect, the present application provides a communication method, the execution subject of the method is a collaborative control function network element or a module of a collaborative control function network element in the network, the collaborative control function network element is a control plane network element, the network is a core network or an access network, and the network also includes a collaborative execution function network element. Here, the collaborative control function network element is used as an example for description. In this method, the collaborative control function network element receives a first collaborative request message from a second intelligent agent, the first collaborative request message includes description information of a collaborative task, and at least one intelligent agent participating in the collaborative task includes a first intelligent agent; and sends a second collaborative request message to the collaborative execution function network element corresponding to the first intelligent agent, the second collaborative request message includes description information of the collaborative task and an identifier of at least one intelligent agent participating in the collaborative task.

[0042] In this way, the embodiment of the present application introduces collaborative control function network elements and collaborative execution function network elements in the core network or access network, and jointly controls the intelligent body to complete collaborative tasks through the collaborative control function network elements and collaborative execution function network elements. Since the transmission delay between the network elements in the core network or access network and the intelligent body is relatively small, it is easy to meet the collaborative needs of low-latency services.

[0043] In one possible design, the method further includes: receiving status information from the first agent, the status information being used to indicate the status of the first agent; the status information meeting the status requirements of the collaborative task for the agents participating in the collaborative task; wherein the status requirements are determined based on the description information of the collaborative task.

[0044] In this way, considering that the intelligent agent may have mobility (for example, the intelligent agent is a mobile terminal), the collaborative control function network element can determine that the first intelligent agent participates in the collaborative task when the status information of the first intelligent agent meets the status requirements, thereby making the determined intelligent agent participating in the collaborative task more reasonable and accurate, and avoiding the problem of determining an intelligent agent that does not meet the status requirements as an intelligent agent participating in the collaborative task, resulting in failure of task execution.

[0045] In one possible design, the state of the first agent includes at least one of the following: the network connection state of the first agent; the computing resource state of the first agent; the location state of the first agent; the power state of the first agent; the motion state of the first agent; and the memory state of the first agent.

[0046] In one possible design, the method further includes: sending status request information to the first agent, where the status request information is used to request the status information.

[0047] In this way, the collaborative control function network element sends status request information to the first intelligent agent, and then the first intelligent agent feeds back status information based on the request of the collaborative control function network element, so that the first intelligent agent can feed back status information in a targeted manner.

[0048] In one possible design, the method further includes: receiving capability information from the first agent; determining whether the capability information of the first agent meets the capability requirements of the collaborative task for the agents participating in the collaborative task; wherein the capability requirements are determined based on the description information of the collaborative task.

[0049] In this way, the collaborative control function network element can determine the intelligent agent that the first intelligent agent participates in the collaborative task when the capability information of the first intelligent agent meets the capability requirements, thereby making the determined intelligent agent that participates in the collaborative task more reasonable and accurate.

[0050] In one possible design, the capability information of the first agent is used to indicate the type of data that the first agent supports perceiving and / or the type of task that the first agent supports executing.

[0051] In one possible design, receiving capability information from the first agent includes receiving a registration request message from the first agent, wherein the registration request message includes the capability information.

[0052] In one possible design, the method further includes: determining that the first collaboration request information includes an identifier of the first agent.

[0053] In one possible design, the method also includes: receiving the execution result of the subtask of the collaborative task from the collaborative execution functional network element; obtaining the execution result of the collaborative task based on the execution result of the subtask; and sending the execution result of the collaborative task to the second intelligent agent.

[0054] In one possible design, the method further includes: sending collaborative configuration request information to the first agent, where the collaborative configuration request information includes configuration parameters required for the first agent to participate in the collaborative task.

[0055] In one possible design, the method further includes: determining, based on the description information of the collaborative task, that a maximum transmission delay required by the collaborative task is less than or equal to a threshold.

[0056] In one possible design, the method also includes: receiving a logout request message from the first agent; and releasing the connection between the first agent and the collaborative control function network element, and / or releasing the connection between the first agent and the collaborative execution function network element according to the logout request message.

[0057] In one possible design, the first intelligent agent is a terminal device or an access network device.

[0058] In a fifth aspect, the present application provides a communication method, the execution subject of the method is a collaborative execution function network element or a module of a collaborative execution function network element in the network, the collaborative execution function network element is a user plane network element, and the network is a core network or an access network. Here, the collaborative execution function network element is used as an example for description as the execution subject. In this method, the collaborative execution function network element receives a second collaborative request message from the collaborative control function network element, the second collaborative request message includes description information of the collaborative task and an identifier of at least one intelligent agent participating in the collaborative task, the at least one intelligent agent includes a first intelligent agent; and sends an execution request message to the first intelligent agent, the execution request message is used to request the first intelligent agent to execute a subtask of the collaborative task.

[0059] In this way, the embodiment of the present application introduces collaborative control function network elements and collaborative execution function network elements in the core network or access network, and jointly controls the intelligent body to complete collaborative tasks through the collaborative control function network elements and collaborative execution function network elements. Since the transmission delay between the network elements in the core network or access network and the intelligent body is relatively small, it is easy to meet the collaborative needs of low-latency services.

[0060] In one possible design, the method further includes: receiving the execution result of the subtask from the first intelligent agent; and sending the execution result of the subtask to the collaborative control function network element.

[0061] In one possible design, the method further includes: receiving collaborative configuration response information from the first agent, where the collaborative configuration response information is used to indicate that the configuration of the first agent is successful.

[0062] In one possible design, the first intelligent agent is a terminal device or an access network device.

[0063] In a sixth aspect, the present application provides a communication method, wherein the execution subject of the method is a first agent or a module of the first agent. The method is described herein using the first agent as the execution subject as an example. In the method, the first agent receives an execution request message from a collaborative execution function network element in a network, wherein the execution request message is used to request the first agent to execute a subtask of a collaborative task; wherein the network is an access network or a core network; and the subtask is executed according to the execution request message.

[0064] In one possible design, the method further includes: sending status information of the first agent to a collaborative control function network element in the network, where the status information is used to indicate the status of the first agent.

[0065] In one possible design, the state of the first agent includes at least one of the following: the network connection state of the first agent; the computing resource state of the first agent; the location state of the first agent; the power state of the first agent; the motion state of the first agent; and the memory state of the first agent.

[0066] In one possible design, the method further includes: receiving status request information from a collaborative control function network element in the network, wherein the status request information is used to request the status information.

[0067] In one possible design, the method further includes: sending capability information of the first agent to a collaborative control function network element in the network.

[0068] In one possible design, the capability information of the first agent is used to indicate the type of data that the first agent supports perceiving and / or the type of task that the first agent supports executing.

[0069] In one possible design, sending the capability information of the first intelligent agent to the collaborative control function network element in the network includes: sending a registration request message to the collaborative control function network element, wherein the registration request message includes the capability information.

[0070] In one possible design, the method also includes: receiving collaborative configuration request information from a collaborative control function network element in the network, the collaborative configuration request information including configuration parameters required for the first intelligent agent to participate in the collaborative task; and sending collaborative configuration response information to the collaborative control function network element, the collaborative configuration response information being used to indicate that the configuration of the first intelligent agent is successful.

[0071] In one possible design, the method further includes: sending the execution result of the subtask to the collaborative execution function network element.

[0072] In one possible design, the method further includes: sending a deregistration request message to a collaborative control function network element in the network.

[0073] In one possible design, the first intelligent agent is a terminal device or an access network device.

[0074] In a seventh aspect, the present application provides a communication method, in which the execution subject of the method is a second agent or a module of the second agent. Here, the second agent is described as an example of the execution subject. In this method, the second agent sends a first collaborative request message to a collaborative control function network element in the network, wherein the first collaborative request message includes description information of the collaborative task; wherein the network is an access network or a core network; and receives a collaborative response message from the collaborative control function network element, wherein the collaborative response message includes the execution result of the collaborative task.

[0075] In one possible design, the second intelligent agent is a terminal device or an access network device.

[0076] The communication methods provided in the fifth to seventh aspects above correspond to the fourth aspect, and the beneficial effects of the relevant technical features can refer to the description of the fourth aspect.

[0077] In an eighth aspect, the present application provides a communication method, wherein the execution subject of the method is a collaborative control function network element or a module of the collaborative control function network element in the network, the collaborative control function network element is a control plane network element, and the network is a core network or an access network. Here, the collaborative control function network element is used as an example for description as the execution subject. In this method, the collaborative control function network element receives a registration request message from a first intelligent agent, the registration request message includes capability information of the first intelligent agent, and the capability information includes data information supported by the first intelligent agent for perception and / or task information supported by the first intelligent agent for execution; and sends a registration response message to the first intelligent agent.

[0078] In one possible design, the method further includes: receiving an update request message from the first agent; and updating capability information of the first agent according to the update request message.

[0079] In one possible design, the method also includes: receiving a logout request message from the first intelligent agent; releasing the connection between the first intelligent agent and the collaborative control function network element, and / or releasing the connection between the first intelligent agent and the collaborative execution function network element according to the logout request message of the first intelligent agent.

[0080] In one possible design, the first intelligent agent is a terminal device or an access network device.

[0081] Ninthly, the present application provides a communication method, the execution subject of the method is a first agent or a module of the first agent. Here, the first agent is used as an example for description. In this method, the first agent sends a registration request message to the collaborative control function network element in the network, and the registration request message includes the capability information of the first agent, and the capability information includes the data information supported by the first agent for perception and / or the task information supported by the first agent for execution; wherein, the network is an access network or a core network; and receives a registration response message from the collaborative control function network element.

[0082] In one possible design, the method further includes: sending an update request message to the collaborative control function network element, where the update request message is used to update the capability information of the first intelligent agent.

[0083] In one possible design, the method further includes: sending a deregistration request message to the collaborative control function network element.

[0084] In one possible design, the first intelligent agent is a terminal device or an access network device.

[0085] In the tenth aspect, the present application provides a communication device, which has the ability to implement the functions involved in any one of the first to ninth aspects above. For example, the communication device includes modules or units or means corresponding to the operations involved in any one of the first to ninth aspects above. The functions or units or means can be implemented through software, or through hardware, or the corresponding software can be implemented through hardware.

[0086] In one possible design, the communication device includes a processing unit and a communication unit. The communication unit can be used to send and receive signals to enable communication between the communication device and other devices; the processing unit can be used to perform certain internal operations of the communication device. The functions performed by the processing unit and the communication unit can correspond to the operations described in any of the first to ninth aspects above.

[0087] In one possible design, the communication device includes a processor, which can be coupled to a memory. The memory can store the necessary computer programs or instructions for implementing the functions of any of the first to ninth aspects. The processor can execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the communication device implements the method of any possible design or implementation of the first to ninth aspects.

[0088] In one possible design, the communication device includes a processor and a memory, and the memory may store the necessary computer programs or instructions for implementing the functions of any of the first to ninth aspects described above. The processor may execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the communication device implements the method of any possible design or implementation of the first to ninth aspects described above.

[0089] In one possible design, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method in any possible design or implementation of the first to ninth aspects above.

[0090] In the above tenth aspect, the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. In addition, the above processors can be one or more, and the memories can be one or more. The memory can be integrated with the processor, or the memory and the processor can be set separately. In the specific implementation process, the memory can be integrated with the processor on the same chip, or can be set on different chips respectively. The embodiment of the present application does not limit the type of memory and the setting method of the memory and the processor.

[0091] In the eleventh aspect, the present application provides a communication system, which may include a collaborative control function network element, a first intelligent agent and a second intelligent agent in a network, and the network is a core network or an access network; wherein the collaborative control function network element is used to execute the method described in any possible design of the first aspect above, the first intelligent agent is used to execute the method described in any possible design of the second aspect above, and the second intelligent agent is used to execute the method described in any possible design of the third aspect above.

[0092] Alternatively, the communication system may include a collaborative control function network element in a network, a collaborative execution function network element in the network, a first intelligent agent and a second intelligent agent, and the network is a core network or an access network; wherein the collaborative control function network element is used to execute the method described in any possible design of the fourth aspect above, the collaborative execution function network element is used to execute the method described in any possible design of the fifth aspect above, the first intelligent agent is used to execute the method described in any possible design of the sixth aspect above, and the second intelligent agent is used to execute the method described in any possible design of the seventh aspect above.

[0093] Alternatively, the communication system includes a collaborative control function network element and a first intelligent entity in a network, and the network is a core network or an access network; wherein the collaborative control function network element is used to execute the method described in any possible design of the above-mentioned eighth aspect, and the first intelligent entity is used to execute the method described in any possible design of the above-mentioned ninth aspect.

[0094] In the twelfth aspect, the present application provides a computer-readable storage medium, in which computer-readable instructions are stored. When a computer reads and executes the computer-readable instructions, the computer executes the method in any possible design of the above-mentioned first to ninth aspects.

[0095] Exemplarily, a computer-readable storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, a computer-readable medium can include a non-transitory computer-readable medium, a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a CD-ROM or other optical disk storage, a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0096] In a thirteenth aspect, the present application provides a computer program product, which, when read and executed by a computer, enables the computer to execute the method in any possible design of the above-mentioned first to ninth aspects.

[0097] In the fourteenth aspect, the present application provides a chip (or chip system), which includes a processor, and the processor is coupled to a memory, and is used to read and execute a software program stored in the memory to implement the method in any possible design of the first to ninth aspects above. BRIEF DESCRIPTION OF THE DRAWINGS

[0098] FIG1 is a schematic diagram of a network architecture applicable to an embodiment of the present application;

[0099] FIG2 is a schematic diagram of a more specific network architecture applicable to an embodiment of the present application;

[0100] FIG3A is a schematic diagram of a collaborative control function network element and a collaborative execution function network element introduced into a core network according to an embodiment of the present application;

[0101] FIG3B is a schematic diagram of a collaborative control function network element and a collaborative execution function network element introduced into an access network according to an embodiment of the present application;

[0102] FIG4 is a schematic diagram of the registration process of an agent provided in an embodiment of the present application;

[0103] FIG5 is a schematic diagram of an update process of an intelligent agent provided in an embodiment of the present application;

[0104] FIG6 is a schematic diagram of the cancellation process of an agent provided in an embodiment of the present application;

[0105] FIG7 is a flow chart of the communication method according to the first embodiment of the present application;

[0106] FIG8 is a flow chart of the communication method according to the second embodiment of the present application;

[0107] FIG9 is a flow chart of the communication method according to the third embodiment of the present application;

[0108] FIG10 is a flow chart of the communication method according to the fourth embodiment of the present application;

[0109] FIG11 is a possible exemplary block diagram of a device involved in an embodiment of the present application;

[0110] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0111] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. This application will present various aspects, embodiments, or features around a system that may include multiple devices, components, modules, etc. Each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. In addition, combinations of these solutions may also be used.

[0112] In the embodiments of the present application, words such as "exemplarily" and "such as" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as an "example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the word "example" is intended to present concepts in a concrete way. In the embodiments of the present application, "of", "corresponding, relevant" and "corresponding" can sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings to be expressed are consistent.

[0113] The technical solutions in the embodiments of the present application can be applied to various communication systems, such as universal mobile telecommunications system (UMTS), wireless local area network (WLAN), wireless fidelity (Wi-Fi) system, 4th generation (4G) communication system, such as long term evolution (LTE) system, 5G communication system, such as new radio (NR) system, and future evolved communication system, such as sixth generation (6G) mobile communication system. In particular, the technical solutions in the embodiments of the present application can also be applied to information technology (IT) system.

[0114] Figure 1 is a schematic diagram of the network architecture of a communication system applicable to this application. The network architecture includes four components: terminal equipment, access network (AN), core network (CN), and data network (DN). The access network can be a radio access network (RAN).

[0115] Terminal devices, access networks, and core networks are the main components of the aforementioned network architecture. Logically, they can be divided into the user plane and the control plane. The control plane is responsible for managing the mobile network, while the user plane is responsible for transmitting service data. For example, as shown in Figure 1, in a 5G communication system, the next generation (NG) 2 reference point is located between the (radio) access network control plane and the core network control plane, the NG3 reference point is located between the (radio) access network user plane and the core network user plane, and the NG6 reference point is located between the core network user plane and the data network.

[0116] The following is a detailed introduction to the various components of the above network architecture.

[0117] (1) Terminal equipment

[0118] Terminal equipment is a device that provides voice and / or data connectivity to users. Terminal equipment can also be called user equipment (UE), terminal, access terminal, terminal unit, terminal station, mobile station (MS), remote station, remote terminal, mobile terminal (MT), wireless communication device, terminal agent, or terminal device.

[0119] For example, the terminal device may be a handheld device with a wireless connection function, or a vehicle with a communication function, a vehicle-mounted device (such as a vehicle-mounted communication device, a vehicle-mounted communication chip), etc. Currently, some examples of terminal devices include: mobile phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, tablet computers, computers with wireless transceiver capabilities, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0120] The terminal device can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on the water (such as a ship); it can also be deployed in the air (such as an airplane, balloon, or satellite). The embodiments of this application do not limit the specific technology, device form, application scenario, or name used by the terminal device.

[0121] (2) Access network

[0122] The access network, deployed close to terminal devices, provides network access for authorized users in a specific area and determines transmission tunnels of varying quality to transmit user data based on user levels and service requirements. The access network manages and rationally utilizes its own resources, providing access services to terminal devices on demand and forwarding control signals and service data between terminal devices and the core network.

[0123] Access network equipment is deployed in the access network to connect terminal devices to the wireless network. Access network equipment is typically connected to the core network via a wired link (such as a fiber optic cable). Access network equipment is also called RAN equipment / node or base station.

[0124] Exemplarily, the access network equipment may include a base station, an evolved NodeB (eNodeB) in an LTE system or an evolved LTE system (LTE-Advanced, LTE-A), a next generation NodeB (gNB) in a 5G communication system, a transmission reception point (TRP), a baseband unit (BBU), an access point (AP) in a wireless local area network (WLAN), an integrated access and backhaul (IAB) node, a base station in a future mobile communication system, or an access node in a WiFi system. The wireless access network equipment may also be a module or unit that performs some of the functions of a base station, such as a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU may be separately configured or included in the same network element, such as a baseband unit (BBU). The RU may be included in a radio frequency device or a radio frequency unit, for example, in a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).

[0125] Access network equipment can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.). The embodiments of this application do not limit the specific technology, device form, application scenario, and name adopted by the access network equipment. In the embodiments of this application, the access network equipment can be simply referred to as the access network (AN) equipment. Unless otherwise specified, the access network equipment mentioned below can all be access network equipment.

[0126] (3) Core Network

[0127] The core network is responsible for maintaining mobile network subscription data, managing mobile network elements, and providing terminal devices with session management, mobility management, policy management, security authentication and other functions.

[0128] Specifically, it may include: providing network access authentication for the terminal device when the terminal device is attached; allocating network resources for the terminal device when the terminal device has a service request; updating network resources for the terminal device when the terminal device moves; providing a fast recovery mechanism for the terminal device when the terminal device is idle; releasing network resources for the terminal device when the terminal device detaches; providing data routing functions for the terminal device when the terminal device has service data, such as forwarding uplink data to the data network, or receiving downlink data from the data network and forwarding it to the access network, and then sending it to the terminal device.

[0129] (4) Data Network

[0130] Data networks are used to provide business services to users. In actual communication, the client typically resides on a terminal device, while the server typically resides on a data network. Data networks can be private networks, such as local area networks (LANs), external networks not controlled by the operator, such as the Internet, or proprietary networks jointly deployed by operators, such as those providing IP multimedia core network subsystem (IMS) services.

[0131] Figure 2 is a schematic diagram of a more specific network architecture applicable to an embodiment of the present application, which may be a network architecture of a 5G communication system. As shown in Figure 2, the network architecture includes terminal devices, access network devices, various types of core network elements / functional entities, and data networks.

[0132] The core network user plane includes the user plane function (UPF) network element. The core network control plane includes, but is not limited to, the access and mobility management function (AMF) network element, the session management function (SMF) network element, the network exposure function (NEF) network element, the network function repository function (NRF) network element, the policy control function (PCF) network element, and the data storage network element.

[0133] The UPF network element is mainly responsible for connecting to the external network and forwarding user data packets according to the routing rules of the SMF network element, such as sending uplink data to the data network or other UPF network elements, and sending downlink data to other UPF network elements or access network devices.

[0134] The AMF network element is mainly responsible for the access management and mobility management of terminal devices, such as the status maintenance of terminal devices, the reachability management of terminal devices, the forwarding of non-mobility management access layer (mobility management non-access-stratum, MM NAS) messages, and the forwarding of session management (session management, SM) N2 messages.

[0135] The SMF network element is primarily responsible for session management in mobile networks, including establishing sessions for terminal devices and allocating and releasing resources for sessions, including session quality of service (QoS), session paths, and forwarding rules. For example, it allocates Internet Protocol (IP) addresses to terminal devices and selects the UPF network element that provides packet forwarding functions.

[0136] The NEF network element is used to connect the interactions between other network elements within the core network and the core network's external application servers, to provide network capability information to the external application servers, or to provide information from the external application servers to the core network elements.

[0137] The NRF network element is mainly responsible for providing storage and selection functions for network function entity information for other network elements.

[0138] The PCF network element is mainly responsible for user policy management, including the generation of policy authorization, service quality and billing rules, and sends the corresponding rules to the UPF network element through the SMF network element to complete the installation of the corresponding policies and rules.

[0139] Data storage network element, the data storage network element is mainly responsible for data management and control. For example, the data storage network element can be a unified data management (UDM) network element and / or a unified data repository (UDR) network element. Figure 2 illustrates the data storage network element as a UDM network element. The UDM network element can manage the user's contract information, including obtaining contract information and providing it to other network elements (such as the AMF network element); generating 3GPP authentication credentials for the terminal device; and registering and maintaining the network element currently serving the terminal device (for example, the AMF represented by AMF ID1 is the current serving AMF of the terminal device, i.e., serving AMF). The functions of the UDM network element can be realized through interaction with the UDR network element. The UDR network element is used to store the data required by the UDM network element to perform its operations. In actual implementation, the UDM network element and the UDR network element can be two independent physical entities, or the UDR network element can also be integrated into the UDM network element, without limitation.

[0140] Although not shown, the above network architecture may also include other possible network elements, which are not specifically limited.

[0141] Figure 2 illustrates the core network control plane using a service-oriented architecture as an example. In the service-oriented architecture, each control plane network element is connected to a service bus, and the interaction between the control plane network elements adopts the service call method, that is, the control plane network element will open services to other control plane network elements for other control plane network elements to call. In other possible implementations, the core network control plane can also adopt a point-to-point communication method. In point-to-point communication, there will be a set of specific messages on the communication interface between the control plane network elements. Among them, the interface between the terminal device and the AMF network element is called the N1 interface, the interface between the access network device and the AMF network element is called the N2 interface, the interface between the access network device and the UPF network element is called the N3 interface, the interface between the UPF network element and the SMF network element can be called the N4 interface, and the interface between the UPF network element and the data network is called the N6 interface. Of course, in future communication systems, the names of these interfaces may remain unchanged, or may be replaced by other names, and this application is not limited to this. In future communication systems such as the sixth generation (6G) communication system, the above-mentioned network elements or devices may still use their names in the fourth generation (4G) or 5G communication system, or have other names; the functions of the above-mentioned network elements or devices may be performed by an independent network element or by several network elements together, and the embodiments of the present application are not limited to this.

[0142] The network elements / functional entities in the above-mentioned various possible network architectures can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). Optionally, the above-mentioned network elements or functional entities can be implemented by one device, or by multiple devices together, or they can be different functional modules within a device. The embodiments of the present application do not specifically limit this. In actual deployment, the above-mentioned network elements can be combined. For example, the access and mobility management function network element can be combined with the session management function network element; the session management function network element can be combined with the user plane function network element. When two network elements are combined, the interaction between the two network elements provided by the embodiments of the present application becomes the internal operation of the combined network element or can be omitted.

[0143] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of communication system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0144] Taking the 5G communication system shown in Figure 2 as an example, one possible implementation for achieving multi-agent collaboration is to control multiple agents (i.e., multiple terminal devices) through a cloud server deployed in the data network to collaboratively complete a task. However, because the transmission latency between the cloud server and the terminal device fluctuates between 20 and 75 milliseconds (ms), it is impossible to guarantee low-latency, highly reliable services, such as the maximum transmission latency of less than 20ms required in autonomous driving scenarios.

[0145] Based on this, the embodiments of this application will study the relevant implementation of multi-agent collaboration. For example, the embodiments of this application provide a communication method for controlling agents to complete collaborative tasks through network elements in the core network or access network, thereby reducing transmission latency and meeting the collaborative requirements of low-latency services.

[0146] The embodiment of the present application introduces a collaborative control function network element in the core network or access network, and optionally, also introduces a collaborative execution function network element. The collaborative control function network element can also be called a multi-agent collaborative control function (MACF) network element, and the collaborative execution function network element can also be called a multi-agent collaborative execution function (MAEF) network element. The embodiment of the present application does not limit the specific names. Exemplarily, the collaborative control function network element can be located in the control plane, that is, the collaborative control function network element belongs to the control plane network element; the collaborative execution function network element can be located in the user plane, that is, the collaborative execution function network element belongs to the user plane network element.

[0147] When a collaborative control function network element and a collaborative execution function network element are introduced into a core network, the collaborative control function network element or the collaborative execution function network element may be co-located with other network elements in the core network, i.e., the functions of the collaborative control function network element or the collaborative execution function network element are performed by other network elements; or, the collaborative control function network element or the collaborative execution function network element may be a separately configured network element. When a collaborative control function network element and a collaborative execution function network element are introduced into an access network, the collaborative control function network element or the collaborative execution function network element may be co-located with other network elements in the access network, i.e., the functions of the collaborative control function network element or the collaborative execution function network element are performed by other network elements; or, the collaborative control function network element or the collaborative execution function network element may be a separately configured network element. Refer to Figures 3A and 3B. Figure 3A is an example of introducing collaborative control function network elements and collaborative execution function network elements in the core network. In Figure 3A, the collaborative control function network element and the collaborative execution function network element are set separately; Figure 3B is an example of introducing collaborative control function network elements and collaborative execution function network elements in the access network. In Figure 3B, the collaborative control function network element is located in the CU, and the collaborative execution function network element can be located in the DU.

[0148] The collaborative control function network element is used to control the intelligent agent to complete the collaborative task, or the collaborative control function network element and the collaborative execution function network element jointly control the intelligent agent to complete the collaborative task. The intelligent agent can be an intelligent device, such as a robot, smart car, or smartphone with intelligent technology. In the 5G communication system, the intelligent agent can be a terminal device or a network device, and the network device can be an access network device or a core network element.

[0149] The following first explains the relevant terms involved in the embodiments of this application. When not specifically explained, these explanations are intended to support the meaning of the relevant terms and make the embodiments of this application easier to understand, and should not be regarded as strict limitations on the relevant terms in the scope of protection claimed by this application.

[0150] (1) Collaborative tasks

[0151] A collaborative task can also be called a collaborative task, a cooperative task, or an assisting task. A collaborative task may refer to a task that cannot be completed by the initiator and requires the collaboration of at least one intelligent agent. That is, the intelligent agents participating in the collaborative task include at least one intelligent agent.

[0152] Among them, the initiator of the collaborative task can be a third-party application terminal or a third-party application server; or, the initiator of the collaborative task can also be an agent. The embodiment of the present application does not limit the initiator of the collaborative task. For example, the initiator of the collaborative task may not participate in the collaborative task, and the collaborative task is completed by multiple agents participating in the collaborative task. The multiple agents participating in the collaborative task can respectively perform the subtasks of the collaborative task. For example, the agents participating in the collaborative task include agent 1 and agent 2, then agent 1 can perform subtask 1 of the collaborative task, and agent 1 can perform subtask 2 of the collaborative task; for example, subtask 1 or subtask 2 can be part of the collaborative task, that is, agent 1 performs part of the collaborative task, and agent 2 performs another part of the collaborative task, that is, agent 1 and agent 2 complete the collaborative task together. In some special scenarios, there can be only one agent participating in the collaborative task (such as agent 1), and the subtask performed by agent 1 can be the collaborative task itself. In this case, since it does not involve the collaboration of multiple agents, "collaborative task" can also be replaced by "task". The embodiments of the present application are mainly described using the example of "multiple intelligent agents participating in a collaborative task".

[0153] The collaborative tasks in the embodiments of the present application can be computing tasks, such as model training. For example, if the computing center (e.g., central processing unit) of agent A is too busy to execute the computing task, it can request one or more other agents to collaboratively complete the computing task. Alternatively, the collaborative tasks can be perception tasks, such as those involving the detection and / or collection of perception data. For example, if the sensor of agent A is blocked and it is unable to execute the perception task, it can request one or more other agents to collaboratively complete the perception task.

[0154] (2) Agent Registration

[0155] After the collaborative control function network element is introduced in the embodiment of this application, the intelligent agent can register with the collaborative control function network element to facilitate the collaborative control function network element to centrally and collaboratively control the intelligent agent. The following uses "the collaborative control function network element as a network element in the core network and the intelligent agent as a terminal device" as an example to describe a possible registration process in conjunction with Figure 4.

[0156] FIG4 is a schematic diagram of the registration process of an agent provided in an embodiment of the present application. As shown in FIG4 , the process may include:

[0157] S401, the agent sends a registration request message to the AMF network element.

[0158] Here, the intelligent agent can send a registration request message to the AMF network element through the access network device, and the registration request message can be a non-access layer message.

[0159] Exemplarily, the registration request message may include the capability information of the agent, and the capability information of the agent is used to indicate the type of data that the agent supports perceiving and / or the type of task that the agent supports performing. Among them, the type of data that the agent supports perceiving may include at least one of the following: video data, position data, image data, and radar data. The type of task that the agent supports performing may include at least one of the following: object detection and image-to-text. Among them, object detection may refer to detecting a specific target (such as detecting a person, a vehicle, etc.). Optionally, the registration request message also includes other possible information, such as message type information, manufacturer information to which the agent belongs, device type of the agent (such as a mobile phone, a vehicle, a robot, etc.), identification of the network to which the agent is connected, message format requirements for agent requests and responses, etc., which are not specifically limited. As shown in Table 1, this is an example of the format of a registration request message.

[0160] Table 1: Example of the format of a registration request message

[0161] S402, the AMF network element forwards the registration request message to the collaborative control function network element.

[0162] S403, the collaborative control function network element queries the UDM for the contract data of the intelligent entity.

[0163] For example, the specific implementation of the collaborative control network element querying the UDM for the contract data of the intelligent body can refer to the implementation of the PCF network element or other network elements querying the UDM for the contract data of the intelligent body in the prior art, and will not be repeated here.

[0164] S404, the collaborative control function network element configures and authenticates the intelligent agent, and persistently stores the registration request message.

[0165] For example, the specific implementation of the configuration and authentication of the intelligent body by the collaborative control function network element can refer to the implementation of the configuration and authentication of the intelligent body by the PCF network element or other network elements in the prior art, and will not be repeated here.

[0166] S405, the control function network element sends a registration response message to the AMF network element.

[0167] Exemplarily, the registration response message may include an identifier assigned by the collaborative control function network element to the agent. The collaborative control function network element may maintain a list of identifiers of registered agents, and the collaborative control function network element may assign different identifiers to different agents.

[0168] S406, the AMF network element forwards the registration response message to the agent; accordingly, the agent receives the registration response message and completes the registration.

[0169] (3) Agent Update

[0170] After the agent completes registration with the collaborative control function network element, if the agent's capability information changes, an agent update process can be initiated to facilitate the collaborative control function network element to update the agent's capability information. The agent can also initiate the agent update process due to other triggering reasons, which are not limited to specific reasons. The following uses "the collaborative control function network element is a network element in the core network and the agent is a terminal device" as an example to describe a possible update process in conjunction with Figure 5.

[0171] FIG5 is a schematic diagram of an agent update process according to an embodiment of the present application. As shown in FIG5 , the process may include:

[0172] S501, the agent sends an update request message to the AMF network element.

[0173] Here, the update request message may include the identity of the agent and the updated capability information. Optionally, the update request message may also include other possible contents, which are not specifically limited.

[0174] For example, the capability information carried by an agent in a registration request message is: {"SensingData":["video","positioning","image","radar"],"Action":["object-detection","image-to-text"]}. If the agent's capabilities change, such as if the agent no longer supports sensing position data, the updated capability information may be: {"SensingData":["video","image","radar"],"Action":["object-detection","image-to-text"]}. Table 2 shows an example format for an update request message.

[0175] Table 2: Example of the format of an update request message

[0176] S502, the AMF network element forwards the update request message to the collaborative control function network element.

[0177] S503, the collaborative control function network element updates the capabilities of the intelligent agent, such as persistently storing the updated capability information.

[0178] S504, the collaborative control function network element sends an update response message to the AMF network element.

[0179] S505, the AMF network element forwards the update response message to the agent; accordingly, the agent receives the update response message and completes the update.

[0180] (4) Agent deregistration

[0181] After completing registration with the collaborative control function network element, the agent may initiate the agent deregistration process due to some reasons (such as not being able to participate in collaborative tasks). The following uses the "collaborative control function network element as a network element in the core network and the agent as a terminal device" as an example to describe a possible deregistration process with reference to Figure 6.

[0182] FIG6 is a schematic diagram of the deregistration process of an agent according to an embodiment of the present application. As shown in FIG6 , the process may include:

[0183] S601, the agent sends a deregistration request message to the AMF network element.

[0184] Here, the deregistration request message may include the agent's identifier and message type information, where the message type information indicates that the message is for agent deregistration. Optionally, the deregistration request message may also include other possible contents, which are not specifically limited. Table 3 shows an example format of a deregistration request message.

[0185] Table 3: Example of the format of a logout request message

[0186] S602, the AMF network element forwards the deregistration request message to the collaborative control function network element.

[0187] S603, the collaborative control function network element releases the connection between the intelligent agent and the collaborative control function network element, and deletes the identifier of the intelligent agent.

[0188] Optionally, the coordinated control function network element further releases the connection between the intelligent agent and the coordinated execution function network element, wherein the connection between the intelligent agent and the coordinated control function network element is a control plane connection, and the connection between the intelligent agent and the coordinated execution function network element is a user plane connection.

[0189] Exemplarily, there are multiple implementations of the collaborative control function network element releasing the connection between the intelligent agent and the collaborative control function network element (or collaborative execution function network element), for example, reference may be made to the relevant implementations of releasing the connection in the prior art.

[0190] (5) Agent status information

[0191] The state information of an agent is used to indicate the state of the agent. For example, the state of an agent changes over time, meaning that the state of the agent can be different at different times. For example, the state of an agent includes at least one of the following: the agent's network connection state; the agent's computing resource state; the agent's location state; the agent's power state; the agent's motion state; or the agent's memory state. Each of these items can be understood as a state type. The states listed here are merely examples and are not limited in this embodiment.

[0192] The network connection status of the agent may include: whether the network connection of the agent is normal.

[0193] The computing resource status of the agent may include: the computing resource load of the agent.

[0194] The location status of the agent may include: global positioning system (GPS) data of the agent.

[0195] The power status of the agent may include: the remaining power of the agent.

[0196] The motion state of the intelligent agent may include: the motion trajectory of the intelligent agent and the motion speed of the intelligent agent.

[0197] The memory state of an agent may include: the memory load of the agent.

[0198] Based on the introduction of the above-mentioned related terms, the communication method provided by the embodiment of the present application is described in detail below in combination with Examples 1 to 4. The communication method provided by the embodiment of the present application involves a collaborative control function network element and one or more intelligent agents, and optionally, also involves a collaborative execution function network element. Unless otherwise specified, "intelligent agent" can refer to the intelligent device itself or a component in the device, such as a chip or a chip system.

[0199] Example 1

[0200] In the first embodiment, the implementation of "the collaborative control function network element controls the intelligent agent to complete the collaborative task" will be described.

[0201] FIG7 is a flow chart of the communication method according to the first embodiment of the present application. As shown in FIG7 , the method includes the following steps:

[0202] S701: The initiator of a collaborative task sends first collaborative request information to a collaborative control function network element, where the first collaborative request information includes description information of the collaborative task; accordingly, the collaborative control function network element receives the first collaborative request information.

[0203] For example, the description of a collaborative task might be: Detect people and vehicles at entrance and exit of scenic area A between 8:00 AM and 5:00 PM, and count the total number of people and vehicles. The initiator of the collaborative task is similar to the previous description, for example, the initiator of the collaborative task is an agent (for ease of description, we will refer to it as the second agent).

[0204] S701', the collaborative control function network element determines at least one intelligent agent participating in a collaborative task, where the at least one intelligent agent includes a first intelligent agent.

[0205] Here, there may be multiple ways for the collaborative control function network element to determine at least one intelligent agent participating in the collaborative task. Three possible ways are described below in combination with Ways 1 to 3.

[0206] (1) Method 1

[0207] The collaborative control function network element can determine M1 intelligent agents that meet the capability requirements as intelligent agents participating in the collaborative task based on the capability information of multiple intelligent agents and the capability requirements of the collaborative task for the intelligent agents participating in the collaborative task, or determine M1 intelligent agents that meet the capability requirements to participate in the collaborative task, where M1 is an integer greater than or equal to 1.

[0208] There are various ways for the collaborative control function network element to obtain the agent's capability information. For example, the agent can send capability information to the collaborative control function network element via a registration request message. The collaborative control function network element can then receive the agent's capability information. For details, please refer to the relevant description in Figure 4 above. There are various ways for the collaborative control function network element to obtain capability requirements. For example, the collaborative control function network element can determine capability requirements based on the description information of the collaborative task.

[0209] For example, a collaborative task requires the agents involved to support target detection. Multiple agents include agents 1 through 10. Agent 1's capability information includes {"Action":["object-detection","image-to-text"]}, Agent 2's capability information includes {"Action":["object-detection"]}, and Agent 3's capability information includes {"Action":["object-detection"]}. Agents 4 through 10 do not support target detection. The collaborative control functional network element selects agents 1, 2, and 3 (i.e., M1 = 3) to meet the capability requirements. After the collaborative control functional network element selects agents 1, 2, and 3, it determines that the agents participating in the collaborative task include agents 1, 2, and 3.

[0210] The “agent 1” in the embodiment of the present application may also be replaced by the “first agent”.

[0211] (2) Method 2

[0212] The collaborative control function network element may select M1 intelligent agents that meet the capability requirements from the multiple intelligent agents based on the capability information of the multiple intelligent agents and the capability requirements of the collaborative task for the intelligent agents participating in the collaborative task, with specific reference to the description in Method 1. Furthermore, the collaborative control function network element may determine M2 intelligent agents that meet the status requirements among the M1 intelligent agents as the intelligent agents participating in the collaborative task based on the status information of the M1 intelligent agents and the status requirements of the collaborative task for the intelligent agents participating in the collaborative task, where M2 is an integer greater than or equal to 1. For example, if the M2 intelligent agents that meet the status requirements selected by the collaborative control function network element include intelligent agent 1 and intelligent agent 2, then it can be determined that the intelligent agents participating in the collaborative task include intelligent agent 1 and intelligent agent 2.

[0213] There are multiple ways for the collaborative control function network element to obtain state requirements. For example, the collaborative control function network element can determine the state requirements based on the description of the collaborative task. For example, the state requirements of the collaborative task for the participating intelligent agents include: location requirements (such as being near the entrance and exit of scenic area A), computing resource requirements (such as CPF load less than threshold 1), and memory requirements (such as memory load less than threshold 2).

[0214] There are multiple ways for the collaborative control function network element to obtain the status information of an agent. Here, we use agent 1 as an example to describe one possible implementation (agents 2 and 3 can also be handled similarly). The collaborative control function network element can send a status request message to agent 1, which is used to request the status information of agent 1.

[0215] The status request information may include the agent's identifier and status type information; the status type information indicates the requested status type, such as location status, computing resource status, or memory status. Optionally, the status request information may also include other information, such as the frequency of status reporting, which can be every 10ms or every 30ms, without limitation. Table 4 shows an example format for a status request information.

[0216] Table 4: Example of the format of status request information

[0217] Accordingly, after receiving the status request message, Agent 1 can send a status response message to the collaborative control function network element based on the status request message. The status response message includes the agent's status information; optionally, the status response message also includes other information, such as the agent's identifier and a status monitoring timestamp, though these are not specifically limited. Table 5 shows an example format for a status response message.

[0218] Table 5: Example of status response message format

[0219] The above description is based on the example of "the intelligent agent 1 sends the status information of the intelligent agent 1 to the collaborative control function network element according to the request of the collaborative control function network element", and the embodiments of the present application are not limited to this. For example, the intelligent agent 1 periodically sends the status information of the intelligent agent 1 to the collaborative control function network element; in this case, the status information of the intelligent agent 1 can be full information, that is, indicating all types of status, or the status information of the intelligent agent 1 indicates the status of the default type. For another example, the collaborative control function network element sends a subscription request to the intelligent agent 1 in advance, and the subscription request is used to subscribe to one or more statuses of the intelligent agent 1 (such as subscribing to the location status, computing resource status and memory status of the intelligent agent 1). Then, the intelligent agent 1 can send the status information of the intelligent agent 1 to the collaborative control function network element according to the subscription request.

[0220] (3) Method 3

[0221] The first collaboration request message includes the identities of K1 agents, where K1 is an integer greater than or equal to 1. In other words, the initiator of the collaborative task indicates that these K1 agents can participate in the collaborative task. For example, the K1 agents include Agent 1, Agent 2, and Agent 3.

[0222] Furthermore, the collaborative control function network element can determine, based on the status information of the K1 agents and the status requirements of the collaborative task for the agents participating in the collaborative task, K2 agents from the K1 agents that meet the status requirements as the agents participating in the collaborative task. For example, if the K2 agents selected by the collaborative control function network element that meet the status requirements include agent 1 and agent 2, then the agents participating in the collaborative task can be determined to include agent 1 and agent 2.

[0223] Typically, it can be assumed that the K1 agents indicated by the initiator of the collaborative task meet the capability requirements of the collaborative task for participating agents. Therefore, the collaborative control functional network element does not need to determine whether the K1 agents meet the capability requirements. In other examples, the collaborative control functional network element can also select K3 agents that meet the capability requirements from the K1 agents, and then select K4 agents that meet the status requirements from the K3 agents, and determine that the agents participating in the collaborative task include K4 agents.

[0224] In this way, since the collaborative control function network element takes into account the ability information and / or state information of the intelligent agent when determining the intelligent agent participating in the collaborative task, the determined intelligent agent participating in the collaborative task is more reasonable and accurate.

[0225] The above S701' is an optional step. For example, if the first collaborative request information includes the identifier of at least one intelligent agent participating in the collaborative task, the collaborative control function network element can obtain the intelligent agent participating in the collaborative task based on the first collaborative request information. In this case, there is no need to execute S701'.

[0226] Optionally, the collaborative control function network element determines whether the maximum transmission delay required by the collaborative task is less than or equal to the threshold value based on the description information of the collaborative task. If the maximum transmission delay required by the collaborative task is greater than the threshold value, then execute S702 to S706 in Example 1. If the maximum transmission delay required by the collaborative task is less than or equal to the threshold value, then execute the steps in Example 3. The reason is: in Example 3, the collaborative control function network element and the collaborative execution function network element jointly control the intelligent body to complete the collaborative task. Since the collaborative execution function network element is located on the user plane, under normal circumstances, the transmission delay of the user plane is less than the transmission delay of the control plane. Therefore, by sending execution request information to the intelligent body through the collaborative execution function network element and receiving the execution results of the subtask from the intelligent body, the transmission delay can be more effectively reduced to meet the transmission delay requirements of the collaborative task.

[0227] The collaborative control function network element may also determine whether to execute the steps of Example 1 or Example 3 based on other possible factors (such as the data volume of the collaborative task), and the embodiments of the present application do not limit this.

[0228] S702, the collaborative control function network element sends an execution request message (for the convenience of description, referred to as execution request message 1) to agent 1. Execution request message 1 is used to request agent 1 to execute a subtask of the collaborative task (for the convenience of description, referred to as subtask 1); accordingly, the agent receives execution request message 1.

[0229] Assuming that the agents participating in the collaborative task determined by the collaborative control function network element include agent 1, the collaborative control function network element sends execution request information 1 to agent 1. For example, execution request information 1 may include description information of subtask 1 (optionally, also includes the identifier of agent 1). Optionally, if the agents participating in the collaborative task also include other agents (such as agent 2), the collaborative control function network element may also send execution request information 2 to agent 2. Execution request information 2 is used to request agent 2 to execute subtask 2 of the collaborative task. For example, execution request information 2 may include description information of subtask 2.

[0230] The embodiments of this application do not limit the specific implementation of "how the collaborative control function network element determines subtask 1 and subtask 2 based on the collaborative task." In addition, if the agents participating in the collaborative task determined by the collaborative control function network element only include agent 1, then subtask 1 is the collaborative task itself.

[0231] In one possible implementation, after the collaborative control function network element determines the agents participating in the collaborative task (e.g., agent 1 and agent 2), it may send collaborative configuration request information 1 to agent 1, where collaborative configuration request information 1 includes the configuration parameters required for agent 1 to participate in the collaborative task; and send collaborative configuration request information 2 to agent 2, where collaborative configuration request information 2 includes the configuration parameters required for agent 2 to participate in the collaborative task. Accordingly, agent 1 may be configured according to collaborative configuration request information 1 and send collaborative configuration response information 1 to the collaborative control function network element, where collaborative configuration response information 1 is used to indicate whether agent 1 has been successfully configured or failed; agent 2 may be configured according to collaborative configuration request information 2 and send collaborative configuration response information 2 to the collaborative control function network element, where collaborative configuration response information 2 is used to indicate whether agent 2 has been successfully configured or failed. If both agent 1 and agent 2 are configured successfully, the collaborative control function network element can send execution request information 1 to agent 1 and execution request information 2 to agent 2; or, if agent 1 is configured successfully and agent 2 fails to be configured, the collaborative control function network element can send execution request information 1 to agent 1. Execution request information 1 is used to request agent 1 to execute subtask 1 of the collaborative task, and subtask 1 is the collaborative task itself.

[0232] Taking collaborative configuration request information 1 as an example, for example, collaborative configuration request information 1 includes: {'task':'object-detection','args':{'starttime':'08:00','endtime':'09:00','object':['people','vehicle'],'frequency':1min}}, that is, the start time of the target detection task is 08:00, the end time is 09:00, the targets include people and vehicles, and the detection frequency is once every 1 minute.

[0233] S703, agent 1 executes the subtask (ie, subtask 1) of the collaborative task according to execution request information 1.

[0234] S704, agent 1 sends feedback information 1 to the collaborative control function network element, where feedback information 1 includes the execution result of the subtask (ie, subtask 1); accordingly, the collaborative control function network element receives the execution result of subtask 1.

[0235] Optionally, the feedback information 1 also includes the identification of the agent 1 .

[0236] Optionally, the intelligent agent 2 sends feedback information 2 to the collaborative control function network element, where the feedback information 2 includes the execution result of the subtask 2, and the collaborative control function network element receives the execution result of the subtask 2.

[0237] S705 , the collaborative control function network element determines the execution result of the collaborative task according to the execution result of the subtask (ie, subtask 1 ).

[0238] For example, if subtask 1 is the collaborative task itself, the collaborative control function network element can directly use the execution result of subtask 1 as the execution result of the collaborative task; or, the collaborative control function network element can also perform some possible processing on the execution result of subtask 1 to obtain the execution result of the collaborative task.

[0239] If the collaborative task includes subtask 1 and subtask 2, the collaborative control function network element determines the execution result of the collaborative task based on the execution results of subtask 1 and subtask 2. For example, the collaborative control function network element can directly use the execution results of subtask 1 and subtask 2 as the execution result of the collaborative task; for another example, the collaborative control function network element can perform some possible processing (such as aggregation or merging) on ​​the execution results of subtask 1 and subtask 2 to obtain the execution result of the collaborative task. This example uses two subtasks. When there are more subtasks, the same processing can be used.

[0240] In one possible implementation, for example, the agents participating in the collaborative task include agent 1 and agent 2. Taking agent 1 as an example, if agent 1 fails to execute subtask 1, it can send an execution failure message to the collaborative control function network element. If agent 1 successfully executes subtask 1, it can send the execution result of subtask 1 to the collaborative control function network element. Therefore, the collaborative control function network element can determine whether all multiple subtasks of the collaborative task are successfully executed. If all are successfully executed, the execution result of the collaborative task is determined based on the execution results of these subtasks. If not all are successfully executed, the agents participating in the collaborative task can be re-determined, and the execution task information can be sent to the determined agents to facilitate the continuation of the unfinished subtasks.

[0241] S706 , the collaborative control function network element sends the execution result of the collaborative task to the initiator of the collaborative task; correspondingly, the initiator of the collaborative task receives the execution result of the collaborative task.

[0242] Optionally, after reporting the execution result of subtask 1, intelligent agent 1 sends a deregistration request message to the collaborative control function network element, and then the collaborative control function network element can release the connection between intelligent agent 1 and the collaborative control function network element. For details, please refer to the relevant description corresponding to Figure 6 in the previous text.

[0243] By adopting the above method, a collaborative control function network element is introduced into the core network or access network, and the collaborative control function network element is used to control the intelligent agent to complete the collaborative task. Since the transmission delay between the network element in the core network or access network and the intelligent agent is less than the transmission delay of the communication between the cloud server and the intelligent agent, it is easy to meet the collaborative needs of low-latency services.

[0244] Example 2

[0245] In Example 2, based on Example 1, a specific implementation process will be described, taking the initiator of the collaborative task as the second agent and the agents participating in the collaborative task as Agent 1 and Agent 2. When the agents participating in the collaborative task include more than two agents, the implementation process can be referred to.

[0246] FIG8 is a flow chart of the communication method according to the second embodiment of the present application. As shown in FIG8 , the method includes the following steps:

[0247] S801, the second intelligent agent sends a first coordination request message to a coordination control function network element in a network, which is an access network or a core network; accordingly, the coordination control function network element receives the first coordination request message.

[0248] Exemplarily, the first collaboration request information includes description information of the collaborative task.

[0249] S802, the collaborative control function network element determines an agent that meets the capability requirements from multiple registered agents, such as agent 1 and agent 2.

[0250] S803, the collaborative control function network element sends status request information 1 to agent 1, where the status request information 1 is used to request status information of agent 1; accordingly, agent 1 receives the status request information 1.

[0251] S804, the collaborative control function network element sends status request information 2 to agent 2, where the status request information 2 is used to request status information of agent 2; accordingly, agent 2 receives the status request information 2.

[0252] S805, agent 1 sends the status information of agent 1 to the collaborative control function network element according to the status request information 1.

[0253] S806, agent 2 sends the status information of agent 2 to the collaborative control function network element according to the status request information 2.

[0254] S807, the collaborative control function network element determines that both agent 1 and agent 2 meet the status requirements of the collaborative task for the agents participating in the collaborative task based on the status information of agent 1 and the status information of agent 2, and then determines that the agents participating in the collaborative task include agent 1 and agent 2.

[0255] S808, the collaborative control function network element sends collaborative configuration request information 1 to agent 1, where the collaborative configuration request information 1 includes configuration parameters required for agent 1 to participate in the collaborative task; accordingly, agent 1 receives the collaborative configuration request information 1.

[0256] S809, the collaborative control function network element sends collaborative configuration request information 2 to agent 2, where the collaborative configuration request information 2 includes configuration parameters required for agent 2 to participate in the collaborative task; accordingly, agent 2 receives the collaborative configuration request information 2.

[0257] S810, agent 1 sends collaborative configuration response information 1 to the collaborative control function network element according to collaborative configuration request information 1, and collaborative configuration response information 1 is used to indicate that the configuration of agent 1 is successful.

[0258] S811, agent 2 sends collaborative configuration response information 2 to the collaborative control function network element according to collaborative configuration request information 2, and collaborative configuration response information 2 is used to indicate that the configuration of agent 2 is successful.

[0259] S812, after the collaborative control function network element determines that the configuration of intelligent agent 1 is successful, it sends execution request information 1 to intelligent agent 1, and execution request information 1 is used to request intelligent agent 1 to execute subtask 1 of the collaborative task; accordingly, intelligent agent 1 receives execution request information 1 and executes subtask 1 according to execution request information 1.

[0260] S813, after the collaborative control function network element determines that the configuration of intelligent agent 2 is successful, it sends execution request information 2 to intelligent agent 2, and execution request information 2 is used to request intelligent agent 2 to execute subtask 2 of the collaborative task; accordingly, intelligent agent 2 receives execution request information 2 and executes subtask 2 according to execution request information 2.

[0261] S814, agent 1 executes subtask 1 according to execution request information 1 and obtains the execution result of subtask 1.

[0262] S815, agent 1 sends the execution result of subtask 1 to the collaborative control function network element; correspondingly, the collaborative control function network element receives the execution result of subtask 1.

[0263] S816, agent 2 executes subtask 2 according to execution request information 2 and obtains the execution result of subtask 2.

[0264] S817, agent 2 sends the execution result of subtask 2 to the collaborative control function network element; correspondingly, the collaborative control function network element receives the execution result of subtask 2.

[0265] S818 , the collaborative control function network element determines the execution result of the collaborative task according to the execution result of subtask 1 and the execution result of subtask 2.

[0266] S819, the collaborative control function network element sends the execution result of the collaborative task to the second agent; correspondingly, the second agent receives the execution result of the collaborative task.

[0267] The process illustrated in FIG8 corresponds to the process illustrated in FIG7 , and the steps of the two can refer to each other. For example, S801 can refer to S701, S802 to S807 can refer to S701′, S808 to S813 can refer to S702, S814 and S816 can refer to S703, S815 and S817 can refer to S704, S818 can refer to S705, and S819 can refer to S706.

[0268] In addition, in the above-mentioned embodiment 1 and embodiment 2, when the collaborative control function network element is located in the core network, the intelligent agent participating in the collaborative task (such as intelligent agent 1) can be a terminal device, or it can also be an access network device. If intelligent agent 1 is a terminal device, intelligent agent 1 and the collaborative control function network element can communicate through non-access layer messages. If intelligent agent 1 is an access network device, intelligent agent 1 and the collaborative control function network element can communicate through the AMF network element (for example, intelligent agent 1 sends information to the AMF network element through the N2 interface message, and then the AMF network element forwards the information to the collaborative control function network element).

[0269] When the collaborative control function network element is located in the access network, for example, the collaborative control function network element is located in the CU, in this case, the intelligent agent participating in the collaborative task (such as intelligent agent 1) can be a terminal device, or it can also be an access network device (such as DU). If intelligent agent 1 is a terminal device, intelligent agent 1 and the collaborative control function network element can communicate through air interface messages. If intelligent agent 1 is a DU, intelligent agent 1 and the collaborative control function network element can communicate through F1 interface messages (F1 interface is the interface between CU and DU).

[0270] In addition, when the initiator of the collaborative task is an intelligent agent (such as the second intelligent agent), the communication method between the second intelligent agent and the collaborative control function network element can refer to the communication method between intelligent agent 1 and the collaborative control function network element.

[0271] Example 3

[0272] In the third embodiment, the implementation of "the collaborative control function network element and the collaborative execution function network element jointly controlling the intelligent body to complete the collaborative task" will be described.

[0273] FIG9 is a flow chart of the communication method according to the third embodiment of the present application. As shown in FIG9 , the method includes the following steps:

[0274] S901: The initiator of a collaborative task sends first collaborative request information to a collaborative control function network element, where the first collaborative request information includes description information of the collaborative task; accordingly, the collaborative control function network element receives the first collaborative request information.

[0275] S901′, the collaborative control function network element determines at least one intelligent agent participating in a collaborative task, where the at least one intelligent agent includes a first intelligent agent.

[0276] For example, the specific implementation of S901 may refer to S701 of the first embodiment, and the specific implementation of S901′ may refer to S701′ of the first embodiment, which will not be described in detail.

[0277] S902, the collaborative control function network element sends a second collaborative request message to the collaborative execution function network element, where the second collaborative request message includes description information of the collaborative task and the identifier of at least one intelligent entity participating in the collaborative task; accordingly, the collaborative execution function network element receives the second collaborative request message.

[0278] Exemplarily, after the collaborative control function network element determines at least one agent participating in the collaborative task (such as agent 1 and agent 2), it can determine the collaborative execution function network elements corresponding to agent 1 and agent 2. Among them, agent 1 and agent 2 can correspond to the same collaborative execution function network element, such as collaborative execution function network element 1, and the collaborative control function network element sends a second collaborative request message to collaborative execution function network element 1. Alternatively, agent 1 and agent 2 can correspond to different collaborative execution function network elements, such as agent 1 corresponds to collaborative execution function network element 1, and agent 2 corresponds to collaborative execution function network element 2, and the collaborative control function network element sends collaborative request information 1 to collaborative execution function network element 1, and collaborative request information 1 includes description information of the collaborative task and an identifier of at least one agent (or an identifier of the agent corresponding to collaborative execution function network element 1, such as an identifier of agent 1); and the collaborative control function network element sends collaborative request information 2 to collaborative execution function network element 2, and collaborative request information 2 includes description information of the collaborative task and an identifier of at least one agent (or an identifier of the agent corresponding to collaborative execution function network element 2, such as an identifier of agent 2).

[0279] The correspondence between the agent and the collaborative execution function network element may be preconfigured or predefined, and this embodiment of the application does not limit this. The following description takes "agent 1 and agent 2 may correspond to the same collaborative execution function network element" as an example.

[0280] In addition, after the collaborative control function network element determines the collaborative execution function network element corresponding to agent 1 and agent 2, it can send notification information 1 to agent 1. Notification information 1 is used to notify agent 1 to establish a connection with the collaborative execution function network element. For example, notification information 1 includes the identifier of the collaborative execution function network element. Accordingly, agent 1 establishes a connection with the collaborative execution function network element according to notification information 1. Furthermore, the collaborative control function network element can send notification information 2 to agent 2. Notification information 2 is used to notify agent 2 to establish a connection with the collaborative execution function network element. For example, notification information 2 includes the identifier of the collaborative execution function network element. Accordingly, agent 2 establishes a connection with the collaborative execution function network element according to notification information 2.

[0281] Optionally, after the collaborative control function network element determines the agents participating in the collaborative task (e.g., agent 1 and agent 2), it may also send collaborative configuration request information 1 to agent 1 and collaborative configuration request information 2 to agent 2. Accordingly, agent 1 sends collaborative configuration response information 1 to the collaborative execution function network element via the connection between agent 1 and the collaborative execution function network element based on collaborative configuration request information 1; and agent 2 sends collaborative configuration response information 2 to the collaborative execution function network element via the connection between agent 2 and the collaborative execution function network element based on collaborative configuration request information 2. The collaborative configuration request information and collaborative configuration response information may refer to the description of Example 1.

[0282] Further optionally, taking agent 1 as an example, the collaborative control function network element instructs agent 1 to send collaborative configuration response information 1 to the collaborative execution function network element, rather than sending collaborative configuration response information 1 to the collaborative control function network element. There are many specific instruction methods, which are not limited in the embodiments of the present application. Alternatively, the protocol predefines "the agent sends collaborative configuration response information to the collaborative execution function network element."

[0283] S903, the collaborative execution function network element sends an execution request message (for the convenience of description, referred to as execution request message 1) to agent 1. Execution request message 1 is used to request agent 1 to execute a subtask of the collaborative task (for the convenience of description, referred to as subtask 1); accordingly, agent 1 receives execution request message 1.

[0284] Assuming that the agents participating in the collaborative task include agent 1, the collaborative execution functional network element sends execution request information 1 to agent 1. For example, execution request information 1 may include description information of subtask 1. Optionally, if the agents participating in the collaborative task also include other agents (such as agent 2), the collaborative execution functional network element may also send execution request information 2 to agent 2. Execution request information 2 is used to request agent 2 to execute subtask 2 of the collaborative task. For example, execution request information 2 may include description information of subtask 2.

[0285] The embodiments of this application do not limit the specific implementation of "how the collaborative execution functional network element determines subtask 1 and subtask 2 based on the collaborative task." In addition, if the agents participating in the collaborative task only include agent 1, then subtask 1 is the collaborative task itself.

[0286] In one possible implementation, the collaborative execution function network element receives a collaborative configuration response message 1 from the intelligent agent 1. If the collaborative configuration response message 1 is used to indicate that the configuration of the intelligent agent 1 is successful, the collaborative execution function network element sends an execution request message 1 to the intelligent agent 1. If the collaborative configuration response message 1 is used to indicate that the configuration of the intelligent agent 1 fails, the collaborative execution function network element does not send the execution request message 1.

[0287] S904, agent 1 executes subtask 1 of the collaborative task according to execution request information 1.

[0288] S905, agent 1 sends the execution result of subtask 1 to the collaborative execution function network element; accordingly, the collaborative execution function network element receives the execution result of subtask 1.

[0289] Optionally, agent 2 sends the execution result of subtask 2 to the collaborative execution function network element, and the collaborative execution function network element receives the execution result of subtask 2.

[0290] S906: The collaborative execution function network element sends the execution result of subtask 1 to the collaborative control function network element.

[0291] Optionally, the collaborative execution function network element also sends the execution result of subtask 2 to the collaborative control function network element.

[0292] For example, the collaborative execution function network element may send the execution result of subtask 1 and the execution result of subtask 2 to the collaborative control function network element through different messages, or may send the execution result of subtask 1 and the execution result of subtask 2 to the collaborative control function network element through the same message. The embodiments of the present application do not limit the specific implementation.

[0293] S907 , the collaborative control function network element determines the execution result of the collaborative task according to the execution result of subtask 1 .

[0294] For example, the implementation of S907 may refer to the description of S705 in the first embodiment.

[0295] S908: The collaborative control function network element sends the execution result of the collaborative task to the initiator of the collaborative task.

[0296] Optionally, after completing the collaborative task, the collaborative control function network element releases the connection between agent 1 and the collaborative execution function network element. Alternatively, after reporting the execution result of subtask 1, agent 1 sends a deregistration request message to the collaborative control function network element, and the collaborative control function network element releases the connection between agent 1 and the collaborative execution function network element, and also releases the connection between agent 1 and the collaborative control function network element.

[0297] By adopting the above method, collaborative control function network elements and collaborative execution function network elements are introduced into the core network or access network, and the collaborative control function network elements and collaborative execution function network elements are used to jointly control the intelligent body to complete the collaborative task. Since the collaborative execution function network element is located on the user plane, the transmission delay of the user plane is relatively small, which makes it easier to meet the collaborative needs of low-latency services.

[0298] Example 4

[0299] In Example 4, based on Example 2, a specific implementation process will be described, taking the initiator of the collaborative task as the second agent and the agents participating in the collaborative task as Agent 1 and Agent 2. When the agents participating in the collaborative task include more than two agents, the implementation process can be referred to.

[0300] FIG10 is a flow chart of the communication method according to the fourth embodiment of the present application. As shown in FIG10 , the method includes the following steps:

[0301] S1001, a second intelligent agent sends a first collaboration request message to a collaborative control function network element in a network, which is an access network or a core network; accordingly, the collaborative control function network element receives the first collaboration request message.

[0302] Exemplarily, the first collaboration request information includes description information of the collaborative task.

[0303] S1002: The collaborative control function network element determines an agent that meets the capability requirements from multiple registered agents, such as agent 1 and agent 2.

[0304] S1003, the collaborative control function network element sends status request information 1 to agent 1, where the status request information 1 is used to request status information of agent 1; accordingly, agent 1 receives the status request information 1.

[0305] S1004, the collaborative control function network element sends status request information 2 to agent 2, where the status request information 2 is used to request status information of agent 2; accordingly, agent 2 receives the status request information 2.

[0306] S1005, agent 1 sends the status information of agent 1 to the collaborative control function network element according to the status request information 1.

[0307] S1006, agent 2 sends the status information of agent 2 to the collaborative control function network element according to the status request information 2.

[0308] S1007, the collaborative control function network element determines that both agent 1 and agent 2 meet the status requirements of the collaborative task for the agents participating in the collaborative task based on the status information of agent 1 and the status information of agent 2, and further determines that at least one agent participating in the collaborative task includes agent 1 and agent 2.

[0309] S1008, the collaborative control function network element sends notification information 1 to the intelligent agent 1, and the notification information 1 is used to notify the intelligent agent 1 to establish a connection with the collaborative execution function network element; accordingly, the intelligent agent 1 establishes a connection with the collaborative execution function network element according to the notification information 1.

[0310] S1009, the collaborative control function network element sends notification information 2 to the intelligent agent 2, and the notification information 2 is used to notify the intelligent agent 2 to establish a connection with the collaborative execution function network element; accordingly, the intelligent agent 2 establishes a connection with the collaborative execution function network element according to the notification information 2.

[0311] S1010, the collaborative control function network element sends collaborative configuration request information 1 to agent 1, where the collaborative configuration request information 1 includes configuration parameters required for agent 1 to participate in the collaborative task; accordingly, agent 1 receives the collaborative configuration request information 1.

[0312] For example, the notification information 1 and the collaborative configuration request information 1 may be carried in the same message or in different messages, and the specific details are not limited thereto. When carried in the same message, S1008 and S1010 may be executed simultaneously.

[0313] S1011, the collaborative control function network element sends collaborative configuration request information 2 to agent 2, where the collaborative configuration request information 2 includes configuration parameters required for agent 2 to participate in the collaborative task; accordingly, agent 2 receives the collaborative configuration request information 2.

[0314] For example, the notification information 2 and the collaborative configuration request information 2 may be carried in the same message or in different messages, and the specific details are not limited thereto. When carried in the same message, S1009 and S1011 may be executed simultaneously.

[0315] S1012: The collaborative control function network element sends second collaborative request information to the collaborative execution function network element. The second collaborative request information includes description information of the collaborative task and an identifier of at least one intelligent agent participating in the collaborative task.

[0316] S1013, the intelligent agent 1 sends the collaborative configuration response information 1 to the collaborative execution function network element according to the collaborative configuration request information 1, and the collaborative configuration response information 1 is used to indicate that the configuration of the intelligent agent 1 is successful.

[0317] S1014, the intelligent agent 2 sends a collaborative configuration response message 2 to the collaborative execution function network element according to the collaborative configuration request message 2. The collaborative configuration response message 2 is used to indicate that the configuration of the intelligent agent 2 is successful.

[0318] S1015, after the collaborative execution functional network element determines that the configuration of intelligent agent 1 is successful, it sends execution request information 1 to intelligent agent 1, and execution request information 1 is used to request intelligent agent 1 to execute subtask 1 of the collaborative task; accordingly, intelligent agent 1 receives execution request information 1 and executes subtask 1 according to execution request information 1.

[0319] S1016, after the collaborative execution functional network element determines that the configuration of intelligent agent 2 is successful, it sends execution request information 2 to intelligent agent 2. Execution request information 2 is used to request intelligent agent 2 to execute subtask 2 of the collaborative task; accordingly, intelligent agent 2 receives execution request information 2 and executes subtask 2 according to execution request information 2.

[0320] S1017, agent 1 executes subtask 1 according to execution request information 1 and obtains the execution result of subtask 1.

[0321] S1018, agent 1 sends the execution result of subtask 1 to the collaborative execution function network element; accordingly, the collaborative execution function network element receives the execution result of subtask 1.

[0322] S1019, agent 2 executes subtask 2 according to execution request information 2 and obtains the execution result of subtask 2.

[0323] S1020, agent 2 sends the execution result of subtask 2 to the collaborative execution function network element; accordingly, the collaborative execution function network element receives the execution result of subtask 2.

[0324] S1021, the collaborative execution function network element sends the execution result of subtask 1 and the execution result of subtask 2 to the collaborative control function network element; accordingly, the collaborative control function network element receives the execution result of subtask 1 and the execution result of subtask 2.

[0325] S1022: The collaborative control function network element determines the execution result of the collaborative task according to the execution result of subtask 1 and the execution result of subtask 2.

[0326] S1023, the collaborative control function network element sends the execution result of the collaborative task to the second agent; correspondingly, the second agent receives the execution result of the collaborative task.

[0327] The process illustrated in FIG10 corresponds to the process illustrated in FIG9 , and the steps of the two processes can refer to each other. For example, S1001 can refer to S901, S1002 to S1007 can refer to S901′, S1008 to S1012 can refer to S902, S1013 and S1016 can refer to S903, S1017 and S1019 can refer to S904, S1018 and S1020 can refer to S905, S1021 can refer to S906, S1022 can refer to S907, and S1023 can refer to S908.

[0328] In addition, in the above-mentioned embodiments 3 and 4, when the collaborative control function network element and the collaborative execution function network element are located in the core network, the agent participating in the collaborative task (such as agent 1) can be a terminal device or an access network device. If agent 1 is a terminal device, the agent 1 and the collaborative execution function network element can communicate through the access network device and the UPF network element (as shown in Figure 3A). If agent 1 is an access network device, the agent 1 and the collaborative execution function network element can communicate through the UPF network element.

[0329] When the collaborative execution function network element is located in the access network, for example, the collaborative execution function network element is located in the DU, in this case, the intelligent agent participating in the collaborative task (such as intelligent agent 1) can be a terminal device, and intelligent agent 1 and the collaborative execution function network element can communicate through air interface messages.

[0330] In addition, in Examples 3 and 4, the communication method between the collaborative control function network element and the intelligent agents participating in the collaborative task (such as intelligent agent 1) and the initiator of the collaborative task (such as the second intelligent agent) can refer to the description of Examples 1 and 2.

[0331] For each of the above embodiments:

[0332] (1) The above description focuses on the differences between different embodiments, different implementations, or different examples. Except for the differences, different embodiments, different implementations, or different examples can refer to each other. In addition, different embodiments, different implementations, or different examples may be implemented partially, combined, or partially combined, etc., and the embodiments of this application will not be listed one by one.

[0333] (2) The step numbers in the flowcharts described in the above embodiments are merely examples of the execution process and do not limit the order in which the steps are executed. In the embodiments of the present application, steps that do not have a temporal dependency on each other may not be strictly executed in any particular order. Furthermore, not all of the steps shown in the flowcharts are mandatory steps. Some steps may be added or deleted based on actual needs, or only some of the steps in the flowcharts may be executed.

[0334] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between devices. In order to achieve the above functions, each device may include a hardware structure and / or software module that performs each function. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0335] In the embodiment of the present application, the collaborative control function network element, the collaborative execution function network element, the first intelligent agent, and the second intelligent agent can be divided into functional units according to the above method example. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or software functional units.

[0336] In the case of adopting an integrated unit, Figure 11 shows a possible exemplary block diagram of the device involved in the embodiments of the present application. As shown in Figure 11, the device 1100 may include: a processing unit 1102 and a communication unit 1103. The processing unit 1102 is used to control and manage the actions of the device 1100. The communication unit 1103 is used to support the communication between the device 1100 and other devices. Optionally, the communication unit 1103 is also called a transceiver unit, and may include a receiving unit and / or a sending unit, which are used to perform receiving and sending operations respectively. The device 1100 may also include a storage unit 1101 for storing program code and / or data of the device 1100.

[0337] (1) The apparatus 1100 may be the collaborative control function network element in the above-described embodiment. The processing unit 1102 may support the apparatus 1100 in executing the actions of the collaborative control function network element in each of the above-described method examples. Alternatively, the processing unit 1102 may primarily execute the internal actions of the collaborative control function network element in the method examples, and the communication unit 1103 may support communication between the apparatus 1100 and other devices.

[0338] For example, in one embodiment, the communication unit 1103 is used to: receive a first collaborative request message from a second agent, the first collaborative request message including description information of the collaborative task, and at least one agent participating in the collaborative task including the first agent; and send a second collaborative request message to the collaborative execution function network element corresponding to the first agent, the second collaborative request message including description information of the collaborative task and an identifier of at least one agent participating in the collaborative task.

[0339] In one possible design, the communication unit 1103 is also used to: receive status information from the first agent, the status information is used to indicate the status of the first agent; the status information meets the status requirements of the collaborative task for the agents participating in the collaborative task; wherein the status requirements are determined based on the description information of the collaborative task.

[0340] In one possible design, the state of the first agent includes at least one of the following: the network connection state of the first agent; the computing resource state of the first agent; the location state of the first agent; the power state of the first agent; the motion state of the first agent; and the memory state of the first agent.

[0341] In a possible design, the communication unit 1103 is further used to: send status request information to the first agent, where the status request information is used to request the status information.

[0342] In one possible design, the communication unit 1103 is also used to: receive capability information from the first intelligent agent; determine whether the capability information of the first intelligent agent meets the capability requirements of the collaborative task for the intelligent agents participating in the collaborative task; wherein the capability requirements are determined based on the description information of the collaborative task.

[0343] In one possible design, the capability information of the first agent is used to indicate the type of data that the first agent supports perceiving and / or the type of task that the first agent supports executing.

[0344] In one possible design, the communication unit 1103 is further used to: receive a registration request message from the first agent, where the registration request message includes the capability information.

[0345] In one possible design, the communication unit 1103 is also used to: receive the execution results of the subtasks of the collaborative task from the collaborative execution functional network element; the processing unit 1102 is used to: obtain the execution results of the collaborative task based on the execution results of the subtasks; the communication unit 1103 is also used to: send the execution results of the collaborative task to the second intelligent agent.

[0346] In one possible design, the communication unit 1103 is further used to: send collaborative configuration request information to the first agent, where the collaborative configuration request information includes configuration parameters required for the first agent to participate in the collaborative task.

[0347] In one possible design, the processing unit 1102 is used to: determine, based on the description information of the collaborative task, that the maximum transmission delay required by the collaborative task is less than or equal to a threshold.

[0348] In one possible design, the communication unit 1103 is also used to: receive a logout request message from the first agent; the processing unit 1102 is used to: release the connection between the first agent and the collaborative control function network element, and / or release the connection between the first agent and the collaborative execution function network element according to the logout request message.

[0349] In one possible design, the first intelligent agent is a terminal device or an access network device.

[0350] (2) The apparatus 1100 may be the collaborative execution function network element in the above-described embodiments. The processing unit 1102 may support the apparatus 1100 in executing the actions of the collaborative execution function network element in each of the above-described method examples. Alternatively, the processing unit 1102 may primarily execute the internal actions of the collaborative execution function network element in the method examples, and the communication unit 1103 may support communication between the apparatus 1100 and other devices.

[0351] For example, in one embodiment, the communication unit 1103 is used to: receive a second collaborative request message from a collaborative control function network element, the second collaborative request message including description information of the collaborative task and an identifier of at least one intelligent agent participating in the collaborative task, the at least one intelligent agent including a first intelligent agent; and send an execution request message to the first intelligent agent, the execution request message being used to request the first intelligent agent to execute a subtask of the collaborative task.

[0352] In one possible design, the communication unit 1103 is further used to: receive the execution result of the subtask from the first intelligent agent; and send the execution result of the subtask to the collaborative control function network element.

[0353] In one possible design, the communication unit 1103 is further used to: receive collaborative configuration response information from the first agent, where the collaborative configuration response information is used to indicate that the configuration of the first agent is successful.

[0354] In one possible design, the first intelligent agent is a terminal device or an access network device.

[0355] (3) The apparatus 1100 may be the first agent in the above-described embodiments. The processing unit 1102 may support the apparatus 1100 in executing the actions of the first agent in each of the above-described method examples. Alternatively, the processing unit 1102 may primarily execute the internal actions of the first agent in the method examples, and the communication unit 1103 may support communication between the apparatus 1100 and other devices.

[0356] For example, in one embodiment, the communication unit 1103 is used to: receive execution request information from a collaborative execution function network element in the network, wherein the execution request information is used to request the first intelligent agent to perform a subtask of the collaborative task; wherein the network is an access network or a core network; and execute the subtask according to the execution request information.

[0357] In one possible design, the communication unit 1103 is used to: send status information of the first agent to a collaborative control function network element in the network, where the status information is used to indicate the status of the first agent.

[0358] In one possible design, the state of the first agent includes at least one of the following: the network connection state of the first agent; the computing resource state of the first agent; the location state of the first agent; the power state of the first agent; the motion state of the first agent; and the memory state of the first agent.

[0359] In one possible design, the communication unit 1103 is used to: receive status request information from a collaborative control function network element in the network, where the status request information is used to request the status information.

[0360] In one possible design, the communication unit 1103 is used to send the capability information of the first agent to the collaborative control function network element in the network.

[0361] In one possible design, the capability information of the first agent is used to indicate the type of data that the first agent supports perceiving and / or the type of task that the first agent supports executing.

[0362] In one possible design, the communication unit 1103 is used to: send a registration request message to the collaborative control function network element, where the registration request message includes the capability information.

[0363] In one possible design, the communication unit 1103 is used to: receive collaborative configuration request information from a collaborative control function network element in the network, the collaborative configuration request information including the configuration parameters required for the first intelligent agent to participate in the collaborative task; and send collaborative configuration response information to the collaborative control function network element, the collaborative configuration response information being used to indicate that the configuration of the first intelligent agent is successful.

[0364] In one possible design, the communication unit 1103 is used to send the execution result of the subtask to the collaborative execution function network element.

[0365] In one possible design, the communication unit 1103 is used to send a deregistration request message to a collaborative control function network element in the network.

[0366] In one possible design, the first intelligent agent is a terminal device or an access network device.

[0367] (4) The apparatus 1100 may be the second agent in the above-described embodiments. The processing unit 1102 may support the apparatus 1100 in executing the actions of the second agent in each of the above-described method examples. Alternatively, the processing unit 1102 may primarily execute the internal actions of the second agent in the method examples, and the communication unit 1103 may support communication between the apparatus 1100 and other devices.

[0368] For example, in one embodiment, the communication unit 1103 is used to: send a first collaborative request message to a collaborative control function network element in the network, the first collaborative request message including description information of the collaborative task; wherein the network is an access network or a core network; and receive a collaborative response message from the collaborative control function network element, the collaborative response message including the execution result of the collaborative task.

[0369] In one possible design, the second intelligent agent is a terminal device or an access network device.

[0370] The division of units in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, the units in the device can all be implemented in the form of software calling through processing elements; they can also all be implemented in the form of hardware; some units can also be implemented in the form of software calling through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device. In addition, it can also be stored in the memory in the form of a program, called by a certain processing element of the device and execute the function of the unit. In addition, all or part of these units can be integrated together, or they can be implemented independently. The processing element described here can also be a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each operation of the above method or each unit above can be implemented by the integrated logic circuit of the hardware in the processor element or in the form of software calling through the processing element.

[0371] In one example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), one or more digital singnal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0372] The above-mentioned receiving unit is an interface circuit of the device, which is used to receive signals from other devices. For example, when the device is implemented as a chip, the receiving unit is the interface circuit of the chip used to receive signals from other chips or devices. The above-mentioned sending unit is an interface circuit of the device, which is used to send signals to other devices. For example, when the device is implemented as a chip, the sending unit is the interface circuit of the chip used to send signals to other chips or devices.

[0373] Based on the above embodiments, an embodiment of the present application further provides a communication device. As shown in FIG12 , the communication device 1200 may include a processor 1202. Optionally, the communication device 1200 may further include a transceiver 1201 and / or a memory 1203. The memory 1203 may be disposed inside the communication device 1200 or outside the communication device 1200. The processor 1202 may control the transceiver 1201 to receive and send messages, etc.

[0374] Specifically, the processor 1202 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor 1202 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0375] The transceiver 1201, the processor 1202, and the memory 1203 are interconnected. Optionally, the transceiver 1201, the processor 1202, and the memory 1203 are interconnected via a bus 1204; the bus 1204 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, FIG12 shows only one thick line, but this does not mean that there is only one bus or one type of bus.

[0376] In an optional embodiment, the memory 1203 is used to store programs, etc. Specifically, the programs may include program code, which includes computer operating instructions. The memory 1203 may include RAM, or may also include non-volatile memory (non-volatile memory), such as one or more disk storage devices. The processor 1202 executes the application stored in the memory 1203 to implement the above functions, thereby realizing the functions of the communication device 1200.

[0377] Exemplarily, the communication device 1200 may be the collaborative control function network element, collaborative execution function network element, or intelligent agent in the above-described embodiments. The transceiver 1201 may implement the transceiver operations performed by the collaborative control function network element, collaborative execution function network element, or intelligent agent in the above-described method embodiments; the processor 1202 may implement other operations other than the transceiver operations performed by the collaborative control function network element, collaborative execution function network element, or intelligent agent in the above-described method embodiments. For specific related descriptions, please refer to the relevant descriptions in the above-described embodiments and will not be described in detail here.

[0378] The terms "system" and "network" in the embodiments of the present application can be used interchangeably. "At least one" refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, "at least one of A, B or C" includes A, B, C, AB, AC, BC or ABC, and "at least one of A, B and C" can also be understood to include A, B, C, AB, AC, BC or ABC. And, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects and are not used to limit the order, timing, priority or importance of multiple objects.

[0379] The embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, optical storage, etc.) that contain computer-usable program code.

[0380] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. Each flow and / or box in the flow chart and / or block diagram, as well as the combination of the flow chart and / or box in the flow chart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more flow charts and / or one or more boxes in the block diagram.

[0381] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0382] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

Claims

1. A communication method, characterized in that: The method is applied to a collaborative control function network element in a network, where the network is an access network or a core network, and the method includes: receiving first collaboration request information from a second agent, wherein the first collaboration request information includes description information of a collaborative task, and at least one agent participating in the collaborative task includes the first agent; Sending a second collaborative request message to the collaborative execution function network element corresponding to the first agent, wherein the second collaborative request message includes description information of the collaborative task and an identifier of at least one agent participating in the collaborative task.

2. The method according to claim 1, characterized in that Also includes: receiving status information from the first agent, wherein the status information is used to indicate a status of the first agent; Determining that the state information satisfies the state requirements of the collaborative task for the agents participating in the collaborative task; The state requirement is determined according to the description information of the collaborative task.

3. The method according to claim 2, characterized in that The state of the first agent includes at least one of the following: The network connection status of the first agent; The computing resource status of the first agent; The position state of the first agent; The power status of the first agent; The motion state of the first agent; The memory state of the first agent.

4. The method according to any one of claims 1 to 3, characterized in that Also includes: Receiving capability information from the first agent, wherein the capability information is used to indicate the type of data that the first agent supports sensing and / or the type of task that the first agent supports executing; Determining that the capability information satisfies the capability requirements of the collaborative task for the agents participating in the collaborative task; The capability requirement is determined according to the description information of the collaborative task.

5. The method according to claim 4, characterized in that Receiving capability information of the first agent, including: A registration request message of the first agent is received, wherein the registration request message includes the capability information.

6. The method according to any one of claims 1 to 5, characterized in that Also includes: Receiving the execution result of the subtask of the collaborative task from the collaborative execution function network element; Obtaining the execution result of the collaborative task according to the execution result of the subtask; The execution result of the collaborative task is sent to the second agent.

7. The method according to any one of claims 1 to 6, characterized in that Also includes: It is determined, according to the description information of the collaborative task, that a maximum transmission delay required by the collaborative task is less than or equal to a threshold.

8. The method according to any one of claims 1 to 7, characterized in that Also includes: Sending collaborative configuration request information to the first agent, wherein the collaborative configuration request information includes configuration parameters required for the first agent to participate in the collaborative task.

9. The method according to any one of claims 1 to 8, characterized in that Also includes: Receiving a logout request message from the first agent; According to the deregistration request message, the connection between the first agent and the collaborative control function network element is released, and / or the connection between the first agent and the collaborative execution function network element is released.

10. The method according to any one of claims 1 to 9, characterized in that The first intelligent entity is a terminal device or an access network device.

11. A communication method, characterized in that: The method is applied to a collaborative execution function network element in a network, where the network is an access network or a core network, and the method includes: receiving second collaboration request information from a collaboration control function network element, wherein the second collaboration request information includes description information of a collaboration task and an identifier of at least one agent participating in the collaboration task, wherein the at least one agent includes a first agent; Sending execution request information to the first agent, wherein the execution request information is used to request the first agent to execute a subtask of the collaborative task.

12. The method according to claim 11, characterized in that Also includes: Receiving the execution result of the subtask from the first agent; Send the execution result of the subtask to the collaborative control function network element.

13. The method according to claim 11 or 12, characterized in that: Also includes: A collaborative configuration response message is received from the first agent, where the collaborative configuration response message is used to indicate that the first agent is successfully configured.

14. A communication method, characterized in that: The method is applied to a first agent, comprising: Receiving execution request information from a collaborative execution function network element in a network, wherein the execution request information is used to request the first agent to execute a subtask of a collaborative task; wherein the network is an access network or a core network; The subtask is executed according to the execution request information.

15. The method according to claim 14, characterized in that Also includes: Sending status information of the first agent to a collaborative control function network element in the network, where the status information is used to indicate the status of the first agent.

16. The method according to claim 15, characterized in that The state of the first agent includes at least one of the following: The network connection status of the first agent; The computing resource status of the first agent; The position state of the first agent; The power status of the first agent; The motion state of the first agent; The memory state of the first agent.

17. The method according to any one of claims 14 to 16, characterized in that Also includes: The capability information of the first agent is sent to a collaborative control function network element in the network, where the capability information of the first agent is used to indicate the type of data that the first agent supports sensing and / or the type of task that the first agent supports executing.

18. The method according to any one of claims 14 to 17, characterized in that Also includes: Receiving collaborative configuration request information from a collaborative control function network element in the network, wherein the collaborative configuration request information includes configuration parameters required for the first agent to participate in the collaborative task; A collaborative configuration response message is sent to the collaborative execution function network element, where the collaborative configuration response message is used to indicate that the first agent is successfully configured.

19. The method according to any one of claims 14 to 18, characterized in that Also includes: Send the execution result of the subtask to the collaborative execution function network element.

20. The method according to any one of claims 14 to 19, characterized in that The first intelligent entity is a terminal device or an access network device.

21. A communication method, characterized in that: The method is applied to a second agent, comprising: Sending first coordination request information to a coordination control function network element in a network, wherein the first coordination request information includes description information of a coordination task; wherein the network is an access network or a core network; Receive collaborative response information from the collaborative control function network element, where the collaborative response information includes an execution result of the collaborative task.

22. The method according to claim 21, characterized in that The second intelligent entity is a terminal device or an access network device.

23. A communication device, characterized in that: It comprises a processor, the processor is coupled to a memory, and a computer program is stored in the memory; the processor is used to call the computer program in the memory so that the method according to any one of claims 1 to 22 is executed.

24. A communication system, characterized in that: The communication system includes a collaborative control function network element in the network, a collaborative execution function network element in the network, a first intelligent agent and a second intelligent agent, and the network is a core network or an access network; wherein the collaborative control function network element is used to execute the method described in any one of claims 1 to 22.

25. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by a computer, the method according to any one of claims 1 to 22 is executed.

26. A computer program product, characterized in that The method comprises a computer program or an instruction, which, when executed by a computer, enables the method according to any one of claims 1 to 22 to be performed.

Images