CN114630341A

CN114630341A - Communication method, device and system

Info

Publication number: CN114630341A
Application number: CN202011447020.5A
Authority: CN
Inventors: 刘哲; 彭程晖; 吴建军
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-12-11
Filing date: 2020-12-11
Publication date: 2022-06-14
Also published as: US20230319601A1; EP4250800A4; WO2022121991A1; EP4250800A1

Abstract

The application provides a communication method, a device and a system. In the method, a first terminal device sends request information including a first task to a first network function entity, and after receiving the request information of the first task, the first network function entity can manage the first task, that is, allocate at least one first node executing a subtask of the first task, and send configuration information of the subtask corresponding to each first node. And executing the corresponding subtasks of the first task by the first node according to the configuration information of the subtasks, thereby realizing a task-centered communication mode. In addition, when the plurality of first nodes execute the subtasks of the first task, the task execution efficiency can be improved, thereby improving the task service efficiency of the communication system.

Description

Communication method, device and system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communication method, apparatus, and system.

Background

With the intensive deployment of millimeter wave and other high-frequency stations, the popularization of diversified terminals and the development of network endogenous intelligence, more and more terminal devices such as handheld terminals and vehicle-mounted terminals are provided with sensors, a future communication mode is a mode oriented to connection and sensing, and various sensing tasks can become mainstream services of a future network.

However, the communication mode of the existing fifth generation (5th generation, 5G) network is developed based on the traditional voice service, and is a single point-to-point connection-oriented communication mode between a terminal and a terminal or between a terminal and a server, and may not be applicable any more.

Disclosure of Invention

The embodiment of the application provides a communication method, a device and a system, which can realize a task-centered communication mode.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, a communication method is provided, and the method includes: the first network functional entity receives first information including request information of a first task from a first terminal device and sends configuration information of at least one second task, wherein the second task is a subtask of the first task, the configuration information of the second task configures execution resources corresponding to the second task, and the second task corresponds to the first node.

Based on the scheme, after receiving the request information of the task, the first network functional entity may send configuration information of a subtask of the first task corresponding to at least one first node, so that the first node executes the subtask of the first task according to the configuration of the first network functional entity, and when a plurality of first nodes exist, the plurality of first nodes cooperate to complete the first task finally. That is, in the present application, the first network function entity manages the first task, so as to implement the task-centric communication mode.

In some possible designs, the first terminal device is a terminal device that serves the first access network device; the first network function entity receives first information from a first terminal device, comprising: the first network function entity receives first information from the first terminal device through the first access network device. Based on the possible design, the first network function entity may obtain the first information through the first access network device.

In some possible designs, the communication method further includes: the first network functional entity receives an execution result of a second task corresponding to at least one first node from second access network equipment, wherein the at least one first node comprises the second access network equipment and/or second terminal equipment, and the second terminal equipment serves the second access network equipment; and the first network functional entity sends an execution result of the second task corresponding to at least one first node to the first terminal equipment. Based on the possible design, the first network function entity can provide data interaction service for the first terminal device, so that the first terminal device obtains the execution result of the task.

In some possible designs, the first network function entity sends configuration information of at least one second task, including: and the first network functional entity sends configuration information of a second task corresponding to at least one first node to the second access network equipment, wherein the at least one first node comprises the second access network equipment and/or second terminal equipment, and the second terminal equipment serves the second access network equipment. Based on the possible design, the second access network device can acquire the configuration information of the second task corresponding to the second access network device, so as to execute the corresponding second task, or the second access network device can acquire the configuration information of the second task corresponding to the second terminal device served by the second access network device, so that the second access network device can send the configuration information of the second task corresponding to the second terminal device, so that the second task corresponding to the second terminal device is executed.

In some possible designs, the first network function entity sends configuration information of at least one second task, including: the first network functional entity verifies the validity of the first task; and when the first task is legal, sending the configuration information of at least one second task. Based on the possible design, the safety of task service can be improved, when the task is legal, the configuration information of at least one second task is sent, and compared with a scheme that the configuration information of at least one second task is still sent under the condition that the legality verification is not carried out but the task is illegal, the waste of unnecessary resources, power consumption and the like can be reduced.

In some possible designs, the method further comprises: the first network function entity obtains node capability information of at least one first node, and the node capability information is used for indicating task execution capability of the first node. Based on the possible design, the first network functional entity can acquire the task execution capacity of the first node, and provides reference for the first network functional entity when the first network entity disassembles the task and determines the first node for executing the task, so that the task management efficiency and the rationality of the first network functional entity are improved, and the task execution delay is reduced.

In a second aspect, a communication method is provided, the method comprising: the first terminal device sends first information including request information of a first task to a first network function entity, and receives an execution result of at least one second task, wherein the second task is a subtask of the first task, and the second task corresponds to the first node.

Based on the scheme, the first terminal device sends request information of the first task to the first network function entity, so that the first network function entity configures subtasks of the first task to at least one first node, and when a plurality of first nodes exist, the plurality of first nodes cooperate to complete the first task finally, so that the first terminal device obtains an execution result of the first task. That is, in the present application, a first terminal device initiates a request of a first task to a first network function entity, and the first network function entity manages the first task, thereby implementing a task-centric communication mode.

In some possible designs, the first terminal device is a terminal device served by the first access network device; the first terminal equipment sends first information to a first network function entity, and the first information comprises the following steps: the first terminal equipment sends the first information to the first network function entity through the first access network equipment. Based on the possible design, the first terminal device may send the first information through the first access network device.

In some possible designs, the first information is transmitted via one or more of: the task type radio resource control RRC container, the task type non-access stratum NAS signaling or the task type radio signaling bears SRB. Based on the possible design, the application provides the task type RRC container, the task type NAS signaling, or the task type SRB for transmitting the task related control information, so that the access network device can determine a receiver of the task related control information, for example, a first network function entity, after receiving the task related control information transmitted through the task type RRC container, the task type NAS signaling, or the task type SRB, thereby forwarding the task related control information to the receiver, ensuring a correct transmission direction of the task related control information, and improving a task success rate.

In some possible designs, the first terminal device receives a result of execution of at least one second task, including: the first terminal device receives an execution result of a second task corresponding to at least one first node from the first access network device, wherein the first node comprises a second access network device and/or a second terminal device, and the second terminal device serves the second access network device.

In some possible designs, the first terminal device receives a result of execution of at least one second task, including: and the first terminal equipment receives an execution result of a second task corresponding to the second terminal equipment from the second terminal equipment. Based on the possible design, the first terminal device and the second terminal device may perform the results in a sidelink interworking task.

In some possible designs, the result of the execution of the second task maps to one of: a task class data protocol data unit of a packet data convergence protocol PDCP, a task class data protocol data unit of a service data adaptation protocol SDAP, a task class data radio bearer DRB or a task class quality of service QoS flow. Based on the possible design, the method provides task execution results of task class SDAP data PDU, task class PDCP data PDU, task class data radio bearer DRB or task class QoS transmission, so that the access network equipment can identify the task execution results and directly send the task execution results to a task requester.

In some possible designs, the first terminal device receives a result of execution of at least one second task, including: the first terminal device receives results of the execution of the at least one second task from the first network function entity. Based on the possible design, the first network functional entity can provide data interaction service for the first terminal device, so that the first terminal device obtains the execution result of the task.

In a third aspect, a communication method is provided, which includes: the second terminal device receives configuration information of a second task corresponding to the second terminal device from the second access network device, and then executes the second task corresponding to the second terminal device and sends an execution result of the second task corresponding to the second terminal device.

Based on the scheme, after receiving the configuration information of the corresponding second task, the second terminal device can execute the second task and send the execution result of the second task, and finally the first terminal device obtains the execution result of the second task, so that the task-centered communication mode is realized.

In some possible designs, the configuration information of the second task corresponding to the second terminal device is transmitted through one or more of: the task type radio resource control RRC container, the task type non-access stratum NAS signaling or the task type radio signaling bears SRB.

In some possible designs, the method further comprises: and the second terminal equipment receives third information from the second access network equipment, and determines a transmission link of an execution result of a second task corresponding to the second terminal equipment according to the third information.

In some possible designs, the transmission link is a sidelink between the second terminal device and the first terminal device; the second terminal device sends an execution result of a second task corresponding to the second terminal device, and the execution result comprises the following steps: and the second terminal equipment sends an execution result of a second task corresponding to the second terminal equipment to the first terminal equipment.

In some possible designs, the transmission link is an air interface link between the second terminal device and the second access network device; the second terminal device sends an execution result of a second task corresponding to the second terminal device, and the execution result comprises the following steps: and the second terminal equipment sends an execution result of a second task corresponding to the second terminal equipment to the second access network equipment.

In some possible designs, the execution result of the second task corresponding to the second terminal device is mapped to one of: a task class data protocol data unit of a packet data convergence protocol PDCP, a task class data protocol data unit of a service data adaptation protocol SDAP, a task class data radio bearer DRB, or a task class quality of service QoS flow.

The technical effects brought by any possible design of the third aspect can refer to the technical effects brought by the corresponding design of the second aspect, and are not described herein again.

In a fourth aspect, a communication method is provided, the method comprising: the second access network equipment receives second information from the first network function entity, the second information comprises configuration information of a second task corresponding to the second terminal equipment, and the configuration information of the second task is used for configuring execution resources corresponding to the second task; and the second access network equipment sends the configuration information of the second task corresponding to the second terminal equipment.

Based on the scheme, after receiving the second information from the first network function entity, the second access network device sends the configuration information of the subtask corresponding to the second terminal device, so that the second terminal device executes the subtask of the first task according to the configuration of the first network function entity. That is to say, in the present application, the first network functional entity manages the first task, and the first access network device cooperatively transmits the configuration information of the task, thereby implementing a task-centric communication mode.

In some possible designs, the method further comprises: and the second access network equipment sends third information to the second terminal equipment, wherein the third information is used for determining a transmission link of an execution result of a second task corresponding to the second terminal equipment.

In some possible designs, the transmission link is a sidelink between the second terminal device and the first terminal device.

In some possible designs, the transmission link is an air interface link between the second terminal device and the second access network device.

In some possible designs, the execution result of the second task corresponding to the second terminal device is mapped to one of: a task class data protocol data unit of a packet data convergence protocol PDCP, a task class data protocol data unit of a service data adaptation protocol SDAP, a task class data radio bearer DRB or a task class quality of service QoS flow.

In some possible designs, the method further comprises: the second access network equipment receives first information from the first terminal equipment and sends the first information to the first network functional entity, the first information comprises request information of the first task, and the second task is a subtask of the first task.

In some possible designs, the first information is transmitted via one or more of: radio resource control, RRC, container, non-access stratum, NAS, signaling, or radio signaling bearer, SRB.

In some possible designs, the second information further includes configuration information for a second task corresponding to the second access network device.

For technical effects brought by any possible design of the fourth aspect, reference may be made to the technical effects brought by the corresponding design of the second aspect or the third aspect, which are not described herein again.

In a fifth aspect, a communication method is provided, the method comprising: the first access network device receives first information from the first terminal device and sends the first information to the first network function entity, wherein the first information comprises request information of a first task.

Based on the scheme, after receiving configuration information of subtasks of a first task corresponding to each first node from a first network functional entity, first access network equipment sends the configuration information of the corresponding subtasks to part or all of the first nodes, so that the first nodes execute the subtasks of the first task according to the configuration of the first network functional entity, and when a plurality of first nodes exist, the plurality of first nodes cooperate to complete the first task. That is to say, in the present application, the first network functional entity manages the first task, and the first access network device cooperatively transmits the configuration information of the task, thereby implementing a task-centric communication mode.

In some possible designs, the first information is transmitted via one or more of: the method comprises the steps of task type Radio Resource Control (RRC) container, task type non-access stratum (NAS) signaling, and task type or radio signaling bearing SRB.

In some possible designs, the method further comprises: receiving an execution result of a second task corresponding to at least one first node from second access network equipment, wherein the second task is a subtask of the first task, the at least one first node comprises second access network equipment and/or second terminal equipment, and the second terminal equipment is terminal equipment served by the second access network equipment; and sending an execution result of the second task corresponding to the at least one first node to the first terminal equipment.

In some possible designs, the execution result of the second task corresponding to the at least one first node is mapped to one or more of: a task class data protocol data unit of a packet data convergence protocol PDCP, a task class data protocol data unit of a service data adaptation protocol SDAP, a task class data radio bearer DRB or a task class quality of service QoS flow.

The technical effects brought by any possible design of the fifth aspect may refer to the technical effects brought by the corresponding designs of the second aspect, the third aspect, or the fourth aspect, and are not described herein again.

In a sixth aspect, a communications apparatus is provided for implementing the various methods described above. The communication device comprises corresponding modules, units or means (means) for implementing the above method, and the modules, units or means can be implemented by hardware, software or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

The communication device may be the first network function entity in the first aspect, or a device including the first network function entity, or a device included in the first network function entity, such as a chip; alternatively, the communication device may be the first terminal device in the second aspect, or a device including the first terminal device, or a device included in the first terminal device, such as a chip; alternatively, the communication device may be the second terminal device in the third aspect, or a device including the second terminal device, or a device included in the second terminal device, such as a chip; alternatively, the communication device may be the second access network device in the fourth aspect, or a device including the second access network device, or a device included in the second access network device, such as a chip; alternatively, the communication device may be the first access network device in the fifth aspect, or a device including the first access network device, or a device included in the first access network device, such as a chip.

In a seventh aspect, a communication apparatus is provided, including: a processor and a memory; the memory is configured to store computer instructions that, when executed by the processor, cause the communication device to perform the method of any of the above aspects.

