Terminal capability registration method, terminal capability acquisition method, terminal capability registration device, terminal capability acquisition device, terminal and equipment

Abstract

The invention discloses a terminal capability registration method, a terminal capability acquisition method, a terminal capability registration device, a terminal capability acquisition device, a terminal and equipment, and belongs to the technical field of communication. The terminal capability registration method comprises the steps that the terminal sends a first message, the first message is used for providing task capability information of the terminal, or the first message is used for providing task capability information of the terminal; the first message is used for modifying task capability information of the terminal; wherein the task capability information of the terminal comprises at least one of the following items: task capability indication information used for indicating whether the terminal supports task related characteristics or not; the subtask capability information is used for indicating whether the terminal supports the capability of executing the subtask and / or an identifier of the supported subtask; the subtask template information is used for indicating the type of a subtask template supported by the terminal and / or the content of the task template; the activation time information is used for indicating a time period when the terminal supports execution of the subtask; the template downloading capability information is used for indicating whether the terminal supports downloading of the template or not.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a terminal capability registration method, acquisition method, device, terminal and equipment. Background Art

[0002] Traditional communication systems are connection-oriented in design. Typical application scenarios involve providing connections between specific terminals or between terminals and application servers. The network architecture provides a complete lifecycle management mechanism and Quality of Service (QoS) guarantees for sessions, thereby providing connectivity for data transmission, supporting user mobility, and guaranteeing a robust service experience.

[0003] Unlike traditional communications services, artificial intelligence (AI) is data- and compute-intensive. To enable networks with native AI capabilities, 6G networks must introduce new resource dimensions, including heterogeneous computing and storage resources, new computing tasks, and new data types. In the future, a task-centric management mechanism may be introduced, enabling management at a task-based rather than session-based granularity. With this task-based management mechanism, if the network does not know the terminal's task capabilities, it cannot determine what tasks the terminal can perform. For example, whether a terminal can request a task, participate in a task, or complete a task cannot guarantee successful task execution. Summary of the Invention

[0004] The embodiments of the present application provide a terminal capability registration method, acquisition method, apparatus, terminal and device, which are used to solve the problem that the successful execution of tasks cannot be guaranteed under a task-based management mechanism.

[0005] In a first aspect, a terminal capability registration method is provided, which is executed by a terminal, and the method includes:

[0006] The terminal sends a first message, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal;

[0007] The task capability information of the terminal includes at least one of the following:

[0008] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0009] Subtask capability information, used to indicate whether the terminal supports the ability to perform subtasks and / or the identification of supported subtasks;

[0010] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the terminal;

[0011] Activation time information, used to indicate the time period during which the terminal supports execution of the subtask;

[0012] Template download capability information is used to indicate whether the terminal supports template downloading.

[0013] In a second aspect, a method for acquiring terminal capabilities is provided, which is performed by a second network element. The method includes:

[0014] The second network element receives a first message sent by the terminal, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal;

[0015] The task capability information of the terminal includes at least one of the following:

[0016] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0017] Subtask capability information, used to indicate whether the terminal supports the ability to perform subtasks and / or the identification of supported subtasks;

[0018] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the terminal;

[0019] Activation time information, used to indicate the time period during which the terminal supports execution of the subtask;

[0020] Template download capability information is used to indicate whether the terminal supports template downloading.

[0021] In a third aspect, a method for acquiring terminal capabilities is provided, which is performed by a first network element. The method includes:

[0022] The first network element receives a first message sent by the terminal or receives a third message sent by the second network element; wherein the first message or the third message is used to provide task capability information of the terminal;

[0023] The task capability information of the terminal includes at least one of the following:

[0024] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0025] Subtask capability information, used to indicate whether the terminal supports the ability to perform subtasks and / or the identification of supported subtasks;

[0026] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the terminal;

[0027] Activation time information, used to indicate the time period during which the terminal supports execution of the subtask;

[0028] Template download capability information is used to indicate whether the terminal supports template downloading.

[0029] In a fourth aspect, a terminal capability registration device is provided, which is applied to a terminal, and the device includes:

[0030] A first sending module is configured to send a first message, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal;

[0031] The task capability information of the terminal includes at least one of the following:

[0032] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0033] Subtask capability information, used to indicate whether the terminal supports the ability to perform subtasks and / or the identification of supported subtasks;

[0034] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the terminal;

[0035] Activation time information, used to indicate the time period during which the terminal supports execution of the subtask;

[0036] Template download capability information is used to indicate whether the terminal supports template downloading.

[0037] In a fifth aspect, a terminal capability acquisition device is provided, which is applied to a second network element, and the device includes:

[0038] A second receiving module is configured to receive a first message sent by a terminal, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal;

[0039] The task capability information of the terminal includes at least one of the following:

[0040] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0041] Subtask capability information, used to indicate whether the terminal supports the ability to perform subtasks and / or the identification of supported subtasks;

[0042] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the terminal;

[0043] Activation time information, used to indicate the time period during which the terminal supports execution of the subtask;

[0044] Template download capability information is used to indicate whether the terminal supports template downloading.

[0045] In a sixth aspect, a terminal capability acquisition device is provided, applied to a first network element, the device including:

[0046] a fourth receiving module, configured to receive a first message sent by a terminal or a third message sent by a second network element; wherein the first message or the third message is used to provide task capability information of the terminal;

[0047] The task capability information of the terminal includes at least one of the following:

[0048] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0049] Subtask capability information, used to indicate whether the terminal supports the ability to perform subtasks and / or the identification of supported subtasks;

[0050] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the terminal;

[0051] Activation time information, used to indicate the time period during which the terminal supports execution of the subtask;

[0052] Template download capability information is used to indicate whether the terminal supports template downloading.

[0053] In a seventh aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0054] In an eighth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to send a first message, the first message being used to provide task capability information of the terminal, or the first message being used to modify the task capability information of the terminal; wherein the task capability information of the terminal includes at least one of the following: task capability indication information, used to indicate whether the terminal supports task-related characteristics; subtask capability information, used to indicate whether the terminal supports the ability to execute subtasks and / or the identification of supported subtasks; subtask template information, used to indicate the type of subtask template supported by the terminal and / or the content of the task template; activation time information, used to indicate the time period in which the terminal supports the execution of subtasks; template download capability information, used to indicate whether the terminal supports template downloading.

[0055] In the ninth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect or the third aspect are implemented.

[0056] In a tenth aspect, a network-side device is provided, comprising a processor and a communication interface, wherein, when the network-side device is a second network element, the communication interface is configured to receive a first message sent by a terminal, the first message being configured to provide task capability information of the terminal, or the first message being configured to modify the task capability information of the terminal;

[0057] In a case where the network side device is a first network element, the communication interface is used to receive a first message sent by a terminal or receive a third message sent by a second network element; wherein the first message or the third message is used to provide task capability information of the terminal;

[0058] Among them, the task capability information of the terminal includes at least one of the following: task capability indication information, used to indicate whether the terminal supports task-related characteristics; subtask capability information, used to indicate whether the terminal supports the ability to execute subtasks and / or the identification of supported subtasks; subtask template information, used to indicate the type of subtask templates supported by the terminal and / or the content of the task template; activation time information, used to indicate the time period for the terminal to execute the subtask; template download capability information, used to indicate whether the terminal supports template downloading.

[0059] In the eleventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0060] In the twelfth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect or the third aspect.

[0061] In the thirteenth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect.

[0062] In the fourteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the terminal capability registration method as described in the first aspect, or to implement the steps of the terminal capability acquisition method as described in the second aspect or the third aspect.

[0063] In the fifteenth aspect, a computer program product is provided, comprising computer instructions, which, when executed by a processor, implement the steps of the terminal capability registration method as described in the first aspect, or implement the steps of the terminal capability acquisition method as described in the second aspect or the third aspect.

[0064] In the embodiments of the present application, a terminal can send its own task capability information to other network elements or modify its own task capability information, thereby realizing the registration or modification of task capabilities. By the terminal reporting its own task capability information to the network side, the network side can determine a lot of information related to the terminal task, such as whether the terminal is allowed to initiate a task, what tasks the terminal can initiate, whether the terminal can participate in the execution of a task, etc., to ensure the successful execution of the task. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0066] Figure 2 This is one of the flow charts of the terminal capability registration method according to an embodiment of the present application;

[0067] Figure 3 This is the second flow chart of the terminal capability registration method according to an embodiment of the present application;

[0068] Figure 4 This is the third flow chart of the terminal capability registration method according to an embodiment of the present application;

[0069] Figure 5 This is the fourth flow chart of the terminal capability registration method according to an embodiment of the present application;

[0070] Figure 6 This is one of the flow charts of the terminal capability acquisition method according to an embodiment of the present application;

[0071] Figure 7 This is the second flow chart of the terminal capability acquisition method according to an embodiment of the present application;

[0072] Figure 8 is a schematic structural diagram of a terminal capability registration device according to an embodiment of the present application;

[0073] Figure 9This is one of the structural diagrams of the terminal capability acquisition device according to an embodiment of the present application;

[0074] Figure 10 This is the second structural diagram of the terminal capability acquisition device according to an embodiment of the present application;

[0075] Figure 11 is a schematic structural diagram of a communication device according to an embodiment of the present application;

[0076] Figure 12 is a schematic structural diagram of a terminal according to an embodiment of the present application;

[0077] Figure 13 It is a structural diagram of the network side device of an embodiment of the present application. DETAILED DESCRIPTION

[0078] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0079] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0080] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0081] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0082] Figure 1The block diagram of a wireless communication system applicable to the embodiments of the present application is shown. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture, etc.), a game console, a personal computer (PC), a teller machine, or a self-service machine, etc., and other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0083] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application server discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0084] In addition, to facilitate understanding of the technical solutions provided by this application, the following describes the relevant technical features involved in this application, as follows:

[0085] 1. Mission: A comprehensive service (collection) including communication, information, synaesthesia, and computing, provided on-demand by the 6G system based on external service requests. The external service requests can come from UEs, OTT (Over The Top), etc.

[0086] 2. Task Management (TM): This is a management process that aims to respond to external business requests and provides communication functions and other 6G additional functions (such as positioning, telepathy, computing, etc.).

[0087] 3. Task Session: This refers to the process of communication between a UE and a TM, or the process of communication between the UE, the TM, and related subtask functions. A task session can correspond to one or more subtask sessions (a subtask session refers to the process of communication between the TM and a subtask function). Establishing a task session establishes a data transmission channel between the UE and the TM, or a data transmission channel between the UE, the TM, and related subtasks. In other words, a task session is a network resource established between the UE, the TM, and related subtask functions in the operator's network. A task session is sometimes also referred to as a task connection or task bearer. A task session or subtask session can sometimes be implemented as a PDU session. The task session in this application is different from the Protocol Data Unit (PDU) session (the data channel between the UE and the User Plane Function (UPF)) in the prior art. For example, in the prior art, if a UE wants to use a perception service, the UE will establish a PDU session (the data channel between the UE and the UPF). When the data reaches the UPF, the UPF may use some non-standard methods to transfer it to the perception execution node.

[0088] The task session identifier is used to identify the task session and can be allocated by the UE and sent to the network, or allocated by the TM.

[0089] The subtask session identifier is used to identify the subtask session. The task session identifier and the subtask identifier have a one-to-one mapping relationship or a one-to-many mapping relationship (a task is a combined task). The subtask session identifier can be allocated by the UE and sent to the network, or the subtask session identifier can be allocated by the TM, subtask management, or subtask function.

[0090] It should be noted that the target task or subtask in the embodiment of the present application is a task that is transmitted through a task session or a subtask session, and the transmission here can be the transmission of signaling or the transmission of data.

[0091] 4. The TM function is a core network element that can be used to implement one or more of the following functions: task verification, task template generation, task translation or disassembly, task management, task ID or task session ID allocation, task slicing or task data network name (DNN) allocation, subtask management function or subtask function selection.

[0092] Task verification refers to verifying whether a task is a legitimate task requested by an authorized or permitted task consumer or requester (including but not limited to UE and AF). Task verification includes at least one of the following: verifying whether the AF allows the task template request, whether the task request comes from an authorized or permitted UE (whether the UE has a task contract), whether the task request comes from an authorized or permitted AF (depending on whether there is a task agreement between the TM and the AF), and whether the task exceeds the upper limit of the number of tasks associated with the UE or AF.

[0093] The following, in conjunction with the accompanying drawings, describes in detail the terminal capability registration method, acquisition method, apparatus, terminal and device provided in the embodiments of the present application through some embodiments and their application scenarios.

[0094] like Figure 2 As shown, an embodiment of the present application provides a terminal capability registration method, which is executed by a terminal, and the method includes:

[0095] Step 201: The terminal sends a first message, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal;

[0096] The task capability information of the terminal includes at least one of the following:

[0097] (1) Task capability indication information (Task indication), which is used to indicate whether the terminal supports task-related features, including: initiating a task request and / or obeying the task-based management of the network-side device. Whether the terminal supports the task-related features, for example: whether the terminal supports initiating a task request; and / or whether the terminal can obey the task-based management of the network-side device. Whether the terminal can obey the task-based management of the network-side device can also be understood as whether the terminal can participate in some sub-tasks of the network-side device management.

[0098] Optionally, the task-related characteristics of a terminal can also be understood as whether it supports a specific task. For example, whether the terminal supports initiating an automatic parking task request; and / or whether the terminal supports initiating an environment reconstruction task; and / or whether the terminal supports initiating a digital twin task.

[0099] In this embodiment, the terminal reports or registers the task capability indication information to the network side device so that the network side can know the task-related capabilities of the terminal that are different from other terminals. When the network side device performs task-based management in the future, it can use this information to determine whether the terminal can initiate a task request, and can also use this information to determine whether the terminal can participate in the execution of a task.

[0100] (2) Sub-task capability information, which indicates whether the terminal supports the ability to perform sub-tasks and / or the identification of supported sub-tasks; that is, it indicates which sub-tasks the terminal supports, such as communication sub-tasks, computing sub-tasks, perception sub-tasks, and AI sub-tasks.

[0101] In this embodiment, the terminal reports or registers the subtask capability information to the network side device so that the network side can know which specific subtasks the terminal can initiate, such as synaesthesia subtasks and AI subtasks. In this way, when the network side device subsequently accepts a task request, if the task contains a subtask that the terminal does not support, the network side device can reject the request. In addition, the network side device can also send the corresponding subtask template to the terminal based on this information. If the terminal does not support a subtask, the network side device does not need to send the template of the subtask to the terminal.

[0102] Optionally, the subtask capability information of the terminal refers to whether the terminal supports the ability to complete / process a certain subtask, such as whether the terminal supports the processing of the AI ​​training subtask. If supported, the information is set to supported, otherwise it can be set to unsupported; similarly, there may be some supported or unsupported capability indications for other subtasks.

[0103] (3) Subtask template information (Template capability), which is used to indicate the type of subtask templates supported by the terminal and / or the content of the task template. The subtask template information can be expressed as a subtask identifier, for example, 0001 is used to identify a subtask template, which is a general template belonging to a computing subtask; or 000A is used to identify a task template, which is a task template belonging to users in a certain area.

[0104] In this embodiment, the terminal reports or registers the subtask template information to the network side device so that the network side can know which subtask templates the terminal can support. It can be further understood as which task templates or subtask templates the terminal can understand or use, which makes it convenient for the network side to issue the corresponding task templates or subtask templates that the terminal can support. For example: the network side issues a calculation subtask template, which contains many parameters. When the terminal requests a task, this task includes a calculation subtask, then the terminal will carry this subtask template and fill in various parameter requirements and indicator requirements similar to filling out a questionnaire. If the terminal does not support the calculation subtask template, it cannot fill in the requirements of the subtask, and it cannot initiate a task.

[0105] Optionally, the subtask template information may include, but is not limited to, at least one of: a task description, a task Quality of Experience (QoE) description, a task policy / QoS description, and task parameters. The purpose of the subtask template information is to enable the subtask executor to have a clear and specific understanding of a subtask, such as the required QoS, the service the subtask is used to complete, perception, or AI model training, etc.

[0106] (4) Activation period information, which is used to indicate the time period during which the terminal supports the execution of the subtask; that is, the time period during which the terminal can provide task-related services. The terminal can provide task-related services within the indicated time period.

[0107] In this embodiment, the terminal reports or registers the activation time information to the network side device so that the network side can know at which specific time the terminal expects to perform task-related signaling interaction. For example, if the terminal does not expect to be disturbed at night, it will actively turn off the task-related function and expect the network side device not to page the terminal due to task-related signaling, nor to allow the terminal to participate in the execution of a task.

[0108] (5) Template download capability information, which is used to indicate whether the terminal supports template downloading. Optionally, the template download capability information may also indicate which templates the terminal supports downloading.

[0109] In this embodiment, the terminal reports or registers the template download capability information to the network device, allowing the network to know whether the terminal supports direct download of a template, including a task template or a subtask template. Because some templates vary greatly in size, for larger templates (for example, templates that may be around 1M), the network device may pre-deploy them on the terminal, or download them to the terminal via the network control plane or user plane. If the terminal supports downloading, then when the template is subsequently updated, the network can update the terminal via signaling or data. If the terminal does not support downloading, it can only use the initial template and cannot support some new template features.

[0110] In this embodiment, the first message may be a registration message or a registration request message, i.e., the terminal registers its own task capability information. The first message may also be a modification message, i.e., the terminal modifies its own task capability information. For example, the task capability information of the terminal may be pre-stored in a predetermined network element (such as a UDM), and the terminal may update its own task-related information and send the updated task capability information to the predetermined network element.

[0111] Optionally, the subtasks in the embodiments of the present application include at least one of the following types: perception subtask, computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP Multimedia System (IMS) subtask; for another example, the subtasks may also include but are not limited to computing subtasks, information processing subtasks, multimedia subtasks, immersive subtasks, communication subtasks, etc. Among them, the computing subtasks include AI computing tasks and non-AI computing tasks; the information processing subtasks include positioning information processing, synaesthesia information processing, etc.; the immersive subtasks include extended reality (XR) tasks, virtual reality (VR) tasks, etc.

[0112] The subtasks can be understood as completing an independent function, with multiple subtasks combined to support the completion of a single task. A task can be a combination of multiple functions or subtasks, such as an automated parking task or an environmental reconstruction task. These tasks require not only computational subtasks but also positioning subtasks, and may also require AI subtasks. Multiple functions are combined to complete a single task.

[0113] In the embodiments of the present application, a terminal can send its own task capability information to other network elements or modify its own task capability information, thereby realizing the registration or modification of task capabilities. By the terminal reporting its own task capability information to the network side, the network side can determine a lot of information related to the terminal task, such as whether the terminal is allowed to initiate a task, what tasks the terminal can initiate, whether the terminal can participate in the execution of a task, etc., to ensure the successful execution of the task.

[0114] As an optional embodiment, sending the first message includes at least one of the following:

[0115] (1) sending the first message to a first network element, where the first network element is a network element that supports splitting a target task into one or more target subtasks;

[0116] (2) Sending the first message to a second network element, where the second network element is a core network element.

