WO2025195236A1 - Information monitoring method and apparatus and communication device - Google Patents

Abstract

The present application relates to the technical field of communications, and discloses an information monitoring method and apparatus and a communication device. The information monitoring method in embodiments of the present application comprises: on the basis of a local policy or a first message from a second device, a first device determines whether to monitor a target task or a first sub-task, the first sub-task being a sub-task of the target task, wherein the first message is used for requesting to monitor the target task, or the first message is used for requesting to monitor the first sub-task.

Description

Information monitoring method, device and communication equipment

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Chinese Patent Application No. 202410315604.9 filed in China on March 19, 2024, the entire contents of which are incorporated herein by reference.

Technical Field

The present application belongs to the field of communication technology, and specifically relates to an information monitoring method, device and communication equipment.

Background Art

With the diversification of services, services such as perception, positioning, and artificial intelligence (AI) have emerged. These services are typically data- and compute-intensive, requiring the participation of multiple nodes. For example, a task can be broken down into multiple subtasks, with different nodes performing different subtasks, ultimately completing the task together. During this process, network elements other than the node executing the subtask are unaware of the execution status of the task or subtask.

Summary of the Invention

The embodiments of the present application provide an information monitoring method, apparatus, and communication device, which can solve the problem of not being able to know the execution status of a task or subtask.

In a first aspect, an information monitoring method is provided, which is performed by a first device. The method includes:

The first device determines whether to monitor the target task or the first subtask based on a local policy or a first message from the second device, where the first subtask is a subtask of the target task;

The first message is used to request monitoring of the target task, or the first message is used to request monitoring of the first subtask.

In a second aspect, an information monitoring method is provided, which is performed by a second device. The method includes:

The second device sends a first message to the first device, where the first message is used to request monitoring of a target task, or the first message is used to request monitoring of a first subtask, where the first subtask is a subtask of the target task.

In a third aspect, an information monitoring method is provided, which is performed by a third device. The method includes:

The third device receives a second message from the first device, where the second message is used to request monitoring of a target task or one or more subtasks within the target task, and the third device includes one or more devices that execute one or more subtasks within the target task; or, the second message is used to request monitoring of a first subtask, the third device is a device that executes the first subtask, and the first subtask is a subtask of the target task;

The third device sends a third message to the first device, where the third message is used to provide reply information for monitoring the target task or one or more subtasks in the target task, or the third message is used to provide reply information for monitoring the first subtask.

In a fourth aspect, an information monitoring device is provided, the device comprising:

a processing unit, configured to determine whether to monitor a target task or a first subtask based on a local policy or a first message from a second device, where the first subtask is a subtask of the target task;

The first message is used to request monitoring of the target task, or the first message is used to request monitoring of the first subtask.

In a fifth aspect, an information monitoring device is provided, the device comprising:

The sending unit is configured to send a first message to a first device, where the first message is used to request monitoring of a target task, or the first message is used to request monitoring of a first subtask, where the first subtask is a subtask of the target task.

In a sixth aspect, an information monitoring device is provided, the device comprising:

a receiving unit, configured to receive a second message from a first device, wherein the second message is used to request monitoring of a target task or one or more subtasks in the target task; or, the second message is used to request monitoring of a first subtask, where the first subtask is a subtask of the target task;

A sending unit is used to send a third message to the first device, wherein the third message is used to provide reply information for monitoring the target task or one or more subtasks in the target task, or the third message is used to provide reply information for monitoring the first subtask.

In the seventh aspect, a communication device is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented, when the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented, and when the program or instruction is executed by the processor, the steps of the method described in the third aspect are implemented.

In the eighth aspect, a communication device is provided, including a processor and a communication interface, wherein the processor is used to: determine whether to monitor a target task or a first subtask based on a local policy or a first message from a second device, where the first subtask is a subtask of the target task; the first message is used to request monitoring of the target task, or the first message is used to request monitoring of the first subtask.

In the ninth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to: send a first message to a first device, wherein the first message is used to request monitoring of a target task, or the first message is used to request monitoring of a first subtask, wherein the first subtask is a subtask of the target task.

In the tenth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to: receive a second message from a first device, the second message being used to request monitoring of a target task or one or more subtasks in the target task, and the communication device comprising one or more devices that execute one or more subtasks in the target task; or, the second message being used to request monitoring of a first subtask, the communication device being a device that executes the first subtask, and the first subtask being a subtask of the target task; and send a third message to the first device, the third message being used to provide reply information for monitoring the target task or one or more subtasks in the target task, or, the third message being used to provide reply information for monitoring the first subtask.

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

In the twelfth aspect, a wireless communication system is provided, including: a first device and a second device, wherein the first device can be used to execute the steps of the method described in the first aspect, and the second device can be used to execute the steps of the method described in the second aspect.

In the thirteenth aspect, a wireless communication system is provided, including: a first device and a third device, wherein the first device can be used to execute the steps of the method described in the first aspect, and the third device can be used to execute the steps of the method described in the third aspect.

In the fourteenth aspect, a chip is provided, comprising 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 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.

In the fifteenth aspect, a computer program/program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the information monitoring method described in the first aspect, or the steps of the information monitoring method described in the second aspect, or the steps of the information monitoring method described in the third aspect.

In an embodiment of the present application, the first device determines whether to monitor a target task or a first subtask based on a local policy or a first message from a second device, where the first subtask is a subtask of the target task; the first message is used to request monitoring of the target task, or the first message is used to request monitoring of the first subtask. In this way, when it is necessary or desirable to monitor a task or subtask, the first device can monitor the task or subtask, thereby being able to know the specific execution status of the task or subtask through monitoring.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a network structure applicable to an embodiment of the present application;

FIG2 is a flow chart of an information monitoring method provided in an embodiment of the present application;

FIG3 is a flow chart of another information monitoring method provided in an embodiment of the present application;

FIG4 is a flow chart of another information monitoring method provided in an embodiment of the present application;

FIG5 is a flow chart of Example 1 provided in the embodiments of the present application;

FIG6 is a flow chart of Example 2 provided in the embodiments of the present application;

FIG7 is a structural diagram of an information monitoring device provided in an embodiment of the present application;

FIG8 is a structural diagram of another information monitoring device provided in an embodiment of the present application;

FIG9 is a structural diagram of another information monitoring device provided in an embodiment of the present application;

FIG10 is a structural diagram of a communication device provided in an embodiment of the present application;

FIG11 is a structural diagram of a terminal provided in an embodiment of the present application;

FIG12 is a structural diagram of a network-side device provided in an embodiment of the present application;

FIG13 is a structural diagram of another network-side device provided in an embodiment of the present application.

DETAILED DESCRIPTION

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.

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

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.

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 described technology 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 example 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) communication systems.

FIG1 shows a block diagram of a wireless communication system applicable to embodiments of the present application. The wireless communication system includes a terminal 11 and a network-side device 12 . Among them, 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), a flight vehicle, a vehicle user equipment (VUE), a ship-borne equipment, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (PC), an ATM or a self-service machine 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, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc. Among them, the base station can be called 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, base The Basic Service Set (BSS), Extended Service Set (ESS), home Node B (HNB), home evolved Node B, transmission reception point (TRP) or other appropriate terms in the relevant 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 embodiments of the present application, only the base station in the NR system is introduced as an example, and the specific type of the base station is not limited.

The core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, 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 (Edge Application Server Discovery Function), etc. ion, EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), etc. It should be noted that in the embodiments of the present application, only the core network equipment in the NR system is taken as an example for introduction, and the specific type of the core network equipment is not limited.

Before describing the embodiments of the present application, the following briefly introduces the relevant technologies:

Traditional communication systems are designed for connection-orientation and typically employ a session-centric management model. The network provides complete session lifecycle management mechanisms (e.g., processes such as the creation, modification, and deletion of end-to-end communication tunnels and anchor migration) and Quality of Service (QoS) guarantees. Their primary purpose is to provide connectivity for data transmission, support user mobility, and ensure a secure user experience. Traditional communication services typically utilize dedicated computing resources, with low demands on both compute and storage resources.

With the diversification of service types, services such as perception and artificial intelligence (AI) have emerged. Since AI services are data- and compute-intensive, enabling native AI capabilities in 6G networks requires the introduction of new resource dimensions, including heterogeneous computing and storage resources, new computing tasks (AI-related tasks), and new data types (input and output data required for AI computations). This requires the design of corresponding management and control mechanisms. Furthermore, 6G networks will have more comprehensive perception capabilities, including target detection, positioning (distance and angle), speed measurement, and three-dimensional (3D) imaging, and will introduce solutions based on radar echoes. These new network capabilities, such as AI and perception, will involve the coordination and deployment of resources such as computing power, connectivity, algorithms, and data in multi-node scenarios to achieve a specific goal. Session-centric management models are not suitable for these scenarios. Therefore, future communication systems may adopt a task-centric management model. However, when different nodes perform different subtasks, the execution status of tasks or subtasks cannot be known except by the node executing the subtask. In a task-centered management model, how to monitor the execution of tasks or subtasks, such as the training progress of the AI model, the current location, and other information, becomes a problem that needs to be solved.

In view of this, embodiments of the present application provide an information monitoring method, an information monitoring apparatus, and a communication device to solve the problem of not being able to know the execution status of a task or subtask.

The information monitoring method provided by the embodiments of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

FIG2 shows a flow chart of an information monitoring method provided by an embodiment of the present application. As shown in FIG2 , the information monitoring method includes the following steps:

Step 201: The first device determines whether to monitor a target task or a first subtask based on a local policy or a first message from a second device, where the first subtask is a subtask of the target task.

The first message is used to request monitoring of the target task, or the first message is used to request monitoring of the first subtask.

This application introduces a task-centered management mechanism and a device for managing tasks, namely a first device (or network element). The first device is a network element or device with a task management function. The first device can also be called a task management unit or a task management function (Task Management function). The first device can be referred to as TM or TMF. The first device can be responsible for tasks such as translation of tasks, decomposition of tasks, selection of subtask nodes (or subtask functions), and coordination between subtasks. Here, the subtask node is a node that executes a subtask. It can be a certain device (or network element), one or more functional modules in a device (or network element), or a unit composed of multiple devices (or network elements).

