Task-based communication method and communication device

Abstract

The embodiment of the invention provides a task-based communication method and device, and the method comprises the steps: a task anchor TA is independently deployed in a core network and an access network, a terminal device can send a task request to a first node, the first node selects a proper TA based on the task request, and indicates the type of the TA to the terminal device, and the terminal device sends the TA to the terminal device. And the terminal equipment sends a task request to the TA according to the type of the TA, or the first node directly forwards the task request to the TA, and the TA completes deployment of the TE and executes a specific task. Therefore, the first node selects the TA, the complexity of the terminal equipment can be reduced, the terminal equipment senses the TA type, and the efficiency of the terminal equipment for subsequently sending the task message can be improved.

Description

A task-based communication method and communication device Technical Field

[0001] The embodiments of the present application relate to the field of communications, and more specifically, to a task-based communication method and communication device. Background Art

[0002] Existing radio access network (RAN) architectures, such as the fifth generation (5G) RAN architecture, are flat architectures based on session management and control. The system establishes channels for user data transmission and allocates corresponding connections and air interface resources.

[0003] In addition to traditional connectivity services, future wireless communication networks will also offer a variety of new service capabilities, including computing, AI (artificial intelligence), perception, and data. To support these new services, the network must coordinate the scheduling of various heterogeneous resources, such as computing, algorithms, connectivity, and data, to achieve specific service objectives. This process can be considered task-granular control and must support mechanisms for ensuring quality of service (QoS).

[0004] Traditional wireless communication systems are session-centric, manage and control based on session granularity, and implement session QoS guarantees, but cannot support task-based management and control.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a task-based communication method and communication device, which implement task deployment and management based on a task-centric communication architecture to meet task requests of terminal devices.

[0007] In a first aspect, a task-based communication method is provided. The method may be executed by a first node, or may be executed by a chip or circuit configured in the first node, which is not limited in this application.

[0008] The method includes: receiving a first request from a terminal device, the first request is used to request control of the execution of a first task, and the first request includes information of the first task; determining a second node based on the first request, the second node is used to control the execution of the first task; sending the type of the second node to the terminal device, the type of the second node including an access network element or a core network element; or, sending the first request to the second node.

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

[0010] Heterogeneous resources can be understood as computing, intelligence, data, perception and other resources.

[0011] Service targets can be new services such as computing, data, trust, intelligence, and perception.

[0012] Among them, the first node can be a control plane function, and the first node is used to provide a management and control function of the first task.

[0013] For example, the first node can be responsible for the lifecycle management of the first task, complete task deployment, startup, deletion, modification, monitoring, etc. based on the needs of the first task, and regulate network resources to ensure task QoS.

[0014] In the present application, the management and control functions of the first task can be deployed in both the core network and the access network, for example, the cluster control node (cNode) in the access network and the task control function (TCF) in the core network.

[0015] It should be understood that in this application, the collaborative control function of tasks in the core network is explained using TCF as an example. The task control function in the core network can also evolve into other names, and the embodiments of this application do not limit this.

[0016] It can be understood that the first node in this application can be a cNode in the access network or a TCF in the core network.

[0017] The second node in this application is the node determined by the first node to provide collaborative management functions for the first task, that is, the task anchor (TA), which is used to deploy TE to interact with business logic data and perform specific tasks. The second node can be the same node as the first node or a different node from the first node.

[0018] In this technical solution, TAs are independently deployed in the core network and access network. Terminal devices can send task requests to the first node. The first node selects an appropriate TA based on the task request and indicates the TA type to the terminal device. The terminal device then sends the task request to the TA based on the TA type. Alternatively, the first node directly forwards the task request to the TA, which then completes the TE deployment and executes the specific task. Having the first node select the TA reduces terminal device complexity, and the terminal device's awareness of the TA type improves the efficiency of subsequent task message transmission.

[0019] In combination with the first aspect, in an implementation of the first aspect, before sending the first request to the second node, the first request received from the terminal device is sent according to the type of the second node, and the type of the second node is determined by the terminal device based on the first mapping relationship, and the first mapping relationship is used to indicate the correspondence between the first task event and the type of the second node.

[0020] The first task event includes the first task itself or the type of the first task.

[0021] In this technical solution, the terminal device can determine the TA type corresponding to the first task based on a preconfigured mapping relationship, and send a first request to a first node of the same type based on the task type, thereby enabling the first node to select a TA of the same type as the second node and send the first request to the second node. Based on the preconfigured mapping relationship between task types and TA types, the terminal device can autonomously determine the TA type corresponding to the task to be initiated, thereby directly sending a task request to that type of TA, improving task access efficiency.

[0022] In combination with the first aspect, in an implementation manner of the first aspect, the first node sends a first mapping relationship to the terminal device.

[0023] The first mapping relationship may be in the form of a mapping relationship table or other forms, which is not limited in the embodiment of the present application.

[0024] In this technical solution, the terminal device can obtain the first mapping relationship through the first node. For example, during the terminal device registration process, the network device can configure the first mapping relationship to the terminal device through initial registration, mobile registration update, periodic registration update, etc., or can configure the first mapping relationship to the terminal device during the terminal device configuration update process, or can configure the first mapping relationship during the paging process. This embodiment of the present application is not limited to this.

[0025] In combination with the first aspect, in an implementation of the first aspect, the first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0026] In this technical solution, when a terminal device sends a first request to a first node for the first time, the request message can include the first configuration information. When the second node receives the first request, it can directly deploy the first task based on the first configuration information, thus saving signaling and improving task efficiency.

[0027] In combination with the first aspect, in an implementation of the first aspect, first configuration information is received from a terminal device; the first configuration information is sent to a second node, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0028] In this technical solution, after receiving the task confirmation message from the second node, the terminal device sends the first configuration information to the second node through the first node.

[0029] In combination with the first aspect, in an implementation manner of the first aspect, the first node is a core network element or an access network element.

[0030] In this technical solution, the first node may be a TA in the access network, for example, a cNode; or may be a TA in the access network, for example, a TCF.

[0031] In combination with the first aspect, in one implementation of the first aspect, when the first node is a core network element, the first request is received through non-access layer signaling; or, when the first node is an access network element, the first request is received through wireless resource control signaling.

[0032] In this technical solution, the terminal device sends a first request to the TA of the core network element through non-access layer signaling, and the terminal device sends a first request to the TA of the access network element through wireless resource control signaling.

[0033] In combination with the first aspect, in an implementation of the first aspect, when the first node is a core network element, the identifier of the second node is sent to a third node, and the third node is an access network element accessed by the terminal device.

[0034] In this technical solution, when the first node is a core network element, the first node sends the type of the second node to the terminal device, and can also send the identifier of the second node to the third node. When the third node receives the first request sent by the first node, it determines to send the first request to the second node based on the identifier of the second node.

[0035] It can be understood that if the third node and the second node are the same node, there is no need to send the identifier of the second node to the third node.

[0036] In combination with the first aspect, in one implementation of the first aspect, the first node may request secondary authentication from the task authentication and authorization function based on the information of the first task, wherein the request message includes the information of the first task, and a response message is received from the authentication and authorization function to confirm that the first task completes the authentication and authorization.

[0037] In this technical solution, the first node determines, based on the information of the first task, that the first task is not an existing task type, and therefore needs to perform secondary authentication.

[0038] In combination with the first aspect, in an implementation method of the first aspect, when the first node is a core network element, the first node can send first registration information to the mobile management function, and the first registration information is used to register the binding relationship between the first task and the second node to the mobile management function. The first registration information includes the identifier of the terminal device, the identifier of the first task, and the identifier of the second node.

[0039] In this technical solution, after the first node determines the correspondence between the first task and the second node, it registers the context of the first task to the mobile management function. When the terminal device sends a location movement and moves to a new TA area, the mobile management function can trigger the TA to switch.

[0040] In combination with the first aspect, in an implementation manner of the first aspect, the information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of the first task, a description of the first task, and requirements of the first task.

[0041] In a second aspect, a task-based communication method is provided. The method can be executed by a terminal device, or can be executed by a chip or circuit configured in the terminal device, and this application does not limit this.

[0042] The method includes: obtaining a first node, the first node is used to provide a management and control function of a first task, the first task includes a process of collaboratively achieving a service goal based on heterogeneous resources; sending a first request to the first node, the first request is used to request control of the execution of the first task, and the first request includes information about the first task.

[0043] Heterogeneous resources can be understood as computing, intelligence, data, perception and other resources.

[0044] Service objectives can be new service capabilities such as computing, data, trust, intelligence, and perception.

[0045] Among them, the first node can be a control plane function, and the first node is used to provide a management and control function of the first task.

[0046] For example, the first node can be responsible for the lifecycle management of the first task, complete task deployment, startup, deletion, modification, monitoring, etc. based on the needs of the first task, and regulate network resources to ensure task QoS.

[0047] In the present application, the management and control functions of the first task can be deployed in both the core network and the access network, for example, the cluster control node (cNode) in the access network and the task control function (TCF) in the core network.

[0048] It should be understood that in this application, the collaborative control function of tasks in the core network is explained using TCF as an example. The task control function in the core network can also evolve into other names, and the embodiments of this application do not limit this.

[0049] It can be understood that the first node in this application can be a cNode in the access network or a TCF in the core network.

[0050] In this technical solution, the terminal device can obtain the first node and then send a first request to the first node, so that the first node can select a suitable TA to perform task deployment.

[0051] In combination with the second aspect, in an implementation method of the second aspect, the type of the second node is determined based on a first mapping relationship, the first mapping relationship is used to indicate the correspondence between the first task event and the type of the second node, and the type of the second node includes a core network network element or an access network network element; the first node is determined based on the type of the second node, and the type of the first node is the same as the type of the second node.

[0052] In this application, the first task event includes the first task itself or the type of the first task.

[0053] In this technical solution, the terminal device can determine the TA type corresponding to the first task based on a preconfigured mapping relationship, and send a first request to a first node of the same type based on the task type, thereby enabling the first node to select a TA of the same type as the second node and send the first request to the second node. Based on the preconfigured mapping relationship between task types and TA types, the terminal device can autonomously determine the TA type corresponding to the task to be initiated, thereby directly sending a task request to that type of TA, improving task access efficiency.

[0054] In combination with the second aspect, in an implementation manner of the second aspect, a first mapping relationship is received from an access network element or a core network element.

[0055] In this technical solution, the terminal device can obtain the first mapping relationship through the access network device or the core network device. The specific solution is the same as the first aspect and will not be repeated here.

[0056] In combination with the second aspect, in an implementation method of the second aspect, the type of the second node is received from the first node, the type of the second node includes a core network network element or an access network element, and the second node is a node determined by the first node to control the execution of the first task; a first request is sent to the second node according to the type of the second node, and the first request is used to request to control the execution of the first task.

[0057] In this technical solution, a terminal device receives the type of a second node from a first node and initiates a task request to the second node based on the type of the second node. The terminal device can sense the type of the TA, thereby improving the efficiency of the terminal device in sending subsequent task messages.

