Data transmission method and device

Abstract

The embodiment of the invention provides a data transmission method and device, and the method comprises the steps that access network equipment receives first data from terminal equipment on a first data bearer, and the access network equipment can transmit the first data to a TPF (Task Processing Function) or a UPF (User Plane Function) based on the first data bearer or the first data. Through the method, the base station can know how to transmit the data from the user, and the communication efficiency is improved.

Description

Method and device for transmitting data Technical Field

[0001] The present invention relates to the field of communications, and more specifically, to a method and apparatus for transmitting data. Background Art

[0002] In fifth-generation (5G) communication systems, service data is transmitted between terminal devices and user plane functions (UPFs) by establishing protocol data unit (PDU) sessions. To effectively enable "anything as a service" (XaaS) in future communication systems, the concept of "tasks" has been introduced in sixth-generation (6G) communication systems. Task data is transmitted between terminal devices and task process functions (TPFs) through established task sessions. Typically, a terminal device may need to send both service data and task data to the UPF. However, when a base station receives data from a terminal device, it has no way of knowing how to forward the data.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a method and apparatus for transmitting data, so that a base station can know how to forward data from a terminal device, thereby improving communication efficiency.

[0005] In a first aspect, a method for transmitting data is provided. The method can be executed by an access network device, or can be executed by a chip or circuit configured in the access network device, and this application does not limit this.

[0006] The method includes: an access network device receives first data from a terminal device on a first data bearer; the access network device sends the first data to a TPF based on the first data bearer or the first data, and the TPF is used to interact with the terminal device for task data.

[0007] Among them, the task includes the process of achieving service goals based on the collaboration of heterogeneous resources.

[0008] Heterogeneous resources can be understood as resources that include at least one of computing, intelligence, data, and perception.

[0009] The service target may include at least one of computing, data, trust, intelligence, and perception services.

[0010] Specifically, the access network device can be any device that provides access to a communication network for authorized users in a specific area, and this application does not limit this. For example, the access network device can be a gNB in ​​a 5G network, or it can have a hierarchical RAN architecture including sNode and cNode in a 6G network.

[0011] Through the above method, the access network device can obtain the data that needs to be forwarded to the TPF, thereby improving communication efficiency.

[0012] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the access network device sends first information to the terminal device, the first information indicating that the first data bearer is used to transmit data between the terminal device and the TPF; the access network device sends the first data bearer to the TPF based on the first data bearer.

[0013] Specifically, the first data bearer may be a data bearer newly defined by the access network device. For example, if there are currently ten data radio bearers (DRBs), the access network device may define at least one of the ten DRBs as the first data bearer and indicate it to the terminal device.

[0014] Specifically, the above method can be applied to the scenario of one TPF, and also to the scenario of multiple TPFs. The multiple TPFs in the scenario of multiple TPFs use different data bearers to transmit data. For example, the terminal device interacts with TPF#1 for data of a task, and the above first data bearer is used to transmit data between the terminal device and TPF#1. Alternatively, the terminal device interacts with TPF#1 for data of task#1, the terminal device interacts with TPF#2 for data of task#2, and the terminal device interacts with TPF#3 for data of task#3, and the above first data bearer includes data bearer#1, data bearer#2, and data bearer#3, data bearer#1 is used to transmit data between the terminal device and TPF#1, data bearer#2 is used to transmit data between the terminal device and TPF#2, and data bearer#3 is used to transmit data between the terminal device and TPF#3.

[0015] Through the above method, the access network device can know to which TPF the data is forwarded based on the bearer of the received data, thereby improving communication efficiency.

[0016] In combination with the first aspect, in certain implementations of the first aspect, when multiple TPFs interact with a terminal device for data of multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data includes identification information of the first task, and the first task belongs to one of the above-mentioned multiple tasks. The above-mentioned access network device sends the above-mentioned first data to the TPF based on the above-mentioned first data bearer, including: the above-mentioned access network device sends the above-mentioned first data to the first TPF based on the above-mentioned first data bearer and the identification information of the above-mentioned first task, and the first TPF is the TPF corresponding to the above-mentioned first task.

[0017] Specifically, in the aforementioned multiple TPF scenario, multiple TPFs share the same data bearer to transmit data. In this case, the access network device learns to forward data to a TPF based on the first data bearer, but does not know which TPF among the multiple TPFs to forward the data to. Furthermore, by including identification information of the first task in the first data, the access network device can learn which TPF to forward the data to, thereby improving communication efficiency.

[0018] Specifically, the identification information of the above-mentioned first task can be carried in the service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, radio link control protocol (RLC) layer, task resource scheduler (TRS) layer, etc. of the first data, and this application does not limit this.

[0019] In combination with the first aspect, in certain implementations of the first aspect, when there are multiple task control functions (TCFs) controlling multiple TPFs to interact with the above-mentioned terminal device to perform multiple task data, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first TCF, and the first TCF is used to control the above-mentioned first TPF to interact with the above-mentioned terminal device to perform the first task data, and the above-mentioned access network device sends the first data to the TPF based on the above-mentioned first data bearer, including: the above-mentioned access network device sends the first data to the above-mentioned first TPF based on the above-mentioned first data bearer, the identification information of the above-mentioned first task, and the identification information of the above-mentioned first TCF.

[0020] Specifically, the identification information of the first TCF may be carried in the SDAP layer, PDCP layer, RLC layer, TRS layer, etc. of the first data, and this application does not limit this.

[0021] When multiple TCFs deploy multiple tasks for multiple TPFs and UEs, different TCFs may assign the same task identification information. Therefore, it is necessary to further distinguish different TPFs through the identification information of the TCF that deploys the task, so that the access network equipment knows which TPF to forward data to, which can improve communication efficiency.

[0022] In combination with the first aspect, in certain implementations of the first aspect, when multiple TPFs interact with a terminal device to exchange data of the first task, the first data includes identification information of a first task session, and the first task session is used for the terminal device to interact with the first TPF to exchange data of the first task, and the first TPF belongs to one of the multiple TPFs. The access network device sends the first data to the TPF based on the first data bearer, including: the access network device sends the first data to the first TPF based on the first data bearer and the identification information of the first task session.

[0023] Specifically, multiple TPFs establish separate task sessions with terminal devices. When one or more TCFs deploy a task for multiple TPFs, it's impossible to distinguish between different TPFs using the task's identification information. Therefore, the identification information of the first task can be replaced with the identification information of the first task session. Alternatively, the identification information of the first task and the identification information of the first TCF can be replaced with the identification information of the first task session. This allows the access network device to know which TPF to forward data to, thereby improving communication efficiency.

[0024] In combination with the first aspect, in certain implementations of the first aspect, when the above-mentioned first data carrier is a DRB, the above-mentioned first data includes second information, and the second information is used to indicate that the first data is task session data. The above-mentioned method also includes: the above-mentioned access network device sends the first data to the TPF based on the above-mentioned second information, or the above-mentioned access network device sends the first data without carrying the above-mentioned second information to the TPF based on the above-mentioned second information.

[0025] Specifically, the above "when the above-mentioned first data bearer is DRB" can be understood as the access network device not newly defining a data bearer for transmitting data between the terminal device and the TPF, or, it can be understood as the first data bearer being an existing DRB for transmitting data between the terminal device and the UPF.

[0026] Through the above method, the access network device can be informed to forward data to the TPF based on the indication information carried by the first data, which can improve communication efficiency.

[0027] In combination with the first aspect, in certain implementations of the first aspect, when multiple TPFs interact with a terminal device for data of multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first task, and the first task belongs to one of the above-mentioned multiple tasks. The above-mentioned access network device sends the first data to the TPF based on the above-mentioned second information, including: the above-mentioned access network device sends the first data to the first TPF based on the above-mentioned second information and the identification information of the above-mentioned first task, and the first TPF is the TPF corresponding to the above-mentioned first task.

[0028] Specifically, multiple TPFs in the above-mentioned multiple TPF scenario share the same data bearer to transmit data, and the shared data bearer can be considered as an existing DRB used to transmit data between the terminal device and the UPF. At this time, the access network device learns to forward data to the TPF based on the second information. Furthermore, by carrying the identification information of the first task in the first data, the access network device can know which TPF to forward the data to, which can improve communication efficiency.

[0029] Specifically, the identification information of the first task may be carried in the SDAP layer, PDCP layer, RLC layer, TRS layer, etc. of the first data, and this application does not limit this.

[0030] In combination with the first aspect, in certain implementations of the first aspect, when there are multiple TCFs controlling multiple TPFs to interact with terminal devices for data of multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first TCF, and the above-mentioned first TCF is used to control the above-mentioned first TPF to interact with the terminal device for data of the above-mentioned first task, and the above-mentioned access network device sends the first data to the TPF based on the above-mentioned second information, including: the above-mentioned access network device sends the first data to the above-mentioned first TPF based on the above-mentioned second information, the identification information of the above-mentioned first task and the identification information of the above-mentioned first TCF.

[0031] Specifically, the identification information of the first TCF may be carried in the SDAP layer, PDCP layer, RLC layer, TRS layer, etc. of the first data, and this application does not limit this.

[0032] When multiple TCFs deploy multiple tasks for multiple TPFs and UEs, different TCFs may assign the same task identification information. Therefore, it is necessary to further distinguish different TPFs through the identification information of the TCF that deploys the task, so that the access network equipment knows which TPF to forward data to, which can improve communication efficiency.

[0033] In combination with the first aspect, in certain implementations of the first aspect, when multiple TPFs interact with the above-mentioned terminal device to interact with the data of the first task, the above-mentioned first data also includes identification information of the first task session, and the first task session is used for the above-mentioned terminal device to interact with the first TPF to interact with the data of the above-mentioned first task. The first TPF belongs to one of the above-mentioned multiple TPFs, and the above-mentioned access network device sends the first data to the TPF based on the above-mentioned second information, including: the above-mentioned access network device sends the above-mentioned first data to the above-mentioned first TPF based on the above-mentioned second information and the identification information of the above-mentioned first task session.

[0034] Specifically, multiple TPFs establish separate task sessions with terminal devices. When one or more TCFs deploy a task for multiple TPFs, it's impossible to distinguish between different TPFs using the task's identification information. Therefore, the identification information of the first task can be replaced with the identification information of the first task session. Alternatively, the identification information of the first task and the identification information of the first TCF can be replaced with the identification information of the first task session. This allows the access network device to know which TPF to forward data to, thereby improving communication efficiency.

[0035] In conjunction with the first aspect, in certain implementations of the first aspect, the method further includes: the access network device receiving third information, where the third information includes at least one of the following information:

[0036] Identification information of at least one task, identification information of at least one task session, identification information of at least one TCF, each item of information included in the third information corresponds to at least one TPF; the above-mentioned access network device sends the first data to the above-mentioned first TPF based on the above-mentioned third information.

[0037] Specifically, the above “each item of information included in the third information corresponds to at least one TPF” can be understood as each item of information included in the third information can be mapped to at least one TPF.

[0038] For example, the identification information of the first task included in the third information corresponds to the IP address and TEID of the first TPF. The access network device finds the IP address and TEID of the first TPF corresponding to the first task based on the identification information of the first task carried in the first data. Furthermore, the access network device may encapsulate the IP address and TEID of the first TPF in the first data and forward the first data to the first TPF.

[0039] For another example, the identification information of the first task included in the third information corresponds to the IP address and TEID of the first TPF and the IP address and TEID of the second TPF, and the identification information of the first TCF included in the third information corresponds to the IP address and TEID of the first TPF. The access network device finds the IP address and TEID of the first TPF and the IP address and TEID of the second TPF corresponding to the first task based on the identification information of the first task carried by the first data. Further, the access network device finds the IP address of the first TPF corresponding to the first task based on the identification information of the first TCF carried by the first data. Further, the access network device can encapsulate the IP address and TEID of the first TPF in the first data and forward the first data to the first TPF.

[0040] For another example, the identification information of the first task session included in the third information corresponds to the IP address and TEID of the first TPF. The access network device finds the IP address and TEID of the first TPF corresponding to the first task session based on the identification information of the first task session carried by the first data. Further, the access network device can encapsulate the IP address and TEID of the first TPF in the first data and forward the first data to the first TPF.

[0041] Specifically, the third information may be sent from the core network side to the access network device.

[0042] Through the above method, the access network device knows to which TPF to forward data, which can improve communication efficiency.

[0043] In a second aspect, a method for transmitting data is provided. The method can be executed by a terminal device, or can also be executed by a chip or circuit configured in the terminal device, and this application does not limit this.

[0044] The method includes: the terminal device determines a first data bearer; the terminal device sends first data to the access network device on the first data bearer, the first data bearer or the first data is used by the access network device to determine to send first data to the TPF, and the TPF is used to interact with the terminal device for task data.

[0045] Among them, the task includes the process of achieving service goals based on the collaboration of heterogeneous resources.

[0046] Heterogeneous resources can be understood as resources that include at least one of computing, intelligence, data, and perception.

[0047] The service target may include at least one of computing, data, trust, intelligence, and perception services.

[0048] Specifically, the access network device can be any device that provides access to a communication network for authorized users in a specific area, and this application does not limit this. For example, the access network device can be a gNB in ​​a 5G network, or it can have a hierarchical RAN architecture including sNode and cNode in a 6G network.

[0049] Through the above method, the access network device can obtain the data that needs to be forwarded to the TPF, thereby improving communication efficiency.

[0050] In combination with the second aspect, in some implementations of the second aspect, the above method also includes: the terminal device receives first information from the access network device, and the first information indicates that the first data bearer is used to transmit data between the terminal device and the TPF.

[0051] Specifically, the first data bearer may be a data bearer newly defined by the access network device. For example, if there are currently ten data radio bearers (DRBs), the access network device may define at least one of the ten DRBs as the first data bearer and indicate it to the terminal device.

[0052] Specifically, the above method can be applied to the scenario of one TPF, and also to the scenario of multiple TPFs. The multiple TPFs in the scenario of multiple TPFs use different data bearers to transmit data. For example, the terminal device interacts with TPF#1 for data of a task, and the above first data bearer is used to transmit data between the terminal device and TPF#1. Alternatively, the terminal device interacts with TPF#1 for data of task#1, the terminal device interacts with TPF#2 for data of task#2, and the terminal device interacts with TPF#3 for data of task#3, and the above first data bearer includes data bearer#1, data bearer#2, and data bearer#3, data bearer#1 is used to transmit data between the terminal device and TPF#1, data bearer#2 is used to transmit data between the terminal device and TPF#2, and data bearer#3 is used to transmit data between the terminal device and TPF#3.

[0053] Through the above method, the access network device can know to which TPF the data is forwarded based on the bearer of the received data, thereby improving communication efficiency.

[0054] In combination with the second aspect, in certain implementations of the second aspect, when multiple TPFs interact with the terminal device to exchange data of multiple tasks, and the multiple TPFs correspond one-to-one with the multiple tasks, the above-mentioned first data includes identification information of the first task, and the first task belongs to one of the above-mentioned multiple tasks.

[0055] Specifically, in the aforementioned multiple TPF scenario, multiple TPFs share the same data bearer for data transmission. In this case, the access network device learns to forward data to a TPF based on the first data bearer, but does not know which TPF among the multiple TPFs to forward the data to. Furthermore, by having the terminal device carry identification information of the first task in the first data, the access network device can learn which TPF to forward the data to, thereby improving communication efficiency.

[0056] Specifically, the terminal device can carry the identification information of the above-mentioned first task in the SDAP layer, PDCP layer, RLC layer, TRS layer, etc. of the first data, and this application does not limit this.

[0057] In combination with the second aspect, in certain implementations of the second aspect, when there are multiple TCFs controlling multiple TPFs to interact with the above-mentioned terminal device to perform data of multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first TCF, and the first TCF is used to control the above-mentioned first TPF to interact with the above-mentioned terminal device to perform data of the above-mentioned first task.

[0058] Specifically, the terminal device can carry the identification information of the above-mentioned first TCF in the SDAP layer, PDCP layer, RLC layer, TRS layer, etc. of the first data, and this application does not limit this.

[0059] When multiple TCFs deploy multiple tasks for multiple TPFs and UEs, different TCFs may assign the same task identification information. Therefore, it is necessary to further distinguish different TPFs through the identification information of the TCF that deploys the task reported by the terminal device, so that the access network device knows which TPF to forward data to, which can improve communication efficiency.

[0060] In combination with the second aspect, in certain implementations of the second aspect, when multiple TPFs interact with the terminal device for data of the first task, the above-mentioned first data includes identification information of the first task session, which is used for the terminal device to communicate with the above-mentioned first TPF based on the above-mentioned first task, and the first TPF belongs to one of the above-mentioned multiple TPFs.

[0061] Specifically, multiple TPFs establish task sessions with terminal devices. When one or more TCFs deploy a task for multiple TPFs, it is impossible to distinguish different TPFs using the task identification information. Therefore, the terminal device can replace the identification information of the first task with the identification information of the first task session. Alternatively, the terminal device can replace the identification information of the first task and the identification information of the first TCF with the identification information of the first task session. This allows the access network device to know which TPF to forward data to, thereby improving communication efficiency.

[0062] In combination with the second aspect, in certain implementations of the second aspect, when the first data bearer is a DRB, the first data includes second information, and the second information is used to indicate that the first data is task session data.

[0063] Specifically, the above "when the above-mentioned first data bearer is DRB" can be understood as the access network device not newly defining a data bearer for transmitting data between the terminal device and the TPF, or, it can be understood as the first data bearer being an existing DRB for transmitting data between the terminal device and the UPF.

[0064] Through the above method, the access network device can be informed to forward data to the TPF based on the indication information carried by the first data, which can improve communication efficiency.

[0065] In combination with the second aspect, in certain implementations of the second aspect, when multiple TPFs interact with the terminal device to exchange data of multiple tasks, and the multiple TPFs correspond one-to-one with the multiple tasks, the above-mentioned first data also includes identification information of the first task, and the first task belongs to one of the above-mentioned multiple tasks.

[0066] Specifically, multiple TPFs in the above-mentioned multiple TPF scenario share the same data bearer to transmit data, and the shared data bearer can be considered as an existing DRB for transmitting data between the terminal device and the UPF. At this time, the access network device learns to forward data to the TPF based on the second information reported by the terminal device. Furthermore, by carrying the identification information of the first task in the first data, the access network device can know to which TPF to forward the data, which can improve communication efficiency.

[0067] Specifically, the terminal device can carry the identification information of the above-mentioned first task in the SDAP layer, PDCP layer, RLC layer, TRS layer, etc. of the first data, and this application does not limit this.

[0068] In combination with the second aspect, in certain implementations of the second aspect, when there are multiple TCFs controlling multiple TPFs to interact with terminal devices for data of multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first TCF, and the above-mentioned first TCF is the TCF that controls the above-mentioned first TPF to communicate with the terminal device based on the above-mentioned first task.

[0069] Specifically, the terminal device can carry the identification information of the above-mentioned first TCF in the SDAP layer, PDCP layer, RLC layer, TRS layer, etc. of the first data, and this application does not limit this.

[0070] When multiple TCFs deploy multiple tasks for multiple TPFs and UEs, different TCFs may assign the same task identification information. Therefore, it is necessary to further distinguish different TPFs through the identification information of the TCF that deploys the task reported by the terminal device, so that the access network device knows which TPF to forward data to, which can improve communication efficiency.

[0071] In combination with the second aspect, in certain implementations of the second aspect, when multiple TPFs interact with the above-mentioned terminal device to exchange data of the first task, the above-mentioned first data also includes identification information of the first task session, which is used for the above-mentioned terminal device to interact with the first TPF to exchange data of the above-mentioned first task, and the first TPF belongs to one of the above-mentioned multiple TPFs.

[0072] Specifically, multiple TPFs establish task sessions with terminal devices. When one or more TCFs deploy a task for multiple TPFs, it is impossible to distinguish different TPFs using the task identification information. Therefore, the terminal device can replace the identification information of the first task with the identification information of the first task session. Alternatively, the terminal device can replace the identification information of the first task and the identification information of the first TCF with the identification information of the first task session. This allows the access network device to know which TPF to forward data to, thereby improving communication efficiency.

[0073] In a third aspect, a device for transmitting data is provided, which includes: a transceiver unit for receiving first data from a terminal device on a first data bearer; the device also includes: a processing unit for determining to send the first data to the TPF based on the first data bearer or the first data; the above-mentioned transceiver unit is also used to send the first data to the TPF based on the first data bearer or the first data.

[0074] In combination with the third aspect, in certain implementations of the third aspect, the above-mentioned transceiver unit is also used to send first information to the terminal device, where the first information is used to indicate a first data bearer, and the first data bearer is used to transmit data between the terminal device and the TPF; the above-mentioned transceiver unit is also used to send first data to the TPF based on the first data bearer.

