[go: up one dir, main page]

WO2025195240A1 - Procédé et appareil de traitement de tâche, et dispositif associé - Google Patents

Procédé et appareil de traitement de tâche, et dispositif associé

Info

Publication number
WO2025195240A1
WO2025195240A1 PCT/CN2025/081974 CN2025081974W WO2025195240A1 WO 2025195240 A1 WO2025195240 A1 WO 2025195240A1 CN 2025081974 W CN2025081974 W CN 2025081974W WO 2025195240 A1 WO2025195240 A1 WO 2025195240A1
Authority
WO
WIPO (PCT)
Prior art keywords
subtask
task
target task
network element
release
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/081974
Other languages
English (en)
Chinese (zh)
Inventor
周通
康艳超
王慧
于航
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2025195240A1 publication Critical patent/WO2025195240A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to a task processing method, apparatus and related equipment.
  • the embodiments of the present application provide a task processing method, apparatus, and related equipment, which can solve the problem of long service processing time in traditional communication systems.
  • a task processing method comprising:
  • the first network element receives a first message sent by the second network element, where the first message is used to request the release of a target task or a subtask of the target task;
  • the first network element performs a release operation on the target task or a subtask of the target task according to the first message
  • the target task includes at least one subtask
  • the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.
  • a task processing method comprising:
  • the second network element sends a first message to the first network element, where the first message is used to request the release of the target task or a subtask of the target task;
  • the target task includes at least one subtask
  • the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.
  • a task processing device comprising:
  • a receiving module configured to receive a first message sent by a second network element, wherein the first message is used to request the release of a target task or a subtask of the target task;
  • An execution module configured to execute a release operation on the target task or a subtask of the target task
  • the target task includes at least one subtask
  • the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.
  • a task processing device comprising:
  • a sending module configured to send a first message to a first network element, wherein the first message is used to request the release of a target task or a subtask of the target task;
  • the target task includes at least one subtask
  • the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.
  • a communication device comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.
  • a first network element including a processor and a communication interface, wherein the communication interface is configured to:
  • the processor is configured to: perform a release operation on the target task or a subtask of the target task;
  • the target task includes at least one subtask
  • the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.
  • a second network element comprising a processor and a communication interface, wherein the communication interface is configured to:
  • the target task includes at least one subtask
  • the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.
  • a readable storage medium on which a program or instruction is stored.
  • the program or instruction is executed by a processor, the steps of the method described in the first aspect or the steps of the method described in the second aspect are implemented.
  • a chip 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 steps of the method described in the first aspect, or to implement the steps of the method described in the second 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 method described in the first aspect, or to implement the steps of the method described in the second aspect.
  • an information sending and receiving system including: a first access network device and a core network device, wherein the first access network device can be used to execute the steps of the method described in the first aspect, and the core network device can be used to execute the steps of the method described in the second aspect.
  • a first network element receives a first message sent by a second network element, wherein the first message is used to request the release of a target task or a subtask of a target task; the first network element performs a release operation on the target task or a subtask of the target task; wherein the subtask of the target task includes at least one of the following: a perception subtask, a computing subtask, an artificial intelligence AI subtask, a data subtask, a positioning subtask, a communication subtask, an IP multimedia subsystem IMS subtask, an information processing subtask, and an immersive subtask.
  • the embodiment of the present application can also support the release of multiple subtasks of the target task through one signaling message.
  • FIG1 is a block diagram of a wireless communication system applicable to embodiments of the present application.
  • FIG2 is a flowchart of a task processing method according to an embodiment of the present application.
  • FIG3 is a second flow chart of a task processing method provided in an embodiment of the present application.
  • FIG4 is a third flow chart of a task processing method provided in an embodiment of the present application.
  • FIG5 is a fourth flow chart of a task processing method provided in an embodiment of the present application.
  • FIG6 is a fifth flow chart of a task processing method provided in an embodiment of the present application.
  • FIG7 is a structural diagram of a task processing device according to an embodiment of the present application.
  • FIG8 is a second structural diagram of a task processing device provided in an embodiment of the present application.
  • FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application.
  • FIG10 is a schematic diagram of a structure of a network side device according to an embodiment of the present application.
  • FIG11 is a second structural diagram of a network-side device provided in an embodiment of the present application.
  • 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.
  • “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.
  • 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.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • 6G 6th Generation
  • 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 .
  • 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.
  • PC personal computer
  • ATM an ATM or a self-service machine and other terminal
  • 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.
  • 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.
  • WLAN wireless Local Area Network
  • AP Access Point
  • WiFi wireless Fidelity
  • 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 node, core network function, Mobility Management Entity (MME), Access Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (Edge Application Server Discovery Function), and so on.
  • EASDF Unified Data Management
  • UDM Unified Data Repository
  • HSS Home Subscriber Server
  • CNC Centralized Network Configuration
  • NRF Network Repository Function
  • NEF Network Exposure Function
  • L-NEF Binding Support Function
  • BSF Binding Support Function
  • AF Application Function
  • Communication, perception, and computing are the three most important foundational capabilities for building a freely connected physical and digital world.
  • 6G will natively support communication, perception, and computing services, which means 6G networks will need to introduce a new resource dimension. Unlike existing connection-oriented designs, 6G systems will adopt a task-oriented design.
  • AI artificial intelligence
  • 6G networks To enable 6G networks to have native AI capabilities, new resource dimensions must be introduced, including heterogeneous computing and storage resources, new computing subtasks (such as AI-related computing), and new data types (such as AI computing input and output data). Accordingly, corresponding management and control mechanisms must be designed. 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 or perception capabilities, will involve the coordination and deployment of computing power, connectivity, algorithms, and data resources in multi-node scenarios to jointly achieve a specific goal.
  • the existing 5G system can only provide a pipeline for data transmission.
  • the corresponding deletion of the end-to-end communication tunnel only targets communication resources, and cannot support the release of communication, perception, and computing resources required for the execution of 6G network tasks.
  • Mission The 6G system provides comprehensive services (including communication, information, interawareness, and computing) on demand based on external service requests.
  • the external service requests can come from user equipment (UE) or over-the-top (OTT) services.
  • UE user equipment
  • OTT over-the-top
  • Task Management The goal is to respond to external business requests and provide a management process that includes communication functions and other 6G additional functions (such as positioning, telepathy, computing, etc.).
  • Task template used to indicate the UE or network's requirements for a task.
  • the task template may include, but is not limited to, at least one of task description information, task Quality of Experience (QoE) requirement information, task strategy or task Quality (QoT) information, and task parameters.
  • QoE Quality of Experience
  • QoT task Quality of T
  • the task description information indicates the type of task, that is, what the task is. For example, if the task is to sense traffic congestion in the target area, the task description information would be "traffic congestion"; for another example, if the task is to park the vehicle in a suitable or designated location, the task description information would be "automatic parking.”
  • the task description information is used to identify the task information of the task parameter application, which may include but is not limited to at least one of the data network name (Data Network Name, DNN), single network slice selection assistance information (S-NSSAI), AF identifier, and application (Application, APP) identifier.
  • Data Network Name DNN
  • S-NSSAI single network slice selection assistance information
  • AF identifier AF identifier
  • Application, APP Application, APP
  • the task QoE requirement information is used to indicate the user's subjective perception of the quality and performance of the task, which refers to the user's perceived difficulty in completing the entire task process.
  • the task QoE requirement information can be represented by the level of user experience achieved.
  • the task strategy or task quality information is used to indicate the service quality requirements of the task, which may include but is not limited to at least one of the following (a)-(d).
  • Task feedback time or task latency which indicates the time limit from when a task consumer or requester (e.g., UE, AF, etc.) initiates a task request to when it receives a task response.
  • a task consumer or requester e.g., UE, AF, etc.
  • Task accuracy which indicates the probability of successful task completion or the degree to which the UE's expected value/the value promised by the task provider is consistent with the actual value.
  • the task parameters are used to indicate task-specific parameters, which may include subtask configuration information. For example, if a task includes a perception subtask and a computing subtask, the task parameters include the perception subtask configuration and the computing subtask configuration.
  • the perception subtask configuration may include but is not limited to at least one of the perception measurement method, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, and perception update frequency.
  • the sensing measurement mode may include at least one of the following modes: UE self-transmitting and self-receiving, other UE transmitting and UE receiving, base station transmitting and UE receiving, UE transmitting and base station receiving, base station transmitting and base station receiving, etc.
  • Transmitting refers to sending measurement signals
  • receiving refers to receiving measurement signals and performing measurements.
  • the sensing services may include, but are not limited to, at least one of: large-scale sensing (LSS) services with high delay criticality, large-scale sensing (LSS) services with low delay criticality, small-scale sensing (SSS) services with low delay criticality, and small-scale sensing (SSS) services with low delay criticality.
  • LSS large-scale sensing
  • SSS small-scale sensing
  • SSS small-scale sensing
  • SSS small-scale sensing
  • the sensing purpose may include one or more applications supported by the sensing device and requiring sensing services, such as respiratory monitoring, surrounding traffic environment monitoring, etc.
  • the perception measurement signal is used to indicate a signal supported by the perception device (which can be sent or received, or both sent and received) for perception measurement.
  • the perception measurement signal may include, but is not limited to, at least one of Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), multipath angle of arrival, multipath angle of departure, multipath delay, and Doppler frequency.
  • RSRP Reference Signal Received Power
  • RSRQ Reference Signal Received Quality
  • multipath angle of arrival multipath angle of departure
  • multipath delay multipath delay
  • Doppler frequency Doppler frequency
  • the perceptual measurement accuracy may include, but is not limited to, at least one of perceptual resolution and perceptual error.
  • the perception resolution refers to the ability to distinguish multiple perception targets from different dimensions.
  • the perception resolution may include distance resolution, velocity resolution, angle resolution, etc.
  • the perception range refers to the effective range of a specific perception parameter under the premise of meeting certain perception performance indicators (such as perception accuracy).
  • the perception range may include but is not limited to the perception distance range, perception speed range, perception angle range, etc.
  • the perception delay is used to quantitatively describe the real-time requirements of the perception service.
  • the perception delay can be the maximum delay from generating a perception service request to feeding back a perception result.
  • the perception update frequency is the reciprocal of the time interval between two adjacent perception results.
  • the computing subtask configuration may include but is not limited to at least one of data processing method, data processing delay, computing accuracy, and computing power information.
  • the data processing method may include at least one of denoising, privacy protection, standardization, and normalization.
  • the data processing delay is used to indicate the overall delay of data collection and data calculation.
  • the calculation accuracy is used to indicate the data acquisition accuracy and the overall accuracy of data calculation.
  • the computing power information may include at least one of computing power size and computing power type.
  • the computing subtask configuration may include but is not limited to at least one of model complexity, model training time, model inference time, model identification, model download address, data source information (or data source address), computing power, and computing type.
  • the model complexity refers to the complexity of the data that the model can fit.
  • Task type Multi-tasking.
  • task feedback time (such as 10s, 20s...); accuracy (such as 95%, 90%...);...
  • Subtask type perception subtask.
  • Perception subtask configuration information perception measurement mode (such as UE self-transmitting and receiving, other UE transmitting and UE receiving, base station transmitting and UE receiving, UE transmitting and base station receiving, base station transmitting and base station receiving, etc.), perception purpose (such as surrounding environment monitoring), etc.
  • perception measurement mode such as UE self-transmitting and receiving, other UE transmitting and UE receiving, base station transmitting and UE receiving, UE transmitting and base station receiving, base station transmitting and base station receiving, etc.
  • perception purpose such as surrounding environment monitoring
  • Subtask type Computational subtask
  • Computing subtask configuration information data processing method (such as denoising, privacy protection, standardization, normalization%), data processing delay (such as 10s, 20s%), etc.
  • the task template here is a framework description without specific numerical description.
  • the task instance is obtained after the UE fills it in or the TM combines it with the task strategy or task quality information to translate it.
  • Task instance refers to an ongoing task.
  • the network will assign relevant parameters or information to the ongoing task. These parameters or information are task context. Considering that different networks require different task information, different network elements may store different task contexts for the same task instance.
  • Task session refers to the process of communication between a UE and a TM, or the process of communication between the UE, the TM, and related subtask functions.
  • a task session can correspond to one or more subtask sessions (a subtask session refers to the process of communication between the TM and the subtask function).
  • 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.
  • a task session is a network resource established between the UE and the TM and related subtask functions in the operator's network.
  • a task session can sometimes also be called a task connection or a task bearer.
  • a task session or a subtask session can sometimes also be implemented by a protocol data unit (PDU) session.
  • PDU protocol data unit
  • the task session in this application is different from the PDU session in the prior art (i.e., the data channel between the UE and the UPF).
  • the UE wants to use the perception service, the UE will establish a PDU session (the data channel between the UE and the UPF).
  • the UPF may adopt some non-standard methods to transfer it to the perception execution node.
  • the task session identifier is used to identify the task session and can be allocated by the UE and sent to the network, or allocated by the TM.
  • the subtask session identifier is used to identify the subtask session.
  • the task session identifier and the subtask identifier have a one-to-one mapping relationship or a one-to-many mapping relationship (a task is a combined task).
  • the subtask session identifier can be allocated by the UE and sent to the network, or the subtask session identifier can be allocated by the TM, subtask management, or subtask function.
  • the target task or subtask in the embodiment of the present application is a task that is transmitted through a task session or a subtask session, and the transmission here can be the transmission of signaling or the transmission of data.
  • the subtask functions mentioned in this application may be, but are not limited to, terminal devices, access network devices, or independently deployed execution units, etc.
  • the TM function is a core network element that can be used to implement one or more of the following functions: task verification, task template generation, task translation or disassembly, task management, task ID or task session ID allocation, task slicing or task DNN allocation, subtask management function or subtask function selection.
  • Task verification refers to verifying whether a task is a legitimate task requested by an authorized or permitted task consumer or requester (including but not limited to UE and AF). Task verification includes at least one of the following: verifying whether the AF allows the task template request, whether the task request comes from an authorized or permitted UE (whether the UE has a task contract), whether the task request comes from an authorized or permitted AF (depending on whether there is a task agreement between the TM and the AF), and whether the task exceeds the upper limit of the number of tasks associated with the UE or AF.
  • the task verification function can be implemented by the NEF.
  • Task template generation refers to the process of determining a task template through negotiation with the AF. This template describes a customized task for the UE, similar to a questionnaire. The requester expresses their task requirements by selecting required or optional parameters.
  • the task template may include at least one of a task template identifier, task description information, task QoE requirements, task strategy or task quality information, and task parameters, wherein the task template identifier is used to identify the task template.
  • Tasks of different task types may have one or more task templates.
  • the task translation or decomposition refers to translating or decomposing the task request into task instances, which are ongoing tasks.
  • the task instance includes at least one of the following:
  • Task type used to indicate whether the task is a single task, a combined task, or multiple tasks.
  • the single task is any one of communication, perception, and computing, and the combined task is any combination of the above tasks.
  • Task strategy or task quality information which is used to indicate the service quality requirements of the task.
  • Security-related parameters information used to encrypt transmitted signaling or data.
  • Subtask type used to indicate the type of subtask.
  • the subtask type may include at least one of a perception subtask, a computation subtask, and an AI subtask.
  • Subtask strategy or subtask quality information used to indicate the service quality requirement of the subtask.
  • the subtask strategy or subtask quality information is a perception subtask configuration value (including specific information).
  • the subtask strategy or subtask quality information is the computing subtask configuration value (including specific information).
  • the subtask strategy or subtask quality information is the AI subtask configuration value (including specific information).
  • the subtask timing relationship includes at least one of the subtask execution order and the subtask bearer establishment order.
  • the subtask execution order is used to indicate the timing relationship of subtask execution, which includes at least one of the following implementation methods 1 and 2.
  • Method 1 informs the subsequent subtask execution function of the information of the previous subtask execution node.
  • Method 2 serves as the control node for task execution.
  • the execution function of the previous subtask informs TM of the result of the previous subtask, and TM informs the execution function of the subsequent subtask of the result of the previous subtask.
  • a task includes a perception subtask and a computing subtask.
  • TM determines that the perception subtask is a preceding subtask, then TM informs the computing function of the perception function address. After the computing function receives data from the perception function, the computing function can start executing the computing subtask.
  • the subtask bearer establishment order is used to indicate the temporal relationship of subtask bearer establishment, which may include but is not limited to at least one of random establishment, concurrent establishment, establishment according to priority, etc.
  • subtask temporal relationship may be a part of the subtask strategy or subtask quality information.
  • the task instances can also be classified as follows, that is, the task instances can include general parameters and special parameters.
  • the general parameters are a description of the service quality requirements of the complete task, and include at least one of task description information, task type, task strategy or task quality information, and security-related parameters.
  • the dedicated parameter is a description of the service quality requirement of the specifically disassembled subtasks, and the dedicated parameter includes at least one of the subtask type, subtask strategy or subtask quality information, and subtask execution order.
  • the TM determines the task strategy or task quality information, subtask strategy or subtask quality information
  • its implementation method may include at least one of the following methods 1 and 2.
  • Method 1 Obtain the task policy or task quality information, subtask policy or task quality information from the PCF or a function responsible for policy billing.
  • Mode 2 Determine the task policy or task quality information, subtask policy or subtask quality information according to information obtained from the PCF or the policy charging function.
  • the task identifier or task session identifier allocation may include allocating a task identifier or a task session identifier, and allocating a subtask identifier or a subtask session identifier.
  • the task slice or task DNN allocation may include allocating task slices or subtask DNNs, and allocating subtask slices or subtask DNNs.
  • the subtask management function or subtask function selection refers to the TM selecting a subtask management function or subtask function that can meet the subtask quality requirements. For example, the TM may query the NRF, UDM, or UDR to determine the appropriate subtask management function or subtask function, or the TM may determine the appropriate subtask management function or subtask function based on stored or maintained information (such as whether the task is supported, computing power, etc.).
  • the task processing method includes the following steps:
  • Step 101 A first network element receives a first message sent by a second network element, where the first message is used to request the release of a target task or a subtask of the target task.
  • Step 102 The first network element performs a release operation on the target task or a subtask of the target task according to the first message;
  • the target task includes at least one subtask, and the subtask of the target task includes at least one of the following:
  • Perception subtask computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, Internet Protocol (IP) multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.
  • AI artificial intelligence
  • IP Internet Protocol
  • IMS multimedia subsystem
  • the first message may be used to request the release of a target task, or the first message may be used to request the release of a subtask of the target task.
  • the first network element may perform a release operation on the target task, or the first network element may perform a release operation on a subtask of the target task.
  • the first message is used to request the release of a target task
  • the first network element may perform a release operation on the target task or a subtask of the target task.
  • the first message may be used to request the release of a subtask of the target task, and the first network element may perform a release operation on the subtask of the target task.
  • the subtask of the target task may include a perception subtask
  • the first message may be used to request the release of the perception subtask, and the first network element may perform a release operation on the perception subtask
  • the subtask of the target task may include a computing subtask
  • the first message may be used to request the release of the computing subtask
  • the first network element may perform a release operation on the computing subtask
  • the subtask of the target task may include an artificial intelligence (AI) task
  • AI artificial intelligence
  • a task can refer to an integrated service, including communication, information, interpersonal communication, and computing, or a collection of integrated services, provided on-demand by a network system (such as a 6G network system) based on external service requests (including services requested by UEs, over-the-top (OTT) services, or services requested by AFs).
  • a task is composed of subtasks, which can also be described as a service, business, or event.
  • a subtask of a task can be described as a task within a service, business, or event.
  • a subtask can be a service or task within an integrated service including communication, information, interpersonal communication, and computing.
  • the subtasks in the embodiments of the present application include at least one of the following types: a perception subtask (or described as a perception task), a computing subtask (or described as a computing task), an artificial intelligence AI subtask (or described as an AI task), a data subtask (or described as a data task), a positioning subtask (or described as a positioning task), a communication subtask (or described as a communication task), an IP Multimedia Subsystem (IMS) subtask (or described as an IMS task); for another example, the subtasks may also include but are not limited to computing subtasks, information processing subtasks (or described as information processing tasks), multimedia subtasks (or described as multimedia tasks), immersive subtasks (or described as immersive tasks), communication subtasks, etc.
  • the computing subtasks include AI computing tasks and non-AI computing tasks; the information processing subtasks include positioning information processing, synaesthesia information processing, etc.; the immersive subtasks include extended reality (XR) tasks, virtual reality (VR) tasks, etc.
  • the subtasks can be understood as completing an independent function, with multiple subtasks combined to support the completion of a single task.
  • a task can be a combination of multiple functions or subtasks, such as an automated parking task or an environmental reconstruction task. These tasks require not only computational subtasks but also positioning subtasks, and may also require AI subtasks. Multiple functions are combined to complete a single task.
  • the target task may include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.
  • the first network element can be a newly added network element, such as a task management (TM) network element, or it can be jointly set up with the network elements in the core network (such as AMF, SMF, PCF), that is, the function of the first network element is realized through the network elements in the core network;
  • the second network element can be a device outside the communication network, such as an application function (AF).
  • TM task management
  • AF application function
  • the target task may be an established task that meets at least one of the following conditions: a subtask management function or a subtask execution function corresponding to the task has allocated corresponding resources to the task; and a task context for the task has been established.
  • the release operation may include: deleting the task; releasing the allocated task resources; deleting the subtasks of the target task; deleting the task context; deleting the subtask management function corresponding to the target task; or deleting the address of the subtask execution node corresponding to the target task, etc.
  • the release operation can be used to release the resource occupation related to the task or subtask, so that other tasks or subtasks can use the released resources, which include: communication resources, computing resources or data resources, etc.; or, the release operation can be used to delete information related to the task strategy in the task or subtask.
  • the first message may be a task release request message, a task resource release request message, a service release request message, or a business release request message, etc., which is not limited in this embodiment.
  • release request and release execution in the related art are only for communication resources or a single type of network resources.
  • the embodiment of the present application can realize the release of multiple subtasks of the target task through a signaling message (such as the first message).
  • the embodiments of the present application can solve the problem of how the network releases the network resources allocated for a task when a second network element (such as AF or OTT) initiates a release request, aiming to rationally utilize resources and provide the possibility of meeting the task requirements of a large number of second network elements.
  • the embodiments of the present application can support the release of resources allocated to the task by performing a release operation on the target task or a subtask of the target task, thereby increasing the availability of network resources.
  • the AF initiates a task release request and indicates the release reason and release type.
  • TM performs task release operations, including at least one of the following: releasing task resources (such as one or more of perception, computing, and AI resources), deleting subtasks, and deleting task contexts.
  • releasing task resources such as one or more of perception, computing, and AI resources
  • deleting subtasks and deleting task contexts.
  • the first network element is a TM and the second network element is an AF.
  • the TM can be a newly added TM network element, or network elements in the core network (such as AMF, SMF, PCF, NEF) can be enhanced to implement the functions of the TM.
  • the PCF and TM are not limited to being co-located.
  • the AF initiates a task request to the PCF, and the PCF is responsible for all or part of the functions of the TM.
  • control information can be transmitted through one or more of the following: task-related radio resource control (RRC) (which can also be subtask-related radio resource control RRC), task-related non-access stratum (NAS) signaling (which can also be subtask-related non-access stratum NAS signaling), or task-related radio signaling bearer (SRB) (which can also be subtask-related radio signaling bearer SRB).
  • RRC task-related radio resource control
  • NAS task-related non-access stratum
  • SRB task-related radio signaling bearer
  • the embodiments of the present application do not limit whether the TM responsible for routing and the TM responsible for task management are the same functional node or different functional nodes.
  • the embodiments of the present application do not limit the data transmission method between the AF and the TM, and between the TM and the subtask function.
  • the data between the AF and the TM, and between the TM and the subtask function can be transmitted through one or more of the following: the task data protocol data unit of the Packet Data Convergence Protocol (PDCP) (can also be the subtask PDCP), the task data protocol data unit of the Service Data Adaptation Protocol (SDAP) (can also be the subtask SDAP), the task data radio bearer (DRB) (can also be the subtask DRB), or the task quality of service QoS flow (can also be the subtask QoS flow), the Session Initialization Protocol (SIP), the Hypertext Transfer Protocol (HTTP), and the Transport Layer Security (TLS) protocol.
  • PDCP Packet Data Convergence Protocol
  • SDAP Service Data Adaptation Protocol
  • DRB task data radio bearer
  • QoS flow can also be the subtask QoS flow
  • SIP Session Initialization Protocol
  • HTTP Hypertext Transfer Protocol
  • TLS Transport Layer Security
  • a first network element receives a first message sent by a second network element, wherein the first message is used to request the release of a target task or a subtask of a target task; the first network element performs a release operation on the target task or a subtask of the target task; wherein the subtask of the target task includes at least one of the following: a perception subtask, a computing subtask, an artificial intelligence AI subtask, a data subtask, a positioning subtask, a communication subtask, an IP multimedia subsystem IMS subtask, an information processing subtask, and an immersive subtask.
  • the embodiment of the present application can also support the release of multiple subtasks of the target task through one signaling message.
  • the release operation includes at least one of the following:
  • the task context corresponding to the target task or the subtask of the target task may include the address of the subtask management function or the address of the subtask execution function corresponding to the target task.
  • the resource corresponding to the target task or the subtask of the target task may refer to a network resource established based on the target task or the subtask of the target task.
  • releasing the resources corresponding to the target task or the subtask of the target task may include sending a task release request to the subtask management function or subtask execution function corresponding to the target task, requesting the subtask management function or subtask execution function to release the resources allocated to the subtask of the target task.
  • deleting the task context corresponding to the target task or the subtask of the target task may include deleting the stored task context of the target task or the subtask of the target task.
  • the stored task context includes a task context stored locally by the first network element or a task context stored on another network element.
  • the first network element may directly delete the locally stored task context, or the first network element may send a deletion request to the network element storing the task context to delete the task context stored on the other network element.
  • the resources can be reasonably released after the task is completed.
  • the released task resources can be used for the needs of subsequent tasks, which is beneficial to network resource management; or, deleting the task context corresponding to the target task or the subtask of the target task can avoid the subtask occupying resources.
  • the first message carries at least one of the following:
  • Task description information used to indicate the type of the target task
  • Task quality information QoT used to indicate the service quality requirement of the target task
  • a task identifier or task session identifier, is used to identify the target task
  • An identifier of a subtask management function used to indicate a subtask management function for managing subtasks in the target task or a subtask function for executing subtasks in the target task;
  • Subtask requirement information used to indicate the service quality requirements of the subtasks in the target task
  • a subtask identifier or subtask session identifier, is used to identify a subtask in the target task
  • third indication information for indicating a resource release type
  • the task template is used to represent task requirement information.
  • the identifier of the task template may implicitly indicate the resource type included, and the resource type included may include at least one of communication resources, perception resources, computing resources, and AI resources.
  • the indication information for indicating the reason for requesting to release resources may indicate: regular release, normal release, temporary release, network switching, insufficient resources, semantic error or grammatical error, etc.
  • the task description information can be used to indicate the target type of the task, that is, to indicate what kind of task it is. For example, if the task is to perceive the traffic congestion situation in the target area, the task description information is "traffic congestion situation"; if the task is to park the vehicle at a suitable location or a designated location, the task description information is "automatic parking”; or it can be used to identify specific task parameters, including at least one of the following: task DNN, task-associated S-NSSAI, AF identification and APP identification.
  • DNN information can be used to characterize the DNN assigned to a task
  • slice information can be used to characterize the slice assigned to a task.
  • Task strategy information or task quality information can be used to indicate the service quality requirements of the task, including at least one of the following: task feedback time or task latency: used to indicate the upper limit of the time from the task consumer or requester (for example, a terminal or a second network element, etc.) initiating a task request to receiving a task response; task accuracy: used to indicate the probability of successful completion of the task or the degree to which the terminal's expected value or the task provider's promised value is consistent with the actual value; comprehensive energy consumption: used to indicate the energy consumption required to complete the task, including the energy consumption of the network or terminal, and the network includes but is not limited to the core network and the access network; data density: used to indicate the number of bits transmitted per unit time.
  • the task identifier can be used to identify the task.
  • the subtask management function identifier can be the identifier of the function used to manage the subtask.
  • the subtask execution function identifier can be the identifier of the function used to execute the subtask.
  • the subtask policy information is used to indicate the quality of service requirements of the subtask.
  • the subtask requirement information can be used to indicate the requirements of the subtask.
  • a task template can be a description of a customized task, which can be understood as a questionnaire. The requester "checks" certain required or optional parameters on the questionnaire to express their requirements for the task.
  • the task template can include at least one of the following: a task template identifier, used to identify the task template; task description information; task quality information; task strategy information; and task parameters.
  • Task parameters These are parameters used to indicate the task, and may include subtask configuration information. For example, if the target task includes both a perception task and a computation task, the task parameters include both the perception task configuration information and the computation task configuration information.
  • the subtask execution function may also be described as a subtask function or a subtask execution node.
  • the identifier of the task template may be simply described as a task template indication.
  • the indication information for indicating the subtask execution order may be simply described as a subtask execution order indication.
  • the task description information may also be simply described as a task description; the task strategy information may also be simply described as a task strategy; the subtask strategy information may also be simply described as a subtask strategy; and the DNN information may also be simply described as a DNN.
  • the slice information may include S-NSSAI.
  • the identifier of the subtask management function may include, but is not limited to, an identifier (ID), an Internet Protocol (IP) address, and a fully qualified domain name (FQDN).
  • ID identifier
  • IP Internet Protocol
  • FQDN fully qualified domain name
  • the identifier of the subtask execution function may include, but is not limited to, an ID, an IP address, and an FQDN.
  • the second network element can obtain from the first network element the subtasks included in the target task and the corresponding subtask execution functions.
  • the second network element may receive an execution result from the corresponding subtask execution function, for example, the execution result indicates that the subtask function has insufficient resources and cannot meet the subtask quality.
  • the second network element can send a first message to the first network element to request the release of the corresponding subtask.
  • the first message can carry an identifier of the subtask execution function to request the release of the corresponding subtask.
  • the first network element can determine the target task or the subtask of the target task through one or more of the task description information, DNN information, slicing information, task strategy information, QoT, task identifier, task template identifier, subtask identifier, subtask management function identifier, subtask execution function identifier, subtask requirement information and subtask strategy information carried by the first message, and then perform a release operation on the target task or the subtask of the target task.
  • the first network element can determine the target task through one or more of the task description information, DNN information, slicing information, task strategy information, QoT, task identifier, and task template identifier carried by the first message, and then perform a release operation on the target task or a subtask of the target task.
  • the first network element can determine the target task through one or more of the task description information, DNN information, slicing information, task strategy information, QoT, task identifier, and task template identifier carried by the first message, and determine one or more subtasks of the target task through one or more of the subtask management function identifier, subtask execution function identifier, subtask identifier, subtask requirement information, and subtask strategy information carried by the first message, and then perform a release operation on the one or more subtasks.
  • the first network element may determine one or more subtasks of the target task through the identifier of the task template or the subtask requirement information or the subtask strategy information carried in the first message, and then perform a release operation on the one or more subtasks.
  • the first network element may determine the resource type through the identifier of the task template carried in the first message, and further determine the type of released resources.
  • the first network element may release the resources of the subtasks in the order in which the subtasks are executed, using the indication information for indicating the order in which the subtasks are executed carried in the first message.
  • the first network element may learn the reason why the second network element requests to release resources through indication information carried in the first message and used to indicate the reason for requesting to release resources.
  • the first network element may determine the type of released resources through indication information carried in the first message for indicating the type of resource release.
  • the third indication information indicates at least one of the following:
  • Release perception resources release computing resources; release artificial intelligence (AI) resources; release predefined resource combinations; release all resources.
  • AI artificial intelligence
  • the predefined resource combination may include a resource combination consisting of at least one of communication resources, perception resources, computing resources and AI resources.
  • the indication information for indicating the resource release type may indicate at least one of the following:
  • Release one or more resources such as instructing to release at least one of perception resources, computing resources, and AI resources;
  • the predefined resource combination may be sensing resources + computing resources;
  • Release all resources such as indicating to release all resources.
  • all resources include perception resources+computing resources+AI resources+data storage resources.
  • the first message further includes fourth indication information used to instruct the second network element to trigger sending the first message based on at least one of the following:
  • the second network element expects to release the target task or a subtask of the target task
  • the second network element receives a request message sent by the terminal for requesting to release the target task or a subtask of the target task;
  • the timer corresponding to the target task times out.
  • the reason why the second network element expects to release the target task or the subtask of the target task may include at least one of the following: the second network element closes the application associated with the target task; the available resources of the second network element are less than a preset threshold; the second network element cannot provide relevant data of the target task.
  • the second network element may start a timer, and when the timer times out, the second network element may send a first message to the first network element.
  • the conditions for the AF to send a task release request include at least one of the following:
  • AF expects to release tasks, including at least one of the following: AF closes the application (Application, APP), AF resources are insufficient, and AF privacy is restricted.
  • the AF receives a task release request from the UE through the application layer.
  • the task information included in the task release request is consistent with the task information carried in the first message.
  • the task information included in the task release request and the task information carried in the first message are information about the same task.
  • AF The timer maintained by AF times out. AF will start a timer after the task is successfully established. When the timer times out, AF will initiate a task release request.
  • the second network element when the second network element expects to release the target task or the subtask of the target task, the second network element sends a first message to the first network element, so that the second network element can actively request to release the target task or the subtask of the target task; or, when the second network element receives a request message sent by the terminal to request the release of the target task or the subtask of the target task, the second network element sends a first message to the first network element, so that the second network element can send a request to release the target task or the subtask of the target task based on the request of the terminal; or, when the timer corresponding to the target task times out, the second network element sends a first message to the first network element, so that the second network element can request to release the target task or the subtask of the target task based on the timeout of the timer corresponding to the target task.
  • the second network element when the second network element meets the first condition, the second network element expects to release the target task or a subtask of the target task:
  • the first condition includes at least one of the following:
  • the second network element closes an application associated with the target task; available resources of the second network element are less than a preset threshold; and the second network element cannot provide relevant data of the target task.
  • the second network element cannot provide relevant data of the target task, which may indicate that the privacy of the second network element is limited.
  • the method further includes:
  • the first network element sends a second message corresponding to the first message to the second network element
  • the second message is used to indicate whether the release operation is executed successfully or fails.
  • the second message can be a task release response message; taking the first message as a task resource release request message as an example, the second message can be a task resource release response message; taking the first message as a service release request message as an example, the second message can be a service release response message; taking the first message as a business release request message as an example, the second message can be a business release response message.
  • the first network element sends a second message corresponding to the first message to the second network element; the second message is used to indicate that the release operation is executed successfully or the release operation fails, so that the second network element can obtain the release result of the target task or the subtask of the target task through the second message.
  • the second message carries fifth indication information, where the fifth indication information is used to indicate at least one of the following:
  • the target task is in the execution state; the target task does not exist; the target task is not authorized; there is no task contract for the target task; the subtask of the target task is in the execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.
  • the non-existence of the target task can be understood as the target task requested to be released by the second network element has not been established or the first network element has already released the target task locally.
  • the first network element can determine that the target task does not exist when it is determined that the network has not allocated network resources for the target task.
  • the non-existence of a subtask of the target task can be understood as the subtask of the target task requested to be released by the second network element has not been established or the first network element has already released the subtask of the target task locally.
  • the first network element can determine that the target task does not exist when it is determined that the network has not allocated network resources for the subtask of the target task.
  • the target task is not authorized, which can be understood as no service level agreement on the target task is signed between the first network element and the second network element, or no service level agreement is signed between the second network element and the first network element.
  • the first message can be used to request the release of the target task, and the first indication information is used to indicate at least one of the following: the target task is in an execution state; the target task does not exist; the target task is not authorized; the target task has no task contract; the subtask of the target task is in an execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.
  • the first message can be used to request the release of a subtask of the target task
  • the first indication information is used to indicate at least one of the following: the target task is in an execution state; the target task does not exist; the target task is not authorized; the target task has no task contract; the subtask of the target task is in an execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.
  • the first network element performs a release operation on the target task or a subtask of the target task, including the first network element determining a subtask management function or a subtask execution function corresponding to the target task;
  • the first network element sends a third message to the subtask management function or the subtask execution function, where the third message is used to request the release of the subtask of the target task.
  • the first network element may determine the subtask management function or subtask execution function corresponding to the target task according to at least one of the following:
  • the subtask management function or subtask execution function identifier stored in the task context of the target task.
  • the first network element stores the task context when the task is established.
  • the task context includes the association relationship between the target task and the subtask management function or subtask execution function.
  • the first network element can query the NRF, UDM or UDR to determine the appropriate subtask management function or subtask function, or the first network element can determine the appropriate subtask management function or subtask function based on stored or maintained information (such as whether the task is supported, the size of computing power, etc.).
  • the first network element may reject the request of the second network element and indicate that the release operation has failed.
  • the first message can be used to request the release of the target task, and the first network element can determine the management function or execution function of all or part of the subtasks of the target task, and send a third message to the determined subtask management function or subtask execution function.
  • the first message can be used to request the release of one or more subtasks of the target task, and the first network element can determine the management function or execution function of the one or more subtasks, and send a third message to the determined subtask management function or subtask execution function.
  • the third message may be generated by triggering the first message.
  • the first network element After receiving the first message, the first network element triggers the generation of the third message and sends the third message to the subtask management function or the subtask execution function.
  • the subtask management function corresponding to the target task can also be described as the management function or control function of the subtask of the target task; the subtask execution function corresponding to the target task can also be described as the execution function or execution node of the subtask of the target task.
  • the first network element determines the subtask management function or subtask execution function corresponding to the target task; the first network element sends a third message to the subtask management function or subtask execution function, and the third message is used to request the release of the subtask of the target task, so that the first network element can release the subtask of the target task through the subtask management function or subtask execution function corresponding to the target task.
  • the third message includes at least one of the following: an identifier of the second network element; a perception subtask identifier; a perception execution function address; perception strategy information; perception requirement information; or
  • the third message includes at least one of the following: an identifier of the second network element; an identifier of the computing subtask; an address of a computing execution function; computing strategy information; computing requirement information; or
  • the third message includes at least one of the following: an identifier of the second network element; an AI subtask identifier; an AI resource node address; AI strategy information; and AI requirement information.
  • the network system may include a first network element, a second network element, a third network element, a fourth network element, and a fifth network element.
  • the first network element in the embodiment of the present application may be used for task management.
  • the first network element may include a newly added network element TM, or may be co-located with an existing network element (e.g., AMF, SMF, PCF).
  • the second network element can be a third-party server whose content or services are built on top of the basic telecommunications service, for example, an OTT server; or it can be an application function, such as an Application Function (AF).
  • OTT refers to the provision of various application services to users via the Internet.
  • the third network element can be located between the 6G core network and external third-party application functions (possibly also some internal AFs). It is responsible for exposing network capabilities and internal network information. All external applications that want to access internal data of the 6G core network must go through the TNE.
  • the TNE provides corresponding security guarantees to ensure the security of external applications in the 3rd Generation Partnership Project (3GPP) network, and provides functions such as external application demand or target customization capability exposure, mobility status event subscription, and AF request distribution.
  • the TNE can include network exposure functions such as NEF.
  • the fourth network element can determine the required AI resources, AI units, and data sources based on the AI service category and the internal requirements of the AI service.
  • the fourth network element may include AI service management functions.
  • the fifth network element may determine the required sensing resources, sensing units and data sources according to the sensing service category and the internal requirements of the sensing service.
  • the fifth network element may include a sensing management function.
  • the first network element (such as TM) may be a 3GPP internal network element, and may be used to implement one or more of the following functions:
  • Task Verification Verify whether a task is a legitimate task requested by a legitimate UE or AF.
  • Task verification includes at least one of the following: whether the AF allows the task template request, whether the task request comes from a legitimate UE (whether the UE has a task contract), whether the task request comes from a legitimate AF (based on whether there is a task agreement between the TM and the AF), and whether the task exceeds the upper limit of the number of tasks associated with the UE or AF.
  • the task verification function can be implemented by the NEF.
  • Task Template Generation The task template is determined through negotiation with the AF.
  • the task template is a description of a customized task that the network assigns to the UE. It can be thought of as a questionnaire, where the requester "checks" some required or optional parameters to express their requirements for the task.
  • the task template contains at least one of the following:
  • Task template identifier used to identify the task template
  • Task translation or decomposition Translate or decompose the task request into a task instance, which is an ongoing task.
  • the task instance includes at least one of the following:
  • Task type used to indicate whether the task is a single task, a combined task, or multiple tasks.
  • the single task is any one of communication, perception, computing, and AI.
  • the combined task is any combination of the above tasks.
  • Security-related parameters which are information used to encrypt transmitted signaling or data
  • Subtask type used to indicate the type of subtask, including at least one of the following: perception, calculation, AI;
  • Subtask policy or QoS used to indicate the quality of service requirements of the subtask.
  • the subtask policy or QoS is the perception subtask configuration value (including specific configuration information);
  • the subtask policy or QoS is the computing subtask configuration value (including specific configuration information);
  • the subtask policy or QoS is the AI subtask configuration value (including specific configuration information);
  • Subtask execution order which indicates the temporal relationship of subtask execution and includes at least one of the following implementation methods:
  • TM informs the subsequent subtask execution node of the information of the previous subtask execution node
  • TM serves as the central control node for task execution.
  • the previous subtask execution node informs TM of the previous subtask result, and TM informs the subsequent subtask execution node of the previous subtask result.
  • a task includes a perception subtask and a computing subtask.
  • TM determines that the perception subtask is a preceding subtask, then TM informs the computing execution function of the address of the perception execution function. After the computing execution function receives data from the perception execution function, the computing execution function can start executing the computing subtask.
  • Subtask bearer establishment order used to indicate the timing relationship of subtask bearer establishment, including at least one of:
  • the subtask timing relationship may be part of a subtask strategy or QoS.
  • task instances can be further categorized as follows: they contain general parameters and specific parameters.
  • General parameters describe the QoS requirements for the complete task and include at least one of the following: task description, task type, task policy or QoS, and security-related parameters.
  • Specific parameters describe the QoS requirements for specific subtasks and include at least one of the following: subtask type, subtask policy or QoS, and subtask execution order.
  • TM can also use any of the following methods to determine the task policy or QoS, subtask policy or QoS:
  • the task policy or QoS, subtask policy or QoS is determined according to information obtained from the PCF or the policy charging function.
  • Allocate task slices or task DNNs and optionally, subtask slices or subtask DNNs;
  • the TM selects a subtask management function or subtask execution function that can meet the subtask QoS. Specifically, the TM can query the NRF, UDM, or UDR to determine the appropriate subtask management function or subtask execution function, or the TM can determine the appropriate subtask management function or subtask execution function based on stored or maintained information (such as whether the task is supported, computing power, etc.).
  • a task may refer to a comprehensive service, or a collection of comprehensive services, including communication, information, interawareness, and computing, provided on demand by a network system (such as a 6G network system) based on external service requests (including UE, OTT, or AF).
  • Task management refers to the management process of providing communication functions and other additional network system functions (such as positioning, interawareness, computing, etc.) with the goal of responding to external service requests.
  • the task template can be used to indicate the requirements of the UE, AF or network for the task.
  • the task template may include at least one of the following:
  • Task description information used to indicate the target type of the task, that is, to indicate what kind of task it is. For example, if the task is to perceive the traffic congestion in the target area, the task description information is "traffic congestion"; if the task is to park the vehicle at a suitable location or a designated location, the task description information is "automatic parking”; or, used to identify specific task parameters, including at least one of the following: DNN, Single Network Slice Selection Assistance Information (S-NSSAI), AF identifier, APP identifier.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • Task QoE description information used to indicate the level of user experience achieved.
  • Task strategy information or task QoS description information which is used to indicate the service quality requirements of the task and includes at least one of the following:
  • Task feedback time or task delay used to indicate the time limit from when the UE or AF initiates a task to when it receives a task response;
  • Task accuracy used to indicate the probability of successfully completing a task
  • Data density used to indicate the number of bits transmitted per unit time.
  • Task parameters Parameters used to indicate a specific task, which may include subtask configuration information. For example, if a task includes a perception subtask and a computation subtask, the task parameters include the perception subtask configuration and the computation subtask configuration.
  • the perception subtask configuration includes at least one of the following:
  • Perception measurement mode This may include at least one of the following modes: 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
  • receiving refers to receiving measurement signals and performing measurements.
  • Sensing services may include at least one of the following: long sensing range and high real-time requirements (Delay Critical LSS); long sensing range and low real-time requirements (LSS); short sensing range and low real-time requirements (Delay Critical SSS); and short sensing range and low real-time requirements (SSS). These services may also be represented by numbers, letters, or other character strings.
  • Perception purpose may include one or more applications that require perception services supported by the perception device, such as respiratory monitoring, surrounding traffic environment monitoring, etc.
  • Perception measurement signal indicates the signal supported by the perception device (which can be sent or received, or both) for perception measurement.
  • the perception device 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.
  • RSRP Reference Signal Received Power
  • RSRQ Reference Signal Received Quality
  • multipath angle of arrival multipath angle of departure
  • multipath delay multipath delay
  • Doppler frequency 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.
  • 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 used to indicate the overall delay between data collection and data calculation
  • Calculation accuracy used to indicate the accuracy of data collection and the overall accuracy of data calculation
  • Computing power information includes at least one of the following: computing power size and computing power type.
  • the AI subtask configuration includes at least one of the following:
  • Model complexity refers to the computational complexity of the model, such as the number of floating point operations (FLOPs) or multiplications and additions required; model training latency; model inference latency; model identification; model download address; data source information (or data source address); computing power; and calculation type.
  • FLOPs floating point operations
  • the framework of the automatic parking task template includes general parameters, perception task parameters, and calculation task parameters.
  • the task template is as follows:
  • Sensing task parameters Sensing measurement mode (UE sends and receives independently, other UE sends and the UE receives, base station sends and the UE receives, UE sends and the base station receives, base station sends and the base station receives); sensing purpose (surrounding environment monitoring); ...
  • Computing task parameters data processing method (denoising, privacy protection, standardization, normalization, etc.); data processing delay (10s, 20s, etc.);
  • the task template here is a framework description (without specific numerical description), which is filled by the UE or AF or translated by the TM in combination with the task policy or QoS description information to obtain a task instance.
  • a task instance may refer to an ongoing task with a corresponding task context.
  • Different network elements may store different task contexts for the same task instance.
  • a task session can refer to the communication process between a UE and a TM, along with related subtask functions.
  • a task session can correspond to one or more subtask sessions (a subtask session refers to the communication process between the TM and a subtask function).
  • Establishing a task session establishes a data transmission channel between the UE, the TM, and related subtasks.
  • a task session is a network resource established between the UE, the TM, and related subtask execution functions in the operator's network.
  • a task session is sometimes also referred to as a task connection or task bearer.
  • the task session identifier can be used to identify the task session, which is allocated by the UE and sent to the network or allocated by the TM.
  • the subtask session identifier is used to identify the subtask session.
  • the task session identifier and the subtask identifier have a one-to-one mapping relationship or a one-to-many mapping relationship (a task is a combined task).
  • the task processing method includes the following steps:
  • Step 201 A second network element sends a first message to a first network element, where the first message is used to request the release of a target task or a subtask of the target task.
  • the subtasks of the target task include at least one of the following:
  • Perception subtask computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.
  • AI artificial intelligence
  • IMS IP multimedia subsystem
  • the first message carries at least one of the following:
  • Task description information data network name (DNN) information; slicing information; task strategy information; task quality information (QoT); task identifier; identifier of the subtask management function; identifier of the subtask execution function; subtask strategy information; subtask requirement information; subtask identifier; task template identifier; first indication information for indicating the subtask execution order; second indication information for indicating the reason for requesting resource release; third indication information for indicating the resource release type;
  • the task template is used to represent task requirement information.
  • the third indication information indicates at least one of the following:
  • Release perception resources release computing resources; release artificial intelligence (AI) resources; release predefined resource combinations; release all resources.
  • AI artificial intelligence
  • the second network element sending the first message to the first network element includes:
  • the second network element When it is determined that the first condition is met, the second network element sends a first message to the first network element;
  • the first condition includes at least one of the following:
  • the second network element expects to release the target task or a subtask of the target task
  • the second network element receives a request message sent by the terminal for requesting to release the target task or a subtask of the target task;
  • the timer corresponding to the target task times out.
  • the second network element when the second network element satisfies the second condition, the second network element expects to release the target task or a subtask of the target task:
  • the second condition includes at least one of the following:
  • the second network element closes an application associated with the target task; available resources of the second network element are less than a preset threshold; and the second network element cannot provide relevant data of the target task.
  • the method further includes:
  • the second network element receives a second message corresponding to the first message sent by the first network element
  • the second message is used to indicate whether the release operation is executed successfully or fails.
  • the second message carries fifth indication information, where the fifth indication information is used to indicate at least one of the following:
  • the target task is in the execution state; the target task does not exist; the target task is not authorized; there is no task contract for the target task; the subtask of the target task is in the execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.
  • this embodiment is an implementation method of the second network element corresponding to the embodiment shown in Figure 2. Its specific implementation method can refer to the relevant description of the embodiment shown in Figure 2. To avoid repetition, this embodiment will not be repeated.
  • the first network element is a TM and the second network element is an AF as an example.
  • the task processing method includes the following steps:
  • Step (1) TM receives the first message
  • the AF sends a task release request message to the TM, which is used to request the network to release the resources allocated for the task.
  • the task release request message includes at least one of the following:
  • Task description information e.g., “traffic congestion,” “environment reconstruction”
  • Task ID or task session ID
  • the identifier of the subtask management function or the subtask execution function (in the form of representation including but not limited to ID, IP address, FQDN);
  • Release reason used to indicate the reason for releasing the task, including at least one of the following: normal release, temporary release, insufficient resources, semantic error, syntax error;
  • Release type including at least one of the following: release only perception resources, release only computing resources, release only AI resources; release all resources.
  • the locally stored context in subsequent operations, after the network element releases the response resources, the locally stored context will be retained, and the resource configuration can be referenced or reused when the same task is established subsequently; if it is other release (including normal release, etc.), the locally retained context will be directly deleted, and it will need to be reconsidered when the same task is established subsequently.
  • the AF can request the network to release resources allocated for the task, or request the network to release resources allocated for a subtask, for example, requesting to release only the sensing resources.
  • the first message can be forwarded to the TM by a third network element.
  • the third network element is located between the 6G core network and external third-party application functions (possibly also some internal AFs), and is responsible for opening network capabilities and internal network information. All external applications that want to access internal data of the 6G core network must go through the third network element.
  • the third network element provides corresponding security guarantees to ensure the security of external applications accessing the 3GPP network, and provides functions such as external application demand or target customization capability opening, mobility status event subscription, and AF request distribution.
  • the third network element is a network opening function, such as NEF.
  • the conditions for the AF to send a task release request message include at least one of the following:
  • AF expects to release the task, including at least one of the following: AF closes the APP, AF resources are insufficient, and AF privacy is restricted.
  • the AF receives a task release request from the UE through the application layer.
  • the task information included in the task release request is consistent with the task information carried in the first message.
  • the task information included in the task release request and the task information carried in the first message are information about the same task.
  • AF The timer maintained by AF times out. AF will start a timer after the task is successfully established. When the timer times out, AF will initiate a task release request.
  • Step (2) TM performs the first operation
  • the TM performs a first operation, including at least one of the following:
  • the TM verifies whether the task release request is a legal request. Specifically, if the TM stores the task identifier, the TM determines that the task release request is legal; if the TM does not store the task identifier and the AF does not have the task contract, the TM determines that the task release request is illegal.
  • the TM may directly reject the task modification request and directly execute step (5).
  • the TM sends a subtask release request to the subtask management function or the subtask execution function.
  • the TM determines the subtask management function or the subtask execution function according to at least one of the following:
  • the subtask management function or subtask execution function identifier stored in the task context.
  • the TM stores the task context when the task is established.
  • the task context includes the association between the task and the subtask management function and/or subtask execution function.
  • the TM directly executes step (5), rejects the AF's request, and indicates that the resources associated with the requested task cannot be released.
  • the TM sends a sensing subtask release request to the sensing management function or the sensing execution function, requesting the release of sensing resources, including at least one of the following: AF identifier, sensing subtask identifier, sensing execution function address, sensing policy, or QoS.
  • the perception management function or the perception execution function sends a perception subtask release response to the TM, indicating whether the perception resources associated with the task are successfully released.
  • the perception subtask release response includes a failure reason, including at least one of: the perception subtask is in use, the perception subtask does not exist, the perception execution function does not exist, and the perception resource does not exist.
  • the TM sends a computing subtask release request to the computing management function or the computing execution function to request the network to release computing resources, including at least one of the following: AF identifier, computing subtask identifier, computing execution function address, computing policy or QoS.
  • the computing management function or computing execution function sends a computing subtask release response to the TM, indicating whether the computing resources associated with the task are successfully released.
  • the computing subtask release response includes a failure reason, including at least one of: the computing subtask is in use, the computing subtask does not exist, the computing execution function does not exist, and the computing resource does not exist.
  • the TM sends an AI subtask release request to the AI management function (e.g., AI service management function, AI resource management function) or AI resource node to request the network to release the AI resource, including at least one of the following: AF identifier, AI subtask identifier, AI resource node address, AI policy, or QoS.
  • AI management function e.g., AI service management function, AI resource management function
  • the AI management function eg, AI service management function, AI resource management function
  • the AI resource node sends an AI subtask release response to the TM, indicating whether the AI resources associated with the task are successfully released.
  • the AI subtask release response may optionally include a failure reason, including at least one of: the AI subtask is in use, the AI subtask does not exist, the AI resource node does not exist, or the AI resource does not exist.
  • the TM After the TM releases the subtask, the connection between the TM and the subtask management function or subtask execution function is disconnected, and the TM deletes the subtask management function or subtask execution function address. When the TM executes the task again, it needs to select the subtask management function or subtask execution function again.
  • TM releases the task context, including at least one of:
  • the TM deletes the saved complete task context.
  • the TM deletes the saved subtask context.
  • the saved task context includes at least one of: the task context stored locally in the TM, and the task context stored in the UDM or UDR.
  • Step (5) TM sends a second message
  • the TM sends a second message to the AF in response to the first message, notifying the AF of the result of the task release.
  • the message optionally carries a failure reason value, indicating at least one of the following: task in progress, task does not exist, task is illegal, task is not signed, subtask is in use, subtask does not exist, subtask execution function does not exist, or subtask resource does not exist.
  • the subtask indicated by the reason value can be one or more of the perception, computing, and AI subtasks.
  • the AF requests to release the task or subtask.
  • the task processing method includes the following process:
  • Step (1) TM receives the first message
  • Step (2) TM performs the first operation
  • FIG5 expands step (3) in detail based on FIG4.
  • the AF requests to release the context.
  • the task processing method includes the following steps:
  • Step (1) same as step (1) in Example 1;
  • Step (2) Same as step (4) in Example 1;
  • Step (3) Same as step (5) in Example 1;
  • the difference from the first embodiment is that here the AF requests the release of the task context, and the TM releases the task context, but the data transmission channel between the TM and the AF remains.
  • the task context includes the association between the task policy or task requirement and the subtask management function or subtask execution function, or the association between the subtask policy or subtask requirement and the subtask management function or subtask execution function.
  • the embodiments of the present application provide a feasible AF-triggered task release process and method, which enables the network to dynamically reclaim resources and can meet the resource requests of a large number of tasks.
  • the task processing method provided in the embodiment of the present application can be executed by a task processing device.
  • the task processing device provided in the embodiment of the present application is described by taking the task processing method executed by the task processing device as an example.
  • FIG. 7 is a structural diagram of a task processing device provided in an embodiment of the present application.
  • the first network element includes the task processing device.
  • the task processing device 300 includes:
  • a receiving module 301 is configured to receive a first message sent by a second network element, where the first message is used to request the release of a target task or a subtask of the target task;
  • An execution module 302 is configured to execute a release operation on the target task or a subtask of the target task according to the first message;
  • the target task includes at least one subtask, and the subtask of the target task includes at least one of the following:
  • Perception subtask computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.
  • AI artificial intelligence
  • IMS IP multimedia subsystem
  • the release operation includes at least one of the following:
  • the first message carries at least one of the following:
  • Task description information data network name (DNN) information; slicing information; task strategy information; task quality information (QoT); task identifier; identifier of the subtask management function; identifier of the subtask execution function; subtask strategy information; subtask requirement information; subtask identifier; task template identifier; first indication information for indicating the subtask execution order; second indication information for indicating the reason for requesting resource release; third indication information for indicating the resource release type;
  • the task template is used to represent task requirement information.
  • the third indication information indicates at least one of the following:
  • Release perception resources release computing resources; release artificial intelligence (AI) resources; release predefined resource combinations; release all resources.
  • AI artificial intelligence
  • the first message further includes fourth indication information used to instruct the second network element to trigger sending the first message based on at least one of the following:
  • the second network element expects to release the target task or a subtask of the target task
  • the second network element receives a request message sent by the terminal for requesting to release the target task or a subtask of the target task;
  • the timer corresponding to the target task times out.
  • the device further comprises:
  • a sending module configured to send a second message corresponding to the first message to the second network element
  • the second message is used to indicate whether the release operation is executed successfully or fails.
  • the second message carries fifth indication information, where the fifth indication information is used to indicate at least one of the following:
  • the target task is in the execution state; the target task does not exist; the target task is not authorized; there is no task contract for the target task; the subtask of the target task is in the execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.
  • the execution module is specifically configured to:
  • a third message is sent to the subtask management function or the subtask execution function, where the third message is used to request the release of the subtask of the target task.
  • the third message includes at least one of the following: an identifier of the second network element; a perception subtask identifier; a perception execution function address; perception strategy information; perception requirement information; or
  • the third message includes at least one of the following: an identifier of the second network element; an identifier of the computing subtask; an address of a computing execution function; computing strategy information; computing requirement information; or
  • the third message includes at least one of the following: an identifier of the second network element; an AI subtask identifier; an AI resource node address; AI strategy information; and AI requirement information.
  • the task processing 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.
  • 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 task processing device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 2 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • FIG8 is a structural diagram of a task processing device provided in an embodiment of the present application.
  • the first network element includes the task processing device.
  • the task processing device 400 includes:
  • a sending module 401 is configured to send a first message to a first network element, where the first message is used to request the release of a target task or a subtask of the target task;
  • the target task includes at least one subtask, and the subtask of the target task includes at least one of the following:
  • Perception subtask computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.
  • AI artificial intelligence
  • IMS IP multimedia subsystem
  • the first message carries at least one of the following:
  • Task description information data network name (DNN) information; slicing information; task strategy information; task quality information (QoT); task identifier; identifier of the subtask management function; identifier of the subtask execution function; subtask strategy information; subtask requirement information; subtask identifier; task template identifier; first indication information for indicating the subtask execution order; second indication information for indicating the reason for requesting resource release; third indication information for indicating the resource release type;
  • the task template is used to represent task requirement information.
  • the third indication information indicates at least one of the following:
  • Release perception resources release computing resources; release artificial intelligence (AI) resources; release predefined resource combinations; release all resources.
  • AI artificial intelligence
  • the sending module is specifically configured to:
  • the second network element When it is determined that the first condition is met, the second network element sends a first message to the first network element;
  • the first condition includes at least one of the following:
  • the second network element expects to release the target task or a subtask of the target task
  • the second network element receives a request message sent by the terminal for requesting to release the target task or a subtask of the target task;
  • the timer corresponding to the target task times out.
  • the second network element when the second network element satisfies the second condition, the second network element expects to release the target task or a subtask of the target task:
  • the second condition includes at least one of the following:
  • the second network element closes an application associated with the target task; available resources of the second network element are less than a preset threshold; and the second network element cannot provide relevant data of the target task.
  • the device further comprises:
  • a receiving module configured to receive a second message corresponding to the first message sent by the first network element
  • the second message is used to indicate whether the release operation is executed successfully or fails.
  • the second message carries fifth indication information, where the fifth indication information is used to indicate at least one of the following:
  • the target task is in the execution state; the target task does not exist; the target task is not authorized; there is no task contract for the target task; the subtask of the target task is in the execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.
  • the task processing 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.
  • 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 task processing device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • an embodiment of the present application further provides a communication device 500, comprising a processor 501 and a memory 502, wherein the memory 502 stores a program or instruction that can be run on the processor 501.
  • the communication device 500 is a first network element
  • the program or instruction when executed by the processor 501, implements the various steps of the embodiment of the task processing method applied to the first network element, and can achieve the same technical effect. To avoid repetition, it is not described here.
  • the communication device 500 is a second network element
  • the program or instruction when executed by the processor 501, implements the various steps of the embodiment of the task processing method applied to the second network element, and can achieve the same technical effect. To avoid repetition, it is not described here.
  • the present application also provides a network-side device, which is a first network element or a second network element and includes 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 Figure 2 or Figure 3.
  • This network-side device embodiment corresponds to the above-mentioned method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network-side device embodiment and can achieve the same technical effects.
  • an embodiment of the present application further provides a network-side device.
  • the network-side device can be a first network element or a second network element.
  • the network-side device 600 includes: an antenna 601, a radio frequency device 602, a baseband device 603, a processor 604, and a memory 605.
  • the antenna 601 is connected to the radio frequency device 602.
  • the radio frequency device 602 receives information via the antenna 601 and sends the received information to the baseband device 603 for processing.
  • the baseband device 603 processes the information to be transmitted and sends it to the radio frequency device 602.
  • the radio frequency device 602 processes the received information and then sends it through the antenna 601.
  • the method executed by the network-side device in the above embodiment may be implemented in the baseband device 603 , which includes a baseband processor.
  • the baseband device 603 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 10, one of which is, for example, a baseband processor, which is connected to the memory 605 through a bus interface to call the program in the memory 605 and execute the network device operations shown in the above method embodiment.
  • the network side device may also include a network interface 606, which is, for example, a Common Public Radio Interface (CPRI).
  • CPRI Common Public Radio Interface
  • the network side device 600 of the embodiment of the present application also includes: instructions or programs stored in the memory 605 and can be run on the processor 604.
  • the processor 604 calls the instructions or programs in the memory 605 to execute the method executed by each module shown in Figure 7 or Figure 8, and achieves the same technical effect. To avoid repetition, it will not be repeated here.
  • an embodiment of the present application further provides a network-side device.
  • the network-side device may be a first network element or a second network element.
  • the network-side device 700 includes: a processor 701, a network interface 702, and a memory 703.
  • the network interface 702 may be, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 700 of the embodiment of the present application also includes: instructions or programs stored in the memory 703 and can be run on the processor 701.
  • the processor 701 calls the instructions or programs in the memory 703 to execute the methods executed by each module shown in Figure 7 or Figure 8, and achieves the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • the various processes of the above-mentioned task processing 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.
  • ROM computer read-only memory
  • RAM random access memory
  • magnetic disk such as a hard disk, a hard disk, or a magnetic disk.
  • optical disk such as a hard disk, a hard disk, or an optical disk.
  • 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 task processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • 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 task processing 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 task processing system, including: a first network element and a second network element, wherein the first network element can be used to execute the steps of the task processing method applied to the first network element as described above, and the second network element can be used to execute the steps of the task processing method applied to the second network element as described above.
  • 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.
  • a storage medium such as ROM, RAM, magnetic disk, optical disk, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande appartient au domaine technique des communications. Sont divulgués un procédé et un appareil de traitement de tâche, et un dispositif associé. Le procédé de traitement de tâche dans les modes de réalisation de la présente demande comprend les étapes suivantes : un premier élément de réseau reçoit un premier message envoyé par un second élément de réseau, le premier message étant utilisé pour demander la libération d'une tâche cible ou de sous-tâches de la tâche cible ; et le premier élément de réseau exécutant une opération de libération pour la tâche cible ou les sous-tâches de la tâche cible, les sous-tâches de la tâche cible comprenant au moins l'un des éléments suivants : une sous-tâche de détection, une sous-tâche de calcul, une sous-tâche d'intelligence artificielle (IA), une sous-tâche de données, une sous-tâche de positionnement, une sous-tâche de communication, une sous-tâche de sous-système multimédia IP (IMS), une sous-tâche de traitement d'informations et une sous-tâche immersive.