In an eighth aspect, there is provided a communication apparatus comprising: the interface circuit can be a code/data read-write interface circuit and is used for acquiring input information and/or outputting output information; the logic circuit is configured to perform the method of any one of the above aspects, process and/or generate the output data according to the input information.

In some possible designs, the communication device may be the first network function entity in the first aspect, or a device including the first network function entity, or a device included in the first network function entity, such as a chip. At this time, the input information includes first information, and the output information includes configuration information of at least one second task.

Optionally, the input information and the output information may further include configuration information of a second task corresponding to the at least one first node, where the at least one first node includes a second access network device and/or a second terminal device, and the second terminal device is a terminal device serving the second access network device.

Optionally, the input information may further include node capability information of at least one first node, where the node capability information is used to indicate task execution capability of the first node.

In some possible designs, the communication device may be the first terminal device in the second aspect, or a device including the first terminal device, or a device included in the first terminal device, such as a chip. At this time, the input information includes an execution result of at least one second task, and the output information includes the first information.

In some possible designs, the communication device may be the second terminal device in the third aspect, or a device including the second terminal device, or a device included in the second terminal device, such as a chip. At this time, the input information includes configuration information of a second task corresponding to the second terminal device, and the output information includes an execution result of the second task corresponding to the second terminal device.

In some possible designs, the communication device may be the second access network apparatus in the fourth aspect, or a device including the second access network apparatus, or a device included in the second access network apparatus, such as a chip. At this time, the input information includes second information, and the output information includes configuration information of a second task corresponding to the second terminal device.

In some possible designs, the communication device may be the first access network device in the fifth aspect, or a device including the first access network device, or a device included in the first access network device, such as a chip. At this time, the input information and the output information each include the first information.

Optionally, the input information and the output information may further include: and the execution result of the second task corresponding to the at least one first node. The at least one first node comprises a second access network device and/or a second terminal device, and the second terminal device is a terminal device served by the second access network device.

In a ninth aspect, there is provided a communication apparatus comprising: at least one processor; the processor is configured to execute computer programs or instructions stored in the memory to cause the communication device to perform the method of any of the above aspects. The memory may be coupled to the processor or may be independent of the processor.

A tenth aspect provides a computer-readable storage medium having stored therein instructions that, when run on a communication device, cause the communication device to perform the method of any of the above aspects.

In an eleventh aspect, there is provided a computer program product comprising instructions which, when run on a communication device, cause the communication device to perform the method of any of the above aspects.

In a twelfth aspect, there is provided a communication device (which may be a chip or a system of chips, for example) comprising a processor for implementing the functionality referred to in any of the above aspects. In one possible design, the communication device further includes a memory for storing necessary program instructions and data. When the communication device is a chip system, it may be constituted by a chip, or may include a chip and other discrete devices.

For technical effects brought by any one of the design manners of the sixth aspect to the twelfth aspect, reference may be made to technical effects brought by different design manners of the first aspect, the second aspect, the third aspect, the fourth aspect, or the fifth aspect, and no further description is given here.

In a thirteenth aspect, a communication system is provided, the communication system comprising one or more of the first terminal device of the above aspect, the first network function entity of the above aspect, the second access network device of the above aspect, and the second terminal device of the above aspect.

Drawings

Fig. 1a is a schematic diagram of a 5G network architecture provided in an embodiment of the present application;

fig. 1b is a schematic mapping diagram of an SRB and a DRB provided in this embodiment of the present application;

fig. 2 is a schematic diagram of a scene of a perceptual task provided in an embodiment of the present application;

fig. 3 is a schematic diagram of a control logic facing "connection + sensing" according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 5a is a schematic structural diagram of another communication system provided in the embodiment of the present application;

fig. 5b is a schematic structural diagram of another communication system according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 7a is a schematic diagram illustrating module division of a first network functional entity according to an embodiment of the present application;

fig. 7b is a schematic block diagram of another first network functional entity according to an embodiment of the present application;

fig. 8 is a schematic diagram of logic division of an access network device according to an embodiment of the present application;

fig. 9 is a schematic diagram of logic division of another access network device according to an embodiment of the present application;

fig. 10 is a schematic diagram of a control plane protocol stack architecture according to an embodiment of the present application;

fig. 11 is a schematic diagram of a task plane protocol stack architecture according to an embodiment of the present application;

fig. 12a is a first schematic diagram illustrating a mapping of a task execution result according to an embodiment of the present disclosure;

fig. 12b is a schematic diagram illustrating a mapping of a task execution result according to an embodiment of the present application;

fig. 12c is a schematic diagram of mapping a task execution result according to the embodiment of the present application;

fig. 12d is a schematic diagram illustrating a mapping of a task execution result according to an embodiment of the present disclosure;

fig. 13 is a schematic diagram of a protocol stack architecture of an access network device according to an embodiment of the present application;

fig. 14 is a first flowchart illustrating a communication method according to an embodiment of the present application;

fig. 15 is a second flowchart illustrating a communication method according to an embodiment of the present application;

fig. 16 is a third flowchart illustrating a communication method according to an embodiment of the present application;

fig. 17 is a fourth flowchart illustrating a communication method according to an embodiment of the present application;

fig. 18 is a fifth flowchart illustrating a communication method according to an embodiment of the present application;

fig. 19 is a sixth flowchart of a communication method according to an embodiment of the present application;

fig. 20 is a schematic structural diagram of a first network functional entity according to an embodiment of the present application;

fig. 21 is a schematic structural diagram of a first terminal device according to an embodiment of the present application;

fig. 22 is a schematic structural diagram of a second access network device according to an embodiment of the present application;

fig. 23 is a schematic structural diagram of a first access network device according to an embodiment of the present application;

fig. 24 is a schematic structural diagram of a second terminal device according to an embodiment of the present application.

Detailed Description

To facilitate understanding of the technical solutions of the embodiments of the present application, a brief description of the related art of the present application is first given as follows.

1. 5G network architecture:

as shown in fig. 1a, the system architecture diagram of the 5G network includes a terminal, an access network device, an access and mobility management function (AMF) network element, a User Plane Function (UPF) network element, and a Data Network (DN). Of course, other functional network elements may also be included, such as a Session Management Function (SMF) network element, a Unified Data Management (UDM) network element, and the like.

Wherein, a next generation (N) network interface 1 (i.e. an N1 interface) is a reference point between the terminal and the AMF network element, and is used for interacting control plane signaling, such as non-access-stratum (NAS) signaling, between the terminal and the AMF network element; the N2 interface is a reference point between the access network device and the AMF network element, and is used for sending NAS messages and Next Generation Application Protocol (NGAP) messages, and the like; the N3 interface is a reference point between the access network device and the UPF network element, and is used for the data of the interactive user plane of the access network device and the UPF network element, and the like; the N6 interface is a reference point between the UPF network element and the DN, and is used for the UPF network element and the DN to interact with the data of the user plane, and the like.

2. Non-access-stratum (NAS) signaling, Radio Resource Control (RRC) container (container):

generally, NAS signaling refers to signaling that does not need to be processed by an access network device, and can be classified into multiple types of NAS signaling according to different contents, for example: mobility management NAS (NAS-MM) signaling, session management NAS (NAS-session management, NAS-SM) signaling, short message service NAS (NAS-short message service, NAS-SMs) signaling, and the like.

After receiving the NAS signaling from the terminal device, the access network device forwards the NAS signaling to the AMF network element, and then the AMF network element performs subsequent processing, for example, forwarding the NAS-SM signaling to the SMF network element, analyzing the NAS-MM signaling, and performing processing.

The RRC Container is used for transmission of RRC cells in RRC messages, and can be divided into multiple types according to different cell types of RRC messages, for example, NAS-Container is used for transparent transmission of NAS signaling, and ue-capability rat-Container is used for transmission of 3G/4G/5G capability information supported by the terminal device.

3. Signaling Radio Bearer (SRB), Data Radio Bearer (DRB):

a Radio Bearer (RB) describes a transmission path between two layers of protocols.

SRB is used for transmission of RRC messages, and currently standards define SRB0, SRB1, and SRB 2. The SRB0 carries RRC signaling before RRC connection establishment, and maps to a Common Control Channel (CCCH) for Transmission in an RLC layer by using a Transmission Mode (TM); the SRB1 is configured to carry RRC signaling after the RRC connection is successfully established and NAS signaling before the SRB2 is established, and map to a Dedicated Control Channel (DCCH) for transmission in an Acknowledged Mode (AM) mode in the RLC layer; the SRB2 carries NAS signaling, and adopts an AM mode in an RLC layer to be mapped to DCCH logical channel transmission. SRB2 has lower priority than SRB 1.

The DRBs are used for connection-oriented service data transmission, and in a New Radio (NR) system, at most 32 DRBs can be simultaneously established between one terminal device and one access network device according to quality of service (QoS) differences.

Illustratively, as shown in fig. 1b, a downlink radio protocol architecture for NR shows related information of SRB and DRB. Among them, the SDAP refers to Service Data Adaptation Protocol (SDAP), the PDCP refers to Packet Data Convergence Protocol (PDCP), and the RLC refers to Radio Link Control (RLC). DTCH refers to a Dedicated Traffic Channel (DTCH), ARQ refers to an automatic repeat request (ARQ), AM refers to an Acknowledged Mode (AM), and UM refers to an Unacknowledged Mode (UM).

4. Communication requirements and communication scenarios of the sixth generation (6th generation, 6G) system:

with the increasing maturity of 5G standardization, the industry starts related technical research of 6G communication systems, and compared with 5G systems, the 6G systems have the following new communication requirements and communication scenarios:

site type diversity, location rapid change in real time-sky-sea (de-sectorization): the connecting position is changed rapidly in real time based on a sky ground sea stereo network of a satellite, an unmanned aerial vehicle and a marine communication platform.

Terminal types are diversified, terminal connections are more flexible-everything is at will (terminal cooperation): mass connection in the internet of things (IOT) (e.g., internet of things, car networking, industry, medical treatment, etc.) requires more flexible terminal connection.

Network intelligence, network endogenous intelligence-endogenous intelligence (intelligent depth edge): network endogenous intelligence enables automatic network driving, and the network is required to better support real-time Artificial Intelligence (AI) and support the deployment of user/service AI application in a 6G network.

Holographic omnisense communication requires polarization performance-holographic omnisense (decollation, cooperative transmission): from 4K resolution, 8K resolution, Augmented Reality (AR), Virtual Reality (VR) to holographic full-sense communication, a sidelink between terminals needs ultra-low time delay, ultra-high reliability and ultra-large bandwidth. Terminals need to cooperate to assist in achieving full-induction polarization performance.

With the intensive deployment of millimeter wave and other high-frequency stations, the popularization of diversified terminals and the development of network endogenous intelligence, more and more terminal devices such as mobile terminals and vehicle-mounted terminals are provided with sensors, and a network in the future is a real-time full-scene sensing network. For example, as shown in fig. 2, in order to complete a traffic route planning task, a vehicle-mounted terminal and a handheld terminal with sensing capability are required to sense original data such as traffic congestion indexes (e.g., speed, acceleration, etc.), location information, etc., and report the original data to a sensing task center through an access network device, so as to provide an instant traffic route planning service.

Further, as the depth edge computing power sinks inside the wireless network, each node in the wireless network may have computing power, referred to as an edge computing node. The nodes in the wireless network include, for example, a terminal, an Active Antenna Unit (AAU), a Remote Radio Unit (RRU), or a baseband unit (BBU). In addition, the terminal with computing capability usually has some sensors, such as an acceleration sensor, a Global Positioning System (GPS) sensor, and the like.

When the edge computing node completes the sensing task, certain processing calculation can be carried out on the original data sensed by the sensor, the network transmission overhead is reduced, and meanwhile, the data which are more convenient for completing the sensing task are obtained, so that the completion of the sensing task is accelerated. Exemplarily, as shown in fig. 3, for a control logic facing "connection + sensing" provided by the present application, a system includes multiple types of terminals, independently deployed computing nodes, and multiple access network devices, and a sensing task management center controls and completes a sensing task.

As is known, a communication mode of an existing 5G network is developed based on a traditional voice service, and is a point-to-point single-connection communication mode between a terminal and the terminal or between the terminal and a server, and a connection-oriented control plane and a connection-oriented data plane between an access network device and a core network provide an on-demand high-speed pipeline service.

Based on this, the application provides a communication method for realizing a task-centric communication mode and improving task service efficiency.

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Where in the description of the present application, "/" indicates an OR meaning, for example, A/B may indicate A or B; "and/or" herein merely describes an association relationship of associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. Also, in the description of the present application, "a plurality" means two or more than two unless otherwise specified.

In addition, in order to facilitate clear description of technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items having substantially the same functions and actions. Those skilled in the art will appreciate that the terms "first," "second," and the like do not denote any order or importance, but rather the terms "first," "second," and the like do not denote any order or importance.

In addition, the network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation to the technical solution provided in the embodiment of the present application, and it can be known by a person skilled in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.

The communication method provided in the embodiment of the present application may be applied to any communication system, which may be a third generation partnership project (3 GPP) communication system, such as a 5G communication system, a 6G communication system, a New Radio (NR) system, an NR vehicle to outside of vehicle (V2X) system, and other next generation communication systems; and may be a non-3GPP communication system, without limitation.

The communication method provided by the embodiment of the application can be applied to various communication scenes, for example, one or more of the following communication scenes: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), Machine Type Communication (MTC), large-scale Machine Type Communication (MTC), device-to-device (D2D), vehicle-to-outside (V2X), vehicle-to-vehicle (V2V), and internet of things (IoT), among others. D2D communication may include, without limitation, vehicle-to-vehicle communication, vehicle-to-pedestrian communication, vehicle-to-infrastructure communication, communication between Unmanned Aerial Vehicles (UAVs) and drones, and the like.