[0058] In combination with the second aspect, in an implementation of the second aspect, the first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0059] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0060] In combination with the second aspect, in an implementation of the second aspect, first configuration information is sent to the second node according to the type of the second node, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0061] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0062] In combination with the second aspect, in an implementation manner of the second aspect, the first node is a core network element or an access network element.

[0063] In combination with the second aspect, in an implementation of the second aspect, when the first node is a core network element, the first request is sent through non-access layer signaling, or when the first node is an access network element, the first request is sent through wireless resource control signaling.

[0064] In combination with the second aspect, in an implementation manner of the second aspect, the information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of task, a task description, and a task requirement.

[0065] On the third aspect, a task-based communication method is provided. The method can be executed by a third node, or can be executed by a chip or circuit configured in the third node, which is not limited in this application.

[0066] The method includes: receiving a first request from a terminal device, the first request is used to request control of the execution of a first task, the first request includes information about the first task requested by the terminal device, the first task includes a process of collaboratively achieving service goals based on heterogeneous resources; determining a second node based on an identifier of the second node sent by the first node, the first node being used to provide a management and control function for the first task; sending the first request to the second node; or, based on the first request, controlling the execution of the first task.

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

[0068] Heterogeneous resources can be understood as computing, intelligence, data, perception and other resources.

[0069] Service objectives can be new service capabilities such as computing, data, trust, intelligence, and perception.

[0070] Among them, the first node can be a control plane function, and the first node is used to provide a management and control function of the first task.

[0071] For example, the first node can be responsible for the lifecycle management of the first task, complete task deployment, startup, deletion, modification, monitoring, etc. based on the needs of the first task, and regulate network resources to ensure task QoS.

[0072] In the present application, the management and control functions of the first task can be deployed in both the core network and the access network, for example, the cluster control node (cNode) in the access network and the task control function (TCF) in the core network.

[0073] It should be understood that in this application, the control function of the task in the core network is explained using TCF as an example. The task control function in the core network can also evolve into other names, and the embodiments of this application do not limit this.

[0074] It can be understood that the first node in this application can be a cNode in the access network or a TCF in the core network.

[0075] The second node in this application is the node determined by the first node to provide collaborative management functions for the first task, that is, the TA, which is used to deploy the TE to perform data interaction in business logic and execute specific tasks. The second node can be the same node as the first node or a different node from the first node.

[0076] The third node in this application is a TA of the access network, for example, it may be a cNode.

[0077] In this technical solution, the third node receives the first request from the terminal device, and sends the first request to the second node according to the identifier of the second node, or controls the execution of the first task based on the first request.

[0078] In combination with the third aspect, in an implementation of the third aspect, the first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0079] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0080] In combination with the third aspect, in an implementation of the third aspect, first configuration information is received from a terminal device; the first configuration information is sent to a second node, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0081] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0082] In combination with the third aspect, in an implementation manner of the third aspect, the first node is a core network element or an access network element.

[0083] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0084] In combination with the third aspect, in an implementation manner of the third aspect, the information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of task, a task description, and a task requirement.

[0085] In a fourth aspect, a task-based communication method is provided. The method can be executed by a terminal device, or can be executed by a chip or circuit configured in the terminal device. This application does not limit this.

[0086] The method includes: determining the type of the second node based on a first mapping relationship, the first mapping relationship is used to indicate the correspondence between the first task event and the type of the second node, the second node is a node used to control the execution of the first task, and the type of the second node includes a core network element or an access network element; sending a first request to the second node based on the type of the second node, the first request is used to request control of the execution of the first task, and the first request message includes information about the first task.

[0087] The task event of the first task includes the first task itself or the type of the first task.

[0088] In this technical solution, the terminal device determines the type of the second node corresponding to the first task based on the first mapping relationship, considers the node of this type to be the second node, and sends a first request to the second node to request control of the execution of the first task. In other words, based on the preconfigured mapping relationship between task types and TA types, the terminal device can autonomously determine the TA type corresponding to the task to be initiated, and can then directly send the task request to this type of TA, improving task access efficiency.

[0089] In combination with the fourth aspect, in an implementation of the fourth aspect, the first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0090] In combination with the fourth aspect, in an implementation of the fourth aspect, first configuration information is sent to the second node based on the type of the second node, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0091] In combination with the fourth aspect, in an implementation manner of the fourth aspect, the information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of task, a task description, and a task requirement.

[0092] In combination with the fourth aspect, in an implementation manner of the fourth aspect, a first mapping relationship is received from a first node.

[0093] In a fifth aspect, a task-based communication method is provided. The method can be executed by the second node, or can be executed by a chip or circuit configured in the second node. This application does not limit this.

[0094] The method includes: receiving a first request from a terminal device, the first request is used to request control of the execution of a first task, the first request includes information of the first task, and the first task includes a process of collaboratively achieving a service goal based on heterogeneous resources; and controlling the execution of the first task according to the first request.

[0095] The second node can be a node determined by the first node to provide collaborative management functions for the first task, that is, a task anchor (TA), used to deploy TE to perform data interaction based on business logic and execute specific tasks. The second node can be the same node as the first node or a different node from the first node.

[0096] It can be understood that the first node in this application can be a cNode in the access network or a TCF in the core network.

[0097] In this technical solution, the second node receives a first request from a terminal device and controls the execution of the first task according to the first request.

[0098] In combination with the fifth aspect, in one implementation of the fifth aspect, a second request is sent to the task authentication and authorization function based on the information of the first task, and the second request message includes the information of the first task; a first response message is received from the task authentication and authorization function, and the first response message is used to confirm that the first task completes authentication and authorization.

[0099] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0100] In combination with the fifth aspect, in an implementation of the fifth aspect, the first request also includes first configuration information, the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task, and the execution of the first task is controlled according to the first configuration information.

[0101] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0102] In combination with the fifth aspect, in an implementation of the fifth aspect, first configuration information is received from a terminal device, the first configuration information including computing power configuration and / or algorithm configuration for executing the first task; and the execution of the first task is controlled according to the first configuration information.

[0103] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0104] In combination with the fifth aspect, in an implementation of the fifth aspect, the information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of task, a task description, and a task requirement.

[0105] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0106] In combination with the fifth aspect, in an implementation of the fifth aspect, when the second node is a core network element, the method also includes: sending first registration information to the mobile management function, the first registration information is used to register the binding relationship between the first task and the second node to the mobile management function, the first registration information includes the identifier of the terminal device, the identifier of the first task and the identifier of the second node.

[0107] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0108] In a sixth aspect, a communication device is provided. The device may be a first node, or a chip or circuit configured in the first node, which is not limited in this application.

[0109] The apparatus includes: a transceiver unit for receiving a first request from a terminal device, the first request being used to request control of execution of a first task, and the first request including information of the first task; a processing unit for determining a second node based on the first request, the second node being used to control execution of the first task; the transceiver unit is further used to send the type of the second node to the terminal device, the type of the second node including an access network element or a core network element; or, to send the first request to the second node.

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

[0111] Heterogeneous resources can be understood as computing, intelligence, data, perception and other resources.

[0112] Service objectives can be new service capabilities such as computing, data, trust, intelligence, and perception.

[0113] Among them, the first node can be a control plane function, and the first node is used to provide a management and control function of the first task.

[0114] For example, the first node can be responsible for the lifecycle management of the first task, complete task deployment, startup, deletion, modification, monitoring, etc. based on the needs of the first task, and regulate network resources to ensure task QoS.

[0115] In the present application, the management and control functions of the first task can be deployed in both the core network and the access network, for example, the cluster control node cNode in the access network and the task control function TCF in the core network.

[0116] It should be understood that in this application, the task control function in the core network is explained using TCF as an example. The task control function in the core network can also evolve into other names, and the embodiments of this application do not limit this.

[0117] It can be understood that the first node in this application can be a cNode in the access network or a TCF in the core network.

[0118] The second node in this application is the node determined by the first node to provide control functions for the first task, that is, the task anchor TA, which is used to deploy TE to perform data interaction in business logic and execute specific tasks. The second node can be the same node as the first node or a different node from the first node.

[0119] In this technical solution, TAs are independently deployed in the core network and access network. Terminal devices can send task requests to the first node. The first node selects an appropriate TA based on the task request and indicates the TA type to the terminal device. The terminal device then sends the task request to the TA based on the TA type. Alternatively, the first node directly forwards the task request to the TA, which then completes the TE deployment and executes the specific task. Having the first node select the TA reduces terminal device complexity, and the terminal device's awareness of the TA type improves the efficiency of subsequent task message transmission.

[0120] In combination with the sixth aspect, in an implementation method of the sixth aspect, before the transceiver unit sends the first request to the second node, the first request received by the transceiver unit is sent according to the type of the second node, and the type of the second node is determined by the terminal device according to the first mapping relationship, and the first mapping relationship is used to indicate the correspondence between the first task event and the type of the second node.

[0121] In this technical solution, the terminal device can determine the TA type corresponding to the first task based on a preconfigured mapping relationship, and send a first request to a first node of the same type based on the task type, thereby enabling the first node to select a TA of the same type as the second node and send the first request to the second node. Based on the preconfigured mapping relationship between task types and TA types, the terminal device can autonomously determine the TA type corresponding to the task to be initiated, thereby directly sending a task request to that type of TA, improving task access efficiency.

[0122] In combination with the sixth aspect, in an implementation of the sixth aspect, the transceiver unit is further used to send the first mapping relationship to the terminal device.

[0123] The first mapping relationship may be in the form of a mapping relationship table or other forms, which is not limited in the embodiment of the present application.

[0124] In this technical solution, the terminal device can obtain the first mapping relationship through the first node. For example, during the terminal device registration process, the network device can configure the first mapping relationship to the terminal device through initial registration, mobile registration update, periodic registration update, etc., or can configure the first mapping relationship to the terminal device during the terminal device configuration update process, or can configure the first mapping relationship during the paging process. This embodiment of the present application is not limited to this.

[0125] In combination with the sixth aspect, in an implementation of the sixth aspect, the first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0126] In this technical solution, when a terminal device sends a first request to a first node for the first time, the request message can include the first configuration information. When the second node receives the first request, it can directly deploy the first task based on the first configuration information, thus saving signaling and improving task efficiency.

[0127] In combination with the sixth aspect, in an implementation of the sixth aspect, the transceiver unit is also used to receive first configuration information from the terminal device; the transceiver unit is also used to send the first configuration information to the second node, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0128] In this technical solution, after receiving the task confirmation message from the second node, the terminal device sends the first configuration information to the second node through the first node.

[0129] In combination with the sixth aspect, in an implementation of the sixth aspect, the first node is a core network element or an access network element.

[0130] In this technical solution, the first node may be a TA in the access network, for example, a cNode; or may be a TA in the access network, for example, a TCF.

[0131] In combination with the sixth aspect, in an implementation method of the sixth aspect, when the first node is a core network element, the transceiver unit is specifically used to receive the first request through non-access layer signaling; or, when the first node is an access network element, the transceiver unit is specifically used to receive the first request through wireless resource control signaling.

[0132] In this technical solution, the terminal device sends a first request to the TA of the core network element through non-access layer signaling, and the terminal device sends a first request to the TA of the access network element through wireless resource control signaling.

