Communication method and apparatus

Abstract

A communication method and apparatus. The method comprises: on the basis of a first task identifier of a first task and a first quality-of-service flow identifier, determining a first packet detection rule and a first forwarding action rule, wherein the first packet detection rule is used for detecting a data packet corresponding to the first task, and the first forwarding action rule is used for forwarding the data packet corresponding to the first task; and sending the first packet detection rule and the first forwarding action rule. A first packet detection rule and a first forwarding action rule corresponding to a first task are determined at the granularity of quality-of-service flows, so as to detect and forward, according to the granularity of quality-of-service flows, a data packet related to the first task that is transmitted by a first terminal device. Since one session can correspond to a plurality of quality-of-service flows, resources of one session can be multiplexed within the session according to the granularity of quality-of service-flows, so as to transmit data of a plurality of tasks, thereby improving the resource utilization rate; moreover, data of different tasks can be isolated from each other within one session, thereby improving the communication flexibility.

Description

A communication method and apparatus

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510353614.6, filed on March 24, 2025, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] 5G (Fifth Generation Mobile Networks) defines 5G local area network (LAN) services. Regardless of whether users are in the same geographical area, as long as they join the same 5G LAN, they can achieve data exchange and communication based on the LAN. Building upon 5G LAN, the concept of virtual network (VN) groups is introduced. One VN group corresponds to one 5G LAN and can include multiple terminal devices. Different VN groups can access different data networks (DNs). Terminal devices connected to the same VN group can exchange data with the data network corresponding to that VN group, and can also directly exchange data with other terminal devices within the VN group through user plane function (UPF) network elements.

[0005] In current networks, the VN groups that terminal devices join are static, and terminal devices cannot change the VN groups they join in real time. Moreover, in order to achieve isolation between VN groups, each VN group corresponds to a session, which results in very poor communication flexibility. Summary of the Invention

[0006] This application provides a communication method and apparatus to improve the flexibility of communication.

[0007] In a first aspect, this application provides a communication method applicable to a network-side device, such as a session management function network element, other devices including session management function network element functions, a circuit, a chip system (or chip), or other functional modules. The chip system or functional module is capable of implementing the communication method and is, for example, located within a session management function network element. The method includes: receiving first information and second information, wherein the first information indicates a first task, and the second information indicates a first policy control and charging rule corresponding to a first terminal device, the first terminal device being used to execute the first task; determining a first packet detection rule and a first forwarding action rule associated with the first packet detection rule based on a first task identifier of the first task and a first quality of service flow identifier corresponding to the first policy control and charging rule; wherein the first packet detection rule is used to detect data packets corresponding to the first task, and the first forwarding action rule is used to forward data packets corresponding to the first task; and sending the first packet detection rule and the first forwarding action rule to a first user plane function network element, the first terminal device being located within the service range of the first user plane function network element.

[0008] This method determines the first packet detection rules and first forwarding action rules corresponding to the first task at the granularity of Quality of Service (QoS) flow. This allows the first user plane function network element to detect and forward data packets related to the first task transmitted by the first terminal device according to the QoS flow granularity. Since one session can correspond to multiple QoS flows, it is possible to transmit data for multiple tasks within a single session at the QoS flow granularity. This allows for the reuse of session resources to transmit data for multiple tasks, improving resource utilization. Furthermore, since different tasks correspond to different QoS flows, this allows for the isolation of data from different tasks within a single session, improving communication flexibility.

[0009] In one optional implementation, the first task is performed by a terminal device in a first virtual network group, the first virtual network group including the first terminal device and a second terminal device, the second terminal device being located within the service range of the first user plane function network element; the first packet detection rule includes a first uplink packet detection rule, a first downlink packet detection rule, a second uplink packet detection rule, and a second downlink packet detection rule; the first forwarding action rule includes a first uplink forwarding action rule associated with the first uplink packet detection rule and a second uplink forwarding action rule associated with the second uplink packet detection rule; wherein, the first uplink packet detection rule includes the first address information and the first quality of service flow identifier of the first terminal device, the first downlink packet detection rule includes the first task identifier and the second address information of the second terminal device, and the first uplink forwarding action rule includes the first task identifier; the second uplink packet detection rule includes the second address information and the second quality of service flow identifier corresponding to the second terminal device, the second downlink packet detection rule includes the first task identifier and the first address information, and the second uplink forwarding action rule includes the first task identifier.

[0010] This method uses a first Quality of Service (QoS) flow identifier to distinguish packet detection rules and forwarding action rules for different tasks, enabling data packets from different tasks within a session to be distinguished by the QoS flow identifier. This achieves data packet isolation for different tasks through QoS flow, realizing a group communication mechanism based on QoS flow granular isolation.

[0011] In one optional implementation, the first task is performed by a terminal device in a first virtual network group, the first virtual network group including the first terminal device and a second terminal device, the second terminal device being located within the service range of a second user plane function network element; the first packet detection rule includes a first uplink packet detection rule, a first downlink packet detection rule, a second uplink packet detection rule, and a second downlink packet detection rule; the first forwarding action rule includes a first uplink forwarding action rule associated with the first uplink packet detection rule, a second uplink forwarding action rule associated with the second uplink packet detection rule, and a first downlink forwarding action rule associated with the first downlink packet detection rule; wherein, the first uplink packet detection rule includes the first address information and the first quality of service flow identifier of the first terminal device, the first downlink packet detection rule includes the first task identifier and the second address information of the second terminal device, the first uplink forwarding action rule includes the first task identifier, the first downlink forwarding action rule includes the first task identifier; the second uplink packet detection rule includes the first task identifier, the second downlink packet detection rule includes the first task identifier and the first address information, and the second uplink forwarding action rule includes the first task identifier.

[0012] In an optional implementation, the method further includes: sending a second packet detection rule corresponding to the first task and a second forwarding action rule associated with the second packet detection rule to the second user plane function network element; wherein the second packet detection rule includes a third uplink packet detection rule, a third downlink packet detection rule, a fourth uplink packet detection rule, and a fourth downlink packet detection rule; the second forwarding action rule includes a third uplink forwarding action rule associated with the third uplink packet detection rule, a fourth uplink forwarding action rule associated with the fourth uplink packet detection rule, and a fourth downlink forwarding action rule associated with the fourth downlink packet detection rule; wherein the third uplink packet detection rule includes the first task identifier, the third downlink packet detection rule includes the first task identifier and the second address information of the second terminal device, and the third uplink forwarding action rule includes the first task identifier; the fourth uplink packet detection rule includes the second address information and the second service quality flow identifier corresponding to the second terminal device, the fourth downlink packet detection rule includes the first task identifier and the first address information, the fourth uplink forwarding action rule includes the first task identifier, and the fourth downlink forwarding action rule includes the first task identifier.

[0013] In an optional implementation, the method further includes: receiving first indication information, the first indication information indicating that there is a mapping relationship between the first policy control and billing rule and the first task.

[0014] In an optional implementation, the method further includes: receiving third information and fourth information, wherein the third information indicates a second task, and the fourth information indicates a second policy control and charging rule corresponding to the first terminal device, the first terminal device being used to execute the second task; determining a third packet detection rule and a third forwarding action rule associated with the third packet detection rule based on a second task identifier of the second task and a third service quality flow identifier corresponding to the second policy control and charging rule; wherein the third packet detection rule is used to detect data packets corresponding to the second task, and the third forwarding action rule is used to forward data packets corresponding to the second task; and sending the third packet detection rule and the third forwarding action rule to the first user plane function network element.

[0015] In one alternative implementation, the third quality of service flow identifier and the first quality of service flow identifier correspond to the same session of the first terminal device.

[0016] This method allows the first terminal device to use the same session to execute the first and second tasks, enabling different tasks to be executed through the same configured session. This way, the network side does not need to reconfigure network resources for the terminal device each time it executes a task, thereby improving resource utilization and task execution efficiency.

[0017] Secondly, this application provides a communication method that can be applied to a network-side device, such as a first user plane function network element, or other equipment including the functions of a first user plane function network element, or a circuit, or a chip system (or chip) or other functional module, which is capable of implementing the above-mentioned communication method. The chip system or functional module is, for example, located in the first user plane function network element. The method includes: receiving a first packet detection rule and a first forwarding action rule associated with the first packet detection rule; the first packet detection rule is used to detect data packets corresponding to a first task, and the first forwarding action rule is used to forward the data packets corresponding to the first task; the first packet detection rule and the first forwarding action rule are determined based on a first task identifier of the first task and a first quality of service flow identifier of a first policy control and charging rule corresponding to a first terminal device, the first terminal device being used to execute the first task; detecting data packets corresponding to the first task according to the first packet detection rule, and forwarding the data packets corresponding to the first task according to the first forwarding action rule.

[0018] In one optional implementation, the first task is performed by a terminal device in a first virtual network group, the first virtual network group including the first terminal device and a second terminal device, the first terminal device and the second terminal device being located within the service range of a first user plane function network element; the first packet detection rule includes a first uplink packet detection rule, a first downlink packet detection rule, a second uplink packet detection rule and a second downlink packet detection rule; the first forwarding action rule includes a first uplink forwarding action rule associated with the first uplink packet detection rule and a second uplink forwarding action rule associated with the second uplink packet detection rule; wherein, the first uplink packet detection rule includes the first address information and the first quality of service flow identifier of the first terminal device, the first downlink packet detection rule includes the first task identifier and the second address information of the second terminal device, and the first uplink forwarding action rule includes the first task identifier; the second uplink packet detection rule includes the second address information and the second quality of service flow identifier corresponding to the second terminal device, the second downlink packet detection rule includes the first task identifier and the first address information, and the second uplink forwarding action rule includes the first task identifier.

[0019] In one optional implementation, the step of detecting the data packet corresponding to the first task according to the first packet detection rule and forwarding the data packet corresponding to the first task according to the first forwarding action rule includes: detecting a first data packet whose source address is the first address information and includes the first quality of service flow identifier according to the first uplink packet detection rule; adding the first task identifier to the first data packet according to the first uplink forwarding action rule; and forwarding the first data packet to the virtual network internal interface according to the first uplink forwarding action rule; detecting the first data packet whose destination address is the second address information and includes the first task identifier within the virtual network internal interface according to the first downlink packet detection rule; and forwarding the first data packet to the second terminal device through the quality of service flow corresponding to the second quality of service flow identifier of the second terminal device.

[0020] In one optional implementation, the first task is performed by a terminal device in a first virtual network group, the first virtual network group including the first terminal device and a second terminal device, the first terminal device being located within the service range of a first user plane function network element, and the second terminal device being located within the service range of a second user plane function network element; the first packet detection rule includes a first uplink packet detection rule, a first downlink packet detection rule, a second uplink packet detection rule, and a second downlink packet detection rule; the first forwarding action rule includes a first uplink forwarding action rule associated with the first uplink packet detection rule, a second uplink forwarding action rule associated with the second uplink packet detection rule, and a first downlink forwarding action rule associated with the first downlink packet detection rule; wherein, the first uplink packet detection rule includes the first address information and the first quality of service flow identifier of the first terminal device, the first downlink packet detection rule includes the first task identifier and the second address information of the second terminal device, the first uplink forwarding action rule includes the first task identifier, the first downlink forwarding action rule includes the first task identifier; the second uplink packet detection rule includes the first task identifier, the second downlink packet detection rule includes the first task identifier and the first address information, and the second uplink forwarding action rule includes the first task identifier.

[0021] In one optional implementation, the step of detecting the data packet corresponding to the first task according to the first packet detection rule and forwarding the data packet corresponding to the first task according to the first forwarding action rule includes:

[0022] If a first data packet with the source address of the first address information and including the first quality of service flow identifier is detected according to the first uplink packet detection rule, then the first task identifier is added to the first data packet according to the first uplink forwarding action rule, and the first data packet is forwarded to the virtual network internal interface according to the first uplink forwarding action rule.

[0023] If, within the virtual network internal interface, the first data packet whose destination address is the second address information and includes the first task identifier is detected according to the first downlink packet detection rule, then the first task identifier is added to the first data packet according to the first downlink forwarding action rule, and the first data packet is forwarded to the second user plane function network element corresponding to the second terminal device according to the first downlink forwarding action rule.

[0024] In one optional implementation, the step of detecting the data packet corresponding to the first task according to the first packet detection rule and forwarding the data packet corresponding to the first task according to the first forwarding action rule includes: detecting a second data packet including a first task identifier according to the second uplink packet detection rule, adding the first task identifier to the second data packet according to the second uplink forwarding action rule, and forwarding the second data packet to the virtual network internal interface according to the second uplink forwarding action rule; detecting a second data packet with the first address information as its destination and including the first task identifier according to the second downlink packet detection rule within the virtual network internal interface, and forwarding the second data packet to the first terminal device through the quality of service flow corresponding to the first quality of service flow identifier.

[0025] In an optional implementation, the method further includes: receiving a third packet detection rule and a third forwarding action rule associated with the third packet detection rule from the session management function network element; wherein the third packet detection rule is used to detect data packets corresponding to the second task, and the third forwarding action rule is used to forward data packets corresponding to the second task; the third packet detection rule and the third forwarding action rule are determined based on the second task identifier of the second task and the third service quality flow identifier corresponding to the first terminal device.

[0026] In one alternative implementation, the third quality of service flow identifier and the first quality of service flow identifier correspond to the same session of the first terminal device.

[0027] Thirdly, this application provides a communication method that can be applied to a terminal-side device, such as a terminal device, other devices including a terminal device, a circuit, a chip system (or chip), or other functional modules. The chip system or functional module is capable of implementing the aforementioned communication method and is, for example, disposed in the terminal device. The method includes: receiving first broadcast information from a network device, the first broadcast information indicating a first task; determining to execute the first task; and sending first confirmation information, the first confirmation information indicating that the first task has been executed.

[0028] In an optional implementation, the method further includes: receiving broadcast information (second broadcast information) from the network device, the broadcast information indicating a second task; determining to execute the second task; and sending second confirmation information, the second confirmation information indicating that the second task has been determined to be executed.

[0029] In an optional implementation, the method further includes: sending a first data packet corresponding to the first task through a quality of service flow corresponding to a first quality of service flow identifier; sending a second data packet corresponding to the second task through a quality of service flow corresponding to a third quality of service flow identifier; wherein the third quality of service flow identifier and the first quality of service flow identifier correspond to the same session.

[0030] Fourthly, this application provides a communication method that can be applied to a network-side device, such as a second user plane function network element, or other equipment including the functions of a second user plane function network element, or a circuit, or a chip system (or chip) or other functional module, which is capable of implementing the above-mentioned communication method. The chip system or functional module is, for example, disposed in the second user plane function network element. The method includes: receiving a second packet detection rule corresponding to a first task from a session management function network element; detecting a data packet corresponding to the first task according to the second packet detection rule; and forwarding the data packet corresponding to the first task according to the second forwarding action rule; wherein the second packet detection rule includes a third uplink packet detection rule, a third downlink packet detection rule, a fourth uplink packet detection rule, and a fourth downlink packet detection rule; the second forwarding action rule includes a third uplink forwarding action rule associated with the third uplink packet detection rule, a third downlink forwarding action rule associated with the third downlink packet detection rule, a fourth uplink forwarding action rule associated with the fourth uplink packet detection rule, and a fourth downlink forwarding action rule associated with the fourth downlink packet detection rule.

[0031] In one optional implementation, the third uplink packet detection rule includes the first task identifier, and the third uplink forwarding action rule includes the first task identifier; the third downlink packet detection rule includes the first task identifier and the second address information of the second terminal device, and the third downlink packet detection rule is associated with the first quality of service flow identifier; the first terminal device is located within the service range of the first user plane function network element, and the second terminal device is located within the service range of the second user plane function network element.

[0032] In one optional implementation, the step of detecting the data packet corresponding to the first task according to the second packet detection rule and forwarding the data packet corresponding to the first task according to the second forwarding action rule includes: if the first data packet includes the first task identifier according to the third uplink packet detection rule, then add the first task identifier to the first data packet according to the third uplink forwarding action rule, and forward the first data packet to the virtual network internal interface of the second UPF network element according to the third uplink forwarding action rule.

[0033] If a first data packet with a destination address of the second address information and including the first task identifier is detected within the virtual network internal interface according to the third downlink packet detection rule, then the first data packet is forwarded to the second terminal device through the quality of service flow corresponding to the first quality of service flow identifier according to the third downlink forwarding action rule.