A communication system is provided that includes a first network function entity, at least one access network device, and a plurality of terminal devices. Illustratively, taking an access network device, a terminal device 1, and a terminal device 2 in the communication system as an example, as shown in fig. 4, a connection relationship among a first network function entity, the access network device, and the terminal device is shown.

The terminal device related to the present application is a device for implementing a wireless communication function, and includes a terminal device (e.g., terminal device 1) generated in a Radio Access Network (RAN). Optionally, the terminal device of the present application may further include a third party terminal device (e.g., terminal device 2). The RAN endogenous terminal device refers to a terminal device that accesses a network through an access network device, and the third party terminal device refers to a terminal device that accesses the network through another method, for example, a terminal device that accesses the network through a wireless fidelity (WIFI) or a Non-3GPP interworking function (N3 IWF) entity.

Optionally, when the terminal device is an internal terminal device of the RAN, the terminal device may perform Sidelink (SL) communication or D2D communication with another terminal device, and send data to the other terminal device on the SL, for example: the SL transmits side-line data to another terminal through a side-link physical layer shared channel (psch), and the SL transmits side-line feedback control information (SFCI) corresponding to the received side-line data to another terminal through a side-link physical layer feedback channel (PSFCH). In the embodiment of the present application, the SL may also be referred to as a direct link or a PC5 interface link, which is not limited.

Or, when the terminal device is an endogenous terminal device in the RAN, the terminal device may perform air interface communication with the access network device through an Uplink (UL), and in an Uplink (UL) direction, the terminal sends data to the access network device, and the access network device forwards the received data to a core network element, and the core network element processes the data and sends the processed data to the application server through an N6 interface; in a Downlink (DL) direction, the application server sends downlink data to a core network element, the core network element processes the data, and sends the processed data to the access network device through an N3 interface, and the access network device processes the data and sends the processed data to the terminal through an air interface.

Or, when the terminal device is an endogenous terminal device in the RAN, the terminal device may also communicate with a core network element through a specific interface, such as: the terminal device may communicate with the first network function entity via an Nx interface, or may communicate with a mobility management network element in a core network element via an N1 interface.

Optionally, the terminal device related to the present application may include a User Equipment (UE) in a 5G network or a Public Land Mobile Network (PLMN) for future evolution, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device, or other processing device connected to a wireless modem, a vehicle-mounted device or a wearable device, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a terminal in an industrial control (industrial control), a terminal in a vehicle external association (VR) terminal device, a terminal in a remote intelligent terminal (2X), a terminal in a remote intelligent network (smart grid), a terminal in a vehicle external association (smart grid), and a wireless local loop (SIP) terminal device, A terminal in transportation security (transportation security), a terminal in a smart city (smart city), a terminal in a smart home (smart home), a Machine Type Communication (MTC) terminal, and the like.

The access network device related to the present application is a device providing a wireless communication function for a terminal device, and is mainly used for implementing functions such as a wireless physical control function, resource scheduling, wireless resource management, and wireless access control.

Optionally, the access network device includes but is not limited to: a next generation base station (gNB ), a Transmission and Reception Point (TRP), an evolved node B (eNB), a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved node B, or home node B, HNB), a Base Band Unit (BBU), a Transmission Point (TP), a mobile switching center, and the like in 5G. Optionally, the base station in the embodiment of the present application may include various forms of base stations, for example: macro base stations, micro base stations (also referred to as small stations), access points, and the like, which are not particularly limited in this embodiment of the present application.

Alternatively, the access network device related to the present application may be composed of a Central Unit (CU) and a Distributed Unit (DU). The CU and the DU may be physically separated or disposed together, which is not specifically limited in this embodiment of the present application. The CU and DU may be connected via an interface, such as an F1 interface. CUs and DUs may be partitioned according to protocol layers of the wireless network. For example, the functions of the RRC protocol layer and the PDCP protocol layer are provided in the CU, and the functions of the RLC protocol layer, the Medium Access Control (MAC) protocol layer, the Physical (PHY) protocol layer, and the like are provided in the DU. It is understood that the division of the CU and the DU processing functions according to the protocol layer is only an example, and may also be performed in other manners, which is not specifically limited in this embodiment of the present application.

The first network function entity is configured to implement one or more functions of:

(1) and verifying the legality of the task: and verifying whether one task is a reasonable task requested by a legal terminal device.

Alternatively, the task in the present application may be a perceptual task or a computational task. The sensing task may be understood as a task executed based on sensing resources, and the sensing resources may be various sensors, such as a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a temperature sensor, an ambient light sensor, a fingerprint sensor, a touch sensor, a bone conduction sensor, and the like. A computational task is understood to be a task that is executed based on computational resources, which may be various types of Central Processing Units (CPUs), General Processing Units (GPUs), and the like.

(2) And task disassembling: it is determined whether a task is to be broken down into a plurality of subtasks. When a task is decomposed into a plurality of subtasks, a node for executing each subtask is determined.

Illustratively, task 1 is broken down into subtask 1, subtask 2, and subtask 3, and it is determined that subtask 1 is executed by node 1, subtask 2 is executed by node 2, and subtask 3 is executed by node 3.

Optionally, in this application, the node performing the task may include a terminal device, an access network device, or an independently deployed execution unit.

(3) Performing type configuration of resources: the type of execution resources used by the configuration node to execute the task. The execution resources can be sensing resources or computing resources, and when the execution resources are sensing resources, the types of the sensing resources can be the types of the sensors; when the execution resource is a computational resource, the computational resource may be of the type of CPU or GPU.

For example, when the node performs a task of sensing the temperature of the environment in which the node is located, the type of execution resource may be a temperature sensor.

(4) Performing quantity configuration of resources: and configuring the number of the execution resources when the nodes execute the tasks.

For example, when the node performs a task of sensing the temperature of the environment in which the node is located, the amount of the execution resource may be the amount of the temperature sensor, that is, the amount of the temperature sensor used by the node to perform the task is configured by the first network functional entity.

(5) Analyzing network requirements: and determining the quality of service (QoS) grade and/or bandwidth size corresponding to the transmission of the task execution result.

Illustratively, the execution result of the sensing task executed by the node is a result obtained through semantic extraction, or when the execution result of the computing task executed by the node is a model after data modeling, the occupied bandwidth is smaller, and the first network functional entity can configure a smaller bandwidth for executing result transmission. Or, the execution result of the sensing task executed by the node is the original data, or when the execution result of the computing task executed by the node is the data, the occupied bandwidth is larger, and the first network functional entity can configure a larger bandwidth for executing result transmission.

Illustratively, when the task executed by the node is a real-time task and the transmission delay and reliability requirements are high, the first network functional entity may configure a higher QoS class for executing the result transmission, for example, configure a highest priority QoS class. Or, the task executed by the node is a non-real-time task, and when the requirements on transmission delay and reliability are low, the first network functional entity may configure a low QoS level.

(6) And data service: and providing interaction service of task execution results.

Illustratively, when the terminal device is a third-party terminal device, the first network functional entity provides a task execution result for the third-party terminal device.

It should be noted that the present application does not limit the first network function entity to implement all the functions listed above, nor does it limit the first network function entity to implement functions other than the functions listed above.

Optionally, the first network function entity may include a control unit and a data unit. The control unit is configured to implement a control function of the first network functional entity, such as a validity verification function of the task, a task disassembling function, a type configuration function of the execution resource, a quantity configuration function of the execution resource, and a network requirement analysis function. The data unit is used to implement a data plane function of the first network functional entity, such as the data service function described above.

In the communication system provided by the present application, the Nx interface is a reference point between the terminal device and the first network function entity, and is used for the terminal device and the first network function entity to interact control plane information facing a task, such as request information of the task, confirmation information of the task, terminal capability information, and the like. It is to be understood that, when the terminal device is a third party terminal device, the Nx interface may be understood as an external interface. In addition, the Nx interface can also be used as an external interface to exchange control information with a server in the DN.

The Ny interface is a reference point between the access network device and the first network functional entity, and is used for the access network device and the first network functional entity to interact task-oriented control information (for example, configuration information of a task) and/or task-oriented data information (for example, an execution result of the task). Further, the Ny interface may include a control plane Ny interface (denoted as Ny _1 interface) and a data plane Ny interface (denoted as Ny _2 interface), which are respectively used for the access network device and the first network function entity to interact task-oriented control information and task-oriented data information.

The Nz interface is another external interface, which is used for data interaction between the first network functional entity and the third-party device, for example, used for the first network functional entity to interact data information with a server in the DN, or used for the first network functional entity to interact task-oriented data information with the terminal device 2.

It should be noted that the terminal device, the access network device, and the first network functional entity related to the present application may be one or more chips, or may be a System On Chip (SOC), etc. Fig. 4 is only an exemplary drawing, and the number of devices included is not limited. Further, the communication system may include other devices in addition to the device shown in fig. 4. Names of the respective devices, the respective links, and the respective interfaces in fig. 4 are not limited, and the respective devices, the respective links, and the respective interfaces may be named by other names in addition to the names shown in fig. 4. In addition to the network elements shown in fig. 4, the system shown in fig. 4 may further include a network slice selecting network element, a network warehouse network element, an authentication service network element, a network storage network element, a network data analyzing network element, a network opening network element, and the like, which are not limited.

Alternatively, the communication system 40 shown in fig. 4 may be applied to the current 5G network and other future networks, such as a 6G network, which is not specifically limited in the embodiment of the present application.

Taking the communication system 40 shown in fig. 4 applied to the current 5G network or 6G network as an example, as shown in fig. 5a, the first network functional entity may be a Perceptual Management Function (PMF) network element, and the communication system may further include an AMF network element, an UPF network element, and a DN.

It is understood that fig. 5a is only an exemplary network element that the communication system includes, and in practical applications, the communication system may further include other network elements, such as an SMF network element, a UDM network element, a network open Function (NEF) network element, an authentication server Function (AUSF) network element, a Network Slice Selection Function (NSSF) network element, a network Function storage Function (NRF) network element, or a Policy Control Function (PCF) network element, a unified data storage (UDR) network element, an Unstructured Data Storage Function (UDSF), and the like, which are not specifically limited in this application.

The control plane of the communication system shown in fig. 5a is composed of an AMF network element and a PMF network element, where the AMF network element is oriented to conventional access and mobility management, that is, oriented to connection management, and the PMF network element is oriented to task management.

The functions of each interface can refer to the related descriptions in fig. 1 or fig. 4, and are not described herein again.

Optionally, the PMF network element may include a PMF control plane network element (denoted as PMF-C) and a PMF data plane network element (denoted as PMF-U). The PMF control plane network element is configured to implement a control function of the PMF network element, such as a validity verification function of the task, a task disassembling function, a type configuration function of the execution resource, a quantity configuration function of the execution resource, and a network requirement analysis function. The PMF data plane network element is used to implement data plane functions of the PMF network element, such as the data service functions described above. At this time, the communication system of the present application may be as shown in fig. 5 b.

It should be noted that the interface name between the network elements in fig. 4, fig. 5a, or fig. 5b is only an example, and the interface name may be other names in a specific implementation, which is not specifically limited in this embodiment of the present application.

It should be noted that the access network device, the AMF network element, the PMF network element, and the like in fig. 5a or fig. 5b are only names, and the names do not limit the device itself. In the 5G network and other future networks, network elements or entities corresponding to the access network device, the AMF network element, and the PMF network element may also be other names, which is not specifically limited in this embodiment of the present application.

In a specific implementation, each terminal device, access network device, or first network functional entity shown in fig. 4 may adopt the composition structure shown in fig. 6, or include the components shown in fig. 6. Fig. 6 is a schematic composition diagram of a communication apparatus 600 according to an embodiment of the present application, where the communication apparatus 600 may be a terminal device or a chip or a system on a chip in the terminal device; the device can also be an access network device or a chip or a system on chip in the access network device; or may be the first network functional entity or a chip or system on chip in the first network functional entity.

As shown in fig. 6, the communication device 600 includes a processor 601, a transceiver 602, and a communication link 603. Further, the communication device 600 may also include a memory 604. The processor 601, the memory 604 and the transceiver 602 may be connected via a communication line 603.

The processor 601 is a Central Processing Unit (CPU), a general purpose processor, a Network Processor (NP), a Digital Signal Processor (DSP), a microprocessor, a microcontroller, a Programmable Logic Device (PLD), or any combination thereof. The processor 601 may also be other devices with processing functions, such as, without limitation, a circuit, a device, or a software module.

A transceiver 602 for communicating with other devices or other communication networks. The other communication network may be an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), or the like. The transceiver 602 may be a module, a circuit, a transceiver, or any device capable of enabling communication.

A communication line 603 for communicating information between the various components included in the communication device 600.

A memory 604 for storing instructions and/or data. Wherein the instructions may be a computer program.

The memory 604 may be a read-only memory (ROM) or other types of static storage devices that can store static information and/or instructions, a Random Access Memory (RAM) or other types of dynamic storage devices that can store information and/or instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disc storage medium or other magnetic storage devices, and the like, without limitation.

It is noted that the memory 604 may exist separately from the processor 601 or may be integrated with the processor 601. The memory 604 may be used for storing instructions or program code or some data or the like. The memory 604 may be located within the communication device 600 or may be located outside the communication device 600, without limitation. The processor 601 is configured to execute the instructions stored in the memory 604 to implement the communication method provided by the following embodiments of the present application.

In one example, processor 601 may include one or more CPUs, such as CPU0 and CPU1 in fig. 6.

As an alternative implementation, the communication device 600 includes multiple processors, for example, the processor 607 may be included in addition to the processor 601 in fig. 6.