[0075] In combination with the third aspect, in certain implementations of the third aspect, when multiple TPFs communicate with a terminal device based on multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data includes identification information of the first task, and the first task belongs to one of the above-mentioned multiple tasks. The above-mentioned transceiver unit is used to send the first data to the TPF based on the first data bearer, including: the above-mentioned transceiver unit sends the above-mentioned first data to the first TPF based on the above-mentioned first data bearer and the identification information of the above-mentioned first task, and the first TPF is the TPF corresponding to the above-mentioned first task.

[0076] In combination with the third aspect, in certain implementations of the third aspect, when there are multiple TCFs controlling multiple TPFs to communicate with the above-mentioned terminal devices based on multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first TCF, and the first TCF is the TCF that controls the above-mentioned first TPF to communicate with the above-mentioned terminal device based on the above-mentioned first task. The above-mentioned transceiver unit is used to send the first data to the TPF based on the first data bearer, including: the above-mentioned transceiver unit is also used to send the first data to the above-mentioned first TPF based on the above-mentioned first data bearer, the identification information of the above-mentioned first task and the identification information of the above-mentioned first TCF.

[0077] In combination with the third aspect, in certain implementations of the third aspect, when multiple TPFs communicate with a terminal device based on a first task, the above-mentioned first data includes identification information of a first task session, and the first task session is used for the terminal device to communicate with the above-mentioned first TPF based on the above-mentioned first task. The first TPF belongs to one of the above-mentioned multiple TPFs, and the above-mentioned transceiver unit is used to send the first data to the TPF based on the above-mentioned first data bearer, including: the above-mentioned transceiver unit is used to send the first data to the above-mentioned first TPF based on the above-mentioned first data bearer and the identification information of the above-mentioned first task session.

[0078] In combination with the third aspect, in certain implementations of the third aspect, when the above-mentioned first data carrier is a DRB, the above-mentioned first data includes second information, and the second information is used to indicate that the first data is task session data, and the above-mentioned transceiver unit is also used to send the first data to the TPF based on the above-mentioned second information.

[0079] In combination with the third aspect, in certain implementations of the third aspect, when multiple TPFs communicate with a terminal device based on multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first task, and the first task belongs to one of the above-mentioned multiple tasks. The above-mentioned transceiver unit is used to send the first data to the TPF based on the above-mentioned second information, including: the above-mentioned transceiver unit is also used to send the first data to the first TPF based on the above-mentioned second information and the identification information of the above-mentioned first task, and the first TPF is the TPF corresponding to the above-mentioned first task.

[0080] In combination with the third aspect, in certain implementations of the third aspect, when there are multiple TCFs controlling multiple TPFs to communicate with terminal devices based on multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first TCF, and the above-mentioned first TCF is the TCF that controls the above-mentioned first TPF to communicate with the terminal device based on the above-mentioned first task. The above-mentioned transceiver unit is used to send the first data to the TPF based on the above-mentioned second information, including: the above-mentioned transceiver unit is used to send the first data to the above-mentioned first TPF based on the above-mentioned second information, the identification information of the above-mentioned first task, and the identification information of the above-mentioned first TCF.

[0081] In combination with the third aspect, in certain implementations of the third aspect, when multiple TPFs communicate with the above-mentioned terminal device based on the first task, the above-mentioned first data also includes identification information of the first task session, and the first task session is used for the above-mentioned terminal device to communicate with the first TPF based on the above-mentioned first task. The first TPF belongs to one of the above-mentioned multiple TPFs, and the above-mentioned transceiver unit is used to send the first data to the TPF based on the above-mentioned second information, including: the above-mentioned transceiver unit is used to send the above-mentioned first data to the above-mentioned first TPF based on the above-mentioned second information and the identification information of the above-mentioned first task session.

[0082] In conjunction with the third aspect, in certain implementations of the third aspect, the transceiver unit is further configured to receive third information, where the third information includes at least one of the following information:

[0083] The identification information of at least one task, the identification information of at least one task session, and the identification information of at least one TCF, each item of information included in the third information corresponds one to one; the above-mentioned transceiver unit is also used to send the first data to the above-mentioned first TPF based on the above-mentioned third information.

[0084] The explanation and beneficial effects of the data transmission device provided in the third aspect may refer to the data transmission method shown in the first aspect, and will not be repeated here.

[0085] In a fourth aspect, a device for transmitting data is provided, which includes: a processing unit for determining a first data bearer; the device also includes: a transceiver unit for sending first data to an access network device on the first data bearer, and the first data bearer or the first data is used by the access network device to determine to send the first data to the TPF, and the TPF is used to communicate with the terminal device based on the task.

[0086] In combination with the fourth aspect, in certain implementations of the fourth aspect, the above-mentioned transceiver unit is also used to receive first information from the access network device, and the first information is used to indicate a first data bearer, and the first data bearer is used to transmit data between the terminal device and the TPF.

[0087] In combination with the fourth aspect, in certain implementations of the fourth aspect, when multiple TPFs communicate with a terminal device based on multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data includes identification information of the first task, and the first task belongs to one of the above-mentioned multiple tasks.

[0088] In combination with the fourth aspect, in certain implementations of the fourth aspect, when there are multiple TCFs controlling multiple TPFs to communicate with the above-mentioned terminal devices based on multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first TCF, and the first TCF is the TCF that controls the above-mentioned first TPF to communicate with the above-mentioned terminal devices based on the above-mentioned first task.

[0089] In combination with the fourth aspect, in certain implementations of the fourth aspect, when multiple TPFs communicate with a terminal device based on a first task, the above-mentioned first data includes identification information of a first task session, which is used for the terminal device to communicate with the above-mentioned first TPF based on the above-mentioned first task, and the first TPF belongs to one of the above-mentioned multiple TPFs.

[0090] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the first data bearer is a DRB, the first data includes second information, and the second information is used to indicate that the first data is task session data.

[0091] In combination with the fourth aspect, in certain implementations of the fourth aspect, when multiple TPFs communicate with a terminal device based on multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first task, and the first task belongs to one of the above-mentioned multiple tasks.

[0092] In combination with the fourth aspect, in certain implementations of the fourth aspect, when there are multiple TCFs controlling multiple TPFs to communicate with terminal devices based on multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the above-mentioned first data also includes identification information of the first TCF, and the above-mentioned first TCF is the TCF that controls the above-mentioned first TPF to communicate with the terminal device based on the above-mentioned first task.

[0093] In combination with the fourth aspect, in certain implementations of the fourth aspect, when multiple TPFs communicate with the above-mentioned terminal device based on the first task, the above-mentioned first data also includes identification information of the first task session, which is used for the above-mentioned terminal device to communicate with the first TPF based on the above-mentioned first task, and the first TPF belongs to one of the above-mentioned multiple TPFs.

[0094] The explanation and beneficial effects of the data transmission device provided in the fourth aspect can refer to the data transmission method shown in the first aspect, and will not be repeated here.

[0095] In a fifth aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0096] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0097] In a sixth aspect, the present application provides a communication device, which includes: a memory for storing programs; the device also includes at least one processor for executing computer programs or instructions stored in the memory to execute the method provided by any one of the above aspects or its implementation.

[0098] In a seventh aspect, the present application provides a computer-readable storage medium, which stores program code for execution by a device, and the program code includes a method for executing any of the above aspects or its implementation method.

[0099] In an eighth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method provided by any one of the above aspects or its implementation.

[0100] In a ninth aspect, the present application provides a chip, which includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface and executes the method provided by any one of the above aspects or its implementation.

[0101] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is used to execute the method provided by any of the above aspects or its implementation methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0102] FIG1 shows a schematic diagram of a communication system architecture applicable to an embodiment of the present application.

[0103] FIG2 shows a schematic diagram of an application architecture of a communication system applicable to an embodiment of the present application.

[0104] FIG3 shows a schematic diagram of a core network architecture applicable to an embodiment of the present application.

[0105] FIG4 shows a protocol stack architecture applicable to an embodiment of the present application.

[0106] FIG5 shows a schematic diagram of a method 500 for transmitting data provided in an embodiment of the present application.

[0107] FIG6 shows a schematic diagram of a method 600 for establishing a task session provided in an embodiment of the present application.

[0108] FIG7 shows a schematic diagram of a method 700 for transmitting data provided in an embodiment of the present application.

[0109] FIG8 shows a schematic diagram of a method 800 for transmitting data provided in an embodiment of the present application.

[0110] FIG9 shows a schematic diagram of a method 900 for transmitting data provided in an embodiment of the present application.

[0111] FIG10 shows a schematic diagram of a communication device 1000 provided in an embodiment of the present application.

[0112] FIG11 shows a schematic diagram of a communication device 1100 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0113] The technical solution in this application will be described below with reference to the accompanying drawings.

[0114] The technical solutions provided in this application can be applied to various communication systems, such as: fifth generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as sixth generation (6G) mobile communication systems. The technical solutions provided in this application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0115] First, a communication system applicable to this application is briefly introduced as follows.

[0116] As an example, Figure 1 shows a schematic architecture diagram of a communication system. For example, the architecture may include user equipment (UE), a radio access network (RAN), a core network (CN), and an external network. The external network may be a data network (DN), and the RAN refers to the RAN provided in this application, or may be referred to as a RAN node, RAN device, or access network device.

[0117] A terminal device in this application may be referred to as an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.

[0118] The terminal device can be a device that provides voice / data to users, for example, a handheld device or vehicle-mounted device with a wireless connection function. At present, some examples of terminals are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (PLMNs). The terminal equipment in the network (PLMN), etc., is not limited to this in the embodiments of the present application.

[0119] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0120] In addition, in the embodiments of the present application, the terminal device can also be a terminal device in an IoT system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0121] It should be noted that the terminal device and the access network device can communicate with each other using a certain air interface technology (such as but not limited to NR or LTE technology). The terminal devices can also communicate with each other using a certain air interface technology (such as but not limited to NR or LTE technology).

[0122] In the embodiments of the present application, the device for implementing the function of the terminal device can be the terminal device, or it can be a device that can support the terminal device to implement the function, such as a chip system or chip, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0123] RAN: Also known as RAN node, RAN equipment, or access network equipment. The RAN provides access to the communications network for authorized users in a specific area. Specifically, the RAN can include wireless network equipment in the Third Generation Partnership Project (3GPP) network, as well as access points in non-3GPP networks. For ease of description, the term "access network (AN)" will be used below.