The first message can be understood as a monitoring request message. When the first message is used to request monitoring of a target task, it can be understood that the first message is used to request monitoring of all subtasks of the target task. For example, if the target task is divided into N subtasks, the first message is used to request monitoring of these N subtasks. In the embodiment of the present application, monitoring a task or subtask can be understood as monitoring the execution process, performance, performance, execution results, etc. of the task or subtask.

In the embodiment of the present application, the first device can decide whether to monitor the execution of the task or subtask based on the monitoring request message. If the first device does not receive the monitoring request message, the first device can also decide whether to monitor the execution of the task or subtask based on the local policy.

When the first device decides to monitor the execution status of a task or subtask, the first device may subsequently execute the monitoring process of the task or subtask and provide a monitoring report to the monitoring requester (ie, the second device) so that the monitoring requester can understand the execution status of the task or subtask.

It should be noted that the monitoring requester can be a subtask node participating in the target task, or any device that requires the target task's execution results. If the monitoring requester is a subtask node participating in the target task, the monitoring requester can determine whether the subtask needs to be dynamically modified or stopped by understanding the execution status of the task or subtask, thereby ensuring the execution of the subtask and ultimately facilitating the achievement of the target task.

The monitoring requester can be, for example, a user equipment (UE), RAN, subtask node, AF, 5G Core Network (5GC), network function (NF), and other communication devices. Subtask nodes include, for example, communication resource management nodes (such as communication-mobility management nodes and communication-session management nodes), data resource management nodes, algorithm resource management nodes, and computing resource management nodes.

The process of communication between the first device and other communication devices can be understood as a task session. For example, a task session can be the process of communication between the UE and the TM, or the process of communication between the UE, the TM, and related subtask nodes. 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 node). Establishing a task session means establishing 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 nodes in the operator's network. A task session can sometimes also be referred to as a task connection or task bearer. A task session or subtask session can sometimes also be implemented by a Protocol Data Unit (PDU) session. The task session in this application is different from the PDU session in the prior art. The task session in the prior art establishes a data channel between the UE and the UPF, while the task session in this application establishes a data transmission channel between the UE and the TM, or a data transmission channel between the UE, the TM, and related subtasks. A task session identifier and a subtask session identifier can be introduced in the task session. The task session identifier is used to identify a task session and can be allocated by the UE and sent to the network, or allocated by the TM. The subtask session identifier is used to identify a subtask session. Task session identifiers and subtask identifiers have a one-to-one mapping relationship or a one-to-many mapping relationship (a task is a combination of tasks). The subtask session identifier can be allocated by the UE and sent to the network, or it can be allocated by the TM, the subtask management function, or the subtask function.

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

In an embodiment of the present application, the first device determines whether to monitor a target task or a first subtask based on a local policy or a first message from a second device, where the first subtask is a subtask of the target task; the first message is used to request monitoring of the target task, or the first message is used to request monitoring of the first subtask. In this way, when it is necessary or desirable to monitor a task or subtask, the first device can monitor the task or subtask, thereby being able to know the execution status of the task or subtask through monitoring.

In some embodiments, the first message includes at least one of the following information:

The identifier of the target task (Task ID);

The identifier of the first subtask (Sub-task ID);

The identifier of the second device (such as UE ID, AF ID, etc.);

first indication information, used for requesting monitoring of the target task (monitoring request), or for requesting monitoring of the first subtask; in one embodiment, the first indication information is used for requesting the first device to monitor the target task, or the first indication information is used for requesting the first device to monitor the first subtask;

first time information, used to indicate a time (or time period) when the target task needs to be monitored (Monitoring period), or used to indicate a time (or time period) when the first subtask needs to be monitored; in one embodiment, the first time information is used to indicate a time when the first device needs to monitor the target task, or the first time information is used to indicate a time when the first device needs to monitor the first subtask;

a first monitoring indication, used to indicate a first monitoring parameter that needs to be monitored for the target task, or used to indicate a first monitoring parameter that needs to be monitored for the first subtask; in one embodiment, the first monitoring indication is used to indicate a first monitoring parameter that needs to be monitored by the first device for the target task, or the first monitoring indication is used to indicate a first monitoring parameter that needs to be monitored by the first device for the first subtask;

The first condition information is used to indicate the triggering condition for replying to the monitoring status of the target task, or the triggering condition for replying to the monitoring status of the first subtask; in one embodiment, the first condition information is used to indicate the triggering condition for the first device to reply to the monitoring status of the target task, or the first condition information is used to indicate the triggering condition for the first device to reply to the monitoring status of the first subtask.

The first indication information can be understood as a message type identifier, that is, it is used to indicate whether the type of the first message is: a request to monitor the target task, or a request to monitor the first subtask. In one embodiment, the type of the first message can be indicated by the name of the first message. That is, when the type of the first message is indicated by the name of the first message, the first indication information is the name of the first message.

In one implementation, the first indication information is used to request the first device to monitor the target task, or to request the first device to monitor the first subtask.

The first monitoring parameter can be understood as the parameter (or information) that needs to be monitored, which may include the type of subtask that needs to be monitored, as well as the parameters that need to be monitored (such as model accuracy, average latency, calculation accuracy or perception resolution, etc.). When the first message contains the first monitoring parameter, the first device may monitor according to the first monitoring parameter or according to the default monitoring parameter. When the first message does not contain the first monitoring parameter, the first device may monitor according to the default monitoring parameter.

The first condition information can be understood as a notification threshold (Notify threshold), that is, when the trigger condition corresponding to the first condition information is reached, it is necessary to reply to the monitoring requester with the monitoring situation (such as sending a monitoring report). If it is a scheduled report, the trigger condition can be the interval time, number of reports, etc.; if it is a conditional report, the trigger condition can be a specific condition.

Optionally, the first monitoring parameter includes at least one of the following:

Identification of the target task;

The identification of the target subtask;

Type information of the target subtask, used to indicate the type of the target subtask;

Monitoring parameters of the target subtask;

The target subtask includes one or more subtasks in the target task, or the target subtask is the first subtask.

In the case where the first message requests monitoring of the target task, the first message may carry the monitoring parameters of any number of subtasks of the target task, or may not carry the monitoring parameters of any subtask. For example, assuming that the target task includes three subtasks, namely the first subtask, the second subtask and the third subtask, then the first message may carry the monitoring parameters of all three subtasks, or may only carry the monitoring parameters of some subtasks, or may not carry the monitoring parameters of any subtask. For example, the first message only carries the monitoring parameters of the first subtask and the second subtask, but does not carry the monitoring parameters of the third subtask. In the case that the first message does not carry the monitoring parameters of the third subtask, the first device may use the default monitoring parameters of the third subtask as the monitoring parameters of the third subtask.

In the case where the first message requests monitoring of the first subtask, the first message may or may not carry the monitoring parameters of the first subtask. In the case where the first message does not carry the monitoring parameters of the first subtask, the first device may use the default monitoring parameters of the first subtask as the monitoring parameters of the first subtask.

Optionally, the target subtask includes at least one of the following types: a perception subtask, a computing subtask, an AI subtask, a data subtask, a positioning subtask, a communication subtask, and an Internet Protocol (IP) Multimedia Subsystem (IMS) subtask. For another example, the target subtask may also include, but is not limited to, a computing subtask, an information processing subtask, a multimedia subtask, an immersive subtask, and a communication subtask. Computing subtasks may include AI computing subtasks and non-AI computing subtasks; information processing subtasks may include positioning information processing subtasks and synaesthesia information processing subtasks; and immersive subtasks may include extended reality (XR) subtasks and virtual reality (VR) subtasks.

Exemplarily, the target subtask can be understood as a subtask set composed of multiple subtasks combined together in order to complete an independent function. That is, the target subtask includes multiple subtasks, and these multiple subtasks can support the completion of an independent function.

The understanding of the target task can be a combination of multiple functions or multiple subtasks, such as an automatic parking task or an environment reconstruction task. These tasks require not only the participation of computing subtasks, but also the participation of positioning subtasks. At the same time, they may also require the participation of AI subtasks. Multiple functions are combined to complete a task.

In one implementation, the first subtask or target subtask is a subtask obtained by decomposing the target task.

The monitoring parameters of the perception subtask include at least one of the following parameters: perception measurement mode, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, perception update frequency, and subtask execution time;

The monitoring parameters of the computing subtask include at least one of the following parameters: data processing mode, data processing delay, computing accuracy, computing power information, computing delay, and subtask execution time;

The monitoring parameters of the AI subtask include at least one of the following parameters: model training time, model inference time, model identifier, model download address, data source information, computing power information, computing type, model accuracy, and subtask execution time;

The monitoring parameters of the data subtask include at least one of the following parameters: data source information, data timestamp, data collection quantity, data collection size, data credibility, and subtask execution time.

In an embodiment of the present application, if the first device determines to monitor the target task or the first subtask, the first device may perform signaling interaction with each subtask node to implement monitoring of the target task or the first subtask. If the first device determines not to monitor the target task or the first subtask, the first device may reply with a rejection message to the monitoring requester.

In some embodiments, the method further comprises:

The first device sends a second message to a third device, where the second message is used to request monitoring of the target task or one or more subtasks in the target task, and the third device includes one or more devices that execute one or more subtasks in the target task; or, the second message is used to request monitoring of the first subtask, and the third device is a device that executes the first subtask;

The first device receives a third message from the third device, where the third message is used to provide reply information for monitoring the target task or one or more subtasks in the target task, or the third message is used to provide reply information for monitoring the first subtask.

In this implementation, the third device can be understood as a subtask node.

The second message can be understood as a monitoring request message. The difference from the first message is that the sender of the first message is the source requester, and the sender of the second message is the task management unit.

In the case where the first message requests monitoring of the target task, when the first device interacts with each subtask node, the first device can process the first message and request monitoring of each subtask node respectively, that is, the second message is used to request monitoring of the subtask performed by the third device; or, the second device does not process the first message and directly requests monitoring of the target task to each subtask node, that is, the second message is used to request monitoring of the target task.

Regardless of the method, after receiving the second message, the subtask node can determine that the subtask it needs to monitor is the subtask it is executing. For example, assuming that the second message is used to request monitoring of the target task, and the third device is executing the first subtask, the third device can know that it needs to monitor the first subtask.

After receiving the second message, the third device may determine whether to monitor the subtask and provide reply information to the first device.

In this implementation, the first device can enable the subtask node to monitor the subtask through signaling interaction with the subtask node, so that the first device can know the execution status of the task or subtask.

In some embodiments, the second message includes at least one of the following information:

The identification of the target task;