As an alternative implementation, the communication apparatus 600 further comprises an output device 605 and an input device 606. Illustratively, the input device 606 is a keyboard, mouse, microphone, or joystick-like device, and the output device 605 is a display screen, speaker (microphone), or the like.

It is noted that the communication apparatus 600 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system or a device with a similar structure as in fig. 6. Further, the constituent structure shown in fig. 6 does not constitute a limitation of the communication apparatus, and the communication apparatus may include more or less components than those shown in fig. 6, or combine some components, or a different arrangement of components, in addition to the components shown in fig. 6.

Fig. 6 above can be understood as a structural description of the terminal device, the access network device, or the first network functional entity from a hardware perspective. The present application also divides the first network functional entity into various modules from the perspective of logical function division, as shown in fig. 7a, for the logical module division of the first network functional entity provided by the present application.

As shown in fig. 7a, the first network function entity comprises one or more of the following modules: the system comprises a verification module, a task disassembling module, a type configuration module, a quantity configuration module, a requirement analysis module and a data service module, wherein the verification module, the task disassembling module, the type configuration module, the quantity configuration module, the requirement analysis module and the data service module respectively provide a legality verification function, a task disassembling function, a resource execution type configuration function, a resource execution quantity configuration function, a network requirement analysis function and a data service function of the tasks.

Optionally, when the first network functional entity includes a control unit and a data unit, as shown in fig. 7b, the control unit may include a verification module, a task disassembling module, a type configuration module, a quantity configuration module, and a requirement analyzing module, and the data unit may include a data service module.

It should be noted that the names of the modules in fig. 7a or fig. 7b are only an example, and the names of the modules in the specific implementation may be other names. The connection relationship between the modules in fig. 7a or fig. 7b is also only an example, and other connection relationships may be available in a specific implementation, which is not specifically limited in this embodiment of the application.

Next, a protocol stack of the access network device according to the present application will be described.

As shown in fig. 8, the access network device in the present application includes a control plane, a user plane, and a task plane (or called a computing plane). The control plane may include a task-control plane (T-CP) entity for controlling a task, where a reference point between the T-CP and the first network function entity is an Ny interface, and specifically may be an Ny _1 interface; the reference point between the T-CP and the AMF network element is the N2 interface. The control plane may further include a connection-control plane (C-CP) entity for connection-oriented control. The user plane may include a connection-user plane (C-UP) entity for connection-oriented data transmission, which has an N3 interface as a reference point with the UPF network element. The task plane may include a task-user plane (T-UP) entity for task-oriented data transmission, and a reference point between the task-user plane and the first network functional entity is an Ny interface, which may be specifically an Ny _2 interface.

Wherein, the various entities in fig. 8 can communicate with each other through an interface, for example, the T-UP entity and the T-CP entity can communicate with each other through an E2 interface, and the T-CP entity and the C-UP entity can communicate with each other through an E1 interface. Optionally, the T-UP entity and the C-UP entity can communicate with each other through an E3 interface.

Alternatively, when the access network device is composed of CU and DU, referring to fig. 9, CU may be composed of CU-CP for implementing the above-described control plane function, CU-UP for implementing the above-described user plane function, and CU-T-UP for implementing the above-described task plane function.

Optionally, in the control plane, the present application further provides a T-CP protocol, located above the RRC protocol layer, for task-related control, for example, performing task request, task disassembly, performing resource configuration, and transmitting task-related control information. Based on this, a control plane protocol stack architecture between the terminal device, the access network device, and the first network functional entity may be as shown in fig. 10.

The task-related control information refers to information other than the task execution result in the task-oriented scene, such as request information of the task, configuration information of the task, confirmation information of the task, and the like.

Optionally, the task-related control information may be transmitted between the terminal device and the access network device through one or more of the following: a task class RRC Container (e.g., T-CP-Container), a task class NAS signaling (e.g., NAS-T-CP), or a task class SRB (e.g., SRB 3). That is, the present application provides a task-like RRC container, task-like NAS signaling, or task-like SRB transport task-related control information.

Optionally, the task-related control information is transmitted through a task-like RRC container, and may be understood as: the task related control information is encapsulated in an RRC container. Similarly, the task-related control information is transmitted through the task-like NAS signaling, which can be understood as: the task related control information is encapsulated in NAS signaling. The task-related control information is transmitted through the task class SRB, which can be understood as: and mapping the control information related to the task class SRB for transmission.

Optionally, when the task-related control information is transmitted through the task-like RRC container, after receiving the task-like RRC container, the access network device forwards the task-related control information included in the task-related control information to the first network function entity, or the access network device encapsulates the task-related control information from the first network function entity in the task-like RRC container and forwards the task-related control information to the terminal device. When the control information related to the task is transmitted through the task NAS signaling, after receiving the task NAS signaling, the access network equipment forwards the task NAS signaling to the AMF network element, and then the AMF network element forwards the task NAS signaling to the first network function entity, or the first network function entity sends the control information related to the task to the access network equipment through the forwarding of the AMF network element, and the control information related to the task of the access network equipment is packaged in the task NAS signaling and is forwarded to the terminal equipment.

It should be understood that the task class RRC container described above only represents a type of RRC container newly proposed in the present application, and the name of the RRC container is not specifically limited in the present application, and other names may be provided in practical applications. Similarly, the task-type NAS signaling also only represents a new type of NAS signaling, and the task-type SRB only represents a new type of SRB, and the name of the task-type SRB is not specifically limited in the present application.

Based on the scheme, the application provides the task RRC container, the task NAS signaling or the task SRB for transmitting the task-related control information, so that the access network equipment can determine a receiver of the task-related control information, such as a first network function entity, after receiving the task-related control information transmitted through the task RRC container, the task NAS signaling or the task SRB, thereby forwarding the task-related control information to the receiver, ensuring the correct transmission direction of the task-related control information and improving the task success rate.

In the task plane, the application also provides a T-UP protocol, which is positioned above the PDCP layer or the SDAP layer and is used for transmitting the task execution result. Based on this, the task plane protocol stack architecture between the terminal device and the access network device may be as shown in fig. 11, where the SDAP layer indicates with a dashed box that the task plane protocol stack may include the SDAP layer, and at this time, the T-UP protocol layer is located above the SDAP protocol layer; alternatively, the task plane protocol stack may not include the SDAP protocol layer, and in this case, the T-UP protocol layer is located above the PDCP protocol layer.

Optionally, when the execution result of the task is transmitted between the terminal device and the access network device, there may be four mapping manners as follows:

in the first mode, a Protocol Data Unit (PDU) mapped to a PDCP, that is, a task class PDCP data PDU.

That is to say, the application distinguishes the execution result of the task in the PDCP layer, and maps the execution result to the task class PDCP data PDU, at this time, the PDCP layer has three types of PDCP data PDU: PDCP data PDU corresponding to the SRB, PDCP data PDU corresponding to the DRB and task class PDCP data PDU.

Optionally, similar to the SRB and the DRB, in this way, the present application provides a Computing Radio Bearers (CRB) for transmitting the task execution result. At this time, for example, as shown in fig. 12a, the task execution result of the task plane is first mapped to the CRB, and is mapped to the task class PDCP data PDU in the PDCP layer, and is finally transmitted by the DTCH.

And the second mode is that the task class data protocol data unit mapped to the SDAP, namely the task class SDAP data PDU.

That is to say, the method distinguishes the execution result of the task and the traditional connection-oriented service data in the SDAP layer, maps the execution result of the task to the task class SDAP data PDU, and maps the connection-oriented service data to the traditional type SDPA data PDU, namely the SDAP layer has two types of SDAP data PDUs.

Optionally, when the second method is adopted, the application also provides the CRB for the task execution result. At this time, for example, as shown in fig. 12b, the task execution result of the task plane is mapped to the task class SDAP data PDU, and then mapped to the CRB, and after the PDCP layer performs encryption integrity protection, the result is transmitted by the DTCH.

And the third mode is mapping to the task QoS flow.

That is to say, the present application distinguishes the task execution result from the traditional connection-oriented service data through the QoS flow, specifically, distinguishes the task execution result from the traditional connection-oriented service data through a QoS Flow Identifier (QFI), and the access network device and the terminal device receive the task QoS flow, so that the execution result of the QoS flow transmission task can be determined.

And the method IV maps the task class DRB.

That is, the application distinguishes the execution result of the task from the traditional connection-oriented service data through the DRB, maps the execution result of the task to the task class DRB, and maps the connection-oriented service data to the traditional type DRB.

For example, when the task plane protocol stack does not include the SDAP layer, as shown in fig. 12c, the task execution result of the task plane is first mapped to a task class DRB (denoted as DRBx and DRBy in the drawing), and is finally transmitted by DTCH after being processed by the PDCP layer and the RLC layer. Or, when the task plane protocol stack includes the SDAP layer, as shown in fig. 12d, the task execution result of the task plane is first mapped to the QoS flow, and the mapping from the QoS flow to the DRB is performed in the SDAP layer.

Optionally, the DRBs and the task classes DRBs for transmitting the connection-oriented service data may be uniformly numbered, for example, the terminal device supports 32 DRBs, that is, the terminal device supports DRBs 0 to DRBs 32, then DRBs 0 to DRBs 20 may be DRBs for transmitting the connection-oriented service data, and DRBs 21 to DRBs 31 may be task classes DRBs, at this time, DRBx and DRBy in fig. 12c and 12d may be two DRBs of DRBs 21 to DRBs 31. Of course, other DRB numbering and task class DRB distinguishing manners may exist, and this is not specifically limited in this application.

It should be noted that fig. 12c and 12d only exemplarily show two task classes DRB, and the application does not limit the number of task classes DRB. Optionally, the first manner may be adopted when the task plane protocol stack does not include the SDAP layer, or the second manner is adopted when the task plane protocol stack includes the SDAP layer, or the third manner or the fourth manner is adopted when the task plane protocol stack includes the SDAP layer, which is not specifically limited in this application.

Optionally, the method may also be used in combination with the method three and the method four, for example, by distinguishing the execution result of the task from the transmitted connection-oriented service data through QoS, when the SDPA maps the QoS flow to the DRB, the task class QoS flow is mapped to the task class DRB, and the conventional connection-oriented QoS flow is mapped to the conventional DRB.

It can be understood that the task class PDCP data PDU only represents a new type of PDCP data PDU proposed in the present application, and the name of the task class PDCP data PDU is not specifically limited in the present application, and other names may be available in practical applications. Similarly, the task class SDAP data PDU also only represents a new type of SDAP data PDU, the task class QoS stream only represents a new type of QoS stream, and the task class DRB only represents a new type of DRB, which is not specifically limited in name.

Optionally, when the structure of the access network device is as shown in fig. 9, as shown in fig. 13, the functions of the RRC protocol layer, the PDCP protocol layer corresponding to the SRB, and the T-CP protocol layer may be set in the CU-CP; the functions of the PDCP protocol layer and the SDAP protocol layer corresponding to the DRB can be set in the CU-UP; the functions of the T-UP protocol layer and the PDCP protocol layer corresponding to the task can be arranged in the CU-T-CP, and optionally, the function of the SDAP protocol layer corresponding to the task can also be arranged in the CU-T-CP.

Based on the scheme, the task execution result is transmitted by the task SDAP data PDU, the task PDCP data PDU, the task DRB or the task QoS, so that the access network equipment can identify the task execution result and directly transmit the task execution result to a task requester.

The communication method provided by the embodiment of the present application is described in detail below with reference to the communication system shown in fig. 4. First, the relationship between the devices involved in the following embodiments will be described:

the first terminal device may be any terminal device in the communication system, and when the first terminal device is an intrinsic terminal device in the RAN, the first access network device is a serving access network device of the first terminal device, or the first terminal device is a terminal device served by the first access network device.

The second terminal device and the first terminal device may be the same terminal device, or may be terminal devices other than the first terminal device in the communication system, and the second access network device is a service access network device of the second terminal device, or the second terminal device is a terminal device served by the second access network device.

Optionally, the second access network device and the first access network device may be the same access network device, and at this time, the service access network devices of the first terminal device and the second terminal device are the same and are located within the coverage area of the same access network device; or the second access network device and the first access network device may be different access network devices, and in this case, the serving access network devices of the first terminal device and the second terminal device are different and are located in the coverage area of different access network devices.

The first node is a node for executing tasks, and the type of the first node can be terminal equipment, access network equipment or an independently deployed execution unit. It should be understood that, when the first node is a terminal device or an access network device, it means that the terminal device or the access network device has a task execution capability, that is, has a sensing capability or a computing capability, for example, has a sensor. The independently deployed execution unit may be understood as a device with task execution capability that is not integrated in the terminal device or the access network device, and task configuration information or a task execution result corresponding to the independently deployed execution unit is transmitted through the terminal device or the access network device with communication capability to which the independently deployed execution unit is attached.

It is to be understood that the second terminal device represents a class of terminal devices, and the number of the second terminal devices is not particularly limited in the present application. Similarly, the second access network device represents a type of access network device, and the number of the second access network devices is not specifically limited in this application.

The communication method provided by the present application is introduced below in a scenario where the first terminal device is an endogenous terminal device in the RAN and the first node does not include an independently deployed execution unit. As shown in fig. 14, the method includes the steps of:

s1401, a first terminal device sends first information to a first network function entity through a first access network device. Correspondingly, the first network function entity receives the first information from the first terminal device through the first access network device.

Wherein the first information includes request information of the first task. Optionally, the request information of the first task may include target type information of the first task and area information corresponding to the first task, for example, taking weather of the first task as a perceived target area as an example, the target type of the first task may be "weather", and the area information corresponding to the first task is information of the target area. Or the first task is to sense the traffic jam condition of the target area, the target type of the first task is the traffic jam condition, and the area information corresponding to the first task is the information of the target area.