[0124] AN devices can use different wireless access technologies. There are currently two types of wireless access technologies: 3GPP access technology (for example, the wireless access technology used in the third generation (3G), fourth generation (4G) or 5G systems) and non-3GPP access technology. 3GPP access technology refers to access technology that complies with 3GPP standard specifications. For example, the access network equipment in the 5G system is called the next generation Node Base station (gNB) or RAN equipment. Non-3GPP access technologies may include air interface technologies represented by access points (APs) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code division multiple access (CDMA), etc. AN devices can allow terminal devices and the 3GPP core network to interconnect and communicate using non-3GPP technologies.

[0125] AN equipment is responsible for radio resource management, quality of service (QoS) management, data compression and encryption, etc. on the air interface side. AN equipment provides access services to terminal devices and forwards control signals and user data between terminal devices and the core network.

[0126] AN equipment may include, for example, but is not limited to: a macro base station, a micro base station (also known as a small station), 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., a home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), an AP in a WiFi system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc. It may also be a gNB or a transmission point (TRP or TP) in a 5G (e.g., NR) system, one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a distributed unit (DU), or a base station in a next-generation communication 6G system. The embodiments of the present application do not limit the specific technology and specific device form adopted by the AN equipment.

[0127] In addition to providing basic connectivity services, the AN provided in this application also needs to provide various new service capabilities such as computing, data, trust, intelligence, and perception, effectively enabling everything as a service (XaaS) in future communication systems. Therefore, future communication systems need to build endogenous integration and fusion of multi-dimensional heterogeneous resources (computing, artificial intelligence (AI) data, AI models, etc.) to efficiently provide new service capabilities.

[0128] Specifically, the process of achieving a specific goal through the collaboration of multi-dimensional resources at the network level is defined as a "task". In other words, a task refers to the process of collaborating heterogeneous resources such as computing, algorithms, connections, and data to achieve a specific goal.

[0129] In the task-centric architecture, task anchors (TA) and task executors (TE) are introduced. TA and TE manage tasks and support task lifecycle management. They ensure the quality of service (QoS) and smooth execution of tasks through the coordination and allocation of computing, algorithms, connections, and data.

[0130] TA can also be understood as the control plane function, and TE is the data processing function. TA is used to provide task management and control functions. The management and control function may include being responsible for the lifecycle management of the task, completing the deployment, startup, deletion, modification, monitoring, etc. of the task based on the task requirements, and regulating network resources to ensure the requirements of the task. In addition to the control function, the management and control function also has the function of selecting the control function. For example, the first TA with the management and control function can select the second TA to perform the control function of the task. TE is responsible for the execution of the task and performs data interaction in business logic. The task trigger source sends the task request to the TA, and the TA deploys the task to one or more TEs for execution.

[0131] In order to achieve the above task structure, a hierarchical RAN architecture is proposed, which can provide new services more efficiently.

[0132] FIG2 shows a schematic diagram of a network architecture applicable to an embodiment of the present application.

[0133] This network architecture can be applied to the 6th generation system (6GS), which includes the 6th generation core (6GC) (as shown in Figure 2 ) and a hierarchical RAN architecture (as shown in Figure 2 ).

[0134] The hierarchical RAN architecture introduces a centralized coordination node to provide task coordination within and between regions. For example, the RAN architecture includes a cluster control node (cNode) and a service service node (sNode). Exemplarily, the cNode provides regional-level centralized coordination functions for multiple sNodes, as well as coordination functions between cNodes across regions; within the cluster (or within the corresponding area where the cNode can provide centralized coordination), it provides the anchor function of the task; on the air interface, it does not provide connection functions or only provides connection control functions (the functions provided vary depending on the different designs of the hierarchical RAN architecture). The sNode provides the execution function of the task; on the air interface, it provides connection control and / or data functions (the functions provided vary depending on the different designs of the hierarchical RAN architecture).

[0135] Optionally, cNode and sNode are respectively referred to as network elements (NEs), without limitation. If the functions of cNode and sNode are separated (microservice architecture is adopted within the base station), the network functions within cNode and sNode can be further defined.

[0136] For example, cNode can be responsible for task-based control plane functions (such as TA) and data processing functions (for example, when cNode has computing power, task scheduler (TS) and TE can also be deployed to perform data processing tasks). sNode is responsible for task-based user plane functions (such as TE).

[0137] The above-mentioned layered RAN architecture supports resource coordination and service QoS assurance of multiple types of resources and multiple nodes in the form of tasks, which will ultimately bring new dimensions to future wireless communication networks (from the single dimension of connection services to new service dimensions such as connection, computing, data, intelligence, trust, algorithms, and perception that are encapsulated and provided in the form of tasks), and achieve service level agreements (SLAs) for various AI, perception, computing, data and other services, thereby further expanding the application scenarios of wireless communication networks.

[0138] In the network architecture shown in Figure 2, different nodes communicate through interfaces.

[0139] For example, cNodes and sNodes are connected to each other through the Y1 interface, cNodes are connected to each other through the Y2 interface, and sNodes are connected to each other through the Y3 interface.

[0140] For another example, a cNode can be connected to a 6GC via a Tx interface. The cNode is connected to the network access function (NAF) via a T3 interface, to the connection function-control plane (CF-C) via a T4 interface, and to the task control function (TCF) / task process function (TPF) via a T2 interface.

[0141] For another example, the sNode can be connected to the 6GC via the Ty interface. The sNode is connected to the NAF via the T5 interface, to the CF-C via the T6 interface, and to the connectivity function-user (CF-U) via the T7 interface.

[0142] It should be noted that the UE can be connected to one or more TCFs of the 6GC, or the UE can also be connected to one or more TPFs under the control of one or more TCFs of the 6GC, or the TCF of the 6GC can be connected to one or more UEs, or the TPF under the control of the TCF of the 6GC can be connected to one or more UEs, etc., and this application does not limit this. Among them, the UE can be connected to the 6GC through the hierarchical RAN, or it can be directly connected to the 6GC through non-access stratum (NAS) signaling, and this application does not limit this.

[0143] The above interface names are for illustrative purposes only and are not limited to these in the embodiments of the present application.

[0144] It should be understood that the above naming is only defined to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 6G networks and other future networks.

[0145] Among them, 6GC network elements such as TCF and TPF can refer to the description in Figure 3 below.

[0146] FIG3 shows a schematic diagram of a core network architecture applicable to an embodiment of the present application.

[0147] The network architecture includes but is not limited to: TPF, TCF, access and mobility management function (AMF), session management function (SMF), and user plane function (UPF).

[0148] This core network architecture can be applied to 6G and is called 6G core network (6GC or 6GCN).

[0149] The following is a brief introduction to each network element shown in FIG3 .

[0150] 1. TCF: Provides task control and scheduling functions on the core network side, or provides TA and TS functions. Specifically, it manages task lifecycles, such as task deployment, modification, and deletion; manages the four essential resources (computing, data, algorithms, and connections); and dynamically adjusts task configurations and schedules these resources during task execution.

[0151] 2. TPF: Provides task execution functionality on the core network side, or TE functionality. The TPF is managed and controlled by the TCF, executes tasks assigned by the TCF, and exchanges task data with other executors. Upon completion of a task, it outputs the task results in a specified manner.

[0152] 3. SMF: Mainly responsible for session management functions, completing the allocation and management of the Internet Protocol (IP) address of terminal equipment, selecting the endpoints of the UPF, policy control and charging function interface, as well as downlink data notification, and completing the establishment, release, and update processes related to the protocol data unit (PDU) session.

[0153] 4. UPF: As the interface with the data network, it performs functions such as user-plane data forwarding, session / flow-level billing and statistics, and bandwidth limiting. This includes packet routing, forwarding, and quality of service (QoS) processing for user-plane data.

[0154] 5. AMF: Mainly used for mobility management and access management. It mainly performs functions such as mobility management, access authentication / authorization, etc. In addition, it is also responsible for transmitting user policies between terminal devices and policy control function (PCF) network elements. It can receive non-access stratum (NAS) signaling (including mobility management (MM) signaling and session management (SM) signaling) of terminal devices and related signaling of access network devices (for example, N2 (next generation, NG) 2 interface) signaling at the base station granularity that interacts with AMF), complete the user registration process and forwarding of session management signaling and mobility management.

[0155] In the network architecture shown in FIG3 , network elements can communicate with each other through interfaces.

[0156] It should be understood that the network architecture shown above is only an exemplary illustration, and the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0157] It should also be understood that the functions shown in Figure 3 can be understood as network elements for implementing different functions, for example, they can be combined into network slices as needed. These network elements can each be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, or they can be software functions running on dedicated hardware, or they can be virtualized functions instantiated on a platform (for example, a cloud platform). This application does not limit the specific form of the above network elements.

[0158] It should also be understood that the above naming is only defined to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in future communication networks.

[0159] This application includes communications between UE and RAN nodes, communications between RAN nodes, and communications between RAN nodes and core network elements. The specific protocol stack for communications in this application is described below.

[0160] Figure 4 shows a protocol stack architecture according to an embodiment of the present application. The protocol stack includes a control plane protocol stack and a user plane protocol stack.

[0161] The corresponding core network element in the control plane protocol stack is taken as TCF as an example, and the corresponding core network element in the user plane protocol stack is taken as TPF as an example.

[0162] The control plane performs signaling exchanges. The task resource control (TRC) layer of the control plane between the UE and the RAN node can be an enhancement or evolution of the radio resource control (RRC) layer in the existing wireless communication protocol stack, adding control functions such as task AI, computing, and data processing on top of the existing RRC functions. TRC can be a protocol layer that includes RRC functions, or it can be a protocol layer independent of RRC that includes control functions such as task AI, computing, and data processing.

[0163] The control plane interface between RAN nodes is defined between them. To ensure reliable signaling, the Stream Control Transmission Protocol (SCTP) layer is added above the Internet Protocol (IP) layer. SCTP provides guaranteed delivery of application layer information. The application layer signaling protocol is called Yn-AP (Tx Application Protocol).

[0164] The control plane interface between RAN nodes and core network elements (TCFs) is defined. SCTP is added on top of the IP layer to ensure reliable signaling. SCTP provides guaranteed application layer information delivery. The application layer signaling protocol is called Tx / Ty-AP (Tx / Ty application protocol).

[0165] The RAN node and the core network element communicate with each other via interfaces, for example, the communication interfaces are Tx and Ty. In the embodiment of the present application, the interface names are not limited and may be other names.

[0166] The above is only an exemplary description. In the embodiments of the present application, the interface name is not limited and can also be other names.

[0167] The user plane performs data interaction. The task resource scheduler (TRS) layer of the user plane between the UE and the RAN node can be an enhancement or evolution of the medium access control (MAC) layer in the existing wireless communication protocol stack. For example, a computing power scheduling function is added to the existing air interface resource scheduling function of the MAC layer.