[0117] In this embodiment, the first network element supports decomposing the target task into one or more subtasks. The target task may be a task requested by the terminal to the network side device, for example: the terminal requests an automatic parking task from the network side device, and the network side device establishes and executes the task. The first network element may support the translation of tasks, the decomposition of tasks, the function selection of subtasks, the collaboration between subtasks, the management of the task life cycle, etc. The first network element may be a task management unit (Task Management function, TM). The terminal sends a first message to the first network element, which may be used to register or modify its own task capability information. When the first message is used to modify its own task capability information, the task capability information of the terminal may be pre-stored in the first network element.

[0118] The second network element is a core network element, such as one or more of an AMF, an SMF, and an UDM. The terminal sends a first message to the second network element to register its own task capability information with the second network element or to modify its own task capability information with the second network element. When the first message is used to modify its own task capability information, the second network element may pre-store the task capability information of the terminal.

[0119] Optionally, when the first network element or the second network element pre-stores the task capability information of the terminal, the first network element or the second network element can sign a contract to modify the task capability information of the terminal, that is, the first network element or the second network element can directly update the task capability information of the terminal internally without the terminal triggering the modification.

[0120] After the first network element or the second network element modifies the task capability information of the terminal, the first network element or the second network element may send a notification message to the terminal to notify the terminal that the task capability information has been modified.

[0121] As an optional embodiment, sending the first message includes:

[0122] Sending a first request message to the second network element, where the first request message is used to request an address of the first network element;

[0123] receiving a second message sent by the second network element, where the second message carries the address of the first network element;

[0124] Send the first message to the first network element according to the address of the first network element.

[0125] In this embodiment, when a terminal needs to send a first message to a first network element, it can first obtain the address of the first network element from a second network element, and then send the first message to the first network element based on the address sent by the second network element. Specifically, the first network element sends a first request message to the second network element, which may be a registration request message, for obtaining the address of the first network element for registering task capabilities. The second network element responds to the terminal with the address of the first network element based on the first request message.

[0126] Optionally, the method further includes:

[0127] A first response message is received, where the first response message carries task capability information of the network-side device, or the first response message indicates a modification result of the task capability information.

[0128] In this embodiment, the first response message is a reply message of the first network element or the second network element after receiving the first message. For example: the terminal sends a first message to the first network element, and the first message is used to provide the task capability information of the terminal, that is, the terminal registers the task capability information with the first network element; after the first network element receives the first message, it can send a first response message to the terminal, and the first response message can indicate that the aforementioned task capability information is successfully registered or the task capability information registration fails. In addition, the first response message can also carry the task capability information on the network side. Alternatively, the first message sent by the terminal is used to modify the task capability information. After the first network element receives the first message, it replies to the terminal with the modification result, such as a successful modification or a failed modification.

[0129] Optionally, the task capability information of the network-side device includes at least one of the following:

[0130] (1) Task capability indication information (Task indication), used to indicate whether the network-side device supports task-based management capabilities; for example, indicating whether the first network element supports task-based management capabilities;

[0131] Optionally, the task capability indication information of the network side device can also be understood as whether it supports the management of a specific task (such as lifecycle management, service provision, etc.), for example: whether the network side device supports the task management and service provision of automatic parking; and / or whether the network side device supports the task management and service provision of environment reconstruction; and / or whether the network side device supports the task management and service provision of digital twins.

[0132] In this embodiment, the first network element or the second network element provides the task capability indication information to the terminal so that the terminal can know whether the currently serving network can accept a task request. If the network does not support task-based management, then the task cannot be completed. For example: the terminal wants to request an automatic parking task. If the current area does not support task-based management, then the automatic parking task cannot be completed. Therefore, the terminal will not further request the task from the network. (2) Sub-task capability information (Sub-Task capability), which is used to indicate whether the network-side device supports the ability to execute (or process or complete) subtasks and / or the identification of supported subtasks; that is, it indicates which subtasks the network-side device supports to execute or manage, such as communication subtasks, computing subtasks, perception subtasks, AI subtasks, etc.

[0133] In this embodiment, the first or second network element provides the subtask capability information to the terminal, allowing the terminal to know the subtask capabilities supported by the network. For example, some network-side devices may not have AI training units deployed and cannot train AI models. This can prevent tasks that require training a new model from being completed smoothly, affecting the user experience. If the terminal knows the subtask capability information of the network-side device, the terminal can request the corresponding task based on the subtask capabilities of the network.

[0134] Optionally, the subtask capability information of the network side device refers to whether the network side device supports the ability to complete / process a certain subtask, such as whether the network supports the processing of the AI ​​training subtask. If supported, the information is set to supported, otherwise it can be set to unsupported; similarly, there may be some supported or unsupported capability indications for other subtasks.

[0135] (3) Subtask template information, which is used to indicate the type of subtask templates supported by the network-side device and / or the content of the task template; for example, 0001 is used to identify a subtask template, which is a general template belonging to a computing subtask; or 000A is used to identify a task template, which is a task template belonging to a user in a certain area.

[0136] The first network element or the second network element provides the subtask template information to the terminal so that the terminal can know which task templates or subtask templates the network can support. It can be further understood that the subtask template sent by the terminal can be understood or used by the network, which makes it convenient for the terminal to request the task template or subtask template that the network can support accordingly.

[0137] Optionally, subtask template information refers to information used to indicate requirements for subtasks. Subtask template information may include but is not limited to task description, task QoE description, task strategy / QoS description, and at least one of task parameters. The purpose of subtask template information is to enable the subtask executor to have a clear and definite understanding of a subtask, such as what kind of QoS is required, what service this subtask is used to complete, perception or AI model training, etc.

[0138] (4) Activation time information, used to indicate the time period during which the network-side device supports the execution of the subtask; for example, indicating the time period during which the first network element can provide task-based management capabilities, and the first network element can provide task-based services within the indicated time period.

[0139] In this embodiment, the first network element or the second network element provides the activation time information to the terminal so that the terminal can know at which specific time the network can perform task-related signaling interaction. For example, in order to save energy and power, the network does not support task requests at certain times. When the terminal sends the request, it will be directly rejected. For example, at some tourist attractions, there is no need to guide traffic most of the time. Only when the traffic becomes heavier on certain holidays will some traffic guidance tasks be supported. In this way, the network can enable task-based management in a specific time period to facilitate the terminal to request traffic guidance tasks and improve network efficiency.

[0140] In this embodiment, based on the task capability information of the above-mentioned network side device, the terminal can know whether the network side device supports functions such as translation and understanding of the task, management of the task, splitting of the task, and management of various templates, and ensure the successful execution of the task through the interaction of task capability information.

[0141] The following example illustrates the implementation process of terminal capability registration.

[0142] Example 1: For example, the terminal sends a first message to the second network element, the first message is used to provide the task capability information of the terminal, and the first network element requests the task capability information of the terminal from the second network element. Figure 3 As shown, the first network element is TM, the second network element is AMF or SMF, and the terminal capability registration process includes:

[0143] Step 30: The TM registers the capabilities of the network-side device with the NRF. The task capability information of the network-side device sent includes at least one of the following:

[0144] (1) Task capability indication information (Task indication), used to indicate whether the network-side device supports task-based management capabilities; for example, indicating whether the first network element supports task-based management capabilities;

[0145] (2) Sub-task capability information, which indicates whether the network-side device supports the ability to perform sub-tasks and / or the identifier of the supported sub-tasks;

[0146] (3) Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the network-side device;

[0147] Optionally, subtask template information refers to information used to indicate requirements for subtasks. Subtask template information may include but is not limited to task description, task QoE description, task strategy / QoS description, and at least one of task parameters. The purpose of subtask template information is to enable the subtask executor to have a clear and definite understanding of a subtask, such as what kind of QoS is required, what service this subtask is used to complete, perception or AI model training, etc.

[0148] (4) Activation time information is used to indicate that the network-side device supports the execution of the subtask within the second time period. It can be understood that the activation time information is used to indicate the time period in which the network-side device supports the execution of the subtask.

[0149] Method 1: The UE registers task capability information with the AMF.

[0150] Step 31a: The UE sends a first message to the AMF. The first message may be a registration message or a registration request message. The first message carries the task capability information of the terminal, including at least one of the following:

[0151] (1) Task capability indication information, which indicates whether the terminal supports task-related features; for example, whether the terminal supports initiating a task request; or whether the terminal supports task-based management, that is, participating as a terminal in some subtasks such as data collection.

[0152] (2) Sub-task capability information, which is used to indicate whether the terminal supports the ability to execute sub-tasks and / or the identifiers of supported sub-tasks; that is, to indicate which sub-tasks the terminal supports.

[0153] (3) Subtask template information (Template capability), which is used to indicate the type of subtask templates and / or the content of the task templates supported by the terminal; the subtask template information may be expressed as an identifier of the subtask.

[0154] (4) Activation period information, which is used to indicate the time period during which the terminal supports the execution of the subtask; that is, the time period during which the terminal can provide task-related services. The terminal can provide task-related services within the indicated time period.

[0155] (5) Template download capability information, which is used to indicate whether the terminal supports template downloading.

[0156] Step 32a: After receiving the first message, the AMF queries the NRF for the task capability information of the network-side device;

[0157] Step 33a: The AMF sends a response message to the terminal, which carries the task capability information of the network-side device.

[0158] Optionally, step 34a: the TM may request the task capability information of the terminal from the AMF.

[0159] Method 2: UE registers task capability information with SMF.

[0160] Step 31b: The UE sends a first message to the SMF. The first message may be a registration message or a registration request message. The first message carries the task capability information of the terminal, including at least one of the following:

[0161] (1) Task capability indication information (Task indication), used to indicate whether the terminal supports task-related features;

[0162] (2) Sub-task capability information, which is used to indicate whether the terminal supports the ability to execute sub-tasks and / or the identifiers of supported sub-tasks; that is, to indicate which sub-tasks the terminal supports.