Optionally, when the first terminal device sends the first information to the first access network device, the first information may be transmitted through one or more of a task-like RRC container, a task-like NAS signaling, or a task-like SRB, that is, the first information may be encapsulated in the RRC container or the NAS signaling, and further may be mapped to the task-like SRB for transmission, which may refer to the foregoing related description and is not described herein again.

Optionally, after receiving the request information of the first task, the first network functional entity may further verify the validity of the first task, for example, verify whether a requester of the first task (i.e., the first terminal device) is valid, and/or verify whether the first task is valid. Upon verifying that the first task is legitimate, the following step S1402 is performed.

Optionally, after receiving the request information of the first task, the first network function entity may further send task confirmation information to the first terminal device through the first access network device, so as to notify the first terminal device that it receives the request information of the first task. Accordingly, the first terminal device may receive the task confirmation information from the first network function entity through the first access network device. When the first network functional entity further performs validity verification of the task, the task confirmation information may be sent after verifying that the first task is valid.

It should be noted that, the sequence of executing step S1402 and sending the task confirmation information by the first network functional entity is not specifically limited in this application.

S1402, the first network function entity determines at least one first node and a second task corresponding to each first node in the at least one first node.

The second task is a subtask of the first task. That is to say, after receiving the request information of the first task, the first network function entity may determine whether the first task is executed by multiple first nodes, if yes, determine multiple first nodes and a second task corresponding to each first node, and if no, determine one first node and execute the first task by the first node.

It can be understood that the second task corresponding to the first node is a second task to be executed by the first node. If the first task is completed by one first node, the second task is the same as the first task, and the second task may still be referred to as a subtask of the first task, except that in this case, the subtask of the first task is the first task itself. The present embodiment takes the first task comprising a plurality of first nodes as an example.

Optionally, the second tasks corresponding to different first nodes may be the same or different, and this is not specifically limited in this application.

Optionally, the first network functional entity may determine at least one first node according to the node capability information of the first node within its service range, and a second task corresponding to each first node in the at least one first node. The node capability information is used to indicate task execution capability of the first node, and for example, the node capability information may include a type, a number, and the like of sensors that the first node has.

Alternatively, the node capability information of the first node within the service range of the first network functional entity may be acquired by the first network functional entity before this step S1402. For example, the first network functional entity may send request information to a first node within a service range of the first network functional entity to request the first node to report the node capability information, or the first node may actively report the node capability information to the first network functional entity, which is not specifically limited in this application.

Based on the scheme, the first network function entity can obtain the task execution capacity of the first node, and provides reference for the first network function entity when the first network entity disassembles the task and determines the first node for executing the task, so that the task management efficiency and the rationality of the first network function entity are improved, and the task execution delay is reduced.

Specifically, in this embodiment, the first node that performs the second task includes the second terminal device and/or the second access network device as an example for description, and of course, the number of the second terminal device or the second access network device is not specifically limited in this application.

It should be noted that, the second terminal device executing the second task may be the same as the first terminal device, that is, the request method of the first task may execute the sub-task of the first task, and at this time, the interaction between the second terminal device and the first terminal device may not be executed in the following embodiments. The following embodiments of the present application will be described by taking as an example that the second terminal device that performs the second task is different from the first terminal device.

Optionally, the second access network device and the first access network device may be the same or different, and fig. 14 illustrates that the second access network device and the first access network device are different as an example. It is to be appreciated that the following actions performed by the second access network device are performed by the first access network device when the second access network device and the first access network device are the same.

Illustratively, taking the first task as sensing the weather of the target area as an example, the first network function entity determines at least one terminal device and/or at least one access network device for executing the first task according to the distribution of the terminal devices in the target area, the node capability information of the terminal devices, the distribution of the access network devices, and the node capability information of the access network devices. For example, the first network function entity may determine that the temperature of the target area is sensed by a second terminal device within the target area and the ambient light intensity of the target area is sensed by a second access network device within the target area.

Or, for example, taking the first task as sensing the traffic congestion condition of the target area, the first network function entity determines, according to the distribution of the terminal devices in the target area and the node capability information of the terminal devices, information such as acceleration, speed, distance, and the like, which are sensed by a plurality of second terminal devices in the target area and correspond to each other.

S1403, the first network function entity sends configuration information of at least one second task. Correspondingly, the second access network device receives the second information from the first network function entity.

And the configuration information of the second task is used for configuring the execution resources corresponding to the second task. Specifically, the configuration information of the second task may be used to configure a resource type of the execution resource corresponding to the second task, and further, may be used to configure the number of the execution resource.

For example, taking the second task corresponding to the second terminal device as the temperature of the sensing target area as an example, the execution resource corresponding to the second task corresponding to the second terminal device may be a temperature sensor, that is, the first network function entity may configure the type of the execution resource to the second terminal device as the temperature sensor, and further, may configure the number of the temperature sensors. Similarly, taking the second task corresponding to the second access network device as the ambient light intensity of the sensing target area as an example, the execution resource corresponding to the second task corresponding to the second access network device may be an ambient light sensor, that is, the first network function entity may configure the type of the execution resource to the second terminal device as the ambient light sensor, and further, may also configure the number of the ambient light sensors.

Or, for example, taking the first task as the traffic congestion condition of the sensing target area, the second task corresponding to the second terminal device 1 as the sensed acceleration, and the second task corresponding to the second terminal device 2 as the sensed instantaneous speed as examples, the execution resource corresponding to the second task corresponding to the second terminal device 1 may be an acceleration sensor, that is, the first network function entity may configure the type of the execution resource to the second terminal device 1 as an acceleration sensor, and further, may also configure the number of the acceleration sensors; the execution resource corresponding to the second task corresponding to the second terminal device 2 may be a speed sensor, that is, the first network function entity may configure the type of the execution resource to the second terminal device 2 as a speed sensor, and further, may also configure the number of the speed sensors.

Wherein, the first network function entity sends configuration information of all the second tasks determined in step S1402. If the first node corresponding to the second task is a terminal device, the first network function entity sends configuration information of the second task corresponding to the terminal device to a service access network device of the terminal device, and then the service access network device of the terminal device sends the configuration information of the second task corresponding to the terminal device; and if the first node corresponding to the second task is the access network equipment, the first network functional entity sends the configuration information of the corresponding second task to the access network equipment.

Based on this, the sending, by the first network function entity, the configuration information of the at least one second task may include: and sending configuration information of a second task corresponding to at least one first node to second access network equipment, wherein the at least one first node comprises the second access network equipment and/or second terminal equipment. Correspondingly, when the first node comprises the second terminal device, the second information received by the second access network device comprises configuration information of a second task corresponding to the second terminal device; when the first node includes the second access network device, the second information includes configuration information of a second task corresponding to the second access network device.

Optionally, when the second information includes configuration information of a second task corresponding to the second access network device, the second access network device executes the corresponding second task. When the second information includes configuration information of a second task corresponding to the second terminal device, the second access network device performs steps S1404 and S1405 described below.

And S1404, the second access network device sends configuration information of a second task corresponding to the second terminal device. Correspondingly, the second terminal device receives second task configuration information corresponding to the second terminal device from the second access network device.

Optionally, the configuration information of the second task corresponding to the second terminal device is transmitted through one or more of the task RRC container, the task NAS signaling, or the task SRB, that is, the configuration information of the second task corresponding to the second terminal device may be encapsulated in the RRC container or the NAS signaling, and further may be mapped to the task SRB for transmission, which may refer to the foregoing related description and is not described herein again.

After receiving the configuration information of the corresponding second task, the second terminal device may execute the corresponding second task according to the configuration information.

S1405, the second access network device sends the third information to the second terminal device. Correspondingly, the second terminal device receives the third information from the second access network device.

And the third information is used for determining a transmission link of an execution result of the second task corresponding to the second terminal device. The transmission link may be a sidelink between the second terminal device and the first terminal device, or may be an air interface link between the second terminal device and the second access network device.

Optionally, the third information may have different modes:

in a possible implementation manner, the third information may include configuration information of a sidelink resource, where the transmission link is a sidelink between the second terminal device and the first terminal device; or, the third information may include configuration information of an air interface resource, where the transmission link is an air interface link between the second terminal device and the second access network device.

In another possible implementation manner, the third information includes 1-bit indication information, where a transmission link is a sidelink between the second terminal device and the first terminal device when a value of the bit is "1", and a transmission link is an air interface link between the second terminal device and the second access network device when a value of the bit is "0". Or, when the value of the bit is "0", the transmission link is a sidelink between the second terminal device and the first terminal device, and when the value of the bit is "1", the transmission link is an air interface link between the second terminal device and the second access network device.

It can be understood that, in the second implementation manner, the second access network device also configures corresponding link resources to the second terminal device.

Optionally, the second access network device may send the configuration information of the second task and the third information corresponding to the second terminal device in one message, or may send the configuration information and the third information in two messages, which is not specifically limited in this application.

Optionally, the step S1404 and the step S1405 are not in strict sequence, and the step S1404 may be executed first, and then the step S1405 is executed; alternatively, step S1405 may be executed first, and then step S1404 may be executed; alternatively, step S1404 and step S1405 may be performed simultaneously.

After receiving the third information, the second terminal device may determine, according to the third information, a transmission link of an execution result of a second task corresponding to the second terminal device, and if it is determined that the transmission link is an air interface link according to the third information, perform the following steps S1406a to S1408; alternatively, if the transmission link is determined to be a sidelink according to the third information, the following step S1406b is executed.

S1406a, the second terminal device sends an execution result of the second task corresponding to the second terminal device to the second access network device. Correspondingly, the second access network device receives an execution result of the second task corresponding to the second terminal device from the second terminal device.

Optionally, the execution result of the second task corresponding to the second terminal device may be mapped to one of task class PDCP data PDU, task class SDAP data PDU, task class DRB, or task class QoS stream for transmission.

Optionally, when the execution result of the second task corresponding to the second terminal device is mapped to QoS stream transmission, the QoS class of the QoS stream may be configured by the first network functional entity. Or, when the execution result of the second task corresponding to the second terminal device is mapped to the task class PDCP data PDU or the task class SDAP data PDU or the task class QoS stream or the task class DRB, the size of the transmission bandwidth may be configured by the first network functional entity.

Optionally, when the second access network device is different from the first access network device, the second access network device further performs the following step S1407.

And S1407, the second access network equipment sends the execution result of the second task corresponding to the second terminal equipment to the first access network equipment. Correspondingly, the first access network device receives an execution result of a second task corresponding to the second terminal device from the second access network device.

Optionally, if the first node executing the second task includes the second access network device, in step S1407, the second access network device sends an execution result of the second task corresponding to the second access network device to the first access network device.

It is understood that step S1407 is not performed when the second access network device and the first access network device are the same access network device.

S1408, the first access network device sends an execution result of the at least one second task to the first terminal device. Accordingly, the first terminal device receives the result of the execution of the at least one second task from the first access network device.

And the execution result of the at least one second task comprises an execution result of a second task corresponding to the second terminal equipment and/or an execution result of a second task corresponding to the second access network equipment.

Optionally, the execution result of the at least one second task may be mapped to one of task class PDCP data PDU, task class SDAP data PDU, task class DRB, or task class QoS stream for transmission.

S1406b, the second terminal device sends an execution result of the second task corresponding to the second terminal device to the first terminal device. Correspondingly, the first terminal device receives an execution result of the second task corresponding to the second terminal device from the second terminal device.

Optionally, in this case, the execution result of the second task corresponding to the second terminal device may also be mapped to one of the task class PDCP data PDU, the task class SDAP data PDU, the task class DRB, or the task class QoS stream for transmission.

The first terminal device may obtain an execution result of the at least one second task, and may subsequently perform processing according to the execution result, which is not specifically limited in this application.

Based on the method shown in fig. 14, the first terminal device sends the request information of the first task to the first network function entity, and after receiving the request information of the task, the first network function entity may manage the first task, that is, allocate at least one first node that executes the subtasks of the first task, and finally execute the subtasks of the first task by the first node, and complete the first task in cooperation, thereby implementing a communication mode with the task as a center. In addition, when the plurality of first nodes execute the subtasks of the first task, the task execution efficiency can be improved, and the time delay can be reduced, so that the task service efficiency of the network is improved.

If the second task corresponding to the second terminal device is not successfully executed, the steps S1406a to S1408 and the step S1406b are not executed. At this time, optionally, the second terminal device may send error information to the second access network device to notify that the second task corresponding to the second terminal device is not successfully executed, and the second access network device may feed the error information back to the first network function entity, where the error information is processed by the first network function entity, for example, the error information is recorded, and in a subsequent task management process, a task is not allocated to the second terminal device, which is not limited.

The communication method provided by the present application is introduced below in a scenario where a first terminal device is an endogenous terminal device in a RAN and a first node includes an independently deployed execution unit. As shown in fig. 15, the method includes the steps of:

s1501 to S1502 are similar to steps S1401 to S1402 shown in fig. 14, except that: in step S1502, the first node that is determined by the first network functional entity to execute the second task includes an independently deployed execution unit, which is denoted as execution unit 1 in fig. 15. Furthermore, the execution unit 1 is attached to the second access network device.

S1503, similar to step S1403 shown in fig. 14, except that: the second information received by the second access network device includes configuration information of the second task corresponding to the execution unit 1.

S1504, the second access network device sends the configuration information of the second task corresponding to the execution unit 1. Correspondingly, the execution unit 1 receives configuration information of a second task corresponding to the execution unit 1 from a second access network device.

Optionally, after receiving the configuration information of the corresponding second task, the execution unit 1 may execute the second task according to the configuration information, and execute the following step S1505.

