Network capability acquisition and registration method, device and equipment

Abstract

Disclosed are a network capability acquisition and registration method, apparatus and device, the network capability acquisition method comprising: a first network element receiving first information sent by a second network element or receiving second information sent by a third network element; the first information is used for indicating at least one third network element meeting the target capability, and the second information is used for indicating task capability information of the third network element; the task capability information comprises at least one of the following items: task capability indication information used for indicating whether task-based management capability is supported or not; the subtask capability information is used for indicating whether the capability of executing the subtask is supported or not and / or the identifier of the supported subtask; the supported subtask template information is used for indicating the type of the supported subtask template and / or the content of the task template; the activation time information is used for representing that execution of the subtask is supported in the first time period; the maximum number of supported subtask services; and the maximum terminal service quantity is supported.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a method, device and equipment for acquiring and registering network capabilities. 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 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. However, existing technologies do not support the registration of task-related capabilities within the network, making task-centric management impossible. Summary of the Invention

[0004] The embodiments of the present application provide a network capability acquisition and registration method, apparatus, and device for solving the problem that the existing technology cannot achieve task-centric management.

[0005] In a first aspect, a network capability acquisition method is provided, which is performed by a first network element. The method includes:

[0006] The first network element receives first information sent by the second network element or receives second information sent by the third network element; the first information is used to indicate at least one third network element that meets the target capability, and the second information is used to indicate task capability information of the third network element;

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

[0008] Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0009] Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks;

[0010] Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates;

[0011] Activation time information, used to represent support for executing the subtask within the first time period;

[0012] The maximum number of subtask services supported;

[0013] The maximum number of terminal services supported;

[0014] The first information is determined by the second network element based on the third information sent by the third network element. The first network element is a network element that supports decomposing the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks.

[0015] In a second aspect, a network capability acquisition method is provided, which is performed by a second network element. The method includes:

[0016] The second network element receives a request message sent by the first network element, where the request message is used to request a query for a third network element that meets the target capability;

[0017] The second network element sends the first information to the first network element;

[0018] The first information is used to indicate at least one third network element that meets the target capability, the first information is determined based on third information sent by the third network element, and the third information is used to indicate task capability information of the third network element; the first network element is a network element that supports decomposing the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks;

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

[0020] Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0021] Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks;

[0022] Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates;

[0023] Activation time information, used to represent support for executing the subtask within the first time period;

[0024] The maximum number of subtask services supported;

[0025] The maximum number of terminal services supported.

[0026] In a third aspect, a network capability registration method is provided, which is performed by a third network element. The method includes:

[0027] The third network element sends the second information to the first network element or sends the third information to the second network element; the second information or the third information is used to indicate the task capability information of the third network element;

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

[0029] Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0030] Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks;

[0031] Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates;

[0032] Activation time information, used to represent support for executing the subtask within the first time period;

[0033] The maximum number of subtask services supported;

[0034] The maximum number of terminal services supported;

[0035] The first network element is a network element that supports splitting a target task into one or more target subtasks; and the third network element is a network element that supports executing target subtasks.

[0036] In a fourth aspect, a network capability acquisition device is provided, applied to a first network element, the device comprising:

[0037] A first receiving module is configured to receive first information sent by a second network element or second information sent by a third network element; the first information is used to indicate at least one third network element that meets the target capability, and the second information is used to indicate task capability information of the third network element;

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

[0039] Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0040] Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks;

[0041] Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates;

[0042] Activation time information, used to represent support for executing the subtask within the first time period;

[0043] The maximum number of subtask services supported;

[0044] The maximum number of terminal services supported;

[0045] The first information is determined by the second network element based on the third information sent by the third network element. The first network element is a network element that supports decomposing the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks.

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

[0047] A third receiving module is configured to receive a request message sent by the first network element, wherein the request message is used to request a query for a third network element that meets the target capability;

[0048] A fourth sending module, configured to send the first information to the first network element;

[0049] The first information is used to indicate at least one third network element that meets the target capability, the first information is determined based on third information sent by the third network element, and the third information is used to indicate task capability information of the third network element; the first network element is a network element that supports decomposing the target task into one or more target subtasks; the third network element is a network element that supports executing the target subtasks; and the task capability information includes at least one of the following:

[0050] Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0051] Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks;

[0052] Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates;

[0053] Activation time information, used to represent support for executing the subtask within the first time period;

[0054] The maximum number of subtask services supported;

[0055] The maximum number of terminal services supported.

[0056] In a sixth aspect, a network capability registration device is provided, which is applied to a third network element, and the device includes:

[0057] a seventh sending module, configured to send second information to the first network element or send third information to the second network element; the second information or the third information is used to indicate task capability information of the third network element;

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

[0059] Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0060] Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks;

[0061] Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates;

[0062] Activation time information, used to represent support for executing the subtask within the first time period;

[0063] The maximum number of subtask services supported;

[0064] The maximum number of terminal services supported;

[0065] The first network element is a network element that supports splitting a target task into one or more target subtasks; and the third network element is a network element that supports executing target subtasks.

[0066] In the seventh 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 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.

[0067] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein, when the network side device is a first network element, the processor is used to: receive first information sent by a second network element or receive second information sent by a third network element; the first information is used to indicate at least one third network element that meets the target capability, and the second information is used to indicate the task capability information of the third network element; when the network side device is a second network element, the processor is used to: receive a request message sent by the first network element, and the request message is used to request a query for a third network element that meets the target capability; the second network element sends the first information to the first network element; when the network side device is a third network element, the communication interface is used to send the second information to the first network element or send the third information to the second network element; the second information or the third information is used to indicate the task capability information of the third network element.

[0068] In the ninth 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.

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

[0070] In the eleventh aspect, a chip is provided, 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 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.

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

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

[0073] In an embodiment of the present application, the first network element receives the first information sent by the second network element or receives the second information sent by the third network element. The first information can indicate at least one third network element that meets the target capability; the second information is used to indicate the task capability of the third network element, so that the first network element can determine the task capability of each third network element based on the first information or the second information, and thus can select a suitable third network element to perform the subtask in the subsequent task disassembly and subtask selection based on the task capability information of each network element. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0075] Figure 2 This is one of the flow charts of the network capability acquisition method according to an embodiment of the present application;

[0076] Figure 3 This is the second flow chart of the network capability acquisition method according to an embodiment of the present application;

[0077] Figure 4 This is the third flow chart of the network capability acquisition method according to an embodiment of the present application;

[0078] Figure 5This is the fourth flow chart of the network capability acquisition method according to an embodiment of the present application;

[0079] Figure 6 Schematic diagram of the network capability registration method according to an embodiment of the present application;

[0080] Figure 7 This is one of the structural diagrams of the network capability acquisition device according to an embodiment of the present application;

[0081] Figure 8 This is the second structural diagram of the network capability acquisition device according to an embodiment of the present application;

[0082] Figure 9 is a schematic structural diagram of a network capability registration device according to an embodiment of the present application;

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

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

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

[0086] 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 the number of objects is not limited. 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.

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

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

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

[0090] 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 service 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 ( 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.

[0091] 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:

[0092] 1. Mission: A comprehensive service (collection of services) 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.

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

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

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

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

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

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

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

[0100] The following, in conjunction with the accompanying drawings, describes in detail some embodiments and their application scenarios the network capability acquisition and registration methods, devices, and equipment provided by the embodiments of the present application.

[0101] like Figure 2 As shown, an embodiment of the present application provides a network capability acquisition method, which is performed by a first network element, and the method includes:

[0102] Step 201: A first network element receives first information sent by a second network element or receives second information sent by a third network element; the first information is used to indicate at least one third network element that meets the target capability, and the second information is used to indicate task capability information of the third network element;

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

[0104] 1) Task capability indication information (Task indication), used to indicate whether task-based management capabilities are supported;

[0105] Optionally, the task capability indication information can be further understood as a network element having the ability to receive task requests, understand and translate tasks, split tasks into one or more subtasks, and provide lifecycle management for task completion, which may include one or more of these capabilities.

[0106] 2) Sub-task capability information (Sub-Task capability), used to indicate whether the ability to perform subtasks is supported and / or the identification of supported subtasks; the subtask capability information can indicate the type of subtasks that the third network element can support, such as: communication, computing, perception, AI, etc.

[0107] 3) Supported subtask template information (Template capability), used to indicate the type of supported subtask templates and / or the content of the task template; the supported subtask template information can indicate the subtask templates supported by the third network element, and can include the identification of the supported subtask (or task) template and / or the content of the supported subtask (or task) template.

[0108] Optionally, the subtask template information may include but is not limited to: task description, task quality of experience (QoE) description, task strategy / QoS description, and at least one of task parameters. The role of the subtask template information is to enable the first network element and the third network element to have a clear and definite understanding of a task, such as what kind of QoS is required, and what is the process and result of this task.

[0109] 4) Activation time information (Activity period), used to characterize support for executing subtasks within the first time period; the activation time information can indicate the time period during which the third network element can provide services based on task management capabilities, and during this time period the third network element can provide corresponding services.