[0163] (3) Subtask template information (Template capability), which is used to indicate the type of subtask templates and / or the content of the task templates supported by the terminal; the subtask template information may be expressed as an identifier of the subtask.

[0164] (4) Activation period information, which is used to indicate the time period during which the terminal supports the execution of the subtask; that is, the time period during which the terminal can provide task-related services. The terminal can provide task-related services within the indicated time period.

[0165] (5) Template download capability information, which is used to indicate whether the terminal supports template downloading.

[0166] Step 32b: After receiving the first message, the SMF queries the NRF for the task capability information of the network-side device;

[0167] Step 33b: The SMF sends a response message to the terminal, which carries the task capability information of the network-side device.

[0168] Optionally, step 34b: the TM may request the task capability information of the terminal from the SMF.

[0169] In this embodiment, the terminal registers task capability information with the AMF or SMF. After receiving the task capability information of the terminal, the AMF or SMF feeds back the task capability information of the network-side device to the terminal. The TM can learn the task capability of the terminal from the AMF or SMF, thus realizing task capability interaction between the terminal and the network-side device.

[0170] Example 2: For example, the terminal sends a first message to the first network element, and the first message is used to provide the task capability information of the terminal. Figure 4 As shown, the first network element is TM, and the terminal capability registration process includes:

[0171] Method A: The terminal knows the TM address and the UE registers directly with the TM. The TM address is configured by default in the terminal or in a joint configuration of the TM and other network elements such as the AMF.

[0172] Step 41a: The UE sends a first message to the TM. The first message may be a registration message or a registration request message. The first message carries task capability information of the terminal, including at least one of the following:

[0173] (1) Task capability indication information (Task indication), used to indicate whether the terminal supports task-related features;

[0174] (2) Sub-task capability information, which is used to indicate whether the terminal supports the ability to execute sub-tasks and / or the identifiers of supported sub-tasks; that is, to indicate which sub-tasks the terminal supports.

[0175] (3) Subtask template information (Template capability), which is used to indicate the type of subtask templates and / or the content of the task templates supported by the terminal; the subtask template information may be expressed as an identifier of the subtask.

[0176] (4) Activation period information, which is used to indicate the time period during which the terminal supports the execution of the subtask; that is, the time period during which the terminal can provide task-related services. The terminal can provide task-related services within the indicated time period.

[0177] (5) Template download capability information, which is used to indicate whether the terminal supports template downloading.

[0178] Step 42a: After receiving the first message, the TM sends a response message to the terminal. The response message carries the task capability information of the network-side device.

[0179] The task capability information of the network side device includes at least one of the following:

[0180] Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities;

[0181] Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask;

[0182] Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device;

[0183] The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

[0184] Method B: The terminal does not know the address of the TM, and requests the address of the TM from the second network element, which is the AMF.

[0185] Step 41b: The UE sends a request message to the AMF, requesting the address of the TM for task capability registration.

[0186] Step 42b: The AMF sends a reply message to the UE, which carries the address of the TM.

[0187] Step 43b: The UE sends a first message to the TM. The first message may be a registration message or a registration request message. The first message carries the task capability information of the terminal. The task capability information of the terminal is not described here.

[0188] Step 44b: After receiving the first message, the TM sends a response message to the terminal. The response message carries the task capability information of the network side device. The task capability information of the network side device is not described here.

[0189] Method C: The terminal does not know the address of the TM, and requests the address of the TM from the second network element, which is the SMF.

[0190] Step 41c: The UE sends a request message to the SMF, where the request message is used to request the address of the TM for task capability registration.

[0191] Step 42c: The SMF sends a reply message to the request message to the UE, which carries the address of the TM;

[0192] Step 43c: The UE sends a first message to the TM. The first message may be a registration message or a registration request message. The first message carries the task capability information of the terminal. The task capability information of the terminal is not described here.

[0193] Step 44c: After receiving the first message, the TM sends a response message to the terminal. The response message carries the task capability information of the network side device. The task capability information of the network side device is not described in detail here.

[0194] In this embodiment, the terminal registers task capability information with the TM. After receiving the task capability information of the terminal, the TM feeds back the task capability information of the network side device to the terminal, thereby realizing task capability interaction between the terminal and the network side device.

[0195] Example 3: For example, the terminal sends a first message to the second network element, and the first message is used to modify the task capability information of the terminal. Figure 5 As shown in the figure, the first network element is TM and the second network element is UDM. The terminal capability registration process includes:

[0196] Step 50: The UDM stores the contract information of the terminal, including the task capability information of the terminal, including at least one of the following:

[0197] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0198] The subtask capability information is used to indicate whether the terminal supports the capability of executing the subtask and / or the identifier of the supported subtask; that is, to indicate which subtasks the terminal supports executing.

[0199] The subtask template information is used to indicate the type of subtask templates and / or the content of the task templates supported by the terminal; the subtask template information may be expressed as an identifier of the subtask.

[0200] The activation time information is used to indicate the time period during which the terminal supports the execution of the subtask; that is, to indicate the time period during which the terminal can provide task-related services. The terminal can provide task-related services within the indicated time period.

[0201] Template download capability information is used to indicate whether the terminal supports template downloading.

[0202] Step 51 (optional), TM or other network elements (such as AMF, SMF) query the UDM for the terminal's contract information;

[0203] Step 52 (optional): UDM replies to TM or other network elements (e.g., AMF, SMF) with the terminal's subscription information.

[0204] Step 53: The UE sends a first message to the UDM, where the first message carries the modified task capability information of the UE.

[0205] Optionally, the UE may forward the first message to the UDM through network elements such as AMF and SMF, or the UE may directly send the first message to the UDM.

[0206] Step 54: The UDM sends a response message to the UE, indicating that the modification is successful.

[0207] Step 55: UDM notifies TM or other network elements (such as AMF, SMF) that the task capability information of the terminal has been modified, which carries the modified task capability information.

[0208] Optionally, in another embodiment, the UE does not trigger the task capability information modification, the UDM can sign a contract for modification, and directly update the task capability information of the terminal internally, and the above steps 53 and 54 are not included.

[0209] In this embodiment, the terminal updates task capability information to the UDM. After receiving the updated task capability information from the terminal, the UDM notifies the TM or other network elements of the updated task capability information, thereby implementing task capability interaction between the terminal and network-side devices.

[0210] In the embodiments of the present application, a terminal can send its own task capability information to other network elements or modify its own task capability information, thereby realizing the registration or modification of task capabilities. By the terminal reporting its own task capability information to the network side, the network side can determine a lot of information related to the terminal task, such as whether the terminal is allowed to initiate a task, what tasks the terminal can initiate, whether the terminal can participate in the execution of a task, etc., to ensure the successful execution of the task.

[0211] like Figure 6 As shown, the embodiment of the present application further provides a terminal capability acquisition method, which is executed by the second network element, including:

[0212] Step 601: A second network element receives a first message sent by a terminal, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal.

[0213] The task capability information of the terminal includes at least one of the following:

[0214] (1) Task capability indication information (Task indication), which is used to indicate whether the terminal supports task-related features; the task-related features include: initiating a task request and / or obeying the task-based management of the network-side device. Whether the terminal supports task-related features, for example: whether the terminal supports initiating a task request; and / or whether the terminal can obey the task-based management of the network-side device. Whether the terminal can obey the task-based management of the network-side device can also be understood as whether the terminal can participate in some sub-tasks of the network-side device management.

[0215] Optionally, the task-related characteristics of a terminal can also be understood as whether it supports a specific task. For example, whether the terminal supports initiating an automatic parking task request; and / or whether the terminal supports initiating an environment reconstruction task; and / or whether the terminal supports initiating a digital twin task.

[0216] In this embodiment, the terminal reports or registers the task capability indication information to the second network element so that the network side can know the task-related capabilities of the terminal that are different from other terminals. When the network side device performs task-based management in the future, it can use this information to determine whether the terminal can initiate a task request, and can also use this information to determine whether the terminal can participate in the execution of a task.

[0217] (2) Sub-task capability information, which indicates whether the terminal supports the ability to perform sub-tasks and / or the identification of supported sub-tasks; that is, it indicates which sub-tasks the terminal supports, such as communication sub-tasks, computing sub-tasks, perception sub-tasks, and AI sub-tasks.

[0218] In this embodiment, the terminal reports or registers the subtask capability information to the second network element so that the network side can know which specific subtasks the terminal can initiate, such as synaesthesia subtasks and AI subtasks. In this way, when the network side device subsequently accepts a task request, if the task contains a subtask that the terminal does not support, the network side device can reject the request. In addition, the network side device can also send the corresponding subtask template to the terminal based on this information. If the terminal does not support a subtask, the network side device does not need to send the template of the subtask to the terminal.

[0219] Optionally, the subtask capability information of the terminal refers to whether the terminal supports the capability of completing / processing a certain subtask.

[0220] (3) Subtask template information (Template capability), which is used to indicate the type of subtask templates supported by the terminal and / or the content of the task template. The subtask template information can be expressed as a subtask identifier, for example, 0001 is used to identify a subtask template, which is a general template belonging to a computing subtask; or 000A is used to identify a task template, which is a task template belonging to users in a certain area.

[0221] In this embodiment, the terminal reports or registers the subtask template information to the second network element so that the network side can know which subtask templates the terminal can support. This can be further understood as which task templates or subtask templates the terminal can understand or use, which makes it convenient for the network side to issue the corresponding task templates or subtask templates that the terminal can support. For example: the network side issues a calculation subtask template, which contains many parameters. When the terminal requests a task, the task includes a calculation subtask. Then the terminal will carry this subtask template and fill in various parameter requirements and indicator requirements similar to filling out a questionnaire. If the terminal does not support the calculation subtask template, it cannot fill in the requirements of the subtask, and it cannot initiate a task.