S1505, the executing unit 1 sends an execution result of the second task corresponding to the executing unit 1 to the second access network device. Correspondingly, the second access network device receives the execution result of the second task corresponding to the execution unit 1 from the execution unit 1.

S1506, the second access network device sends the execution result of the second task corresponding to the execution unit 1 to the first access network device. Correspondingly, the first access network device receives an execution result of the second task corresponding to the execution unit 1 from the second access network device.

S1507, the first access network device sends the execution result of the second task corresponding to the execution unit 1 to the first terminal device. Correspondingly, the first terminal device receives an execution result of the second task corresponding to the execution unit 1 from the first access network device.

Optionally, the execution result of the second task corresponding to the execution unit 1 may be transmitted through one or more of a task class RRC container, a task class NAS signaling, or a task class SRB.

It should be noted that, in step S1502 of this embodiment, the first node that is determined by the first network function entity and performs the second task may further include a second terminal device and/or a second access network device, at this time, the communication method shown in fig. 15 further includes a procedure that involves the second terminal device and the second access network device, and the specific process may refer to the relevant description in fig. 14, and is not described again here.

Based on the method shown in fig. 15, the first terminal device sends the request information of the first task to the first network function entity, and after receiving the request information of the task, the first network function entity may manage the first task, that is, allocate at least one first node that executes the subtasks of the first task, and finally execute the subtasks of the first task by the first node, and complete the first task in cooperation, thereby implementing a communication mode with the task as a center. In addition, when the plurality of first nodes execute the subtasks of the first task, the task execution efficiency can be improved, and the time delay can be reduced, so that the task service efficiency of the network is improved.

The communication method provided by the application is introduced in the following scenario that the first terminal device is a third-party device and the first node does not include an independently deployed execution unit. As shown in fig. 16, the method includes the steps of:

s1601, the first terminal device sends first information to a first network function entity. Correspondingly, the first network function entity receives the first information from the first terminal device.

The first information may refer to the related description in step S1401, which is not described herein again.

Optionally, in this step S1601, the first terminal device may send the first information to the first network function entity through the N3IWF entity. Accordingly, the first network function entity receives the first information from the first terminal device via the N3IWF entity.

Optionally, after receiving the request information of the first task, the first network functional entity may further perform validity verification of the first task, or may further send confirmation information to the first terminal device, which may refer to the relevant description in the embodiment shown in fig. 14, and is not described herein again.

S1602 to S1604 are the same as the steps S1402 to S1404 in the embodiment shown in fig. 14, and reference may be made to the description of the steps S1402 to S1404, which is not repeated herein.

S1605, which is different from the step S1405 in the embodiment shown in fig. 14 in the following types: the third information indicates that a transmission link of a second task corresponding to the second terminal device is an air interface link between the second terminal device and the second access network device.

S1606 is the same as step S1406a in the embodiment shown in fig. 14, and reference may be made to the related description of step S1406, which is not repeated herein.

S1607, the second access network device sends the execution result of the at least one second task to the first network function entity. Accordingly, the first network function entity receives the result of the execution of the at least one second task from the second access network device.

When the first node executing the second task includes the second terminal device, step S1607 includes an execution result of the second task corresponding to the second terminal device; when the first node executing the second task includes the second access network device, step S1607 includes an execution result of the second task corresponding to the second access network device.

S1608, the first network function entity sends an execution result of the at least one second task to the first terminal device. Correspondingly, the first terminal device receives the execution result of the at least one second task from the first network function entity.

Optionally, the first network function entity may send the execution result of the at least one second task to the first terminal device through the N3IWF entity. Accordingly, the first terminal device may receive the execution result of the at least one second task from the first network function entity through the N3IWF entity.

Based on the method shown in fig. 16, the first terminal device sends the request information of the first task to the first network function entity, and after receiving the request information of the task, the first network function entity may manage the first task, that is, allocate at least one first node that executes the subtasks of the first task, and finally execute the subtasks of the first task by the first node, and complete the first task in cooperation, thereby implementing a communication mode with the task as a center. In addition, when the plurality of first nodes execute the subtasks of the first task, the task execution efficiency can be improved, and the time delay can be reduced, so that the task service efficiency of the network is improved.

The communication method provided by the application is introduced in the following scenario that the first terminal device is a third-party device and the first node includes an independently deployed execution unit. As shown in fig. 17, the method includes the steps of:

s1701 is the same as S1601 in the embodiment shown in fig. 16, and reference may be made to the related description of S1601, which is not repeated herein.

S1702 to S1705 are similar to steps S1502 to S1505 in the embodiment shown in fig. 15, and the steps can refer to the description of steps S1502 to S1505, which is not repeated herein.

S1706, the second access network device sends an execution result of the second task corresponding to the execution unit 1 to the first network function entity. Correspondingly, the first network function entity receives an execution result of the second task corresponding to the execution unit 1 from the second access network device.

S1707, the first network function entity sends an execution result of the second task corresponding to the execution unit 1 to the first terminal device. Correspondingly, the first terminal device receives the execution result of the second task corresponding to the execution unit 1 from the first network function entity.

It should be noted that, in step S1702 in this embodiment, the first node that is determined by the first network function entity to perform the second task may further include a second terminal device and/or a second access network device, and at this time, this embodiment also performs a process related to the second terminal device and the second access network device, and the specific process may refer to the relevant description in fig. 14, and is not described again here.

Based on the method shown in fig. 17, the first terminal device sends the request information of the first task to the first network function entity, and after receiving the request information of the task, the first network function entity may manage the first task, that is, allocate at least one first node that executes the subtasks of the first task, and finally execute the subtasks of the first task by the first node, and complete the first task in cooperation, thereby implementing a communication mode with the task as a center. In addition, when the plurality of first nodes execute the subtasks of the first task, the task execution efficiency can be improved, and the time delay can be reduced, so that the task service efficiency of the network is improved.

In the above, the first network functional entity performs task management in various scenarios provided by the present application, thereby implementing a task-centric communication method.

In addition, in an implementation scenario of the present application, the first network function entity may be integrated on the access network device, or the access network device may implement a function implemented by the first network function entity. At this time, the communication system provided by the present application includes at least one terminal device and at least one access network device, and the terminal device is a terminal device endogenous to the RAN. In this scenario, the communication method provided by the present application is shown in fig. 18, and the method includes the following steps:

s1801, the first terminal device sends the first information to the first access network device. Accordingly, the first access network device receives the first information from the first terminal device.

Wherein the first information includes request information of the first task. The first information may be transmitted through one or more of a task class RRC container, task class NAS signaling, or task class SRB.

S1802, a first access network device determines at least one first node and a second task corresponding to each first node in the at least one first node.

The first access network device may implement all functions implemented by the first network function entity in step S1402, refer to the related description in step S1402, and are not described herein again.

S1803, the first access network device sends configuration information of at least one second task. Accordingly, the second access network device receives the second information from the first access network device.

The first access network device may implement all functions implemented by the first network function entity in step S1403, which may refer to the relevant description in step S1403 and is not described herein again.

The second information includes configuration information of a second task corresponding to the second access network device, and/or configuration information of a second task corresponding to the second terminal device.

S1804 to S1805 are the same as the steps S1404 to S1405 in the embodiment shown in fig. 14, and reference may be made to the description of the steps S1404 to S1405, which is not repeated herein.

After receiving the third information, the second terminal device performs the following steps S1806 to S1806a to S1808 if determining that the transmission link is an air interface link according to the third information; alternatively, if the transmission link is determined to be a sidelink according to the third information, the following step S1806b is executed.

S1806a to S1808 are the same as the steps S1406a to S1408 of the embodiment shown in fig. 14, and reference may be made to the description of the steps S1806a to S1808, which is not repeated herein.

S1806b is the same as the step S1406b of the embodiment shown in fig. 14, and reference may be made to the related description of the step S1406b, which is not repeated herein.

Based on the method shown in fig. 18, the first terminal device sends the request information of the first task to the first access network device, and after receiving the request information of the task, the first access network device may manage the first task, that is, allocate at least one first node that executes the subtasks of the first task, and finally execute the subtasks of the first task by the first node, and complete the first task in cooperation, thereby implementing a communication mode with the task as a center. In addition, when the plurality of first nodes execute the subtasks of the first task, the task execution efficiency can be improved, and the time delay can be reduced, so that the task service efficiency of the network is improved. Moreover, the method shown in fig. 18 is easy to implement without changing the existing network architecture.

In the method shown in fig. 18, the first node executing the second task does not include an independently deployed execution unit, and a communication method in which the first node executing the second task includes an independently deployed execution unit is described below, as shown in fig. 19, the method includes the following steps:

s1901 to S1902 are different from the embodiments shown in fig. 18 in the types of steps S1801 to S1802: in step S1902, the first access network device determines that the first node includes an independently deployed execution unit, which is denoted as execution unit 1 in fig. 19. Furthermore, the execution unit 1 is attached to the second access network device.

S1903, similar to step S1803 shown in fig. 18, except that: the second information received by the second access network device includes configuration information of the second task corresponding to the execution unit 1.

S1904, the second access network device sends the configuration information of the second task corresponding to the execution unit 1. Correspondingly, the execution unit 1 receives configuration information of a second task corresponding to the execution unit 1 from a second access network device.

Optionally, after receiving the configuration information of the corresponding second task, the execution unit 1 may execute the second task according to the configuration information, and execute the following step S1905.

S1905, the execution unit 1 sends the execution result of the second task corresponding to the execution unit 1 to the second access network device. Correspondingly, the second access network device receives the execution result of the second task corresponding to the execution unit 1 from the execution unit 1.

S1906, the second access network device sends the execution result of the second task corresponding to the execution unit 1 to the first access network device. Correspondingly, the first access network device receives an execution result of the second task corresponding to the execution unit 1 from the second access network device.

S1907, the first access network device sends the execution result of the second task corresponding to the execution unit 1 to the first terminal device. Correspondingly, the first terminal device receives an execution result of the second task corresponding to the execution unit 1 from the first access network device.

It should be noted that, in step S1902 of this embodiment, the first node that is determined by the first access network device to execute the second task may further include a second terminal device and/or a second access network device, at this time, the communication method shown in fig. 19 further includes a process related to the second terminal device and the second access network device, and the specific process may refer to the relevant description in fig. 18, and is not described again here.

Based on the method shown in fig. 19, the first terminal device sends the request information of the first task to the first access network device, and after receiving the request information of the task, the first access network device may manage the first task, that is, allocate at least one first node that executes the subtasks of the first task, and finally execute the subtasks of the first task by the first node, and complete the first task in cooperation, thereby implementing a communication mode with the task as a center. In addition, when the plurality of first nodes execute the subtasks of the first task, the task execution efficiency can be improved, and the time delay can be reduced, so that the task service efficiency of the network is improved. Moreover, the method shown in fig. 19 is easy to implement without changing the existing network architecture.

In the embodiments shown in fig. 14 to 19, the processor 601 in the communication apparatus 600 shown in fig. 6 may call the application program code stored in the memory 604 to instruct each device to perform the actions of each device.

In the embodiments of the present application, unless otherwise specified or conflicting with respect to logic, the terms and/or descriptions in different embodiments have consistency and may be mutually cited, and technical features in different embodiments may be combined to form a new embodiment according to their inherent logic relationship.

It is to be understood that, in the above embodiments, the methods and/or steps implemented by each device may also be implemented by a component (e.g., a chip or a circuit) applicable to the device.

The above description mainly introduces the scheme provided by the present application from the perspective of interaction between various devices. Correspondingly, the application also provides a communication device which is used for realizing the various methods. The communication device may be the terminal device in the above method embodiment, or a device including the above terminal device, or a component that can be used for the terminal device; alternatively, the communication device may be the network device in the above method embodiment, or a device including the above network device, or a component that can be used for the network device. It is to be understood that the communication device comprises corresponding hardware structures and/or software modules for performing the respective functions in order to realize the above-mentioned functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the communication apparatus may be divided into functional modules according to the method embodiments, for example, each functional module may be divided according to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

For example, the communication device is taken as the first network function entity in the above method embodiment. Fig. 20 shows a schematic structural diagram of a first network functional entity 200. The first network function 200 comprises a receiving module 2001 and a sending module 2002, and further comprises a processing module 2003. The receiving module 2001 and the transmitting module 2002 may be collectively referred to as a transceiver module, and the receiving module 2001 and the transmitting module 2002 may be separated or integrated, which is not limited in this embodiment of the present application.

Alternatively, the receiving module 2001 may be implemented by a receiving circuit, a receiver, or a communication interface. The sending module 2002 may be implemented by a sending circuit, a transmitter, or a communication interface.

Optionally, the first network function entity may further comprise a storage module (not shown in fig. 20) for storing data and/or computer programs or instructions.

Illustratively, the first network functional entity 200 may be a first network functional entity, and may also be a chip applied in the first network functional entity or other combined devices, components, etc. having the functions of the first network functional entity. When the first network functional entity 200 is a first network functional entity, the receiving module 2001 and the sending module 2002 may be transceivers, the transceivers may include antennas, radio frequency circuits, and the like, and the processing module 2003 may be a processor (or processing circuit), such as a baseband processor, in which one or more CPUs may be included. When the first network functional entity 200 is a component having the above-mentioned first network functional entity function, the receiving module 2001 and the sending module 2002 may be radio frequency units, and the processing module 2003 may be a processor (or processing circuit), such as a baseband processor. When the first network functional entity 200 is a chip system, the receiving module 2001 and the sending module 2002 may be input and output interfaces of a chip (e.g., a baseband chip), and the processing module 2003 may be a processor (or, a processing circuit) of the chip system, and may include one or more central processing units.