The identifiers of one or more subtasks in the target task, or the identifier of the first subtask;

an identifier of a second device, where the second device is a device requesting to monitor the target task or the first subtask;

an identifier of the third device;

The second indication information is used to indicate a request to monitor the target task or one or more subtasks in the target task, or to indicate a request to monitor the first subtask; in one embodiment, the second indication information is used to request a third device to monitor the target task or one or more subtasks in the target task, or the second indication information is used to request a third device to monitor the first subtask;

The second time information is used to indicate a time when the target task or one or more subtasks in the target task need to be monitored, or to indicate a time when the first subtask needs to be monitored; in one embodiment, the second time information is used to indicate a time when a third device needs to monitor the target task or one or more subtasks in the target task, or the second time information is used to indicate a time when the third device needs to monitor the first subtask;

A second monitoring indication is used to indicate a second monitoring parameter that needs to be monitored for the target task or one or more subtasks in the target task, or to indicate a second monitoring parameter that needs to be monitored for the first subtask; in one embodiment, the second monitoring indication is used to indicate a second monitoring parameter that needs to be monitored by a third device for the target task or one or more subtasks in the target task, or the second monitoring indication is used to indicate a second monitoring parameter that needs to be monitored by a third device for the first subtask;

The second condition information is used to indicate the triggering condition for reporting the monitoring report of the target task or one or more subtasks in the target task, or to indicate the triggering condition for reporting the monitoring report of the first subtask; in one embodiment, the second condition information is used to indicate the triggering condition for the third device to report the monitoring report of the target task or one or more subtasks in the target task, or the second condition information is used to indicate the triggering condition for the third device to report the monitoring report of the first subtask.

The monitoring information such as the second time information, the second monitoring parameter, the second condition information in the second message may come from the first message, or may be determined by the first device itself.

Exemplarily, the first device filters out monitoring information that is compatible with the subtask executed by the third device from the monitoring information of the first message.

Optionally, when the subtask includes a perception subtask, the second monitoring parameter includes at least one of the following parameters: perception measurement method, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, perception update frequency, and subtask execution time.

Optionally, when the subtask includes a computing subtask, the second monitoring parameter includes at least one of the following parameters: data processing method, data processing delay, computing accuracy, computing power information, computing delay, and subtask execution time.

Optionally, when the subtask includes an AI subtask, the second monitoring parameter includes at least one of the following parameters: model training time, model inference time, model identification, model download address, data source information, computing power information, calculation type, model accuracy, and subtask execution time.

Optionally, when the subtask includes a data subtask, the second monitoring parameter includes at least one of the following parameters: data source information, data timestamp, data collection quantity, data collection size, and data credibility.

In some embodiments, the third message includes at least one of the following information:

The identification of the target task;

The identifiers of one or more subtasks in the target task, or the identifier of the first subtask;

an identifier of the third device;

The third indication information (monitoring complete) is used to indicate a reply to the monitoring status of one or more subtasks in the target task (which can be understood as the completion of monitoring of one or more subtasks in the target task), or is used to indicate a reply to the monitoring status of the first subtask (which can be understood as the completion of monitoring of the first subtask);

The first monitoring report is a monitoring report of one or more subtasks in the target task, or a monitoring report of the first subtask;

The third time information is used to indicate the actual monitoring time of one or more subtasks in the target task, or to indicate the actual monitoring time of the first subtask;

fourth indication information (monitoring reject), used to indicate a rejection of monitoring one or more subtasks in the target task, or used to indicate a rejection of monitoring the first subtask;

The fifth indication information is used to indicate the reason for refusing to monitor one or more subtasks in the target task, or to indicate the reason for refusing to monitor the first subtask.

As mentioned above, after receiving the second message, the third device may determine whether to monitor the subtask and provide reply information to the first device.

When the third device determines to monitor the subtask, it may provide the first device with information such as the first monitoring report and the third time information through a third message.

Optionally, the first monitoring report includes at least one of the following information:

The first performance indicator is a performance indicator corresponding to the second monitoring parameter, where the second monitoring parameter is a monitoring parameter included in the second message;

The second performance indicator is a performance indicator corresponding to the third monitoring parameter, and the third monitoring parameter is the default monitoring parameter corresponding to the target task or one or more subtasks in the target task, or the third monitoring parameter is the default monitoring parameter corresponding to the first subtask.

Performance indicators can be understood as key performance indicators (KPIs), which characterize the performance parameters during task execution. Performance indicators may include, for example, perception accuracy information, model inference accuracy, calculation of server load, or calculation of average latency.

When the third device determines not to monitor the subtask, that is, the third device refuses to monitor the subtask, it may provide the first device with information such as the fourth indication information and the fifth indication information through a third message.

The fifth indication information may be understood as information used to indicate a reason for rejection, and may be referred to as a reason value.

Optionally, the reason indicated by the fifth indication information includes at least one of the following:

One or more subtasks in the target task do not support being monitored, or the first subtask does not support being monitored;

One or more subtasks in the target task do not support the second monitoring parameter, or the first subtask does not support the second monitoring parameter;

The third device is congested or busy.

In some embodiments, the method further comprises:

The first device sends a fourth message to the second device, where the fourth message is used to provide reply information for monitoring the target task, or the fourth message is used to provide reply information for monitoring the first subtask.

In an embodiment of the present application, when the first device receives a monitoring request from a monitoring requester, regardless of whether the first device monitors the task or subtask, the first device can provide reply information to the monitoring requester.

In one implementation, if the first device determines not to monitor the task or subtask, the first device may directly reply a rejection message to the monitoring requester.

In another implementation, if the first device determines to monitor a task or subtask, the first device may, after signaling with the subtask node, provide a response to the monitoring requester. This implementation has two possibilities: the first possibility is that the subtask node determines to monitor the subtask and provides a monitoring report to the first device. In this case, the first device may respond with the monitoring report to the monitoring requester. The second possibility is that the subtask node refuses to monitor the subtask and responds with a rejection message to the first device. In this case, the first device may respond with a rejection message to the monitoring requester.

In this embodiment, by sending the fourth message to the second device, the second device can timely understand the execution status of the target task or the first subtask, thereby providing a reference for the dynamic adjustment of subsequent task resources or the stopping of the task, etc., and ensuring better implementation of the target task.

In some embodiments, the fourth message includes at least one of the following information:

The identification of the target task;

an identifier of the first subtask;

an identifier of the second device;

an identifier of a first object, wherein the first object includes one or more devices that perform one or more subtasks of the target task, or the first object is a device that performs the first subtask;

Sixth indication information (monitoring complete), used to indicate a reply to the monitoring status of the target task (which can be understood as indicating that the monitoring of the target task has been completed), or used to indicate a reply to the monitoring status of the first subtask (which can be understood as indicating that the monitoring of the first subtask has been completed);

The second monitoring report is a monitoring report of the target task, or a monitoring report of the first subtask;

The third time information is used to indicate the actual monitoring time of the target task, or to indicate the actual monitoring time of the first subtask;

seventh indication information (monitoring reject), used to indicate a rejection of monitoring the target task, or used to indicate a rejection of monitoring the first subtask;

The eighth indication information is used to indicate the reason for refusing to monitor the target task, or to indicate the reason for refusing to monitor the first subtask.

Optionally, the second monitoring report includes at least one of the following information:

A third performance indicator is a performance indicator corresponding to the first monitoring parameter, where the first monitoring parameter is the monitoring parameter included in the first message;

The fourth performance indicator is a performance indicator corresponding to a fourth monitoring parameter, where the fourth monitoring parameter is a default monitoring parameter corresponding to the target task, or the fourth monitoring parameter is a default monitoring parameter corresponding to the first subtask.

It should be noted that the second monitoring report can be the same as or different from the first monitoring report. The first device can directly send the first monitoring report to the monitoring requester, in which case the second monitoring report is the first monitoring report; or the first device can first filter the first monitoring report to obtain the second monitoring report, and then send the second monitoring report to the monitoring requester.

Optionally, the cause indicated by the eighth indication information includes at least one of the following:

The second device does not have monitoring authority for the target task, or the second device does not have monitoring authority for the first subtask;

The second device is not authenticated or the authentication fails;

The target task does not support being monitored, or the first subtask does not support being monitored;

The target task does not support the first monitoring parameter, or the first subtask does not support the first monitoring parameter;

The first device is congested or busy;

The first object is congested or busy, and the first object includes one or more devices that execute one or more subtasks of the target task, or the first object is a device that executes the first subtask.

In an embodiment of the present application, when it is necessary or desirable to monitor a task or subtask, the first device may monitor the task or subtask, thereby being able to know the execution status of the task or subtask through monitoring.

The above is a method embodiment on the first device side. The following describes a method embodiment on the second device side.

FIG3 shows a flow chart of an information monitoring method provided by an embodiment of the present application. As shown in FIG3 , the information monitoring method includes the following steps:

Step 301: The second device sends a first message to the first device, where the first message is used to request monitoring of a target task, or the first message is used to request monitoring of a first subtask, which is a subtask of the target task.

Optionally, the first message includes at least one of the following information:

The identification of the target task;

an identifier of the first subtask;

an identifier of the second device;

First indication information, used to indicate a request to monitor the target task, or to indicate a request to monitor the first subtask;

First time information, used to indicate a time when the target task needs to be monitored, or used to indicate a time when the first subtask needs to be monitored;

A first monitoring indication, used to indicate a first monitoring parameter that needs to be monitored for the target task, or used to indicate a first monitoring parameter that needs to be monitored for the first subtask;

The first condition information is used to indicate a triggering condition for replying to the monitoring status of the target task, or to indicate a triggering condition for replying to the monitoring status of the first subtask.

Optionally, the first monitoring parameter includes at least one of the following:

The identification of the target subtask;

Type information of the target subtask;

Monitoring parameters of the target subtask;

The target subtask includes one or more subtasks of the target task, or the target subtask is the first subtask.

Optionally, the target subtask includes at least one of the following types: a perception subtask, a computing subtask, an artificial intelligence (AI) subtask, and a data subtask;

The monitoring parameters of the perception subtask include at least one of the following parameters: perception measurement mode, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, perception update frequency, and subtask execution time;

The monitoring parameters of the computing subtask include at least one of the following parameters: data processing mode, data processing delay, computing accuracy, computing power information, computing delay, and subtask execution time;