[0110] 5) Maximum number of sub-task services supported: used to indicate the maximum number of sub-task services that the third network element can simultaneously serve.

[0111] 6) Maximum number of terminal services supported; used to indicate the number of terminals that the third network element can serve simultaneously.

[0112] The first information is determined by the second network element based on third information sent by the third network element, wherein the first network element is a network element that supports splitting the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks. Optionally, the third information is used to indicate task capability information of the third network element.

[0113] In this embodiment, the target task may be a task requested by a terminal to a network device. For example, the terminal requests a task from the 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 task management function (TM).

[0114] The second network element is a core network element for storing network element information. The second network element is, for example, a Network Repository Function (NRF).

[0115] The third network element is a network element that supports the execution of the target subtask, that is, the third network element is an execution node for executing the subtask obtained by disassembling the first network element. The third network element can also be called a subtask execution node. The third network element can be a network element or a locally (co-located) deployed module.

[0116] The first network element decomposes the target task to obtain multiple subtasks, and the first network element can select one or more third network elements to perform the decomposed subtasks based on the task capabilities of each third network element. It should be noted that a third network element can support the execution of one or more subtasks. The first network element can select a third network element to perform a subtask, or select a third network element to perform multiple subtasks that it can support. For example: the target subtasks obtained by the first network element after decomposing the target task include: communication tasks, perception tasks, and computing tasks. For example, the third network elements are: network element 1 supports the execution of communication tasks, network element 2 supports the execution of perception tasks, and network element 3 supports the execution of computing tasks and perception tasks. Then, the first network element can select network element 1 to perform the decomposed communication task, select network element 2 to perform the decomposed perception task, and select network element 3 to perform the decomposed computing task; or, the first network element can select network element 1 to perform the decomposed communication task, and select network element 3 to perform the decomposed perception task and computing task.

[0117] Optionally, the subtasks include at least one of the following types: a perception subtask, a computing subtask, an artificial intelligence (AI) subtask, a data subtask, a positioning subtask, a communication subtask, and an 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, and communication subtasks. The computing subtasks include AI computing tasks and non-AI computing tasks; the information processing subtasks include positioning information processing and synaesthesia information processing; and the immersive subtasks include extended reality (XR) tasks and virtual reality (VR) tasks.

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

[0119] The third network element may be, for example, a data resource management unit, an algorithm management unit, a computing resource management unit, an AMF, an SMF, etc. The first network element, the second network element, and the third network element may be core network elements. It should be noted that the embodiments of the present application do not limit the specific names of the first network element, the second network element, and the third network element.

[0120] After the first network element decomposes the target task into one or more target subtasks, it can select a suitable subtask execution node to execute the corresponding subtask. Therefore, the first network element needs to know which subtask execution nodes support task-centric management. The third network element can send third information related to its own task capability to the second network element, and the second network element determines the first information based on the third information. The second network element provides the first information to the first network element, so that the first network element can know the various subtask execution nodes that meet the target capability and the corresponding task capabilities; or, the third network element can directly provide its own task capability information to the first network element. After determining the task capability information of each third network element, the first network element can select a suitable third network element to execute the subtask according to the task capability of each network element after the task is decomposed.

[0121] In an embodiment of the present application, a first network element receives first information sent by a second network element or receives second information sent by a third network element, and the first information can indicate at least one third network element that meets the target capability; the second information is used to indicate the task capability of the third network element, so that the first network element can determine the task capability of each third network element based on the first information or the second information, and thus can select a suitable third network element to perform the subtask in the subsequent task disassembly and subtask selection based on the task capability information of each network element.

[0122] Optionally, the target capability includes at least one of the following:

[0123] Target task capability, where the target task capability may be a task-based management capability; the first information may indicate a third network element that supports the target task capability (such as supporting the task-based management capability);

[0124] Target subtask capability, such as communication capability, computing capability, perception capability, AI capability, etc.; the first information may indicate a third network element that supports the target subtask capability;

[0125] A capability of supporting a target subtask template, where the first information may indicate a third network element that supports the target subtask template; a capability of supporting task-based management at a target activation time, where the first information may indicate a third network element that supports the capability of supporting task-based management at the activation time;

[0126] a maximum number of subtask services, wherein the first information may indicate a third network element that supports the maximum number of subtask services;

[0127] The maximum number of terminal services, the first information may indicate a third network element that supports the maximum number of terminal services.

[0128] As an optional embodiment, before receiving the first information sent by the second network element, the method further includes:

[0129] A request message is sent to the second network element, where the request message is used to request a query for a third network element that meets the target capability.

[0130] In this embodiment, the first network element may send a request message to the second network element to request the second network element to query information about a third network element. After receiving the request message, the second network element queries for a third network element that meets the requirements of the request message and replies to the first network element with the relevant information about the queried third network element. Optionally, the request message may be a discovery request message.

[0131] Optionally, the request message carries at least one of the following information:

[0132] (1) Identification of the first network element; for example, the ID of the first network element, the address of the first network element, etc.;

[0133] (2) a message type identifier of the request message; the message type identifier is used to indicate that the request message is used to query the task capability of the third network element;

[0134] (3) Target task capability; used to indicate a request to query a third network element that supports task-based management, i.e., the first network element requests the second network element to query a subtask execution node that can comply with task-based management, or the first network element requests the second network element to query a subtask execution node that supports task-based management capabilities;

[0135] (4) Target sub-task capability (required sub-task capability), which is used to indicate a request to query a third network element that supports the target sub-task capability; that is, the first network element requests the second network element to query a sub-task execution node that supports the target sub-task capability, such as communication capability, computing capability, perception capability, AI capability, etc.

[0136] (5) Target subtask template (required Template capability), used to indicate a request to query a third network element that supports the target subtask template; that is, the first network element requests the second network element to query a subtask execution node that supports the target subtask template;

[0137] (6) Activation period (required activity period), which indicates a request to query a third network element that supports the execution of the subtask within the activation period; the first network element requests the second network element to query a network element that can provide the task-based management subtask service within the activation period;

[0138] (7) Maximum number of subtask services, used to indicate a request to query a third network element that supports the maximum number of subtask services; the first network element requests the second network element to query a subtask execution node that can meet the maximum number of subtask services required;

[0139] (8) Maximum terminal service quantity, used to indicate a request to query a third network element that supports the maximum terminal service quantity; the first network element requests the second network element to query a subtask execution node that can meet the maximum terminal service quantity requirement.

[0140] In this embodiment, after receiving the request message, the second network element searches for a third network element that meets at least one of the above requirements, and replies relevant information of the found third network element to the first network element.

[0141] As an optional embodiment, the first information includes at least one of the following:

[0142] (A) A message type identifier of the first information; used to indicate that the first information is a task capability reply message.

[0143] (B) one or more task capability lists; optionally, the task capability list is a task capability list corresponding to a third network element that meets the target capability.

[0144] The task capability list includes at least one of the following information:

[0145] b1) an identifier of a third network element; used to indicate an identifier of a third network element that meets the target capability and is queried by the second network element, such as an ID or address of the third network element.

[0146] b2) Task capability indication information (Task indication) of the third network element, used to indicate whether task-based management capability is supported; that is, to indicate whether the third network element supports task-based management capability.

[0147] b3) Sub-Task capability information of the third network element, which is used to indicate whether the ability to perform subtasks and / or the identification of supported subtasks is supported; that is, it indicates which subtasks the third network element supports, such as communication, computing, perception, AI, etc.

[0148] b4) subtask template information supported by the third network element (Template capability), used to indicate the type of supported subtask templates and / or the content of the task template;

[0149] Among them, the subtask template information refers to the information used to indicate the requester or TM's requirements for the subtask. The subtask template information may include but is not limited to at least one of the task description, task QoE description, task policy / QoS description, and task parameters. The role of the subtask template information is to enable the subtask executor (i.e., the third network element) and the TM (the first network element) to have a clear and definite understanding of a task, such as what kind of QoS is required, and what the process and results of this task are.

[0150] b5) Activation time information (Activity period) of the third network element, used to characterize support for executing the subtask within the second time period; that is, indicating the time period in which the third network element can provide task-based management capabilities, and the third network element can provide task-based services within the indicated time period.

[0151] b6) Maximum number of sub-tasks supported by the third network element: used to indicate the maximum number of sub-tasks that the third network element can serve simultaneously.

[0152] b7) The maximum number of terminal services supported by the third network element is used to indicate the maximum number of terminals that the third network element can serve simultaneously.

[0153] Optionally, the first network element may also perform information interaction with the third network element based on the identifier of the third network element to obtain the task capability information of the third network element.

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

[0155] Sending fourth information to the second network element, where the fourth information includes at least one of the following:

[0156] (a) Identification of the first network element; for example, the ID, IP address, etc. of the first network element.

[0157] (b) a message type identifier of the first information; used to indicate the message type of the fourth information, for example, indicating that the fourth information is the task capability registration information of the first network element.