[0222] Optionally, the subtask template information may include, but is not limited to, at least one of: a task description, a task Quality of Experience (QoE) description, a task policy / QoS description, and task parameters. The purpose of the subtask template information is to enable the subtask executor to have a clear and specific understanding of a subtask, such as the required QoS, the service the subtask is used to complete, perception, or AI model training, etc.

[0223] (4) Activation period information, which is used to indicate the time period during which the terminal supports the execution of the subtask; that is, the time period during which the terminal can provide task-related services. The terminal can provide task-related services within the indicated time period.

[0224] In this embodiment, the terminal reports or registers the activation time information to the second network element, so that the network side can know at which specific time the terminal expects to perform task-related signaling interaction. For example, if the terminal does not expect to be disturbed at night, it will actively turn off the task-related function and expect the network side device not to page the terminal due to task-related signaling, nor to let the terminal participate in the execution of a task.

[0225] (5) Template download capability information, which is used to indicate whether the terminal supports template downloading. Optionally, the template download capability information may also indicate which templates the terminal supports downloading.

[0226] In this embodiment, the terminal reports or registers the template download capability information to the second network element, allowing the network to know whether the terminal supports direct download of a template, including a task template or a subtask template. Because some templates vary greatly in size, for larger templates (for example, templates that may be around 1M), network-side equipment may be pre-deployed on the terminal, or downloaded to the terminal via the network control plane or user plane. If the terminal supports downloading, the network can update the terminal via signaling or data when the template is subsequently updated. If the terminal does not support downloading, it can only use the initial template and cannot support some new template features.

[0227] In this embodiment, the first message may be a registration message or a registration request message, i.e., the terminal registers its own task capability information. The first message may also be a modification message, i.e., the terminal modifies its own task capability information. For example, the task capability information of the terminal may be pre-stored in a predetermined network element (such as a UDM), and the terminal may update its own task-related information and send the updated task capability information to the predetermined network element. Optionally, the second network element is a core network element, such as one or more of the AMF, SMF, and UDM.

[0228] In the embodiments of the present application, the terminal can send its own task capability information to the second network element or modify its own task capability information, thereby realizing the registration or modification of task capabilities. By the terminal reporting its own task capability information to the network side, the network side can determine a lot of information related to the terminal task, such as whether the terminal is allowed to initiate a task, what tasks the terminal can initiate, whether the terminal can participate in the execution of a task, etc., to ensure the successful execution of the task.

[0229] As an optional embodiment, the method further includes:

[0230] A first response message is sent to the terminal, where the first response message carries the task capability information of the network side device, or the first response message indicates a modification result of the task capability information.

[0231] In this embodiment, the first response message is a reply message of the second network element after receiving the first message. For example: the terminal sends a first message to the second network element, and the first message is used to provide the task capability information of the terminal, that is, the terminal registers the task capability information with the second network element; after the second network element receives the first message, it can send a first response message to the terminal, and the first response message can indicate that the aforementioned task capability information is successfully registered or the task capability information registration fails. In addition, the first response message can also carry the task capability information on the network side. Alternatively, the first message sent by the terminal is used to modify the task capability information. After the second network element receives the first message, it replies to the terminal with the modification result, such as a successful modification or a failed modification.

[0232] Optionally, the method further includes: querying a third network element for task capability information of the network-side device.

[0233] In this embodiment, the third network element may be a network element with a network storage function, such as an NRF. After receiving the task capability information of the terminal, the second network element may query the task capability information of the network side device from the third network element and reply the task capability information of the network side device to the terminal.

[0234] Optionally, the task capability information of the network-side device includes at least one of the following:

[0235] (1) Task capability indication information (Task indication), used to indicate whether the network-side device supports task-based management capabilities; for example, indicating whether the first network element supports task-based management capabilities;

[0236] Optionally, the task capability indication information of the network side device can also be understood as whether it supports the management of a specific task (such as lifecycle management, service provision, etc.), for example: whether the network side device supports the task management and service provision of automatic parking; and / or whether the network side device supports the task management and service provision of environment reconstruction; and / or whether the network side device supports the task management and service provision of digital twins.

[0237] In this embodiment, the second network element provides the task capability indication information to the terminal, allowing the terminal to know whether the current serving network can accept a task request. If the network does not support task-based management, the task cannot be completed. For example, if the terminal wants to request an automatic parking task, if the current area does not support task-based management, the automatic parking task cannot be completed, and therefore the terminal will not further request the task from the network.

[0238] (2) Sub-task capability information, which is used to indicate whether the network-side device supports the ability to execute sub-tasks and / or the identification of the supported sub-tasks; that is, it indicates which sub-tasks the network-side device supports to execute or manage, such as communication sub-tasks, computing sub-tasks, perception sub-tasks, AI sub-tasks, etc.

[0239] In this embodiment, the second network element provides the terminal with the subtask capability information, allowing the terminal to know the subtask capabilities supported by the network. For example, some network-side devices may not have an AI training unit deployed and cannot train AI models. This can prevent tasks that require training a new model from being completed smoothly, affecting the user experience. If the terminal knows the subtask capability information of the network-side device, it can request the corresponding task based on the network's subtask capabilities.

[0240] (3) Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the network-side device;

[0241] For example, 0001 is used to identify a subtask template, which is a general template belonging to a computing subtask; or 000A is used to identify a task template, which is a task template belonging to a user in a certain area.

[0242] The second network element provides the subtask template information to the terminal so that the terminal can know which task templates or subtask templates the network can support. It can be further understood that the subtask template sent by the terminal can be understood or used by the network, which makes it convenient for the terminal to request the task template or subtask template that the network can support accordingly.

[0243] (4) Activation time information, used to indicate the time period during which the network-side device supports the execution of the subtask; for example, indicating the time period during which the first network element can provide task-based management capabilities, and the first network element can provide task-based services within the indicated time period.

[0244] In this embodiment, the second network element provides the activation time information to the terminal so that the terminal can know at which specific time the network can perform task-related signaling interaction. For example, in order to save energy and power, the network does not support task requests at certain times. When the terminal sends the request, it will be directly rejected. For example, at some tourist attractions, there is no need to guide traffic most of the time. Only when the traffic becomes heavier on certain holidays will some traffic guidance tasks be supported. In this way, the network can enable task-based management in a specific time period to facilitate the terminal to request traffic guidance tasks and improve network efficiency.

[0245] As an optional embodiment, the method further includes: sending the modified task capability information of the terminal to the first network element.

[0246] In this embodiment, after receiving the modified task capability information sent by the terminal, the second network element may notify the first network element or other network elements of the modified task capability information of the terminal.

[0247] As an optional embodiment, the method further includes:

[0248] receiving a second request message sent by the first network element, where the second request message is used to request task capability information of the terminal;

[0249] A third message is sent to the first network element, where the third message is used to provide task capability information of the terminal.

[0250] In this embodiment, the first network element may request the task capability information of the terminal from the second network element. The first network element is a network element that supports decomposing a target task into one or more target subtasks. The target task may be a task requested by the terminal to the network side device, for example: the terminal requests a task from the network side device, and the network side device establishes and executes the task. The first network element may support task translation, task decomposition, subtask function selection, collaboration between subtasks, etc. The first network element may be a task management function (TM).

[0251] In an embodiment of the present application, the terminal can send its own task capability information to the second network element or modify its own task capability information, thereby realizing the registration or modification of the task capability. The second network element can notify other network elements of the task capability information sent by the terminal, thereby realizing the interaction of task capability information between the terminal and the network side. By the terminal reporting its own task capability information to the network side, the network side can determine a lot of information related to the terminal task, such as whether the terminal is allowed to initiate a task, what kind of tasks the terminal can initiate, whether the terminal can participate in the execution process of a task, etc., to ensure the successful execution of the task.

[0252] like Figure 7 As shown, the embodiment of the present application further provides a terminal capability acquisition method, which is executed by a first network element and includes:

[0253] Step 701: A first network element receives a first message sent by a terminal or receives a third message sent by a second network element; wherein the first message or the third message is used to provide task capability information of the terminal;

[0254] The task capability information of the terminal includes at least one of the following:

[0255] (1) Task capability indication information (Task indication), used to indicate whether the terminal supports task-related features; the task-related features include: initiating a task request and / or obeying the task-based management of the network-side device. Whether the terminal supports task-related features, for example: whether the terminal supports initiating a task request; and / or whether the terminal can obey the task-based management of the network-side device. Whether the terminal can obey the task-based management of the network-side device can also be understood as whether the terminal can participate in some sub-tasks of the network-side device management. Optionally, the task-related features of the terminal can also be understood as whether a specific task is supported. Whether the terminal supports task-related features, for example, whether the terminal supports initiating an automatic parking task request; and / or whether the terminal supports initiating an environment reconstruction task; and / or whether the terminal supports initiating a digital twin task.

[0256] In this embodiment, the terminal reports or registers the task capability indication information to the network side device so that the network side can know the task-related capabilities of the terminal that are different from other terminals. When the network side device performs task-based management in the future, it can use this information to determine whether the terminal can initiate a task request, and can also use this information to determine whether the terminal can participate in the execution of a task.

[0257] (2) Sub-task capability information, which is used to indicate whether the terminal supports the ability to execute sub-tasks and / or the identifiers of supported sub-tasks; that is, to indicate which sub-tasks the terminal supports.

[0258] In this embodiment, the terminal reports or registers the subtask capability information to the network side device so that the network side can know which specific subtasks the terminal can initiate, such as synaesthesia subtasks and AI subtasks. In this way, when the network side device subsequently accepts a task request, if the task contains a subtask that the terminal does not support, the network side device can reject the request. In addition, the network side device can also send the corresponding subtask template to the terminal based on this information. If the terminal does not support a subtask, the network side device does not need to send the template of the subtask to the terminal.