The monitoring parameters of the AI subtask include at least one of the following parameters: model training time, model inference time, model identifier, model download address, data source information, computing power information, computing type, model accuracy, and subtask execution time;

The monitoring parameters of the data subtask include at least one of the following parameters: data source information, data timestamp, data collection quantity, data collection size, data credibility, and subtask execution time.

Optionally, the method further includes:

The second device receives a fourth message from the first device, where the fourth message is used to provide reply information for monitoring the target task, or the fourth message is used to provide reply information for monitoring the first subtask.

Optionally, the fourth message includes at least one of the following information:

The identification of the target task;

an identifier of the first subtask;

an identifier of the second device;

an identifier of a first object, wherein the first object includes one or more devices that perform one or more subtasks of the target task, or the first object is a device that performs the first subtask;

Sixth instruction information, used to instruct to reply to the monitoring status of the target task, or used to instruct to reply to the monitoring status of the first subtask;

The second monitoring report is a monitoring report of the target task, or a monitoring report of the first subtask;

The third time information is used to indicate the actual monitoring time of the target task, or to indicate the actual monitoring time of the first subtask;

seventh indication information, used to indicate a refusal to monitor the target task, or to indicate a refusal to monitor the first subtask;

The eighth indication information is used to indicate the reason for refusing to monitor the target task, or to indicate the reason for refusing to monitor the first subtask.

Optionally, the second monitoring report includes at least one of the following information:

A third performance indicator is a performance indicator corresponding to the first monitoring parameter, where the first monitoring parameter is the monitoring parameter included in the first message;

The fourth performance indicator is a performance indicator corresponding to a fourth monitoring parameter, where the fourth monitoring parameter is a default monitoring parameter corresponding to the target task, or the fourth monitoring parameter is a default monitoring parameter corresponding to the first subtask.

Optionally, the cause indicated by the eighth indication information includes at least one of the following:

The second device does not have monitoring authority for the target task, or the second device does not have monitoring authority for the first subtask;

The second device is not authenticated or the authentication fails;

The target task does not support being monitored, or the first subtask does not support being monitored;

The target task does not support the first monitoring parameter, or the first subtask does not support the first monitoring parameter;

The first device is congested or busy;

The first object is congested or busy, and the first object includes one or more devices that execute one or more subtasks of the target task, or the first object is a device that executes the first subtask.

In an embodiment of the present application, when it is necessary or desirable to monitor a task or subtask, the second device may request to monitor the task or subtask, thereby helping the second device to know the execution status of the task or subtask.

For the relevant description of the embodiments of the present application, please refer to the relevant description of the method embodiment of Figure 2, and the same technical effects can be achieved. To avoid repetition, they will not be described in detail.

The above is a method embodiment on the second device side. The following describes a method embodiment on the third device side.

FIG4 shows a flow chart of an information monitoring method provided by an embodiment of the present application. As shown in FIG4 , the information monitoring method includes the following steps:

Step 401: A third device receives a second message from a first device, where the second message is used to request monitoring of a target task or one or more subtasks within the target task, and the third device includes one or more devices that execute one or more subtasks within the target task; or, the second message is used to request monitoring of a first subtask, and the third device is a device that executes the first subtask, and the first subtask is a subtask of the target task.

Step 402: The third device sends a third message to the first device, where the third message is used to provide reply information for monitoring the target task or one or more subtasks in the target task, or the third message is used to provide reply information for monitoring the first subtask.

Optionally, the second message includes at least one of the following information:

The identification of the target task;

The identifiers of one or more subtasks in the target task, or the identifier of the first subtask;

an identifier of a second device, where the second device is a device requesting to monitor the target task or the first subtask;

an identifier of the third device;

Second indication information, used to indicate a request to monitor the target task or one or more subtasks in the target task, or used to indicate a request to monitor the first subtask;

Second time information, used to indicate a time when the target task or one or more subtasks in the target task need to be monitored, or used to indicate a time when the first subtask needs to be monitored;

A second monitoring indication, used to indicate a second monitoring parameter that needs to be monitored for the target task or one or more subtasks in the target task, or used to indicate a second monitoring parameter that needs to be monitored for the first subtask;

The second condition information is used to indicate a trigger condition for reporting the monitoring report of the target task or one or more subtasks in the target task, or to indicate a trigger condition for reporting the monitoring report of the first subtask.

Optionally, when the target task or the first subtask includes a perception subtask, the second monitoring parameter includes at least one of the following parameters: perception measurement method, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, perception update frequency, and subtask execution time.

Optionally, when the target task or the first subtask includes a computing subtask, the second monitoring parameter includes at least one of the following parameters: data processing method, data processing delay, computing accuracy, computing power information, computing delay, and subtask execution time.

Optionally, when the target task or the first subtask includes an artificial intelligence (AI) subtask, the second monitoring parameter includes at least one of the following parameters: model training time, model inference time, model identification, model download address, data source information, computing power information, calculation type, model accuracy, and subtask execution time.

Optionally, when the target task or the first subtask includes a data subtask, the second monitoring parameter includes at least one of the following parameters: data source information, data timestamp, data collection quantity, data collection size, and data credibility.

Optionally, the third message includes at least one of the following information:

The identification of the target task;

The identifiers of one or more subtasks in the target task, or the identifier of the first subtask;

an identifier of the third device;

The third instruction information is used to instruct a reply to the monitoring status of one or more subtasks in the target task, or to instruct a reply to the monitoring status of the first subtask;

The first monitoring report is a monitoring report of one or more subtasks in the target task, or a monitoring report of the first subtask;

The third time information is used to indicate the actual monitoring time of one or more subtasks in the target task, or to indicate the actual monitoring time of the first subtask;

Fourth indication information, used to indicate a refusal to monitor one or more subtasks in the target task, or used to indicate a refusal to monitor the first subtask;

The fifth indication information is used to indicate the reason for refusing to monitor one or more subtasks in the target task, or to indicate the reason for refusing to monitor the first subtask.

Optionally, the first monitoring report includes at least one of the following information:

The first performance indicator is a performance indicator corresponding to the second monitoring parameter, where the second monitoring parameter is a monitoring parameter included in the second message;

The second performance indicator is a performance indicator corresponding to the third monitoring parameter, and the third monitoring parameter is the default monitoring parameter corresponding to the target task or one or more subtasks in the target task, or the third monitoring parameter is the default monitoring parameter corresponding to the first subtask.

Optionally, the reason indicated by the fifth indication information includes at least one of the following:

One or more subtasks in the target task do not support being monitored, or the first subtask does not support being monitored;

One or more subtasks in the target task do not support the second monitoring parameter, or the first subtask does not support the second monitoring parameter;

The third device is congested or busy.

For the relevant description of the embodiments of the present application, please refer to the relevant description of the method embodiment of Figure 2, and the same technical effects can be achieved. To avoid repetition, they will not be described in detail.

To better understand the embodiments of the present application, the following specific embodiments are provided to illustrate the process of task monitoring. In the embodiments provided below, the first device is a task management unit (TM), the second device includes a UE, a communication-mobility management node (representing a 5GC NF) or an AF, and the third device includes a data resource management node, an algorithm resource management node, or a computing resource management node.

Example 1: TM receives monitoring request and triggers task monitoring

As shown in Figure 5, the following steps are included:

Step 1 (including at least one of steps 1a to 1d): The UE, AF, 5GC NF, or TM decides to monitor the execution of a task. The TM receives a monitoring request message, which may carry at least one of the following:

a)Task ID, identification information of the task;

b) Message type identifier, requesting performance monitoring of the task;

c) Monitor the requester ID to identify the requester;

d) Information to be monitored (information is provided below);

e) Monitoring period, the time period that needs to be monitored;

f) Notify threshold: when the performance reaches a certain condition, the monitoring requester needs to be informed, including scheduled reports and conditional reports. Scheduled reports contain information such as interval time and number of reports; conditional reports contain specific trigger conditions.

Step 2: For the case of step 1a/1b/1c, if the TM accepts to perform task monitoring, the content of embodiment 2 is executed, and the TM monitors the signaling interaction with each subtask node.

Step 3 (including at least one of Steps 3a to 3d): If the TM refuses to perform the task monitoring, it may reply a rejection message to the monitoring requester. If the TM accepts to perform the task monitoring, it may reply a notification message to the monitoring requester after Step 2.

The message sent by the TM to the monitoring requester in step 3 may carry at least one of the following:

a)Task ID, identification information of the task;

b) Message type identification, reply/rejection to monitor the performance of the task;

c) Monitor the requester ID to identify the requester;

d) Monitoring period, the time period that needs to be monitored;

e) Performance KPI, indicating the performance parameters during task execution, including perception accuracy information, model inference accuracy, subtask server load, and subtask average latency;

f) Report trigger conditions, indicating whether it is periodic triggering or conditional triggering, and optionally carrying specific trigger condition information;

g) Reason value, indicating the reason for rejecting performance monitoring.

The following describes the information that needs to be monitored:

The information to be monitored may include one or more task execution parameters, which are used to indicate the parameters of a specific subtask and may include subtask configuration information. For example, if the task includes a perception task and a computing task, the task parameters include the perception task configuration and the computing task configuration.

A. If the subtask type is a perception subtask, the perception subtask configuration includes at least one of the following:

The sensing measurement method may include at least one of the following methods: UE self-transmitting and self-receiving, other UEs transmitting and the UE receiving, base station transmitting and UE receiving, UE transmitting and base station receiving, or base station transmitting and base station receiving. "Transmitting" refers to sending measurement signals, and "receiving" refers to receiving measurement signals and performing measurements.

A sensing service may include at least one of the following: a sensing service with a large sensing range and high real-time requirements; a sensing service with a large sensing range and low real-time requirements; a sensing service with a small sensing range and low real-time requirements; and a sensing service with a small sensing range and low real-time requirements. These services may also be represented by numbers, letters, or other character strings.

The sensing purpose may include one or more applications that require sensing services supported by the sensing device, such as respiratory monitoring, surrounding traffic environment monitoring, etc.

The sensing measurement signal indicates the signals supported by the sensing device (which can be sent or received, or both) for sensing measurement. For example, it may include at least one of the following: Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), multipath angle of arrival, multipath angle of departure, multipath delay, and Doppler frequency.

Perceptual measurement accuracy may include at least one of the following: perceptual resolution and perceptual error.

Perception resolution: refers to the ability to distinguish multiple perception targets from different dimensions, including distance resolution, velocity resolution, angle resolution, etc.