[0168] The user plane signaling interface between RAN nodes is defined between RAN nodes. The transport layer is built on top of the IP layer and uses the General Packet Radio System Tunneling Protocol for the User (GTP-U) over the User Datagram Protocol (UDP) / IP to carry user plane PDUs between RAN nodes.

[0169] The user plane signaling interface between the RAN node and the core network element TCF is defined between the RAN node and the core network element TCF. The transport layer is built on the IP layer and uses GTP-U on top of UDP / IP to carry user plane PDUs between the RAN node and the core network element TCF.

[0170] The above is only an exemplary description. In the embodiments of the present application, the interface name is not limited and can also be other names.

[0171] The protocol layers shown in FIG4 are for illustrative purposes only. These protocol layers may be added or deleted, and this is not limited in the embodiments of the present application.

[0172] In 5G systems, service data is transmitted between the UE and the UPF by establishing a session. In 6G or future communication systems, the concept of "task" is introduced. The UE and TPF exchange task data (also called task session data) through the established task session. When the UE needs to send both service data to the UPF and task data to the TPF, the base station cannot know to which network function the data from the UE should be forwarded.

[0173] Based on this, an embodiment of the present application may provide a method 500 for transmitting data, so that a base station may determine how to forward data from a UE, as shown in FIG5 .

[0174] In this embodiment, the method is illustrated by taking the terminal device and the access network device as the execution subjects of the interaction diagram as examples, but this application does not limit the execution subjects of the interaction diagram. For example, the access network device in Figure 5 can also be a chip, chip system, or processor that supports the method that can be implemented by the access network device, or a logic module or software that can implement all or part of the functions of the access network device; the terminal device in Figure 5 can also be a chip, chip system, or processor that supports the method that can be implemented by the terminal device, or a logic module or software that can implement all or part of the functions of the terminal device.

[0175] Step S512: The terminal device determines the first data bearer.

[0176] Specifically, the first data bearer may be a data radio bearer (DRB) for transmitting PDU session data, or a task data radio bearer (T-DRB) for transmitting task session data.

[0177] Optionally, before step S512, the method 500 further includes step S510, where the access network device sends first information to the terminal device, where the first information is used to indicate that the first data bearer is a T-DRB for transmitting task session data. Accordingly, the terminal device receives the first information from the access network device.

[0178] If step S510 is executed before step S512, the first data bearer determined by the terminal device is T-DRB; if step S510 is not executed before step S512, the first data bearer determined by the terminal device is DRB for transmitting PDU session data.

[0179] If step S510 is performed before step S512, method 500 further includes step S514, where the terminal device sends second data on the first data bearer, where the second data is task session data. Alternatively, if step S510 is not performed before step S512, method 500 includes step S514, where the terminal device sends first data on the first data bearer, where the first data carries second information, where the second information indicates that the first data contains task session data. In other words, the first data contains the second information and the second data.

[0180] In method 500, if the access network device receives the second data, the access network device forwards the second data to the TPF; if the access network device receives the first data, the access network device forwards the first data or the second data to the TPF, that is, the access network device may carry or not carry the above-mentioned second information when forwarding to the TPF.

[0181] Step S516: The access network device sends the first data or the second data to the TPF based on the first data bearer or the first data. Correspondingly, the TPF receives the first data or the second data from the access network device.

[0182] For example, if step S510 is executed before step S512, the access network device sends the second data to the TPF based on the first data bearer. If step S510 is not executed before step S512, the access network device sends the first data or the second data to the TPF based on the second information carried in the first data. In this case, the second data can also be referred to as the first data without the second information. Alternatively, if step S510 is not executed before step S512 and the terminal device does not carry the second information in the first data, the access network device sends the first data to the UPF.

[0183] Through the above method 500, the access network device can determine how to forward data from the terminal device, avoiding retention of data from the terminal device or mis-transmission of data from the terminal device, thereby improving communication efficiency. The above method 500 can also distinguish task session data from PDU session data on the terminal device side and indicate this to the access network device, thereby avoiding retention of data from the terminal device or mis-transmission of data from the terminal device on the access network device, thereby improving communication efficiency.

[0184] The following describes the technical solution of this application in detail, taking as an example an access network device that is a hierarchical RAN architecture as shown in FIG2 above, and a terminal device that is a UE. It should be noted that the access network device of this application can be any of the RANs listed above, and this application does not limit this. For example, the access network device can be a gNB in ​​a 5G system, or a hierarchical RAN architecture including cNodes and sNodes in a 6G system.

[0185] Before exchanging task data, the UE and the TPF must first establish a task session. This application first introduces a method 600 for establishing a task session between the UE and the TPF, as shown in a schematic flowchart in FIG6 .

[0186] To facilitate understanding of the technical solution of the present application, illustratively, the embodiment of the present application refers to the session established between the UE and the UPF in the 5G system as a PDU session, and the task established between the UE and the TPF in the 6G system as a task session.

[0187] Step S610: TCF deploys tasks to UE and TPF.

[0188] Specifically, as mentioned above, the process of achieving a specific goal through multi-dimensional resource collaboration at the network level is called a task. The TCF, which provides core network-side task control, is responsible for deploying tasks. For example, the TCF controls the task executor (TPF) to execute the deployed tasks and exchange task data with other task executors (e.g., UEs).

[0189] Since the UE and TPF need to exchange task data during the execution of a task, the TCF triggers the establishment of a task session between the UE and the TPF.

[0190] Step S612: TCF sends a task session establishment request to TPF. Correspondingly, TPF receives the task session establishment request from TCF.

[0191] The task session establishment request includes UE location information. For example, the UE location information may be the IP address of the cNode to which the UE is connected.

[0192] Optionally, the task session establishment request further includes at least one of the following information:

[0193] Task identification information (task ID), task session identification information (task session ID), and TCF identification information (TCF ID). It should be understood that a task contains one or more task sessions. When a task includes one task session, the task can also be called a task session. When a task includes multiple task sessions, the task identification information corresponds to the identification information of multiple task sessions.

[0194] Step S614: TPF sends the task session CN tunnel information to cNode. Correspondingly, cNode receives the task session CN tunnel information from TPF.

[0195] Exemplarily, the task session CN tunnel information includes information such as the IP address of the TPF and the tunnel endpoint identity (TEID) of the TPF.

[0196] Optionally, the task session CN tunnel information further includes at least one of the following information:

[0197] Task identification information (task ID), task session identification information (task session ID), TCF identification information (TCF ID), etc.

[0198] Step S616: The cNode sends the task session RAN tunnel information to the TPF. Correspondingly, the TPF receives the task session RAN tunnel information from the cNode.

[0199] Exemplarily, the task session RAN tunnel information includes information such as the IP address of the cNode and the TEID of the cNode.

[0200] Optionally, the task session RAN tunnel information further includes at least one of the following information:

[0201] Task identification information (task ID), task session identification information (task session ID), TCF identification information (TCF ID), etc.

[0202] In step S618, the cNode also sends the task session RAN tunnel information to the sNode. Correspondingly, the sNode receives the task session RAN tunnel information from the cNode.

[0203] Step S620: The sNode allocates a task data bearer for the task session and sends information about the task data bearer to the UE. Correspondingly, the UE receives the information about the task data bearer from the sNode.

[0204] Specifically, the information carried by the above-mentioned task data indicates at least one DRB or at least one T-DRB.

[0205] Exemplarily, when the sNode sends the information carrying the task data to the UE, the sNode may carry the first information in the information to indicate at least one T-DRB.

[0206] Optionally, the sNode also sends information such as identification information of the task (task ID), identification information of the task session (task session ID), and identification information of the TCF (TCF ID) to the UE.

[0207] Through the above method 600, a task session can be established between the UE and the TPF, so that the UE and the TPF can exchange task data through the newly established task session.

[0208] Based on the above method 600, the following describes a method for transmitting data provided in an embodiment of the present application, so that a base station can determine how to forward data from a UE.

[0209] Specifically, as mentioned above, the UE can be connected to one or more TCFs of 6GC, or the UE can be connected to one or more TPFs controlled by one or more TCFs of 6GC, or the TCF of 6GC can be connected to one or more UEs, or the TPF under the control of the TCF of 6GC can be connected to one or more UEs, etc. Specifically, the various connection modes can be mainly summarized into the following three scenarios:

[0210] Scenario 1: For a task, a TCF is deployed to a TPF and a UE for execution. In this case, the UE is connected to a TPF, and a TPF is connected to a TCF.

[0211] Scenario 2: The UE is connected to N TPFs, which are connected to one TCF.

[0212] This scenario 2 can be further divided into two situations:

[0213] (a): For N tasks, a TCF is deployed to N TPFs and UEs for execution. One TPF corresponds to one task.

[0214] (b): For a task, a TCF is deployed to N TPFs and UEs for execution.

[0215] Scenario 3: The UE is connected to N TPFs, which are connected to M TCFs.

[0216] This scenario can be further divided into two situations:

[0217] (a): For N tasks, M TCFs are deployed to N TPFs and UEs for execution. One TPF corresponds to one task.

[0218] (b): For a task, M TCFs are deployed to N TPFs and UEs for execution.

[0219] In this application, each of the N tasks includes a process of collaboratively achieving service goals based on heterogeneous resources, where heterogeneous resources may include computing, intelligence, data, perception resources, etc., and service goals may include model training, model reasoning, high-precision positioning, etc.

[0220] It can also be said that each of the N tasks is a task-based service provided through the collaborative capabilities of multi-dimensional heterogeneous resources, such as various new service capabilities such as computing, data, trust, intelligence, and perception.

[0221] Next, FIG. 7 introduces a method 700 for transmitting data provided by the present application in the above-mentioned scenario 1.

[0222] Specifically, the data transmission method 700 corresponds to two modes.

[0223] Method 1:

[0224] In step S710, the sNode sends first information to the UE, where the first information is used to indicate that the first data bearer is a T-DRB. Correspondingly, the UE receives the first information from the sNode.

[0225] Step S712: The UE determines that the first data bearer is a T-DRB according to the fact that the second data currently required to be transmitted is task session data.

[0226] Step S714: The UE sends the second data to the sNode on the first data bearer. Correspondingly, the sNode receives the second data from the UE.

[0227] The first data bearer is T-DRB or DRB.

[0228] In step S716, the sNode encapsulates the TEID corresponding to the task session in the GTP-U header of the second data, the UDP port number in the UDP header of the second data, and the IP address of the cNode in the IP header of the second data, and sends the second data to the cNode. Accordingly, the cNode receives the second data from the sNode.