[0259] Optionally, the subtask capability information of the terminal refers to whether the terminal supports the capability of completing / processing a certain subtask.

[0260] (3) Subtask template information (Template capability), which is used to indicate the type of subtask templates supported by the terminal and / or the content of the task template. The subtask template information can be expressed as a subtask identifier, for example, 0001 is used to identify a subtask template, which is a general template belonging to a computing subtask; or 000A is used to identify a task template, which is a task template belonging to users in a certain area.

[0261] In this embodiment, the terminal reports or registers the subtask template information to the network side device so that the network side can know which subtask templates the terminal can support. It can be further understood as which task templates or subtask templates the terminal can understand or use, which makes it convenient for the network side to issue the corresponding task templates or subtask templates that the terminal can support. For example: the network side issues a calculation subtask template, which contains many parameters. When the terminal requests a task, this task includes a calculation subtask, then the terminal will carry this subtask template and fill in various parameter requirements and indicator requirements similar to filling out a questionnaire. If the terminal does not support the calculation subtask template, it cannot fill in the requirements of the subtask, and it cannot initiate a task.

[0262] Optionally, the subtask template information may include, but is not limited to, at least one of: a task description, a task QoE description, a task policy / QoS description, and task parameters. The purpose of the subtask template information is to enable the subtask executor to have a clear and unambiguous understanding of a subtask.

[0263] (4) Activation period information, which is used to indicate the time period during which the terminal supports the execution of the subtask; that is, the time period during which the terminal can provide task-related services. The terminal can provide task-related services within the indicated time period.

[0264] In this embodiment, the terminal reports or registers the activation time information to the network side device so that the network side can know at which specific time the terminal expects to perform task-related signaling interaction. For example, if the terminal does not expect to be disturbed at night, it will actively turn off the task-related function and expect the network side device not to page the terminal due to task-related signaling, nor to allow the terminal to participate in the execution of a task.

[0265] (5) Template download capability information, which is used to indicate whether the terminal supports template downloading. Optionally, the template download capability information may also indicate which templates the terminal supports downloading.

[0266] In this embodiment, the terminal reports or registers the template download capability information to the network device, allowing the network to know whether the terminal supports direct download of a template, including a task template or a subtask template. Because some templates vary greatly in size, for larger templates (for example, templates that may be around 1M), the network device may pre-deploy them on the terminal, or download them to the terminal via the network control plane or user plane. If the terminal supports downloading, then when the template is subsequently updated, the network can update the terminal via signaling or data. If the terminal does not support downloading, it can only use the initial template and cannot support some new template features.

[0267] Optionally, the first network element is a network element that supports decomposing the target task into one or more target subtasks; and the second network element is a core network element.

[0268] In this embodiment, the first network element supports decomposing a target task into one or more subtasks. The target task may be a task requested by a terminal from a network device. For example, a terminal requests a task from a network device, and the network device establishes and executes the task. The first network element may support task translation, task decomposition, subtask function selection, and collaboration between subtasks. The first network element may be a TM. The second network element is a core network element, such as an AMF, SMF, or UDM.

[0269] The terminal may directly send a first message to the first network element to register or modify its own task capability information. The terminal may also send a first message to a second network element, and the first network element requests the task capability information of the terminal from the second network element.

[0270] When the first message is used to modify the task capability information of the terminal, the first network element may pre-store the task capability information of the terminal. Optionally, if the first network element pre-stores the task capability information of the terminal, the first network element may sign a contract to modify the task capability information of the terminal, that is, without the terminal triggering the modification, the first network element may directly update the task capability information of the terminal internally.

[0271] As an optional embodiment, the method further includes:

[0272] A first response message is sent to the terminal, where the first response message carries task capability information of the network-side device.

[0273] In this embodiment. The first response message is a reply message of the first network element after receiving the first message. For example: the terminal sends a first message to the first network element, and the first message is used to provide the task capability information of the terminal, that is, the terminal registers the task capability information with the first network element; after the first network element receives the first message, it can send a first response message to the terminal, and the first response message can indicate that the aforementioned task capability information is successfully registered or the task capability information registration fails. In addition, the first response message can also carry the task capability information of the network side. Alternatively, the first message sent by the terminal is used to modify the task capability information, and after the first network element receives the first message, it replies to the terminal with the modification result, such as a successful modification or a failed modification.

[0274] Optionally, the task capability information of the network-side device includes at least one of the following:

[0275] (1) Task capability indication information (Task indication), used to indicate whether the network-side device supports task-based management capabilities; for example, indicating whether the first network element supports task-based management capabilities;

[0276] Optionally, the task capability indication information of the network side device can also be understood as whether it supports the management of a specific task (such as lifecycle management, service provision, etc.), for example: whether the network side device supports the task management and service provision of automatic parking; and / or whether the network side device supports the task management and service provision of environment reconstruction; and / or whether the network side device supports the task management and service provision of digital twins.

[0277] In this embodiment, the first network element provides the terminal with the task capability indication information to let the terminal know whether the current serving network can accept a task request. If the network does not support task-based management, the task cannot be completed. For example, if the terminal wants to request an automatic parking task, if the current area does not support task-based management, the automatic parking task cannot be completed. Therefore, the terminal will not further request the task from the network.

[0278] (2) Sub-Task capability information, which indicates whether the network device supports the ability to execute subtasks and / or the identification of supported subtasks; that is, it indicates which subtasks the network device supports executing or managing. Optionally, the sub-task capability information of the network device refers to whether the network device supports the ability to complete / process a subtask.

[0279] In this embodiment, the first network element provides the terminal with the subtask capability information, allowing the terminal to know the subtask capabilities supported by the network. For example, some network-side devices may not have an AI training unit deployed and cannot train AI models. This can prevent tasks that require training a new model from being completed smoothly, affecting the user experience. If the terminal knows the subtask capability information of the network-side device, it can request the corresponding task based on the network's subtask capabilities.

[0280] (3) Subtask template information, which is used to indicate the type of subtask templates supported by the network-side device and / or the content of the task template; for example, 0001 is used to identify a subtask template, which is a general template belonging to a computing subtask; or 000A is used to identify a task template, which is a task template belonging to a user in a certain area.

[0281] The first network element provides the subtask template information to the terminal so that the terminal can know which task templates or subtask templates the network can support. It can be further understood that the subtask template sent by the terminal can be understood or used by the network, which makes it convenient for the terminal to request the task template or subtask template that the network can support accordingly.

[0282] Optionally, subtask template information refers to information used to indicate requirements for a subtask. The subtask template information may include but is not limited to at least one of a task description, a task QoE description, a task strategy / QoS description, and task parameters. The purpose of the subtask template information is to enable the subtask executor to have a clear and definite understanding of a subtask.

[0283] (4) Activation time information, used to indicate the time period during which the network-side device supports the execution of the subtask; for example, indicating the time period during which the first network element can provide task-based management capabilities, and the first network element can provide task-based services within the indicated time period.

[0284] In this embodiment, the first network element provides the activation time information to the terminal so that the terminal can know at which specific time the network can perform task-related signaling interaction. For example, in order to save energy and power, the network does not support task requests at certain times. When the terminal sends the request, it will be directly rejected. For example, at some tourist attractions, there is no need to guide traffic most of the time. Only when the traffic becomes heavier on certain holidays will some traffic guidance tasks be supported. In this way, the network can enable task-based management in a specific time period to facilitate the terminal to request traffic guidance tasks and improve network efficiency.

[0285] As an optional embodiment, before receiving the third message sent by the second network element, the method further includes:

[0286] A second request message is sent to the second network element, where the second request message is used to request task capability information of the terminal.

[0287] In this embodiment, the terminal sends a first message to the second network element to provide task capability information of the terminal or modify the task capability information of the terminal. The first network element may request the task capability information of the terminal from the second network element.

[0288] Optionally, the method further includes:

[0289] Receive the modified task capability information of the terminal sent by the second network element.

[0290] In this embodiment, the terminal may send the modified task capability information to the second network element. After receiving the modified task capability information sent by the terminal, the second network element may notify the first network element or other network elements of the modified task capability information of the terminal.

[0291] In the embodiments of the present application, the terminal can send its own task capability information to the first network element or modify its own task capability information, thereby realizing the registration or modification of task capabilities. By the terminal reporting its own task capability information to the network side, the network side can determine a lot of information related to the terminal task, such as whether the terminal is allowed to initiate a task, what tasks the terminal can initiate, whether the terminal can participate in the execution of a task, etc., to ensure the successful execution of the task.

[0292] The terminal capability registration method provided in the embodiment of the present application can be executed by a terminal capability registration device. In the embodiment of the present application, the terminal capability registration device provided in the embodiment of the present application is described by taking the terminal capability registration method executed by the terminal capability registration device as an example.

[0293] like Figure 8 As shown, an embodiment of the present application provides a terminal capability registration device 800, which is applied to a terminal and includes:

[0294] A first sending module 810 is configured to send a first message, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal;

[0295] The task capability information of the terminal includes at least one of the following:

[0296] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0297] Subtask capability information, used to indicate whether the terminal supports the ability to perform subtasks and / or the identification of supported subtasks;

[0298] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the terminal;

[0299] Activation time information, used to indicate the time period during which the terminal supports execution of the subtask;

[0300] Template download capability information is used to indicate whether the terminal supports template downloading.

[0301] Optionally, the first sending module is configured to perform at least one of the following:

[0302] Sending the first message to a first network element, where the first network element is a network element that supports splitting a target task into one or more target subtasks;

[0303] The first message is sent to a second network element, where the second network element is a core network element.