Perception range: refers to the effective range of specific perception parameters under the premise of meeting certain perception performance indicators (such as perception accuracy), specifically including perception distance range, perception speed range, perception angle range, etc.

Perception latency: used to quantitatively describe the real-time requirements of perception services, such as the maximum latency from generating a perception service request to feeding back the perception result.

Perception update frequency: the reciprocal of the time interval between two adjacent perception results.

Average perceived latency.

Subtask execution duration.

B. If the subtask type is a computing subtask, the computing subtask configuration includes at least one of the following:

Data processing methods, including at least one of the following: denoising, privacy protection, standardization, and normalization.

Data processing delay is used to indicate the overall delay of data collection and data calculation.

Calculation accuracy is used to indicate the accuracy of data collection and the overall accuracy of data calculation.

Computing power information, including at least one of the following: computing power size and computing power type.

Calculate the delay.

Subtask execution duration.

C. If the subtask type is an AI subtask, the AI subtask configuration includes at least one of the following:

Model complexity refers to the model's representational capabilities, that is, the complexity of the data that the model can fit; model training time; model inference time; model identification; model download address; data source information (data source address); computing power; calculation type; model accuracy; and subtask execution time.

D. If the subtask type is a data subtask, the data subtask configuration includes at least one of the following:

Data source information, data timestamp, data collection quantity, data collection size, and data credibility.

Example 2: TM interacts with each subtask node to obtain monitoring reports

As shown in Figure 6, the following steps are included:

Step 1: See the description of step 1 in Example 1.

The following uses the data subtask as an example to explain steps 2 to 4.

Step 2a: The TM sends a monitoring request message for the data subtask. The monitoring request message carries at least one of the following:

a)Task ID, identification information of the task;

b) Message type identifier, requesting performance monitoring of the subtask;

c) Sub-task ID, identification information of the subtask;

d) Information to be monitored (see description in Example 1);

e) Monitoring period, the time period that needs to be monitored;

f) Notify threshold: When the performance reaches a certain condition, a reply needs to be sent to the TM, including scheduled report and conditional report. Scheduled report contains information such as interval time and number of reports; conditional report contains specific triggering conditions.

Step 3a: The data subtask node executes the subtask and records the subtask execution status during the execution process, and generates a monitoring report (or execution report) according to the given conditions/default conditions.

Step 4a: The data subtask node responds to the TM with a monitoring report, which includes at least one of the following:

a)Task ID, identification information of the task;

b) Message type identification, reply/rejection to monitor the performance of the task;

c) Sub-task ID, identification information of the subtask;

d) Monitoring period, the time period that needs to be monitored;

e) Performance KPI, indicating the performance parameters during task execution, including perception accuracy information, model inference accuracy, computing server load, and computing average latency;

f) Reason value, indicating the reason for rejecting performance monitoring.

Step 5: TM can generate a task monitoring report and determine whether subtasks need to be adjusted.

Step 6: See the description of step 3 in Example 1.

The information monitoring method provided in the embodiment of the present application can be executed by an information monitoring device. In the embodiment of the present application, the information monitoring device provided in the embodiment of the present application is described by taking the information monitoring method executed by the information monitoring device as an example.

7 , an embodiment of the present application further provides an information monitoring device. As shown in FIG7 , the information monitoring device 700 includes:

The processing unit 701 is configured to determine whether to monitor a target task or a first subtask based on a local policy or a first message from a second device, where the first subtask is a subtask of the target task;

The first message is used to request monitoring of the target task, or the first message is used to request monitoring of the first subtask.

Optionally, the first message includes at least one of the following information:

The identification of the target task;

an identifier of the first subtask;

an identifier of the second device;

First indication information, used to indicate a request to monitor the target task, or to indicate a request to monitor the first subtask;

First time information, used to indicate a time when the target task needs to be monitored, or used to indicate a time when the first subtask needs to be monitored;

A first monitoring indication, used to indicate a first monitoring parameter that needs to be monitored for the target task, or used to indicate a first monitoring parameter that needs to be monitored for the first subtask;

The first condition information is used to indicate a triggering condition for replying to the monitoring status of the target task, or to indicate a triggering condition for replying to the monitoring status of the first subtask.

Optionally, the first monitoring parameter includes at least one of the following:

Identification of the target task;

The identification of the target subtask;

Type information of the target subtask, used to indicate the type of the target subtask;

Monitoring parameters of the target subtask;

The target subtask includes one or more subtasks in the target task, or the target subtask is the first subtask.

Optionally, the target subtask includes at least one of the following types: a perception subtask, a computing subtask, an artificial intelligence (AI) subtask, and a data subtask;

The monitoring parameters of the perception subtask include at least one of the following parameters: perception measurement mode, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, perception update frequency, and subtask execution time;

The monitoring parameters of the computing subtask include at least one of the following parameters: data processing mode, data processing delay, computing accuracy, computing power information, computing delay, and subtask execution time;

The monitoring parameters of the AI subtask include at least one of the following parameters: model training time, model inference time, model identifier, model download address, data source information, computing power information, computing type, model accuracy, and subtask execution time;

The monitoring parameters of the data subtask include at least one of the following parameters: data source information, data timestamp, data collection quantity, data collection size, data credibility, and subtask execution time.

Optionally, the device further comprises:

a first sending unit, configured to send a second message to a third device, where the second message is used to request monitoring of the target task or one or more subtasks within the target task, and the third device includes one or more devices that execute one or more subtasks within the target task; or, where the second message is used to request monitoring of the first subtask, and the third device is a device that executes the first subtask;

A receiving unit is used to receive a third message from the third device, wherein the third message is used to provide reply information for monitoring the target task or one or more subtasks in the target task, or the third message is used to provide reply information for monitoring the first subtask.

Optionally, the second message includes at least one of the following information:

The identification of the target task;

The identifiers of one or more subtasks in the target task, or the identifier of the first subtask;

an identifier of the second device;

an identifier of the third device;

Second indication information, used to indicate a request to monitor the target task or one or more subtasks in the target task, or used to indicate a request to monitor the first subtask;

Second time information, used to indicate a time when the target task or one or more subtasks in the target task need to be monitored, or used to indicate a time when the first subtask needs to be monitored;

A second monitoring indication, used to indicate a second monitoring parameter that needs to be monitored for the target task or one or more subtasks in the target task, or used to indicate a second monitoring parameter that needs to be monitored for the first subtask;

The second condition information is used to indicate a trigger condition for reporting the monitoring report of the target task or one or more subtasks in the target task, or to indicate a trigger condition for reporting the monitoring report of the first subtask.

Optionally, the third message includes at least one of the following information:

The identification of the target task;

The identifiers of one or more subtasks in the target task, or the identifier of the first subtask;

an identifier of the third device;

The third instruction information is used to instruct a reply to the monitoring status of one or more subtasks in the target task, or to instruct a reply to the monitoring status of the first subtask;

The first monitoring report is a monitoring report of one or more subtasks in the target task, or a monitoring report of the first subtask;

The third time information is used to indicate the actual monitoring time of one or more subtasks in the target task, or to indicate the actual monitoring time of the first subtask;

Fourth indication information, used to indicate a refusal to monitor one or more subtasks in the target task, or used to indicate a refusal to monitor the first subtask;

The fifth indication information is used to indicate the reason for refusing to monitor one or more subtasks in the target task, or to indicate the reason for refusing to monitor the first subtask.

Optionally, the first monitoring report includes at least one of the following information:

The first performance indicator is a performance indicator corresponding to the second monitoring parameter, where the second monitoring parameter is a monitoring parameter included in the second message;

The second performance indicator is a performance indicator corresponding to the third monitoring parameter, and the third monitoring parameter is the default monitoring parameter corresponding to the target task or one or more subtasks in the target task, or the third monitoring parameter is the default monitoring parameter corresponding to the first subtask.

Optionally, the reason indicated by the fifth indication information includes at least one of the following:

One or more subtasks in the target task do not support being monitored, or the first subtask does not support being monitored;

One or more subtasks in the target task do not support the second monitoring parameter, or the first subtask does not support the second monitoring parameter;

The third device is congested or busy.

Optionally, the device further comprises:

The second sending unit is used to send a fourth message to the second device, where the fourth message is used to provide reply information for monitoring the target task, or the fourth message is used to provide reply information for monitoring the first subtask.

Optionally, the fourth message includes at least one of the following information:

The identification of the target task;

an identifier of the first subtask;

an identifier of the second device;

an identifier of a first object, wherein the first object includes one or more devices that perform one or more subtasks of the target task, or the first object is a device that performs the first subtask;

Sixth instruction information, used to instruct to reply to the monitoring status of the target task, or used to instruct to reply to the monitoring status of the first subtask;

The second monitoring report is a monitoring report of the target task, or a monitoring report of the first subtask;

The third time information is used to indicate the actual monitoring time of the target task, or to indicate the actual monitoring time of the first subtask;

seventh indication information, used to indicate a refusal to monitor the target task, or to indicate a refusal to monitor the first subtask;

The eighth indication information is used to indicate the reason for refusing to monitor the target task, or to indicate the reason for refusing to monitor the first subtask.

Optionally, the second monitoring report includes at least one of the following information:

A third performance indicator is a performance indicator corresponding to the first monitoring parameter, where the first monitoring parameter is the monitoring parameter included in the first message;

The fourth performance indicator is a performance indicator corresponding to a fourth monitoring parameter, where the fourth monitoring parameter is a default monitoring parameter corresponding to the target task, or the fourth monitoring parameter is a default monitoring parameter corresponding to the first subtask.

Optionally, the cause indicated by the eighth indication information includes at least one of the following:

The second device does not have monitoring authority for the target task, or the second device does not have monitoring authority for the first subtask;

The second device is not authenticated or the authentication fails;

The target task does not support being monitored, or the first subtask does not support being monitored;

The target task does not support the first monitoring parameter, or the first subtask does not support the first monitoring parameter;

The first device is congested or busy;

The first object is congested or busy, and the first object includes one or more devices that execute one or more subtasks of the target task, or the first object is a device that executes the first subtask.

Referring to Figure 8, another embodiment of the present application provides another information monitoring device. As shown in Figure 8, the information monitoring device 800 includes:

The sending unit 801 is configured to send a first message to a first device, where the first message is used to request monitoring of a target task, or the first message is used to request monitoring of a first subtask, where the first subtask is a subtask of the target task.