[0133] In combination with the sixth aspect, in an implementation of the sixth aspect, when the first node is a core network element, the transceiver unit is further used to send the identifier of the second node to the third node, and the third node is an access network element to which the terminal device accesses.

[0134] In this technical solution, when the first node is a core network element, the first node sends the type of the second node to the terminal device, and can also send the identifier of the second node to the third node. When the third node receives the first request sent by the first node, it determines to send the first request to the second node based on the identifier of the second node.

[0135] It can be understood that if the third node and the second node are the same node, there is no need to send the identifier of the second node to the third node.

[0136] In combination with the sixth aspect, in one implementation of the sixth aspect, the transceiver unit is also used to request secondary authentication from the task authentication and authorization function based on the information of the first task, and the request message includes the information of the first task, and receives a response message from the authentication and authorization function to confirm that the first task has completed authentication and authorization.

[0137] In this technical solution, the first node determines, based on the information of the first task, that the first task is not an existing task type, and therefore needs to perform secondary authentication.

[0138] In combination with the sixth aspect, in an implementation method of the sixth aspect, when the first node is a core network network element, the transceiver unit is also used to send first registration information to the mobile management function, and the first registration information is used to register the binding relationship between the first task and the second node to the mobile management function. The first registration information includes the identifier of the terminal device, the identifier of the first task, and the identifier of the second node.

[0139] In this technical solution, after the first node determines the correspondence between the first task and the second node, it registers the context of the first task to the mobile management function. When the terminal device sends a location movement and moves to a new TA area, the mobile management function can trigger the TA to switch.

[0140] In combination with the sixth aspect, in an implementation of the sixth aspect, the information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of the first task, a description of the first task, and requirements of the first task.

[0141] In a seventh aspect, a communication device is provided. The device may be a terminal device, or a chip or circuit configured in the terminal device, which is not limited in this application.

[0142] The device includes: a processing unit, used to obtain a first node, the first node is used to provide a management and control function of a first task, the first task includes a process of collaboratively achieving a service goal based on heterogeneous resources; a transceiver unit, used to send a first request to the first node, the first request is used to request control of the execution of the first task, and the first request includes information about the first task.

[0143] It can be understood that the first node in this application can be a cNode in the access network or a TCF in the core network.

[0144] In this technical solution, the terminal device can obtain the first node and then send a first request to the first node, so that the first node can select a suitable TA to perform task deployment.

[0145] In combination with the seventh aspect, in an implementation of the seventh aspect, the processing unit is specifically used to determine the type of the second node based on the first mapping relationship, the first mapping relationship is used to indicate the correspondence between the first task event and the type of the second node, and the type of the second node includes a core network network element or an access network network element; the processing unit is specifically used to determine the first node based on the type of the second node, and the type of the first node is the same as the type of the second node.

[0146] In combination with the seventh aspect, in an implementation of the seventh aspect, the transceiver unit is further used to receive a first mapping relationship from an access network element or a core network element.

[0147] In combination with the seventh aspect, in an implementation of the seventh aspect, the transceiver unit is further used to receive the type of the second node from the first node, the type of the second node includes a core network network element or an access network element, and the second node is a node determined by the first node to control the execution of the first task; the transceiver unit is also used to send a first request to the second node according to the type of the second node, and the first request is used to request to control the execution of the first task.

[0148] In this technical solution, a terminal device receives the type of a second node from a first node and initiates a task request to the second node based on the type of the second node. The terminal device can sense the type of the TA, thereby improving the efficiency of the terminal device in sending subsequent task messages.

[0149] In combination with the seventh aspect, in an implementation of the seventh aspect, the first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0150] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0151] In combination with the seventh aspect, in an implementation of the seventh aspect, the transceiver unit is further used to send first configuration information to the second node according to the type of the second node, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0152] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0153] In combination with the seventh aspect, in an implementation of the seventh aspect, the first node is a core network element or an access network element.

[0154] In combination with the seventh aspect, in an implementation method of the seventh aspect, when the first node is a core network network element, the transceiver unit is specifically used to send the first request through non-access layer signaling, or, when the first node is an access network network element, the transceiver unit is specifically used to send the first request through wireless resource control signaling.

[0155] In combination with the seventh aspect, in an implementation of the seventh aspect, the information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of task, a task description, and a task requirement.

[0156] In an eighth aspect, a communication device is provided. The device may be a third node, or may be a chip or circuit configured in the third node, which is not limited in this application.

[0157] The device includes: a transceiver unit for receiving a first request from a terminal device, the first request is used to request control of the execution of a first task, the first request includes information about the first task requested by the terminal device, and the first task includes a process of collaboratively achieving a service goal based on heterogeneous resources; a processing unit for determining a second node based on an identifier of the second node sent by the first node, the first node being used to provide a management and control function for the first task; the transceiver unit is also used to send the first request to the second node; or, the processing unit is used to control the execution of the first task based on the first request.

[0158] It can be understood that the first node in this application can be a cNode in the access network or a TCF in the core network.

[0159] The second node in this application is the node determined by the first node to provide collaborative management functions for the first task, that is, the task anchor TA, which is used to deploy TE to perform data interaction in business logic and execute specific tasks. The second node can be the same node as the first node or a different node from the first node.

[0160] The third node in this application is a TA of the access network, for example, it may be a cNode.

[0161] In this technical solution, the third node receives the first request from the terminal device, and sends the first request to the second node according to the identifier of the second node, or controls the execution of the first task based on the first request.

[0162] In combination with the eighth aspect, in an implementation of the eighth aspect, the first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0163] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0164] In combination with the eighth aspect, in an implementation of the eighth aspect, the transceiver unit is also used to receive first configuration information from the terminal device; the transceiver unit is also used to send the first configuration information to the second node, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0165] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0166] In combination with the eighth aspect, in an implementation of the eighth aspect, the first node is a core network element or an access network element.

[0167] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0168] In combination with the eighth aspect, in an implementation of the eighth aspect, the information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of task, a task description, and a task requirement.

[0169] In a ninth aspect, a communication device is provided. The device may be a terminal device, or a chip or circuit configured in the terminal device, which is not limited in this application.

[0170] The device includes: a processing unit, used to determine the type of the second node according to a first mapping relationship, the first mapping relationship is used to indicate the correspondence between the first task event and the type of the second node, the second node is a node used to control the execution of the first task, and the type of the second node includes a core network element or an access network element; a transceiver unit, used to send a first request to the second node according to the type of the second node, the first request information carries information of the first task, and the first request is used to request to control the execution of the first task.

[0171] In this technical solution, the terminal device determines the type of the second node corresponding to the first task based on the first mapping relationship, considers the node of this type to be the second node, and sends a first request to the second node to request control of the execution of the first task. In other words, based on the preconfigured mapping relationship between task types and TA types, the terminal device can autonomously determine the TA type corresponding to the task to be initiated, and can then directly send the task request to this type of TA, improving task access efficiency.

[0172] In combination with the ninth aspect, in an implementation of the ninth aspect, the first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0173] In combination with the ninth aspect, in an implementation of the ninth aspect, the transceiver unit is further used to send first configuration information to the second node according to the type of the second node, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

[0174] In combination with the ninth aspect, in an implementation of the ninth aspect, the information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of task, a task description, and a task requirement.

[0175] In combination with the ninth aspect, in an implementation of the ninth aspect, the transceiver unit is further used to receive the first mapping relationship from the first node.

[0176] In the tenth aspect, a communication subframe is provided. The device may be a second node, or may be a chip or circuit configured in the second node. This application does not limit this.

[0177] The apparatus includes: a transceiver unit for receiving a first request from a terminal device, the first request being used to request control of execution of a first task, the first request including information of the first task, the first task including a process of collaboratively achieving a service goal based on heterogeneous resources; and a processing unit for controlling execution of the first task according to the first request.

[0178] The second node can be a node determined by the first node to provide collaborative management functions for the first task, that is, a task anchor TA, used to deploy TE to perform data interaction based on business logic and execute specific tasks. The second node can be the same node as the first node or a different node from the first node.

[0179] It can be understood that the first node in this application can be a cNode in the access network or a TCF in the core network.

[0180] In this technical solution, the second node receives a first request from a terminal device and controls the execution of the first task according to the first request.

[0181] In combination with the tenth aspect, in an implementation method of the tenth aspect, the transceiver unit is also used to send a second request to the task authentication and authorization function based on the information of the first task, and the second request message includes the information of the first task; and receive a first response message from the task authentication and authorization function, and the first response message is used to confirm that the first task completes authentication and certification.

[0182] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0183] In combination with the tenth aspect, in an implementation of the tenth aspect, the first request also includes first configuration information, the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task, and the processing unit is also used to control the execution of the first task according to the first configuration information.

[0184] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0185] In combination with the tenth aspect, in an implementation of the tenth aspect, the transceiver unit is further used to receive first configuration information from the terminal device, the first configuration information including computing power configuration and / or algorithm configuration for executing the first task; the processing unit is further used to control the execution of the first task according to the first configuration information.

[0186] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0187] In combination with the tenth aspect, in an implementation manner of the tenth aspect, the information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of task, a task description, and a task requirement.

[0188] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0189] In combination with the tenth aspect, in an implementation method of the tenth aspect, when the second node is a core network network element, the transceiver unit is also used to send first registration information to the mobile management function, and the first registration information is used to register the binding relationship between the first task and the second node to the mobile management function. The first registration information includes the identifier of the terminal device, the identifier of the first task, and the identifier of the second node.

[0190] The beneficial effects of this technical solution are the same as those of the first aspect and will not be repeated here.

[0191] In an eleventh aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0192] 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.

[0193] In the twelfth aspect, the present application provides a communication device, which includes: a memory for storing programs; and 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.

[0194] In a thirteenth 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.

[0195] In a fourteenth 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.

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

[0197] 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

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

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

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

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

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

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

[0204] FIG7 shows a schematic diagram of a task-based communication method 700 provided in an embodiment of the present application.

[0205] FIG8 shows a schematic diagram of a task-based communication method 800 provided in an embodiment of the present application.

[0206] FIG9 shows a schematic diagram of a task-based communication method 900 provided in an embodiment of the present application.

[0207] FIG10 shows a schematic diagram of a task-based communication method 1000 provided in an embodiment of the present application.

[0208] FIG11 shows a schematic diagram of a task-based communication method 1100 provided in an embodiment of the present application.

[0209] FIG12 shows a schematic diagram of a task-based communication device 1200 provided in an embodiment of the present application.

[0210] FIG13 shows a schematic diagram of a task-based communication device 1300 provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0212] 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 the sixth generation mobile communication system. 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.

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

[0214] As an example, Figure 1 shows a schematic architecture diagram of a communication system. For example, the architecture may include a RAN, a terminal, a core network (CN), and an external network. The external network may be a data network (DN). 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, and may include a cluster control node and a service service node, as described below.

[0215] The terminal device in this application can be called 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.

[0216] 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.

[0217] 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.

[0218] 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.

[0219] 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).

[0220] 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.