[0158] (c) Task capability indication information (Task indication) of the first network element, used to indicate whether task-based management capability is supported; that is, to indicate whether the first network element supports task-centric management capability.

[0159] (d) Sub-task capability information (Sub-Task capability) of the first network element, used to indicate whether the ability to manage subtasks is supported and / or the identification of subtasks supported for management; the subtasks include: communication, computing, perception, AI, etc.

[0160] (e) subtask template information (Template capability) supported by the first network element, used to indicate the type of subtask template supported for management and / or the content of the task template;

[0161] (f) Activation period information (Activity period) of the first network element, used to indicate the ability to support task-based management within a third time period; that is, to indicate that the first network element supports task-based management within the third time period.

[0162] (g) The maximum number of task services supported by the first network element; used to indicate the maximum number of tasks that the first network element can serve simultaneously.

[0163] (h) The maximum number of terminal services supported by the first network element; used to indicate the maximum number of terminals that the first network element can serve simultaneously.

[0164] In this embodiment, the fourth information may be sent by the first network element to the second network element through a registration message, that is, the first network element registers the task capability with the second network element.

[0165] Optionally, the method further includes:

[0166] A first response message sent by the second network element is received, where the first response message is used to indicate that the first network element has been successfully registered or failed to be registered.

[0167] In this embodiment, after receiving the fourth information sent by the first network element, the second network element may reply to the first network element with a response message, where the response message carries indication information of whether the registration of the first network element is successful or unsuccessful.

[0168] The following example illustrates a process in which a first network element receives first information sent by a second network element and obtains at least one third network element that meets the target capability based on the first information.

[0169] like Figure 3 As shown, the first network element is TM, the second network element is NRF, and the third network element includes: a data resource management unit, an algorithm resource management unit, and a computing resource management unit. The first network element receives the first information sent by the second network element, and the implementation process of obtaining the third network element that meets the target capability based on the first information includes:

[0170] Step 31 to step 32: The third network element registers task capabilities with the second network element.

[0171] Specifically, in step 31a, the data resource management unit sends a capability registration message to the NRF, which carries at least one of the following:

[0172] Identification of the data resource management unit; for example, the address and ID of the data resource management unit;

[0173] Message type identifier; used to indicate whether the message is a task capability registration message or a resource capability registration message;

[0174] Task management function indication information, used to indicate whether the data resource management unit supports task-based management capabilities;

[0175] Subtask capability information, used to indicate whether the data resource management unit supports the ability to perform subtasks and / or the identification of supported subtasks; supported subtasks include communication, computing, perception, AI, etc.;

[0176] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the data resource management unit;

[0177] Activation time information, used to indicate a time period during which the data resource management unit can provide task-based management capabilities, and the data resource management unit can execute the subtask within the second time period;

[0178] Maximum number of subtask services; used to indicate the maximum number of subtasks that the data resource management unit can serve simultaneously;

[0179] Maximum number of terminals that can be served simultaneously by the data resource management unit.

[0180] Step 32a: The NRF sends a response message to the data resource management unit. The response message is a capability registration reply message of the data resource management unit. The response message may carry indication information of whether the data resource management unit has successfully registered or failed.

[0181] Steps 31b and 32b are the process of the algorithm resource management unit registering task capabilities with the NRF. Steps 31c and 32c are the process of the computing power resource management unit registering task capabilities with the NRF. The registration process is similar to the above steps 31a and 32a and will not be repeated here.

[0182] Step 33 (optional): The TM sends a fourth message to the NRF. The fourth message may be a capability registration message of the TM. The fourth message includes at least one of the following:

[0183] TM identification; such as TM ID, address, etc.;

[0184] A message type identifier of the fourth information; used to indicate that the fourth information is a task capability registration message;

[0185] TM task capability indication information, used to indicate whether the TM supports task-based management capabilities;

[0186] TM subtask capability information, indicating whether the TM supports the ability to manage subtasks and / or the identifiers of the subtasks it supports; the subtasks may include communication, computing, perception, AI, etc.

[0187] The subtask template information supported by the TM is used to indicate the type of subtask templates and / or the content of task templates that the TM supports management;

[0188] The activation time information of the TM is the service period during which the TM can provide task-centric management, and is used to characterize the TM's ability to support task-based management within the third time period;

[0189] The maximum number of task services supported by TM;

[0190] The maximum number of terminal services supported by TM.

[0191] Step 34 (optional): The NRF sends a response message to the TM. The response message may be a capability registration reply message of the TM. The response message may carry indication information of whether the TM registration is successful or failed.

[0192] Step 35: The TM sends a request message to the NRF. The request message may be a capability query request message. The request message may include at least one of the following:

[0193] TM identification, such as TM ID, TM address, etc.;

[0194] The message type identifier of the request message; used to indicate that the request message is a task capability query message;

[0195] Target task capability; used to indicate a request to query a third network element that supports task-based management;

[0196] Target subtask capability, used to indicate a request to query a third network element that supports the target subtask capability;

[0197] The target subtask template is used to indicate a request to query a third network element that supports the target subtask template; the activation time is used to indicate a request to query a third network element that supports executing the subtask within the activation time;

[0198] The maximum number of subtask services is used to indicate a request to query a third network element that supports the maximum number of subtask services;

[0199] The maximum number of terminal services is used to indicate a third network element that requests a query that supports the maximum number of terminal services.

[0200] Step 36: The NRF sends a first message to the TM. The first message is a reply message to the capability query request. The first message may include at least one of the following:

[0201] A: Message type identifier of the first information; used to indicate that the first information is a reply message to a task capability query request.

[0202] B: a list of one or more mission capabilities corresponding to the third network element that meets the target capability;

[0203] The task capability list includes at least one of the following information:

[0204] The identifier of the third network element;

[0205] Task capability indication information of the third network element, used to indicate whether task-based management capability is supported;

[0206] Subtask capability information of the third network element, used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask;

[0207] The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template;

[0208] The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period;

[0209] The maximum number of subtask services supported by the third network element;

[0210] The maximum number of terminal services supported by the third network element.

[0211] In this embodiment, the third network element registers its task capability with the NRF, and the TM queries the NRF for information about the third network element, thereby obtaining the task capability information of the third network element that meets the target task requirements. It can select the appropriate third network element to perform the subtask in the subsequent task decomposition and subtask selection based on the task capability information of each third network element.

[0212] As an optional embodiment, the second information includes at least one of the following:

[0213] 1) Identification of the third network element; for example, the ID, address, etc. of the third network element.

[0214] 2) A message type identifier of the second information; for example, indicating that the second information is a task capability registration message of the third network element or a resource capability registration message of the third network element.

[0215] 3) Task capability indication information (Task indication) of the third network element, used to indicate whether task-based management capability is supported;

[0216] 4) Sub-task capability information (Sub-Task capability) of the third network element, which is used to indicate whether the ability to perform subtasks and / or the identification of supported subtasks is supported; that is, it indicates which subtasks the third network element supports, such as communication, computing, perception, AI, etc.

[0217] 5) subtask template information (Template capability) supported by the third network element, used to indicate the type of supported subtask templates and / or content of task templates;

[0218] 6) The activation time information (Activity period) of the third network element is used to characterize the support for executing the subtask within the second time period; that is, the time period indicating that the third network element can provide task-based management capabilities, and the third network element can provide task-based services within the indicated time period.

[0219] 7) Maximum number of sub-task services supported by the third network element (Maximum number of sub-task); used to indicate the maximum number of sub-tasks that the third network element can serve simultaneously.

[0220] 8) The maximum number of terminal services supported by the third network element; used to indicate the maximum number of terminals that the third network element can serve simultaneously.

[0221] In this embodiment, the second information may be registration information sent by the third network element to the first network element, that is, the third network element registers its task capability with the first network element, and the first network element may store and manage the task capability of each third network element.

[0222] Optionally, the method further includes:

[0223] A second response message is sent to the third network element, where the second response message is used to indicate that the third network element has been successfully registered or failed to be registered.

[0224] In this embodiment, after receiving the second information sent by the third network element, the second network element may reply a response message to the third network element, where the response message carries indication information of successful or failed registration of the third network element.

[0225] The following example illustrates a process in which the first network element determines the task capability information of the third network element based on the second information sent by the third network element.

[0226] like Figure 4As shown, taking the first network element as a TM and the third network element including: a data resource management unit, an algorithm resource management unit, and a computing power resource management unit as an example for explanation, the implementation process of the first network element determining the task capability information of the third network element according to the second information sent by the third network element includes:

[0227] Step 41 to step 42: The third network element registers task capabilities with the first network element.

[0228] Specifically, in step 41a, the data resource management unit sends a capability registration message to the TM, which carries at least one of the following:

[0229] Identification of the data resource management unit; for example, the address and ID of the data resource management unit;

[0230] Message type identifier; used to indicate whether the message is a task capability registration message or a resource capability registration message;

[0231] Task management function indication information, used to indicate whether the data resource management unit supports task-based management capabilities;