[0034] In one optional implementation, the step of detecting the data packet corresponding to the first task according to the second packet detection rule and forwarding the data packet corresponding to the first task according to the second forwarding action rule includes:

[0035] If a second data packet with the source address of the second address information and including the second quality of service flow identifier is detected according to the fourth uplink packet detection rule, then the first task identifier is added to the second data packet according to the fourth uplink forwarding action rule, and the second data packet is forwarded to the virtual network internal interface of the second UPF network element according to the fourth uplink forwarding action rule.

[0036] If a second data packet containing a first task identifier is detected within the virtual network internal interface according to the fourth downlink packet detection rule, then the first task identifier is added to the second data packet according to the fourth downlink forwarding action rule, and the second data packet is forwarded to the first user plane function network element corresponding to the first terminal device according to the fourth downlink forwarding action rule.

[0037] Fifthly, this application also provides a communication device capable of implementing any of the methods provided in any of the first to fourth aspects. This communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the aforementioned functions.

[0038] In one possible implementation, the communication device includes a processor configured to support the communication device in performing corresponding functions of the terminal device, session management function network element, first user plane function network element, or second user plane function network element in the methods described above. The communication device may further include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device may also include interface circuitry for supporting communication between the communication device and devices such as terminal devices.

[0039] In one possible implementation, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0040] In one possible implementation, the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples, as described in the methods provided in any of the first to fourth aspects, and will not be repeated here.

[0041] A sixth aspect provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor implements the functional modules of the methods in any possible implementation of any of the first to fourth aspects through logic circuits or by executing computer programs or instructions. Optionally, the communication device further includes a memory for storing computer programs or instructions.

[0042] In a seventh aspect, a computer-readable storage medium is provided, which stores a computer program or instructions that, when executed by a processor, implement the method in any possible implementation of any of the first to fourth aspects.

[0043] Eighthly, a computer program product storing instructions is provided, which, when read and executed by a computer, implements the method in any possible implementation of any of the first to fourth aspects.

[0044] A ninth aspect provides a circuit for performing the methods in any possible implementation of any of the first to fourth aspects described above, the circuit including chip circuitry. Optionally, the circuit may also be coupled to a memory.

[0045] In a tenth aspect, a chip is provided, the chip including a processor, which, when executing a computer program or instructions, implements the methods in any possible implementation of any of the first to fourth aspects. Optionally, the chip may further include a memory, and the chip may be composed of chips or may include chips and other discrete devices.

[0046] Eleventhly, a communication device is provided, including a processor that implements the method in any possible implementation of any of the first to fourth aspects by means of logic circuits or by executing computer programs or instructions.

[0047] In a twelfth aspect, a communication apparatus is provided, comprising a unit or module for performing a method in any possible implementation of any of the first to fourth aspects described above.

[0048] In a thirteenth aspect, embodiments of this application also provide a communication system. The communication system includes: a terminal device, a session management function network element, and a first user plane function network element; the session management function network element implements the methods of the aforementioned first aspect and any possible implementation thereof; the first user plane function network element implements the methods of the aforementioned second aspect and any possible implementation thereof; and the terminal device implements the methods of the aforementioned third aspect and any possible implementation thereof. Attached Figure Description

[0049] Figure 1 is a schematic diagram of a network architecture applicable to an embodiment of this application;

[0050] Figure 2 is a schematic diagram of a network architecture provided in an embodiment of this application;

[0051] Figure 3 is a schematic diagram of a network architecture provided in an embodiment of this application;

[0052] Figure 4 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0053] Figure 5 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0054] Figures 6A and 6B are schematic diagrams of a data packet transmission process provided in an embodiment of this application;

[0055] Figures 7A and 7B are schematic diagrams of a data packet transmission process provided in an embodiment of this application;

[0056] Figure 8 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0057] Figure 9 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0058] Figure 10 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0059] Figure 11 is a schematic diagram of a communication device structure provided in an embodiment of this application;

[0060] Figure 12 is a schematic diagram of a communication device structure provided in an embodiment of this application. Detailed Implementation

[0061] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. The terms "first," "second," and corresponding terminology in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be interchanged where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or device that comprises a series of units is not necessarily limited to those units, but may include other units not explicitly listed or inherent to these processes, methods, products, or devices. The methods and apparatus provided in the embodiments of this application are based on the same or similar technical concepts. Since the principles by which the methods and apparatus solve problems are similar, the implementations of the apparatus and methods can refer to each other, and repeated details will not be repeated.

[0062] The method provided in this application can be applied to various mobile communication systems, such as the Internet of Things (IoT), narrowband Internet of Things (NB-IoT), fourth-generation (4G) communication systems (e.g., Long Term Evolution (LTE)), fifth-generation (5G) communication systems (e.g., 5G New Radio (NR)), LTE and NR hybrid architectures, or new communication systems emerging in future communication developments. The communication system can also include machine-to-machine (M2M) networks, machine-type communication (MTC) networks, or other networks.

[0063] The following section will first explain some of the terms used in the embodiments of this application so that those skilled in the art can understand them.

[0064] In this embodiment, the network device can be a device in a wireless network, and can also be referred to as a network apparatus, a radio access network device, or an access network device. For example, the network device can be a radio access network (RAN) node that connects a terminal device to a wireless network. Network devices include, but are not limited to: base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, access network devices in open radio access networks (O-RANs), base stations in future mobile communication systems, or access nodes in wireless fidelity (WiFi) systems; or they can be modules or units that perform some of the functions of a base station, such as a central unit (CU), a distributed unit (DU), a central unit control plane (CU-CP) module, or a central unit user plane (CU-UP) module. Network equipment can be macro base stations, micro base stations, indoor stations, relay nodes, or donor nodes, etc. This application does not limit the specific technology or form of the network equipment.

[0065] In some implementations, network devices can include centralized units (CUs) and distributed units (DUs). This includes RAN devices at CU and DU nodes that separate the protocol layers of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed across the DUs, which are then centrally controlled by the CU. Furthermore, the CU can be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP handles control plane functions, primarily including radio resource control (RRC) and the corresponding packet data convergence protocol (PDCP) (PDCP-C). PDCP-C is mainly responsible for control plane data encryption / decryption, integrity protection, and data transmission. The CU-UP handles user plane functions, primarily including the service data adaptation protocol (SDAP) and the corresponding PDCP (PDCP-U). SDAP is mainly responsible for processing core network data and mapping flows to bearers. PDCP-U is primarily responsible for data plane encryption / decryption, integrity protection, header compression, sequence number maintenance, and data transmission. CU-CP and CU-UP are connected via the E1 interface. CU-CP represents the gNB connected to the core network via the NG interface and to the DU via the F1 interface control plane (F1-C). CU-UP is connected to the DU via the F1 interface user plane (F1-U). Alternatively, PDCP-C may also be located within CU-UP.

[0066] It is understood that CU (including CU-CP or CU-UP) or DU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an open radio access network (O-RAN) system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, and CU-UP can also be called O-CU-UP. For ease of description, this application uses CU, CU-CP, CU-UP, and DU as examples. Network devices may also include active antenna units (AAU). CU implements some of the functions of gNB, and DU implements some of the functions of gNB. For example, CU is responsible for handling non-real-time protocols and services, implementing the functions of the RRC layer. DU is responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer. In some deployments, the CU can also be divided into a centralized unit control plane (CU-CP) node and a centralized unit user plane (CU-UP) node. The CU-CP is responsible for control plane functions, while the CU-UP is responsible for user plane functions.

[0067] The terminal device involved in this application embodiment can be a wireless terminal device capable of receiving network device scheduling and instruction information. The terminal device can be referred to as a terminal device, user equipment (UE), terminal, mobile station (MS), mobile terminal (MT), etc. The terminal device can also be a chip or system-on-a-chip, which is built into the aforementioned user equipment (UE), terminal, mobile station (MS), or mobile terminal (MT). The terminal device can be a device including wireless communication functions (providing voice / data connectivity to the user). For example, a handheld device with wireless connectivity, or an in-vehicle device, in-vehicle module, etc. Currently, examples of terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in vehicle-to-everything (V2X) communication, wireless terminals in vehicle-to-everything (V2X) communication, intelligent vehicles, in-vehicle infotainment systems (or onboard transmitters) (T-boxes), machine-to-machine / machine-type communications (M2M / MTC) terminal devices, and the Internet of Things (IoT). of things, IoT (Internet of Things) terminal devices, etc.For example, terminal devices can be in-vehicle equipment, vehicle-mounted equipment, in-vehicle modules, vehicles, on-board units (OBU), roadside units (RSU), T-boxes, chips, or systems-on-chips (SOCs), which can be installed in vehicles, OBUs, RSUs, or T-boxes. Wireless terminals in industrial control can be cameras, robots, etc. Wireless terminals in smart homes can be televisions, air conditioners, robot vacuums, speakers, set-top boxes, etc. Terminal devices can also be V2X devices, such as smart cars, digital cars, unmanned cars, driverless cars, pilotless cars, autonomous cars, pure electric vehicles (EVs), hybrid electric vehicles (HEVs), range-extended electric vehicles (REEVs), plug-in hybrid electric vehicles (PHEVs), new energy vehicles, and roadside units (RSUs). Terminal devices can also be devices in device-to-device (D2D) communication, such as electricity meters and water meters. Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system. IoT is an important component of future information technology development, and its main technical characteristic is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and machine-to-machine interconnection.

[0068] To facilitate understanding, the following section provides a brief introduction to some network elements located in the core network, based on the mobile communication system network architecture.

[0069] Figure 1 is a schematic diagram of a network architecture applicable to this application. As shown in Figure 1, the main functions of the network elements related to this network architecture are described below:

[0070] Application function (AF) network elements, also known as application controllers, are primarily used to convey application-side requests to the network side, such as Quality of Service (QoS) requirements and user state event subscriptions. AF network elements can be application function entities of third-party applications or application services deployed by the operator. When third-party application function entities interact with the core network, authorization processing can be handled through network exposure function (NEF) network elements. For example, a third-party application function entity can directly send a request message to a NEF network element. The NEF network element verifies whether the AF network element is allowed to send the request message. If the verification is successful, the request message is forwarded to the corresponding policy control function (PCF) network element or unified data management (UDM) network element.

[0071] PCF network elements are mainly used to implement policy control functions such as billing at the session and service flow levels, QoS bandwidth guarantee and mobility management, and user equipment policy decision-making.

[0072] UDM network elements are mainly used to implement data management functions such as managing contracted data and authorizing user access.

[0073] Access and mobility management function (AMF) network elements: These are primarily used to implement mobility management, access authentication / authorization, and other functions for terminal devices. In addition, AMF network elements are also responsible for transmitting user policies between terminal devices and PCF network elements.

[0074] Session management function (SMF) network element: mainly used for packet data unit (PDU) session management of terminal equipment, execution of PCF-issued control policies, selection of user plane function (UPF) network elements, etc.

[0075] UPF network elements are responsible for forwarding and receiving user data in terminal devices. They can receive user data from the data network and transmit it to the terminal device through network equipment; UPF network elements can also receive user data from terminal devices through network equipment and forward it to the data network. The transmission resources and scheduling functions that provide services to terminal devices in UPF network elements are managed and controlled by SMF network elements.

[0076] Artificial Intelligence Management Function (AI-MF) network element: This is a core network element primarily responsible for group management, such as group creation and release. In future communication systems, AI-MF network elements may have other names, which are not limited in this application. AI-MF network elements can also be core network devices.

[0077] Network Exposure Function (NEF) network element: Primarily supports secure interaction between 3GPP networks and third-party applications.

[0078] Policy control function (PCF) network element: responsible for policy control decisions, providing policy rules for control plane functions, and traffic-based billing control functions.

[0079] Network slice selection function (NSSF) network element: mainly responsible for network slice selection, determining the network slice instance that the UE is allowed to access based on the UE's slice selection auxiliary information, subscription information, etc.

[0080] Unified data management (UDM) network element: mainly responsible for the management of UE subscription data, including the storage and management of UE identifiers, UE access authorization, etc.

[0081] Authentication server function (AUSF) network element: can be used to support access service authentication and other functions.

[0082] The descriptions of each network element above are merely examples. The specific functions of each network element in this network architecture are not limited to the descriptions above, and will not be elaborated further here. Additionally, this network architecture may include other network elements besides those illustrated in the examples above, which will not be listed here.

[0083] It should be noted that this application does not limit the name of the corresponding network element that implements each function. It can also implement other functions or be integrated with other functional network elements, and can also be called by other names.

[0084] In the network architecture shown in Figure 1, there may be communication interfaces between network elements and between network elements and devices. For example, the main functions of some related communication interfaces are described below:

[0085] N1 Interface: This is the signaling plane interface between AMF network elements and terminal equipment. It is independent of the access network and is used to exchange signaling messages between the core network and terminal equipment. It can be used in processes such as terminal equipment registration, terminal equipment establishing PDU sessions, and network-side configuration of terminal equipment policies.

[0086] N2 interface: This is the interface between AMF network elements and RAN equipment, used to transmit radio bearer control information from the core network to the RAN equipment.

[0087] N3 Interface: This is the interface between the (RAN) device and the UPF network element, used to transmit service data of the terminal device between the RAN device and the UPF network element.

[0088] N4 interface: This is the interface between SMF network elements and UPF network elements, used to transmit information between the control plane and the user plane. It can be used by control plane terminal equipment to complete network access operations and other processes based on the contract information with the operator.

[0089] N6 interface: This is the interface between the UPF network element and the DN, used to transmit service data of the terminal equipment between the UPF network element and the DN.

[0090] In communication systems, the establishment of a PDU session is triggered by a terminal device based on an initiated service. Different services have different requirements for PDU session attributes such as network slice, Data Network Name (DNN), and Session and Service Continuity Mode (SSC mode). Therefore, a terminal device may trigger the establishment of different PDU sessions based on different services. Thus, 5G introduces a User Routing Selection Policy (URSP) to help the terminal device determine whether an existing PDU session can be used for data transmission, or whether a new PDU session can be created to transmit the service's data.

[0091] After the terminal device performs URSP matching based on the initiated service, it can obtain the corresponding PDU session parameters based on the matched URSP. If there is a PDU session that meets the parameter requirements, it will use that PDU session for data transmission; otherwise, it can create a new PDU session for data transmission.

[0092] Packet Detection Rule (PDR): On the network side, during PDU session management of terminal devices, the SMF interacts with the UPF through the N4 interface to control the UPF in creating, modifying, and deleting the terminal (UE) N4 session corresponding to the PDU session, thereby controlling the UPF's processing of data packets. PDR is associated with the Forwarding Action Rule (FAR). PDR is used to match data packets, while FAR indicates the forwarding method for the data packets.

[0093] It should be noted that, in this embodiment of the application, the N4 session is also referred to as a packet forwarding control protocol (PFCP) session.

[0094] The PDR is issued by the SMF to the UPF, and the UPF performs corresponding packet matching based on the PDR issued by the SMF. A PDR contains a packet detection information (PDI) parameter. A PDI parameter contains one or more matching fields, which are used to match the packets received by the UPF to identify the packets and complete the association between the packets and the terminal N4 session.

[0095] The information contained in the PDR provided by the SMF to the UPF is mainly shown in Table 1 below:

[0096] Table 1. List of PDR parameters in PFCP session establishment request

[0097] The above are just examples; the specific content of PDR is not limited.

[0098] The PDI in the PDR mainly includes the following information:

[0099] a. Data packet entry / source interface.

[0100] b. A series of parameters for matching inbound packets. For example: tunnel endpoint identity document (TEID) / full qualified TEID (F-TEID), network instance, terminal device IP address, service data flow filter (SDF) filter(s), application ID, etc.

[0101] After obtaining the PDR from the SMF, when the UPF receives a data packet, it matches the header fields of the packet with the parameters defined in the PDI within the PDR. This process identifies the N4 session to which the packet belongs and the highest-priority PDR rule within that N4 session that matches the packet. Once the PDR matching is complete, the UPF forwards the data packet according to the FAR associated with that PDR.

[0102] The information contained in FAR is mainly shown in Table 2 below:

[0103] Table 2. List of FAR parameters in PFCP session establishment request

[0104] The FAR primarily instructs the UPF to process data packets using the following information:

[0105] a. Apply action parameter: This parameter indicates whether the UPF should forward, buffer, copy, or drop packets, or buffer downlink packets with or without notifying the control plane (such as the SMF); or it indicates whether the UPF should allow terminal devices to join IP multicast groups.

[0106] b. Forwarding, caching, and copying parameters: UPF uses these parameters when application action parameters instruct UPF to forward, cache, or copy packets in order to process packets accordingly.

[0107] Virtual Network Groups: 3GPP defines 5G LAN services, which can build a virtual private mobile network for users within a mobile network. 5G LAN introduces the concept of virtual network groups on this basis. A virtual network group corresponds to a 5G LAN and can include multiple terminal devices. Terminal devices belonging to the same virtual network group can access the mobile network and communicate with both the data network and other terminal devices within the same virtual network group.

[0108] Currently, 5G mobile networks can support multiple virtual network groups simultaneously. Terminal devices within the same virtual network group can communicate with each other through the same or different PDU session anchors (PSA) UPFs, while terminal devices in different virtual network groups are isolated from each other.

[0109] Figure 2 is a schematic diagram of the user plane architecture for data exchange between terminal devices in a virtual network group using a PSA UPF local switching scenario. As shown in Figure 2, multiple terminal devices (such as UE1 and UE2) under the same virtual network group are registered in the same PSA UPF network element. In this scenario, in addition to completing data exchange between UE1 and UE2 and the data network, the PSA UPF network element also acts as a local switch for the virtual network group, completing data exchange between UE1 and UE2, since UE1 and UE2 belong to the same virtual network group.

[0110] Figure 3 is a schematic diagram of the user plane architecture for data exchange across PSA UPF between terminal devices in a virtual network group. As shown in Figure 3, multiple terminal devices (such as UE1 and UE2) under the same virtual network group are registered in different PSA UPF network elements. In this scenario, an N19 interface is added between different PSA UPF network elements. When UE1 and UE2, which belong to the same virtual network group, exchange data, data transmission and interaction will be completed by their respective PSA UPF network elements through the N19 interface channel.

[0111] In Figure 2 or Figure 3, the intermediate UPF (I-UPF) network element between the RAN and PSA UPF network elements is used as an uplink classifier (UL-CL) to direct data flow from terminal devices to the data network, or as a branch point to support multi-homed PDU sessions.

[0112] Data networks are typically identified by a Data Network Name (DNN). With the introduction of Virtual Network Groups (VNs) in 5G, the relevant protocols define a 1:1 relationship between the DNN of a data network and the virtual network group. That is, one DNN corresponds to one virtual network group, and one data network corresponds to one virtual network group. Therefore, the 5G LAN corresponding to a virtual network group can only support access to the data network corresponding to that virtual network group.

[0113] Similarly, one virtual network group corresponds to one single network slice selection assistance information (S-NSSAI), meaning one S-NSSAI corresponds to one virtual network group.

[0114] Currently, operators need to pre-configure different DNNs and S-NSSAIs for different virtual network groups to achieve virtual network group isolation. This configuration is time-consuming and complex, and virtual network groups are not dynamically created based on events, resulting in poor flexibility. Furthermore, terminal devices communicate data through PDU sessions corresponding to virtual network groups, with one PDU session corresponding to only one virtual network group. In other words, currently, if a terminal device subscribes to a virtual network group, the network side configures the DNN and S-NSSAI for that virtual network group; the configuration is static and pre-configured. Due to the time-consuming and complex configuration of the pipeline resources corresponding to DNNs and S-NSSAIs, current networks only support static configuration of virtual network groups. How to dynamically create virtual network groups for already configured DNNs and S-NSSAIs to enable the execution of events or tasks through dynamically created virtual network groups, thereby improving the flexibility of executing events or tasks through virtual network groups, is a problem that urgently needs to be solved.

[0115] When the method provided in this application is applied to the network architecture shown in Figure 1, the functions of the network devices can be executed by modules (such as chips) within the network devices, or by a control subsystem that includes network device functions. This control subsystem, including network device functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal devices can be executed by modules (such as chips or modems) within the terminal devices, or by a device that includes terminal device functions.

[0116] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0117] The following embodiments of this application describe the interaction between network devices, terminal devices, SMF network elements, AI-MF network elements, UPF network elements, and PCF network elements as examples. The names of the various network elements or devices mentioned above are merely examples. In practical applications, the names of the various network elements or devices mentioned above may change according to the evolution of the network architecture and / or changes in the service scenario.

[0118] In the following embodiments of this application, the descriptions of first data packet, second data packet, third data packet, fourth data packet, first quality of service flow identifier, second quality of service flow identifier, third quality of service flow identifier, fourth quality of service flow identifier, first task identifier, and second task identifier are merely examples and do not represent limitations on the above terms in actual applications.

[0119] Figure 4 shows a flowchart of a communication method provided in an embodiment of this application. The method includes:

[0120] Step 401: The network device sends a first broadcast message, which indicates the first task.

[0121] Correspondingly, the first terminal device and the second terminal device receive the first broadcast information from the network device.

[0122] The first broadcast message may include the task identifier of the first task.

[0123] This example illustrates how the first terminal device and the second terminal device can access the same network device, but the first terminal device and the second terminal device can also access different network devices.

[0124] Optionally, the first broadcast information may also include the task content corresponding to the first task, and / or the area information corresponding to the first task.

[0125] The task content corresponding to the first task may include the measurement information and accuracy of the first task.

[0126] The area information corresponding to the first task can indicate the first area. Optionally, the first area can be the service range of the network device.

[0127] The first broadcast message may also include other content, which is not limited in this application.

[0128] Here, we take the first terminal device and the second terminal device receiving the first broadcast information as an example. The actual number of terminal devices receiving the first broadcast information is not limited.

[0129] Optionally, the first terminal device determines whether to perform the first task based on its own capabilities and other information. For example, if the first terminal device determines that it has the capability to perform the first task, it will determine to perform the first task. If the first terminal device determines that it does not have the capability to perform the first task, it will determine not to perform the first task.

[0130] If the first terminal device determines to perform the first task, the following process can be executed.

[0131] Step 402: The first terminal device determines to execute the first task and sends a first confirmation message, which instructs the first terminal device to determine to execute the first task.

[0132] In this application, the first terminal device can send a first confirmation message to the AMF network element through the network device. Optionally, the first terminal device may also send at least one of the following: a task identifier for the first task, a session identifier, a DNN, S-NSSAI, and a first identifier of the first terminal device. The first identifier of the first terminal device may be a subscription permanent identifier (SUPI) of the first terminal device.

[0133] In one implementation, the first terminal device sends a first confirmation message through a session establishment request message, that is, the session establishment request message includes the first confirmation message.

[0134] For example, if the first terminal device determines that there is no corresponding PDU session for DNN and S-NSSAI, it sends a session establishment request message to the AMF network element through the network device. The session establishment request message can be used to request the establishment of a PDU session, or it can be used to request the establishment of a virtual network group corresponding to the first task. DNN and S-NSSAI can be configured on the network side; for example, the network side sends a URSP to the first terminal device, and the URSP includes DNN and S-NSSAI. Terminal devices in a virtual network group performing the same task use the same DNN and S-NSSAI. This ensures that terminal devices in the same virtual network group not only obtain the same configured DNN / S-NSSAI when establishing a temporary virtual network group, but also do not need to reconfigure the network resources corresponding to DNN / S-NSSAI for the virtual network group in the entire network each time a virtual network group is established, thus improving the flexibility of establishing virtual network groups. In this application, DNN and S-NSSAI can correspond to multiple virtual network groups, and DNN and S-NSSAI can correspond to multiple tasks.

[0135] Optionally, the session establishment request message may also include the task identifier of the first task, the session identifier, the DNN, S-NSSAI, and the first identifier of the first terminal device.

[0136] The session establishment request message may also include other information, which is not limited in this application.

[0137] In one implementation, the first terminal device sends a first confirmation message through a session modification request message, that is, the session modification request message includes the first confirmation message.

[0138] For example, if the first terminal device determines that there is a corresponding PDU session between DNN and S-NSSAI, it sends a session modification request message to the AMF network element through the network device. The session modification message can be used to request modification of the PDU session, or it can be used to request the establishment of the virtual network group corresponding to the first task.

[0139] Optionally, the session modification request message may also include the task identifier of the first task, the session identifier, the DNN, S-NSSAI, and the first identifier of the first terminal device. The session modification request message may also include other information, which is not limited in this application.

[0140] The above are just examples. The first terminal device may also send the first confirmation information through other messages. This application does not limit this.

[0141] If the second terminal device determines to perform the first task, the following process can be executed.

[0142] Step 403: The second terminal device determines to execute the first task and sends a third confirmation message, which instructs the second terminal device to determine to execute the first task.

[0143] The second terminal device can send a third confirmation message to the AMF network element through the network device. Optionally, the second terminal device can also send at least one of the following: the task identifier of the first task, the session identifier, the DNN, S-NSSAI, and the second identifier of the second terminal device.

[0144] The following example illustrates how the AMF network element can execute the following process when it receives the first confirmation information from the first terminal device and the third confirmation information from the second terminal device.

[0145] Step 404: The AMF network element sends the first confirmation message and the third confirmation message to the AI-MF network element.

[0146] Correspondingly, the AI-MF network element receives the first confirmation message and the third confirmation message.

[0147] If the AMF network element only receives the first confirmation message or the third confirmation message, it can send the first confirmation message or the third confirmation message only to the AI-MF network element.

[0148] The AMF network element can also send at least one of the following to the AI-MF network element: the task identifier of the first task, the session identifier, the DNN, the S-NSSAI, the first identifier of the first terminal device, and the second identifier of the second terminal device.

[0149] For example, an AMF network element sends a group establishment request message to an AI-MF network element. This message includes the task identifier, session identifier, DNN, S-NSSAI, and the first identifier of the first terminal device. The group establishment request message can be used to request the establishment of a virtual network group corresponding to the first task. The name of the group establishment request message is just an example; other names are also possible.

[0150] In one implementation of this application, after receiving the first confirmation information, the AI-MF network element can send the first information to the SMF network element, and the first information indicates the first task.

[0151] In another implementation, after receiving the first confirmation information, the AI-MF network element can send the first information to the PCF network element.

[0152] The following description uses the example of an AI-MF network element sending the first message to an SMF network element.

[0153] Step 405: The AI-MF network element sends the first information to the SMF network element.

[0154] Correspondingly, the SMF network element receives the first information.

[0155] The first information may include the task identifier of the first task.

[0156] Optionally, the first information may also indicate the first terminal device, for example, the first information may include the first identifier of the first terminal device.

[0157] Optionally, the first information may also indicate a Quality of Service (QoS) requirement, which may be determined by the AI-MF network element. This application does not limit how the QoS requirement is determined.

[0158] SMF network elements can forward service quality requests to PCF network elements; the specific process will not be elaborated here.

[0159] Optionally, the first information may also include at least one of the following: session identifier, DNN, S-NSSAI.

[0160] It should be noted that if the AI-MF network element receives first confirmation messages from multiple terminal devices, the AI-MF network element can indicate the identifiers of the multiple terminal devices through the first messages; alternatively, the AI-MF network element can send multiple first messages, with one of the multiple first messages corresponding to one of the multiple terminal devices. These multiple terminal devices belong to the same virtual network group, meaning they all confirm the execution of the first task.

[0161] Optionally, the first information may include a group identifier of a first virtual network group, and the first task is performed by a terminal device in the first virtual network group, wherein the first virtual network group includes the first terminal device. The group identifier of the first virtual network group may be determined by an AI-MF network element or by other network elements, and this application does not limit this.

[0162] AI-MF network elements can send the first information to SMF network elements by establishing task scheduling resource messages, or they can send the first information through other messages. This application does not limit this.

[0163] Optionally, after obtaining the first information, the SMF network element can also request session management subscription data corresponding to the first identifier, DNN, and S-NSSAI of the first terminal device from the UDM network element. The specific process will not be elaborated here. The session management subscription data can be used for N4 rule formulation and session establishment; the specific process will not be elaborated here either.

[0164] Step 406: The PCF network element sends the second information to the SMF network element.

[0165] Accordingly, the SMF network element receives the second information. The second information indicates the first policy control and charging (PCC) rule corresponding to the first terminal device.

[0166] Before sending the second information, the PCF network element can receive the quality of service (QoS) requirements from the SMF network element. The PCF network element can then determine the first policy control and billing rules based on the QoS requirements.

[0167] PCF network elements can also send other information to SMF network elements, but this application does not limit this.

[0168] In another implementation, the SMF network element can receive first information and second information from the PCF network element. Optionally, the SMF network element can receive first indication information from the PCF network element, whereby the first indication information indicates that there is a mapping relationship between the first policy control and billing rule and the first task.

[0169] Optionally, step 406 can be replaced by: the SMF network element obtaining the first policy control and charging rule corresponding to the first terminal device according to the local policy. For example, before step 405, the first terminal device has already established a session through the SMF network element. The SMF network element may include the session management (SM) context of the session, which may include a local policy. The local policy may include the policy control and charging rule corresponding to the first terminal device, and the SMF network element may use this policy control and charging rule as the first policy control and charging rule.

[0170] Optionally, after receiving the third confirmation information from the second terminal device, the AI-MF network element can perform the following process:

[0171] Optionally, in step 407: the AI-MF network element sends the fifth information to the SMF network element.

[0172] Correspondingly, the SMF network element receives the fifth message. The fifth message indicates the first task.

[0173] The fifth piece of information may include the task identifier of the first task.

[0174] Optionally, the fifth information may also indicate the second terminal device; for example, the fifth information may include the second identifier of the second terminal device.

[0175] Optionally, the fifth information may further include at least one of the following: quality of service requirements, session identifier, DNN, and S-NSSAI. The session identifier indicated by the fifth information may be the same as or different from the session identifier indicated by the first information; the DNN and S-NSSAI indicated by the fifth information may be the same as or different from the DNN and S-NSSAI indicated by the first information; the quality of service requirements indicated by the fifth information may be the same as or different from the quality of service requirements indicated by the first information.

[0176] Step 408: The PCF network element sends the sixth information to the SMF network element.

[0177] Correspondingly, the SMF network element receives the sixth information. The sixth information indicates the third policy control and charging rules corresponding to the second terminal device.

[0178] Before sending the sixth message, the PCF network element can receive service quality requirements from the SMF network element. The PCF network element can then determine the third policy control and billing rules based on the service quality requirements.

[0179] Optionally, step 408 can be replaced by: the SMF network element obtaining the third policy control and charging rule corresponding to the second terminal device according to the local policy. For example, before step 407, the second terminal device has already established a session through the SMF network element. The SMF network element can include the SM context of the session, which can include the local policy. The local policy can include the policy control and charging rule corresponding to the second terminal device, and the SMF network element can use this policy control and charging rule as the third policy control and charging rule.

[0180] Step 409: The SMF network element determines the first packet detection rule and the first forwarding action rule associated with the first packet detection rule based on the first task identifier of the first task and the first service quality flow identifier corresponding to the first policy control and charging rule.

[0181] The first packet detection rule is used to detect the data packets corresponding to the first task, and the first forwarding action rule is used to forward the data packets corresponding to the first task. The first task identifier can be determined by the SMF network element for the first task and / or the first virtual network group executing the first task. It can be understood that the first task identifier can be used to identify the first task and / or the first virtual network group, and the first task identifier can also be replaced by descriptions such as the first virtual network group identifier.

[0182] The first QoS flow identifier (QFI) can be determined by the SMF network element for the first policy control and charging rules. The QoS flow corresponding to the first QoS flow identifier can be used to transmit data packets associated with the first task received or sent by the first terminal device. The SMF network element can assign the first QoS flow identifier to the first policy control and charging rules corresponding to the first terminal device, thereby establishing a correspondence between the first task, the first terminal device, and the first QoS flow identifier, i.e., the first QoS flow identifier corresponds to the first task and the first terminal device. Here, the first QoS flow identifier is just an example and does not mean that the first task identifier is necessarily associated with the first QoS flow identifier. The SMF network element can determine the QoS flow identifier associated with the first task identifier in the session corresponding to the first terminal device according to the actual situation, and this application does not limit this.