[0221] Access network (AN) equipment in this application provides access to a communications network for authorized users in a specific area. Specifically, it can include wireless network equipment in a 3rd Generation Partnership Project (3GPP) network or access points in a non-3GPP network. For ease of description, the following description uses AN equipment.

[0222] AN equipment can adopt 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 (3rd generation, 3G), fourth generation (4G) or 5G systems) and non-3GPP (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 equipment can allow terminal devices and the 3GPP core network to interconnect and communicate using non-3GPP technologies.

[0223] AN equipment is responsible for radio resource management, quality of service (QoS) management, data compression and encryption, and other functions 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.

[0224] 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.

[0225] In addition to providing basic connectivity services, the RAN 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 achieve the provision of new service capabilities through the collaborative capabilities of multi-dimensional heterogeneous resources (computing, AI data, AI models, etc.), which will drive the evolution of future radio access network (RAN) architectures.

[0226] Among them, we define the process of achieving a specific goal through the collaboration of multi-dimensional resources at the network level as a "task". In other words, a task refers to the process of collaborative computing, algorithms, connections, data and other heterogeneous resources to achieve a specific goal.

[0227] It should be noted that the "task" defined in this application is different from the connection task. The connection task is generally a user establishing a connection session with the core network function through the radio access network, thereby establishing a channel for user data transmission and allocating corresponding connection and air interface resources to enable data transmission between the user and the external network. The task in this application refers to the process of achieving a goal by coordinating various heterogeneous resources in order to provide users with various new service capabilities.

[0228] It should be understood that the above connection tasks can also be referred to as connection services, connection businesses, etc.

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

[0230] 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 control function may include being responsible for the lifecycle management of the task, completing task deployment, startup, deletion, modification, monitoring, etc. based on the requirements of the task, 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, a first node with a management and control function can select a second node 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 TA, and TA deploys the task to one or more TEs for execution.

[0231] In order to achieve the above task structure, this application proposes a layered RAN architecture that can provide new services more efficiently.

[0232] The following describes the new service as a task-based service, which is not limited in the embodiments of the present application.

[0233] The network architecture provided by this application is described below.

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

[0235] This network architecture can be applied to the 6G system (the 6th generation system, 6GS).

[0236] The network architecture includes 6GC and layered RAN architecture.

[0237] The hierarchical RAN architecture introduces a centralized coordination node to provide task coordination within and between regions. For example, the RAN system includes cluster control nodes (cNodes) and service serving nodes (sNodes), which together constitute RAN nodes.

[0238] cNode: Cluster control node, providing regional centralized coordination of multiple business service nodes and cross-regional coordination between cluster control nodes. It provides task anchoring within the cluster and does not provide connection functionality or only provides connection control functionality over the air interface.

[0239] sNode: Business service node, provides task scheduling and execution functions; on the air interface, provides connection control and / or data functions.

[0240] 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.

[0241] The cNode can be responsible for the control plane functions (such as TA) and data processing functions of task-based services (for example, when the cNode has computing power, it can also deploy a task scheduler (TS) and TE to perform data processing tasks). The sNode is responsible for some control plane and user plane functions of task-based services, such as TS and TE.

[0242] The RAN architecture provided in this application supports resource collaboration 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.

[0243] In this network architecture, different nodes communicate through interfaces.

[0244] 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.

[0245] For another example, the cNode can be connected to the 6GC through the Tx interface, specifically, connected to the NAF through the T3 interface, connected to the CF-C through the T4 interface, and connected to the TCF / TPF through the T2 interface.

[0246] For another example, the sNode can be connected to the 6GC through the Ty interface, specifically, to the NAF through the T5 interface, to the CF-C through the T6 interface, and to the CF-U through the T7 interface.

[0247] Among them, 6GC network elements such as NAF, CF-C, TCF, and TPF can refer to the description in Figure 4 below.

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

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

[0250] The network architecture includes but is not limited to: network access function (NAF), task process function (TPF), connection function-control (CF-C), connection function-user (CF-U), mobility management (MM), unified data management (UDM), policy control function (PCF), and task authentication and authorization (TAA).

[0251] This core network architecture can be applied to 6G and become the 6G core network (6G core network, 6GC or 6GCN).

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

[0253] 1. TPF: Provides scheduling and execution functions for core network-side tasks.

[0254] 2. CF-C and CF-U: provide control plane and user plane functions of the connection respectively.

[0255] 3. MM: Mainly used to provide UE mobility management functions.

[0256] 4. TCF: Provides control functions for core network-side tasks.

[0257] 5. UDM: Provides subscription management, access authorization based on subscription data, registration management of network functions for terminal services, etc.

[0258] 6. PCF: Provides policy management capabilities, including supporting a unified policy framework to manage network behavior, providing policy rules, and accessing policy-related subscription information.

[0259] 7. TAA: Provides initial or secondary authentication and certification functions for tasks.

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

[0261] 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.

[0262] It should also be understood that the functions or network elements shown in Figure 1 can be understood as network elements used to implement different functions, for example, they can be combined into network slices as needed. These network elements can 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.

[0263] It should also be understood that the above naming is defined only 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. For example, in a 6G network, some or all of the above network elements may continue to use the terminology used in 5G, or may adopt other names.

[0264] 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 is described below.

[0265] Figure 4 shows a protocol stack architecture according to an embodiment of the present application. This protocol stack architecture is a protocol stack between a UE and a RAN node. Messages are sent between the UE and the RAN node via a wireless air interface (Uu interface). The protocol stack includes a control plane protocol and a user plane protocol.

[0266] The control plane protocol stack and the user plane protocol stack are shown in Figure 4.

[0267] The control plane performs signaling interaction, where the task resource control (TRC) of the control plane can be an enhancement or evolution of the RRC radio resource scheduling (RRC) layer in the existing wireless communication protocol stack, adding control functions for tasks such as AI, computing, and data processing on the basis of the existing radio resource control functions.

[0268] The user plane interacts with data. The task resource scheduler (TRS) of the user plane 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. In addition, a task resource data (TRD) layer is added above the service data adaptation protocol (SDAP) layer to provide task-related AI training / inference / model processing functions (compression / pruning / quantization / security, etc.).

[0269] 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.

[0270] Figure 5 shows a protocol stack architecture according to an embodiment of the present application. The protocol stack architecture is a communication protocol stack between RAN nodes. The protocol stack includes a control plane protocol stack and a user plane protocol stack.

[0271] The control plane is used for signaling exchanges, and the control plane interface is defined between RAN nodes. The transport network layer is built on top of IP transport. To ensure reliable signaling message transmission, SCTP is added on top of the IP layer. SCTP provides guaranteed application layer message delivery. The application layer signaling protocol is called Yn-AP (Yn application protocol).

[0272] The user plane is used to transmit data, and the user plane signaling interface is defined between RAN nodes. The transport network layer is built on top of IP transport and uses GTP-U on top of UDP / IP to carry user plane PDUs between RAN nodes.

[0273] Among them, the RAN nodes communicate with each other through an interface, for example, a Yn interface. In the embodiment of the present application, the interface name is not limited and may also be other names.

[0274] Exemplarily, cNode and sNode are connected to each other via a Y1 interface, cNode and cNode are connected to each other via a Y2 interface, and sNode and sNode are connected to each other via a Y3 interface.

[0275] 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.

[0276] The protocol layers shown in FIG5 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.

[0277] Figure 6 shows a protocol stack architecture according to an embodiment of the present application, which is a communication protocol stack between a RAN node and a core network.

[0278] The control plane is used for signaling exchanges, and the control plane interface is defined between RAN nodes and core network elements. The transport network layer is built on top of IP transport. To ensure reliable signaling message transmission, SCTP is added on top of the IP layer. SCTP provides guaranteed application layer message delivery. The application layer signaling protocol is called Tx / Ty-AP (Tx / Ty application protocol).

[0279] 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.

[0280] For example, the cNode is connected to the 6GC via the Tx interface. More specifically, the cNode is connected to the NAF via the T3 interface, the cNode is connected to the CF-C via the T4 interface, and the cNode is also connected to the TCF / TPF via the T2 interface. The sNode is also connected to the 6GC via the Ty interface. More specifically, it is connected to the NA via the T5 interface, to the CF-C via the T6 interface, and to the CF-U via the T7 interface.

[0281] 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.

[0282] The protocol layers shown in FIG6 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.

[0283] In this application, task management is performed between cNodes and sNodes via the Y1 interface; task negotiation is performed between cNodes via the Y2 interface; inter-domain task negotiation is performed between cNodes and TCF via the T2 interface; and task signaling or data exchange between sNodes and TEs is performed via the Y3 interface. Task control between network elements can include cNode control of sNodes, task negotiation between cNodes, and task negotiation between TCFs and cNodes.

[0284] Future wireless communication networks will natively support a variety of tasks, including computing, artificial intelligence (AI), perception, and data processing. Therefore, in addition to traditional connection session services, user equipment (UE) can also initiate task requests to the network. To achieve service decoupling, the core network (CN) and radio access network (RAN) independently deploy TA and TE. For example, on the core network side, the TCF (task control function) provides TA functionality, and the TPF (task process function) provides TE functionality. On the access network side, the cNode provides TA functionality, and the sNode provides TE functionality.

[0285] Therefore, the UE (user equipment) can act as a task trigger to initiate a task request to the network's task controller (TA). In scenarios where TAs are independently deployed on the core network and access network, deploying tasks to meet UE task requests is a pressing issue. In other words, determining the TA that controls task execution is a key issue in UE task deployment and management.

[0286] In this application, TAs are independently deployed in the core network and access network. The terminal device can initiate a task request to the core network TA or to the access network TA. The following describes this solution in detail.

[0287] FIG7 is a schematic block diagram of a task-based communication method 700 provided in an embodiment of the present application.

[0288] In this embodiment, the method is illustrated by taking the terminal device and the network device (first node and second node) 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 network device in Figure 7 can also be a chip, chip system, or processor that supports the method that can be implemented by the network device, or a logic module or software that can implement all or part of the network device functions; the terminal device in Figure 7 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 terminal device functions.

[0289] In this application, the first task includes the 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.

[0290] It can also be said that the first task is to provide task-based services through the collaborative capabilities of multi-dimensional heterogeneous resources, such as various new service capabilities such as computing, data, trust, intelligence, and perception.

[0291] The first node in the present application may be a network node with a TA function, that is, the first node is used to provide a management and control function of the first task.

[0292] The second node in this application is the TA selected by the first node to control the execution of the first task. The second node can be the first node or other nodes.

[0293] The method 700 may include the following steps:

[0294] S710, the terminal device sends a first request to the first node.

[0295] The terminal device determines the first node and sends a first request to the first node. Correspondingly, the first node receives the first request from the terminal device.

[0296] The first request is used to request the first node to control the execution of the first task, wherein the first task includes a process of achieving a service goal based on the collaboration of heterogeneous resources.

[0297] Requesting control over the execution of a first task can be understood as requesting that the first task be managed and controlled, and that one or more of the following be completed based on the first task's requirements: deployment, startup, deletion, modification, and monitoring. This involves regulating network resources to meet the requirements of the first task. Specifically, the TE is responsible for executing the first task; further, the TE interacts with the TA regarding business logic data.

[0298] The first request includes information of a first task.

[0299] Exemplarily, the information of the first task may include one or more of the following: an identifier of the terminal device, a type of the first task, an identifier of the first task, a task description of the first task, and requirements of the first task. The requirements of the first task may be, for example, resource requirements, QoS requirements, etc.

[0300] Optionally, the first request may further include first configuration information, where the first configuration information includes relevant configurations such as computing power configuration and / or algorithm configuration for executing the first task.

[0301] In this application, the first node can be a TA deployed in the access network. The first node can be an access network device accessed by the terminal device, or other access network devices, such as cNode; the first node can also be a TA deployed in the core network, such as a TCF network element serving the terminal device.

[0302] When the first node is a TA deployed in the core network, the terminal device sends the first request through task non-access stratum (T-NAS) signaling; correspondingly, the first node receives the first request through T-NAS signaling.

[0303] When the first node is a TA deployed in the access network, the terminal device sends the first request through TRC signaling; correspondingly, the first node receives the first request through TRC signaling.

[0304] In this application, T-NAS signaling refers to task-based NAS signaling. It should be understood that the communication protocol stack of the task-centric network architecture includes the control plane protocol stack and user plane protocol stack of the task, wherein the control plane includes the enhanced NAS (T-NAS) layer, TRC layer, TRS layer, etc., and the user plane includes the TRD layer and the enhanced SDAP (T-SDAP) layer.

[0305] Among them, T-NAS and T-SDAP are merely names defined in the embodiment of the present application for ease of understanding, and are not limited in the embodiment of the present application.

[0306] It should be understood that the task control signaling interaction between the TA of the core network and the UE is through the T-NAS interface, for example, the TCF and the UE interact with each other through the T-NAS interface; the task control signaling interaction between the TA of the access network and the UE is through the TRC interface or through sNode transit, for example, the cNode and the UE interact with each other through the TRC interface or through sNode transit.

[0307] In an optional implementation, the UE determines the first node according to the connected sNode, and the UE sends the first request to the first node through the sNode.

[0308] In another optional embodiment, the terminal device determines the type of the second node based on the first mapping relationship, and the terminal device determines the first node based on the type of the second node, wherein the type of the first node and the type of the second node are the same. The second node is the TA that controls the first task. That is, before sending the first request, the terminal device obtains the type of the TA in advance, and based on the type, can determine a first node of the same type and send the first request to the first node.

[0309] The first mapping relationship is used to indicate the corresponding relationship between the first task event and the type of the second node.

[0310] For example, the first mapping relationship may be a correspondence relationship between the first task itself and the type of the second node, or the first mapping relationship may be a correspondence relationship between the type of the first task and the type of the second node.

[0311] Exemplarily, the first mapping relationship may be predefined by a protocol.

[0312] Exemplarily, the UE may obtain the first mapping relationship or an update of the first mapping relationship through a core network device or an access network device.

[0313] The first node may send the first mapping relationship or update information of the first mapping relationship to the UE in the following exemplary manners.

[0314] Mode 1: UE registration process, including initial registration, mobility registration update, and periodic registration update. The registration process may configure the first mapping relationship for the UE.

[0315] Method 2: UE configuration update procedure. When the above-mentioned first mapping relationship table changes, the TCF can trigger the UE configuration update procedure and send a configuration update message to the UE, carrying the updated first mapping relationship. After the UE locally updates, it returns a configuration update confirmation to the TCF.

[0316] Mode three: a paging procedure, including paging initiated by an access network or a paging initiated by a core network, and a corresponding paging message includes the first mapping relationship.

[0317] The above method is only an example description and does not limit the embodiments of the present application.

[0318] Optionally, after receiving the first request, the first node may further send a task authentication and certification request to the task authentication and certification function element of the core network based on the information about the first task. The authentication and certification request includes the information about the first task. Accordingly, the task authentication and certification function element obtains the contract information of the field device based on the information about the first task, and after completing the authentication and certification, sends a confirmation message to the first node.

[0319] For example, if the first node determines, based on the information about the first task, that the first task is not a task type known to the first node, it may request task authentication and authorization from the task authentication and authorization function network element of the core network. The task authentication and authorization function network element of the core network may be a TAA (task authentication and authorization), which is a logical function of the core network and may be placed in a core network function such as a UDM or PCF. This is not limited in this embodiment of the present application.

[0320] S720: The first node determines a second node according to the first request, wherein the second node is used to control the execution of the first task.

[0321] In a possible implementation, the first node determines the second node according to information about the first task included in the first request.

[0322] Exemplarily, the first node selects the second node according to one or more of the identification of the terminal device, the type of the first task, the identification of the first task, the task description of the first task, the requirements of the first task, and the like.

[0323] In one possible implementation, the first request sent by the terminal device is sent according to the type of the second node, and the type of the second node is determined by the terminal device according to the first mapping relationship. In this case, the first node can select a node of the same type as the second node.

[0324] Exemplarily, the first node selects a node of the same type as the first node as the second node based on one or more of the identification of the terminal device, the type of the first task, the identification of the first task, the task description of the first task, the requirements of the first task, etc.

[0325] Illustratively, the second node may be a TCF or a cNode.

[0326] It should be understood that the second node may also be the first node itself.

[0327] S730: The first node sends the type of the second node to the terminal device, or the first node sends a first request to the second node.

[0328] The type of the second node includes a core network element or an access network element, that is, a TA of the core network or a TA of the access network.

[0329] Case 1: The first node sends the type of the second node to the terminal device.

[0330] In this case, in a possible implementation, after determining the second node, the first node sends the type of the second node to the terminal device.

[0331] Correspondingly, the terminal device forwards the first request to the second node through the access network element of the terminal device based on the type of the second node.

[0332] It should be understood that the terminal device determines to send the first request through T-NAS signaling based on the type of the second node, or sends the first request through TRC signaling.

[0333] Exemplarily, if the type of the second node is a core network element, the terminal device sends the first request through T-NAS signaling; if the type of the second node is an access network element, the terminal device sends the first request through TRC signaling.

[0334] For example, if the first node is a TCF and the access network element to which the terminal device is connected is a cNode, the TCF may also send the identifier of the second node to the cNode. If the second node is an access network element, the terminal device sends a first request to the cNode through TRC signaling. The cNode determines the second node based on the identifier of the second node and forwards the first request to the second node. The second node deploys the corresponding TE to perform the first task.

[0335] For example, if the first node is a TCF and the access network element to which the terminal device is connected is a cNode, the TCF may also send the identifier of the second node to the Node. If the second node is a core network element, the terminal device sends a first request to the cNode through T-NAS signaling. The cNode determines the second node based on the identifier of the second node and forwards the first request to the second node. The second node deploys the corresponding TE to perform the first task.

[0336] For example, if the first node is TCF and the second node determined by TCF is cNode itself, the TCF may not send the identifier of the second node to the cNode. The terminal device sends a first request to the cNode based on the type of the second node. The cNode determines itself as the second node based on the first request, that is, the cNode deploys the corresponding TE to perform the first task.

[0337] For example, if the first node is a cNode, the cNode is an access network element to which the terminal device is connected, and the second node determined by the cNode is another access network element, the terminal device sends a first request to the cNode based on TRC signaling, the cNode determines the second node, and forwards the first request to the second node, and the second node deploys the corresponding TE to perform the first task.

[0338] For example, if the first node is a cNode, which is an access network element to which the terminal device is connected, the second node determined by the cNode is the cNode itself, and the terminal device sends a first request to the cNode based on TRC signaling, the cNode deploys the corresponding TE to perform the first task.

[0339] For example, if the first node is a cNode, the cNode is an access network element to which the terminal device is connected, and the second node determined by the cNode is a core network element, the terminal device sends a first request to the cNode based on T-NAS signaling, the cNode determines the second node, and forwards the first request to the second node, and the second node deploys the corresponding TE to perform the first task.

[0340] Optionally, the terminal device determines to send the first configuration information to the second node through T-NAS signaling based on the type of the second node, or sends the first configuration information through TRC signaling.

[0341] Exemplarily, if the type of the second node is a core network element, the terminal device sends the first configuration information to the second node through T-NAS signaling; if the type of the second node is an access network element, the terminal device sends the first configuration information through TRC signaling.

[0342] Case 2: The first node forwards the first request to the second node.

[0343] In this case, in a possible implementation, after the first node determines the second node, the first node does not send the type of the second node to the terminal device, but forwards the first request to the second node.

[0344] Correspondingly, after receiving the first request, the second node deploys the corresponding TE to perform the first task according to the information of the first task in the first request.

[0345] Exemplarily, if the first node is a TCF and determines that the second node is a cNode, the first request is sent to the cNode, and the cNode deploys a corresponding TE to perform the first task.

[0346] Exemplarily, if the first node is a TCF and determines that the second node is another core network element, a first request is sent to the other core network element, and the other core network element deploys a corresponding TE to perform the first task.

[0347] Exemplarily, if the first node is a cNode and determines that the second node is a TCF, a first request is sent to the TCF, and the TCF deploys a corresponding TE to perform the first task.

[0348] Exemplarily, if the first node is a cNode and determines that the second node is another access network element, a first request is sent to the other access network element, and the other access network element deploys a corresponding TE to perform the first task.

[0349] Exemplarily, if the first node determines that the second node is the first node itself, the first node does not need to forward the first request to the second node, and the first node deploys the corresponding TE to perform the first task.

[0350] Optionally, the first node may also forward the first configuration information to the second node.

[0351] Optionally, the first node may also send registration information to the mobility management function, where the registration information is used to register the binding relationship between the first task and the second node to the mobility management function. The registration information includes the identifier of the terminal device, the identifier of the first task and the identifier of the second node.

[0352] In an optional method, after the first node determines the second node of the first task, it registers the context of the first task to the mobile management function. When the location of the terminal device moves, for example, to a new TA node area, the mobile management function can trigger the TA to switch.

[0353] In the above scheme, the scheme of the terminal device sending a task request to the core network TA or the access network TA is explained through the interaction between the terminal device and the first node. Next, the specific schemes for different interaction subjects are explained in detail.

[0354] First, an exemplary solution for a terminal device to send a task request to a core network TA is introduced.

[0355] FIG8 is a schematic diagram of a task-based communication method 800 provided in an embodiment of the present application.

[0356] In this embodiment, the core network TA uses TCF#1 as an example. Assume that the access network device currently connected to the terminal device is sNode#1, and the cluster node associated with sNode#1 is cNode#1. cNode#1 may be located within the service area of ​​TCF#1. The UE initiates a request for Task#A to the network. Task#A is the first task.

[0357] Method 800 may include the following steps.

[0358] S810: UE sends request message #1 to TCF #1, where request message #1 includes relevant information of task #A.

[0359] The UE sends the request message #1 to sNode#1, and sNode#1 sends the request message #1 to TCF#1 through cNode#1.

[0360] Correspondingly, TCF#1 receives the request information #1 through cNode#1.

[0361] The request information #1 is used to request TCF #1 to control the execution of task #A.

[0362] The UE sends the request information #1 to the TCF #1 through T-NAS signaling.

[0363] Correspondingly, TCF#1 receives the request information #1 based on T-NAS signaling.

[0364] The relevant information of Task #A, for example, includes one or more of the following: UE identification, Task #A type, Task #A identification, Task #A task description, Task #A requirements, etc.

[0365] Optionally, the request information #1 may also include configuration information #1, and the configuration information #1 includes relevant configurations such as computing power configuration and / or algorithm configuration for executing task #A.

[0366] S820, TCF#1 sends authentication request information #1 to TAA.

[0367] Correspondingly, the TAA receives the request information #1 from the TCF #1.

[0368] Authentication request information #1 is used to request task authentication and certification from TAA.

[0369] The authentication request information #1 includes information of task #A, for example, one or more items of UE identification, task #A type, task #A description, and task #A requirements.

[0370] It should be understood that TCF#1 determines that task #A is not an existing task type based on request information #1, and then TCF#1 sends the authentication request information #1 to TAA.

[0371] S830, TCF#1 receives authentication confirmation message #1 from TAA.

[0372] TAA obtains the UE's contract information based on the authentication request information #1 to complete the authentication and authorization, and sends the authentication confirmation message #1 to TCF #1 to complete the authentication and authorization of task #A.

[0373] It should be understood that the above steps S820 and S830 are optional steps.

[0374] S840, TCF#1 determines the TA according to the request information #1.

[0375] TCF#1 determines TA based on the information of task #A in request information #1.

[0376] Exemplarily, TCF#1 determines TA based on one or more of the following: UE identification, task #A type, task #A task description, task #A requirements, etc.

[0377] It should be understood that the TA can be the TA of the core network, the TA of the access network, or the TCF#1 itself. In the solution shown in FIG8 , the selected TA is described using cNode#2 as an example, but this is not limited to the embodiment of the present application.

[0378] After TCF#1 determines TA, there are two ways to send a task request to TA. Way one includes steps S850a1-S850a3, and way two includes step S850b1.

[0379] First, method 1 is described.

[0380] S850a1, TCF#1 sends the TA identifier to cNode#1.

[0381] S850a2, TCF#1 sends the TA type to the UE.

[0382] S850a3, the UE sends request information #1 to the TA through sNode#1 and cNode#1 according to the type of the TA.

[0383] Exemplarily, when the TA is cNode#2, the UE determines to forward the request information #1 to sNode#1 through TRC signaling according to the type of the TA, sNode#1 forwards the request information #1 to cNode#1, and cNode#1 sends the request information #1 to cNode#2 according to the identifier of the TA.

[0384] Exemplarily, when the TA is another TCF (TCF#2), the UE determines to forward the request information #1 to sNode#1 through T-NAS signaling according to the type of TA, sNode#1 forwards the request information #1 to cNode#1, and cNode#1 sends the request information #1 to TCF#2 according to the TA identifier.

[0385] It should be understood that if the type of the TA is a core network element, the UE sends the request information #1 through T-NAS signaling.

[0386] It should be understood that if the TA determined by TCF#1 is cNode#1, the TA identifier may not be sent to cNode#1.

[0387] It can be understood that the request information #1 sent in this step and the request information #1 sent in S810 carry the same content, but the sending signaling is different.

[0388] Next, method 2 is described.

[0389] S850b1, TCF#1 sends request information #1 to cNode#2.

[0390] Correspondingly, cNode#2 receives request information #1 from TCF#1.

[0391] Exemplarily, when the TA is TCF#2, TCF#1 sends request information #1 to TCF#2.

[0392] After TCF#1 determines TA, it directly sends request information#1 to TA.

[0393] It can be understood that the request information #1 sent in this step and the request information #1 sent in S810 carry the same content, but the sending signaling is different.

[0394] S860, cNode#2 sends a confirmation message #1 to the UE.

[0395] cNode#2 sends confirmation message #1 to cNode#1, which forwards it to the UE via sNode#1.

[0396] Exemplarily, when the TA is TCF#2, TCF#2 sends a confirmation message #1 to the UE through cNode#1 and sNode#1.

[0397] Confirmation message #1 is used to confirm the task request to the UE.

[0398] S870, TCF#1 sends registration information #1 to MM.

[0399] Correspondingly, MM receives the registration information #1 from TCF #1.

[0400] The registration information #1 is used to register the context information of task #A with the MM. The registration information #1 includes the identifier of the UE, the identifier of task #A, and the identifier of the TA.

[0401] An optional understanding is that after TCF#1 determines the TA of task #A, it registers the context of task #A with the mobility management function. When the UE moves, for example, to a new TA node area, the mobility management function can trigger the TA to switch.

[0402] It can be understood that the UE can send the configuration information #1 to the TA through the request information #1, and can also send the configuration information #1 through an independent message.

[0403] S880a, the UE sends configuration information #1 to cNode#2 through sNode#1 and cNode#1.

[0404] It can be understood that after obtaining the TA type, the UE can directly send the configuration information #1 to the cNode #2 through TRC signaling.

[0405] Exemplarily, when the TA is TCF#2, the UE sends configuration information #1 to TCF#2 through T-NAS signaling.

[0406] S880b, the UE sends the configuration information #1 to TCF#1, and TCF#1 forwards the configuration information #1 to cNode#2.

[0407] It can be understood that the UE can directly send the configuration information #1 to TCF#1 through T-NAS signaling, and forward it to cNode#2 through TCF#1.

[0408] Exemplarily, when the TA is TCF#2, the UE sends configuration information #1 to TCF#1 through T-NAS signaling, and then forwards it to TCF#2 through TCF#1.

[0409] S890, cNode#2 deployment task.

[0410] cNode#2 deploys the task to one or more TEs for execution based on configuration information#1 and the task request.

[0411] Exemplarily, the TE may be an sNode to which cNode#2 is connected.

[0412] Exemplarily, if the TA is TCF#2, the task is deployed by TCF#2. In this case, the TE may be an access network element served by TCF#2.

[0413] S891, cNode#2 sends the task result to the UE.

[0414] After each execution body completes the task, it reports the execution result to cNode#2 for aggregation, and then cNode#2 sends the final task result to the UE through cNode#1 and sNode#1.

[0415] Exemplarily, if the TA is TCF#2, TCF#2 sends the task result to the UE.

[0416] In this technical solution, the UE sends a task request to the core network's TCF. The TCF selects a task agent (TA) based on the task request. The TCF indicates the TA type to the UE, and the UE sends the task request to the TA based on the TA type. Alternatively, the TCF directly forwards the task request to the TA, which then completes the task deployment. Having the core network's TCF select the TA reduces UE complexity, and the UE's awareness of the TA type improves the efficiency of subsequent task message transmissions.

[0417] Next, an exemplary solution for a terminal device to send a task request to an access network TA is introduced.

[0418] FIG9 is a schematic diagram of a task-based communication method 900 provided in an embodiment of the present application.

[0419] In this embodiment, the access network TA uses cNode#1 as an example. Assume that the access network device currently connected to the terminal device is sNode#1, and the cluster node associated with sNode#1 is cNode#1. cNode#1 may be located within the service area of ​​TCF#1. The UE initiates a request for Task#A to the network. Task#A is the first task.

[0420] Method 900 may include the following steps.

[0421] S910: UE sends request message #2 to cNode #1, where request message #2 includes relevant information of task #A.

[0422] The UE sends the request information #2 to sNode#1, and sNode#1 sends the request information #2 to cNode#1.

[0423] Correspondingly, cNode#1 receives the request information #2 through sNode#1.

[0424] The request information #2 is used to request the cNode #1 to control the execution of the task #A.

[0425] The UE sends the request information #2 to the cNode #1 through TRC signaling.

[0426] The corresponding cNode#1 receives the request information#2 based on TRC signaling.

[0427] The request information #2 includes relevant information of task #A, for example, one or more of the following: UE identification, task #A type, task #A description, task #A requirements, etc.

[0428] Optionally, the request information #2 may also include configuration information #1, where the configuration information #1 includes relevant configurations such as computing power configuration and / or algorithm configuration for executing task #A.

[0429] S920, cNode#1 sends authentication request information #2 to TAA.

[0430] Correspondingly, the TAA receives the authentication request message #2 from TcNode#1.

[0431] Authentication request information #2 is used to request task authentication and certification from TAA.

[0432] The authentication request information #2 includes information of task #A, for example, one or more items of UE identification, task #A type, task #A description, and task #A requirements.

[0433] It should be understood that cNode#1 determines, based on the request information #2, that the task #A is not an existing task type, and then cNode#1 sends the authentication request information #2 to the TAA.

[0434] S930, cNode#1 receives authentication confirmation message #2 from TAA.

[0435] TAA obtains the UE's contract information based on authentication request message #2 to complete authentication and authorization, and sends authentication confirmation message #2 to cNode #1 to complete the authentication and authorization of task #A.

[0436] It should be understood that the above steps S920 and S930 are optional steps.

[0437] S940, cNode#1 determines the TA according to the request information #2.

[0438] cNode#1 determines the TA based on the information of Task#A in Request#2.

[0439] Exemplarily, cNode#1 determines the TA according to one or more of the following: the UE identifier, the type of task #A, the task description of task #A, the requirements of task #A, etc.

[0440] It should be understood that the TA can be a core network TA, an access network TA, or the cNode#1 itself. In the solution shown in FIG9 , the selected TA is described using cNode#2 as an example, but this is not limited to the embodiment of the present application.

[0441] After cNode#1 determines the TA, there are two ways to send a task request to the TA. Way one includes steps S950a1-S950a2, and way two includes step S950b1.

[0442] First, method 1 is described.

[0443] S950a1, cNode#1 sends the TA type to the UE.

[0444] S950a2, the UE sends request information #2 to the TA through sNode#1 and cNode#1 according to the type of the TA.

[0445] Exemplarily, when the TA is cNode#2, the UE determines to forward the request information #2 to sNode#1 through TRC signaling according to the type of the TA, sNode#1 forwards the request information #2 to cNode#1, and cNode#1 sends the request information #2 to cNode#2 according to the identifier of the TA.

[0446] Exemplarily, when the TA is another TCF (TCF#2), the UE determines to forward the request information #2 to sNode#1 through T-NAS signaling based on the type of TA, sNode#1 forwards the request information #2 to cNode#1, and cNode#1 sends the request information #2 to TCF#2 based on the TA identifier.

[0447] It should be understood that if the type of the TA is a core network element, the UE sends the request information #2 through T-NAS signaling.

[0448] It can be understood that the request information #2 sent in this step and the request information #2 sent in S910 carry the same content, but the sending signaling is different.

[0449] Next, method 2 is described.

[0450] S950b1, cNode#1 sends request information #2 to cNode#2.

[0451] Correspondingly, cNode#2 receives request information #2 from cNode#1.

[0452] Exemplarily, when the TA is TCF#2, cNode#1 sends request information #2 to TCF#2.

[0453] After cNode#1 determines TA, it directly sends request information #2 to TA.

[0454] It can be understood that the request information #2 sent in this step and the request information #2 sent in S910 carry the same content, but the sending signaling is different.

[0455] S960, cNode#2 sends confirmation message #2 to UE.

[0456] cNode#2 sends confirmation message #2 to cNode#1, which then forwards it to the UE via sNode#1.

[0457] Exemplarily, when the TA is TCF#2, TCF#2 sends confirmation message #2 to cNode#1, and cNode#1 forwards it to the UE via sNode#1.

[0458] Confirmation message #2 is used to confirm the task request to the UE.

[0459] It can be understood that the UE can send the configuration information #1 to the TA through the request information #2, and can also send the configuration information #1 through an independent message.

[0460] S970 , the UE sends configuration information #1 to cNode#2 through sNode#1 and cNode#1.

[0461] It can be understood that after obtaining the TA type, the UE can directly send the configuration information #1 to the cNode #2 through TRC signaling.

[0462] Exemplarily, when the TA is TCF#2, the UE sends configuration information #1 to TCF#2 through T-NAS signaling.

[0463] S980, cNode#2 deployment task.

[0464] cNode#2 deploys the task to one or more TEs for execution based on configuration information#1 and the task request.

[0465] Exemplarily, the TE may be an sNode to which cNode#2 is connected.

[0466] Exemplarily, if the TA is TCF#2, the task is deployed by TCF#2. In this case, the TE may be an access network element served by TCF#2.

[0467] S990, cNode#2 sends the task result to the UE.

[0468] After each execution body completes the task, it reports the execution result to cNode#2 for aggregation, and then cNode#2 sends the final task result to the UE through cNode#1 and sNode#1.

[0469] Exemplarily, if the TA is TCF#2, TCF#2 sends the task result to the UE.

[0470] In this technical solution, the UE sends a task request to the access network cNode. The cNode selects a task agent (TA) based on the task request. The cNode indicates the TA type to the UE, and the UE sends the task request to the TA based on the TA type. Alternatively, the cNode directly forwards the task request to the TA, which then completes the task deployment. Having the access network cNode select the TA reduces UE complexity, and the UE's awareness of the TA type improves the efficiency of subsequent task message transmission.

[0471] Next, an exemplary solution is introduced in which the UE sends a task request to the core network TA, and all task signaling of the UE is forwarded to the TA by the core network TCF.

[0472] FIG10 is a schematic diagram of a task-based communication method 1000 provided in an embodiment of the present application.

[0473] In this embodiment, the core network TA uses TCF#1 as an example. Assume that the access network device currently connected to the terminal device is sNode#1, and the cluster node associated with sNode#1 is cNode#1. cNode#1 may be located within the service area of ​​TCF#1. The UE initiates a request for Task#A to the network. Task#A is the first task.

[0474] Method 1000 may include the following steps.

[0475] S1010: UE sends request message #3 to TCF #1, wherein request message #1 includes relevant information of task #A.

[0476] S1020, TCF#1 sends authentication request information #3 to TAA.

[0477] S1030, TCF#1 receives authentication confirmation message #3 from TAA.

[0478] S1040, TCF#1 determines TA according to request information #3.

[0479] The specific solutions of the above steps S1010-S1040 can be referred to S810-S840 in method 800, and will not be repeated here.

[0480] In the solution shown in FIG10 , the TA determined by TCF#1 takes cNode#2 as an example.

[0481] In this embodiment, all task signaling is forwarded by TCF#1.

[0482] S1050, TCF#1 sends request information #3 to cNode#2.

[0483] Correspondingly, cNode#2 receives request information #3 from TCF#1.

[0484] Exemplarily, when the TA is TCF#2, TCF#1 sends request information #3 to TCF#2.

[0485] After TCF#1 determines TA, it directly sends request information #3 to TA.

[0486] It can be understood that the request information #3 sent in this step and the request information #3 sent in S1010 carry the same content, but the sending signaling is different.

[0487] S1060, cNode#2 sends a confirmation message #3 to the UE via TCF#1.

[0488] cNode#2 forwards confirmation message #1 to cNode#1 via TCF#1, and cNode#1 forwards it to the UE via sNode#1.

[0489] Exemplarily, when the TA is TCF#2, TCF#2 sends a confirmation message #3 to the UE through cNode#1 and sNode#1.

[0490] Confirmation message #3 is used to confirm the task request to the UE.

[0491] S1070, TCF#1 sends registration information #1 to MM.

[0492] The specific solution of step S1070 can be referred to S870 in method 800 and will not be repeated here.

[0493] S1080 , the UE sends the configuration information #1 to TCF#1, and TCF#1 forwards the configuration information #1 to cNode#2.

[0494] It can be understood that the UE can directly send the configuration information #1 to TCF#1 through T-NAS signaling, and forward it to cNode#2 through TCF#1.

[0495] For example, when the TA is TCF#2, the UE can send configuration information #1 to TCF#1 through T-NAS signaling, and then forward it to TCF#2 through TCF#1. The UE can also send configuration information #1 directly to TCF#2 through T-NAS signaling.

[0496] S1090, cNode#2 deployment task.

[0497] cNode#2 deploys the task to one or more TEs for execution based on configuration information#1 and the task request.

[0498] Exemplarily, the TE may be an sNode to which cNode#2 is connected.

[0499] Exemplarily, if the TA is TCF#2, the task is deployed by TCF#2. In this case, the TE may be an access network element served by TCF#2.

[0500] S1091, cNode#2 sends a location query request message to MM.

[0501] After the task is completed, cNode#2 collects the task execution results and queries the MM for the current location of the UE through a location query request message.

[0502] S1092, cNode#2 receives UE location information from MM.

[0503] MM sends the UE's location information to cNode#2, including the identification information of sNode#1 and cNode#1 to which the UE is currently connected.

[0504] Correspondingly, cNode#2 determines the path to the UE task result based on the identifiers of sNode#1 and cNode#1.

[0505] S1093, cNode#2 sends the task result to the UE.

[0506] After each execution body completes the task, it reports the execution result to cNode#2 for aggregation, and then cNode#2 sends the final task result to the UE through cNode#1 and sNode#1.

[0507] Exemplarily, if the TA is TCF#2, TCF#2 sends the task result to the UE.

[0508] In this technical solution, the UE sends a task request to the core network's TCF. The TCF selects a TA based on the task request and forwards the task request and task configuration information to the TA, which then completes the task deployment. All task signaling sent by the UE is forwarded by the TCF, eliminating the need for the UE to identify the TA type, reducing UE-side complexity and air interface signaling.

[0509] Next, an exemplary solution is introduced in which a terminal device sends a task request to an access network TA, and all task signaling of the UE is forwarded to the TA by the cNode.

[0510] FIG11 is a schematic diagram of a task-based communication method 1000 provided in an embodiment of the present application.

[0511] In this embodiment, the access network TA uses cNode#1 as an example. Assume that the access network device currently connected to the terminal device is sNode#1, and the cluster node associated with sNode#1 is cNode#1. cNode#1 may be located within the service area of ​​TCF#1. The UE initiates a request for Task#A to the network. Task#A is the first task.

[0512] Method 1100 may include the following steps.

[0513] S1110, UE sends request message #4 to cNode #1. Request message #4 includes information about task #A.

[0514] S1120, cNode#1 sends authentication request information #4 to TAA.

[0515] S1130, cNode#1 receives authentication confirmation message #4 from TAA.

[0516] It should be understood that the above steps S1120 and S1130 are optional steps.

[0517] S1140, cNode#1 determines the TA according to the request information #4.

[0518] The specific solutions of the above steps S1110-S1140 can be referred to S910-S940 in method 90, and will not be repeated here.

[0519] In the solution shown in FIG11 , the TA determined by cNode#1 takes TCF#1 as an example.

[0520] In this embodiment, all task signaling is forwarded by cNode#1.

[0521] S1150, cNode#1 sends request information #4 to TCF#1.

[0522] Correspondingly, TCF#1 receives request information #4 from cNode#1.

[0523] Exemplarily, when the TA is cNode#2, cNode#1 sends request information #4 to cNode#2.

[0524] After cNode#1 determines TA, it directly sends request information #4 to TA.

[0525] It can be understood that the request information #4 sent in this step and the request information #4 sent in S1110 carry the same content, but the sending signaling is different.

[0526] S1160 , TCF#1 sends a confirmation message #4 to the UE via cNode#1 and sNode#1.

[0527] TCF#1 sends confirmation message #4 to cNode#1, which forwards it to the UE via sNode#1.

[0528] Exemplarily, when the TA is cNode#2, cNode#2 sends a confirmation message #4 to the UE through sNode#1 and cNode#1.

[0529] Confirmation message #4 is used to confirm the task request to the UE.

[0530] It can be understood that the UE can send the configuration information #1 to the TA through the request information #4, and can also send the configuration information #1 through an independent message.

[0531] S1170, the UE sends configuration information #1 to TCF#1.

[0532] It can be understood that after obtaining the TA type, the UE can directly send configuration information #1 to cNode#1 through TRC signaling, and cNode#1 sends configuration information #1 to TCF#1; the UE can also send configuration information #1 to TCF#1 through T-NAS signaling.

[0533] Exemplarily, when the TA is cNode#2, the UE sends configuration information #1 to sNode#1 through TRC signaling, sNode#1 sends configuration information #1 to cNode#1, and cNode#1 then sends configuration information #1 to cNode#2.

[0534] S1180, cNode#2 deployment task.

[0535] cNode#2 deploys the task to one or more TEs for execution based on configuration information#1 and the task request.

[0536] Exemplarily, the TE may be a cNode connected to TCF#1.

[0537] For example, if the TA is cNode#2, the task is deployed by cNode#2. In this case, the TE may be the sNode to which cNode#2 is connected.

[0538] S1190, TCF#1 sends the task result to the UE.

[0539] After each execution body completes the task, it reports the execution result to TCF#1 for aggregation, and then TCF#1 sends the final task result to UE through cNode#1 and sNode#1.

[0540] Exemplarily, if the TA is cNode#2, cNode#2 sends the task result to the UE.

[0541] In this technical solution, the UE sends a task request to the access network cNode. The cNode selects a task agent (TA) based on the task request. The cNode directly forwards task messages, such as the task request or task configuration, to the TA, which then completes the task deployment. Having the access network cNode select the TA reduces UE complexity. The UE's awareness of the TA type improves the efficiency of subsequent task message transmissions.

[0542] Next, we introduce the scheme of pre-configured task types and TA types.

[0543] In a possible implementation, a mapping relationship between task events and TA types may be pre-configured for the UE.

[0544] Table 1 below is an example of the mapping relationship between task events and TA types.

[0545] Table 1

[0546] In a possible implementation, the network configures the mapping relationship to the UE. The mapping relationship includes a correspondence between a task event and a TA type. The task event may be the task itself or the type of the task.

[0547] Exemplarily, the network may configure the mapping relationship to the UE in the following manner.

[0548] Method 1: UE registration process, including initial registration, mobile registration update, and periodic registration update.

[0549] Method 2: UE configuration update process. When the above mapping table changes, the TCF can trigger the UE configuration update process and send a configuration update message to the UE, carrying the latest mapping table. After the UE locally updates, it returns a configuration update confirmation to the TCF.

[0550] Method 3: Paging process, including paging initiated by the access network or paging initiated by the core network.

[0551] In another possible implementation, the mapping relationship is predefined in the protocol, that is, the corresponding relationship between the task event and the TA type is predefined in the protocol.

[0552] The above methods are merely exemplary and do not limit the embodiments of the present application.

[0553] Specifically, the UE determines the TA type corresponding to task #A according to the mapping relationship, and then the UE sends a task request to the node of the TA type.

[0554] Exemplarily, the UE determines, based on the mapping relationship, that the TA type corresponding to Task #A is a core network element. The UE then sends a task request to TCF #1. TCF #1 may deploy Task #A based on the task request, or may redetermine the TA based on the task request. For example, method 1000 may be executed, where, in S1040, TCF #1 may select a TA of the core network. Details are not repeated here.

[0555] Exemplarily, the UE determines, based on the mapping relationship, that the TA type corresponding to Task #A is an access network element. The UE then sends a task request to cNode #1. cNode #1 may deploy Task #A based on the task request, or may redetermine the TA based on the task request. For example, method 900 may be executed, where, in S940, cNode #1 may select the TA of the access network. Details are not repeated here.

[0556] In this technical solution, the UE can determine the TA type corresponding to the task to be initiated based on the pre-configured mapping relationship between the task type and the TA type, and can thus directly send a task request to the TA of this type, thereby improving task access efficiency.

[0557] It should be understood that the size of the serial numbers 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 embodiments of the present application.

[0558] 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.

[0559] 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.

[0560] The method provided in the embodiments of the present application is described in detail above with reference to Figures 7 to 11. Below, the apparatus provided in the embodiments of the present application is described in detail with reference to Figures 12 and 13. 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.

[0561] FIG12 shows a schematic diagram of a communication device 1200 provided in an embodiment of the present application.

[0562] The device 1200 includes a transceiver unit 1210, which can be used to implement corresponding communication functions. The transceiver unit 1210 can also be called a communication interface or a communication unit.

[0563] The apparatus 1200 may further include a processing unit 1220 , which may be configured to perform data processing.

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

[0565] As a design, the device 1200 is used to execute the actions performed by the first node in each of the above method embodiments.

[0566] Specifically, the transceiver unit 1210 is used to receive a first request from a terminal device, where the first request includes information about the first task; the processing unit 1220 is used to determine a second node based on the first request, where the second node is used to control the execution of the first task; the transceiver unit 1210 is also used to send the type of the second node to the terminal device, where the type of the second node includes an access network element or a core network element; or, to send the first request to the second node, where the first request is used to request the second node to control the execution of the first task.

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

[0568] Specifically, the processing unit 1220 is used to obtain a first node, which is used to provide a management and control function for a first task, and the first task includes a process of collaboratively achieving service goals based on heterogeneous resources; the transceiver unit 1210 is used to send a first request to the first node, and the first request includes information about the first task.

[0569] As a design, the device 1200 is used to execute the actions performed by the third node in each of the above method embodiments.

[0570] Specifically, the transceiver unit 1210 is used to receive a first request from a terminal device, where the first request includes information about a first task requested by the terminal device, and the first task includes a process of collaboratively achieving a service goal based on heterogeneous resources; the transceiver unit 1210 is also used to send the first request to a second node, where the second node is determined based on an identifier of the second node received from the first node, and the first node is used to provide a management and control function for the first task; or, the processing unit 1220 is used to control the execution of the first task based on the first request.

[0571] The device 1200 can implement the steps or processes executed by the terminal device or the first node in the method embodiment according to the embodiment of the present application. The device 1200 may include a unit for executing the method executed by the terminal device or network device (TCF, cNode) in the embodiments shown in Figures 7, 8, 9, 10, and 11.

[0572] 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.

[0573] It should also be understood that the device 1200 here is embodied in the form of a functional unit. The term "unit" here can 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 1200 can be specifically a network device in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the network device in the above-mentioned method embodiments. To avoid repetition, they will not be described here.

[0574] The apparatus 1200 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the device in the above-mentioned method, or the apparatus 1200 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the network device in the above-mentioned method. The function 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.

[0575] In addition, the transceiver unit 1210 may also be a transceiver circuit (for example, may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

[0576] It should be noted that the device in Figure 1200 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.

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

[0578] Optionally, there are one or more processors 1310 .

[0579] Optionally, there are one or more memories 1320 .

[0580] It should be understood that the processor 1310 and memory 1320 described above can be combined into a single processing device, with the processor 1310 configured to execute program code stored in the memory 1320 to implement the aforementioned functions. In a specific implementation, the memory 1320 can also be integrated into the processor 1310 or independent of the processor 1310. It should be understood that the processor 1310 can also correspond to the various processing units in the aforementioned communication device, and the transceiver 1330 can correspond to the various receiving units and transmitting units in the aforementioned communication device.

[0581] It should also be understood that the transceiver 1330 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.

[0582] Specifically, the communication device 1300 may correspond to the terminal device in methods 700 to 1100 according to the embodiments of the present application. The communication device 1300 may include the units of the methods 700 to 1100 performed by the 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.

[0583] When the communication device 1300 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.

[0584] 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.

[0585] 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).

[0586] 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.

[0587] 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.

[0588] 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.

[0589] 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.

[0590] The present application also provides a system, which includes the aforementioned first access network device, second access network device, access and mobility management function device and first session management function device.

[0591] 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)).

[0592] 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.

[0593] 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.

[0594] 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.

[0595] 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.

[0596] It should be noted that in the embodiments of the present application, "pre-setting", "pre-configuration", etc. can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, a terminal device). This application does not limit its specific implementation method, such as the preset rules, preset constants, etc. in the embodiments of the present application.