[0304] Optionally, the first sending module includes:

[0305] A first sending unit, configured to send a first request message to the second network element, where the first request message is used to request an address of the first network element;

[0306] A first receiving unit, configured to receive a second message sent by the second network element, where the second message carries the address of the first network element;

[0307] The second sending unit is used to send the first message to the first network element according to the address of the first network element.

[0308] Optionally, the device further includes:

[0309] The first receiving module is configured to receive a first response message, where the first response message carries task capability information of the network-side device, or the first response message indicates a modification result of the task capability information.

[0310] Optionally, the task capability information of the network-side device includes at least one of the following:

[0311] Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities;

[0312] Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask;

[0313] Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device;

[0314] The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

[0315] In the embodiments of the present application, a terminal can send its own task capability information to other network elements or modify its own task capability information, thereby realizing the registration or modification of task capabilities. By the terminal reporting its own task capability information to the network side, the network side can determine a lot of information related to the terminal task, such as whether the terminal is allowed to initiate a task, what tasks the terminal can initiate, whether the terminal can participate in the execution of a task, etc., to ensure the successful execution of the task.

[0316] The terminal capability acquisition method provided in the embodiment of the present application can be executed by a terminal capability acquisition device. In the embodiment of the present application, the terminal capability acquisition device performing the terminal capability registration method is taken as an example to illustrate the terminal capability acquisition device provided in the embodiment of the present application.

[0317] like Figure 9 As shown, an embodiment of the present application provides a terminal capability acquisition device 900, which is applied to a second network element, including:

[0318] A second receiving module 910 is configured to receive a first message sent by a terminal, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal;

[0319] The task capability information of the terminal includes at least one of the following:

[0320] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0321] Subtask capability information, used to indicate whether the terminal supports the ability to perform subtasks and / or the identification of supported subtasks;

[0322] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the terminal;

[0323] Activation time information, used to indicate the time period during which the terminal supports execution of the subtask;

[0324] Template download capability information is used to indicate whether the terminal supports template downloading.

[0325] Optionally, the device further includes:

[0326] The second sending module is configured to send a first response message to the terminal, where the first response message carries the task capability information of the network side device, or the first response message indicates a modification result of the task capability information.

[0327] Optionally, the device further includes:

[0328] The query module is used to query the task capability information of the network side device from the third network element.

[0329] Optionally, the task capability information of the network-side device includes at least one of the following:

[0330] Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities;

[0331] Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask;

[0332] Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device;

[0333] The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

[0334] Optionally, the device further includes:

[0335] The third sending module is configured to send the modified task capability information of the terminal to the first network element.

[0336] Optionally, the device further includes:

[0337] A third receiving module is configured to receive a second request message sent by the first network element, where the second request message is used to request task capability information of the terminal;

[0338] A third message is sent to the first network element, where the third message carries the task capability information of the terminal.

[0339] Optionally, the first network element is a network element that supports decomposing the target task into one or more target subtasks; and the second network element is a core network element.

[0340] In the embodiments of the present application, the terminal can send its own task capability information to the second network element or modify its own task capability information, thereby realizing the registration or modification of task capabilities. By the terminal reporting its own task capability information to the network side, the network side can determine a lot of information related to the terminal task, such as whether the terminal is allowed to initiate a task, what tasks the terminal can initiate, whether the terminal can participate in the execution of a task, etc., to ensure the successful execution of the task.

[0341] like Figure 10 As shown, an embodiment of the present application provides a terminal capability acquisition device 1000, which is applied to a first network element and includes:

[0342] The fourth receiving module 1010 is configured to receive a first message sent by a terminal or a third message sent by a second network element; wherein the first message or the third message is used to provide task capability information of the terminal;

[0343] The task capability information of the terminal includes at least one of the following:

[0344] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0345] Subtask capability information, used to indicate whether the terminal supports the ability to perform subtasks and / or the identification of supported subtasks;

[0346] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the terminal;

[0347] Activation time information, used to indicate the time period during which the terminal supports execution of the subtask;

[0348] Template download capability information is used to indicate whether the terminal supports template downloading.

[0349] Optionally, the first network element is a network element that supports decomposing the target task into one or more target subtasks; and the second network element is a core network element.

[0350] Optionally, the device further includes:

[0351] The fourth sending module is used to send a first response message to the terminal, where the first response message carries task capability information of the network side device.

[0352] Optionally, the task capability information of the network-side device includes at least one of the following:

[0353] Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities;

[0354] Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask;

[0355] Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device;

[0356] The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

[0357] Optionally, the device further includes:

[0358] The fifth sending module is used to send a second request message to the second network element, where the second request message is used to request task capability information of the terminal.

[0359] Optionally, the device further includes:

[0360] The fifth receiving module is configured to receive the modified task capability information of the terminal sent by the second network element.

[0361] In the embodiments of the present application, the terminal can send its own task capability information to the first network element or modify its own task capability information, thereby realizing the registration or modification of task capabilities. By the terminal reporting its own task capability information to the network side, the network side can determine a lot of information related to the terminal task, such as whether the terminal is allowed to initiate a task, what tasks the terminal can initiate, whether the terminal can participate in the execution of a task, etc., to ensure the successful execution of the task.

[0362] The terminal capability registration device or terminal capability acquisition device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0363] The terminal capability registration device or terminal capability acquisition device provided in the embodiments of the present application can achieve Figures 2 to 7 The various processes implemented by the method embodiment achieve the same technical effect and are not described here again to avoid repetition.

[0364] like Figure 11 As shown, an embodiment of the present application further provides a communication device 1100, including a processor 1101 and a memory 1102, wherein the memory 1102 stores a program or instruction that can be run on the processor 1101. For example, when the communication device 1100 is a terminal, the program or instruction is executed by the processor 1101 to implement the various steps of the above-mentioned terminal capability registration method or terminal capability acquisition method embodiment, and can achieve the same technical effect. When the communication device 1100 is a network-side device, the program or instruction is executed by the processor 1101 to implement the various steps of the above-mentioned terminal capability registration method or terminal capability acquisition method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0365] The embodiment of the present application further provides a terminal, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the following Figure 2The steps in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 12 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0366] The terminal 1200 includes but is not limited to: a radio frequency unit 1201, a network module 1202, an audio output unit 1203, an input unit 1204, a sensor 1205, a display unit 1206, a user input unit 1207, an interface unit 1208, a memory 1209 and at least some of the components of the processor 1210.

[0367] Those skilled in the art will understand that the terminal 1200 may also include a power supply (such as a battery) to power each component, and the power supply may be logically connected to the processor 1210 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. Figure 12 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0368] It should be understood that in an embodiment of the present application, the input unit 1204 may include a graphics processing unit (GPU) 12041 and a microphone 12042, and the graphics processor 12041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1206 may include a display panel 12061, and the display panel 12061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1207 includes a touch panel 12071 and at least one of other input devices 12072. The touch panel 12071 is also called a touch screen. The touch panel 12071 may include two parts: a touch detection device and a touch controller. Other input devices 12072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0369] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1201 may transmit the data to the processor 1210 for processing. Furthermore, the RF unit 1201 may send uplink data to the network-side device. Typically, the RF unit 1201 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0370] The memory 1209 can be used to store software programs or instructions and various data. The memory 1209 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1209 may include a volatile memory 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. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1209 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0371] Processor 1210 may include one or more processing units. Optionally, processor 1210 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1210.

[0372] The radio frequency unit 1201 is configured to send a first message, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal;

[0373] The task capability information of the terminal includes at least one of the following:

[0374] Task capability indication information, used to indicate whether the terminal supports task-related features;

[0375] Subtask capability information, used to indicate whether the terminal supports the ability to perform subtasks and / or the identification of supported subtasks;

[0376] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the terminal;

[0377] Activation time information, used to indicate the time period during which the terminal supports execution of the subtask;

[0378] Template download capability information is used to indicate whether the terminal supports template downloading.

[0379] Optionally, the radio frequency unit 1201 is specifically configured to perform at least one of the following:

[0380] Sending the first message to a first network element, where the first network element is a network element that supports splitting a target task into one or more target subtasks;

[0381] The first message is sent to a second network element, where the second network element is a core network element.

[0382] Optionally, the radio frequency unit 1201 is specifically configured to:

[0383] Sending a first request message to the second network element, where the first request message is used to request an address of the first network element;

[0384] receiving a second message sent by the second network element, where the second message carries the address of the first network element;

[0385] Send the first message to the first network element according to the address of the first network element.

[0386] Optionally, the radio frequency unit 1201 is further configured to:

[0387] A first response message is received, where the first response message carries task capability information of the network-side device, or the first response message indicates a modification result of the task capability information.

[0388] Optionally, the task capability information of the network-side device includes at least one of the following:

[0389] Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities;

[0390] Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask;

[0391] Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device;

[0392] The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

[0393] In the embodiments of the present application, a terminal can send its own task capability information to other network elements or modify its own task capability information, thereby realizing the registration or modification of task capabilities. By the terminal reporting its own task capability information to the network side, the network side can determine a lot of information related to the terminal task, such as whether the terminal is allowed to initiate a task, what tasks the terminal can initiate, whether the terminal can participate in the execution of a task, etc., to ensure the successful execution of the task.

[0394] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the terminal capability registration method in the method embodiment, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0395] Specifically, the embodiment of the present application also provides a network side device. Figure 13 As shown, the network side device 1300 includes: a processor 1301, a network interface 1302 and a memory 1303. The network interface 1302 is, for example, a common public radio interface (CPRI).

[0396] Specifically, the network side device 1300 of the embodiment of the present invention further includes: instructions or programs stored in the memory 1303 and executable on the processor 1301, and the processor 1301 calls the instructions or programs in the memory 1303 to execute. Figure 9 or Figure 10 The methods executed by the modules shown achieve the same technical effects, so they will not be described here to avoid repetition.