[0229] The cNode determines to forward the second data to the TPF by parsing the TEID encapsulated in the GTP-U header.

[0230] In step S718, the cNode encapsulates the TEID corresponding to the task session in the GTP-U header of the second data, the UDP port number in the UDP header of the second data, and the IP address of the TPF in the IP header of the second data, and sends the second data to the TPF. Accordingly, the TPF receives the second data from the cNode.

[0231] Specifically, the cNode sends the second data to the TPF based on the first data bearer.

[0232] Exemplarily, scenario one may also be that TCF#1 deploys a task #1 to TPF and UE for execution, and at the same time, TCF#1 deploys a task #2 to the TPF and UE for execution, so that data of multiple tasks will be exchanged between a TPF and a UE. In this case, the second data sent by the UE to the sNode also includes the identification information of task #1. Specifically, the sNode sends the second data to the TPF based on the second data received on the first data bearer. Further, the TPF can know that the second data interacting with the UE is the data of task #1 based on the identification information of task #1 carried by the second data, or the TPF can know that the second data interacting with the UE is the data of task #2 based on the identification information of task #2 carried by the second data.

[0233] Alternatively, one implementation method is: if step S710 in the above method 1 is not performed, then the cNode sends data to the UPF.

[0234] Method 2:

[0235] The second method is to transmit the data of the task session and the data of the PDU session using the same data bearer. For example, the data of the task session and the data of the PDU session are both transmitted using DRB.

[0236] In step S720, the UE sends first data to the sNode on the DRB, where the first data includes second information and second data, where the second information indicates that the first data includes second data, and the second data is task session data. Accordingly, the sNode receives the first data from the UE.

[0237] Exemplarily, the UE may include the field of the above-mentioned second information in any layer of the service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, radio link control protocol (RLC) layer, and TRS layer of the first data, and this application does not limit this.

[0238] Step S722: sNode sends first data to cNode.

[0239] The cNode determines to forward the first data or the second data to the TPF by parsing the second information.

[0240] In step S724, the cNode encapsulates the TEID corresponding to the task session in the GTP-U header of the first data or the second data, the UDP port number in the UDP header of the first data, and the IP address of the TPF in the IP header of the first data, and then sends the first data or the second data to the TPF. Accordingly, the TPF receives the first data or the second data from the cNode.

[0241] Specifically, the cNode forwards the first data or the second data to the TPF, that is, the cNode may carry or not carry the second information when forwarding to the TPF. It should be understood that the second data can also be called the first data without the second information.

[0242] Specifically, scenario one may also be that TCF#1 deploys a task #1 to the TPF and UE for execution, and at the same time, TCF#1 deploys a task #2 to the TPF and UE for execution, so that data of multiple tasks will be exchanged between a TPF and the UE. In this case, the first data sent by the UE to the sNode also includes task identification information. Exemplarily, the cNode sends the first data to the TPF based on the second information. Further, the TPF can know that the first data interacting with the UE is the data of task #1 based on the identification information of task #1 carried by the first data, or the TPF can know that the first data interacting with the UE is the data of task #2 based on the identification information of task #2 carried by the first data.

[0243] Alternatively, one implementation method is: if the terminal device does not carry the second information in the first data, then the cNode sends the data to the UPF.

[0244] Through the above method 700, the base station can determine how to forward uplink data from the terminal device, thereby improving communication efficiency. The above method 700 can also enable the UE to determine how to send task session data to the base station, thereby improving communication efficiency.

[0245] FIG8 introduces a method 800 for transmitting data provided by the present application in the above-mentioned scenario 2.

[0246] Specifically, the data transmission method 800 corresponding to the case (a) of the above scenario 2 includes three methods.

[0247] Method 1:

[0248] Method 1 is to use different data bearers for task session data and PDU session data.

[0249] In step S810, the sNode sends first information to the UE, where the first information is used to indicate that the first data bearer is a T-DRB. Correspondingly, the UE receives the first information from the sNode.

[0250] Specifically, the first data bearer includes N data bearers, which are N T-DRBs for transmitting task session data. The N T-DRBs correspond one-to-one to the N task sessions, and the N task sessions correspond one-to-one to the N TPFs. N is a positive integer greater than 1.

[0251] In step S812, the UE determines that the first data bearer is T-DBR based on the second data currently required to be transmitted being data of a task session. Further, the UE may determine that the second data currently required to be transmitted is data of a first task performed by the UE and the first TPF, and the first task is one of the N tasks.

[0252] In step S814, the UE sends the second data to the sNode on the data bearer #1 corresponding to the first task. The data bearer #1 belongs to one of the N T-DRBs. Accordingly, the sNode receives the second data from the UE.

[0253] In step S816, the sNode encapsulates the TEID corresponding to the task session in the GTP-U header of the second data, the UDP port number in the UDP header of the second data, and the IP address of the cNode in the IP header of the second data, and sends the second data to the cNode. Accordingly, the cNode receives the second data from the sNode.

[0254] In step S818, the cNode encapsulates the TEID corresponding to the task session in the GTP-U header of the second data, the UDP port number in the UDP header of the second data, and the IP address of the first TPF in the IP header of the second data, and sends the second data to the first TPF. In response, the first TPF receives the second data from the cNode.

[0255] Specifically, the cNode sends the second data to the first TPF based on data bearer #1.

[0256] Alternatively, one implementation method is: if step S810 in the above method 1 is not performed, then the cNode sends data to the UPF.

[0257] Method 2:

[0258] In Method 2, task session data and PDU session data are transmitted using different data bearers. However, unlike Method 1, N different task sessions are transmitted using the same data bearer. In other words, in Method 1, any one of the N task sessions corresponds to one data bearer, and N task sessions correspond to N data bearers. In Method 2, N task sessions correspond to one data bearer.

[0259] Step S820: The sNode sends first information to the UE, where the first information is used to indicate that the first data bearer is a T-DRB. Correspondingly, the UE receives the first information from the sNode.

[0260] Step S822: The UE determines that the first data bearer is a T-DRB according to the fact that the third data currently required to be transmitted is task session data.

[0261] Step S824: The UE sends the third data to the sNode on the first data bearer. Correspondingly, the sNode receives the third data from the UE.

[0262] Specifically, the third data sent by the UE to the sNode includes the identification information of the first task. That is, the third data includes the identification information of the first task and the second data. The first task is any one of the N tasks, and the second data is the data of the task session corresponding to the first task.

[0263] In step S826, the sNode encapsulates the TEID corresponding to the task session in the GTP-U header of the third data, the UDP port number in the UDP header of the third data, and the IP address of the cNode in the IP header of the third data, and sends the third data to the cNode. Accordingly, the cNode receives the third data from the sNode.

[0264] In step S828, the cNode encapsulates the TEID corresponding to the task session in the GTP-U header of the third data or the second data, encapsulates the UDP port number in the UDP header of the third data or the second data, and encapsulates the IP address of the first TPF in the IP header of the third data or the second data, and sends the third data or the second data to the first TPF. Accordingly, the first TPF receives the third data or the second data from the cNode. It should be understood that the second data can also be referred to as third data that does not carry the identification information of the first task.

[0265] Specifically, the cNode forwards the third data or the second data to the first TPF, that is, the cNode may carry or not carry the identification information of the first task when forwarding the data to the first TPF.

[0266] The cNode sends the third data or the second data to the TPF based on the first data bearer. Further, the cNode sends the third data or the second data to the first TPF among the N TPFs based on the identification information of the first task.

[0267] Alternatively, one implementation method is: if step S820 in the above-mentioned method 2 is not executed and the terminal device does not carry the identification information of the first task in the third data, then the cNode sends data to the UPF.

[0268] Method 3:

[0269] Mode 3 is to transmit the data of the task session and the data of the PDU session using the same data bearer. For example, the data of N different task sessions and the data of the PDU session are all transmitted using DRB.

[0270] In step S830, the UE sends fourth data to the sNode over the DRB. The fourth data includes the second information, identification information of the first task, and second data. The second information indicates that the fourth data includes the second data, the first task is any one of the N tasks, and the second data is data of the task session corresponding to the first task. Accordingly, the sNode receives the fourth data from the UE.

[0271] Exemplarily, the UE may carry the field of the second information and the field of the identification information of the first task in the SDAP layer, PDCP layer, RLC layer, TRS layer, etc. of the fourth data, and this application does not limit this.

[0272] Step S832: sNode sends fourth data to cNode.

[0273] The cNode parses the second information and determines to forward the fourth data or the second data to the TPF. In step S834, the cNode encapsulates the TEID corresponding to the task session in the GTP-U header of the fourth data or the second data, the UDP port number in the UDP header of the fourth data or the second data, and the IP address of the first TPF in the IP header of the fourth data or the second data, and then sends the fourth data or the second data to the first TPF. Accordingly, the first TPF receives the fourth data or the second data from the cNode.

[0274] Specifically, the cNode forwards the fourth data or the second data to the first TPF, that is, the cNode may carry or not carry the second information and the identification information of the first task when forwarding to the first TPF.

[0275] The cNode sends the fourth data or the second data to the TPF based on the second information. Furthermore, the cNode sends the fourth data or the second data to the first TPF among the N TPFs based on the identification information of the first task. It should be understood that the second data can also be referred to as fourth data that does not carry the identification information of the first task and the second information.

[0276] Additionally, one implementation method is: if the terminal device does not carry the second information and the identification information of the first task in the fourth data, then the cNode sends the data to the UPF.

[0277] The above description includes three methods for transmitting data in the method 800 corresponding to case (a) of scenario 2. The method 800 corresponding to case (b) of scenario 2 also includes three methods, of which method 1 corresponding to case (b) is similar to method 1 corresponding to case (a) and will not be described in detail here. Method 2 corresponding to case (b) differs from method 2 corresponding to case (a) in that the identification information of the first task carried in the third data sent in step S824 is replaced with the identification information of the first task session. When N TPFs perform the same task with the UE, the identification information of the first task carried in the third data sent in step S824 cannot enable the cNode to identify which TPF the third data is to be sent to. In this case, each of the N TPFs transmits data of a task session in the task to the terminal. The cNode needs to identify the task session identifier to identify the TPF to which the third data should be sent. Method 3 corresponding to case (b) differs from method 3 corresponding to case (a) in that the identification information of the first task carried in the fourth data sent in step S830 is replaced with the identification information of the first task session. When N TPFs and the UE execute the same task, the fourth data sent in step S830 carries the identification information of the first task, which does not enable the cNode to identify which TPF the fourth data is to be sent to. Similarly, the cNode needs to identify the TPF to which the fourth data should be sent based on the identification of the task session.