PCT/CN2025/081974 2024-03-19 2025-03-12 Procédé et appareil de traitement de tâche, et dispositif associé Pending WO2025195240A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410315609.1A CN120670096A (zh) 2024-03-19 2024-03-19 任务处理方法、装置及相关设备
CN202410315609.1 2024-03-19

Publications (1)

Publication Number Publication Date
WO2025195240A1 true WO2025195240A1 (fr) 2025-09-25

Family

ID=97060827

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/081974 Pending WO2025195240A1 (fr) 2024-03-19 2025-03-12 Procédé et appareil de traitement de tâche, et dispositif associé

Country Status (2)

Country Link
CN (1) CN120670096A (fr)
WO (1) WO2025195240A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114546647A (zh) * 2022-02-21 2022-05-27 联想(北京)有限公司 调度方法和调度装置
CN115714774A (zh) * 2021-08-18 2023-02-24 维沃移动通信有限公司 算力请求、算力分配、算力执行方法、终端及网络侧设备
CN115915180A (zh) * 2021-08-10 2023-04-04 维沃移动通信有限公司 计算会话释放方法、设备及可读存储介质
US20230156049A1 (en) * 2021-11-18 2023-05-18 T-Mobile Usa, Inc. Cross-domain routing based on session initiation protocol information
CN117319993A (zh) * 2022-06-21 2023-12-29 维沃移动通信有限公司 信息传输方法、装置及电子设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115915180A (zh) * 2021-08-10 2023-04-04 维沃移动通信有限公司 计算会话释放方法、设备及可读存储介质
CN115714774A (zh) * 2021-08-18 2023-02-24 维沃移动通信有限公司 算力请求、算力分配、算力执行方法、终端及网络侧设备
US20230156049A1 (en) * 2021-11-18 2023-05-18 T-Mobile Usa, Inc. Cross-domain routing based on session initiation protocol information
CN114546647A (zh) * 2022-02-21 2022-05-27 联想(北京)有限公司 调度方法和调度装置
CN117319993A (zh) * 2022-06-21 2023-12-29 维沃移动通信有限公司 信息传输方法、装置及电子设备