[0183] Optionally, the SMF network element can also determine a second Quality of Service (QoS) flow identifier for the third policy control and charging rule. The QoS flow corresponding to the second QoS flow identifier can be used to transmit data packets associated with the first task received or sent by the second terminal device. The SMF network element can also determine a first packet detection rule and a first forwarding action rule associated with the first packet detection rule based on the second QoS flow identifier. Specifically, the SMF network element can assign a second QoS flow identifier to the third policy control and charging rule corresponding to the second terminal device, thereby establishing a correspondence between the first task, the second terminal device, and the second QoS flow identifier; that is, the second QoS flow identifier corresponds to the first task and the second terminal device. Here, the second QoS flow identifier is merely an example and does not necessarily mean that the identifier associated with the first task is the second QoS flow identifier. The SMF network element can determine the QoS flow identifier associated with the first task identifier in the session corresponding to the second terminal device based on the actual situation; this application does not limit this.

[0184] The first quality of service flow identifier corresponds to the first terminal device, and the second quality of service flow identifier corresponds to the second terminal device.

[0185] It should be noted that the first task identifier here is not the same as the task identifier of the first task mentioned earlier. The first task identifier here is the identifier assigned by the SMF network element. The first task identifier can be understood as a task identifier or virtual network group identifier at the granularity of service quality flow. The first task identifier corresponds to a virtual network group (i.e., the virtual network group that executes the first task).

[0186] The specific content of the first packet detection rule and the first forwarding action rule in this application is not limited; several examples are given below.

[0187] In the first implementation, the first task is performed by a first terminal device and a second terminal device, both of which are located within the service range of the first UPF network element. The first and second terminal devices can be located in a first virtual network group, and other terminal devices in the first virtual network group can also perform the first task.

[0188] Both the first terminal device and the second terminal device are within the service range of the first UPF network element, which can mean that both the first terminal device and the second terminal device are registered in the first UPF network element.

[0189] In this implementation, the first packet detection rule includes a first uplink packet detection rule, a first downlink packet detection rule, a second uplink packet detection rule, and a second downlink packet detection rule; the first forwarding action rule includes a first uplink forwarding action rule associated with the first uplink packet detection rule and a second uplink forwarding action rule associated with the second uplink packet detection rule. The first forwarding action rule may also include a first downlink forwarding action rule associated with the first downlink packet detection rule and a second downlink forwarding action rule associated with the second downlink packet detection rule.

[0190] The first uplink packet detection rule and the first downlink packet detection rule are used to detect data packets sent from the first terminal device to the second terminal device in the first virtual network group; the first uplink forwarding action rule and the first downlink forwarding action rule are used to forward data packets sent from the first terminal device to the second terminal device in the first virtual network group.

[0191] The second uplink packet detection rule and the second downlink packet detection rule are used to detect data packets sent from the second terminal device to the first terminal device in the first virtual network group; the second uplink forwarding action rule and the second downlink forwarding action rule are used to forward data packets sent from the second terminal device to the first terminal device in the first virtual network group.

[0192] One uplink forwarding action rule is associated with one uplink packet detection rule. This means that the uplink packet detection rule includes the identifier of the uplink forwarding action rule. Other cases can be deduced in the same way, and will not be elaborated here.

[0193] In this application, "uplink" in the uplink packet detection rules or uplink forwarding action rules can be replaced with "entry" or other descriptions, and "downlink" in the downlink packet detection rules or downlink forwarding action rules can be replaced with "exit" or other descriptions.

[0194] The first uplink packet detection rule includes the first address information and the first quality of service flow identifier of the first terminal device. For example, the source address field in the first uplink packet detection rule includes the first address information, which can be the IP address of the first terminal device. For example, the QFI field in the first uplink packet detection rule includes the first quality of service flow identifier. The first uplink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field in the first uplink packet detection rule includes the access side interface identifier. Optionally, the first uplink packet detection rule may include a first task identifier. For example, the network instance field in the first uplink packet detection rule includes the first task identifier.

[0195] The first uplink forwarding action rule includes a first task identifier. For example, the network instance field in the first uplink forwarding action rule includes the first task identifier. The first uplink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the first uplink forwarding action rule includes a 5G virtual network internal interface identifier. The 5G virtual network internal interface identifier can indicate a 5G virtual network internal interface, which can also be referred to as a virtual network internal interface.

[0196] The first downlink packet detection rule includes a first task identifier and second address information of the second terminal device. For example, the destination address field in the first downlink packet detection rule includes the second address information. For example, the network instance field in the first downlink packet detection rule includes the first task identifier. The first downlink packet detection rule can be associated with a second quality of service flow identifier; it can be understood that the QER indicated by the QER identifier field in the first downlink packet detection rule includes the second quality of service flow identifier. The first downlink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field of the first downlink packet detection rule includes a 5G virtual network internal interface identifier.

[0197] Optionally, the first downlink forwarding action rule may include a first task identifier. For example, the network instance field in the first downlink forwarding action rule may include a first task identifier. The first downlink forwarding action rule may also include other information, which is not limited in this application.

[0198] The second uplink packet detection rule includes second address information and a second Quality of Service (QoS) flow identifier. For example, the source address field in the second uplink packet detection rule includes the second address information. For example, the QFI field in the second uplink packet detection rule includes the second QoS flow identifier. The second uplink packet detection rule may also include other information, which is not limited in this application. Optionally, the second uplink packet detection rule may include a first task identifier. For example, the network instance field in the second uplink packet detection rule includes the first task identifier.

[0199] The second uplink forwarding action rule includes a first task identifier. For example, the network instance field in the second uplink forwarding action rule includes the first task identifier. The second uplink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the second uplink forwarding action rule includes a 5G virtual network internal interface identifier.

[0200] The second downlink packet detection rule includes a first task identifier and first address information of the first terminal device. For example, the destination address field in the second downlink packet detection rule includes the first address information. For example, the network instance field in the second downlink packet detection rule includes the first task identifier. The second downlink packet detection rule can be associated with a first quality of service flow identifier; it can be understood that the QER indicated by the QER identifier field in the second downlink packet detection rule includes the first quality of service flow identifier. The second downlink packet detection rule may also include other information, which is not limited in this application.

[0201] Optionally, the second downlink forwarding action rule may include the first task identifier. For example, the network instance field in the second downlink forwarding action rule may include the first task identifier. The second downlink forwarding action rule may also include other information, which is not limited in this application.

[0202] The above example only uses the first virtual network group as an example, which includes the first terminal device and the second terminal device. If there are other terminal devices performing the first task, the first packet detection rules and the first forwarding action rules can also include other information. The specifics can be deduced from the above content, and will not be elaborated here.

[0203] In the second implementation, the first task is performed by a first terminal device and a second terminal device. The first terminal device is located within the service range of a first UPF network element, and the second terminal device is located within the service range of a second UPF network element. The first and second terminal devices can be located in a first virtual network group, and other terminal devices in the first virtual network group can also perform the first task.

[0204] In this implementation, the first packet detection rule includes a first uplink packet detection rule, a first downlink packet detection rule, a second uplink packet detection rule, and a second downlink packet detection rule; the first forwarding action rule includes a first uplink forwarding action rule associated with the first uplink packet detection rule, a second uplink forwarding action rule associated with the second uplink packet detection rule, a first downlink forwarding action rule associated with the first downlink packet detection rule, and a second downlink forwarding action rule associated with the second downlink packet detection rule.

[0205] The first uplink packet detection rule and the first downlink packet detection rule are used to detect data packets sent from the first terminal device to the second terminal device in the first virtual network group; the first uplink forwarding action rule and the first downlink forwarding action rule are used to forward data packets sent from the first terminal device to the second terminal device in the first virtual network group.

[0206] The second uplink packet detection rule and the second downlink packet detection rule are used to detect data packets sent from the second terminal device to the first terminal device in the first virtual network group; the second uplink forwarding action rule and the second downlink forwarding action rule are used to forward data packets sent from the second terminal device to the first terminal device in the first virtual network group.

[0207] The first uplink packet detection rule includes the first address information and the first quality of service flow identifier of the first terminal device. For example, the source address field in the first uplink packet detection rule includes the first address information. For example, the QFI field in the first uplink packet detection rule includes the first quality of service flow identifier. The first uplink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field in the first uplink packet detection rule includes the access side interface identifier. Optionally, the first uplink packet detection rule may include a first task identifier. For example, the network instance field in the first uplink packet detection rule includes the first task identifier.

[0208] The first uplink forwarding action rule includes a first task identifier. For example, the network instance field in the first uplink forwarding action rule includes the first task identifier. The first uplink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the first uplink forwarding action rule includes the 5G virtual network internal interface identifier.

[0209] The first downlink packet detection rule includes a first task identifier and second address information of the second terminal device. For example, the destination address field in the first downlink packet detection rule includes the second address information. For example, the network instance field in the first downlink packet detection rule includes the first task identifier. The first downlink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field of the first downlink packet detection rule includes a 5G virtual network internal interface identifier.

[0210] The first downlink forwarding action rule may include a first task identifier. For example, the network instance field in the first downlink forwarding action rule includes the first task identifier. The first downlink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the first downlink forwarding action rule includes a core side interface identifier.

[0211] The second uplink packet detection rule includes the first task identifier. For example, the network instance field in the second uplink packet detection rule includes the first task identifier. The second uplink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field of the first downlink packet detection rule includes the core side interface identifier.

[0212] The second uplink forwarding action rule includes a first task identifier. For example, the network instance field in the second uplink forwarding action rule includes the first task identifier. The second uplink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the second uplink forwarding action rule includes a 5G virtual network internal interface identifier.

[0213] The second downlink packet detection rule includes a first task identifier and first address information of the first terminal device. For example, the destination address field in the second downlink packet detection rule includes the first address information. Similarly, the network instance field in the second downlink packet detection rule includes the first task identifier.

[0214] Optionally, the second downlink packet detection rule can be associated with the first quality of service flow identifier. This can be understood as the QER indicated by the QER identifier field in the second downlink packet detection rule including the first quality of service flow identifier. The second downlink packet detection rule may also include other information, which is not limited in this application.

[0215] Optionally, the second downlink forwarding action rule may include the first task identifier. For example, the network instance field in the second downlink forwarding action rule may include the first task identifier. The second downlink forwarding action rule may also include other information, which is not limited in this application.

[0216] The above example only uses the first virtual network group as an example, which includes the first terminal device and the second terminal device. If there are other terminal devices performing the first task, the first packet detection rules and the first forwarding action rules can also include other information. The specifics can be deduced from the above content, and will not be elaborated here.

[0217] In this implementation, the SMF network element can also send the second packet detection rule corresponding to the first task and the second forwarding action rule associated with the second packet detection rule to the second UPF network element.

[0218] The second packet detection rule includes the third uplink packet detection rule, the third downlink packet detection rule, the fourth uplink packet detection rule, and the fourth downlink packet detection rule; the second forwarding action rule includes the third uplink forwarding action rule associated with the third uplink packet detection rule, the third downlink forwarding action rule associated with the third downlink packet detection rule, the fourth uplink forwarding action rule associated with the fourth uplink packet detection rule, and the fourth downlink forwarding action rule associated with the fourth downlink packet detection rule.

[0219] The third uplink packet detection rule and the third downlink packet detection rule are used to detect data packets sent from the first terminal device to the second terminal device in the first virtual network group; the third uplink forwarding action rule and the third downlink forwarding action rule are used to forward data packets sent from the first terminal device to the second terminal device in the first virtual network group.

[0220] The fourth uplink packet detection rule and the fourth downlink packet detection rule are used to detect data packets sent from the second terminal device to the first terminal device in the first virtual network group; the fourth uplink forwarding action rule and the fourth downlink forwarding action rule are used to forward data packets sent from the second terminal device to the first terminal device in the first virtual network group.

[0221] The third uplink packet detection rule includes the first task identifier. For example, the network instance field in the third uplink packet detection rule includes the first task identifier. The third uplink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field in the third uplink packet detection rule includes the core side interface identifier.

[0222] The third uplink forwarding action rule includes a first task identifier. For example, the network instance field in the third uplink forwarding action rule includes the first task identifier. The third uplink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the third uplink forwarding action rule includes a 5G virtual network internal interface identifier.

[0223] The third downlink packet detection rule includes a first task identifier and second address information of the second terminal device. For example, the destination address field in the third downlink packet detection rule includes the second address information. For example, the network instance field in the third downlink packet detection rule includes the first task identifier. The third downlink packet detection rule is associated with the second quality of service flow identifier, which can be understood as the QER indicated by the QER field in the third downlink packet detection rule including the second quality of service flow identifier. The third downlink packet detection rule may also include other information, which is not limited in this application.

[0224] Optionally, the third downlink forwarding action rule includes a first task identifier. For example, the network instance field in the third downlink forwarding action rule includes the first task identifier. The third downlink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the third downlink forwarding action rule includes an access-side interface identifier.

[0225] The fourth uplink packet detection rule includes second address information and a second quality of service flow identifier. For example, the source address field in the fourth uplink packet detection rule includes the second address information. For example, the QFI field in the fourth uplink packet detection rule includes the second quality of service flow identifier. The fourth uplink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field in the fourth uplink packet detection rule includes the access-side interface identifier. Optionally, the fourth uplink packet detection rule may include a first task identifier. For example, the network instance field in the fourth uplink packet detection rule includes the first task identifier.

[0226] The fourth uplink forwarding action rule includes the first task identifier. For example, the network instance field in the fourth uplink forwarding action rule includes the first task identifier. The fourth uplink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the fourth uplink forwarding action rule includes the 5G virtual network internal interface identifier.

[0227] The fourth downlink packet detection rule includes a first task identifier and first address information, and is associated with a first quality of service flow identifier. For example, the destination address field in the fourth downlink packet detection rule includes the first address information. Similarly, the network instance field in the fourth downlink packet detection rule includes the first task identifier.

[0228] The fourth downlink forwarding action rule includes the first task identifier. For example, the network instance field in the fourth downlink forwarding action rule includes the first task identifier.

[0229] Step 410: The SMF network element sends the first packet detection rule and the first forwarding action rule to the first UPF network element.

[0230] Accordingly, the first UPF network element receives the first packet detection rules and the first forwarding action rules.

[0231] Step 411: The first UPF network element detects the data packet corresponding to the first task according to the first packet detection rule, and forwards the data packet corresponding to the first task according to the first forwarding action rule.

[0232] This method establishes an association between a Quality of Service (QoS) flow and a task at the QoS flow granularity. Since a session can correspond to multiple QoS flows, it enables the establishment of an association between a session and multiple tasks. Based on the association between task identifiers and QoS flow identifiers, it achieves mutual isolation between data packets of different tasks corresponding to the same session, realizing a communication mechanism based on QoS flow granularity isolation.

[0233] The above process takes the first task as an example. Optionally, the first terminal device in this application can also perform a second task, as detailed in the process below.

[0234] Figure 5 shows a flowchart of a communication method provided in an embodiment of this application. The method includes:

[0235] Step 501: The network device sends a second broadcast message, which instructs on the second task.

[0236] Correspondingly, the first terminal device and the third terminal device receive the second broadcast information from the network device.

[0237] The second broadcast message may include the task identifier of the second task. The second broadcast message may also include information such as the task content corresponding to the second task.

[0238] This example uses the first and third terminal devices receiving the second broadcast information, but the actual number of terminal devices receiving the second broadcast information is not limited.

[0239] If the first terminal device determines to perform the second task, the following process can be executed.

[0240] Step 502: The first terminal device determines to execute the second task and sends a second confirmation message, which instructs the first terminal device to determine to execute the second task.

[0241] The first terminal device can send a second confirmation message to the AMF network element through the network device. Optionally, the first terminal device can also send at least one of the following: the task identifier of the second task, the session identifier, the DNN, the S-NSSAI, and the first identifier of the first terminal device. The session identifier, DNN, S-NSSAI, and the first identifier of the first terminal device can be the same as those sent by the first terminal device in step 402, meaning that the first task and the second task correspond to the same session, DNN, and S-NSSAI of the first terminal device. This ensures that the DNN and S-NSSAI used by the first terminal device to execute the first task and the second task are the same, enabling the execution of different tasks through the same configured DNN and S-NSSAI. This eliminates the need for the network side to reconfigure the network resources corresponding to the DNN / S-NSSAI for the terminal device each time it executes a task, improving resource utilization and task execution efficiency.

[0242] This application does not limit how the first terminal device sends the second confirmation information. Other contents of the second confirmation information can be found in the description related to the first confirmation information in step 402.