[0232] Subtask capability information, used to indicate whether the data resource management unit supports the ability to perform subtasks and / or the identification of supported subtasks; supported subtasks include communication, computing, perception, AI, etc.;

[0233] Subtask template information, used to indicate the type of subtask templates and / or the content of the task template supported by the data resource management unit;

[0234] Activation time information, used to indicate a time period during which the data resource management unit can provide task-based management capabilities, and the data resource management unit can execute the subtask within the second time period;

[0235] Maximum number of subtask services; used to indicate the maximum number of subtasks that the data resource management unit can serve simultaneously;

[0236] Maximum number of terminals that can be served simultaneously by the data resource management unit.

[0237] Step 42a: The TM sends a response message to the data resource management unit. The response message is a capability registration reply message of the data resource management unit. The response message may carry indication information of whether the data resource management unit has successfully registered or failed.

[0238] Steps 41b and 42b are the process of the algorithm resource management unit registering task capabilities with TM, and steps 41c and 42c are the process of the computing power resource management unit registering task capabilities with TM. The registration process is similar to the above steps 41a and 42a and will not be repeated here.

[0239] In this embodiment, the TM is responsible for storing and maintaining the task capability information of subtask execution nodes. All subtask execution nodes register their task capability information with the TM by default. Subsequently, upon receiving a task request, the TM selects subtask execution nodes by filtering the database for subtask execution nodes that meet the requirements and then decomposing the task into subtasks.

[0240] Optionally, for the above-mentioned embodiments in which the first network element receives first information sent by the second network element and obtains at least one third network element that meets the target capability based on the first information, or in which the first network element receives second information provided by the third network element and determines the task capability information of the third network element based on the second information, subsequent capability updates are supported. For example, the third network element can proactively disable task-based management capabilities, modify supported subtask types, modify supported subtask templates or task templates, modify the activation time for providing task-based management capabilities, etc. The third network element can change its task capabilities to the second network element or the first network element.

[0241] In an embodiment of the present application, a first network element receives first information sent by a second network element or receives second information sent by a third network element, and the first information can indicate at least one third network element that meets the target capability; the second information is used to indicate the task capability of the third network element, so that the first network element can determine the task capability of each third network element based on the first information or the second information, and thus can select a suitable third network element to perform the subtask in the subsequent task disassembly and subtask selection based on the task capability information of each network element.

[0242] like Figure 5 As shown, the embodiment of the present application further provides a network capability acquisition method, which is performed by a second network element, and the method includes:

[0243] Step 501: A second network element receives a request message sent by a first network element, where the request message is used to request a third network element that meets target capabilities.

[0244] Step 502: The second network element sends first information to the first network element;

[0245] The first information is used to indicate at least one third network element that meets the target capability, the first information is determined based on third information sent by the third network element, and the third information is used to indicate task capability information of the third network element; the first network element is a network element that supports decomposing the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks;

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

[0247] 1) Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0248] Optionally, the task capability indication information can be further understood as a network element having the ability to receive task requests, understand and translate tasks, split tasks into one or more subtasks, and provide lifecycle management for task completion, which may include one or more of these capabilities.

[0249] 2) Subtask capability information, used to indicate whether the ability to perform subtasks is supported and / or the identification of supported subtasks; the subtask capability information can indicate the type of subtasks that the third network element can support, such as: communication, computing, perception, AI, etc.

[0250] 3) Supported subtask template information, used to indicate the type of supported subtask templates and the content of the task template; the supported subtask template information can indicate the subtask templates supported by the third network element, and can include the identification of the supported subtask (or task) template and / or the content of the supported subtask (or task) template.

[0251] Optionally, the 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 role of the subtask template information is to enable the first network element and the third network element to have a clear and definite understanding of a task, such as what kind of QoS is required, and what is the process and result of this task.

[0252] 4) Activation time information, used to characterize support for executing the subtask within the first time period; the activation time information can indicate the time period in which the third network element can provide a service based on the task management capability, and the third network element can provide the corresponding service within this time period.

[0253] 5) Maximum number of subtask services supported; used to indicate the maximum number of subtask services that the third network element can serve simultaneously.

[0254] 6) Maximum number of terminal services supported; used to indicate the number of terminals that the third network element can serve simultaneously.

[0255] In this embodiment, the request message may be a discovery request message. The first network element may send a request message to the second network element to request the second network element to query information about a third network element. After receiving the request message, the second network element queries for a third network element that meets the requirements of the request message and replies to the first network element with the relevant information about the queried third network element.

[0256] The third information may be registration information sent by the third network element to the second network element, used to register the task capabilities of the third network element. The second network element determines the first information based on the registration information of the third network element, where the first information may indicate the third network element that meets the target capabilities. The second network element sends the first information to the first network element.

[0257] The first network element is a network element that supports decomposing a target task into one or more target subtasks; the third network element is a network element that supports executing the target subtasks. The first network element may be a Task Management function (TM), which may support task translation, task decomposition, subtask function selection, and collaboration between subtasks.

[0258] The third network element may be, for example, a data resource management unit, an algorithm management unit, a computing resource management unit, an AMF, an SMF, or the like. The second network element is a core network element for storing network element information, and the second network element may be, for example, an NRF. The first network element, the second network element, and the third network element may be core network elements. It should be noted that the specific names of the first network element, the second network element, and the third network element are not limited in this embodiment of the present application.

[0259] After the second network element provides the first information to the first network element, the first network element can obtain relevant information of each third network element that meets the target capability based on the first information, and can select appropriate network elements to perform subtasks based on the task capabilities of each network element after task decomposition.

[0260] In an embodiment of the present application, a first network element sends a request message to a second network element, requesting a query for a third network element that meets the target capability. The second network element can determine first information based on third information provided by the third network element and send the first information to the first network element. The first information can indicate relevant information about each third network element that meets the target capability, enabling the first network element to select an appropriate third network element to perform the subtask during subsequent task decomposition and subtask selection based on the task capability information of each network element.

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

[0262] Receive third information sent by the third network element, where the third information includes at least one of the following:

[0263] (1) Identification of the third network element; for example, the ID, address, etc. of the third network element.

[0264] (2) A message type identifier of the third information; used to indicate that the third information is a task capability registration message or a resource capability registration message of a third network element.

[0265] (3) The task capability indication information of the third network element is used to indicate whether the task-based management capability is supported; that is, to indicate whether the third network element supports the task-based management capability.

[0266] (4) Subtask capability information of the third network element, which is used to indicate whether the ability to perform subtasks is supported and / or the identification of supported subtasks; that is, to indicate which subtasks the third network element supports, such as communication, computing, perception, AI, algorithms, computing power, data, etc.

[0267] (5) information about subtask templates supported by the third network element, used to indicate the types of supported subtask templates and / or the contents of task templates;

[0268] (6) The activation time information of the third network element is used to indicate that the subtask can be executed within the second time period; that is, the time period during which the third network element can provide task-based management capabilities and the third network element can provide task-based services within the indicated time period.

[0269] (7) The maximum number of subtask services supported by the third network element; used to indicate the maximum number of subtasks that the third network element can serve simultaneously.

[0270] (8) The maximum number of terminal services supported by the third network element; used to indicate the maximum number of terminals that the third network element can serve simultaneously.

[0271] In this embodiment, the third network element may send the third information via a registration request message to implement task capability registration of the third network element in the second network element.

[0272] Optionally, the method further includes: sending a third response message to the third network element, where the third response message is used to indicate whether the registration of the third network element is successful or failed.

[0273] In this embodiment, after receiving the third information sent by the third network element, the second network element may reply a response message to the third network element, where the response message carries indication information of successful or failed registration of the third network element.

[0274] As an optional embodiment, after receiving the request message sent by the first network element, the method further includes:

[0275] According to the request message and the third information sent by the third network element, a third network element that meets the target capability is queried.

[0276] In this embodiment, the first network element may send a request message to the second network element to request the second network element to query information of the third network element. After receiving the request message, the second network element queries for a third network element that meets the requirements of the request message and replies the relevant information of the queried third network element to the first network element.

[0277] Optionally, the request message carries at least one of the following information:

[0278] (1) Identification of the first network element; for example, the ID of the first network element, the address of the first network element, etc.;

[0279] (2) a message type identifier of the request message; the message type identifier is used to indicate that the request message is used to query the task capability of the third network element;

[0280] (3) Target task capability; used to indicate a request to query a third network element that supports task-based management, i.e., the first network element requests the second network element to query a third network element that supports task-based management;

[0281] (4) The target subtask capability is used to indicate a request to query a third network element that supports the target subtask capability; that is, the first network element requests the second network element to query a subtask execution node that supports the target subtask capability, such as communication capability, computing capability, perception capability, AI capability, etc.

[0282] (5) Target subtask template, used to indicate a request to query a third network element that supports the target subtask template; that is, the first network element requests the second network element to query a subtask execution node that supports the target subtask template;