Also Published As

Publication number Publication date
CN120670096A (zh) 2025-09-19

Similar Documents

Publication Publication Date Title
CN114980034B (zh) 原生算力业务实现方法、装置、网络设备及终端
EP3860176B1 (fr) Procédé, appareil, et système d'obtention d'informations de capacité de terminal
CN110830925B (zh) 一种用户群组的会话管理方法及装置
US20200296142A1 (en) User Group Establishment Method and Apparatus
KR20200139748A (ko) 서비스 가입 방법 및 장치
US20240179105A1 (en) Policy Determining or Resource Allocation Method for Computing Service and Network Element
WO2022143748A1 (fr) Procédé et appareil de traitement d'informations, dispositif et support d'enregistrement
WO2023213177A1 (fr) Procédé et appareil de communication
EP4300921A1 (fr) Procédé et appareil de mise en oeuvre de service de puissance de calcul natif, dispositif de réseau et terminal
WO2025026192A1 (fr) Procédé et appareil de traitement de service d'ia, dispositif et support de stockage lisible
WO2024198996A1 (fr) Procédé et appareil de communication
WO2025195240A1 (fr) Procédé et appareil de traitement de tâche, et dispositif associé
WO2025195238A1 (fr) Procédé et appareil de traitement de tâche et dispositif associé
WO2025195274A1 (fr) Procédé de traitement de tâche, terminal, et dispositif côté réseau
WO2025195239A1 (fr) Procédé et appareil de traitement de tâche et dispositif associé
WO2025195237A1 (fr) Procédé et appareil de traitement de transmission, terminal et dispositif côté réseau
WO2025195236A1 (fr) Procédé et appareil de surveillance d'informations et dispositif de communication
WO2025195276A1 (fr) Procédé de traitement de tâche, terminal et dispositif côté réseau
CN120676371A (zh) 任务管理方法、装置、终端及网络侧设备
WO2025026299A1 (fr) Procédé et appareil d'établissement de service d'ia, et dispositif côté réseau
US20250374125A1 (en) Apparatus, method, and computer program
EP4539418A1 (fr) Procédé de communication et appareil
WO2025195234A1 (fr) Procédé d'enregistrement de capacité de terminal, procédé d'acquisition, appareil, terminal et dispositif
WO2025195235A1 (fr) Procédé et appareil de traitement de tâche, et dispositif de communication
CN119449611A (zh) 策略协商方法、策略生成方法及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25772948

Country of ref document: EP

Kind code of ref document: A1