[0278] Through the above method 800, the base station can determine how to forward uplink data from the terminal device when there are multiple task processing functions, thereby improving communication efficiency. The above method 800 can also enable the UE to determine how to send task session data to the base station when there are multiple task processing functions, thereby improving communication efficiency.

[0279] FIG9 introduces a method 900 for transmitting data provided by the present application in the above-mentioned scenario three.

[0280] Specifically, the data transmission method 900 corresponding to the above scenario three (a) includes three methods.

[0281] Method 1:

[0282] Method 1 is to use different data bearers for task session data and PDU session data.

[0283] In step S910, the sNode sends first information to the UE, where the first information is used to indicate that the first data bearer is a T-DRB. Correspondingly, the UE receives the first information from the sNode.

[0284] Specifically, the first data bearer includes N data bearers, which are N T-DRBs for transmitting task session data. The N T-DRBs correspond one-to-one to the N task sessions, and the N task sessions correspond one-to-one to the N TPFs. N is a positive integer greater than 1.

[0285] In step S912, the UE determines that the first data bearer is a T-DRB based on the second data currently required to be transmitted being data of a task session. Further, the UE may determine that the second data currently required to be transmitted is data of a first task performed by the UE and the first TPF, and the first task is one of the N tasks.

[0286] In step S914, the UE sends the second data to the sNode on the data bearer #1 corresponding to the first task. The data bearer #1 belongs to one of the N T-DRBs. Accordingly, the sNode receives the second data from the UE.

[0287] In step S916, the sNode encapsulates the TEID corresponding to the task session in the GTP-U header of the second data, the UDP port number in the UDP header of the second data, and the IP address of the cNode in the IP header of the second data, and sends the second data to the cNode. Accordingly, the cNode receives the second data from the sNode.

[0288] In step S918, the cNode encapsulates the TEID corresponding to the task session in the GTP-U header of the second data, the UDP port number in the UDP header of the second data, and the IP address of the first TPF in the IP header of the second data, and sends the second data to the first TPF. Accordingly, the first TPF receives the second data from the cNode.

[0289] Specifically, the cNode sends the second data to the first TPF based on data bearer #1.

[0290] Alternatively, one implementation method is: if step S910 in the above method 1 is not performed, then the cNode sends data to the UPF.

[0291] Method 2:

[0292] In Method 2, task session data and PDU session data are transmitted using different data bearers. However, unlike Method 1, N different task sessions are transmitted using the same data bearer. In other words, in Method 1, any one of the N task sessions corresponds to one data bearer, and N task sessions correspond to N data bearers. In Method 2, N task sessions correspond to one data bearer.

[0293] In step S920, the sNode sends first information to the UE, where the first information is used to indicate that the first data bearer is a T-DRB. Correspondingly, the UE receives the first information from the sNode.

[0294] Step S922: The UE determines that the first data bearer is a T-DRB according to the fifth data currently required to be transmitted being data of a task session.

[0295] Step S924: The UE sends the fifth data to the sNode on the first data bearer. Correspondingly, the sNode receives the fifth data from the UE.

[0296] Specifically, the fifth data sent by the UE to the sNode includes the identification information of the first task and the identification information of the first TCF. The first TCF is the TCF that controls the communication between the first TPF and the UE based on the first task. That is, the fifth data contains the identification information of the first task, the identification information of the first TCF and the second data. The first task is any one of the N tasks, and the second data is the data of the task session corresponding to the first task. When there are M TCFs deploying N tasks for N TPFs and UEs, different TCFs may assign the same task identification information. Therefore, it is necessary to distinguish different TPFs through the identification information of the TCF that deploys the task and the identification information of the task.

[0297] In step S926, the sNode encapsulates the TEID corresponding to the task session in the GTP-U header of the fifth data, the UDP port number in the UDP header of the fifth data, and the IP address of the cNode in the IP header of the fifth data, and sends the fifth data to the cNode. Accordingly, the cNode receives the fifth data from the sNode.

[0298] In step S928, the cNode encapsulates the TEID corresponding to the task session in the GTP-U header of the fifth data or the second data, encapsulates the UDP port number in the UDP header of the fifth data or the second data, and encapsulates the IP address of the first TPF in the IP header of the fifth data or the second data, and sends the fifth data or the second data to the first TPF. Accordingly, the first TPF receives the fifth data or the second data from the cNode. It should be understood that the second data can also be referred to as the fifth data that does not carry the identification information of the first task and the identification information of the first TCF.

[0299] Specifically, the cNode forwards the fifth data or the second data to the first TPF, that is, the cNode may carry or not carry the identification information of the first task and the identification information of the first TCF when forwarding to the first TPF.

[0300] The cNode sends the fifth data or the second data to the TPF based on the first data bearer. Further, the cNode sends the fifth data or the second data to the first TPF among the N TPFs based on the identification information of the first task and the identification information of the first TCF.

[0301] Alternatively, one implementation method is: if step S920 in the above-mentioned method 2 is not executed and the terminal device does not carry the identification information of the first task and the identification information of the first TCF in the fifth data, then the cNode sends data to the UPF.

[0302] Method 3:

[0303] Mode 3 is to transmit the data of the task session and the data of the PDU session using the same data bearer. For example, the data of N different task sessions and the data of the PDU session are all transmitted using DRB.

[0304] In step S930, the UE sends sixth data to the sNode over the DRB. The sixth data includes the second information, identification information of the first task, identification information of the first TCF, and the second data. The second information indicates that the sixth data includes the second data, the first task is any one of the N tasks, and the second data is data of the task session corresponding to the first task. Accordingly, the sNode receives the sixth data from the UE.

[0305] Exemplarily, the UE may carry the field of the second information, the field of the identification information of the first task, and the field of the identification information of the first TCF in the SDAP layer, PDCP layer, RLC layer, TRS layer, etc. of the sixth data, and this application does not limit this.

[0306] Step S932: sNode sends sixth data to cNode.

[0307] The cNode determines to forward the sixth data or the second data to the TPF by parsing the second information.

[0308] In step S934, the cNode encapsulates the TEID corresponding to the task session in the GTP-U header of the sixth data or the second data, encapsulates the UDP port number in the UDP header of the sixth data or the second data, and encapsulates the IP address of the first TPF in the IP header of the sixth data or the second data, and sends the sixth data or the second data to the first TPF. Accordingly, the first TPF receives the sixth data or the second data from the cNode.

[0309] Specifically, the cNode forwards the sixth data or the second data to the first TPF. That is, the cNode may or may not carry the second information, the identification information of the first task, and the identification information of the first TCF when forwarding the data to the first TPF. It should be understood that the second data can also be referred to as the sixth data without the identification information of the first TCF, the identification information of the first task, and the second information.

[0310] The cNode sends the sixth data or the second data to the TPF based on the second information. Further, the cNode sends the sixth data or the second data to the first TPF among the N TPFs based on the identification information of the first task and the identification information of the first FCT.

[0311] Additionally, one implementation method is: if the terminal device does not carry the second information, the identification information of the first task, and the identification information of the first TCF in the sixth data, then the cNode sends the data to the UPF.

[0312] The above description includes three methods of the method 900 for transmitting data corresponding to case (a) of the above scenario three. The method 900 for transmitting data corresponding to case (b) of the above scenario three also includes three methods, among which method one corresponding to case (b) is similar to method one corresponding to case (a) and will not be repeated here. The difference between method two corresponding to case (b) and method two corresponding to case (a) is that the identification information of the first task and the identification information of the first TCF carried by the fifth data sent in step S924 are replaced with the identification information of the first task session. When N TPFs perform the same task with the UE, the fifth data sent in step S924 carries the identification information of the first task and the identification information of the first TCF, which cannot enable the sNode to identify which TPF the fifth data is to be sent to. At this time, each TPF in the N TPFs transmits the data of a task session in the task to the terminal. The cNode needs to identify to which TPF the third data should be sent by the identification of the task session. The difference between the third method corresponding to case (b) and the third method corresponding to case (a) is that the identification information of the first task and the identification information of the first TCF carried by the sixth data sent in step S930 are replaced with the identification information of the first task session. When N TPFs perform the same task with the UE, the sixth data sent in step S930 carrying the identification information of the first task and the identification information of the first TCF cannot enable the sNode to identify to which TPF the sixth data is sent. Similarly, the cNode needs to identify to which TPF the fourth data should be sent through the identification of the task session.

[0313] Through the above method 900, the base station can determine how to forward uplink data from the terminal device in the presence of multiple task processing functions and multiple task control functions, thereby improving communication efficiency. The above method 900 can also enable the UE to determine how to send task session data to the base station in the presence of multiple task processing functions and multiple task control functions, thereby improving communication efficiency. It should be understood that the size of the sequence number of each of the above processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0314] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the interaction between various network elements. It can be understood that each network element, such as a transmitting end device or a receiving end device, includes a hardware structure and / or software module corresponding to the execution of each function in order to implement the above functions. Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0315] In the embodiment of the present application, the functional modules of the transmitting device or the receiving device can be divided according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module according to each function.

[0316] The method provided in the embodiments of the present application is described in detail above with reference to Figures 5 to 9. Below, the apparatus provided in the embodiments of the present application is described in detail with reference to Figures 10 and 11. It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, reference can be made to the method embodiment above, and for the sake of brevity, no further description will be given here.

[0317] FIG10 shows a schematic diagram of a communication device 1000 provided in an embodiment of the present application.

[0318] The device 1000 includes a transceiver unit 1010 , which can be used to implement corresponding communication functions. The transceiver unit 1010 can also be called a communication interface, a communication unit, or an interface unit.

[0319] The apparatus 1000 may further include a processing unit 1020 , which may be configured to perform data processing.

[0320] Optionally, the device 1000 also includes a storage unit, which can be used to store instructions and / or data. The processing unit 1020 can read the instructions and / or data in the storage unit so that the device implements the actions of different devices in the aforementioned method embodiments.

[0321] As a design, the apparatus 1000 is used to execute the actions performed by the access network device in each of the above method embodiments.

[0322] Specifically, the transceiver unit 1010 is used to receive first data from the terminal device on the first data bearer; the processing unit 1020 is used to determine whether to send the first data to the TPF based on the first data bearer or the first data; the transceiver unit 1010 is also used to send the first data to the TPF.

[0323] As a design, the device 1000 is used to execute the actions performed by the terminal device in each of the above method embodiments.

[0324] Specifically, the processing unit 1020 is configured to determine a first data bearer; and the transceiver unit 1010 is configured to send first data to the access network device on the first data bearer.