[0283] (6) Activation time, used to indicate a request to query a third network element that supports executing the subtask within the activation time; the first network element requests the second network element to query a subtask execution node that can provide task-based management capabilities within the activation time;

[0284] (7) Maximum number of subtask services, used to indicate a request to query a third network element that supports the maximum number of subtask services; the first network element requests the second network element to query a subtask execution node that can meet the maximum number of subtask services required;

[0285] (8) Maximum terminal service quantity, used to indicate a request to query a third network element that supports the maximum terminal service quantity; the first network element requests the second network element to query a subtask execution node that can meet the maximum terminal service quantity requirement.

[0286] In this embodiment, after receiving the request message, the second network element searches for a third network element that meets at least one of the above requirements, and replies relevant information of the found third network element to the first network element.

[0287] Optionally, the first information includes at least one of the following:

[0288] (A) A message type identifier of the first information; used to indicate that the first information is a task capability reply message.

[0289] (B) one or more task capability lists; optionally, the task capability list is a task capability list corresponding to a third network element that meets the target capability.

[0290] The task capability list includes at least one of the following information:

[0291] b1) an identifier of a third network element; used to indicate an identifier of a third network element that meets the target capability and is queried by the second network element, such as an ID or address of the third network element.

[0292] b2) Task capability indication information (Task indication) of the third network element, used to indicate whether task-based management capability is supported; that is, to indicate whether the third network element supports task-based management capability.

[0293] b3) Sub-Task capability information of the third network element, which is used to indicate whether the ability to perform subtasks and / or the identification of supported subtasks is supported; that is, it indicates which subtasks the third network element supports, such as communication, computing, perception, AI, algorithms, computing power, data, etc.

[0294] b4) subtask template information supported by the third network element (Template capability), used to indicate the type of supported subtask templates and / or the content of the task template;

[0295] Among them, the subtask template information refers to the information used to indicate the requesting party or TM's requirements for the subtask. The subtask template information may include but is not limited to at least one of the task description, task QoE description, task policy / QoS description, and task parameters. The role of the subtask template information is to enable the subtask executor (i.e., the third network element) and the TM (the first network element) to have a clear and definite understanding of a task.

[0296] b5) Activation time information (Activity period) of the third network element, used to characterize support for executing the subtask within the second time period; that is, indicating the time period in which the third network element can provide task-based management capabilities, and the third network element can provide task-based services within the indicated time period.

[0297] b6) Maximum number of sub-tasks supported by the third network element: used to indicate the maximum number of sub-tasks that the third network element can serve simultaneously.

[0298] b7) The maximum number of terminal services supported by the third network element is used to indicate the maximum number of terminals that the third network element can serve simultaneously.

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

[0300] Receive fourth information sent by the first network element, where the fourth information includes at least one of the following:

[0301] (1) Identification of the first network element; for example, the ID, IP address, etc. of the first network element.

[0302] (2) A message type identifier of the first information; used to indicate the message type of the fourth information, for example, indicating that the fourth information is the task capability registration information of the first network element.

[0303] (3) Task capability indication information of the first network element, used to indicate whether task-based management capability is supported; that is, to indicate whether the first network element supports task-centric management capability.

[0304] (4) Subtask capability information of the first network element, used to indicate whether the capability of managing subtasks is supported and / or the identifier of the subtasks supported for management; the subtasks include, for example, communication, computing, perception, AI, etc.

[0305] (5) subtask template information supported by the first network element, used to indicate the type of subtask template supported for management and / or the content of the task template;

[0306] (6) The activation time information of the first network element is used to indicate that the first network element supports the execution of the subtask within the third time period; that is, it indicates that the first network element supports the execution of the subtask within the third time period.

[0307] (7) The maximum number of task services supported by the first network element; used to indicate the maximum number of tasks that the first network element can serve simultaneously.

[0308] (8) Maximum number of terminal services supported by the first network element; used to indicate the maximum number of terminals that the first network element can serve simultaneously.

[0309] In this embodiment, the fourth information may be sent by the first network element to the second network element through a registration message, that is, the first network element registers the task capability with the second network element.

[0310] Optionally, the method further includes:

[0311] A first response message is sent to the first network element, where the first response message is used to indicate that the first network element has been successfully registered or failed to be registered.

[0312] In this embodiment, after receiving the fourth information sent by the first network element, the second network element may reply to the first network element with a response message, where the response message carries indication information of whether the registration of the first network element is successful or unsuccessful.

[0313] In an embodiment of the present application, the second network element may determine first information based on third information provided by the third network element and send the first information to the first network element. The first information may indicate the task capabilities of each third network element, enabling the first network element to select an appropriate third network element to perform the subtask during subsequent task decomposition and subtask selection based on the task capability information of each network element.

[0314] like Figure 6 As shown, the embodiment of the present application also provides a network capability registration method, which is performed by a third network element, and the method includes:

[0315] Step 601: A third network element sends second information to a first network element or sends third information to a second network element; the second information or the third information is used to indicate task capability information of the third network element;

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

[0317] 1) Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0318] 2) Subtask capability information, used to indicate whether the ability to perform subtasks is supported and / or the identification of supported subtasks; the subtask capability information can indicate the type of subtasks that the third network element can support, such as: communication, computing, perception, AI, etc.

[0319] 3) Supported subtask template information, used to indicate the type of supported subtask templates and / or the content of the task template; the supported subtask template information can indicate the subtask templates supported by the third network element, and can include the identification of the supported subtask (or task) template or the content of the supported subtask (or task) template.

[0320] 4) Activation time information, used to characterize support for executing the subtask within the first time period; the activation time information can indicate the time period in which the third network element can provide a service based on the task management capability, and the third network element can provide the corresponding service within this time period.

[0321] 5) Maximum number of subtask services supported; used to indicate the maximum number of subtask services that the third network element can serve simultaneously.

[0322] 6) Maximum number of terminal services supported; used to indicate the number of terminals that the third network element can serve simultaneously.

[0323] The first network element is a network element that supports splitting a target task into one or more target subtasks; and the third network element is a network element that supports executing target subtasks.

[0324] In this embodiment, the target task may be a task requested by a terminal from a network device. For example, the terminal requests a task from the 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 for storing network element information, such as an NRF.

[0325] The third network element supports executing the target subtask. Examples of the third network element include a data resource management unit, an algorithm management unit, a computing resource management unit, an AMF, and an SMF. The first network element, the second network element, and the third network element may be core network elements. It should be noted that the specific names of the first network element, the second network element, and the third network element are not limited in this embodiment of the application.

[0326] The second information may be registration information of the third network element registering task capabilities with the first network element, and the third information may be registration information of the third network element registering task capabilities with the second network element. The second information and the information carried by the third network element may have the same content.

[0327] In this embodiment, the third network element may directly provide its own task capability information to the first network element, or the third network element may provide its own task capability information to the second network element, and the second network element may determine the first information based on the information sent by the third network element and send it to the first network element. After determining the task capability information of each third network element, the first network element may select an appropriate third network element to perform the subtask based on the task capability of each network element after task decomposition.

[0328] The second information or the third information includes at least one of the following:

[0329] 1) Identification of the third network element; for example, the ID, address, etc. of the third network element.

[0330] 2) A message type identifier of the second information or the third information; for example, indicating that the second information is a task capability registration message of the third network element or a resource capability registration message of the third network element.

[0331] 3) Task management function indication information of the third network element, used to indicate whether task-based management capabilities are supported;

[0332] 4) The subtask capability information of the third network element is used to indicate whether the ability to execute subtasks is supported and / or the identification of supported subtasks; that is, to indicate which subtasks the third network element supports, such as communication, computing, perception, AI, etc.

[0333] 5) information on subtask templates supported by the third network element, used to indicate the types of supported subtask templates and / or content of task templates;

[0334] 6) The activation time information of the third network element is used to indicate that the subtask execution is supported within the second time period; that is, the time period in which the third network element can provide task-based management capabilities, and the third network element can provide task-based services within the indicated time period.

[0335] 7) The maximum number of subtask services supported by the third network element; used to indicate the maximum number of subtasks that the third network element can serve simultaneously.

[0336] 8) The maximum number of terminal services supported by the third network element; used to indicate the maximum number of terminals that the third network element can serve simultaneously.

[0337] Optionally, the method further includes:

[0338] Receive a second response message sent by the first network element or a third response message sent by the second network element, where the second response message or the third response message is used to indicate that the third network element has successfully registered or failed to register.

[0339] In this embodiment, if the third network element sends the second information to the first network element, the first network element may send a response message to the third network element, where the response message indicates that the third network element has successfully registered or failed to register. If the third network element sends the third information to the second network element, the second network element may send a response message to the third network element, where the response message indicates that the third network element has successfully registered or failed to register.

[0340] In an embodiment of the present application, the third network element may directly provide its own task capability information to the first network element, or the third network element may provide its own task capability information to the second network element, and the second network element may determine the first information based on the information sent by the third network element and send it to the first network element. After determining the task capability information of each third network element, the first network element may select an appropriate third network element to perform the subtask based on the task capability of each network element after task decomposition.

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