Optionally, the first message includes at least one of the following information:

The identification of the target task;

an identifier of the first subtask;

an identifier of the second device;

First indication information, used to indicate a request to monitor the target task, or to indicate a request to monitor the first subtask;

First time information, used to indicate a time when the target task needs to be monitored, or used to indicate a time when the first subtask needs to be monitored;

a first monitoring indication, used to indicate a first monitoring parameter that needs to be monitored for the target task, or used to indicate a first monitoring parameter that needs to be monitored for the first subtask;

The first condition information is used to indicate a triggering condition for replying to the monitoring status of the target task, or to indicate a triggering condition for replying to the monitoring status of the first subtask.

Optionally, the first monitoring parameter includes at least one of the following:

The identification of the target subtask;

Type information of the target subtask;

Monitoring parameters of the target subtask;

The target subtask includes one or more subtasks of the target task, or the target subtask is the first subtask.

Optionally, the target subtask includes at least one of the following types: a perception subtask, a computing subtask, an artificial intelligence (AI) subtask, and a data subtask;

The monitoring parameters of the perception subtask include at least one of the following parameters: perception measurement mode, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, perception update frequency, and subtask execution time;

The monitoring parameters of the computing subtask include at least one of the following parameters: data processing mode, data processing delay, computing accuracy, computing power information, computing delay, and subtask execution time;

The monitoring parameters of the AI subtask include at least one of the following parameters: model training time, model inference time, model identifier, model download address, data source information, computing power information, computing type, model accuracy, and subtask execution time;

The monitoring parameters of the data subtask include at least one of the following parameters: data source information, data timestamp, data collection quantity, data collection size, data credibility, and subtask execution time.

Optionally, the device further comprises:

A receiving unit is configured to receive a fourth message from the first device, wherein the fourth message is configured to provide reply information for monitoring the target task, or the fourth message is configured to provide reply information for monitoring the first subtask.

Optionally, the fourth message includes at least one of the following information:

The identification of the target task;

an identifier of the first subtask;

an identifier of the second device;

an identifier of a first object, wherein the first object includes one or more devices that perform one or more subtasks of the target task, or the first object is a device that performs the first subtask;

Sixth instruction information, used to instruct to reply to the monitoring status of the target task, or used to instruct to reply to the monitoring status of the first subtask;

The second monitoring report is a monitoring report of the target task, or a monitoring report of the first subtask;

The third time information is used to indicate the actual monitoring time of the target task, or to indicate the actual monitoring time of the first subtask;

seventh indication information, used to indicate a refusal to monitor the target task, or to indicate a refusal to monitor the first subtask;

The eighth indication information is used to indicate the reason for refusing to monitor the target task, or to indicate the reason for refusing to monitor the first subtask.

Optionally, the second monitoring report includes at least one of the following information:

A third performance indicator is a performance indicator corresponding to the first monitoring parameter, where the first monitoring parameter is the monitoring parameter included in the first message;

The fourth performance indicator is a performance indicator corresponding to a fourth monitoring parameter, where the fourth monitoring parameter is a default monitoring parameter corresponding to the target task, or the fourth monitoring parameter is a default monitoring parameter corresponding to the first subtask.

Optionally, the cause indicated by the eighth indication information includes at least one of the following:

The second device does not have monitoring authority for the target task, or the second device does not have monitoring authority for the first subtask;

The second device is not authenticated or the authentication fails;

The target task does not support being monitored, or the first subtask does not support being monitored;

The target task does not support the first monitoring parameter, or the first subtask does not support the first monitoring parameter;

The first device is congested or busy;

The first object is congested or busy, and the first object includes one or more devices that execute one or more subtasks of the target task, or the first object is a device that executes the first subtask.

Referring to FIG9 , another embodiment of the present application further provides another information monitoring device. As shown in FIG9 , the information monitoring device 900 includes:

A receiving unit 901 is configured to receive a second message from a first device, where the second message is used to request monitoring of a target task or one or more subtasks within the target task; or, the second message is used to request monitoring of a first subtask, where the first subtask is a subtask of the target task;

The sending unit 902 is used to send a third message to the first device, where the third message is used to provide reply information for monitoring the target task or one or more subtasks in the target task, or the third message is used to provide reply information for monitoring the first subtask.

Optionally, the second message includes at least one of the following information:

The identification of the target task;

The identifiers of one or more subtasks in the target task, or the identifier of the first subtask;

an identifier of a second device, where the second device is a device requesting to monitor the target task or the first subtask;

an identifier of a third device, wherein the third device includes one or more devices that perform one or more subtasks of the target task, or the third device is a device that performs the first subtask;

Second indication information, used to indicate a request to monitor the target task or one or more subtasks in the target task, or used to indicate a request to monitor the first subtask;

Second time information, used to indicate a time when the target task or one or more subtasks in the target task need to be monitored, or used to indicate a time when the first subtask needs to be monitored;

A second monitoring indication, used to indicate a second monitoring parameter that needs to be monitored for the target task or one or more subtasks in the target task, or used to indicate a second monitoring parameter that needs to be monitored for the first subtask;

The second condition information is used to indicate a trigger condition for reporting the monitoring report of the target task or one or more subtasks in the target task, or to indicate a trigger condition for reporting the monitoring report of the first subtask.

Optionally, when the target task or the first subtask includes a perception subtask, the second monitoring parameter includes at least one of the following parameters: perception measurement method, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, perception update frequency, and subtask execution time.

Optionally, when the target task or the first subtask includes a computing subtask, the second monitoring parameter includes at least one of the following parameters: data processing method, data processing delay, computing accuracy, computing power information, computing delay, and subtask execution time.

Optionally, when the target task or the first subtask includes an artificial intelligence AI subtask, the second monitoring parameter includes at least one of the following parameters: model training time, model inference time, model identification, model download address, data source information, computing power information, calculation type, model accuracy, and subtask execution time.

Optionally, when the target task or the first subtask includes a data subtask, the second monitoring parameter includes at least one of the following parameters: data source information, data timestamp, data collection quantity, data collection size, and data credibility.

Optionally, the third message includes at least one of the following information:

The identification of the target task;

The identifiers of one or more subtasks in the target task, or the identifier of the first subtask;

an identifier of the third device;

The third instruction information is used to instruct a reply to the monitoring status of one or more subtasks in the target task, or to instruct a reply to the monitoring status of the first subtask;

The first monitoring report is a monitoring report of one or more subtasks in the target task, or a monitoring report of the first subtask;

The third time information is used to indicate the actual monitoring time of one or more subtasks in the target task, or to indicate the actual monitoring time of the first subtask;

Fourth indication information, used to indicate a refusal to monitor one or more subtasks in the target task, or used to indicate a refusal to monitor the first subtask;

The fifth indication information is used to indicate the reason for refusing to monitor one or more subtasks in the target task, or to indicate the reason for refusing to monitor the first subtask.

Optionally, the first monitoring report includes at least one of the following information:

The first performance indicator is a performance indicator corresponding to the second monitoring parameter, where the second monitoring parameter is a monitoring parameter included in the second message;

The second performance indicator is a performance indicator corresponding to the third monitoring parameter, and the third monitoring parameter is the default monitoring parameter corresponding to the target task or one or more subtasks in the target task, or the third monitoring parameter is the default monitoring parameter corresponding to the first subtask.

Optionally, the reason indicated by the fifth indication information includes at least one of the following:

One or more subtasks in the target task do not support being monitored, or the first subtask does not support being monitored;

One or more subtasks in the target task do not support the second monitoring parameter, or the first subtask does not support the second monitoring parameter;

The third device is congested or busy.

The information monitoring device in the embodiment 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 a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

The information monitoring device provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 6 and achieve the same technical effects. To avoid repetition, they will not be described here.

As shown in Figure 10, 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 programs or instructions that can be run on the processor 1001. For example, when the communication device 1000 is a first device, the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned first device side method embodiment, and can achieve the same technical effect. When the communication device 1000 is a second device, the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned second device side method embodiment, and can achieve the same technical effect. When the communication device 1000 is a third device, the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned third device side method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

The present application also provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG3 . This terminal embodiment corresponds to the second device-side method embodiment described above, and each implementation process and implementation method of the method embodiment described above are applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG11 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

The terminal 1100 includes but is not limited to: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109 and at least some of the components of the processor 1110.

Those skilled in the art will appreciate that the terminal 1100 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1110 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG11 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.

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

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

The memory 1109 can be used to store software programs or instructions and various data. The memory 1109 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1109 may include volatile memory or non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM (DRRAM). The memory 1109 in the embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

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

The radio frequency unit 1101 is used for:

A first message is sent to a first device, where the first message is used to request monitoring of a target task, or the first message is used to request monitoring of a first subtask, where the first subtask is a subtask of the target task.

In an embodiment of the present application, when it is necessary or desirable to monitor a task or subtask, the second device may request to monitor the task or subtask, thereby helping the second device to know the execution status of the task or subtask.

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

The present application also 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 configured to execute a program or instruction to implement the steps of the method embodiments shown in Figures 2 to 6. This network-side device embodiment corresponds to the first device-side, second device-side, or third device-side method embodiments described above, and each implementation process and implementation method of the aforementioned method embodiments are applicable to this network-side device embodiment and can achieve the same technical effects.

Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 12, the network-side device 1200 includes an antenna 121, a radio frequency device 122, a baseband device 123, a processor 124, and a memory 125. Antenna 121 is connected to radio frequency device 122. In the uplink direction, radio frequency device 122 receives information via antenna 121 and sends the received information to baseband device 123 for processing. In the downlink direction, baseband device 123 processes the information to be transmitted and sends it to radio frequency device 122. Radio frequency device 122 processes the received information and then sends it through antenna 121.

The method executed by the network-side device in the above embodiment may be implemented in the baseband device 123 , which includes a baseband processor.

The baseband device 123 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 12, one of the chips is, for example, a baseband processor, which is connected to the memory 125 through a bus interface to call the program in the memory 125 and execute the network device operations shown in the above method embodiment.

The network side device may also include a network interface 126, which is, for example, a Common Public Radio Interface (CPRI).

Specifically, the network side device 1200 of the embodiment of the present application also includes: instructions or programs stored in the memory 125 and executable on the processor 124. The processor 124 calls the instructions or programs in the memory 125 to execute the methods executed by the modules shown in Figures 7 to 9 and achieve the same technical effects. To avoid repetition, they will not be elaborated here.