[0325] The device 1000 can implement the steps or processes executed by the access network device or terminal device in the method embodiment according to the embodiment of the present application. The device 1000 may include a unit for executing the method executed by the terminal device or access network device (cNode, sNode) or TPF (first TPF) in the embodiments shown in Figures 5, 6, 7, 8, and 9.

[0326] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0327] It should also be understood that the device 1000 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 1000 may be specifically the access network device in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the access network device in the above-mentioned method embodiments. To avoid repetition, they will not be described here.

[0328] The apparatus 1000 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the access network device in the above-mentioned method, or the apparatus 1000 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the terminal device in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0329] In addition, the transceiver unit 1010 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.

[0330] It should be noted that the device in Figure 1000 can be a network element or device in the aforementioned embodiment, or a chip or chip system, such as a system on chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit can be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0331] Figure 11 shows a schematic diagram of a communication device 1100 provided in an embodiment of the present application. The device 1100 includes a processor 1110, which is coupled to a memory 1120. The memory 1120 is used to store computer programs or instructions and / or data. The processor 1110 is used to execute the computer programs or instructions stored in the memory 1120, or read the data stored in the memory 1120 to execute the methods in the above method embodiments. As shown in Figure 11, the device 1100 also includes a transceiver 1130, which is used to receive and / or send signals. For example, the processor 1110 is used to control the transceiver 1130 to receive and / or send signals.

[0332] Optionally, there are one or more processors 1110 .

[0333] Optionally, there are one or more memories 1120 .

[0334] It should be understood that the processor 1110 and memory 1120 can be combined into a processing device, and the processor 1110 is used to execute the program code stored in the memory 1120 to implement the above functions. In specific implementations, the memory 1120 can also be integrated into the processor 1110, or independent of the processor 1110. It should be understood that the processor 1110 can also correspond to the various processing units in the aforementioned communication device, and the transceiver 1130 can correspond to the various receiving units and transmitting units in the aforementioned communication device.

[0335] It should also be understood that the transceiver 1130 may include a receiver (or receiver) and a transmitter (or transmitter). The transceiver may further include an antenna, and the number of antennas may be one or more. The transceiver may also be a communication interface or interface circuit.

[0336] Specifically, the communication device 1100 may correspond to the access terminal device in methods 500 to 900 according to the embodiments of the present application. The communication device 1100 may include the units of the methods 500 to 900 performed by the access network device. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments and will not be repeated here for the sake of brevity.

[0337] When the communication device 1100 is a chip, the chip includes an interface unit and a processing unit, wherein the interface unit may be an input / output circuit or a communication interface; and the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip.

[0338] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0339] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0340] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0341] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0342] The present application also provides a computer-readable medium having a computer program stored thereon, which implements the functions of any of the above method embodiments when executed by a computer.

[0343] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0344] The present application also provides a system, which includes the aforementioned access network device, TPF device and TCF device.

[0345] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0346] In the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete way.

[0347] It should be understood that references to "embodiments" throughout this specification mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0348] It should be understood that in the various embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. The names of all nodes and messages in this application are merely names set by this application for the convenience of description. The names in the actual network may be different. It should not be understood that this application limits the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in this application is regarded as the method or equivalent replacement of this application, and is within the scope of protection of this application.

[0349] It should also be understood that in this application, "when", "if" and "if" all mean that the UE or base station will take corresponding measures under certain objective circumstances. It does not limit the time, and does not require the UE or base station to take judgment actions when implementing it, nor does it mean that there are other limitations.

[0350] Additionally, the terms "system" and "network" are often used interchangeably. The term "and / or" is simply used to describe an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone.

[0351] As used herein, the term "at least one of" or "at least one of" refers to all or any combination of the listed items. For example, "at least one of A, B, and C" can mean: A alone, B alone, C alone, A and B together, B and C together, and A, B, and C together. As used herein, "at least one" means one or more. "A plurality" means two or more.

[0352] It should be understood that in the various embodiments of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information. The terms "include," "comprising," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0353] It should be understood that in various embodiments of the present application, the first, second, and various numerical numbers are merely distinctions for ease of description and are not intended to limit the scope of the embodiments of the present application.

[0354] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0355] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0356] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0357] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0358] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0359] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0360] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for transmitting data, characterized in that: The method comprises: The access network device receives first data from the terminal device on the first data bearer; The access network device sends the first data to a task processing function TPF based on the first data bearer or the first data, and the TPF is used to interact with the terminal device for task data.

2. The method according to claim 1, characterized in that The method further comprises: The access network device sends first information to the terminal device, where the first information indicates that the first data bearer is used to transmit data between the terminal device and the TPF; The access network device sends the first data to the TPF based on the first data bearer.

3. The method according to claim 2, characterized in that When multiple TPFs interact with the terminal device to exchange data of multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the first data includes identification information of the first task, and the first task belongs to one of the multiple tasks; The access network device sending the first data to the TPF based on the first data bearer includes: The access network device sends the first data to a first TPF based on the first data bearer and identification information of the first task, and the first TPF is the TPF corresponding to the first task.

4. The method according to claim 3, characterized in that When there are multiple task control functions TCFs controlling multiple TPFs to interact with the terminal device to exchange data of multiple tasks, the first data further includes identification information of a first TCF, and the first TCF is used to control the first TPF to interact with the terminal device to interact with the data of the first task; The access network device sending the first data to the TPF based on the first data bearer includes: The access network device sends the first data to the first TPF based on the first data bearer, identification information of the first task, and identification information of the first TCF.

5. The method according to claim 2, characterized in that: When multiple TPFs interact with the terminal device to exchange data of the first task, the first data includes identification information of a first task session, the first task session is used for the terminal device to interact with a first TPF to exchange data of the first task, and the first TPF belongs to one of the multiple TPFs; The access network device sending the first data to the TPF based on the first data bearer includes: The access network device sends the first data to the first TPF based on the first data bearer and identification information of the first task session.

6. The method according to claim 1, characterized in that When the first data bearer is a data radio bearer DRB, the first data includes second information, and the second information is used to indicate that the first data is data of a task session, and the method further includes: The access network device sends the first data to the TPF based on the second information; or, The access network device sends the first data without carrying the second information to the TPF based on the second information.

7. The method according to claim 6, characterized in that When multiple TPFs interact with the terminal device to exchange data of multiple tasks, and the multiple TPFs correspond to the multiple tasks one by one, the first data also includes identification information of the first task, and the first task belongs to one of the multiple tasks; The access network device sending the first data to the TPF based on the second information includes: The access network device sends the first data to a first TPF based on the second information and identification information of the first task, and the first TPF is the TPF corresponding to the first task.

8. The method according to claim 7, characterized in that When there are multiple task control functions TCFs controlling multiple TPFs to interact with the terminal device to exchange data of multiple tasks, the first data further includes identification information of a first TCF, and the first TCF is used to control the first TPF to interact with the terminal device to interact with the data of the first task; The access network device sending the first data to the TPF based on the second information includes: The access network device sends the first data to the first TPF based on the second information, the identification information of the first task, and the identification information of the first TCF.

9. The method according to claim 6, characterized in that When multiple TPFs interact with the terminal device to exchange data of the first task, the first data further includes identification information of a first task session, the first task session is used for the terminal device to interact with a first TPF to exchange data of the first task, and the first TPF belongs to one of the multiple TPFs; The access network device sending the first data to the TPF based on the second information includes: The access network device sends the first data to the first TPF based on the second information and identification information of the first task session.

10. The method according to any one of claims 3 to 9, characterized in that The method further comprises: The access network device receives third information, where the third information includes at least one of the following information: identification information of at least one task, identification information of at least one task session, and identification information of at least one TCF, wherein each item of information included in the third information corresponds to at least one TPF; The access network device sends the first data to the first TPF based on the third information.

11. A method for transmitting data, characterized in that: The method comprises: The terminal device determines a first data bearer; The terminal device sends the first data to the access network device on the first data bearer. The first data bearer or the first data is used by the access network device to determine that the first data is sent to the task processing function TPF. The TPF is used to interact with the terminal device about task data.

12. The method according to claim 11, characterized in that The method further comprises: The terminal device receives first information from the access network device, where the first information indicates that a first data bearer is used to transmit data between the terminal device and the TPF.

13. The method according to claim 12, characterized in that When multiple TPFs interact with the terminal device to exchange data of multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the first data includes identification information of the first task, and the first task belongs to one of the multiple tasks.

14. The method according to claim 13, characterized in that When there are multiple task control functions TCF controlling multiple TPFs to interact with the terminal device to obtain data of multiple tasks, the first data also includes identification information of the first TCF, and the first TCF is used to control the first TPF to interact with the terminal device to obtain data of the first task.

15. The method according to claim 12, characterized in that When multiple TPFs interact with the terminal device to exchange data of the first task, the first data includes identification information of a first task session, and the first task session is used for the terminal device to interact with the first TPF to exchange data of the first task, and the first TPF belongs to one of the multiple TPFs.

16. The method according to claim 11, characterized in that When the first data bearer is a data radio bearer DRB, the first data includes second information, where the second information is used to indicate that the first data is data of a task session.

17. The method according to claim 16, characterized in that When multiple TPFs interact with the terminal device to exchange data of multiple tasks, and the multiple TPFs correspond one-to-one to the multiple tasks, the first data also includes identification information of the first task, and the first task belongs to one of the multiple tasks.

18. The method according to claim 17, characterized in that When there are multiple task control functions TCF controlling multiple TPFs to interact with the terminal device to obtain data of multiple tasks, the first data also includes identification information of the first TCF, and the first TCF is used to control the first TPF to interact with the terminal device to obtain data of the first task.

19. The method according to claim 16, characterized in that When there are multiple TPFs interacting with the terminal device for the data of the first task, the first data also includes identification information of the first task session, and the first task session is used for the terminal device to interact with the first TPF for the data of the first task, and the first TPF belongs to one of the multiple TPFs.

20. A communication device, characterized in that: The communication device is used to execute the method according to any one of claims 1 to 19.

21. A communication device, characterized in that: include: A processor, configured to execute a computer program stored in the memory, so that the apparatus performs the method according to any one of claims 1 to 19.

22. The device according to claim 21, characterized in that The apparatus also includes the memory.

23. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 19.

24. A computer program product, characterized in that The computer program product comprises instructions for performing the method of any one of claims 1 to 19.

25. A chip system, characterized in that: include: A processor, used to call and run a computer program from a memory so that a communication device equipped with the chip system executes the method described in any one of claims 1 to 19.

Images