[0243] If the third terminal device determines to perform the second task, the following process can be executed.

[0244] Step 503: The third terminal device determines to execute the second task and sends a fourth confirmation message, which instructs the third terminal device to determine to execute the second task.

[0245] The third terminal device can send a fourth confirmation message to the AMF network element through the network device. Optionally, the second terminal device can also send at least one of the following: the task identifier of the second task, the session identifier, the DNN, S-NSSAI, and the third identifier of the third terminal device.

[0246] The following example shows how an AMF network element can execute the following process when receiving the second and fourth confirmation messages.

[0247] Step 504: The AMF network element sends the second confirmation message and the fourth confirmation message to the AI-MF network element.

[0248] Correspondingly, the AI-MF network element receives the second and fourth confirmation messages.

[0249] If the AMF network element only receives the second or fourth confirmation message, it can send the second or fourth confirmation message only to the AI-MF network element.

[0250] The AMF network element can also send at least one of the following to the AI-MF network element: the task identifier of the second task, the session identifier, the DNN, the S-NSSAI, the first identifier of the first terminal device, and the third identifier of the third terminal device.

[0251] In one implementation of this application, after receiving the second confirmation information, the AI-MF network element can send third information to the SMF network element, and the third information indicates the second task.

[0252] In another implementation, after receiving the second confirmation information, the AI-MF network element can send the third information to the PCF network element.

[0253] The following description uses the example of an AI-MF network element sending third information to an SMF network element.

[0254] Step 505: The AI-MF network element sends third information to the SMF network element.

[0255] The third piece of information may include the task identifier of the second task.

[0256] Optionally, the third information may also indicate the first terminal device, for example, the third information may include the first identifier of the first terminal device.

[0257] The third information can also indicate service quality requirements, which can be determined by AI-MF network elements. This application does not limit how service quality requirements are determined.

[0258] SMF network elements can forward service quality requests to PCF network elements; the specific process will not be elaborated here.

[0259] Optionally, the third information may further include at least one of the following: a session identifier, a DNN, and an S-NSSAI. The session identifier indicated by the third information may be the same as the session identifier indicated by the first information; the DNN and S-NSSAI indicated by the third information may be the same as the DNN and S-NSSAI indicated by the first information.

[0260] Optionally, the third information may include a group identifier for the second virtual network group. The second task is performed by a terminal device in the second virtual network group, which includes the second terminal device. The group identifier for the second virtual network group may be determined by an AI-MF network element or by other network elements; this application does not limit this.

[0261] Step 506: The PCF network element sends the fourth information to the SMF network element.

[0262] Accordingly, the SMF network element receives the fourth information. The fourth information indicates the second policy control and charging rules corresponding to the first terminal device.

[0263] Before sending the fourth information, the PCF network element can receive service quality requirements from the SMF network element. The PCF network element can then determine the second policy control and billing rules based on the service quality requirements.

[0264] Optionally, step 506 can be replaced by: the SMF network element obtaining the first policy control and charging rule corresponding to the first terminal device according to the local policy. For example, before step 505, the first terminal device has already established a session through the SMF network element. The SMF network element can include the SM context of the session, which can include the local policy. The local policy can include the policy control and charging rule corresponding to the first terminal device, and the SMF network element can use this policy control and charging rule as the second policy control and charging rule.

[0265] Optionally, in another implementation, the SMF network element can receive third and fourth information from the PCF network element. Optionally, the SMF network element can receive second indication information from the PCF network element, the second indication information indicating a mapping relationship between the second policy control and charging rules and the second task.

[0266] Optionally, after receiving the fourth confirmation information from the third terminal device, the AI-MF network element can perform the following process:

[0267] Optionally, in step 507: the AI-MF network element sends the seventh information to the SMF network element.

[0268] Correspondingly, the SMF network element receives the seventh information.

[0269] The seventh piece of information indicates the second task. For example, the seventh piece of information may include the task identifier of the second task.

[0270] Optionally, the seventh information may also indicate a third terminal device, for example, the seventh information may include a third identifier of the third terminal device.

[0271] Optionally, the seventh information may further include at least one of the following: quality of service requirements, session identifier, DNN, and S-NSSAI. The session identifier indicated by the seventh information may be the same as the session identifier indicated by the third information, or the session identifier indicated by the seventh information may be different from the session identifier indicated by the first information; the DNN and S-NSSAI indicated by the seventh information may be the same as the DNN and S-NSSAI indicated by the third information; the quality of service requirements indicated by the seventh information may be the same as or different from the quality of service requirements indicated by the third information.

[0272] Step 508: The PCF network element sends the eighth message to the SMF network element.

[0273] Correspondingly, the SMF network element receives the eighth information. The eighth information indicates the fourth policy control and charging rule corresponding to the third terminal device.

[0274] Before sending the eighth message, the PCF network element can receive service quality requirements from the SMF network element. The PCF network element can then determine the fourth policy control and billing rules based on these service quality requirements.

[0275] Optionally, step 508 can be replaced by: the SMF network element obtaining the fourth policy control and charging rule corresponding to the third terminal device according to the local policy. For example, before step 507, the third terminal device has already established a session through the SMF network element. The SMF network element can include the SM context of the session, which can include the local policy. The local policy can include the policy control and charging rule corresponding to the third terminal device, and the SMF network element can use this policy control and charging rule as the fourth policy control and charging rule.

[0276] Step 509: The SMF network element determines the third packet detection rule and the third forwarding action rule associated with the third packet detection rule based on the second task identifier of the second task, the third service quality flow identifier corresponding to the second policy control and charging rule, and the fourth service quality flow identifier corresponding to the fourth policy control and charging rule.

[0277] The third packet detection rule is used to detect the data packets corresponding to the second task, and the third forwarding action rule is used to forward the data packets corresponding to the second task. The second task identifier can be determined by the SMF network element for the second task and / or the second virtual network group executing the second task. It can be understood that the second task identifier can be used to identify the second task and / or the second virtual network group, and the second task identifier can also be replaced by descriptions such as the second virtual network group identifier.

[0278] The third Quality of Service (QoS) flow identifier can be determined by the SMF network element for the second policy control and charging rules corresponding to the first terminal device. The QoS flow corresponding to the third QoS flow identifier can be used to transmit data packets received or sent by the first terminal device that are associated with the second task. The SMF network element assigns the third QoS flow identifier to the second policy control and charging rules corresponding to the first terminal device, thereby establishing a correspondence between the second task, the first terminal device, and the third QoS flow identifier, that is, the third QoS flow identifier corresponds to the second task and the first terminal device. Here, the third QoS flow identifier is just an example and does not mean that the identifier associated with the second task is necessarily the third QoS flow identifier. The SMF network element can determine the QoS flow identifier associated with the second task identifier in the session corresponding to the first terminal device according to the actual situation, and this application does not limit this.

[0279] Optionally, the SMF network element can also determine a fourth Quality of Service (QoS) flow identifier for the fourth policy control and charging rule. The QoS flow corresponding to the fourth QoS flow identifier can be used to transmit data packets associated with the second task received or sent by the third terminal device. Specifically, the SMF network element assigns a fourth QoS flow identifier to the fourth policy control and charging rule corresponding to the third terminal device, thereby establishing a correspondence between the second task, the third terminal device, and the fourth QoS flow identifier; that is, the fourth QoS flow identifier corresponds to the second task and the third terminal device. Here, the fourth QoS flow identifier is merely an example and does not necessarily mean that the identifier associated with the second task is necessarily the first QoS flow identifier. The SMF network element can determine the QoS flow identifier associated with the second task identifier in the session corresponding to the third terminal device based on actual circumstances; this application does not limit this.

[0280] Among them, the third service quality flow identifier corresponds to the first terminal device, and the fourth service quality flow identifier corresponds to the third terminal device.

[0281] The specific content of the third packet detection rules and the third forwarding action rules is not limited; examples are given below.

[0282] In the first implementation, the second task is performed by the first terminal device and the third terminal device, both of which are located within the service range of the first UPF network element. The first and third terminal devices can be located in a second virtual network group, and other terminal devices in the second virtual network group can also perform the second task.

[0283] In this implementation, the third packet detection rule includes the fifth uplink packet detection rule, the fifth downlink packet detection rule, the sixth uplink packet detection rule, and the sixth downlink packet detection rule; the third forwarding action rule includes the fifth uplink forwarding action rule associated with the fifth uplink packet detection rule and the sixth uplink forwarding action rule associated with the sixth uplink packet detection rule. The third forwarding action rule may also include the fifth downlink forwarding action rule associated with the fifth downlink packet detection rule and the sixth downlink forwarding action rule associated with the sixth downlink packet detection rule.

[0284] Among them, the fifth uplink packet detection rule and the fifth downlink packet detection rule are used to detect data packets sent from the first terminal device to the third terminal device; the fifth uplink forwarding action rule and the fifth downlink forwarding action rule are used to forward data packets sent from the first terminal device to the third terminal device.

[0285] The sixth uplink packet detection rule and the sixth downlink packet detection rule are used to detect data packets sent from the third terminal device to the first terminal device; the sixth uplink forwarding action rule and the sixth downlink forwarding action rule are used to forward data packets sent from the third terminal device to the first terminal device.

[0286] The fifth uplink packet detection rule includes the first address information and the third quality of service flow identifier of the first terminal device. For example, the source address field in the fifth uplink packet detection rule includes the first address information. For example, the QFI field in the fifth uplink packet detection rule includes the third quality of service flow identifier. The fifth uplink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field in the fifth uplink packet detection rule includes the access side interface identifier. Optionally, the fifth uplink packet detection rule may include a second task identifier. For example, the network instance field in the fifth uplink packet detection rule includes the second task identifier.

[0287] The fifth uplink forwarding action rule includes a second task identifier. For example, the network instance field in the fifth uplink forwarding action rule includes the second task identifier. The destination internal field in the fifth uplink forwarding action rule includes the 5G virtual network internal interface identifier.

[0288] The fifth downlink packet detection rule includes a second task identifier and third address information of the third terminal device. For example, the destination address field in the fifth downlink packet detection rule includes the third address information. For example, the network instance field in the fifth downlink packet detection rule includes the second task identifier. The fifth downlink packet detection rule is associated with the fourth quality of service flow identifier, which can be understood as the QER indicated by the QER field in the fifth downlink packet detection rule including the fourth quality of service flow identifier. The fifth downlink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field of the fifth downlink packet detection rule includes the 5G virtual network internal interface identifier.

[0289] Optionally, the fifth downlink forwarding action rule may include a second task identifier. For example, the network instance field in the fifth downlink forwarding action rule may include a second task identifier.

[0290] The sixth uplink packet detection rule includes third address information and a fourth Quality of Service (QoS) flow identifier. For example, the source address field in the sixth uplink packet detection rule includes third address information. For example, the QFI field in the sixth uplink packet detection rule includes the fourth QoS flow identifier. Optionally, the sixth uplink packet detection rule may include a second task identifier. For example, the network instance field in the sixth uplink packet detection rule includes a second task identifier.

[0291] The sixth uplink forwarding action rule includes the second task identifier. For example, the network instance field in the sixth uplink forwarding action rule includes the second task identifier.

[0292] The sixth downlink packet detection rule includes a second task identifier and first address information of the first terminal device. For example, the destination address field in the sixth downlink packet detection rule includes the first address information. Similarly, the network instance field in the sixth downlink packet detection rule includes the second task identifier. The sixth downlink packet detection rule is associated with the third quality of service flow identifier; therefore, it can be understood that the QER indicated by the QER field in the sixth downlink packet detection rule includes the third quality of service flow identifier.

[0293] Optionally, the sixth downlink forwarding action rule may include a second task identifier. For example, the network instance field in the sixth downlink forwarding action rule may include a second task identifier.

[0294] In the second implementation, the second task is performed by a first terminal device and a third terminal device. The first terminal device is located within the service range of a first UPF network element, and the third terminal device is located within the service range of a second UPF network element. The first and third terminal devices can be located in a second virtual network group, and other terminal devices in the second virtual network group can also perform the second task.

[0295] In this implementation, the third packet detection rule includes the fifth uplink packet detection rule, the fifth downlink packet detection rule, the sixth uplink packet detection rule, and the sixth downlink packet detection rule; the third forwarding action rule includes the fifth uplink forwarding action rule associated with the fifth uplink packet detection rule and the sixth uplink forwarding action rule associated with the sixth uplink packet detection rule. The third forwarding action rule may also include the fifth downlink forwarding action rule associated with the fifth downlink packet detection rule and the sixth downlink forwarding action rule associated with the sixth downlink packet detection rule.

[0296] Among them, the fifth uplink packet detection rule and the fifth downlink packet detection rule are used to detect data packets sent from the first terminal device to the third terminal device; the fifth uplink forwarding action rule and the fifth downlink forwarding action rule are used to forward data packets sent from the first terminal device to the third terminal device.

[0297] The sixth uplink packet detection rule and the sixth downlink packet detection rule are used to detect data packets sent from the third terminal device to the first terminal device; the sixth uplink forwarding action rule and the sixth downlink forwarding action rule are used to forward data packets sent from the third terminal device to the first terminal device.

[0298] The fifth uplink packet detection rule includes the first address information and the third quality of service flow identifier of the first terminal device. For example, the source address field in the fifth uplink packet detection rule includes the first address information. For example, the QFI field in the fifth uplink packet detection rule includes the third quality of service flow identifier. The fifth uplink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field in the fifth uplink packet detection rule includes the access side interface identifier. Optionally, the fifth uplink packet detection rule may include a second task identifier. For example, the network instance field in the fifth uplink packet detection rule includes the second task identifier.

[0299] The fifth uplink forwarding action rule includes a second task identifier. For example, the network instance field in the fifth uplink forwarding action rule includes the second task identifier. The fifth uplink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the fifth uplink forwarding action rule includes a 5G virtual network internal interface identifier.

[0300] The fifth downlink packet detection rule includes a second task identifier and third address information of the third terminal device. For example, the destination address field in the fifth downlink packet detection rule includes the third address information. For example, the network instance field in the fifth downlink packet detection rule includes the second task identifier. The fifth downlink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field of the fifth downlink packet detection rule includes the 5G virtual network internal interface identifier.

[0301] The fifth downlink forwarding action rule may include a second task identifier. For example, the network instance field in the fifth downlink forwarding action rule may include a second task identifier. The fifth downlink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the fifth downlink forwarding action rule may include a core side interface identifier.

[0302] The sixth uplink packet detection rule includes a second task identifier. For example, the network instance field in the sixth uplink packet detection rule includes the second task identifier. The sixth uplink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field of the first downlink packet detection rule includes a core side interface identifier.

[0303] The sixth uplink forwarding action rule includes a second task identifier. For example, the network instance field in the sixth uplink forwarding action rule includes the second task identifier. The sixth uplink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the sixth uplink forwarding action rule includes a 5G virtual network internal interface identifier.

[0304] The sixth downlink packet detection rule includes a second task identifier and first address information of the first terminal device. For example, the destination address field in the sixth downlink packet detection rule includes the first address information. For example, the network instance field in the sixth downlink packet detection rule includes the second task identifier. The sixth downlink packet detection rule is associated with the third quality of service flow identifier; it can be understood that the QER indicated by the QER identifier field in the sixth downlink packet detection rule includes the third quality of service flow identifier. The sixth downlink packet detection rule may also include other information, which is not limited in this application.

[0305] Optionally, the sixth downlink forwarding action rule may include a second task identifier. For example, the network instance field in the sixth downlink forwarding action rule may include a second task identifier. The sixth downlink forwarding action rule may also include other information, which is not limited in this application.

[0306] The above example only uses the first virtual network group, which includes the first terminal device and the third terminal device. If there are other terminal devices performing the second task, the third packet detection rules and the third forwarding action rules can also include other information. The specifics can be deduced from the above content, and will not be elaborated here.

[0307] In this implementation, the SMF network element can also send the fourth packet detection rule corresponding to the second task and the fourth forwarding action rule associated with the fourth packet detection rule to the second UPF network element.

[0308] The fourth packet detection rule includes the seventh uplink packet detection rule, the seventh downlink packet detection rule, the eighth uplink packet detection rule, and the eighth downlink packet detection rule; the fourth forwarding action rule includes the seventh uplink forwarding action rule associated with the seventh uplink packet detection rule, the seventh downlink forwarding action rule associated with the seventh downlink packet detection rule, the eighth uplink forwarding action rule associated with the eighth uplink packet detection rule, and the eighth downlink forwarding action rule associated with the eighth downlink packet detection rule.