Specifically, embodiments of the present application also provide another network-side device. As shown in FIG13 , the network-side device 1300 includes a processor 1301, a network interface 1302, and a memory 1303. The network interface 1302 is, for example, a common public radio interface (CPRI).

Specifically, the network side device 1300 of the embodiment of the present application also includes: instructions or programs stored in the memory 1303 and executable on the processor 1301. The processor 1301 calls the instructions or programs in the memory 1303 to execute the methods executed by the modules shown in Figures 7 to 9 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

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 information monitoring method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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.

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 information monitoring method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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.

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

An embodiment of the present application also provides a communication system, including: a first device and a second device, wherein the first device can be used to execute the steps of the information monitoring method on the first device side as described above, and the second device can be used to execute the steps of the information monitoring method on the second device side as described above.

An embodiment of the present application also provides a communication system, including: a first device and a third device, wherein the first device can be used to execute the steps of the information monitoring method on the first device side as described above, and the third device can be used to execute the steps of the information monitoring method on the third device side as described above.

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.

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.

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 (39)

An information monitoring method, comprising: The first device determines whether to monitor the target task or the first subtask based on a local policy or a first message from the second device, where the first subtask is a subtask of the target task; The first message is used to request monitoring of the target task, or the first message is used to request monitoring of the first subtask. The method according to claim 1, wherein the first message includes at least one of the following information: The identification of the target task; an identifier of the first subtask; an identifier of the second device; First indication information, used to indicate a request to monitor the target task, or to indicate a request to monitor the first subtask; First time information, used to indicate a time when the target task needs to be monitored, or used to indicate a time when the first subtask needs to be monitored; A first monitoring indication, used to indicate a first monitoring parameter that needs to be monitored for the target task, or used to indicate a first monitoring parameter that needs to be monitored for the first subtask; The first condition information is used to indicate a triggering condition for replying to the monitoring status of the target task, or to indicate a triggering condition for replying to the monitoring status of the first subtask. The method according to claim 2, wherein the first monitoring parameter includes at least one of the following: Identification of the target task; The identification of the target subtask; Type information of the target subtask, used to indicate the type of the target subtask; Monitoring parameters of the target subtask; The target subtask includes one or more subtasks in the target task, or the target subtask is the first subtask. The method according to claim 3, wherein the target subtask comprises at least one of the following types: a perception subtask, a computation subtask, an artificial intelligence (AI) subtask, and a data subtask; The monitoring parameters of the perception subtask include at least one of the following parameters: perception measurement mode, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, perception update frequency, and subtask execution time; The monitoring parameters of the computing subtask include at least one of the following parameters: data processing mode, data processing delay, computing accuracy, computing power information, computing delay, and subtask execution time; The monitoring parameters of the AI subtask include at least one of the following parameters: model training time, model inference time, model identifier, model download address, data source information, computing power information, computing type, model accuracy, and subtask execution time; The monitoring parameters of the data subtask include at least one of the following parameters: data source information, data timestamp, data collection quantity, data collection size, data credibility, and subtask execution time. The method according to any one of claims 1 to 4, further comprising: The first device sends a second message to a third device, where the second message is used to request monitoring of the target task or one or more subtasks in the target task, and the third device includes one or more devices that execute one or more subtasks in the target task; or, the second message is used to request monitoring of the first subtask, and the third device is a device that executes the first subtask; The first device receives a third message from the third device, where the third message is used to provide reply information for monitoring the target task or one or more subtasks in the target task, or the third message is used to provide reply information for monitoring the first subtask. The method according to claim 5, wherein the second message includes at least one of the following information: The identification of the target task; The identifiers of one or more subtasks in the target task, or the identifier of the first subtask; an identifier of the second device; an identifier of the third device; The second indication information is used to request monitoring of the target task or one or more subtasks in the target task, or to request monitoring of the first subtask; Second time information, used to indicate a time when the target task or one or more subtasks in the target task need to be monitored, or used to indicate a time when the first subtask needs to be monitored; A second monitoring indication, used to indicate a second monitoring parameter that needs to be monitored for the target task or one or more subtasks in the target task, or used to indicate a second monitoring parameter that needs to be monitored for the first subtask; The second condition information is used to indicate a trigger condition for reporting the monitoring report of the target task or one or more subtasks in the target task, or to indicate a trigger condition for reporting the monitoring report of the first subtask. The method according to claim 5 or 6, wherein the third message includes at least one of the following information: The identification of the target task; The identifiers of one or more subtasks in the target task, or the identifier of the first subtask; an identifier of the third device; The third instruction information is used to instruct a reply to the monitoring status of one or more subtasks in the target task, or to instruct a reply to the monitoring status of the first subtask; The first monitoring report is a monitoring report of one or more subtasks in the target task, or a monitoring report of the first subtask; The third time information is used to indicate the actual monitoring time of one or more subtasks in the target task, or to indicate the actual monitoring time of the first subtask; Fourth indication information, used to indicate a refusal to monitor one or more subtasks in the target task, or used to indicate a refusal to monitor the first subtask; The fifth indication information is used to indicate the reason for refusing to monitor one or more subtasks in the target task, or to indicate the reason for refusing to monitor the first subtask. The method according to claim 7, wherein the first monitoring report includes at least one of the following information: The first performance indicator is a performance indicator corresponding to the second monitoring parameter, where the second monitoring parameter is a monitoring parameter included in the second message; The second performance indicator is a performance indicator corresponding to the third monitoring parameter, and the third monitoring parameter is the default monitoring parameter corresponding to the target task or one or more subtasks in the target task, or the third monitoring parameter is the default monitoring parameter corresponding to the first subtask. The method according to claim 7, wherein the cause indicated by the fifth indication information includes at least one of the following: One or more subtasks in the target task do not support being monitored, or the first subtask does not support being monitored; One or more subtasks in the target task do not support the second monitoring parameter, or the first subtask does not support the second monitoring parameter; The third device is congested or busy. The method according to any one of claims 1 to 9, further comprising: The first device sends a fourth message to the second device, where the fourth message is used to provide reply information for monitoring the target task, or the fourth message is used to provide reply information for monitoring the first subtask. The method according to claim 10, wherein the fourth message includes at least one of the following information: The identification of the target task; an identifier of the first subtask; an identifier of the second device; an identifier of a first object, wherein the first object includes one or more devices that perform one or more subtasks of the target task, or the first object is a device that performs the first subtask; Sixth instruction information, used to instruct to reply to the monitoring status of the target task, or used to instruct to reply to the monitoring status of the first subtask; The second monitoring report is a monitoring report of the target task, or a monitoring report of the first subtask; The third time information is used to indicate the actual monitoring time of the target task, or to indicate the actual monitoring time of the first subtask; seventh indication information, used to indicate a refusal to monitor the target task, or to indicate a refusal to monitor the first subtask; The eighth indication information is used to indicate the reason for refusing to monitor the target task, or to indicate the reason for refusing to monitor the first subtask. The method according to claim 11, wherein the second monitoring report includes at least one of the following information: A third performance indicator is a performance indicator corresponding to the first monitoring parameter, where the first monitoring parameter is the monitoring parameter included in the first message; The fourth performance indicator is a performance indicator corresponding to a fourth monitoring parameter, where the fourth monitoring parameter is a default monitoring parameter corresponding to the target task, or the fourth monitoring parameter is a default monitoring parameter corresponding to the first subtask. The method according to claim 11, wherein the cause indicated by the eighth indication information includes at least one of the following: The second device does not have monitoring authority for the target task, or the second device does not have monitoring authority for the first subtask; The second device is not authenticated or authentication fails; The target task does not support being monitored, or the first subtask does not support being monitored; The target task does not support the first monitoring parameter, or the first subtask does not support the first monitoring parameter; The first device is congested or busy; The first object is congested or busy, and the first object includes one or more devices that execute one or more subtasks of the target task, or the first object is a device that executes the first subtask. An information monitoring method, comprising: The second device sends a first message to the first device, where the first message is used to request monitoring of a target task, or the first message is used to request monitoring of a first subtask, where the first subtask is a subtask of the target task. The method according to claim 14, wherein the first message includes at least one of the following information: The identification of the target task; an identifier of the first subtask; an identifier of the second device; First indication information, used to request monitoring of the target task, or to request monitoring of the first subtask; First time information, used to indicate a time when the target task needs to be monitored, or used to indicate a time when the first subtask needs to be monitored; A first monitoring indication, used to indicate a first monitoring parameter that needs to be monitored for the target task, or used to indicate a first monitoring parameter that needs to be monitored for the first subtask; The first condition information is used to indicate a triggering condition for replying to the monitoring status of the target task, or to indicate a triggering condition for replying to the monitoring status of the first subtask. The method according to claim 15, wherein the first monitoring parameter includes at least one of the following: The identification of the target subtask; Type information of the target subtask; Monitoring parameters of the target subtask; The target subtask includes one or more subtasks of the target task, or the target subtask is the first subtask. The method according to claim 16, wherein the target subtask comprises at least one of the following types: a perception subtask, a computation subtask, an artificial intelligence (AI) subtask, and a data subtask; The monitoring parameters of the perception subtask include at least one of the following parameters: perception measurement mode, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, perception update frequency, and subtask execution time; The monitoring parameters of the computing subtask include at least one of the following parameters: data processing mode, data processing delay, computing accuracy, computing power information, computing delay, and subtask execution time; The monitoring parameters of the AI subtask include at least one of the following parameters: model training time, model inference time, model identifier, model download address, data source information, computing power information, computing type, model accuracy, and subtask execution time; The monitoring parameters of the data subtask include at least one of the following parameters: data source information, data timestamp, data collection quantity, data collection size, data credibility, and subtask execution time. The method according to any one of claims 14 to 17, further comprising: The second device receives a fourth message from the first device, where the fourth message is used to provide reply information for monitoring the target task, or the fourth message is used to provide reply information for monitoring the first subtask. The method according to claim 18, wherein the fourth message includes at least one of the following information: The identification of the target task; an identifier of the first subtask; an identifier of the second device; an identifier of a first object, wherein the first object includes one or more devices that perform one or more subtasks of the target task, or the first object is a device that performs the first subtask; Sixth instruction information, used to instruct to reply to the monitoring status of the target task, or used to instruct to reply to the monitoring status of the first subtask; The second monitoring report is a monitoring report of the target task, or a monitoring report of the first subtask; The third time information is used to indicate the actual monitoring time of the target task, or to indicate the actual monitoring time of the first subtask; seventh indication information, used to indicate a refusal to monitor the target task, or to indicate a refusal to monitor the first subtask; The eighth indication information is used to indicate the reason for refusing to monitor the target task, or to indicate the reason for refusing to monitor the first subtask. The method according to claim 19, wherein the second monitoring report includes at least one of the following information: A third performance indicator is a performance indicator corresponding to the first monitoring parameter, where the first monitoring parameter is the monitoring parameter included in the first message; The fourth performance indicator is a performance indicator corresponding to a fourth monitoring parameter, where the fourth monitoring parameter is a default monitoring parameter corresponding to the target task, or the fourth monitoring parameter is a default monitoring parameter corresponding to the first subtask. The method according to claim 19, wherein the cause indicated by the eighth indication information includes at least one of the following: The second device does not have monitoring authority for the target task, or the second device does not have monitoring authority for the first subtask; The second device is not authenticated or the authentication fails; The target task does not support being monitored, or the first subtask does not support being monitored; The target task does not support the first monitoring parameter, or the first subtask does not support the first monitoring parameter; The first device is congested or busy; The first object is congested or busy, and the first object includes one or more devices that execute one or more subtasks of the target task, or the first object is a device that executes the first subtask. An information monitoring method, comprising: The third device receives a second message from the first device, where the second message is used to request monitoring of a target task or one or more subtasks within the target task, and the third device includes one or more devices that execute one or more subtasks within the target task; or, the second message is used to request monitoring of a first subtask, the third device is a device that executes the first subtask, and the first subtask is a subtask of the target task; The third device sends a third message to the first device, where the third message is used to provide reply information for monitoring the target task or one or more subtasks in the target task, or the third message is used to provide reply information for monitoring the first subtask. The method according to claim 22, wherein the second message includes at least one of the following information: The identification of the target task; The identifiers of one or more subtasks in the target task, or the identifier of the first subtask; an identifier of a second device, where the second device is a device requesting to monitor the target task or the first subtask; an identifier of the third device; The second indication information is used to request monitoring of the target task or one or more subtasks in the target task, or to request monitoring of the first subtask; Second time information, used to indicate a time when the target task or one or more subtasks in the target task need to be monitored, or used to indicate a time when the first subtask needs to be monitored; A second monitoring indication, used to indicate a second monitoring parameter that needs to be monitored for the target task or one or more subtasks in the target task, or used to indicate a second monitoring parameter that needs to be monitored for the first subtask; The second condition information is used to indicate a trigger condition for reporting the monitoring report of the target task or one or more subtasks in the target task, or to indicate a trigger condition for reporting the monitoring report of the first subtask. The method according to claim 23, wherein, when the target task or the first subtask includes a perception subtask, the second monitoring parameter includes at least one of the following parameters: perception measurement mode, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, perception update frequency, and subtask execution time; or, In the case where the target task or the first subtask includes a computing subtask, the second monitoring parameter includes at least one of the following parameters: data processing mode, data processing delay, computing accuracy, computing power information, computing delay, and subtask execution time; or, In the case where the target task or the first subtask includes an artificial intelligence (AI) subtask, the second monitoring parameter includes at least one of the following parameters: model training time, model inference time, model identifier, model download address, data source information, computing power information, computing type, model accuracy, and subtask execution time; or, In the case where the target task or the first subtask includes a data subtask, the second monitoring parameter includes at least one of the following parameters: data source information, data timestamp, data collection quantity, data collection size, and data credibility. The method according to any one of claims 22 to 24, wherein the third message includes at least one of the following information: The identification of the target task; The identifiers of one or more subtasks in the target task, or the identifier of the first subtask; an identifier of the third device; The third instruction information is used to instruct a reply to the monitoring status of one or more subtasks in the target task, or to instruct a reply to the monitoring status of the first subtask; The first monitoring report is a monitoring report of one or more subtasks in the target task, or a monitoring report of the first subtask; The third time information is used to indicate the actual monitoring time of one or more subtasks in the target task, or to indicate the actual monitoring time of the first subtask; Fourth indication information, used to indicate a refusal to monitor one or more subtasks in the target task, or used to indicate a refusal to monitor the first subtask; The fifth indication information is used to indicate the reason for refusing to monitor one or more subtasks in the target task, or to indicate the reason for refusing to monitor the first subtask. The method according to claim 25, wherein the first monitoring report includes at least one of the following information: The first performance indicator is a performance indicator corresponding to the second monitoring parameter, where the second monitoring parameter is a monitoring parameter included in the second message; The second performance indicator is a performance indicator corresponding to the third monitoring parameter, and the third monitoring parameter is the default monitoring parameter corresponding to the target task or one or more subtasks in the target task, or the third monitoring parameter is the default monitoring parameter corresponding to the first subtask. The method according to claim 25, wherein the cause indicated by the fifth indication information includes at least one of the following: One or more subtasks in the target task do not support being monitored, or the first subtask does not support being monitored; One or more subtasks in the target task do not support the second monitoring parameter, or the first subtask does not support the second monitoring parameter; The third device is congested or busy. An information monitoring device, comprising: a processing unit, configured to determine whether to monitor a target task or a first subtask based on a local policy or a first message from a second device, where the first subtask is a subtask of the target task; The first message is used to request monitoring of the target task, or the first message is used to request monitoring of the first subtask. The apparatus according to claim 28, further comprising: a first sending unit, configured to send a second message to a third device, where the second message is used to request monitoring of the target task or one or more subtasks within the target task, and the third device includes one or more devices that execute one or more subtasks within the target task; or, where the second message is used to request monitoring of the first subtask, and the third device is a device that executes the first subtask; A receiving unit is used to receive a third message from the third device, wherein the third message is used to provide reply information for monitoring the target task or one or more subtasks in the target task, or the third message is used to provide reply information for monitoring the first subtask. The apparatus according to claim 28 or 29, further comprising: The second sending unit is used to send a fourth message to the second device, where the fourth message is used to provide reply information for monitoring the target task, or the fourth message is used to provide reply information for monitoring the first subtask. The apparatus according to claim 30, wherein the fourth message includes at least one of the following information: The identification of the target task; an identifier of the first subtask; an identifier of the second device; an identifier of a first object, wherein the first object includes one or more devices that perform one or more subtasks of the target task, or the first object is a device that performs the first subtask; Sixth instruction information, used to instruct to reply to the monitoring status of the target task, or used to instruct to reply to the monitoring status of the first subtask; The second monitoring report is a monitoring report of the target task, or a monitoring report of the first subtask; The third time information is used to indicate the actual monitoring time of the target task, or to indicate the actual monitoring time of the first subtask; seventh indication information, used to indicate a refusal to monitor the target task, or to indicate a refusal to monitor the first subtask; The eighth indication information is used to indicate the reason for refusing to monitor the target task, or to indicate the reason for refusing to monitor the first subtask. An information monitoring device, comprising: The sending unit is configured to send a first message to a first device, where the first message is used to request monitoring of a target task, or the first message is used to request monitoring of a first subtask, where the first subtask is a subtask of the target task. The apparatus according to claim 32, further comprising: A receiving unit is used to receive a fourth message from the first device, where the fourth message is used to provide reply information for monitoring the target task, or the fourth message is used to provide reply information for monitoring the first subtask. An information monitoring device, comprising: a receiving unit, configured to receive a second message from a first device, wherein the second message is used to request monitoring of a target task or one or more subtasks in the target task; or, the second message is used to request monitoring of a first subtask, where the first subtask is a subtask of the target task; A sending unit is used to send a third message to the first device, wherein the third message is used to provide reply information for monitoring the target task or one or more subtasks in the target task, or the third message is used to provide reply information for monitoring the first subtask. The apparatus according to claim 34, wherein the second message includes at least one of the following information: The identification of the target task; The identifiers of one or more subtasks in the target task, or the identifier of the first subtask; an identifier of a second device, where the second device is a device requesting to monitor the target task or the first subtask; an identifier of a third device, wherein the third device includes one or more devices that perform one or more subtasks of the target task, or the third device is a device that performs the first subtask; The second indication information is used to request monitoring of the target task or one or more subtasks in the target task, or to request monitoring of the first subtask; Second time information, used to indicate a time when the target task or one or more subtasks in the target task need to be monitored, or used to indicate a time when the first subtask needs to be monitored; A second monitoring indication, used to indicate a second monitoring parameter that needs to be monitored for the target task or one or more subtasks in the target task, or used to indicate a second monitoring parameter that needs to be monitored for the first subtask; The second condition information is used to indicate a trigger condition for reporting the monitoring report of the target task or one or more subtasks in the target task, or to indicate a trigger condition for reporting the monitoring report of the first subtask. The apparatus according to claim 34 or 35, wherein the third message includes at least one of the following information: The identification of the target task; The identifiers of one or more subtasks in the target task, or the identifier of the first subtask; an identifier of a third device, wherein the third device includes one or more devices that perform one or more subtasks of the target task, or the third device is a device that performs the first subtask; The third instruction information is used to instruct a reply to the monitoring status of one or more subtasks in the target task, or to instruct a reply to the monitoring status of the first subtask; The first monitoring report is a monitoring report of one or more subtasks in the target task, or a monitoring report of the first subtask; The third time information is used to indicate the actual monitoring time of one or more subtasks in the target task, or to indicate the actual monitoring time of the first subtask; Fourth indication information, used to indicate a refusal to monitor one or more subtasks in the target task, or used to indicate a refusal to monitor the first subtask; The fifth indication information is used to indicate the reason for refusing to monitor one or more subtasks in the target task, or to indicate the reason for refusing to monitor the first subtask. A communication device 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, it implements the steps of the information monitoring method according to any one of claims 1 to 13, or implements the steps of the information monitoring method according to any one of claims 14 to 21, or implements the steps of the information monitoring method according to any one of claims 22 to 27. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the information monitoring method according to any one of claims 1 to 13, or implements the steps of the information monitoring method according to any one of claims 14 to 21, or implements the steps of the information monitoring method according to any one of claims 22 to 27. A computer program product comprising computer instructions, which, when executed by a processor, implement the steps of the information monitoring method according to any one of claims 1 to 13, or implement the steps of the information monitoring method according to any one of claims 14 to 21, or implement the steps of the information monitoring method according to any one of claims 22 to 27.