[0597] 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.

[0598] 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.

[0599] 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 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.

[0600] 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.

[0601] 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.

[0602] 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.

[0603] 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.

[0604] 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.

[0605] 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.

[0606] 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.

[0607] 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 changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A task-based communication method, characterized in that: Applied to a first node, the first node is used to provide a management and control function of a first task, the first task includes a process of achieving a service goal based on the collaboration of heterogeneous resources, and the method includes: receiving a first request from a terminal device, wherein the first request is used to request control of execution of the first task, and the first request includes information of the first task; determining a second node according to the first request, where the second node is used to control execution of the first task; Sending the type of the second node to the terminal device, where the type of the second node includes an access network element or a core network element; Alternatively, the first request is sent to the second node.

2. The method according to claim 1, characterized in that Before sending the first request to the second node, the first request received from the terminal device is sent according to the type of the second node, and the type of the second node is determined by the terminal device according to a first mapping relationship, and the first mapping relationship is used to indicate the correspondence between the first task event and the type of the second node.

3. The method according to claim 2, characterized in that The method further comprises: Send the first mapping relationship to the terminal device.

4. The method according to any one of claims 1 to 3, characterized in that The first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

5. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Receiving first configuration information from the terminal device; The first configuration information is sent to the second node, where the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

6. The method according to any one of claims 1 to 5, characterized in that The first node is a core network element or an access network element.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: When the first node is a core network element, receiving the first request through non-access layer signaling; Alternatively, when the first node is an access network element, the first request is received via radio resource control signaling.