[0309] Among them, the seventh uplink packet detection rule and the seventh downlink packet detection rule are used to detect data packets sent from the first terminal device to the third terminal device; the seventh uplink forwarding action rule and the seventh downlink forwarding action rule are used to forward data packets sent from the first terminal device to the third terminal device.

[0310] The eighth uplink packet detection rule and the eighth downlink packet detection rule are used to detect data packets sent from the third terminal device to the first terminal device; the eighth uplink forwarding action rule and the eighth downlink forwarding action rule are used to forward data packets sent from the third terminal device to the first terminal device.

[0311] The seventh uplink packet detection rule includes the second task identifier. For example, the network instance field in the seventh uplink packet detection rule includes the second task identifier. The seventh uplink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field in the seventh uplink packet detection rule includes the core side interface identifier.

[0312] The seventh uplink forwarding action rule includes a second task identifier. For example, the network instance field in the seventh uplink forwarding action rule includes the second task identifier. The seventh uplink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the seventh uplink forwarding action rule includes a 5G virtual network internal interface identifier.

[0313] The seventh downlink packet detection rule includes a second task identifier and third address information of the third terminal device. For example, the destination address field in the seventh downlink packet detection rule includes the third address information. For example, the network instance field in the seventh downlink packet detection rule includes the second task identifier. The seventh downlink packet detection rule is associated with the fourth quality of service flow identifier; it can be understood that the QER indicated by the QER identifier field in the seventh downlink packet detection rule includes the fourth quality of service flow identifier. The seventh downlink packet detection rule may also include other information, which is not limited in this application.

[0314] Optionally, the seventh downlink forwarding action rule includes a second task identifier. For example, the network instance field in the seventh downlink forwarding action rule includes a second task identifier. The seventh downlink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the seventh downlink forwarding action rule includes an access-side interface identifier.

[0315] The eighth uplink packet detection rule includes third address information and a fourth quality of service flow identifier. For example, the source address field in the eighth uplink packet detection rule includes third address information. For example, the QFI field in the eighth uplink packet detection rule includes the fourth quality of service flow identifier. The eighth uplink packet detection rule may also include other information, which is not limited in this application. For example, the source internal field in the eighth uplink packet detection rule includes the access-side interface identifier. Optionally, the eighth uplink packet detection rule may include a second task identifier. For example, the network instance field in the eighth uplink packet detection rule includes a second task identifier.

[0316] The eighth uplink forwarding action rule includes a second task identifier. For example, the network instance field in the eighth uplink forwarding action rule includes the second task identifier. The eighth uplink forwarding action rule may also include other information, which is not limited in this application. For example, the destination internal field in the eighth uplink forwarding action rule includes a 5G virtual network internal interface identifier.

[0317] The eighth downlink packet detection rule includes a second task identifier and first address information, and is associated with a third quality of service flow identifier. For example, the destination address field in the eighth downlink packet detection rule includes the first address information. Similarly, the network instance field in the eighth downlink packet detection rule includes the second task identifier.

[0318] The eighth downlink forwarding action rule includes a second task identifier. For example, the network instance field in the eighth downlink forwarding action rule includes a second task identifier.

[0319] In this application, after the first terminal device determines that it will execute the first task and the second task, it transmits the data corresponding to the first task and the second task through the same session. That is, the first task and the second task correspond to the same session of the first terminal device, which can be understood as the first service quality flow identifier and the third service quality flow identifier corresponding to the same session of the first terminal device. In this case, the data packets corresponding to the first task and the data packets corresponding to the second task can be transmitted through different service quality flows of the same session of the first terminal device, which can realize the differentiation of data of different tasks in one session through different service quality flows. In this application, the session can refer to a PDU session.

[0320] Step 510: The SMF network element sends the third packet detection rule and the third forwarding action rule to the first UPF network element.

[0321] Correspondingly, the first UPF network element receives the third packet detection rules and the third forwarding action rules.

[0322] The first UPF network element can also detect the data packets corresponding to the second task according to the third packet detection rules, and forward the data packets corresponding to the second task according to the third forwarding action rules.

[0323] Through the processes shown in Figures 4 and 5, the first terminal device can join a first virtual network group for performing a first task and a second virtual network group for performing a second task in the same session, thereby transmitting data for different tasks through different quality of service streams in the same session.

[0324] In this application, there are no restrictions on how the first UPF network element detects and forwards the data packets corresponding to the first task. Several examples are given below.

[0325] In one implementation, the first terminal device, the second terminal device, and the third terminal device are all located within the service range of the first UPF network element. The first terminal device and the second terminal device perform the first task, and the first terminal device and the third terminal device perform the second task.

[0326] Example 1:

[0327] The first terminal device sends a first data packet for a first task through the network device. The source address of the first data packet is the first address information of the first terminal device, and the destination address of the first data packet is the second address information of the second terminal device. The first data packet includes a first quality of service flow identifier. The first terminal device sends a third data packet for a second task through the network device. The source address of the third data packet is the first address information of the first terminal device, and the destination address of the third data packet is the third address information of the third terminal device. The third data packet includes a third quality of service flow identifier.

[0328] For example, as shown in Figure 6A, the first UPF network element receives a first data packet and a third data packet. The first UPF network element detects a first data packet whose source address is the first address information and includes a first quality of service flow identifier according to the first uplink packet detection rule. Then, according to the first uplink forwarding action rule, it adds a first task identifier to the first data packet and forwards the first data packet to the virtual network internal interface of the first UPF network element according to the first uplink forwarding action rule.

[0329] Similarly, if the first UPF network element detects a third data packet whose source address is the first address information and includes the third service quality flow identifier according to the fifth uplink packet detection rule, then it adds the second task identifier to the third data packet according to the fifth uplink forwarding action rule, and forwards the third data packet to the virtual network internal interface of the first UPF network element according to the fifth uplink forwarding action rule.

[0330] Furthermore, if the first UPF network element detects a first data packet with a destination address of the second address information and including the first task identifier within the virtual network internal interface according to the first downlink packet detection rule, then it forwards the first data packet to the second terminal device through the quality of service flow corresponding to the second quality of service flow identifier according to the first downlink forwarding action rule.

[0331] If the first UPF network element detects a third data packet with a destination address of the third address and including the second task identifier within the internal interface of the virtual network according to the fifth downlink packet detection rule, then it forwards the third data packet to the third terminal device through the quality of service flow corresponding to the fourth quality of service flow identifier according to the fifth downlink forwarding action rule.

[0332] Example 2:

[0333] The second terminal device sends a second data packet for the first task through the network device. The source address of the second data packet is the second address information of the second terminal device, and the destination address of the second data packet is the first address information of the first terminal device. The second data packet includes a second quality of service flow identifier. The third terminal device sends a fourth data packet for the second task through the network device. The source address of the fourth data packet is the third address information of the third terminal device, and the destination address of the fourth data packet is the first address information of the first terminal device. The third data packet includes a fourth quality of service flow identifier.

[0334] For example, as shown in Figure 6B, the first UPF network element receives the second data packet and the fourth data packet. The first UPF network element detects the second data packet, which has the second address information as its source address and includes the second quality of service flow identifier, according to the second uplink packet detection rule. Then, according to the second uplink forwarding action rule, it adds the first task identifier to the second data packet and forwards it to the virtual network internal interface of the first UPF network element according to the second uplink forwarding action rule.

[0335] Similarly, the first UPF network element detects a fourth data packet whose source address is the third address information and includes the fourth service quality flow identifier according to the sixth uplink packet detection rule. Then, according to the sixth uplink forwarding action rule, it adds the second task identifier to the fourth data packet and forwards the fourth data packet to the virtual network internal interface of the first UPF network element according to the sixth uplink forwarding action rule.

[0336] Furthermore, if the first UPF network element detects a second data packet with a destination address of the first address information and including the first task identifier within the virtual network internal interface according to the second downlink packet detection rule, then it forwards the second data packet to the first terminal device through the quality of service flow corresponding to the first quality of service flow identifier according to the second downlink forwarding action rule.

[0337] If the first UPF network element detects a fourth data packet with a destination address of the first address information and including the second task identifier in the interface of the virtual network according to the sixth downlink packet detection rule, then forwards the fourth data packet to the first terminal device through the quality of service flow corresponding to the third quality of service flow identifier according to the sixth downlink forwarding action rule.

[0338] In one implementation, the first terminal device is located within the service range of the first UPF network element, and the second terminal device is located within the service range of the second UPF network element, with the first terminal device and the second terminal device performing the first task as an example.

[0339] Example 3:

[0340] The first terminal device sends a first data packet for the first task through the network device. The source address of the first data packet is the first address information of the first terminal device, and the destination address of the first data packet is the second address information of the second terminal device. The first data packet includes a first quality of service flow identifier.

[0341] The first terminal device sends a third data packet for the second task through the network device. The source address of the third data packet is the first address information of the first terminal device, the destination address of the third data packet is the third address information of the third terminal device, and the third data packet includes a third quality of service flow identifier.

[0342] For example, as shown in Figure 7A, the first UPF network element receives a first data packet and a third data packet. The first UPF network element detects a first data packet whose source address is the first address information and includes a first quality of service flow identifier according to the first uplink packet detection rule. Then, according to the first uplink forwarding action rule, it adds a first task identifier to the first data packet and forwards the first data packet to the virtual network internal interface of the first UPF network element according to the first uplink forwarding action rule.

[0343] If the first UPF network element detects a first data packet with a destination address of the second address information and including the first task identifier within the virtual network internal interface according to the first downlink packet detection rule, then it adds the first task identifier to the first data packet according to the first downlink forwarding action rule, and forwards the first data packet to the second UPF network element corresponding to the second terminal device according to the first downlink forwarding action rule.

[0344] Similarly, if the first UPF network element detects a third data packet whose source address is the first address information and includes the third service quality flow identifier according to the fifth uplink packet detection rule, then it adds the second task identifier to the third data packet according to the fifth uplink forwarding action rule, and forwards the third data packet to the virtual network internal interface of the first UPF network element according to the fifth uplink forwarding action rule.

[0345] If the first UPF network element detects a third data packet with a destination address of the third address and including the second task identifier within the virtual network internal interface according to the fifth downlink packet detection rule, then it adds the second task identifier to the third data packet according to the fifth downlink forwarding action rule, and forwards the third data packet to the second UPF network element corresponding to the third terminal device according to the fifth downlink forwarding action rule.

[0346] Accordingly, if the first data packet of the second UPF includes the first task identifier according to the third uplink packet detection rule, then the first task identifier is added to the first data packet according to the third uplink forwarding action rule, and the first data packet is forwarded to the virtual network internal interface of the second UPF network element according to the third uplink forwarding action rule.

[0347] If the second UPF network element detects a first data packet with a destination address of the second address and including the first task identifier within the internal interface of the virtual network according to the third downlink packet detection rule, then it forwards the first data packet to the second terminal device through the quality of service flow corresponding to the first quality of service flow identifier according to the third downlink forwarding action rule.

[0348] Accordingly, if the second UPF includes the second task identifier in the third data packet according to the seventh uplink packet detection rule, then the second task identifier is added to the third data packet according to the seventh uplink forwarding action rule, and the third data packet is forwarded to the virtual network internal interface of the second UPF network element according to the seventh uplink forwarding action rule.

[0349] If the second UPF network element detects a third data packet with a destination address of the third address and including the second task identifier within the interface of the virtual network according to the seventh downlink packet detection rule, then it forwards the third data packet to the second terminal device through the quality of service flow corresponding to the first quality of service flow identifier according to the seventh downlink forwarding action rule.

[0350] Example 4:

[0351] The second terminal device sends a second data packet for the first task through the network device. The source address of the second data packet is the second address information of the second terminal device, and the destination address of the second data packet is the first address information of the first terminal device. The second data packet includes a second quality of service flow identifier.

[0352] The third terminal device sends the fourth data packet of the second task through the network device. The source address of the fourth data packet is the third address information of the third terminal device, and the destination address of the fourth data packet is the first address information of the first terminal device. The third data packet includes the fourth quality of service flow identifier.

[0353] For example, as shown in Figure 7B, the second UPF network element receives a second data packet and a fourth data packet. The second UPF network element detects a second data packet whose source address is the second address information and includes a second quality of service flow identifier according to the fourth uplink packet detection rule. Then, according to the fourth uplink forwarding action rule, it adds a first task identifier to the second data packet and forwards the second data packet to the virtual network internal interface of the second UPF network element according to the fourth uplink forwarding action rule.

[0354] If the second UPF network element detects a second data packet with a destination address of the first address information and including the first task identifier within the virtual network internal interface according to the fourth downlink packet detection rule, then it adds the first task identifier to the second data packet according to the fourth downlink forwarding action rule, and forwards the second data packet to the first UPF network element corresponding to the first terminal device according to the fourth downlink forwarding action rule.

[0355] Similarly, the second UPF network element detects a fourth data packet whose source address is the third address information and includes the fourth service quality flow identifier according to the eighth uplink packet detection rule. Then, according to the eighth uplink forwarding action rule, it adds the second task identifier to the fourth data packet and forwards the fourth data packet to the virtual network internal interface of the second UPF network element according to the eighth uplink forwarding action rule.

[0356] If the second UPF network element detects a fourth data packet with a destination address of the first address information and including the second task identifier within the virtual network internal interface according to the eighth downlink packet detection rule, then it adds the second task identifier to the third data packet according to the eighth downlink forwarding action rule, and forwards the third data packet to the first UPF network element corresponding to the third terminal device according to the fifth downlink forwarding action rule.

[0357] Accordingly, if the first UPF includes the first task identifier in the second data packet according to the second uplink packet detection rule, then the first task identifier is added to the second data packet according to the second uplink forwarding action rule, and the second data packet is forwarded to the virtual network internal interface of the first UPF network element according to the second uplink forwarding action rule.

[0358] If the first UPF network element detects a second data packet with a destination address of the first address information and including the first task identifier within the virtual network internal interface according to the second downlink packet detection rule, then it forwards the second data packet to the first terminal device through the quality of service flow corresponding to the first quality of service flow identifier according to the second downlink forwarding action rule.

[0359] Accordingly, if the first UPF includes the second task identifier in the fourth data packet according to the sixth uplink packet detection rule, then the second task identifier is added to the fourth data packet according to the sixth uplink forwarding action rule, and the fourth data packet is forwarded to the virtual network internal interface of the first UPF network element according to the sixth uplink forwarding action rule.

[0360] If the first UPF network element detects a fourth data packet with a destination address of the first address information and including the second task identifier in the interface of the virtual network according to the sixth downlink packet detection rule, then forwards the fourth data packet to the first terminal device through the quality of service flow corresponding to the third quality of service flow identifier according to the sixth downlink forwarding action rule.

[0361] Using the above method, UPF network elements can dynamically establish correspondences between the same session and multiple tasks based on the association between task identifiers and quality of service flow identifiers. That is, they can dynamically establish virtual network groups for executing tasks and establish correspondences between tasks, virtual network groups, and sessions. This enables the detection and forwarding of data packets for different tasks based on the granularity of quality of service flow, thereby improving the flexibility of communication.

[0362] Based on the preceding description, the following section uses the session establishment process as an example to describe how SMF network elements establish the association between quality of service flow and tasks within a session.

[0363] Figure 8 shows a flowchart of a communication method provided in an embodiment of this application. The method includes:

[0364] Step 801: AI-MF network element generation, first task.

[0365] Optionally, the AI-MF network element can receive intent information from the AF network element, which is used to instruct the collection of measurement information. For example, the measurement information can be traffic state information, etc., and this application is not limited to this.

[0366] AI-MF network elements can determine the task content of the first task based on intent information. For example, the task content may include measurement information, and the task content may also indicate information such as the accuracy of the measurement information.

[0367] AI-MF network elements can also determine task filtering conditions through UDM network elements. The task filtering conditions indicate the capabilities required to execute the first task, the area information corresponding to the first task, etc.

[0368] Step 802: The AI-MF network element sends a task release message to the AMF network element.

[0369] The task release message may include the task identifier, task content, and area information for the first task. The task identifier can be determined by an AI-MF network element or a UDM network element.

[0370] The AMF network element can be determined by the AI-MF network element. For example, the AI-MF network element selects the AMF network element located in the area indicated by the area information based on the area information.