[0397] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned terminal capability registration method or terminal capability acquisition method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0398] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0399] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned terminal capability registration method or terminal capability acquisition method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0400] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0401] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned terminal capability registration method or terminal capability acquisition method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0402] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the terminal capability registration method described above, and the network side device can be used to execute the steps of the terminal capability acquisition method described above.

[0403] An embodiment of the present application further provides a computer program product, including computer instructions, which, when executed by a processor, implement the steps of the terminal capability registration method or the terminal capability acquisition method described above.

[0404] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0405] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0406] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A terminal capability registration method, characterized in that: include: The terminal sends a first message, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal; The task capability information of the terminal includes at least one of the following: Task capability indication information, used to indicate whether the terminal supports task-related features; Subtask capability information, used to indicate whether the terminal supports the capability of executing the subtask and / or the identification of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the terminal; Activation time information, used to indicate the time period during which the terminal supports execution of the subtask; Template download capability information is used to indicate whether the terminal supports template downloading.

2. The method according to claim 1, characterized in that The sending of the first message includes at least one of the following: Sending the first message to a first network element, where the first network element is a network element that supports splitting a target task into one or more target subtasks; The first message is sent to a second network element, where the second network element is a core network element.

3. The method according to claim 1 or 2, characterized in that The sending of the first message includes: Sending a first request message to the second network element, where the first request message is used to request an address of the first network element; receiving a second message sent by the second network element, where the second message carries the address of the first network element; Send the first message to the first network element according to the address of the first network element.

4. The method according to claim 1, wherein The method further comprises: A first response message is received, where the first response message carries task capability information of the network-side device, or the first response message indicates a modification result of the task capability information.

5. The method according to claim 4, characterized in that The task capability information of the network-side device includes at least one of the following: Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities; Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device; The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

6. A method for acquiring terminal capabilities, characterized in that: include: The second network element receives a first message sent by the terminal, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal; The task capability information of the terminal includes at least one of the following: Task capability indication information, used to indicate whether the terminal supports task-related features; Subtask capability information, used to indicate whether the terminal supports the capability of executing the subtask and / or the identification of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the terminal; Activation time information, used to indicate the time period during which the terminal supports execution of the subtask; Template download capability information is used to indicate whether the terminal supports template downloading.

7. The method according to claim 6, characterized in that The method further comprises: A first response message is sent to the terminal, where the first response message carries the task capability information of the network side device, or the first response message indicates a modification result of the task capability information.

8. The method according to claim 7, characterized in that The method further comprises: Query the third network element for the task capability information of the network side device.

9. The method according to claim 7 or 8, characterized in that The task capability information of the network-side device includes at least one of the following: Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities; Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device; The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

10. The method according to claim 7, characterized in that The method further comprises: Send the modified task capability information of the terminal to the first network element.

11. The method according to claim 7, characterized in that The method further comprises: receiving a second request message sent by the first network element, where the second request message is used to request task capability information of the terminal; A third message is sent to the first network element, where the third message is used to provide task capability information of the terminal.

12. The method according to claim 10 or 11, characterized in that The first network element is a network element that supports splitting a target task into one or more target subtasks; the second network element is a core network element.

13. A method for acquiring terminal capabilities, characterized in that: include: The first network element receives a first message sent by the terminal or receives a third message sent by the second network element; wherein the first message or the third message is used to provide task capability information of the terminal; The task capability information of the terminal includes at least one of the following: Task capability indication information, used to indicate whether the terminal supports task-related features; Subtask capability information, used to indicate whether the terminal supports the capability of executing the subtask and / or the identification of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the terminal; Activation time information, used to indicate the time period during which the terminal supports execution of the subtask; Template download capability information is used to indicate whether the terminal supports template downloading.

14. The method according to claim 13, characterized in that The first network element is a network element that supports splitting a target task into one or more target subtasks; the second network element is a core network element.

15. The method according to claim 13, characterized in that The method further comprises: A first response message is sent to the terminal, where the first response message carries task capability information of the network-side device.

16. The method according to claim 15, characterized in that The task capability information of the network-side device includes at least one of the following: Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities; Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device; The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

17. The method according to claim 13, wherein Before receiving the third message sent by the second network element, the method further includes: A second request message is sent to the second network element, where the second request message is used to request task capability information of the terminal.

18. The method according to claim 13, characterized in that The method further comprises: Receive the modified task capability information of the terminal sent by the second network element.

19. A terminal capability registration device, applied to a terminal, characterized in that: include: A first sending module, configured to send a first message, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal; The task capability information of the terminal includes at least one of the following: Task capability indication information, used to indicate whether the terminal supports task-related features; Subtask capability information, used to indicate whether the terminal supports the capability of executing the subtask and / or the identification of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the terminal; Activation time information, used to indicate the time period during which the terminal supports execution of the subtask; Template download capability information is used to indicate whether the terminal supports template downloading.

20. The device according to claim 19, characterized in that The first sending module is configured to perform at least one of the following: Sending the first message to a first network element, where the first network element is a network element that supports splitting a target task into one or more target subtasks; The first message is sent to a second network element, where the second network element is a core network element.

21. The device according to claim 19 or 20, characterized in that The first sending module includes: A first sending unit, configured to send a first request message to the second network element, where the first request message is used to request an address of the first network element; A first receiving unit, configured to receive a second message sent by the second network element, where the second message carries the address of the first network element; The second sending unit is used to send the first message to the first network element according to the address of the first network element.

22. The device according to claim 19, characterized in that The device further comprises: The first receiving module is configured to receive a first response message, where the first response message carries task capability information of the network-side device, or the first response message indicates a modification result of the task capability information.

23. The device according to claim 22, characterized in that The task capability information of the network-side device includes at least one of the following: Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities; Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device; The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

24. A terminal capability acquisition device, applied to a second network element, characterized in that: include: A second receiving module is configured to receive a first message sent by a terminal, where the first message is used to provide task capability information of the terminal, or the first message is used to modify the task capability information of the terminal; The task capability information of the terminal includes at least one of the following: Task capability indication information, used to indicate whether the terminal supports task-related features; Subtask capability information, used to indicate whether the terminal supports the capability of executing the subtask and / or the identification of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the terminal; Activation time information, used to indicate the time period during which the terminal supports execution of the subtask; Template download capability information is used to indicate whether the terminal supports template downloading.

25. The device according to claim 24, characterized in that The device further comprises: The second sending module is configured to send a first response message to the terminal, where the first response message carries the task capability information of the network side device, or the first response message indicates a modification result of the task capability information.

26. The device according to claim 25, characterized in that The device further comprises: The query module is used to query the task capability information of the network side device from the third network element.

27. The device according to claim 25 or 26, characterized in that The task capability information of the network-side device includes at least one of the following: Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities; Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device; The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

28. The device according to claim 25, characterized in that The device further comprises: The third sending module is configured to send the modified task capability information of the terminal to the first network element.

29. The device according to claim 25, characterized in that The device further comprises: A third receiving module is configured to receive a second request message sent by the first network element, where the second request message is used to request task capability information of the terminal; A third message is sent to the first network element, where the third message carries the task capability information of the terminal.

30. The device according to claim 28 or 29, characterized in that The first network element is a network element that supports splitting a target task into one or more target subtasks; the second network element is a core network element.

31. A terminal capability acquisition device, applied to a first network element, characterized in that: include: a fourth receiving module, configured to receive a first message sent by a terminal or a third message sent by a second network element; wherein the first message or the third message is used to provide task capability information of the terminal; The task capability information of the terminal includes at least one of the following: Task capability indication information, used to indicate whether the terminal supports task-related features; Subtask capability information, used to indicate whether the terminal supports the capability of executing the subtask and / or the identification of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the terminal; Activation time information, used to indicate the time period during which the terminal supports execution of the subtask; Template download capability information is used to indicate whether the terminal supports template downloading.

32. The device according to claim 31, characterized in that The first network element is a network element that supports splitting a target task into one or more target subtasks; the second network element is a core network element.

33. The device according to claim 31, characterized in that The device further comprises: The fourth sending module is used to send a first response message to the terminal, where the first response message carries task capability information of the network side device.

34. The device according to claim 33, characterized in that The task capability information of the network-side device includes at least one of the following: Task capability indication information, used to indicate whether the network-side device supports task-based management capabilities; Subtask capability information, used to indicate whether the network-side device supports the ability to perform the subtask and / or the identifier of the supported subtask; Subtask template information, used to indicate the type of subtask templates and / or the content of the task templates supported by the network-side device; The activation time information is used to indicate the time period during which the network-side device supports the execution of the subtask.

35. The device according to claim 31, characterized in that The device further comprises: The fifth sending module is used to send a second request message to the second network element, where the second request message is used to request task capability information of the terminal.

36. The device according to claim 31, characterized in that The device further comprises: The fifth receiving module is configured to receive the modified task capability information of the terminal sent by the second network element.

37. A terminal, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the terminal capability registration method according to any one of claims 1 to 5 are implemented.

38. A network side device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the method implements the steps of the terminal capability acquisition method as described in any one of claims 6 to 12, or implements the steps of the terminal capability acquisition method as described in any one of claims 13 to 18.

39. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the steps of the terminal capability registration method as described in any one of claims 1 to 5, or implements the steps of the terminal capability acquisition method as described in any one of claims 6 to 12, or implements the steps of the terminal capability acquisition method as described in any one of claims 13 to 18.

40. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the steps of the terminal capability registration method according to any one of claims 1 to 5, or implement the steps of the terminal capability acquisition method according to any one of claims 6 to 12, or implement the steps of the terminal capability acquisition method according to any one of claims 13 to 18.

Images