8. The method according to any one of claims 1 to 7, characterized in that When the first node is a core network element, the method further includes: The identifier of the second node is sent to a third node, where the third node is a network element of the access network to which the terminal device accesses.

9. The method according to any one of claims 1 to 8, characterized in that The information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of the first task, a description of the first task, and requirements of the first task.

10. A task-based communication method, characterized in that: Applied to a terminal device, the method comprises: Acquire a first node, where the first node is used to provide a management and control function of a first task, where the first task includes a process of achieving a service goal based on the collaboration of heterogeneous resources; Sending a first request to the first node, the first request being used to request control of execution of the first task, The first request includes information of the first task.

11. The method according to claim 10, characterized in that The obtaining of the first node comprises: Determining the type of the second node according to a first mapping relationship, where the first mapping relationship is used to indicate a correspondence between the first task event and the type of the second node, where the type of the second node includes a core network element or an access network element; A first node is determined according to a type of the second node, where the type of the first node is the same as the type of the second node.

12. The method according to claim 11, characterized in that The method further comprises: Receive the first mapping relationship from an access network element or a core network element.

13. The method according to claim 10, characterized in that The method further comprises: receiving a type of a second node from the first node, where the type of the second node includes a core network element or an access network element, and the second node is a node determined by the first node to control execution of the first task; The first request is sent to the second node according to the type of the second node, where the first request is used to request control of execution of the first task.