[0371] Step 803: The AMF network element sends a task release message to the network device.

[0372] Step 804: The network device sends a first broadcast message, which indicates the first task.

[0373] The first broadcast information may include the task identifier, task content, and area information of the first task.

[0374] Network devices can send the first broadcast message periodically, or they can send the first broadcast message in other ways.

[0375] Step 805: The first terminal device sends a session establishment request message.

[0376] The Session Establishment Request Message is used to request the establishment of a PDU session. The Session Establishment Request Message includes the first confirmation information, the task identifier of the first task, the session identifier, the DNN, and S-NSSAI.

[0377] If the first terminal device determines that it will execute the first task and determines that there is no corresponding PDU session between DNN and S-NSSAI, then it can send a session establishment request message.

[0378] Step 806: The AMF network element receives the session establishment request message and sends a group establishment request message to the AI-MF network element.

[0379] The group creation request message includes first confirmation information, the task identifier of the first task, the session identifier, the DNN, S-NSSAI, and the first identifier of the first terminal device. The group creation request message can be used to request the creation of a virtual network group corresponding to the first task. The name of the group creation request message is just an example; other names are also possible.

[0380] Among them, the AMF network element can receive session establishment request messages through network devices, and the specific process is not limited.

[0381] Step 807: The AI-MF network element sends the first information to the SMF network element.

[0382] The first information may indicate the first task. Optionally, the first information may include quality of service requirements.

[0383] Optionally, the first information may also include the task identifier of the first task, the session identifier, the DNN, the S-NSSAI, and the first identifier of the first terminal device.

[0384] Optionally, after receiving the first group establishment request message including the first confirmation information and the task identifier of the first task, the AI-MF network element can start a timer. The timer's duration is either preset or determined by the AI-MF network element. When the timer expires, the AI-MF network element can then count and determine the number of terminal devices executing the first task.

[0385] During the timer's countdown, if the AI-MF network element receives multiple group establishment request messages including a first confirmation message and a task identifier for the first task, it can determine that multiple terminal devices are executing the first task. The AI-MF network element can indicate the identifiers of the multiple terminal devices through the first message; or, the AI-MF network element can send multiple first messages, with one of the first messages corresponding to one of the multiple terminal devices.

[0386] After receiving the first information, the SMF network element can obtain the session management subscription data of the session; the specific process will not be described in detail here.

[0387] Step 808: The SMF network element sends an acknowledgment message to the AI-MF network element, indicating that the first information has been successfully received.

[0388] The specific content of the confirmation message is not limited and will not be elaborated here.

[0389] Step 809: The AI-MF network element sends a group establishment response message to the AMF network element.

[0390] The specific content of the group creation response message is not limited and will not be elaborated here.

[0391] Step 810: The SMF network element sends a Session Management Policy Control Update message to the PCF network element.

[0392] Optionally, the session management policy controls update messages to include quality of service requirements.

[0393] Optionally, SMF network elements can also use local policies to obtain service quality requirements; the specific process will not be elaborated here.

[0394] Step 811: The PCF network element sends a Session Management Policy Control Update Response message to the SMF network element. The Session Management Policy Control Update Response message includes second information, which indicates the first policy control and charging rules.

[0395] Among them, the PCF network element can determine the first policy control and billing rules according to the service quality requirements, and the specific process is not limited.

[0396] SMF network elements can determine the first task identifier for the first task based on the first information, and determine the first quality of service flow identifier for the first policy control and billing rules based on the second information, thereby establishing an association (or mapping) relationship between the first quality of service flow identifier and the first task identifier.

[0397] SMF network elements can determine the first packet detection rule and the first forwarding action rule associated with the first packet detection rule based on the first task identifier and the first service quality flow identifier.

[0398] Optionally, steps 810 and 811 can also be replaced by: the SMF network element obtaining the first policy control and billing rules corresponding to the first terminal device according to the local policy.

[0399] Step 812: The SMF network element sends an N4 session establishment request message to the first UPF network element. The N4 session establishment request message includes the first packet detection rule and the first forwarding action rule.

[0400] The first terminal device is located within the service range of the first UPF network element.

[0401] Optionally, the N4 session establishment request message may also include the QoS enforcement rule associated with the first packet detection rule.

[0402] Taking the first UPF network element as an example, if other UPF network elements, such as the second UPF network element, also include the terminal device performing the first task within their service range, the SMF network element can also send a group-level N4 rule session establishment request message or a packet forwarding control protocol (PFCP) session establishment request message, or an N4 session establishment request message, to other UPF network elements. The specific process will not be elaborated here. Among them, the N4 session is also called a PFCP session.

[0403] Step 813: The first UPF network element sends an N4 session establishment response message to the SMF network element.

[0404] Step 814: The SMF network element sends a Communication_N1N2MessageTransfer message to the AMF network element.

[0405] The communication N1N2 message transmission message may include the N1 session management (SM) container and the N2 session management information.

[0406] Step 815: The AMF network element sends an N2 PDU Session Request message to the network device.

[0407] The N2 PDU session request message includes non-access stratum (NAS) messages. NAS messages may include the N1 SM container, which includes the PDU session establishment accept message.

[0408] Step 816: The network device sends a PDU session establishment accept message to the first terminal device.

[0409] Network devices can also allocate RAN tunnel information for PDU sessions; the specific process will not be elaborated here.

[0410] Step 817: The network device sends an N2 PDU session response message to the AMF network element.

[0411] The N2 PDU session response message may include access network (AN) tunnel information (Tunnel Info), which includes the access network address of the N3 tunnel corresponding to the PDU session.

[0412] Furthermore, AMF, SMF, and UPF network elements can establish a session corresponding to the first task based on information such as the session management context (SM context) of the PDU session. After the session corresponding to the first task is established, the terminal devices executing the first task can transmit data packets corresponding to the first task through this session, and network elements such as the UPF network element can forward the data packets corresponding to the first task. The specific process will not be elaborated further.

[0413] Based on the preceding description, if the first terminal device determines to execute a second task after determining to execute the first task, the first terminal device can initiate a session modification process in the session corresponding to the first task to establish a correspondence between the second task and the session. For details, please refer to the following description.

[0414] Figure 9 shows a flowchart of a communication method provided in an embodiment of this application. The method includes:

[0415] Step 901: AI-MF network element generation second task.

[0416] Step 902: The AI-MF network element sends a task release message to the AMF network element.

[0417] The task release message may include the task identifier, task content, and area information for the second task. The task identifier can be determined by an AI-MF network element or a UDM network element.

[0418] Step 903: The AMF network element sends a task release message to the network device.

[0419] Step 904: The network device sends a second broadcast message, which instructs on the second task.

[0420] The second broadcast information may include the mission identifier, mission content, and area information of the second mission.

[0421] The specific details of steps 901 to 904 can be found in the descriptions of steps 801 to 804, and will not be repeated here.

[0422] Step 905: The first terminal device sends a session modification request message.

[0423] The Session Modification Request message is used to request modification of the PDU session. The Session Establishment Request message includes the second confirmation information, the task identifier of the second task, the session identifier, the DNN, and S-NSSAI.

[0424] If the first terminal device determines that it is executing the second task and determines that a PDU session has been established in DNN and S-NSSAI, then it can send a session modification request message.

[0425] The session identifier, DNN, and S-NSSAI included in the session modification request message can be the same as those included in the session identifier, DNN, and S-NSSAI in the session establishment request message in step 804.

[0426] Step 906: The AMF network element receives the session establishment modification message and sends a group establishment request message to the AI-MF network element.

[0427] Among them, the AMF network element can receive session establishment request messages through network devices, and the specific process is not limited.

[0428] Step 907: The AI-MF network element sends third information to the SMF network element.

[0429] The third piece of information can instruct the second task. Optionally, the third piece of information may include quality of service requirements.

[0430] Optionally, the third information may also include the task identifier of the second task, the session identifier, the DNN, the S-NSSAI, and the first identifier of the first terminal device.

[0431] After receiving the first information, the SMF network element can obtain the session management subscription data of the session; the specific process will not be described in detail here.

[0432] Step 908: The SMF network element sends an acknowledgment message to the AI-MF network element, indicating that the third information has been successfully received.

[0433] The specific content of the confirmation message is not limited and will not be elaborated here.

[0434] Step 909: The AI-MF network element sends a group establishment response message to the AMF network element.

[0435] The specific content of the group creation response message is not limited and will not be elaborated here.

[0436] Step 910: The SMF network element sends a session management policy control update message to the PCF network element.

[0437] Optionally, the session management policy controls update messages to include quality of service requirements.

[0438] Step 911: The PCF network element sends a session management policy control update response message to the SMF network element. The session management policy control update response message includes fourth information, which indicates the second policy control and billing rules.

[0439] Among them, the PCF network element can determine the second policy control and billing rules according to the service quality requirements, and the specific process is not limited.

[0440] SMF network elements can determine the second task identifier for the second task based on the third information, and determine the third service quality flow identifier for the second policy control and billing rules based on the fourth information, thereby establishing an association (or mapping) relationship between the third service quality flow identifier and the second task identifier.

[0441] SMF network elements can determine the third packet detection rule and the associated third forwarding action rule based on the second task identifier and the third service quality flow identifier.

[0442] Optionally, steps 910 and 911 can also be replaced by: the SMF network element obtaining the first policy control and billing rules corresponding to the first terminal device according to the local policy.

[0443] Step 912: The SMF network element sends an N4 session establishment request message to the first UPF network element. The N4 session establishment request message includes (the third packet detection rule and the third forwarding action rule).

[0444] The first terminal device is located within the service range of the first UPF network element.

[0445] Optionally, the N4 session establishment request message may also include QoS enforcement rules associated with the third packet detection rule.

[0446] Taking the first UPF network element as an example, if the service range of other UPF network elements, such as the second UPF network element, also includes the terminal device performing the first task, the SMF network element can also send a group-level N4 rule session establishment request message or a PFCP session establishment request message, or an N4 session establishment request message, to other UPF network elements. The specific process will not be elaborated here. Among them, the N4 session is also called the PFCP session.

[0447] Step 913: The first UPF network element sends an N4 session establishment response message to the SMF network element.

[0448] Step 914: The SMF network element sends a Communication_N1N2 Message Transfer message to the AMF network element.

[0449] The communication N1N2 message transmission message may include the N1 session management (SM) container and the N2 session management information.

[0450] Step 915: The AMF network element sends an N2 PDU Session Request message to the network device.

[0451] The N2 PDU session request message includes non-access stratum (NAS) messages. NAS messages may include the N1 SM container, which includes the PDU session establishment accept message.

[0452] Step 916: The network device sends a PDU session establishment accept message to the first terminal device.

[0453] Network devices can also allocate RAN tunnel information for PDU sessions; the specific process will not be elaborated here.

[0454] Step 917: The network device sends an N2 PDU session response message to the AMF network element.

[0455] The N2 PDU session response message may include access network (AN) tunnel information (Tunnel Info), which includes the access network address of the N3 tunnel corresponding to the PDU session.

[0456] Furthermore, AMF, SMF, and UPF network elements can modify the session based on information such as the session management context (SM context) of the PDU session, thereby establishing a correspondence between the session and the second task. After the session corresponding to the second task is established, the terminal devices executing the second task can transmit data packets corresponding to the second task through this session. Network elements such as the UPF network element can forward data packets corresponding to the first task. The specific process will not be elaborated further.

[0457] This method allows for the dynamic creation of a new second task and a second virtual network group on an existing session, enabling the transmission of the second task's data through that session. This improves the flexibility of virtual network group creation and communication.

[0458] In the process shown in Figure 8 or Figure 9, in step 805 or step 905, the session establishment request message or session modification request message sent by the first terminal device is replaced with a first message. The first message includes first confirmation information or second confirmation information, the task identifier of the first task or the task identifier of the second task, a session identifier, DNN, and S-NSSAI. Since the first message is used for messages other than requesting the establishment or modification of a PDU session, steps 807 to 812 can be replaced with the following process:

[0459] Figure 10 shows a flowchart of a communication method provided in an embodiment of this application. The method includes:

[0460] Step 1001: The AI-MF network element sends a task resource scheduling message to the PCF network element.

[0461] The task resource scheduling message may include quality of service requirements, the task identifier of the first task, the session identifier, DNN, S-NSSAI, and the first identifier of the first terminal device.

[0462] PCF network elements can determine the first policy control and billing rules based on service quality requirements.

[0463] After receiving the task resource scheduling message, the PCF network element can trigger the modification process to establish the first quality of service flow corresponding to the first task.

[0464] Step 1002: The PCF network element sends the first information and the second information to the SMF network element.

[0465] The PCF network element can also send the first instruction information to the SMF network element. The first instruction information indicates that there is a mapping relationship between the first policy control and billing rules and the first task, which will not be elaborated here.

[0466] The SMF network element can determine the first task identifier for the first task based on the first information, and determine the first service quality flow identifier for the first policy control and billing rules based on the second information.

[0467] SMF network elements can determine the first packet detection rule and the first forwarding action rule associated with the first packet detection rule based on the first task identifier and the first service quality flow identifier.

[0468] Step 1003: The SMF network element sends an N4 session establishment or modification request message to the first UPF network element. The N4 session establishment or modification request message includes (the first packet detection rule and the first forwarding action rule).

[0469] The first terminal device is located within the service range of the first UPF network element.

[0470] The process after step 1003 can be referred to the descriptions in steps 813 to 817, and will not be repeated here.

[0471] Similarly, steps 907 to 912 can be replaced with the above process, as detailed in the preceding description, and will not be repeated here.

[0472] It is understood that, in order to implement the functions in the above embodiments, the terminal device or session management function network element or the first user plane function network element includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0473] The following are schematic diagrams of possible communication devices provided in the embodiments of this application. These communication devices can be used to implement the functions of terminal devices, session management function network elements, or first user plane function network elements in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0474] Figure 11 shows a schematic diagram of a communication device provided in an embodiment of this application. The communication device 1100 can be used to implement the methods implemented by the terminal device, session management function network element, or first user plane function network element in any of the above method embodiments.

[0475] The communication device 1100 includes at least one processor 1101. The processor 1101 can be used for internal processing within the device to implement certain control processing functions. Optionally, the processor 1101 includes instructions. Optionally, the processor 1101 can store data. Optionally, different processors can be independent devices, located in different physical locations, or located on different integrated circuits. Optionally, different processors can be integrated into one or more processors, for example, integrated onto one or more integrated circuits.

[0476] Optionally, the communication device 1100 includes one or more memories 1103 for storing instructions. Optionally, the memories 1103 may also store data. The processor and the memories may be separate or integrated together.

[0477] Optionally, the communication device 1100 includes a communication line 1102 and at least one communication interface 1104. Since the memory 1103, communication line 1102, and communication interface 1104 are all optional, they are all represented by dashed lines in Figure 11.

[0478] Optionally, the communication device 1100 may further include a transceiver and / or an antenna. The transceiver can be used to send information to or receive information from other devices. The transceiver may be referred to as a transceiver unit, transceiver circuit, input / output interface, etc., and is used to realize the transmission and reception functions of the communication device 1100 via the antenna. Optionally, the transceiver includes a transmitter and a receiver. For example, the transmitter can be used to generate a radio frequency (RF) signal from a baseband signal, and the receiver can be used to convert the RF signal back into a baseband signal.

[0479] Processor 1101 may include a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs according to the present application.

[0480] Communication line 1102 may include a path for transmitting information between the aforementioned components.

[0481] Communication interface 1104 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), wired access network, etc.

[0482] The memory 1103 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1103 may exist independently and be connected to the processor 1101 via communication line 1102. Alternatively, the memory 1103 may be integrated with the processor 1101.

[0483] The memory 1103 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 1101. The processor 1101 executes the computer execution instructions stored in the memory 1103, thereby implementing the steps performed by the terminal device, session management function network element, or first user plane function network element in any of the embodiments shown in Figures 4-5, 6A-6B, 7A-7B, and 8-10.

[0484] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0485] In a specific implementation, as one embodiment, processor 1101 may include one or more CPUs, such as CPU0 and CPU1 in FIG11.