[0342] like Figure 7 As shown, an embodiment of the present application provides a network capability acquisition device 700, which is applied to a first network element. The device includes:

[0343] A first receiving module 710 is configured to receive first information sent by a second network element or second information sent by a third network element; the first information is used to indicate at least one third network element that meets the target capability, and the second information is used to indicate task capability information of the third network element;

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

[0345] Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0346] Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks;

[0347] Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates;

[0348] Activation time information, used to represent support for executing the subtask within the first time period;

[0349] The maximum number of subtask services supported;

[0350] The maximum number of terminal services supported;

[0351] The first information is determined by the second network element based on the third information sent by the third network element. The first network element is a network element that supports decomposing the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks.

[0352] Optionally, the device further includes:

[0353] The first sending module is configured to send a request message to the second network element, where the request message is used to request a query for a third network element that meets the target capability.

[0354] Optionally, the request message carries at least one of the following information:

[0355] an identifier of the first network element;

[0356] A message type identifier of the request message;

[0357] Target task capability, used to indicate the third network element that supports task-based management;

[0358] Target subtask capability, used to indicate a request to query a third network element that supports the target subtask capability;

[0359] A target subtask template, used to indicate a request to query a third network element that supports the target subtask template;

[0360] An activation time, used to indicate a request to query a third network element that supports execution of the subtask within the activation time;

[0361] The maximum number of subtask services is used to indicate a request to query a third network element that supports the maximum number of subtask services;

[0362] The maximum number of terminal services is used to indicate a third network element that requests a query that supports the maximum number of terminal services.

[0363] Optionally, the first information includes at least one of the following:

[0364] a message type identifier of the first information;

[0365] One or more task capability lists;

[0366] The task capability list includes at least one of the following information:

[0367] The identifier of the third network element;

[0368] Task capability indication information of the third network element, used to indicate whether task-based management capability is supported;

[0369] Subtask capability information of the third network element, used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask;

[0370] The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template;

[0371] The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period;

[0372] The maximum number of subtask services supported by the third network element;

[0373] The maximum number of terminal services supported by the third network element.

[0374] Optionally, the device further includes:

[0375] The second sending module is configured to send fourth information to the second network element, where the fourth information includes at least one of the following:

[0376] an identifier of the first network element;

[0377] a message type identifier of the first information;

[0378] The task capability indication information of the first network element is used to indicate whether task-based management capability is supported;

[0379] The subtask capability information of the first network element is used to indicate whether the capability of managing subtasks is supported and / or identifiers of supported subtasks;

[0380] The subtask template information supported by the first network element is used to indicate the type of subtask templates supported for management and / or the content of the task template;

[0381] activation time information of the first network element, used to indicate support for task-based management capability within a third time period;

[0382] The maximum number of task services supported by the first network element;

[0383] The maximum number of terminal services supported by the first network element.

[0384] Optionally, the device further includes:

[0385] The second receiving module is used to receive a first response message sent by the second network element, where the first response message is used to indicate that the first network element has been successfully registered or failed to be registered.

[0386] Optionally, the second information includes at least one of the following:

[0387] an identifier of the third network element;

[0388] a message type identifier of the second information;

[0389] The task capability indication information of the third network element is used to indicate whether task-based management capability is supported;

[0390] The subtask capability information of the third network element is used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask;

[0391] The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template;

[0392] The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period;

[0393] The maximum number of subtask services supported by the third network element;

[0394] The maximum number of terminal services supported by the third network element.

[0395] Optionally, the device further includes:

[0396] The third sending module is used to send a second response message to the third network element, where the second response message is used to indicate that the registration of the third network element is successful or unsuccessful.

[0397] In an embodiment of the present application, a first network element receives first information sent by a second network element or receives second information sent by a third network element, and the first information can indicate at least one third network element that meets the target capability; the second information is used to indicate the task capability of the third network element, so that the first network element can determine the task capability of each third network element based on the first information or the second information, and thus can select a suitable third network element to perform the subtask in the subsequent task disassembly and subtask selection based on the task capability information of each network element.

[0398] like Figure 8 As shown, the embodiment of the present application further provides a network capability acquisition device 800, which is applied to a second network element, and the device includes:

[0399] A third receiving module 810 is configured to receive a request message sent by the first network element, wherein the request message is used to request a third network element that meets the target capability;

[0400] The fourth sending module 820 is configured to send the first information to the first network element;

[0401] The first information is used to indicate at least one third network element that meets the target capability, the first information is determined based on third information sent by the third network element, and the third information is used to indicate task capability information of the third network element; the first network element is a network element that supports decomposing the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks;

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

[0403] Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0404] Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks;

[0405] Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates;

[0406] Activation time information, used to represent support for executing the subtask within the first time period;

[0407] The maximum number of subtask services supported;

[0408] The maximum number of terminal services supported.

[0409] Optionally, the device further includes:

[0410] a fourth receiving module, configured to receive third information sent by the third network element, where the third information includes at least one of the following:

[0411] an identifier of the third network element;

[0412] a message type identifier of the third information;

[0413] The task capability indication information of the third network element is used to indicate whether task-based management capability is supported;

[0414] The subtask capability information of the third network element is used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask;

[0415] The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template;

[0416] The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period;

[0417] The maximum number of subtask services supported by the third network element;

[0418] The maximum number of terminal services supported by the third network element.

[0419] Optionally, the device further includes:

[0420] The fifth sending module is used to send a third response message to the third network element, where the third response message is used to indicate whether the third network element has been successfully registered or failed to be registered.

[0421] Optionally, the device further includes:

[0422] The query module is used to query the third network element that meets the target capability according to the request message and the third information sent by the third network element.

[0423] Optionally, the request message carries at least one of the following information:

[0424] an identifier of the first network element;

[0425] A message type identifier of the request message;

[0426] Target task capability, used to indicate the third network element that supports task-based management;

[0427] Target subtask capability, used to indicate a request to query a third network element that supports the target subtask capability;

[0428] A target subtask template, used to indicate a request to query a third network element that supports the target subtask template;

[0429] An activation time, used to indicate a request to query a third network element that supports execution of the subtask within the activation time;

[0430] The maximum number of subtask services is used to indicate a request to query a third network element that supports the maximum number of subtask services;

[0431] The maximum number of terminal services is used to indicate a third network element that requests a query that supports the maximum number of terminal services.

[0432] Optionally, the first information includes at least one of the following:

[0433] a message type identifier of the first information;

[0434] One or more task capability lists;

[0435] The task capability list includes at least one of the following information:

[0436] The identifier of the third network element;

[0437] Task capability indication information of the third network element, used to indicate whether task-based management capability is supported;

[0438] Subtask capability information of the third network element, used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask;

[0439] The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template;

[0440] The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period;

[0441] The maximum number of subtask services supported by the third network element;

[0442] The maximum number of terminal services supported by the third network element.

[0443] Optionally, the device further includes:

[0444] a fifth receiving module, configured to receive fourth information sent by the first network element, where the fourth information includes at least one of the following:

[0445] an identifier of the first network element;

[0446] a message type identifier of the first information;

[0447] The task capability indication information of the first network element is used to indicate whether task-based management capability is supported;

[0448] The subtask capability information of the first network element is used to indicate whether the capability of managing a subtask is supported and / or an identifier of the subtask supported for management;

[0449] The subtask template information supported by the first network element is used to indicate the type of subtask templates supported for management and / or the content of the task template;

[0450] activation time information of the first network element, used to indicate support for task-based management capability within a third time period;

[0451] The maximum number of task services supported by the first network element;

[0452] The maximum number of terminal services supported by the first network element.

[0453] Optionally, the device further includes:

[0454] The sixth sending module is used to send a first response message to the first network element, where the first response message is used to indicate whether the first network element has been successfully registered or failed to be registered.

[0455] In an embodiment of the present application, a first network element sends a request message to a second network element, requesting a query for a third network element that meets the target capability. The second network element can determine first information based on third information provided by the third network element and send the first information to the first network element. The first information can indicate relevant information about each third network element that meets the target capability, enabling the first network element to select an appropriate third network element to perform the subtask during subsequent task decomposition and subtask selection based on the task capability information of each network element.

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

[0457] like Figure 9As shown, the embodiment of the present application further provides a network capability registration device 900, which is applied to a third network element, and the device includes:

[0458] The seventh sending module 910 is configured to send second information to the first network element or send third information to the second network element; the second information or the third information is used to indicate task capability information of the third network element;

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

[0460] Task capability indication information, used to indicate whether task-based management capabilities are supported;

[0461] Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks;

[0462] Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates;

[0463] Activation time information, used to represent support for executing the subtask within the first time period;

[0464] The maximum number of subtask services supported;

[0465] The maximum number of terminal services supported;

[0466] The first network element is a network element that supports splitting a target task into one or more target subtasks; and the third network element is a network element that supports executing target subtasks.

[0467] Optionally, the second information or the third information includes at least one of the following:

[0468] an identifier of the third network element;