14. The method according to any one of claims 10 to 13, characterized in that: The first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

15. The method according to any one of claims 10 to 13, characterized in that: The method further comprises: First configuration information is sent to the second node according to the type of the second node, where the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

16. The method according to any one of claims 10 to 15, characterized in that The first node is a core network element or an access network element.

17. The method according to any one of claims 10 to 16, characterized in that The method further comprises: When the first node is a core network element, sending the first request through non-access layer signaling; Alternatively, when the first node is an access network element, the first request is sent via radio resource control signaling.

18. The method according to any one of claims 10 to 17, characterized in that: The information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of the task, a description of the task, and a task requirement.

19. A task-based communication method, characterized in that: Applied to a third node, the third node being an access network element accessed by a terminal device, the method comprising: receiving a first request from the terminal device, the first request being used to request control of execution of the first task, the first request including information of the first task requested by the terminal device, the first task including a process of collaboratively achieving a service goal based on heterogeneous resources; determining the second node according to an identifier of the second node sent by the first node, where the first node is used to provide a management and control function of the first task; sending the first request to the second node; or, Based on the first request, execution of the first task is controlled.

20. The method according to claim 19, characterized in that The first request also includes first configuration information, and the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

21. The method according to claim 19, characterized in that The sending the first request to the second node, the method further comprising: Receiving first configuration information from the terminal device; The first configuration information is sent to the second node, where the first configuration information includes computing power configuration and / or algorithm configuration for executing the first task.

22. The method according to any one of claims 19 to 21, characterized in that The first node is a core network element or an access network element.

23. The method according to any one of claims 19 to 22, characterized in that The information of the first task includes one or more of an identifier of the first task, an identifier of the terminal device, a type of the task, a description of the task, and a task requirement.

24. A task-based communication method, characterized in that: The method comprises: The terminal device acquires a first node, where the first node is used to provide a management and control function of a first task, where the first task includes a process of achieving a service goal based on the collaboration of heterogeneous resources; The terminal device sends a first request to the first node, where the first request is used to request to control the execution of a first task, and the first request includes information about the first task; The first node determines the second node according to the first request, and the second node is used to control the execution of the first task; The first node sends the type of the second node to the terminal device, where the type of the second node includes an access network element or a core network element; Alternatively, the first node sends the first request to the second node, where the first request is used to request the second node to control execution of the first task.

25. A communication device, characterized in that: The communication device is used to perform the method according to any one of claims 1 to 24.

26. 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 24.

27. The device according to claim 26, characterized in that The apparatus also includes the memory.

28. 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 24.

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

30. 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 24.

Images