[0486] In a specific implementation, as one embodiment, the communication device 1100 may include multiple processors, such as processor 1101 and processor 1105 in FIG. 11. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, a processor may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0487] When the device shown in Figure 11 is a chip, such as a chip for a session management function network element, a chip for a first user plane function network element, or a chip for a terminal device, the chip includes a processor 1101 (and may also include a processor 1105), a communication line 1102, and a communication interface 1104. Optionally, it may include a memory 1103. Specifically, the communication interface 1104 may be an input interface, pins, or circuits, etc. The memory 1103 may be a register, cache, etc. The processor 1101 and processor 1105 may be a general-purpose CPU, microprocessor, ASIC, or one or more integrated circuits for controlling the execution of a program that controls the communication method of any of the above embodiments.

[0488] This application embodiment can divide the device into functional modules according to the above method examples. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or software functional modules. The module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may exist in actual implementation. For example, in the case of dividing each functional module according to its corresponding function, Figure 12 is a schematic diagram of a device. This device 1200 can be a terminal device, a session management function network element, or a first user plane function network element involved in the above method embodiments, or a chip in a session management function network element, a chip in a first user plane function network element, or a chip in a terminal device. The device 1200 includes a processing unit 1202 and a communication unit 1201.

[0489] It should be understood that the communication device 1200 can be used to implement the steps executed by the terminal device, the session management function network element, or the first user plane function network element in the communication method of the embodiments of this application. The relevant features can be referred to the embodiments shown in any one of the above figures 4-5, 6A-6B, 7A-7B, and 8-10, which will not be repeated here.

[0490] Optionally, the functions / implementation processes of the communication unit 1201 and processing unit 1202 in Figure 12 can be implemented by the processor 1101 in Figure 11 calling computer execution instructions stored in memory 1103. Alternatively, the functions / implementation processes of the processing unit 1202 in Figure 12 can be implemented by the processor 1101 in Figure 11 calling computer execution instructions stored in memory 1103, and the functions / implementation processes of the communication unit 1201 in Figure 12 can be implemented by the communication interface 1104 in Figure 11.

[0491] Optionally, when the device 1200 is a chip or circuit, the function / implementation process of the communication unit 1201 can also be implemented through pins or circuits, etc. Optionally, the communication unit 1201 may include a transmitting unit and / or a receiving unit, whereby the transmitting unit implements the transmitting function and the receiving unit implements the receiving function; or, the communication unit 1201 may be an integral module capable of implementing both transmitting and / or receiving functions. Optionally, the communication unit 1201 can be implemented using a transceiver.

[0492] In one implementation, the device is used to implement the functions of the session management network element, specifically:

[0493] A communication unit is used to receive first information and second information, wherein the first information indicates a first task and the second information indicates a first policy control and billing rule corresponding to a first terminal device, and the first terminal device is used to execute the first task.

[0494] The processing unit is configured to determine a first packet detection rule and a first forwarding action rule associated with the first packet detection rule based on the first task identifier of the first task and the first service quality flow identifier corresponding to the first policy control and charging rule; wherein, the first packet detection rule is used to detect the data packet corresponding to the first task, and the first forwarding action rule is used to forward the data packet corresponding to the first task;

[0495] The communication unit is used to send the first packet detection rule and the first forwarding action rule to the first user plane functional network element, wherein the first terminal device is located within the service range of the first user plane functional network element.

[0496] In one implementation, the device is used to implement the functions of the first user plane functional network element, specifically:

[0497] A communication unit is configured to receive a first packet detection rule and a first forwarding action rule associated with the first packet detection rule; the first packet detection rule is used to detect data packets corresponding to a first task, and the first forwarding action rule is used to forward data packets corresponding to the first task; the first packet detection rule and the first forwarding action rule are determined based on a first task identifier of the first task and a first quality of service flow identifier of a first policy control and charging rule corresponding to the first terminal device; the first terminal device is used to execute the first task.

[0498] The communication unit is configured to detect the data packet corresponding to the first task according to the first packet detection rule, and forward the data packet corresponding to the first task according to the first forwarding action rule.

[0499] In one implementation, the device is used to implement the functions of a terminal device, specifically:

[0500] A communication unit is configured to receive first broadcast information from a network device, wherein the first broadcast information indicates a first task;

[0501] The processing unit is configured to determine whether to execute the first task and send first confirmation information through the communication unit, wherein the first confirmation information indicates that the first task will be executed.

[0502] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the methods performed by the session management function network element and / or the first user plane function network element and / or the terminal device in the aforementioned method embodiments. Thus, the functions described in the above embodiments can be implemented as software functional units and sold or used as independent products. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to it, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0503] This application also provides a computer program product comprising: computer program code, which, when executed on a computer, causes the computer to perform the method executed by the session management function network element and / or the first user plane function network element and / or the terminal device in any of the foregoing method embodiments.

[0504] This application also provides a processing apparatus, including a processor and an interface; the processor is used to execute the methods performed by the session management function network element and / or the first user plane function network element and / or the terminal device involved in any of the above method embodiments.

[0505] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0506] The various illustrative logic units and circuits described in the embodiments of this application can be implemented or operate the described functions using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor; alternatively, it can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0507] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0508] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. Of course, the processor and storage medium can also exist as discrete components in the base station or terminal.

[0509] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0510] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0511] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0512] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0513] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0514] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, include: The device receives first information and second information, wherein the first information indicates a first task and the second information indicates a first policy control and billing rule corresponding to the first terminal device, and the first terminal device is used to execute the first task. The first packet detection rule and the first forwarding action rule associated with the first packet detection rule are determined based on the first task identifier of the first task and the first service quality flow identifier corresponding to the first policy control and charging rule; wherein, the first packet detection rule is used to detect the data packet corresponding to the first task, and the first forwarding action rule is used to forward the data packet corresponding to the first task; The first packet detection rule and the first forwarding action rule are sent to the first user plane function network element, and the first terminal device is located within the service range of the first user plane function network element.

2. The method according to claim 1, characterized in that, The first task is performed by the first terminal device and the second terminal device, with the second terminal device located within the service range of the first user plane function network element. The first packet detection rule includes a first uplink packet detection rule, a first downlink packet detection rule, a second uplink packet detection rule, and a second downlink packet detection rule; the first forwarding action rule includes a first uplink forwarding action rule associated with the first uplink packet detection rule and a second uplink forwarding action rule associated with the second uplink packet detection rule; The first uplink packet detection rule includes the first address information of the first terminal device and the first quality of service flow identifier; the first downlink packet detection rule includes the first task identifier and the second address information of the second terminal device; and the first uplink forwarding action rule includes the first task identifier. The second uplink packet detection rule includes the second address information and the second quality of service flow identifier corresponding to the second terminal device; the second downlink packet detection rule includes the first task identifier and the first address information; and the second uplink forwarding action rule includes the first task identifier.

3. The method according to claim 1, characterized in that, The first task is performed by the first terminal device and the second terminal device, with the second terminal device located within the service range of the second user plane function network element; The first packet detection rule includes a first uplink packet detection rule, a first downlink packet detection rule, a second uplink packet detection rule, and a second downlink packet detection rule; the first forwarding action rule includes a first uplink forwarding action rule associated with the first uplink packet detection rule, a second uplink forwarding action rule associated with the second uplink packet detection rule, and a first downlink forwarding action rule associated with the first downlink packet detection rule. The first uplink packet detection rule includes the first address information of the first terminal device and the first quality of service flow identifier; the first downlink packet detection rule includes the first task identifier and the second address information of the second terminal device; the first uplink forwarding action rule includes the first task identifier; and the first downlink forwarding action rule includes the first task identifier. The second uplink packet detection rule includes the first task identifier, the second downlink packet detection rule includes the first task identifier and the first address information, and the second uplink forwarding action rule includes the first task identifier.

4. The method according to claim 3, characterized in that, The method further includes: Send the second packet detection rule corresponding to the first task and the second forwarding action rule associated with the second packet detection rule to the second user plane function network element; The second packet detection rule includes a third uplink packet detection rule, a third downlink packet detection rule, a fourth uplink packet detection rule, and a fourth downlink packet detection rule; the second forwarding action rule includes a third uplink forwarding action rule associated with the third uplink packet detection rule, a fourth uplink forwarding action rule associated with the fourth uplink packet detection rule, and a fourth downlink forwarding action rule associated with the fourth downlink packet detection rule. The third uplink packet detection rule includes the first task identifier, the third downlink packet detection rule includes the first task identifier and the second address information of the second terminal device, and the third uplink forwarding action rule includes the first task identifier; The fourth uplink packet detection rule includes the second address information and the second service quality flow identifier corresponding to the second terminal device; the fourth downlink packet detection rule includes the first task identifier and the first address information; the fourth uplink forwarding action rule includes the first task identifier; and the fourth downlink forwarding action rule includes the first task identifier.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Receive first instruction information, which indicates that there is a mapping relationship between the first policy control and billing rules and the first task.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: The device receives third information and fourth information, wherein the third information indicates a second task and the fourth information indicates a second policy control and billing rule corresponding to the first terminal device, and the first terminal device is used to execute the second task. The third packet detection rule and the third forwarding action rule associated with the third packet detection rule are determined based on the second task identifier of the second task and the third service quality flow identifier corresponding to the second policy control and charging rule; wherein, the third packet detection rule is used to detect the data packet corresponding to the second task, and the third forwarding action rule is used to forward the data packet corresponding to the second task; The third packet detection rule and the third forwarding action rule are sent to the first user plane function network element.

7. The method according to claim 6, characterized in that, The third quality of service flow identifier and the first quality of service flow identifier correspond to the same session of the first terminal device.

8. A communication method, characterized in that, include: The system receives a first packet detection rule and a first forwarding action rule associated with the first packet detection rule. The first packet detection rule is used to detect data packets corresponding to the first task, and the first forwarding action rule is used to forward data packets corresponding to the first task. The first packet detection rule and the first forwarding action rule are determined based on the first task identifier of the first task and the first quality of service flow identifier of the first policy control and charging rule corresponding to the first terminal device. The first terminal device is used to execute the first task. The data packets corresponding to the first task are detected according to the first packet detection rule, and the data packets corresponding to the first task are forwarded according to the first forwarding action rule.

9. The method according to claim 8, characterized in that, The first task is performed by the first terminal device and the second terminal device, which are located within the service range of the first user plane function network element. The first packet detection rule includes a first uplink packet detection rule, a first downlink packet detection rule, a second uplink packet detection rule, and a second downlink packet detection rule; the first forwarding action rule includes a first uplink forwarding action rule associated with the first uplink packet detection rule and a second uplink forwarding action rule associated with the second uplink packet detection rule; The first uplink packet detection rule includes the first address information of the first terminal device and the first quality of service flow identifier; the first downlink packet detection rule includes the first task identifier and the second address information of the second terminal device; and the first uplink forwarding action rule includes the first task identifier. The second uplink packet detection rule includes the second address information and the second quality of service flow identifier corresponding to the second terminal device; the second downlink packet detection rule includes the first task identifier and the first address information; and the second uplink forwarding action rule includes the first task identifier.

10. The method according to claim 9, characterized in that, The step of detecting the data packet corresponding to the first task according to the first packet detection rule, and forwarding the data packet corresponding to the first task according to the first forwarding action rule, includes: If a first data packet with the source address of the first address information and including the first quality of service flow identifier is detected according to the first uplink packet detection rule, then the first task identifier is added to the first data packet according to the first uplink forwarding action rule, and the first data packet is forwarded to the virtual network internal interface according to the first uplink forwarding action rule. If, within the virtual network internal interface, the first data packet whose destination address is the second address information and includes the first task identifier is detected according to the first downlink packet detection rule, then the first data packet is forwarded to the second terminal device through the quality of service flow corresponding to the second quality of service flow identifier of the second terminal device.

11. The method according to claim 8, characterized in that, The first task is performed by the first terminal device and the second terminal device, wherein the first terminal device is located within the service range of the first user plane function network element and the second terminal device is located within the service range of the second user plane function network element. The first packet detection rule includes a first uplink packet detection rule, a first downlink packet detection rule, a second uplink packet detection rule, and a second downlink packet detection rule; the first forwarding action rule includes a first uplink forwarding action rule associated with the first uplink packet detection rule, a second uplink forwarding action rule associated with the second uplink packet detection rule, and a first downlink forwarding action rule associated with the first downlink packet detection rule. The first uplink packet detection rule includes the first address information of the first terminal device and the first quality of service flow identifier; the first downlink packet detection rule includes the first task identifier and the second address information of the second terminal device; the first uplink forwarding action rule includes the first task identifier; and the first downlink forwarding action rule includes the first task identifier. The second uplink packet detection rule includes the first task identifier, the second downlink packet detection rule includes the first task identifier and the first address information, and the second uplink forwarding action rule includes the first task identifier.

12. The method according to claim 11, characterized in that, The step of detecting the data packet corresponding to the first task according to the first packet detection rule, and forwarding the data packet corresponding to the first task according to the first forwarding action rule, includes: If a first data packet with the source address of the first address information and including the first quality of service flow identifier is detected according to the first uplink packet detection rule, then the first task identifier is added to the first data packet according to the first uplink forwarding action rule, and the first data packet is forwarded to the virtual network internal interface according to the first uplink forwarding action rule. If, within the virtual network internal interface, the first data packet whose destination address is the second address information and includes the first task identifier is detected according to the first downlink packet detection rule, then the first task identifier is added to the first data packet according to the first downlink forwarding action rule, and the first data packet is forwarded to the second user plane function network element corresponding to the second terminal device according to the first downlink forwarding action rule.

13. The method according to claim 11 or 12, characterized in that, The step of detecting the data packet corresponding to the first task according to the first packet detection rule, and forwarding the data packet corresponding to the first task according to the first forwarding action rule, includes: If a second data packet including the first task identifier is detected according to the second uplink packet detection rule, then the first task identifier is added to the second data packet according to the second uplink forwarding action rule, and the second data packet is forwarded to the virtual network internal interface according to the second uplink forwarding action rule. If a second data packet with the destination address of the first address information and including the first task identifier is detected within the virtual network internal interface according to the second downlink packet detection rule, the second data packet is forwarded to the first terminal device through the quality of service flow corresponding to the first quality of service flow identifier.

14. The method according to any one of claims 8 to 10, characterized in that, The method further includes: The system receives a third packet detection rule and a third forwarding action rule associated with the third packet detection rule from the session management function network element; wherein the third packet detection rule is used to detect data packets corresponding to the second task, and the third forwarding action rule is used to forward data packets corresponding to the second task; the third packet detection rule and the third forwarding action rule are determined based on the second task identifier of the second task and the third service quality flow identifier corresponding to the first terminal device.

15. The method according to claim 14, characterized in that, The third quality of service flow identifier and the first quality of service flow identifier correspond to the same session of the first terminal device.

16. A communication method, characterized in that, include: Receive a first broadcast message from a network device, the first broadcast message indicating a first task; The system determines that the first task will be executed and sends a first confirmation message, which indicates that the first task will be executed.

17. The method according to claim 16, characterized in that, The method further includes: Receive a second broadcast message from the network device, the broadcast message indicating a second task; The system confirms that the second task will be executed and sends a second confirmation message, which indicates that the second task will be executed.

18. The method according to claim 17, characterized in that, The method further includes: The first data packet corresponding to the first task is sent through the quality of service flow corresponding to the first quality of service flow identifier; The second data packet corresponding to the second task is sent through the quality of service flow corresponding to the third quality of service flow identifier; The third quality of service flow identifier and the first quality of service flow identifier correspond to the same session.

19. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1 to 7, or a module for performing the method as described in any one of claims 8 to 15, or a module for performing the method as described in any one of claims 16 to 18.

20. A communication device, characterized in that, The communication device includes a processor, which is configured to perform the method as described in any one of claims 1 to 7, or the method as described in any one of claims 8 to 15, or the method as described in any one of claims 16 to 18.

21. A communication system, characterized in that, This includes terminal equipment, session management function network elements, and first user plane function network elements, among which, The session management function network element is used to perform the method as described in any one of claims 1 to 7, the first user plane function network element is used to perform the method as described in any one of claims 8 to 15, and the terminal device is used to perform the method as described in any one of claims 16 to 18.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer, causes the method as described in any one of claims 1 to 7 to be performed, or causes the method as described in any one of claims 8 to 15 to be performed, or causes the method as described in any one of claims 16 to 18 to be performed.

23. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 7, or causes the computer to perform the method as described in any one of claims 8 to 15, or causes the computer to perform the method as described in any one of claims 16 to 18.

Images