[0469] a message type identifier of the second information or the third information;

[0470] The task management function indication information of the third network element is used to indicate whether task-based management capability is supported;

[0471] The subtask capability information of the third network element is used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask;

[0472] The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template;

[0473] The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period;

[0474] The maximum number of subtask services supported by the third network element;

[0475] The maximum number of terminal services supported by the third network element.

[0476] Optionally, the device further includes:

[0477] The sixth receiving module is used to receive a second response message sent by the first network element or a third response message sent by the second network element, where the second response message or the third response message is used to indicate that the registration of the third network element is successful or unsuccessful.

[0478] In an embodiment of the present application, the third network element may directly provide its own task capability information to the first network element, or the third network element may provide its own task capability information to the second network element, and the second network element may determine the first information based on the information sent by the third network element and send it to the first network element. After determining the task capability information of each third network element, the first network element may select an appropriate third network element to perform the subtask based on the task capability of each network element after task decomposition.

[0479] The network capability acquisition device or network capability registration 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.

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

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

[0482] The embodiment of the present application further provides a network side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figures 2 to 6 The network side device embodiment corresponds to the above network side device method embodiment, and each implementation process and implementation method of the above method embodiment are applicable to the network side device embodiment and can achieve the same technical effect.

[0483] Specifically, the embodiment of the present application also provides a network side device. Figure 11 As shown, the network side device 1100 includes: a processor 1101, a network interface 1102 and a memory 1103. The network interface 1102 is, for example, a common public radio interface (CPRI).

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

[0485] 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 network capability acquisition method or network capability registration method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

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

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

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

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

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

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

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

[0494] 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 network capability acquisition method, characterized in that: include: The first network element receives the first information sent by the second network element or receives the second information sent by the third network element; The first information is used to indicate at least one third network element that meets the target capability, and the second information is used to indicate task capability information of the third network element; The task capability information includes at least one of the following: Task capability indication information, used to indicate whether task-based management capabilities are supported; Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks; Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates; Activation time information, used to represent support for executing the subtask within the first time period; The maximum number of subtask services supported; The maximum number of terminal services supported; The first information is determined by the second network element based on the third information sent by the third network element. The first network element is a network element that supports decomposing the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks.

2. The method according to claim 1, characterized in that Before receiving the first information sent by the second network element, the method further includes: A request message is sent to the second network element, where the request message is used to request a query for a third network element that meets the target capability.

3. The method according to claim 2, characterized in that The request message carries at least one of the following information: an identifier of the first network element; A message type identifier of the request message; Target task capability, used to indicate the third network element that supports task-based management; Target subtask capability, used to indicate a request to query a third network element that supports the target subtask capability; A target subtask template, used to indicate a request to query a third network element that supports the target subtask template; An activation time, used to indicate a request to query a third network element that supports execution of the subtask within the activation time; The maximum number of subtask services is used to indicate a request to query a third network element that supports the maximum number of subtask services; The maximum number of terminal services is used to indicate a third network element that requests a query that supports the maximum number of terminal services.

4. The method according to claim 1 or 2, characterized in that The first information includes at least one of the following: a message type identifier of the first information; One or more task capability lists; The task capability list includes at least one of the following information: The identifier of the third network element; Task capability indication information of the third network element, used to indicate whether task-based management capability is supported; Subtask capability information of the third network element, used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask; The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template; The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period; The maximum number of subtask services supported by the third network element; The maximum number of terminal services supported by the third network element.

5. The method according to claim 1 or 2, characterized in that The method further comprises: Sending fourth information to the second network element, where the fourth information includes at least one of the following: an identifier of the first network element; a message type identifier of the first information; The task capability indication information of the first network element is used to indicate whether task-based management capability is supported; The subtask capability information of the first network element is used to indicate whether the capability of managing a subtask is supported and / or an identifier of the subtask supported for management; The subtask template information supported by the first network element is used to indicate the type of subtask templates supported for management and / or the content of the task template; activation time information of the first network element, used to indicate support for task-based management capability within a third time period; The maximum number of task services supported by the first network element; The maximum number of terminal services supported by the first network element.

6. The method according to claim 5, characterized in that The method further comprises: A first response message sent by the second network element is received, where the first response message is used to indicate that the first network element has been successfully registered or failed to be registered.

7. The method according to claim 1, characterized in that The second information includes at least one of the following: an identifier of the third network element; a message type identifier of the second information; The task capability indication information of the third network element is used to indicate whether task-based management capability is supported; The subtask capability information of the third network element is used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask; The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template; The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period; The maximum number of subtask services supported by the third network element; The maximum number of terminal services supported by the third network element.

8. The method according to claim 1, characterized in that The method further comprises: A second response message is sent to the third network element, where the second response message is used to indicate that the third network element has been successfully registered or failed to be registered.

9. A network capability acquisition method, characterized in that: include: The second network element receives a request message sent by the first network element, where the request message is used to request a query for a third network element that meets the target capability; The second network element sends the first information to the first network element; The first information is used to indicate at least one third network element that meets the target capability, the first information is determined based on third information sent by the third network element, and the third information is used to indicate task capability information of the third network element; the first network element is a network element that supports decomposing the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks; The task capability information includes at least one of the following: Task capability indication information, used to indicate whether task-based management capabilities are supported; Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks; Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates; Activation time information, used to represent support for executing the subtask within the first time period; The maximum number of subtask services supported; The maximum number of terminal services supported.

10. The method according to claim 9, characterized in that The method further comprises: Receive third information sent by the third network element, where the third information includes at least one of the following: an identifier of the third network element; a message type identifier of the third information; The task capability indication information of the third network element is used to indicate whether task-based management capability is supported; The subtask capability information of the third network element is used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask; The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template; The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period; The maximum number of subtask services supported by the third network element; The maximum number of terminal services supported by the third network element.

11. The method according to claim 10, characterized in that The method further comprises: A third response message is sent to the third network element, where the third response message is used to indicate that the third network element has been successfully registered or failed to be registered.

12. The method according to claim 9 or 10, characterized in that After receiving the request message sent by the first network element, the method further includes: According to the request message and the third information sent by the third network element, a third network element that meets the target capability is queried.

13. The method according to claim 12, characterized in that The request message carries at least one of the following information: an identifier of the first network element; A message type identifier of the request message; Target task capability, used to indicate the third network element that supports task-based management; Target subtask capability, used to indicate a request to query a third network element that supports the target subtask capability; A target subtask template, used to indicate a request to query a third network element that supports the target subtask template; An activation time, used to indicate a request to query a third network element that supports execution of the subtask within the activation time; The maximum number of subtask services is used to indicate a request to query a third network element that supports the maximum number of subtask services; The maximum number of terminal services is used to indicate a third network element that requests a query that supports the maximum number of terminal services.

14. The method according to claim 9, characterized in that The first information includes at least one of the following: a message type identifier of the first information; One or more task capability lists; The task capability list includes at least one of the following information: The identifier of the third network element; Task capability indication information of the third network element, used to indicate whether task-based management capability is supported; Subtask capability information of the third network element, used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask; The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template; The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period; The maximum number of subtask services supported by the third network element; The maximum number of terminal services supported by the third network element.

15. The method according to claim 9 or 12, characterized in that The method further comprises: Receive fourth information sent by the first network element, where the fourth information includes at least one of the following: an identifier of the first network element; a message type identifier of the first information; The task capability indication information of the first network element is used to indicate whether task-based management capability is supported; The subtask capability information of the first network element is used to indicate whether the capability of managing a subtask is supported and / or an identifier of the subtask supported for management; The subtask template information supported by the first network element is used to indicate the type of subtask templates supported for management and / or the content of the task template; activation time information of the first network element, used to indicate support for task-based management capability within a third time period; The maximum number of task services supported by the first network element; The maximum number of terminal services supported by the first network element.

16. The method according to claim 15, characterized in that The method further comprises: A first response message is sent to the first network element, where the first response message is used to indicate that the first network element has been successfully registered or failed to be registered.

17. A network capability registration method, characterized in that: include: The third network element sends the second information to the first network element or sends the third information to the second network element; The second information or the third information is used to indicate task capability information of the third network element; The task capability information includes at least one of the following: Task capability indication information, used to indicate whether task-based management capabilities are supported; Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks; Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates; Activation time information, used to represent support for executing the subtask within the first time period; The maximum number of subtask services supported; The maximum number of terminal services supported; The first network element is a network element that supports splitting a target task into one or more target subtasks; and the third network element is a network element that supports executing target subtasks.

18. The method according to claim 17, characterized in that The second information or the third information includes at least one of the following: an identifier of the third network element; a message type identifier of the second information or the third information; The task management function indication information of the third network element is used to indicate whether task-based management capability is supported; The subtask capability information of the third network element is used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask; The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template; The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period; The maximum number of subtask services supported by the third network element; The maximum number of terminal services supported by the third network element.

19. The method according to claim 17, wherein The method further comprises: Receive a second response message sent by the first network element or a third response message sent by the second network element, where the second response message or the third response message is used to indicate that the third network element has successfully registered or failed to register.