For example, the receiving module 2001 and the sending module 2002 may be used to perform the receiving and sending operations performed by the first network functional entity in the embodiments shown in fig. 14-19, respectively, and/or other processes to support the techniques described herein. The processing module 2003 may be used to perform operations other than transceiving operations performed by the first network function entity in the embodiments illustrated in fig. 14-19, and/or to support other processes for the techniques described herein.

Specifically, the receiving module 2001 is configured to receive first information from the first terminal device, where the first information includes request information of the first task; the sending module 2002 is configured to send configuration information of at least one second task, where the second task is a subtask of the first task, the configuration information of the second task is used to configure an execution resource corresponding to the second task, and the second task corresponds to the first node.

Optionally, the first terminal device is a terminal device served by the first access network device; a receiving module 2001, configured to receive first information from a first terminal device, including: a receiving module 2001, configured to receive the first information from the first terminal device through the first access network device.

Optionally, the receiving module 2001 is further configured to receive an execution result of a second task corresponding to at least one first node from a second access network device, where the at least one first node includes the second access network device and/or a second terminal device, and the second terminal device is a terminal device served by the second access network device; the sending module 2002 is further configured to send, to the first terminal device, an execution result of the second task corresponding to the at least one first node.

Optionally, the sending module 2002 is configured to send configuration information of at least one second task, and includes: a sending module 2002, configured to send configuration information of a second task corresponding to at least one first node to a second access network device, where the at least one first node includes the second access network device and/or a second terminal device, and the second terminal device is a terminal device served by the second access network device.

Optionally, the processing module 2003 is configured to verify the validity of the first task; a sending module 2002, configured to send configuration information of at least one second task, including: the sending module 2002 is configured to send configuration information of at least one second task when the first task is legal.

Optionally, the processing module 2003 is configured to obtain node capability information of at least one first node, where the node capability information is used to indicate task execution capability of the first node.

All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

In the present embodiment, the first network functional entity 200 is presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, the first network function 200 may take the form of the communication device 600 shown in fig. 6, as will be appreciated by those skilled in the art.

For example, the processor 601 in the communication apparatus 600 shown in fig. 6 may execute the instructions by calling a computer stored in the memory 604, so that the communication apparatus 600 executes the communication method in the above-described method embodiment.

Specifically, the function/implementation process of the receiving module 2001, the sending module 2002, or the processing module 2003 in fig. 20 may be implemented by the processor 601 in the communication apparatus 600 shown in fig. 6 calling a computer executing instruction stored in the memory 604. Alternatively, the function/implementation procedure of the processing module 2003 in fig. 20 may be implemented by the processor 601 in the communication apparatus 600 shown in fig. 6 calling a computer executing instruction stored in the memory 604, and the function/implementation procedures of the receiving module 2001 and the sending module 2002 in fig. 20 may be implemented by the transceiver 602 in the communication apparatus 600 shown in fig. 6.

Since the first network function entity 200 provided in this embodiment can perform the above-mentioned communication method, the technical effects obtained by the first network function entity can refer to the above-mentioned method embodiment, and are not described herein again.

For example, the communication device is taken as the first terminal device in the above method embodiment. Fig. 21 shows a schematic structural diagram of a first terminal device 210. The first terminal device 210 includes a receiving module 2101 and a transmitting module 2102, and further includes a processing module 2103. The receiving module 2101 and the transmitting module 2102 may be collectively referred to as a transceiver module, and the receiving module 2101 and the transmitting module 2102 may be separated or integrated, which is not limited.

Alternatively, the receiving module 2101 may be implemented by a receiving circuit, a receiver or a communication interface. The sending module 2102 may be implemented by a sending circuit, a transmitter, or a communication interface.

Optionally, the first terminal device may further comprise a storage module (not shown in fig. 21) for storing data and/or computer programs or instructions.

Illustratively, the first terminal device 210 may be the first terminal device, and may also be a chip applied in the first terminal device or other combined devices, components, and the like having the functions of the first terminal device. When the first terminal device 210 is a first terminal device, the receiving module 2101 and the transmitting module 2102 may be transceivers, the transceivers may include antennas, radio frequency circuits, and the like, and the processing module 2103 may be a processor (or processing circuit), such as a baseband processor, which may include one or more CPUs therein. When the first terminal device 210 is a component having the above-described first terminal device function, the receiving module 2101 and the transmitting module 2102 may be radio frequency units, and the processing module 2103 may be a processor (or processing circuit), such as a baseband processor. When the first terminal device 210 is a chip system, the receiving module 2101 and the transmitting module 2102 may be input and output interfaces of a chip (e.g., a baseband chip), and the processing module 2103 may be a processor (or a processing circuit) of the chip system, and may include one or more central processing units.

For example, the receiving module 2101 and the transmitting module 2102 may be used to perform the receiving and transmitting operations performed by the first terminal device in the embodiments shown in fig. 14-19, respectively, and/or other processes to support the techniques described herein. The processing module 2103 may be used to perform operations other than transceiving operations performed by the first terminal device in the embodiments illustrated in fig. 14-19, and/or other processes to support the techniques described herein.

Specifically, the sending module 2102 is configured to send first information to the first network function entity, where the first information includes request information of a first task; the receiving module 2101 is configured to receive an execution result of at least one second task, where the second task is a subtask of the first task, and the second task corresponds to the first node.

Optionally, the first terminal device is a terminal device served by the first access network device; a sending module 2102 configured to send first information to a first network function entity, comprising: a sending module 2102 configured to send the first information to the first network function entity through the first access network device.

Optionally, the receiving module 2101 is configured to receive an execution result of at least one second task, including: a receiving module 2101 is configured to receive an execution result of a second task corresponding to at least one first node from a first access network device, where the first node includes a second access network device and/or a second terminal device, and the second terminal device is a terminal device served by the second access network device.

Optionally, the receiving module 2101 is configured to receive an execution result of at least one second task, including: the receiving module 2101 is configured to receive an execution result of a second task corresponding to a second terminal device from the second terminal device.

Optionally, the receiving module 2101 is configured to receive an execution result of at least one second task, where the execution result includes: a receiving module 2101 is configured to receive a result of an execution of at least one second task from the first network function entity.

All relevant contents of the steps related to the method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

In the present embodiment, the first terminal device 210 is presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, the first terminal device 210 may take the form of the communication apparatus 600 shown in fig. 6, as will be appreciated by those skilled in the art.

In particular, the functions/implementation procedures of the receiving module 2101, the sending module 2102, or the processing module 2103 in fig. 21 may be implemented by the processor 601 in the communication device 600 illustrated in fig. 6 calling computer-executable instructions stored in the memory 604. Alternatively, the function/implementation procedure of the processing module 2103 in fig. 21 may be implemented by the processor 601 in the communication apparatus 600 shown in fig. 6 calling a computer executing instruction stored in the memory 604, and the function/implementation procedure of the receiving module 2101 and the transmitting module 2102 in fig. 21 may be implemented by the transceiver 602 in the communication apparatus 600 shown in fig. 6.

Since the first terminal device 210 provided in this embodiment can execute the above-mentioned communication method, the technical effects obtained by the first terminal device can refer to the above-mentioned method embodiment, and are not described herein again.

For example, the communication device is taken as the second access network device in the above method embodiment. Fig. 22 shows a schematic structural diagram of a second access network device 220. The second access network device 220 includes a receiving module 2201 and a transmitting module 2202, and further includes a processing module 2203. The receiving module 2201 and the transmitting module 2202 may be collectively referred to as a transceiver module, and the receiving module 2201 and the transmitting module 2202 may be separate or integrated, without limitation.

Alternatively, the receiving module 2201 may be implemented by a receiving circuit, a receiver or a communication interface. The transmitting module 2202 may be implemented by a transmitting circuit, a transmitter, or a communication interface.

Optionally, the second access network device may further include a storage module (not shown in fig. 22) for storing data and/or computer programs or instructions.

The second access network device 220 may be, for example, a second access network device, or may be a chip applied in the second access network device or other combined devices, components, and the like having the functions of the second access network device. When the second access network device 220 is a second access network device, the receiving module 2201 and the transmitting module 2202 may be transceivers, which may include antennas, radio frequency circuits, and the like, and the processing module 2203 may be a processor (or processing circuit), such as a baseband processor, which may include one or more CPUs therein. When the second access network device 220 is a component having the functionality of the second access network device described above, the receiving module 2201 and the transmitting module 2202 may be radio frequency units, and the processing module 2203 may be a processor (or processing circuitry), such as a baseband processor. When the second access network device 220 is a chip system, the receiving module 2201 and the transmitting module 2202 may be input and output interfaces of a chip (e.g., a baseband chip), and the processing module 2203 may be a processor (or processing circuit) of the chip system, and may include one or more central processing units.

For example, the receiving module 2201 and the transmitting module 2202 may be used to perform receiving and transmitting operations performed by the second access network device in the embodiments illustrated in fig. 14-19, respectively, and/or other processes to support the techniques described herein. The processing module 2203 may be used to perform operations other than transceiving operations performed by the second access network device in the embodiments illustrated in fig. 14-19, and/or to support other processes for the techniques described herein.

Specifically, the receiving module 2201 is configured to receive second information from the first network function entity, where the second information includes configuration information of a second task corresponding to the second terminal device, and the configuration information of the second task is used to configure execution resources corresponding to the second task; a sending module 2202, configured to send configuration information of a second task corresponding to a second terminal device to the second terminal device.

Optionally, the sending module 2202 is further configured to send third information to the second terminal device, where the third information is used to determine a transmission link of an execution result of a second task corresponding to the second terminal device.

Optionally, the receiving module 2201 is further configured to receive first information from the first terminal device, where the first information includes request information of a first task, and the second task is a subtask of the first task; a sending module 2202, configured to send the first information to the first network function entity.

In the present embodiment, the second access network device 220 is presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, those skilled in the art may appreciate that the second access network device 220 may take the form of the communication apparatus 600 shown in fig. 6.

Specifically, the functions/implementation procedures of the receiving module 2201, the sending module 2202 or the processing module 2203 in fig. 22 can be implemented by the processor 601 in the communication device 600 shown in fig. 6 calling the computer stored in the memory 604 to execute the instructions. Alternatively, the function/implementation procedure of the processing module 2203 in fig. 22 may be implemented by the processor 601 in the communication apparatus 600 shown in fig. 6 calling a computer executing instruction stored in the memory 604, and the function/implementation procedure of the receiving module 2201 and the transmitting module 2202 in fig. 22 may be implemented by the transceiver 602 in the communication apparatus 600 shown in fig. 6.

Since the second access network device 220 provided in this embodiment can perform the above communication method, the technical effect obtained by the second access network device can refer to the above method embodiment, and is not described herein again.

For example, the communication device is taken as the first access network device in the above method embodiment. Fig. 23 shows a schematic structural diagram of a first access network device 230. The first access network device 230 comprises a receiving module 2301 and a transmitting module 2302, and further comprises a processing module 2303. The receiving module 2301 and the transmitting module 2302 may be collectively referred to as a transceiver module, and the receiving module 2301 and the transmitting module 2302 may be separated or integrated, without limitation.

Alternatively, the receiving module 2301 may be implemented by a receiving circuit, a receiver or a communication interface. The transmitting module 2302 may be implemented by a transmitting circuit, a transmitter or a communication interface.

Optionally, the first access network device may further include a storage module (not shown in fig. 23) for storing data and/or computer programs or instructions.

Illustratively, the first access network device 230 may be a first access network device, and may also be a chip applied in the first access network device or other combined devices, components, and the like having the functions of the first access network device. When the first access network device 230 is a first access network device, the receiving module 2301 and the transmitting module 2302 may be transceivers, which may include antennas, radio frequency circuits, and the like, and the processing module 2303 may be a processor (or processing circuit), such as a baseband processor, which may include one or more CPUs therein. When the first access network device 230 is a component having the functionality of the first access network device described above, the receiving module 2301 and the transmitting module 2302 may be radio frequency units, and the processing module 2303 may be a processor (or processing circuitry), such as a baseband processor. When the first access network device 230 is a chip system, the receiving module 2301 and the transmitting module 2302 may be input and output interfaces of a chip (e.g., a baseband chip), and the processing module 2303 may be a processor (or a processing circuit) of the chip system, and may include one or more central processing units.

For example, the receiving module 2301 and the transmitting module 2302 may be used to perform receiving and transmitting operations performed by the first access network device in the embodiments illustrated in fig. 14-19, respectively, and/or other processes to support the techniques described herein. The processing module 2303 may be used to perform operations other than transceiving operations performed by the first access network device in the embodiments illustrated in fig. 14-19, and/or other processes to support the techniques described herein.

Specifically, the receiving module 2301 is configured to receive, by the first access network device, first information from the first terminal device; a sending module 2302 is configured to send first information to the first network function entity, where the first information includes request information of the first task.

Optionally, the receiving module 2301 is further configured to receive an execution result of a second task corresponding to at least one first node from a second access network device, where the second task is a subtask of the first task, the at least one first node includes the second access network device and/or a second terminal device, and the second terminal device is a terminal device served by the second access network device; the sending module 2302 is further configured to send an execution result of the second task corresponding to the at least one first node to the first terminal device.

In the present embodiment, the first access network device 230 is presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, those skilled in the art will appreciate that the first access network device 230 may take the form of the communication apparatus 600 shown in fig. 6.

In particular, the functions/implementation procedures of the receiving module 2301, the transmitting module 2302, or the processing module 2303 in fig. 23 can be implemented by the processor 601 in the communication apparatus 600 shown in fig. 6 calling the computer-executable instructions stored in the memory 604 to implement the procedures. Alternatively, the functions/implementation procedures of the processing module 2303 in fig. 23 may be implemented by the processor 601 in the communication apparatus 600 shown in fig. 6 calling a computer executing instructions stored in the memory 604, and the functions/implementation procedures of the receiving module 2301 and the transmitting module 2302 in fig. 23 may be implemented by the transceiver 602 in the communication apparatus 600 shown in fig. 6.