20. A network capability acquisition device, applied to a first network element, characterized in that: include: A first receiving module, configured to receive first information sent by a second network element or receive second information sent by a third network element; The first information is used to indicate at least one third network element that meets the target capability, and the second information is used to indicate task capability information of the third network element; The task capability information includes at least one of the following: Task capability indication information, used to indicate whether task-based management capabilities are supported; Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks; Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates; Activation time information, used to represent support for executing the subtask within the first time period; The maximum number of subtask services supported; The maximum number of terminal services supported; The first information is determined by the second network element based on the third information sent by the third network element. The first network element is a network element that supports decomposing the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks.

21. The device according to claim 20, characterized in that The device further comprises: The first sending module is configured to send a request message to the second network element, where the request message is used to request a query for a third network element that meets the target capability.

22. The device according to claim 21, characterized in that The request message carries at least one of the following information: an identifier of the first network element; A message type identifier of the request message; Target task capability, used to indicate the third network element that supports task-based management; Target subtask capability, used to indicate a request to query a third network element that supports the target subtask capability; A target subtask template, used to indicate a request to query a third network element that supports the target subtask template; An activation time, used to indicate a request to query a third network element that supports execution of the subtask within the activation time; The maximum number of subtask services is used to indicate a request to query a third network element that supports the maximum number of subtask services; The maximum number of terminal services is used to indicate a third network element that requests a query that supports the maximum number of terminal services.

23. The device according to claim 20 or 21, characterized in that The first information includes at least one of the following: a message type identifier of the first information; One or more task capability lists; The task capability list includes at least one of the following information: The identifier of the third network element; Task capability indication information of the third network element, used to indicate whether task-based management capability is supported; Subtask capability information of the third network element, used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask; The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template; The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period; The maximum number of subtask services supported by the third network element; The maximum number of terminal services supported by the third network element.

24. The device according to claim 21, characterized in that The device further comprises: The second sending module is configured to send fourth information to the second network element, where the fourth information includes at least one of the following: an identifier of the first network element; a message type identifier of the first information; The task capability indication information of the first network element is used to indicate whether task-based management capability is supported; The subtask capability information of the first network element is used to indicate whether the capability of managing a subtask is supported and / or an identifier of the subtask supported for management; The subtask template information supported by the first network element is used to indicate the type of subtask templates supported for management and / or the content of the task template; activation time information of the first network element, used to indicate support for task-based management capability within a third time period; The maximum number of task services supported by the first network element; The maximum number of terminal services supported by the first network element.

25. The device according to claim 24, characterized in that The device further comprises: The second receiving module is used to receive a first response message sent by the second network element, where the first response message is used to indicate that the first network element has been successfully registered or failed to be registered.

26. The device according to claim 20, characterized in that The second information includes at least one of the following: an identifier of the third network element; a message type identifier of the second information; The task capability indication information of the third network element is used to indicate whether task-based management capability is supported; The subtask capability information of the third network element is used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask; The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template; The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period; The maximum number of subtask services supported by the third network element; The maximum number of terminal services supported by the third network element.

27. The device according to claim 26, characterized in that The device further comprises: The third sending module is used to send a second response message to the third network element, where the second response message is used to indicate that the registration of the third network element is successful or unsuccessful.

28. A network capability acquisition device, applied to a second network element, characterized in that: include: A third receiving module is configured to receive a request message sent by the first network element, wherein the request message is used to request a query for a third network element that meets the target capability; A fourth sending module, configured to send the first information to the first network element; The first information is used to indicate at least one third network element that meets the target capability, the first information is determined based on third information sent by the third network element, and the third information is used to indicate task capability information of the third network element; the first network element is a network element that supports decomposing the target task into one or more target subtasks; and the third network element is a network element that supports executing the target subtasks; The task capability information includes at least one of the following: Task capability indication information, used to indicate whether task-based management capabilities are supported; Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks; Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates; Activation time information, used to represent support for executing the subtask within the first time period; The maximum number of subtask services supported; The maximum number of terminal services supported.

29. The device according to claim 28, characterized in that The device further comprises: a fourth receiving module, configured to receive third information sent by the third network element, where the third information includes at least one of the following: an identifier of the third network element; a message type identifier of the third information; The task capability indication information of the third network element is used to indicate whether task-based management capability is supported; The subtask capability information of the third network element is used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask; The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template; The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period; The maximum number of subtask services supported by the third network element; The maximum number of terminal services supported by the third network element.

30. The device according to claim 29, characterized in that The device further comprises: The fifth sending module is used to send a third response message to the third network element, where the third response message is used to indicate whether the third network element has been successfully registered or failed to be registered.

31. The device according to claim 28 or 29, characterized in that The device further comprises: The query module is used to query the third network element that meets the target capability according to the request message and the third information sent by the third network element.

32. The device according to claim 31, characterized in that The request message carries at least one of the following information: an identifier of the first network element; A message type identifier of the request message; Target task capability, used to indicate the third network element that supports task-based management; Target subtask capability, used to indicate a request to query a third network element that supports the target subtask capability; A target subtask template, used to indicate a request to query a third network element that supports the target subtask template; An activation time, used to indicate a request to query a third network element that supports execution of the subtask within the activation time; The maximum number of subtask services is used to indicate a request to query a third network element that supports the maximum number of subtask services; The maximum number of terminal services is used to indicate a third network element that requests a query that supports the maximum number of terminal services.

33. The device according to claim 28 or 31, characterized in that The first information includes at least one of the following: a message type identifier of the first information; One or more task capability lists; The task capability list includes at least one of the following information: The identifier of the third network element; Task capability indication information of the third network element, used to indicate whether task-based management capability is supported; Subtask capability information of the third network element, used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask; The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template; The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period; The maximum number of subtask services supported by the third network element; The maximum number of terminal services supported by the third network element.

34. The device according to claim 28 or 31, characterized in that The device further comprises: a fifth receiving module, configured to receive fourth information sent by the first network element, where the fourth information includes at least one of the following: an identifier of the first network element; a message type identifier of the first information; The task capability indication information of the first network element is used to indicate whether task-based management capability is supported; The subtask capability information of the first network element is used to indicate whether the capability of managing a subtask is supported and / or an identifier of the subtask supported for management; The subtask template information supported by the first network element is used to indicate the type of subtask templates supported for management and / or the content of the task template; activation time information of the first network element, used to indicate support for task-based management capability within a third time period; The maximum number of task services supported by the first network element; The maximum number of terminal services supported by the first network element.

35. The device according to claim 34, characterized in that The device further comprises: The sixth sending module is used to send a first response message to the first network element, where the first response message is used to indicate whether the first network element has been successfully registered or failed to be registered.

36. A network capability registration device, applied to a third network element, characterized in that: include: a seventh sending module, configured to send the second information to the first network element or send the third information to the second network element; The second information or the third information is used to indicate task capability information of the third network element; The task capability information includes at least one of the following: Task capability indication information, used to indicate whether task-based management capabilities are supported; Subtask capability information, used to indicate whether the capability to execute the subtask is supported and / or the identification of the supported subtasks; Supported subtask template information, used to indicate the types of supported subtask templates and / or the content of task templates; Activation time information, used to represent support for executing the subtask within the first time period; The maximum number of subtask services supported; The maximum number of terminal services supported; The first network element is a network element that supports splitting a target task into one or more target subtasks; and the third network element is a network element that supports executing target subtasks.

37. The device according to claim 36, characterized in that The second information or the third information includes at least one of the following: an identifier of the third network element; a message type identifier of the second information or the third information; The task management function indication information of the third network element is used to indicate whether task-based management capability is supported; The subtask capability information of the third network element is used to indicate whether the capability of executing the subtask is supported and / or the identifier of the supported subtask; The subtask template information supported by the third network element is used to indicate the type of supported subtask templates and / or the content of the task template; The activation time information of the third network element is used to indicate that it supports the execution of the subtask within the second time period; The maximum number of subtask services supported by the third network element; The maximum number of terminal services supported by the third network element.

38. The device according to claim 36, characterized in that The device further comprises: The sixth receiving module is used to receive a second response message sent by the first network element or a third response message sent by the second network element, where the second response message or the third response message is used to indicate that the registration of the third network element is successful or unsuccessful.

39. 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 network capability acquisition method according to any one of claims 1 to 8, or the steps of the network capability acquisition method according to any one of claims 9 to 16, or the steps of the network capability registration method according to any one of claims 17 to 19.

40. 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 network capability acquisition method as described in any one of claims 1 to 8, or implements the steps of the network capability acquisition method as described in any one of claims 9 to 16, or implements the steps of the network capability registration method as described in any one of claims 17 to 19.

41. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the steps of the network capability acquisition method according to any one of claims 1 to 8, or implement the steps of the network capability acquisition method according to any one of claims 9 to 16, or implement the steps of the network capability registration method according to any one of claims 17 to 19.

Images