Since the first access network device 230 provided in this embodiment can execute the above communication method, the technical effect obtained by the first access network device may refer to the above method embodiment, and is not described herein again.

For example, the communication device is taken as the second terminal device in the above method embodiment. Fig. 24 shows a schematic structural diagram of a second terminal device 240. The second terminal device 240 includes a receiving module 2401, a transmitting module 2402, and a processing module 2403. The receiving module 2401 and the transmitting module 2402 may be collectively referred to as a transceiver module, and the receiving module 2401 and the transmitting module 2402 may be separated or integrated, without limitation.

Alternatively, the receiving module 2401 may be implemented by a receiving circuit, a receiver or a communication interface. The transmitting module 2402 may be implemented by a transmitting circuit, a transmitter or a communication interface.

Optionally, the second terminal device may further comprise a storage module (not shown in fig. 24) for storing data and/or computer programs or instructions.

The second terminal device 240 may be, for example, a second terminal device, or may be a chip applied in the second terminal device or other combined device, component, and the like having the functions of the second terminal device. When the second terminal device 240 is a second terminal device, the receiving module 2401 and the transmitting module 2402 may be transceivers, the transceivers may include an antenna, a radio frequency circuit, and the like, and the processing module 2403 may be a processor (or a processing circuit), such as a baseband processor, which may include one or more CPUs therein. When the second terminal device 240 is a component having the functions of the second terminal device, the receiving module 2401 and the transmitting module 2402 may be radio frequency units, and the processing module 2403 may be a processor (or processing circuit), such as a baseband processor. When the second terminal device 240 is a chip system, the receiving module 2401 and the transmitting module 2402 may be an input-output interface of a chip (e.g., a baseband chip), and the processing module 2403 may be a processor (or a processing circuit) of the chip system, and may include one or more central processing units.

For example, the receiving module 2401 and the sending module 2402 may be used to perform the receiving and sending operations performed by the second terminal device in the embodiments shown in fig. 14-19, respectively, and/or other processes to support the techniques described herein. Processing module 2403 may be used to perform operations other than transceiving operations performed by the second terminal device in the embodiments illustrated in fig. 14-19, and/or other processes to support the techniques described herein.

Specifically, the receiving module 2401 is configured to receive configuration information of a second task corresponding to the second terminal device from a second access network device; a processing module 2403, configured to execute the second task corresponding to the second terminal device; a sending module 2402, configured to send an execution result of the second task corresponding to the second terminal device.

Optionally, the receiving module 2401 is further configured to receive third information from the second access network device; the processing module 2403 is further configured to determine, according to the third information, a transmission link of an execution result of the second task corresponding to the second terminal device.

Optionally, when the transmission link is a sidelink between the second terminal device and the first terminal device, the sending module 2402 is configured to send an execution result of the second task corresponding to the second terminal device, and includes: a sending module 2402, configured to send, to the first terminal device, an execution result of the second task corresponding to the second terminal device.

Optionally, when the transmission link is an air interface link between the second terminal device and the second access network device, the sending module 2402 is configured to send an execution result of the second task corresponding to the second terminal device, and includes: a sending module 2402, configured to send, to the second access network device, an execution result of the second task corresponding to the second terminal device.

In the present embodiment, the second terminal device 240 is presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, the second terminal device 240 may be in the form of the communication apparatus 600 shown in fig. 6, as will be appreciated by those skilled in the art.

In particular, the functions/implementation procedures of the receiving module 2401, the sending module 2402, or the processing module 2403 in fig. 24 may be implemented by the processor 601 in the communication device 600 shown in fig. 6 calling the computer-executable instructions stored in the memory 604 to implement. Alternatively, the functions/implementation processes of the processing module 2403 in fig. 24 may be implemented by the processor 601 in the communication apparatus 600 shown in fig. 6 calling a computer executing instructions stored in the memory 604, and the functions/implementation processes of the receiving module 2401 and the transmitting module 2402 in fig. 24 may be implemented by the transceiver 602 in the communication apparatus 600 shown in fig. 6.

Since the second terminal device 240 provided in this embodiment can execute the above communication method, the technical effect obtained by the second terminal device can refer to the above method embodiment, and is not described herein again.

Optionally, an embodiment of the present application further provides a communication device, where the communication device includes a processor, and is configured to implement the method in any of the above method embodiments. In one possible design, the communication device further includes a memory. The memory for storing the necessary program instructions and data, the processor may call the program code stored in the memory to instruct the communication device to perform the method of any of the above-described method embodiments. Of course, the memory may not be in the communication device. In another possible design, the communication device further includes an interface circuit that is a code/data read/write interface circuit for receiving computer-executable instructions (which are stored in the memory, may be read directly from the memory, or may pass through other devices) and transmitting to the processor. The communication device may be a chip or a chip system, and when the communication device is a chip system, the communication device may be formed by a chip, or may include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

Optionally, an embodiment of the present application further provides a communication apparatus (for example, the communication apparatus may be a chip or a system-on-chip), which includes an interface circuit and a logic circuit, where the interface circuit is configured to obtain input information and/or output information; the logic circuit is configured to perform the method of any of the above method embodiments, process and/or generate output information based on the input information.

When the communication device is used to implement the functionality of the first network function entity in the above method embodiments:

in some possible implementations, the input information includes first information including request information of the first task. Correspondingly, the processing according to the input information may be: at least one first node and a second task corresponding to each first node in the at least one first node are determined.

In some possible implementations, the input information and the output information may include: and the at least one first node comprises second access network equipment and/or second terminal equipment, and the second terminal equipment serves the second access network equipment.

In some possible implementations, the input information may further include: node capability information of at least one first node, the node capability information indicating task execution capabilities of the first node.

When the communication apparatus is used to implement the function of the first terminal device in the above method embodiment:

in some possible implementations, the output information may include first information including request information of the first task. The input information may include a result of execution of the at least one second task.

When the communication apparatus is used to implement the function of the second terminal device in the above method embodiment:

in some possible implementations, the input information may include configuration information of a second task corresponding to the second terminal device. The output information may include a result of execution of a second task corresponding to the second terminal device.

When the communication apparatus is used to implement the function of the second access network device in the above method embodiment:

in some possible implementations, the input information may include second information, and the second information includes configuration information of a second task corresponding to the second terminal device. The output information may include configuration information of a second task corresponding to the second terminal device.

When the communication apparatus is used to implement the function of the first access network device in the above method embodiment:

in some possible implementations, the input information may include first information including request information of the first task. The output information may include the first information.

In some possible implementations, the input information may include an execution result of a second task corresponding to the at least one first node. The output information may include a result of execution of a second task corresponding to the at least one first node. The at least one first node comprises a second access network device and/or a second terminal device, and the second terminal device is a terminal device served by the second access network device.

The communication device provided in this embodiment can execute the communication method, and thus the technical effect obtained by the communication device can refer to the method embodiment, which is not described herein again.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application are all or partially generated upon loading and execution of computer program instructions on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or can comprise one or more data storage devices, such as a server, a data center, etc., that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others. In the embodiment of the present application, the computer may include the aforementioned apparatus.

While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method of communication, the method being applied to a first network function entity, the method comprising:

receiving first information from a first terminal device, wherein the first information comprises request information of a first task;

and sending configuration information of at least one second task, wherein the second task is a subtask of the first task, the configuration information of the second task is used for configuring execution resources corresponding to the second task, and the second task corresponds to the first node.

2. The method of claim 1, wherein the first terminal device is a terminal device served by a first access network device;

the receiving of the first information from the first terminal device includes:

and receiving first information from the first terminal equipment through the first access network equipment.

3. The method of claim 1, further comprising:

receiving an execution result of a second task corresponding to at least one first node from a second access network device, where the at least one first node includes the second access network device and/or a second terminal device, and the second terminal device is a terminal device served by the second access network device;

and sending an execution result of the second task corresponding to the at least one first node to the first terminal equipment.

4. The method according to any of claims 1-3, wherein said sending configuration information for at least one second task comprises:

and sending configuration information of the second task corresponding to at least one first node to second access network equipment, wherein the at least one first node comprises the second access network equipment and/or second terminal equipment, and the second terminal equipment is terminal equipment served by the second access network equipment.

5. The method according to any of claims 1-4, wherein said sending configuration information for at least one second task comprises:

verifying the validity of the first task;

and when the first task is legal, sending the configuration information of the at least one second task.

6. The method according to any one of claims 1-5, further comprising:

and acquiring node capability information of at least one first node, wherein the node capability information is used for indicating the task execution capability of the first node.

7. A communication method, applied to a first terminal device, the method comprising:

sending first information to a first network function entity, wherein the first information comprises request information of a first task;

and receiving an execution result of at least one second task, wherein the second task is a subtask of the first task, and the second task corresponds to the first node.

8. The method of claim 7, wherein the first terminal device is a terminal device served by a first access network device;

sending first information to a first network function entity, comprising:

and sending the first information to the first network function entity through the first access network equipment.

9. The method of claim 8, wherein the first information is transmitted via one or more of: the task type radio resource control RRC container, the task type non-access stratum NAS signaling or the task type radio signaling bears SRB.

10. The method of any of claims 7-9, wherein receiving results of the execution of the at least one second task comprises:

receiving an execution result of the second task corresponding to at least one first node from the first access network device, where the first node includes a second access network device and/or a second terminal device, and the second terminal device is a terminal device served by the second access network device.

11. The method of any of claims 7-9, wherein receiving results of the execution of the at least one second task comprises:

and receiving an execution result of the second task corresponding to the second terminal device from the second terminal device.

12. The method of claim 10 or 11, wherein the result of the execution of the second task maps to one of: a task class data protocol data unit of a packet data convergence protocol PDCP, a task class data protocol data unit of a service data adaptation protocol SDAP, a task class data radio bearer DRB or a task class quality of service QoS flow.

13. The method of claim 7, wherein receiving results of execution of at least one second task comprises:

receiving a result of the execution of the at least one second task from the first network function entity.

14. A communication method, applied to a second terminal device, the method comprising:

receiving configuration information of a second task corresponding to the second terminal equipment from second access network equipment;

executing the second task corresponding to the second terminal device;

and sending an execution result of the second task corresponding to the second terminal device.

15. The method of claim 14, wherein the configuration information of the second task corresponding to the second terminal device is transmitted through one or more of: the task type radio resource control RRC container, the task type non-access stratum NAS signaling or the task type radio signaling bears SRB.

16. The method according to claim 14 or 15, characterized in that the method further comprises:

receiving third information from the second access network device;

and determining a transmission link of the execution result of the second task corresponding to the second terminal device according to the third information.

17. The method of claim 16, wherein the transmission link is a sidelink between the second terminal device and the first terminal device;

sending an execution result of the second task corresponding to the second terminal device, including:

and sending an execution result of the second task corresponding to the second terminal device to the first terminal device.

18. The method of claim 16, wherein the transmission link is an air interface link between the second terminal device and the second access network device;

and sending an execution result of the second task corresponding to the second terminal device to the second access network device.

19. The method according to any of claims 16-18, wherein the result of the execution of the second task by the second terminal device is mapped to one of: a task class data protocol data unit of a packet data convergence protocol PDCP, a task class data protocol data unit of a service data adaptation protocol SDAP, a task class data radio bearer DRB or a task class quality of service QoS flow.

20. A communication method applied to a second access network device, the method comprising:

receiving second information from a first network function entity, wherein the second information comprises configuration information of a second task corresponding to second terminal equipment, and the configuration information of the second task is used for configuring execution resources corresponding to the second task;

and sending configuration information of the second task corresponding to the second terminal device.

21. The method of claim 20, wherein the configuration information of the second task corresponding to the second terminal device is transmitted through one or more of: the task type radio resource control RRC container, the task type non-access stratum NAS signaling or the task type radio signaling bears SRB.

22. The method of claim 20 or 21, further comprising:

and sending third information to the second terminal device, where the third information is used to determine a transmission link of an execution result of the second task corresponding to the second terminal device.

23. The method of claim 22, wherein the transmission link is a sidelink between the second terminal device and the first terminal device.

24. The method of claim 22, wherein the transmission link is an air interface link between the second terminal device and the second access network device.

25. The method according to any of claims 22-24, wherein the result of the execution of the second task by the second terminal device is mapped to one of: a task class data protocol data unit of a packet data convergence protocol PDCP, a task class data protocol data unit of a service data adaptation protocol SDAP, a task class data radio bearer DRB or a task class quality of service QoS flow.

26. The method according to any one of claims 20-25, further comprising:

receiving first information from a first terminal device, wherein the first information comprises request information of a first task, and the second task is a subtask of the first task;

and sending the first information to the first network function entity.

27. The method of claim 26, wherein the first information is transmitted via one or more of: radio resource control, RRC, container, non-access stratum, NAS, signaling, or radio signaling bearer, SRB.

28. The method of any of claims 20-27, wherein the second information further comprises configuration information for the second task corresponding to the second access network device.

29. A communication apparatus, characterized in that the communication apparatus comprises: an interface circuit and a logic circuit;

the interface circuit is used for acquiring input information and/or output information;

the logic circuit is configured to perform the method of any one of claims 1-6, or perform the method of any one of claims 7-13, or perform the method of any one of claims 14-19, or perform the method of any one of claims 20-28, process the input information, and/or generate the output information.

30. A computer readable storage medium storing instructions that, when executed, cause a method of any of claims 1-6 to be implemented, or cause a method of any of claims 7-13 to be implemented, or cause a method of any of claims 14-19 to be implemented, or cause a method of any of claims 20-28 to be implemented.